[Kernel-packages] [Bug 1284899] Re: [Dell Inspiron 1525] suspend/resume failure [non-free: wl]
I am having the same problem..when I close my laptop lid, and then open it up, I have a black screen like it's completely off and nothing seems to wake it up. dell inspiron 1525 as well.. each time I have to do a hard reboot, and when I do now that I have installed 14.04 today I do notice at the boot screen is very dim and I have to adjust the laptop brightness every time (i've turned the power off..if i reboot or shut down it stays normal). Never had any problems before. (12.04) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1284899 Title: [Dell Inspiron 1525] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Confirmed Bug description: Closed my laptop lid then re-opened there was nothing but a black screen with no backlight. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-12-generic 3.13.0-12.32 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kitcat 1846 F pulseaudio Date: Tue Feb 25 18:17:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3b336f44-9e4e-4b3a-b743-d7830226c736 InstallationDate: Installed on 2014-02-25 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Inspiron 1525 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-12-generic root=UUID=8f5677c8-cc1c-4865-b2d7-231dc7900176 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-12-generic N/A linux-backports-modules-3.13.0-12-generic N/A linux-firmware 1.125 SourcePackage: linux Title: [Dell Inc. Inspiron 1525] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Confirmed: works for me as well (UX302LG). Boot is alright and suspend to RAM can now normally resume (screen comes back to life). Brilliant! -- You 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 The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Triaged 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/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 1290745] Re: [Radeon HD 8670A][1002:6660] Unable to load into live desktop after clicked "Try Ubuntu" on 12.04.4 bootable usb drive
Also affects 201309-14197 HP 242 G2
8086:0416 Intel Corporation 4th Gen Core Processor Integrated Graphics
Controller
1002:6663 AMD Radeon HD 8570A/8570M
** Tags removed: precise
** Tags added: 201precise
** Tags removed: 201precise
** Tags added: 201309-14197 precise
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1290745
Title:
[Radeon HD 8670A][1002:6660] Unable to load into live desktop after
clicked "Try Ubuntu" on 12.04.4 bootable usb drive
Status in “linux” package in Ubuntu:
Confirmed
Status in “xorg-lts-saucy” package in Ubuntu:
Confirmed
Bug description:
Failed to load into live desktop after clicked the "Try Ubuntu" button on
welcome screen.
Expected:
Log into live desktop
Actual result:
Following prompted window, trying to run low-graphic mode still not able to
load the desktop, will fallback to console.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.11.0-15-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: PCH [HDA Intel PCH], device 0: ALC292 Analog [ALC292 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 3516 F pulseaudio
/dev/snd/controlC1: ubuntu 3516 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xf7d34000 irq 48'
Mixer name : 'Intel Haswell HDMI'
Components : 'HDA:80862807,80860101,0010'
Controls : 21
Simple ctrls : 3
Card1.Amixer.info:
Card hw:1 'PCH'/'HDA Intel PCH at 0xf7d3 irq 49'
Mixer name : 'Realtek ALC292'
Components : 'HDA:10ec0292,102805bd,0011'
Controls : 28
Simple ctrls : 13
CasperVersion: 1.315.1
DistroRelease: Ubuntu 12.04
LiveMediaBuild: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64
(20140204)
MachineType: Dell Inc. Latitude E6440
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 inteldrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
file=/cdrom/preseed/username.seed boot=casper quiet splash --
ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10
RelatedPackageVersions:
linux-restricted-modules-3.11.0-15-generic N/A
linux-backports-modules-3.11.0-15-generic N/A
linux-firmware 1.79.9
Tags: precise
Uname: Linux 3.11.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/03/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X23
dmi.board.name: 02P3T1
dmi.board.vendor: Dell Inc.
dmi.board.version: X03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrX23:bd07/03/2013:svnDellInc.:pnLatitudeE6440:pvr01:rvnDellInc.:rn02P3T1:rvrX03:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
---
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
CasperVersion: 1.315.1
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
DistUpgraded: Fresh install
DistroCodename: precise
DistroRelease: Ubuntu 12.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, even including gdb or git bisection work if
needed
GraphicsCard:
Intel Corporation 4th Gen Core Processor Integrated Graphics Controller
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:05bd]
Subsystem: Dell Device [1028:05bd]
LiveMediaBuild: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64
(20140204)
MachineType: Dell Inc. Latitude E6440
MarkForUpload: True
Package: xorg 1:7.6+12ubuntu2
PackageArchitecture: amd64
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
file=/cdrom/preseed/username.seed boot=casper quiet splash --
ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10
Tags: precise ubuntu referred-by-support
Uname: Linux 3.11.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/03/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X23
dmi.board.name: 02P3T1
dmi.board.vendor: Dell Inc.
dmi.board.version: X03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrX23:bd07/03/2013:svnDellInc.:pnLatitudeE6440:pvr01:rvnDellInc.:rn02P3T1:rvrX03:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6440
dmi.product.v
[Kernel-packages] [Bug 1307064] Re: Ubuntu 14.04 Beta cannot adjust brightness on Lenovo Ideapad Z570
This fix works in 3.13.0-24-generic. I hope that this helps someone else. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307064 Title: Ubuntu 14.04 Beta cannot adjust brightness on Lenovo Ideapad Z570 Status in “linux” package in Ubuntu: Incomplete Bug description: Fresh install of 14.04 on my laptop cannot adjust brightness. When fn+up arrow or fn+down arrow are used, the indicator in the upper right hand corner as if the brightness should change, but it does not. Also, if one tries to use the slider in the power applet, the brightness does not change. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: will 2960 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 12 21:36:57 2014 HibernationDevice: RESUME=UUID=dfa51f33-0f34-4383-8194-93656983323d InstallationDate: Installed on 2014-04-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: LENOVO 10249RU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=7420c61f-1836-4a44-84dc-71573190ff4c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN38WW 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:bvr45CN38WW:bd10/21/2011:svnLENOVO:pn10249RU:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 10249RU dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307064/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304001] Re: xen:balloon errors in 14.04 beta
** Attachment added: "srat.dsl" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4086876/+files/srat.dsl -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Confirmed Bug description: Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: --> pirq=16 -> irq=8 (gsi=8) [0.562622] xen: --> pirq=17 -> irq=12 (gsi=12) [0.562649] xen: --> pirq=18 -> irq=1 (gsi=1) [0.562673] xen: --> pirq=19 -> irq=6 (gsi=6) [0.562705] xen: --> pirq=20 -> irq=4 (gsi=4) [0.920527] xen: --> pirq=21 -> irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1307064] Re: Ubuntu 14.04 Beta cannot adjust brightness on Lenovo Ideapad Z570
Problem solved. Tried adding acpi_backlight=vendor to boot parameter. Did not work So I tried the recommendation for Intel HD Graphic Controllers. Created the file /usr/share/X11/xorg.conf.d/80-backlight.conf with below contents as recommended. Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "sna" Option "Backlight" "intel_backlight" # use your backlight that works here BusID "PCI:0:2:0" EndSection Problem Solved. I am still running the upstream kernel at this time. Will reboot into the final release kernel and report as to whether this works in that kernel as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307064 Title: Ubuntu 14.04 Beta cannot adjust brightness on Lenovo Ideapad Z570 Status in “linux” package in Ubuntu: Incomplete Bug description: Fresh install of 14.04 on my laptop cannot adjust brightness. When fn+up arrow or fn+down arrow are used, the indicator in the upper right hand corner as if the brightness should change, but it does not. Also, if one tries to use the slider in the power applet, the brightness does not change. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: will 2960 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 12 21:36:57 2014 HibernationDevice: RESUME=UUID=dfa51f33-0f34-4383-8194-93656983323d InstallationDate: Installed on 2014-04-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: LENOVO 10249RU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=7420c61f-1836-4a44-84dc-71573190ff4c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN38WW 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:bvr45CN38WW:bd10/21/2011:svnLENOVO:pn10249RU:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 10249RU dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307064/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309345] 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/1309345 Title: [Gateway LT28] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: I cant Upgrade ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fxone 1840 F pulseaudio Date: Fri Apr 18 01:10:38 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=ed9f8e68-d64b-4651-84b2-10b1b8b8d89e InstallationDate: Installed on 2014-02-11 (65 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140122) InterpreterPath: /usr/bin/python3.4 Lsusb: Bus 001 Device 002: ID 04f2:b209 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 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 MachineType: Gateway LT28 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=ad5aa7cf-1e2f-4416-bdcf-3ac256fba32f ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux Title: [Gateway LT28] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/26/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SJE06_PT dmi.board.vendor: Gateway dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.04:bd04/26/2011:svnGateway:pnLT28:pvrV1.04:rvnGateway:rnSJE06_PT:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: LT28 dmi.product.version: V1.04 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309345] [NEW] [Gateway LT28] suspend/resume failure
Public bug reported: I cant Upgrade ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fxone 1840 F pulseaudio Date: Fri Apr 18 01:10:38 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=ed9f8e68-d64b-4651-84b2-10b1b8b8d89e InstallationDate: Installed on 2014-02-11 (65 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140122) InterpreterPath: /usr/bin/python3.4 Lsusb: Bus 001 Device 002: ID 04f2:b209 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 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 MachineType: Gateway LT28 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=ad5aa7cf-1e2f-4416-bdcf-3ac256fba32f ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux Title: [Gateway LT28] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/26/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SJE06_PT dmi.board.vendor: Gateway dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.04:bd04/26/2011:svnGateway:pnLT28:pvrV1.04:rvnGateway:rnSJE06_PT:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: LT28 dmi.product.version: V1.04 dmi.sys.vendor: Gateway ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-kerneloops i386 resume suspend trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309345 Title: [Gateway LT28] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: I cant Upgrade ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fxone 1840 F pulseaudio Date: Fri Apr 18 01:10:38 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=ed9f8e68-d64b-4651-84b2-10b1b8b8d89e InstallationDate: Installed on 2014-02-11 (65 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140122) InterpreterPath: /usr/bin/python3.4 Lsusb: Bus 001 Device 002: ID 04f2:b209 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 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 MachineType: Gateway LT28 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=ad5aa7cf-1e2f-4416-bdcf-3ac256fba32f ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux Title: [Gateway LT28] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/26/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SJE06_PT dmi.board.vendor: Ga
[Kernel-packages] [Bug 1307064] Re: Ubuntu 14.04 Beta cannot adjust brightness on Lenovo Ideapad Z570
I think I should elaborate on my previous post. I have 2 entries in /sys/class/backlight acpi_video0 intel_backlight When I use the slider in the brightness applet or the hotkeys to change the brightness, the value of /sys/class/backlight/acpi_video0 is changing. This being the case, I believe that if I could point both of those to /sys/class/backlight/intel_backlight/brightness the problem would be solved. This is where I fall down as I do not know how to do this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307064 Title: Ubuntu 14.04 Beta cannot adjust brightness on Lenovo Ideapad Z570 Status in “linux” package in Ubuntu: Incomplete Bug description: Fresh install of 14.04 on my laptop cannot adjust brightness. When fn+up arrow or fn+down arrow are used, the indicator in the upper right hand corner as if the brightness should change, but it does not. Also, if one tries to use the slider in the power applet, the brightness does not change. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: will 2960 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 12 21:36:57 2014 HibernationDevice: RESUME=UUID=dfa51f33-0f34-4383-8194-93656983323d InstallationDate: Installed on 2014-04-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: LENOVO 10249RU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=7420c61f-1836-4a44-84dc-71573190ff4c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN38WW 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:bvr45CN38WW:bd10/21/2011:svnLENOVO:pn10249RU:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 10249RU dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307064/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1307064] Re: Ubuntu 14.04 Beta cannot adjust brightness on Lenovo Ideapad Z570
I appologize for the poorly written original bug report. I was very tired and had been working on this for some time. As mentioned at https://wiki.ubuntu.com/Kernel/Debugging/Backlight, I think that it may be helpful if I include that I do have entries in /sys/class/backlight. I can change brightness by issuing the below command ~$ echo 150 | sudo tee /sys/class/backlight/intel_backlight/brightness -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307064 Title: Ubuntu 14.04 Beta cannot adjust brightness on Lenovo Ideapad Z570 Status in “linux” package in Ubuntu: Incomplete Bug description: Fresh install of 14.04 on my laptop cannot adjust brightness. When fn+up arrow or fn+down arrow are used, the indicator in the upper right hand corner as if the brightness should change, but it does not. Also, if one tries to use the slider in the power applet, the brightness does not change. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: will 2960 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 12 21:36:57 2014 HibernationDevice: RESUME=UUID=dfa51f33-0f34-4383-8194-93656983323d InstallationDate: Installed on 2014-04-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: LENOVO 10249RU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=7420c61f-1836-4a44-84dc-71573190ff4c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN38WW 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:bvr45CN38WW:bd10/21/2011:svnLENOVO:pn10249RU:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 10249RU dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307064/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1213239] Re: [Lenovo ThinkPad Twist] Bluetooth subsystem dies after suspend
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1213239 Title: [Lenovo ThinkPad Twist] Bluetooth subsystem dies after suspend Status in “linux” package in Ubuntu: Expired Bug description: I am using Saucy in XMir mode with the standard Unity desktop on the Lenovo Thinkpad Twist. When I suspend the system not only the suspend itself is broken (bug 1213233) but also after waking up I cannot use my Bluetooth devices any more (mouse, keyboard). I have to reboot to get Bluetooth back working. Do not ask me to update the BIOS from 1.52 to 1.57, this leads to bug 1210748. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: till 3099 F pulseaudio Date: Fri Aug 16 22:19:52 2013 HibernationDevice: RESUME=UUID=e0af6e5c-3cf3-47e2-8603-6a9ffb019484 InstallationDate: Installed on 2013-06-05 (72 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130605) MachineType: LENOVO 334729G MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=80d8eb01-b0c3-47cc-8dba-1ed122b2be4f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-2-generic N/A linux-backports-modules-3.11.0-2-generic N/A linux-firmware1.113 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GDET92WW (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 334729G dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGDET92WW(1.52):bd02/05/2013:svnLENOVO:pn334729G:pvrThinkPadTwist:rvnLENOVO:rn334729G:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 334729G dmi.product.version: ThinkPad Twist dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1279308] Re: [MacBook Air 6, 2] screen backlight brightness and keyboard light turn into fully-on after Grub boot with i915 driver
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1279308 Title: [MacBook Air 6,2] screen backlight brightness and keyboard light turn into fully-on after Grub boot with i915 driver Status in “linux” package in Ubuntu: Expired Bug description: Problem: Both the screen backlight brightness and keyboard light are turned on during the booting as tested on ubuntu 12.04.3, 12.04.4, and 13.10. Due to installation problem on 12.04, it's only tested with the live system. What's expected: the brightness state before booting is preserved. Some trials: the problem should be on i915 driver even in single user mode. Tried "nomodeset" kerenel arguement can avoid the problem, but X will fail to start. --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1776 F pulseaudio /dev/snd/controlC1: john 1776 F pulseaudio DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2014-02-10 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookAir6,2 MarkForUpload: True NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=b52fef82-3749-4624-a352-bd750dcb7e65 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 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 Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/12/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B07.1311121319 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B07.1311121319:bd11/12/2013:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.name: MacBookAir6,2 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/1279308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265940] Re: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0015 address=0x0000000000001000 flags=0x0000]
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1265940 Title: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0015 address=0x1000 flags=0x] Status in “linux” package in Ubuntu: Expired Bug description: Many errors in /var/log/kern.log and /var/log/syslog like: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0015 address=0x1000 flags=0x] These files grow constantly, taking more than 10 GB in 4-5 hours. --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: krot 2131 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e26cb278-a987-418b-8a29-699a1c582847 InstallationDate: Installed on 2012-10-21 (439 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=d3f644cf-a581-4546-97ec-666292691b65 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 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 Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-11-02 (62 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo dmi.bios.date: 12/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8e dmi.board.name: GA-970A-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8e:bd12/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1205104] Re: 12d1:1446 Huawei E173 only detected as mass storage
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1205104
Title:
12d1:1446 Huawei E173 only detected as mass storage
Status in “linux” package in Ubuntu:
Expired
Bug description:
My Huawei E173 UMTS-Stick is only detected as a mass storage device so I
can't connect to the internet with Ubuntu 13.10.
It works great with Ubuntu 13.04
lsusb:
Bus 002 Device 006: ID 12d1:1446 Huawei Technologies Co., Ltd.
E1552/E1800/E173 (HSPA modem)
I tried to add "usbserial " into the /etc/modules, but that didn't
help.
Also this USB device is already included in
/lib/udev/rules.d/40-usb_modeswitch.rules
# Huawei, newer modems
ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1446", RUN+="usb_modeswitch
'%b/%k'"
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-generic 3.10.0.5.14
ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2
Uname: Linux 3.10.0-5-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 3761 F pulseaudio
ubuntu 5721 F pulseaudio
CasperVersion: 1.335
Date: Thu Jul 25 20:46:32 2013
LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130725)
MachineType: Dell Inc. XPS M1330
MarkForUpload: True
ProcFB: 0 nouveaufb
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet
splash -- maybe-ubiquity
RelatedPackageVersions:
linux-restricted-modules-3.10.0-5-generic N/A
linux-backports-modules-3.10.0-5-generic N/A
linux-firmware1.112
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: XPS M1330
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205104/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1279522] Re: [Acer Aspire one] suspend/resume failure
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1279522 Title: [Acer Aspire one] suspend/resume failure Status in “linux” package in Ubuntu: Expired Bug description: In attempting to resume after suspension, the screen was just off, black. I had to force shutdown. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-8-generic 3.13.0-8.27 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1243 F pulseaudio corrado2321 F pulseaudio /dev/snd/pcmC0D0p: corrado2321 F...m pulseaudio CurrentDmesg: [ 120.678109] perf samples too long (2513 > 2500), lowering kernel.perf_event_max_sample_rate to 5 Date: Wed Feb 12 22:03:49 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=192a6da9-1e42-437a-8ff9-4099a2d16ea5 InstallationDate: Installed on 2014-02-02 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140202) InterpreterPath: /usr/bin/python3.3 MachineType: Acer Aspire one ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=93b02eff-9f12-44b6-9864-87fb1bc5c158 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-8-generic N/A linux-backports-modules-3.13.0-8-generic N/A linux-firmware1.123 SourcePackage: linux Title: [Acer Aspire one] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/28/2009 dmi.bios.vendor: Acer dmi.bios.version: V1.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire one dmi.board.vendor: Acer dmi.board.version: V1.21 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.21 dmi.modalias: dmi:bvnAcer:bvrV1.21:bd09/28/2009:svnAcer:pnAspireone:pvrV1.21:rvnAcer:rnAspireone:rvrV1.21:cvnAcer:ct10:cvrV1.21: dmi.product.name: Aspire one dmi.product.version: V1.21 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1279522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1263219] Re: kernel panics with BUG
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1263219 Title: kernel panics with BUG Status in “linux” package in Ubuntu: Expired Bug description: I have a Dell Sputnik 3 that I just got and upgraded it to 12.10->13.04->13.10. On boot the kernel crashes with a BUG. Attached is a dmesg output from after the loading of the module. WORKAROUND: I can prevent the crash by blacklisting the iwlwifi module and I can cause the BUG by manually loading the module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
I have the same problem. My laptop is x240, and the wireless card is the same one, Realtek RTL8192EE [10ec:818b]. Waiting to solutions! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next Project: Incomplete Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308474] Re: CPU-intensive processes killed by OS
** Tags added: kernel-bug-reported-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Triaged Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/3 13 root 20 0 000 S 3 0.0 0.0 0:27 rcu_sched 14
[Kernel-packages] [Bug 1291113] Re: Intel igb driver infinite loop in ksoftirqd, uses 100% of cpu 0
Testing 3.11.0-20~precise1 and this issue appears to be resolved. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1291113 Title: Intel igb driver infinite loop in ksoftirqd, uses 100% of cpu 0 Status in “linux” package in Ubuntu: Fix Released Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Committed Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux” source package in Trusty: Fix Released Status in “linux-lts-raring” source package in Trusty: Invalid Bug description: This bug is present in 3.11.0-17 and 3.11.0-18: https://lkml.org/lkml/2014/2/19/658 The afflicted network interface's lspci output: 02:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) Subsystem: Super Micro Computer Inc Device 1521 Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at df92 (32-bit, non-prefetchable) [size=128K] I/O ports at 8020 [size=32] Memory at df944000 (32-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [70] MSI-X: Enable+ Count=10 Masked- Capabilities: [a0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 00-xx-xx-xx-xx-xx-xx-xx Capabilities: [150] Alternative Routing-ID Interpretation (ARI) Capabilities: [160] Single Root I/O Virtualization (SR-IOV) Capabilities: [1a0] Transaction Processing Hints Capabilities: [1c0] Latency Tolerance Reporting Capabilities: [1d0] Access Control Services Kernel driver in use: igb Kernel modules: igb [I have masked out the MAC address] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308751] Re: Transfer to USB drive slows down to a crawl
** Tags added: kernel-bug-exists-upstream-v3.15-rc1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308751 Title: Transfer to USB drive slows down to a crawl Status in “linux” package in Ubuntu: Confirmed Bug description: This problem has been affecting this computer release after release for as long as I can remember. Kernel is 3.13.0-24-generic #46 When transferring 2.7 Go to a fat32 formatted USB drive, transfer starts at 50 Mb/s and finishes at 5.6 Mb/s, with the transfer dialog staying open for minutes with 0 Mb left to transfer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ao 2970 F pulseaudio /dev/snd/controlC0: ao 2970 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 16:29:42 2014 InstallationDate: Installed on 2014-04-06 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=b49aac97-cebf-48a0-b5b2-db2b0c148a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88TD-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1082418] Re: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access
** Summary changed: - [Fujitsu Lifebook AH532 & AH552] Ubuntu UEFI install locks out UEFI firmware (~bios) access + [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1082418 Title: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access Status in “linux” package in Ubuntu: Expired Bug description: lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 apt-cache policy grub-efi-amd64 grub-efi-amd64: Installed: 2.00-7ubuntu11 Candidate: 2.00-7ubuntu11 Pheonix Secure Core Tiano bios version 1.09 New laptop Fujitsu Lifebook AH532. Windows 7 preinstalled. All functions worked normally when running Win7. Ubuntu 12.10 installed using whole disk. Installation successful Ubuntu boots and runs normally, however all access to the bios has now been lost. Pressing the default key (f2) during boot up is acknowledged by bios beep, but ignored and Ubuntu continues booting. In addition the 'boot choices' menu (f12) contains nothing but Ubuntu making it impossible to boot from USB or CD/DVD. The latter (f12) problem was overcome by opening up the machine, removing the ram and shorting the cl1/cl2 posts with a screwdriver. This restores the ability to boot from USB/CD by pressing f12 but does not restore bios access. The following recovery actions have been tried. 1) Install Boot-Repair, run repair, no change occurred. Boot repair report here: http://paste.ubuntu.com/1375041/ 2) Restore Windows from Clonezilla disk image (factory settings) - result - bios access is no longer possible from windows either, f2 now launches the Windows boot menu. 3) Update all drivers using Fujitsu driver update tool from within windows (which included a bios update). Result - no change, no bios. 4) Restored Ubuntu from Clonezilla disk image - no change. 5) Added second distro to disk. Installed successfully (uefi mode as that is all I have) no change to bios access. So overall result I have lost all bios access even from a reinstalled Windows. I repeat that bios access was perfectly normal before installing Ubuntu. I strongly suggest you read the contents of this thread in addition to the information here: http://ubuntuforums.org/showthread.php?t=2086602 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: grub-efi 2.00-7ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Fri Nov 23 15:50:07 2012 InstallationDate: Installed on 2012-11-22 (1 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308751] Re: Transfer to USB drive slows down to a crawl
** Tags added: latest-bios-1501 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308751 Title: Transfer to USB drive slows down to a crawl Status in “linux” package in Ubuntu: Confirmed Bug description: This problem has been affecting this computer release after release for as long as I can remember. Kernel is 3.13.0-24-generic #46 When transferring 2.7 Go to a fat32 formatted USB drive, transfer starts at 50 Mb/s and finishes at 5.6 Mb/s, with the transfer dialog staying open for minutes with 0 Mb left to transfer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ao 2970 F pulseaudio /dev/snd/controlC0: ao 2970 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 16:29:42 2014 InstallationDate: Installed on 2014-04-06 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=b49aac97-cebf-48a0-b5b2-db2b0c148a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88TD-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 500069] Re: USB file transfer causes system freezes; ops take hours instead of minutes
Ubuntu-QC-1, 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 ** Tags removed: apport-collected bot-stop-nagging. slow trusty usb ** Tags added: bot-stop-nagging ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085731/+files/WifiSyslog.txt ** Attachment removed: "UdevLog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085730/+files/UdevLog.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085729/+files/UdevDb.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085728/+files/PulseList.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085727/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085726/+files/ProcInterrupts.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085725/+files/ProcEnviron.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085724/+files/ProcCpuinfo.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085723/+files/Lsusb.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085722/+files/Lspci.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085721/+files/IwConfig.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085720/+files/CurrentDmesg.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085719/+files/CRDA.txt ** Attachment removed: "BootDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085718/+files/BootDmesg.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500069/+attachment/4085717/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/500069 Title: USB file transfer causes system freezes; ops take hours instead of minutes Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Status in “linux” package in Fedora: Unknown Bug description: USB Drive is a MP3 Player 2GB sbec@Diamant:~$ lsusb Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. MX-1000 Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 004: ID 0402:5661 ALi Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub sbec@Diamant:~$ Linux Diamant 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:54:29 UTC 2009 i686 GNU/Linux Ubuntu 2.6.31-15.50-generic to test, i issued dd command: dd if=/dev/zero of=/media/usb-disk/test-file bs=32 while dd is running i run dstat this is in the log file attached. other logs are also in the tar.gz file... there is a huge USB performance Bug report #1972262. this Report is something simular To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/500069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308751] Re: Transfer to USB drive slows down to a crawl
** Description changed: - This is a duplicate of bug #500069 filled to be able to track the - hardware as instructed by Christopher M. Penalver. - This problem has been affecting this computer release after release for as long as I can remember. Kernel is 3.13.0-24-generic #46 When transferring 2.7 Go to a fat32 formatted USB drive, transfer starts at 50 Mb/s and finishes at 5.6 Mb/s, with the transfer dialog staying open for minutes with 0 Mb left to transfer. - - Please let me know how I could provide extra info, run more tests. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: ao 2970 F pulseaudio - /dev/snd/controlC0: ao 2970 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: ao 2970 F pulseaudio + /dev/snd/controlC0: ao 2970 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 16:29:42 2014 InstallationDate: Installed on 2014-04-06 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=b49aac97-cebf-48a0-b5b2-db2b0c148a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.13.0-24-generic N/A - linux-backports-modules-3.13.0-24-generic N/A - linux-firmware 1.127 + linux-restricted-modules-3.13.0-24-generic N/A + linux-backports-modules-3.13.0-24-generic N/A + linux-firmware 1.127 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88TD-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308751 Title: Transfer to USB drive slows down to a crawl Status in “linux” package in Ubuntu: Confirmed Bug description: This problem has been affecting this computer release after release for as long as I can remember. Kernel is 3.13.0-24-generic #46 When transferring 2.7 Go to a fat32 formatted USB drive, transfer starts at 50 Mb/s and finishes at 5.6 Mb/s, with the transfer dialog staying open for minutes with 0 Mb left to transfer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ao 2970 F pulseaudio /dev/snd/controlC0: ao 2970 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 16:29:42 2014 InstallationDate: Installed on 2014-04-06 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=b49aac97-cebf-48a0-b5b2-db2b0c148a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88TD-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture
[Kernel-packages] [Bug 1228109] Re: [Lenovo ThinkCentre M91p] System freezes
Christopher Penalver, I upgraded to the Saucy enablement stack. Unfortunately, things did not improve - I still have system freezes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1228109 Title: [Lenovo ThinkCentre M91p] System freezes Status in “linux” package in Ubuntu: Confirmed Bug description: * Problem description: The system freezes completely. This includes screen, mouse, and keyboard including numlock light. Even after several weeks of testing I was not able to tie the freezes to a specific event, program, or behavior. There seem to be a few scenarios where freezes are more likely (see below), but they can essentially occur at any time. I have updated my bios and the system; this did not solve the problem. I have not yet tried the mainline kernel, since I am unsure which version to select. * Steps to reproduce: Run long-term measurement device remote control in Matlab (data collection; SCPI, low cpu load, some network, a couple GB RAM usage). The system typically freezes within 24 to 48 hours. I have also tried several other scenarios: - normal work with KDE (Kile, Thunderbird, Firefox, Inkscape, VLC, Dolphin): RARELY (~ once a month) - measurement device remote control in Matlab (memory, network). The following didn't seem to reproduce the problem: - running date + sleep in a bash loop. - running date + sleep in a bash loop within screen. - running ping constantly. - idle loop in Matlab (do nothing). - random data copying loop in Matlab (memory only). * Keeping CPU load high by inverting a some matrix in the data collection loop seems to prevent this problem. * Last working version: Kubuntu 11.10 * Additional information: - memory test came back negative (no problems) - crash is reproducible on a text console - could not obtain trace dump (system does not react to keyboard) Neither of the following fixed the problem: xserver-xorg-lts-quantal libgl1-mesa-dri-lts-quantal:i386 libgl1-mesa-glx-lts-quantal:i386 or fixing the "*BAD*gran_size" issue described in: http://my-fuzzy-logic.de/blog/index.php?/archives/41-Solving-linux-MTRR-problems.html ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-40-generic 3.5.0-40.62~precise1 ProcVersionSignature: Ubuntu 3.5.0-40.62~precise1-generic 3.5.7.20 Uname: Linux 3.5.0-40-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arnitz 2208 F pulseaudio /dev/snd/controlC0: arnitz 2208 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfe52 irq 44' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0662,17aa3070,00100101 HDA:80862805,17aa3070,0010' Controls : 36 Simple ctrls : 16 Card1.Amixer.info: Card hw:1 'Audio'/'Plantronics Wireless Audio Plantronics Wireless Audio at usb-:00:1d.0-1.4, ' Mixer name : 'USB Mixer' Components : 'USB047f:d955' Controls : 4 Simple ctrls : 2 Date: Fri Sep 20 08:13:34 2013 HibernationDevice: RESUME=UUID=2f562564-0248-4280-a46b-9cd0f0e8e5e6 InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 4524-AN4 MarkForUpload: True ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-40-generic root=UUID=af77f384-9007-4d2b-8395-5ada0dcfb93e ro quiet splash enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=64K mtrr_chunk_size=256M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-40-generic N/A linux-backports-modules-3.5.0-40-generic N/A linux-firmware1.79.6 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to precise on 2013-06-20 (91 days ago) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524-AN4:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524-AN4 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1228109/+subscriptions -- Mailing list: https://launchpad.net/~ke
[Kernel-packages] [Bug 1225811] Re: 1002:6601 [Dell Inspiron 15R 5521] Can't toggle backlight brightness
** Tags removed: kernel-bug-exists-upstream ** Tags added: needs-upstream-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1225811 Title: 1002:6601 [Dell Inspiron 15R 5521] Can't toggle backlight brightness Status in “linux” package in Ubuntu: Confirmed Bug description: Since raring at least, it is not possible to change backlight brightness. WORKAROUND: Add acpi_backlight=vendor into grub boot option. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-generic 3.11.0.7.8 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas2839 F pulseaudio Date: Mon Sep 16 02:05:10 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=173db09c-bffc-4da9-ab42-7ca73f84e71f InstallationDate: Installed on 2013-04-08 (160 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Dell Inc. Inspiron 5521 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=09af3e13-8004-48fa-b0fe-116acbf8d3d7 ro crashkernel=384M-2G:64M,2G-:128M quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-5-generic N/A linux-backports-modules-3.11.0-5-generic N/A linux-firmware1.114 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to saucy on 2013-06-24 (83 days ago) dmi.bios.date: 06/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0HK2KG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/25/2013:svnDellInc.:pnInspiron5521:pvrA09:rvnDellInc.:rn0HK2KG:rvrA00:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron 5521 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1225811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305960] Re: [Dell Inspiron 620s] suspend/resume failure
Mayagrafix, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305960/comments/4 regarding this being fixed with a BIOS update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305960 Title: [Dell Inspiron 620s] suspend/resume failure Status in “linux” package in Ubuntu: Invalid Bug description: Upon start up error message appeared. Ask if I want to report. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mayagrafix 3445 F pulseaudio Date: Thu Apr 10 09:50:40 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=a8fec92d-ea0e-4ac7-88ce-682e5e627d81 InstallationDate: Installed on 2013-04-03 (371 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Inspiron 620s ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=41040b88-9b6d-459e-ab47-91c09e3bd0af ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [Dell Inc. Inspiron 620s] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-30 (11 days ago) UserGroups: dmi.bios.date: 11/21/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0GDG8Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd11/21/2011:svnDellInc.:pnInspiron620s:pvr00:rvnDellInc.:rn0GDG8Y:rvrA00:cvnDellInc.:ct3:cvr00: dmi.product.name: Inspiron 620s dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304625] Re: [MSI 880GM-E41] No Desktop Display for kernel versions
FlacBean02, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc1-trusty/ ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304625 Title: [MSI 880GM-E41] No Desktop Display for kernel versions Status in “linux” package in Ubuntu: Incomplete Bug description: Upon logging in with Username and Password, desktop will not show. Black screen... No Desktop Display for kernel versions 3.11.0-19.33 3.11.0-20.34 Desktop displays for kernel versions 3.11.0-18.32 and older Installed Propitery drivers AMD Catalyst™ 14.3 LINUX Beta V1.0 Driver Running Ubuntu 13.10 with all updates including proposed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-18-generic 3.11.0-18.32 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: master 1820 F pulseaudio /dev/snd/controlC0: master 1820 F pulseaudio Date: Tue Apr 8 15:45:52 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ab6d2e50-fef6-4f8c-9d79-96cffdb4cd9f InstallationDate: Installed on 2013-12-28 (101 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: MSI MS-7623 MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=b38cf669-0485-4a08-bf2d-c324d4e7f185 ro radeon.audio=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-18-generic N/A linux-backports-modules-3.11.0-18-generic N/A linux-firmware 1.116.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V11.7 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 880GM-E41 (MS-7623) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV11.7:bd10/22/2010:svnMSI:pnMS-7623:pvr2.0:rvnMSI:rn880GM-E41(MS-7623):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7623 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1261063] Re: [Dell Inspiron 660] Occasional "The disk drive for /dev/mapper/cryptswap1 is not ready yet or not present" on system startup
The problem persists with Ubuntu 14.04 LTS Trusty Tahr. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1261063 Title: [Dell Inspiron 660] Occasional "The disk drive for /dev/mapper/cryptswap1 is not ready yet or not present" on system startup Status in “linux” package in Ubuntu: Confirmed Bug description: Occasional "The disk drive for /dev/mapper/cryptswap1 is not ready yet or not present" on system startup. 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 i686 ApportVersion: 2.12.7-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2833 F pulseaudio CasperVersion: 1.336ubuntu1 CurrentDesktop: Unity Date: Sun Dec 15 01:18:43 2013 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131214) MachineType: Dell Inc. Inspiron 660 ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-3.12.0-7-generic N/A linux-backports-modules-3.12.0-7-generic N/A linux-firmware1.117 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 084J0R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/13/2013:svnDellInc.:pnInspiron660:pvr:rvnDellInc.:rn084J0R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Inspiron 660 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1243904] Re: [LG P1-J273B] Internal keyboard doesn't work in 13.10
Hi Jalgi, Could you help me to review these changes or cherry-pick these changes and build/verify on your labtop? I only verified on LG Electronics LW25-B7HV. Thanks, Shengliang Song -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1243904 Title: [LG P1-J273B] Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Incomplete Bug description: My laptop is a lg p1 express dual. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305322] Re: [ASUS K53E] suspend/resume failure
Jason Lee, when providing the information requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305322/comments/3 please ensure it is in the latest mainline kernel as noted in the article. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305322 Title: [ASUS K53E] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: My laptop failed to resume from a suspended state. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 2226 F pulseaudio Date: Wed Apr 9 14:15:11 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=71ed8f80-8de1-465a-aaf8-51677cb1028b InstallationDate: Installed on 2014-02-12 (56 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: ASUSTeK Computer Inc. K53E ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=bfb9a886-0429-42e2-80a2-72e76865323c ro quiet splash ipv6.disable=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux Title: [ASUSTeK Computer Inc. K53E] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-04-08 (1 days ago) UserGroups: dmi.bios.date: 08/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53E.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53E 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/1305322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1307674] Re: Broadcom BCM57765/57785 SDXC/MMC Card Reader doesn't work
** Description changed: I have a Broadcom BCM57765/57785 SDXC/MMC Card Reader internally in my MacBook Pro Retina 13", and it does not work. - - This is pretty much a duplicate of - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1067222 as - requested by Christopher M. Penalver (penalvch). - - None of the suggested workarounds in the linked bug work for me. Some - people can work around this bug by plugging something into the ethernet - port corresponding to the PCI device in question, but this machine does - not have such an ethernet port exposed. The chip seems to be here only - for the SD card reader. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: mag2387 F pulseaudio - mag2896 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: mag2387 F pulseaudio + mag2896 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 14 21:30:38 2014 HibernationDevice: RESUME=UUID=060f761f-a7ab-442b-9186-51ab74e03896 InstallationDate: Installed on 2013-09-14 (212 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Apple Inc. MacBookPro10,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: \EFI\linux\vmlinuz-3.13.0-24-generic ro root=UUID=61126328-c29e-40a6-913f-7f8690a455bc quiet splash $vt_handoff initrd=EFI\linux\initrd.img-3.13.0-24-generic RelatedPackageVersions: - linux-restricted-modules-3.13.0-24-generic N/A - linux-backports-modules-3.13.0-24-generic N/A - linux-firmware 1.127 + linux-restricted-modules-3.13.0-24-generic N/A + linux-backports-modules-3.13.0-24-generic N/A + linux-firmware 1.127 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-11 (3 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP102.88Z.0106.B03.1211161133 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-AFD8A9D944EA4843 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-AFD8A9D944EA4843 dmi.modalias: dmi:bvnAppleInc.:bvrMBP102.88Z.0106.B03.1211161133:bd11/16/2012:svnAppleInc.:pnMacBookPro10,2:pvr1.0:rvnAppleInc.:rnMac-AFD8A9D944EA4843:rvrMacBookPro10,2:cvnAppleInc.:ct10:cvrMac-AFD8A9D944EA4843: dmi.product.name: MacBookPro10,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Tags removed: kernel-bug-exists-upstream ** Tags added: kernel-bug-exists-upstream-v3.15-rc1 latest-bios-11-16-2012 ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307674 Title: Broadcom BCM57765/57785 SDXC/MMC Card Reader doesn't work Status in “linux” package in Ubuntu: Triaged Bug description: I have a Broadcom BCM57765/57785 SDXC/MMC Card Reader internally in my MacBook Pro Retina 13", and it does not work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mag2387 F pulseaudio mag2896 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 14 21:30:38 2014 HibernationDevice: RESUME=UUID=060f761f-a7ab-442b-9186-51ab74e03896 InstallationDate: Installed on 2013-09-14 (212 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Apple Inc. MacBookPro10,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: \EFI\linux\vmlinuz-3.13.0-24-generic ro root=UUID=61126328-c29e-40a6-913f-7f8690a455bc quiet splash $vt_handoff initrd=EFI\linux\initrd.img-3.13.0-24-generic RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-11 (3 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP102.88Z.0106.B03.1211161133 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-AFD8A9D944EA4843 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-AF
[Kernel-packages] [Bug 1305371] Re: [Dell Inspiron 1525] suspend/resume failure
** 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/1305371 Title: [Dell Inspiron 1525] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: suspend/resume failed. restart required to bring back system ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ashraf 1484 F pulseaudio Date: Thu Apr 10 06:30:00 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=f4caffe3-3165-417b-bd56-386b8e3852b8 InstallationDate: Installed on 2014-03-29 (11 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Inspiron 1525 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=26592a1f-092c-4949-9107-771865219fcd ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux Title: [Dell Inc. Inspiron 1525] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304618] Re: [SAMSUNG NP900X4D-K03SE] suspend/resume failure
** Summary changed: - [SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D] suspend/resume failure + [SAMSUNG NP900X4D-K03SE] suspend/resume failure ** Tags removed: needs-full-computer-model -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304618 Title: [SAMSUNG NP900X4D-K03SE] suspend/resume failure Status in “linux” package in Ubuntu: Fix Released Bug description: Bug is send by system Ubuntu 14.04 beta LTS. Keyboard lights don't not work in samsumg 900x4D. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harri 1867 F pulseaudio Date: Tue Apr 8 22:03:22 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=e79e4d62-348e-4c75-8878-bb5cbdc19c89 InstallationDate: Installed on 2014-02-28 (39 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic.efi.signed root=UUID=27b58a85-9628-45ed-a797-06e373351f65 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux Title: [SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (36 days ago) UserGroups: dmi.bios.date: 11/01/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P10ABK dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP900X4D-K03SE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP10ABK:bd11/01/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X4D-K03SE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305137] Re: [LENOVO ThinkPad Edge E430] hibernate/resume failure
XmlsTeR, as per http://download.lenovo.com/express/ddfm.html an update to your BIOS is available (2.55). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Thank you for your understanding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305137 Title: [LENOVO ThinkPad Edge E430] hibernate/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: Wake up from suspend only works after a short period of time. After a longer sleep it crashes and reboots on resume. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 Annotation: This occured during a previous hibernate and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xmister2579 F pulseaudio /dev/snd/controlC0: xmister2579 F pulseaudio Date: Wed Apr 9 17:16:17 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=8a7f855a-0d14-4691-aab8-c48d936a5ee0 InstallationDate: Installed on 2013-02-06 (427 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 3254A8G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=debb9bc7-0b26-4231-8b9e-f09d2dfbc579 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Title: [LENOVO 3254A8G] hibernate/resume failure UpgradeStatus: Upgraded to trusty on 2014-01-26 (73 days ago) UserGroups: sbuild dmi.bios.date: 08/02/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 3254A8G 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:bvrH0ET94WW(2.54):bd08/02/2013:svnLENOVO:pn3254A8G:pvrThinkPadEdgeE430:rvnLENOVO:rn3254A8G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3254A8G dmi.product.version: ThinkPad Edge E430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308311] Re: uvcvideo kernel module crash
Just tried cheese, can start that multiple times as well (not always getting video), but when it does, I get a very psychedelic view, i.e. a lot of distortion all over the image. At times it's better then at other times. Starting guvcview gives me a perfect image everytime. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308311 Title: uvcvideo kernel module crash Status in “linux” package in Ubuntu: Incomplete Bug description: Symptom: video works once, but crashes during use, or at second use. Happened on 32-bit precise too. /var/log/syslog startup messages: Apr 16 09:46:46 quadrio kernel: [6.181754] input: UVC Camera (17ef:480c) as /devices/pci:00/:00:1d.7/usb2/2-4/2-4:1.0/input/input16 Apr 16 09:46:46 quadrio kernel: [6.183111] usbcore: registered new interface driver uvcvideo When it crashes: Apr 16 14:26:39 quadrio kernel: [16798.368345] uvcvideo: Failed to query (SET_CUR) UVC control 3 on unit 1: -110 (exp. 1). Apr 16 14:26:44 quadrio kernel: [16803.368274] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:26:49 quadrio kernel: [16808.368322] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:26:54 quadrio kernel: [16813.368402] uvcvideo: Failed to set UVC commit control : -110 (exp. 26). Apr 16 14:26:59 quadrio kernel: [16818.368341] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:04 quadrio kernel: [16823.368421] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:09 quadrio kernel: [16828.368336] uvcvideo: Failed to set UVC commit control : -110 (exp. 26). Apr 16 14:27:14 quadrio kernel: [16833.368392] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:19 quadrio kernel: [16838.368326] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:24 quadrio kernel: [16843.368272] uvcvideo: Failed to set UVC commit control : -110 (exp. 26). Does not start working even after an rmmod/modprobe of this module. Need a reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berend 3658 F pulseaudio /dev/snd/pcmC0D0c: berend 3658 F...m pulseaudio /dev/snd/pcmC0D0p: berend 3658 F...m pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 14:42:24 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-01 (15 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: LENOVO 2757CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=UUID=52ddc899-ca26-4fe9-b2ba-e7562258b42c ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZET71WW (1.54 ) dmi.board.name: 2757CTO 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:bvr7ZET71WW(1.54):bd11/27/2008:svnLENOVO:pn2757CTO:pvrThinkPadW700:rvnLENOVO:rn2757CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2757CTO dmi.product.version: ThinkPad W700 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1309246] Re: Keyboard not recognized when typing encryption password
I'd love to, but I don't know what to do. Is there documentation? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309246 Title: Keyboard not recognized when typing encryption password Status in “linux” package in Ubuntu: Confirmed Bug description: My keyboard is not recognized at the initial prompt to unencrypt my harddrive's full-disk encryption if I boot into kernel 3.13.0-24. If I instead boot kernel 3.13.0-23, my keyboard is recognized. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ian2424 F pulseaudio /dev/snd/controlC0: ian2424 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 17 18:00:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-22 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140221) MachineType: TOSHIBA Satellite L875D ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308311] Re: uvcvideo kernel module crash
In addition: just installed guvcview, after power-down, I can start guvcview multiple times, record video, capture image, all works. But I'm pretty sure if I start Skype and go to its video settings, the camera will crash again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308311 Title: uvcvideo kernel module crash Status in “linux” package in Ubuntu: Incomplete Bug description: Symptom: video works once, but crashes during use, or at second use. Happened on 32-bit precise too. /var/log/syslog startup messages: Apr 16 09:46:46 quadrio kernel: [6.181754] input: UVC Camera (17ef:480c) as /devices/pci:00/:00:1d.7/usb2/2-4/2-4:1.0/input/input16 Apr 16 09:46:46 quadrio kernel: [6.183111] usbcore: registered new interface driver uvcvideo When it crashes: Apr 16 14:26:39 quadrio kernel: [16798.368345] uvcvideo: Failed to query (SET_CUR) UVC control 3 on unit 1: -110 (exp. 1). Apr 16 14:26:44 quadrio kernel: [16803.368274] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:26:49 quadrio kernel: [16808.368322] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:26:54 quadrio kernel: [16813.368402] uvcvideo: Failed to set UVC commit control : -110 (exp. 26). Apr 16 14:26:59 quadrio kernel: [16818.368341] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:04 quadrio kernel: [16823.368421] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:09 quadrio kernel: [16828.368336] uvcvideo: Failed to set UVC commit control : -110 (exp. 26). Apr 16 14:27:14 quadrio kernel: [16833.368392] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:19 quadrio kernel: [16838.368326] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:24 quadrio kernel: [16843.368272] uvcvideo: Failed to set UVC commit control : -110 (exp. 26). Does not start working even after an rmmod/modprobe of this module. Need a reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berend 3658 F pulseaudio /dev/snd/pcmC0D0c: berend 3658 F...m pulseaudio /dev/snd/pcmC0D0p: berend 3658 F...m pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 14:42:24 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-01 (15 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: LENOVO 2757CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=UUID=52ddc899-ca26-4fe9-b2ba-e7562258b42c ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZET71WW (1.54 ) dmi.board.name: 2757CTO 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:bvr7ZET71WW(1.54):bd11/27/2008:svnLENOVO:pn2757CTO:pvrThinkPadW700:rvnLENOVO:rn2757CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2757CTO dmi.product.version: ThinkPad W700 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309221] Re: transparent hugepages flaky on arm64
Being discussed on the kernel team mailing list: https://lists.ubuntu.com/archives/kernel-team/2014-April/041621.html ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309221 Title: transparent hugepages flaky on arm64 Status in “linux” package in Ubuntu: Triaged Bug description: linux 3.13.0-24.46 transparent hugepages, which are configured on by default in Ubuntu, are flaky on arm64. The most evident system is that go processes reliably hang or crash. This has been observed with both building juju-core with gccgo, and running the resulting juju binaries. The root cause of this is that get_user_pages_fast is not yet implemented on arm64 (and arm64). Patches are floating around, but haven't landed. http://comments.gmane.org/gmane.linux.ports.arm.kernel/299268 We've verified that either applying those patches, or disabling THP via sysfs, prevents the above issues. At minimum we should change the default boottime sysfs setting for THP to "never" until we can fix this feature properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1291470] Re: Touchpad recognized as generic mouse
Sorry, the Trusty kernel is based off the 3.13 kernel, so we would need to identify the commit in 3.14.1 and backport it to 3.13, unless the commit was cc'd for inclusion in all stable releases. Can you give the latest 3.13 upstream kernel a test, which can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.10-trusty/ ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1291470 Title: Touchpad recognized as generic mouse Status in “linux” package in Ubuntu: Triaged Bug description: Laptop Model: Gateway NE72203h Touchpad manufacturer: ALPS Ubuntu version: 14.04 In a terminal, the command "cat /proc/bus/input/devices" shows the following: I: Bus=0011 Vendor=0002 Product=0001 Version= N: Name="PS/2 Generic Mouse" P: Phys=isa0060/serio4/input0 S: Sysfs=/devices/platform/i8042/serio4/input/input16 U: Uniq= H: Handlers=mouse0 event10 B: PROP=0 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 According to the Ubuntu documentation, (https://wiki.ubuntu.com/DebuggingTouchpadDetection) this would be would be a problem with the kernel which doesn't recognize the touchpad properly. Thank you for your attention, PS: my apology if this bug report is sent to the wrong team, I'm fairly new to Linux in general and this is my first time filling a bug report. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Mar 12 11:45:27 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0782] InstallationDate: Installed on 2014-02-27 (12 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224) MachineType: Gateway NE722 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed root=UUID=84ff13bf-17df-4563-9902-2924bf6ce501 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Asset Tag dmi.board.name: EG70_KB dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd07/01/2013:svnGateway:pnNE722:pvrV1.04:rvnGateway:rnEG70_KB:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: NE722 dmi.product.version: V1.04 dmi.sys.vendor: Gateway version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Mar 11 17:53:29 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308311] Re: uvcvideo kernel module crash
Running with: Linux quadrio.nederware.nl 3.15.0-031500rc1-generic #201404131835 SMP Sun Apr 13 22:36:23 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux But didn't help. 1. I first upgraded to latest 14.04, then rebooted. No webcam found after reboot. 2. Then installed the new kernel, still no webcam found. 3. I then turned off the computer, waited a while, and turned it on. Skype recognised webcam for a few milliseconds, then video crashed. After the crash I rebooted, webcam not found. Turned it off, waited, and on again, wecbcam found. It seems that after a crash I need to physicall turn off the computer before lsusb sees the webcam. This is what it sees after I've turned off the computer: Bus 002 Device 004: ID 17ef:480c Lenovo Integrated Webcam That device simply is not found after the crash. Messages in /var/log/syslog when the webcam was found for a few millisecs: Apr 18 11:42:14 quadrio kernel: [ 285.124490] usb 2-4: USB disconnect, device number 4 Apr 18 11:42:14 quadrio kernel: [ 285.484046] usb 7-2: new full-speed USB device number 2 using uhci_hcd Apr 18 11:42:14 quadrio kernel: [ 285.604111] usb 7-2: device descriptor read/64, error -71 Apr 18 11:42:14 quadrio kernel: [ 285.828075] usb 7-2: device descriptor read/64, error -71 Apr 18 11:42:15 quadrio kernel: [ 286.248105] usb 7-2: new full-speed USB device number 3 using uhci_hcd Apr 18 11:42:15 quadrio kernel: [ 286.368126] usb 7-2: device descriptor read/64, error -71 Apr 18 11:42:15 quadrio kernel: [ 286.592101] usb 7-2: device descriptor read/64, error -71 Apr 18 11:42:15 quadrio kernel: [ 286.808135] usb 7-2: new full-speed USB device number 4 using uhci_hcd Apr 18 11:42:16 quadrio kernel: [ 287.224074] usb 7-2: device not accepting address 4, error -71 Apr 18 11:42:16 quadrio kernel: [ 287.336094] usb 7-2: new full-speed USB device number 5 using uhci_hcd Apr 18 11:42:16 quadrio kernel: [ 287.748043] usb 7-2: device not accepting address 5, error -71 Apr 18 11:42:16 quadrio kernel: [ 287.748083] hub 7-0:1.0: unable to enumerate USB device on port 2 ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308311 Title: uvcvideo kernel module crash Status in “linux” package in Ubuntu: Incomplete Bug description: Symptom: video works once, but crashes during use, or at second use. Happened on 32-bit precise too. /var/log/syslog startup messages: Apr 16 09:46:46 quadrio kernel: [6.181754] input: UVC Camera (17ef:480c) as /devices/pci:00/:00:1d.7/usb2/2-4/2-4:1.0/input/input16 Apr 16 09:46:46 quadrio kernel: [6.183111] usbcore: registered new interface driver uvcvideo When it crashes: Apr 16 14:26:39 quadrio kernel: [16798.368345] uvcvideo: Failed to query (SET_CUR) UVC control 3 on unit 1: -110 (exp. 1). Apr 16 14:26:44 quadrio kernel: [16803.368274] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:26:49 quadrio kernel: [16808.368322] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:26:54 quadrio kernel: [16813.368402] uvcvideo: Failed to set UVC commit control : -110 (exp. 26). Apr 16 14:26:59 quadrio kernel: [16818.368341] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:04 quadrio kernel: [16823.368421] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:09 quadrio kernel: [16828.368336] uvcvideo: Failed to set UVC commit control : -110 (exp. 26). Apr 16 14:27:14 quadrio kernel: [16833.368392] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:19 quadrio kernel: [16838.368326] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:24 quadrio kernel: [16843.368272] uvcvideo: Failed to set UVC commit control : -110 (exp. 26). Does not start working even after an rmmod/modprobe of this module. Need a reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berend 3658 F pulseaudio /dev/snd/pcmC0D0c: berend 3658 F...m pulseaudio /dev/snd/pcmC0D0p: berend 3658 F...m pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 14:42:24 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-01 (15 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: LENOVO 2757CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=UUID=52ddc899-ca26-4fe9-b2ba-e756
[Kernel-packages] [Bug 1307064] Re: Ubuntu 14.04 Beta cannot adjust brightness on Lenovo Ideapad Z570
This still exists in the upstream kernel. I testedlinux- image-3.15.0-031500rc1-generic_3.15.0-031500rc1.201404131835_amd64.deb ** Tags removed: amd64 apport-bug staging trusty ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307064 Title: Ubuntu 14.04 Beta cannot adjust brightness on Lenovo Ideapad Z570 Status in “linux” package in Ubuntu: Incomplete Bug description: Fresh install of 14.04 on my laptop cannot adjust brightness. When fn+up arrow or fn+down arrow are used, the indicator in the upper right hand corner as if the brightness should change, but it does not. Also, if one tries to use the slider in the power applet, the brightness does not change. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: will 2960 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 12 21:36:57 2014 HibernationDevice: RESUME=UUID=dfa51f33-0f34-4383-8194-93656983323d InstallationDate: Installed on 2014-04-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: LENOVO 10249RU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=7420c61f-1836-4a44-84dc-71573190ff4c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN38WW 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:bvr45CN38WW:bd10/21/2011:svnLENOVO:pn10249RU:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 10249RU dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307064/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309246] Re: Keyboard not recognized when typing encryption password
Can you give the latest 3.13 upstream kernel a test, which can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.10-trusty/ ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309246 Title: Keyboard not recognized when typing encryption password Status in “linux” package in Ubuntu: Confirmed Bug description: My keyboard is not recognized at the initial prompt to unencrypt my harddrive's full-disk encryption if I boot into kernel 3.13.0-24. If I instead boot kernel 3.13.0-23, my keyboard is recognized. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ian2424 F pulseaudio /dev/snd/controlC0: ian2424 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 17 18:00:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-22 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140221) MachineType: TOSHIBA Satellite L875D ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309246] Re: Keyboard not recognized when typing encryption password
** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309246 Title: Keyboard not recognized when typing encryption password Status in “linux” package in Ubuntu: Confirmed Bug description: My keyboard is not recognized at the initial prompt to unencrypt my harddrive's full-disk encryption if I boot into kernel 3.13.0-24. If I instead boot kernel 3.13.0-23, my keyboard is recognized. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ian2424 F pulseaudio /dev/snd/controlC0: ian2424 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 17 18:00:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-22 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140221) MachineType: TOSHIBA Satellite L875D ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1290517] Re: Asus R751L Notebook - Touchpad not recognized
Here's more information from my post regarding the same issue on StackExchange. Might be useful maybe: http://unix.stackexchange.com/questions/117940/touchpad-not-recognized- on-linux-asus-r751lb . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1290517 Title: Asus R751L Notebook - Touchpad not recognized Status in “linux” package in Ubuntu: Confirmed Bug description: I made a fresh install of ubuntu 13.10. After that dist upgraded. Mouse works if I attach an optical mouse. This works fine. My touchpad isn't recognized. Even I cannot see a tab for touchpad in settings. --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbc1639 F pulseaudio /dev/snd/controlC1: jbc1639 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=c218623a-1038-4589-8a9f-beb574a44cd6 InstallationDate: Installed on 2014-03-10 (2 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUSTeK COMPUTER INC. X750LB MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic.efi.signed root=UUID=b2acb217-20f6-4ec8-9346-6415483140fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 RelatedPackageVersions: linux-restricted-modules-3.11.0-18-generic N/A linux-backports-modules-3.11.0-18-generic N/A linux-firmware 1.116.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 205 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X750LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 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.:bvr205:bd10/01/2013:svnASUSTeKCOMPUTERINC.:pnX750LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750LB:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: X750LB 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/1290517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309246] 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/1309246 Title: Keyboard not recognized when typing encryption password Status in “linux” package in Ubuntu: Confirmed Bug description: My keyboard is not recognized at the initial prompt to unencrypt my harddrive's full-disk encryption if I boot into kernel 3.13.0-24. If I instead boot kernel 3.13.0-23, my keyboard is recognized. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ian2424 F pulseaudio /dev/snd/controlC0: ian2424 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 17 18:00:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-22 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140221) MachineType: TOSHIBA Satellite L875D ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309246] [NEW] Keyboard not recognized when typing encryption password
Public bug reported: My keyboard is not recognized at the initial prompt to unencrypt my harddrive's full-disk encryption if I boot into kernel 3.13.0-24. If I instead boot kernel 3.13.0-23, my keyboard is recognized. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ian2424 F pulseaudio /dev/snd/controlC0: ian2424 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 17 18:00:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-22 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140221) MachineType: TOSHIBA Satellite L875D ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Description changed: - My keyboard is not recognized at the initial prompt to unencrypt my HDD - if I boot into kernel 3.13.0-24. If I instead boot kernel 3.13.0-23, my - keyboard is recognized. + My keyboard is not recognized at the initial prompt to unencrypt my + harddrive's full-disk encryption if I boot into kernel 3.13.0-24. If I + instead boot kernel 3.13.0-23, my keyboard is recognized. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: ian2424 F pulseaudio - /dev/snd/controlC0: ian2424 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: ian2424 F pulseaudio + /dev/snd/controlC0: ian2424 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 17 18:00:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-22 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140221) MachineType: TOSHIBA Satellite L875D ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: - linux-restricted-modules-3.13.0-23-generic N/A - linux-backports-modules-3.13.0-23-generic N/A - linux-firmware 1.127 + linux-restricted-modules-3.13.0-23-generic N/A + linux-backports-modules-3.13.0-23-generic N/A + linux-firmware 1.127 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309246 Title: Keyboard not recognized when typing encryption password Status in “linux” package in Ubuntu: New Bug description: My keyboard is not recognized
[Kernel-packages] [Bug 1307752] Re: tahr crash running brasero blanking CD
** 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/1307752 Title: tahr crash running brasero blanking CD Status in “linux” package in Ubuntu: Incomplete Bug description: First time, with chromium browser up and using brasero to blank a CD, got a kernel panic. Complete stop to text screen wouldn't do a thing. Lots of stuff on the screen no way to copy it all short of a digital camera. Second time, no browser up, using brasero to blank a CD, tahr got an internal error. I selected to continue to report the error but tahr didn't complete the process. I tried selecting the crash report to process it, however tahr wouldn't do it. I just did an ubuntu-bug linux and will attach the crash report. BTW, the CD was blanked successfully. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jerry 1662 F pulseaudio /dev/snd/controlC0: jerry 1662 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 14 20:03:34 2014 HibernationDevice: RESUME=UUID=c7acd897-2499-4bc7-9ad5-f5020e56d7ac InstallationDate: Installed on 2014-04-12 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140412) MachineType: Acer Aspire 5253 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=93129fd9-f2e5-4cf5-b09f-288b1c8005ec ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.name: Aspire 5253 dmi.board.vendor: Acer dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrV1.05:bd01/06/2011:svnAcer:pnAspire5253:pvrV1.05:rvnAcer:rnAspire5253:rvrV1.05:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 5253 dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308460] Re: Wifi and wired connection don't work on linux 3.11.0-19
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc1-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308460 Title: Wifi and wired connection don't work on linux 3.11.0-19 Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, i update linux kernel to 3.11.0-19 and my wifi and wlan connection stop working at all. I try ifup -a it don't help. ifconfing show's me only Loopback. When i load my laptop with linux kernel version 3.11.0-18-wifi work's fine. 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) Subsystem: Acer Incorporated [ALI] Device [1025:0649] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0649] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 41c1 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: Acer Incorporated [ALI] Device [1025:0649] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us ExtTag- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <16us ClockPM- Surprise- LLActRep+ BwNot- LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #0, PowerLimit 10.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState+ RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range BC, TimeoutDis+ ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- ARIFwd- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDi
[Kernel-packages] [Bug 1291470] Re: Touchpad recognized as generic mouse
This will be fixed in Trusty when it gets the upstream 3.14.1 stable updates. ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1291470 Title: Touchpad recognized as generic mouse Status in “linux” package in Ubuntu: Triaged Bug description: Laptop Model: Gateway NE72203h Touchpad manufacturer: ALPS Ubuntu version: 14.04 In a terminal, the command "cat /proc/bus/input/devices" shows the following: I: Bus=0011 Vendor=0002 Product=0001 Version= N: Name="PS/2 Generic Mouse" P: Phys=isa0060/serio4/input0 S: Sysfs=/devices/platform/i8042/serio4/input/input16 U: Uniq= H: Handlers=mouse0 event10 B: PROP=0 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 According to the Ubuntu documentation, (https://wiki.ubuntu.com/DebuggingTouchpadDetection) this would be would be a problem with the kernel which doesn't recognize the touchpad properly. Thank you for your attention, PS: my apology if this bug report is sent to the wrong team, I'm fairly new to Linux in general and this is my first time filling a bug report. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Mar 12 11:45:27 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0782] InstallationDate: Installed on 2014-02-27 (12 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224) MachineType: Gateway NE722 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed root=UUID=84ff13bf-17df-4563-9902-2924bf6ce501 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Asset Tag dmi.board.name: EG70_KB dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd07/01/2013:svnGateway:pnNE722:pvrV1.04:rvnGateway:rnEG70_KB:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: NE722 dmi.product.version: V1.04 dmi.sys.vendor: Gateway version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Mar 11 17:53:29 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308311] Re: uvcvideo kernel module crash
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc1-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308311 Title: uvcvideo kernel module crash Status in “linux” package in Ubuntu: Incomplete Bug description: Symptom: video works once, but crashes during use, or at second use. Happened on 32-bit precise too. /var/log/syslog startup messages: Apr 16 09:46:46 quadrio kernel: [6.181754] input: UVC Camera (17ef:480c) as /devices/pci:00/:00:1d.7/usb2/2-4/2-4:1.0/input/input16 Apr 16 09:46:46 quadrio kernel: [6.183111] usbcore: registered new interface driver uvcvideo When it crashes: Apr 16 14:26:39 quadrio kernel: [16798.368345] uvcvideo: Failed to query (SET_CUR) UVC control 3 on unit 1: -110 (exp. 1). Apr 16 14:26:44 quadrio kernel: [16803.368274] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:26:49 quadrio kernel: [16808.368322] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:26:54 quadrio kernel: [16813.368402] uvcvideo: Failed to set UVC commit control : -110 (exp. 26). Apr 16 14:26:59 quadrio kernel: [16818.368341] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:04 quadrio kernel: [16823.368421] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:09 quadrio kernel: [16828.368336] uvcvideo: Failed to set UVC commit control : -110 (exp. 26). Apr 16 14:27:14 quadrio kernel: [16833.368392] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:19 quadrio kernel: [16838.368326] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). Apr 16 14:27:24 quadrio kernel: [16843.368272] uvcvideo: Failed to set UVC commit control : -110 (exp. 26). Does not start working even after an rmmod/modprobe of this module. Need a reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berend 3658 F pulseaudio /dev/snd/pcmC0D0c: berend 3658 F...m pulseaudio /dev/snd/pcmC0D0p: berend 3658 F...m pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 14:42:24 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-01 (15 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: LENOVO 2757CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=UUID=52ddc899-ca26-4fe9-b2ba-e7562258b42c ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZET71WW (1.54 ) dmi.board.name: 2757CTO 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:bvr7ZET71WW(1.54):bd11/27/2008:svnLENOVO:pn2757CTO:pvrThinkPadW700:rvnLENOVO:rn2757CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2757CTO dmi.product.version: ThinkPad W700 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308259] Re: ARM Cadence ethernet bloat in x86/_64 kernel.
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308259 Title: ARM Cadence ethernet bloat in x86/_64 kernel. Status in “linux” package in Ubuntu: Confirmed Bug description: /lib/modules/*/kernel/drivers/net/ethernet/cadence via- http://lkml.iu.edu/hypermail/linux/kernel/1404.1/03429.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308259/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308474] Re: CPU-intensive processes killed by OS
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Triaged Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kwor
[Kernel-packages] [Bug 1309070] Re: Possible Bug Translation in the clock menu.
This looks like a translations bug and not a kernel 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/1309070 Title: Possible Bug Translation in the clock menu. Status in “linux” package in Ubuntu: Incomplete Bug description: I just installed Ubuntu 14.04, and downloaded all the updates and then downloaded the packages in the following section translation for my language, so far so good without a single problem, but I noticed that the menu settings for the Date and Time were not aplicas translation . here is the link with pictures for better explanation of what happened. https://www.dropbox.com/sh/8w7jdxsui8f2joq/Rume3ILyAt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309112] Re: x120e does not resume from suspend
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc1-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309112 Title: x120e does not resume from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: fresh install of 14.04 on x120e. resume from suspend fails every time. I have to long-press the power button and then turning it back on doesn't post to BIOS. To recover, I have to pull the battery and power back on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: smoser 2106 F pulseaudio /dev/snd/controlC0: smoser 2106 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 17 12:52:00 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-17 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140415) MachineType: LENOVO 06112EU ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=ff435097-fd56-42de-b160-c1de1580a924 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8FET32WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 06112EU 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:bvr8FET32WW(1.16):bd11/03/2011:svnLENOVO:pn06112EU:pvrThinkPadX120e:rvnLENOVO:rn06112EU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 06112EU dmi.product.version: ThinkPad X120e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309221] Re: transparent hugepages flaky on arm64
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309221 Title: transparent hugepages flaky on arm64 Status in “linux” package in Ubuntu: Incomplete Bug description: linux 3.13.0-24.46 transparent hugepages, which are configured on by default in Ubuntu, are flaky on arm64. The most evident system is that go processes reliably hang or crash. This has been observed with both building juju-core with gccgo, and running the resulting juju binaries. The root cause of this is that get_user_pages_fast is not yet implemented on arm64 (and arm64). Patches are floating around, but haven't landed. http://comments.gmane.org/gmane.linux.ports.arm.kernel/299268 We've verified that either applying those patches, or disabling THP via sysfs, prevents the above issues. At minimum we should change the default boottime sysfs setting for THP to "never" until we can fix this feature properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1243904] Re: [LG P1-J273B] Internal keyboard doesn't work in 13.10
Thanks, Shengliang Song. could I do something to help? Jalgi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1243904 Title: [LG P1-J273B] Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Incomplete Bug description: My laptop is a lg p1 express dual. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309221] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1309221 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/1309221 Title: transparent hugepages flaky on arm64 Status in “linux” package in Ubuntu: Incomplete Bug description: linux 3.13.0-24.46 transparent hugepages, which are configured on by default in Ubuntu, are flaky on arm64. The most evident system is that go processes reliably hang or crash. This has been observed with both building juju-core with gccgo, and running the resulting juju binaries. The root cause of this is that get_user_pages_fast is not yet implemented on arm64 (and arm64). Patches are floating around, but haven't landed. http://comments.gmane.org/gmane.linux.ports.arm.kernel/299268 We've verified that either applying those patches, or disabling THP via sysfs, prevents the above issues. At minimum we should change the default boottime sysfs setting for THP to "never" until we can fix this feature properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1309221] [NEW] transparent hugepages flaky on arm64
Public bug reported: linux 3.13.0-24.46 transparent hugepages, which are configured on by default in Ubuntu, are flaky on arm64. The most evident system is that go processes reliably hang or crash. This has been observed with both building juju-core with gccgo, and running the resulting juju binaries. The root cause of this is that get_user_pages_fast is not yet implemented on arm64 (and arm64). Patches are floating around, but haven't landed. http://comments.gmane.org/gmane.linux.ports.arm.kernel/299268 We've verified that either applying those patches, or disabling THP via sysfs, prevents the above issues. At minimum we should change the default boottime sysfs setting for THP to "never" until we can fix this feature properly. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1309221 Title: transparent hugepages flaky on arm64 Status in “linux” package in Ubuntu: New Bug description: linux 3.13.0-24.46 transparent hugepages, which are configured on by default in Ubuntu, are flaky on arm64. The most evident system is that go processes reliably hang or crash. This has been observed with both building juju-core with gccgo, and running the resulting juju binaries. The root cause of this is that get_user_pages_fast is not yet implemented on arm64 (and arm64). Patches are floating around, but haven't landed. http://comments.gmane.org/gmane.linux.ports.arm.kernel/299268 We've verified that either applying those patches, or disabling THP via sysfs, prevents the above issues. At minimum we should change the default boottime sysfs setting for THP to "never" until we can fix this feature properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 706999] Re: CVE-2010-3448
revert ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Won't Fix => 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/706999 Title: CVE-2010-3448 Status in “linux” package in Ubuntu: Fix Released 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-linaro” package in Ubuntu: Won't Fix Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: New Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-qcm-msm” 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: Fix Released Status in “linux-linaro” source package in Lucid: Won't Fix Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Fix Released Status in “linux-qcm-msm” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux-linaro” source package in Oneiric: Won't Fix Status in “linux-qcm-msm” source package in Oneiric: Won't Fix 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-linaro” source package in Precise: New Status in “linux-lts-backport-maverick” source package in Precise: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-qcm-msm” source package in Precise: New 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: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-linaro” source package in Quantal: Won't Fix Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-qcm-msm” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid 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-linaro” source package in Raring: Won't Fix Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-qcm-msm” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Invalid Status in “linux-linaro” source package in Hardy: Won't Fix Status in “linux-qcm-msm” source package in Hardy: Invalid Bug description: drivers/platform/x86/thinkpad_acpi.c in the Linux kernel before 2.6.34 on ThinkPad devices, when the X.Org X server is used, does not properly restrict access to the video output control state, which allows local users to cause a denial of service (system h
[Kernel-packages] [Bug 706999] Re: CVE-2010-3448
revert ** Changed in: linux-lts-raring (Ubuntu) Status: Won't Fix => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/706999 Title: CVE-2010-3448 Status in “linux” package in Ubuntu: Fix Released 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-linaro” package in Ubuntu: Won't Fix Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: New Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-qcm-msm” 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: Fix Released Status in “linux-linaro” source package in Lucid: Won't Fix Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Fix Released Status in “linux-qcm-msm” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux-linaro” source package in Oneiric: Won't Fix Status in “linux-qcm-msm” source package in Oneiric: Won't Fix 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-linaro” source package in Precise: New Status in “linux-lts-backport-maverick” source package in Precise: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-qcm-msm” source package in Precise: New 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: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-linaro” source package in Quantal: Won't Fix Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-qcm-msm” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid 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-linaro” source package in Raring: Won't Fix Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-qcm-msm” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Invalid Status in “linux-linaro” source package in Hardy: Won't Fix Status in “linux-qcm-msm” source package in Hardy: Invalid Bug description: drivers/platform/x86/thinkpad_acpi.c in the Linux kernel before 2.6.34 on ThinkPad devices, when the X.Org X server is used, does not properly restrict access to the video output control state, which allows local users to cause a denial of service (system hang) via a
[Kernel-packages] [Bug 706999] Re: CVE-2010-3448
revert ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: Won't Fix => 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/706999 Title: CVE-2010-3448 Status in “linux” package in Ubuntu: Fix Released 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-linaro” package in Ubuntu: Won't Fix Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: New Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-qcm-msm” 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: Fix Released Status in “linux-linaro” source package in Lucid: Won't Fix Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Fix Released Status in “linux-qcm-msm” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux-linaro” source package in Oneiric: Won't Fix Status in “linux-qcm-msm” source package in Oneiric: Won't Fix 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-linaro” source package in Precise: New Status in “linux-lts-backport-maverick” source package in Precise: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-qcm-msm” source package in Precise: New 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: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-linaro” source package in Quantal: Won't Fix Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-qcm-msm” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid 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-linaro” source package in Raring: Won't Fix Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-qcm-msm” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Invalid Status in “linux-linaro” source package in Hardy: Won't Fix Status in “linux-qcm-msm” source package in Hardy: Invalid Bug description: drivers/platform/x86/thinkpad_acpi.c in the Linux kernel before 2.6.34 on ThinkPad devices, when the X.Org X server is used, does not properly restrict access to the video output control state, which allows local users to cause a denial of service (system han
[Kernel-packages] [Bug 706999] Re: CVE-2010-3448
revert ** Changed in: linux-lts-raring (Ubuntu Quantal) Status: Won't Fix => 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/706999 Title: CVE-2010-3448 Status in “linux” package in Ubuntu: Fix Released 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-linaro” package in Ubuntu: Won't Fix Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: New Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-qcm-msm” 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: Fix Released Status in “linux-linaro” source package in Lucid: Won't Fix Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Fix Released Status in “linux-qcm-msm” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux-linaro” source package in Oneiric: Won't Fix Status in “linux-qcm-msm” source package in Oneiric: Won't Fix 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-linaro” source package in Precise: New Status in “linux-lts-backport-maverick” source package in Precise: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-qcm-msm” source package in Precise: New 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: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-linaro” source package in Quantal: Won't Fix Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-qcm-msm” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid 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-linaro” source package in Raring: Won't Fix Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-qcm-msm” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Invalid Status in “linux-linaro” source package in Hardy: Won't Fix Status in “linux-qcm-msm” source package in Hardy: Invalid Bug description: drivers/platform/x86/thinkpad_acpi.c in the Linux kernel before 2.6.34 on ThinkPad devices, when the X.Org X server is used, does not properly restrict access to the video output control state, which allows local users to cause a denial of service (system h
[Kernel-packages] [Bug 706999] Re: CVE-2010-3448
revert ** Changed in: linux-lts-raring (Ubuntu Raring) Status: Won't Fix => 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/706999 Title: CVE-2010-3448 Status in “linux” package in Ubuntu: Fix Released 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-linaro” package in Ubuntu: Won't Fix Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: New Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-qcm-msm” 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: Fix Released Status in “linux-linaro” source package in Lucid: Won't Fix Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Fix Released Status in “linux-qcm-msm” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux-linaro” source package in Oneiric: Won't Fix Status in “linux-qcm-msm” source package in Oneiric: Won't Fix 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-linaro” source package in Precise: New Status in “linux-lts-backport-maverick” source package in Precise: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-qcm-msm” source package in Precise: New 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: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-linaro” source package in Quantal: Won't Fix Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-qcm-msm” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid 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-linaro” source package in Raring: Won't Fix Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-qcm-msm” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Invalid Status in “linux-linaro” source package in Hardy: Won't Fix Status in “linux-qcm-msm” source package in Hardy: Invalid Bug description: drivers/platform/x86/thinkpad_acpi.c in the Linux kernel before 2.6.34 on ThinkPad devices, when the X.Org X server is used, does not properly restrict access to the video output control state, which allows local users to cause a denial of service (system ha
Re: [Kernel-packages] [Bug 1176577] Re: [HP Compaq dc7700 Small Form Factor PC] mei unexpected reset in kernel 3.8
Then same on my old thick clients ;) AFAIK only fixable by blacklisting the "mei" and "mei_me" kernel modules. But that should be better than with a full text processing command, otherwise it gets nasty. Am 17.04.2014 22:41, schrieb Lonnie Lee Best: > Dang, I just downgraded by doing a fresh install of server 12.04.4 > (instead of server 14.04) (hoping this would go away). > > No luck! It constantly posts these same mei_me alerts to the terminal; > it makes it hard to even type commands; it constantly interrupts your > typing flow. > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1176577 Title: [HP Compaq dc7700 Small Form Factor PC] mei unexpected reset in kernel 3.8 Status in “linux” package in Ubuntu: Incomplete Status in “linux” package in Arch Linux: New Status in “linux” package in Fedora: Unknown Bug description: Right after upgrading kernel from 3.5 to 3.8 (Ubuntu 13.04), the syslog got flooded by a large number of such messages: (cut) May 5 15:33:15 compaq-aldo kernel: [ 205.064042] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:21 compaq-aldo kernel: [ 211.076029] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:27 compaq-aldo kernel: [ 217.088035] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:33 compaq-aldo kernel: [ 223.100039] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:39 compaq-aldo kernel: [ 229.112045] mei :00:03.0: unexpected reset: dev_state = RESETING (cut) This was associated by non reliable ethernet functionality, i.e. transfer of large files from my Ubuntu box to a local NAS connected via ethernet got hanging with no other apparent errors or diagnostics: nautilus copy just stopped transferring data, leaving the copy window there with the progress bar stopped. I tried to reboot, but this behaviour is perfectly reproducible. This is one of the first syslog lines got from that kernel: May 5 15:30:15 compaq-aldo kernel: [0.00] Linux version 3.8.0-19-generic (buildd@roseapple) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #30-Ubuntu SMP Wed May 1 16:36:13 UTC 2013 (Ubuntu 3.8.0-19.30-generic 3.8.8) I attach the whole syslog from boot of that kernel. On the same box, launching a previsous kernel (3.5) works flawlessly. For the time being, I removed 3.8 kernel from my box, now running 3.5. Kind regards Aldo --- ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ldx2074 F pulseaudio /dev/snd/controlC0: ldx2074 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=32cc5d6d-43c1-4e97-a8b7-10b71aac3e29 InstallationDate: Installed on 2013-01-04 (121 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=38ce1d51-c3cf-438d-b395-f7c4744e2e37 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic i686 UpgradeStatus: Upgraded to raring on 2013-04-26 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark dmi.bios.date: 04/13/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.10 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC7451V4Q dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.10:bd04/13/2007:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1176577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1303819] Re: Bluetooth menu's content disappeared after resume.
Hello Shih-Yuan, or anyone else affected, Accepted bluez into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/bluez/4.98-2ubuntu7.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: bluez (Ubuntu Precise) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1303819 Title: Bluetooth menu's content disappeared after resume. Status in “bluez” package in Ubuntu: Fix Released Status in “bluez” source package in Precise: Fix Committed Status in “bluez” source package in Trusty: Fix Released Bug description: [Impact] * It is very annoying to see Bluetooth menu's content disappeared after suspending and resuming when playing music through Bluetooth audio output. * The better user experience is still seeing Bluetooth menu's content. [Test Case] * Pairing Bluetooth audio device. * Playing music through Bluetooth audio output. * Suspending the system. * Resuming the system. [Regression Potential] * No obvious regression exists. [Other Info] * The patch is to reset default_adapter_id's value to -1, then it can send the signal 'DefaultAdapterChanged' next time when new default adapter is set. * Reproducing Steps 1. Playing music through Bluetooth audio ouput. 2. Suspending the system. 3. Resuming the system. 4. Check Bluethooth menu's content * Expected Result The Bluetooth menu's content is not affected. * Actual Result The Bluetooth menu's content disappeared. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: bluez 4.98-2ubuntu7.1 ProcVersionSignature: Ubuntu 3.5.0-48.72~precise1-generic 3.5.7.31 Uname: Linux 3.5.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon Apr 7 19:08:01 2014 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E6230 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-48-generic root=UUID=8da8a808-6d55-4e04-a813-3f1217ab4f35 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 098M9Y dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/19/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn098M9Y:rvrX03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6230 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 74:DE:2B:D4:BB:8E ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:6082 acl:32 sco:0 events:625 errors:0 TX bytes:949448 acl:1140 sco:0 commands:45 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1303819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1176577] Re: [HP Compaq dc7700 Small Form Factor PC] mei unexpected reset in kernel 3.8
Dang, I just downgraded by doing a fresh install of server 12.04.4 (instead of server 14.04) (hoping this would go away). No luck! It constantly posts these same mei_me alerts to the terminal; it makes it hard to even type commands; it constantly interrupts your typing flow. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1176577 Title: [HP Compaq dc7700 Small Form Factor PC] mei unexpected reset in kernel 3.8 Status in “linux” package in Ubuntu: Incomplete Status in “linux” package in Arch Linux: New Status in “linux” package in Fedora: Unknown Bug description: Right after upgrading kernel from 3.5 to 3.8 (Ubuntu 13.04), the syslog got flooded by a large number of such messages: (cut) May 5 15:33:15 compaq-aldo kernel: [ 205.064042] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:21 compaq-aldo kernel: [ 211.076029] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:27 compaq-aldo kernel: [ 217.088035] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:33 compaq-aldo kernel: [ 223.100039] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:39 compaq-aldo kernel: [ 229.112045] mei :00:03.0: unexpected reset: dev_state = RESETING (cut) This was associated by non reliable ethernet functionality, i.e. transfer of large files from my Ubuntu box to a local NAS connected via ethernet got hanging with no other apparent errors or diagnostics: nautilus copy just stopped transferring data, leaving the copy window there with the progress bar stopped. I tried to reboot, but this behaviour is perfectly reproducible. This is one of the first syslog lines got from that kernel: May 5 15:30:15 compaq-aldo kernel: [0.00] Linux version 3.8.0-19-generic (buildd@roseapple) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #30-Ubuntu SMP Wed May 1 16:36:13 UTC 2013 (Ubuntu 3.8.0-19.30-generic 3.8.8) I attach the whole syslog from boot of that kernel. On the same box, launching a previsous kernel (3.5) works flawlessly. For the time being, I removed 3.8 kernel from my box, now running 3.5. Kind regards Aldo --- ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ldx2074 F pulseaudio /dev/snd/controlC0: ldx2074 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=32cc5d6d-43c1-4e97-a8b7-10b71aac3e29 InstallationDate: Installed on 2013-01-04 (121 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=38ce1d51-c3cf-438d-b395-f7c4744e2e37 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic i686 UpgradeStatus: Upgraded to raring on 2013-04-26 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark dmi.bios.date: 04/13/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.10 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC7451V4Q dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.10:bd04/13/2007:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1176577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308796] Re: Bad page map in openjdk-7
Apport does not seem to want to collect another report -- I chose to "send report" but nothing is appearing in this bug :( If you would like additional files let me know and I can collect them by hand. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308796 Title: Bad page map in openjdk-7 Status in “linux” package in Ubuntu: Confirmed Bug description: [ 2808.161850] BUG: Bad page map in process java pte:0320 pmd:e8048067 [ 2808.161860] addr:7f968a63a000 vm_flags:0870 anon_vma: (null) mapping: (null) index:7f968a63a [ 2808.161866] CPU: 0 PID: 18543 Comm: java Tainted: GB 3.13.0-24-generic #46-Ubuntu [ 2808.161868] 8800e7f623c0 8800e8277a98 81715a64 7f968a63a000 [ 2808.161871] 8800e8277ae0 81174183 0320 0007f968a63a [ 2808.161872] 8800e80481d0 0320 7f968a63a000 7f968a63b000 [ 2808.161874] Call Trace: [ 2808.161881] [] dump_stack+0x45/0x56 [ 2808.161884] [] print_bad_pte+0x1a3/0x250 [ 2808.161886] [] vm_normal_page+0x69/0x80 [ 2808.161888] [] unmap_page_range+0x3bb/0x7f0 [ 2808.161890] [] unmap_single_vma+0x81/0xf0 [ 2808.161892] [] unmap_vmas+0x49/0x90 [ 2808.161894] [] exit_mmap+0x9c/0x170 [ 2808.161898] [] ? __delayacct_add_tsk+0x153/0x170 [ 2808.161901] [] mmput+0x5c/0x120 [ 2808.161903] [] do_exit+0x26c/0xa50 [ 2808.161906] [] ? __unqueue_futex+0x31/0x60 [ 2808.161907] [] ? futex_wait+0x126/0x290 [ 2808.161909] [] do_group_exit+0x3f/0xa0 [ 2808.161912] [] get_signal_to_deliver+0x1d0/0x6f0 [ 2808.161916] [] do_signal+0x48/0x960 [ 2808.161919] [] ? sched_clock+0x9/0x10 [ 2808.161921] [] ? sched_clock_local+0x1d/0x80 [ 2808.161924] [] ? acct_account_cputime+0x1c/0x20 [ 2808.161925] [] ? account_user_time+0x8b/0xa0 [ 2808.161927] [] ? vtime_account_user+0x54/0x60 [ 2808.161929] [] do_notify_resume+0x69/0xb0 [ 2808.161932] [] int_signal+0x12/0x17 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 16 22:18 seq crw-rw 1 root audio 116, 33 Apr 16 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Apr 17 00:06:35 2014 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 17 17:56 seq crw-rw 1 root audio 116, 33 Apr 17 17:56 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.04 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro ProcVersionSignature: U
[Kernel-packages] [Bug 1308796] Re: Bad page map in openjdk-7
Sorry, the above were accidentally collected as duplicates. I am now running Linux ip-10-70-6-145 3.15.0-031500rc1-generic #201404131835 SMP Sun Apr 13 22:36:23 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux as requested. I can still trigger this, easiest way to reproduce is just running 'jps': [ 503.124559] BUG: Bad page map in process jps pte:0320 pmd:e77af067 [ 503.124571] addr:7fa42ebc1000 vm_flags:0870 anon_vma: (null) mapping: (null) index:7fa42ebc1 [ 503.124577] CPU: 0 PID: 4240 Comm: jps Not tainted 3.15.0-031500rc1-generic #201404131835 [ 503.124579] 7fa42ebc1000 8800e77fd9c8 8175ba7d 0007 [ 503.124581] 880004cfa8a0 8800e77fda18 8118311f 810056e1 [ 503.124583] dead00100100 ea00039dfc80 7fa42ebc1000 [ 503.124584] Call Trace: [ 503.124592] [] dump_stack+0x46/0x58 [ 503.124596] [] print_bad_pte+0x1bf/0x290 [ 503.124600] [] ? __raw_callee_save_xen_pte_val+0x11/0x1e [ 503.124602] [] vm_normal_page+0x6e/0x80 [ 503.124604] [] zap_pte_range+0x13f/0x450 [ 503.124606] [] unmap_page_range+0x1d4/0x310 [ 503.124608] [] ? xen_unpin_page+0x27/0x30 [ 503.124610] [] unmap_single_vma+0x87/0x100 [ 503.124612] [] unmap_vmas+0x54/0xa0 [ 503.124614] [] exit_mmap+0x9c/0x170 [ 503.124617] [] mmput.part.25+0x4a/0x120 [ 503.124619] [] mmput+0x30/0x40 [ 503.124621] [] exit_mm+0x13a/0x190 [ 503.124623] [] ? taskstats_exit+0x1cb/0x270 [ 503.124625] [] do_exit+0x14b/0x470 [ 503.124627] [] ? __dequeue_signal+0x6b/0xb0 [ 503.124629] [] do_group_exit+0x44/0xa0 [ 503.124631] [] get_signal_to_deliver+0x230/0x580 [ 503.124634] [] do_signal+0x47/0x140 [ 503.124637] [] ? account_user_time+0x99/0xb0 [ 503.124639] [] ? vtime_account_user+0x5d/0x70 [ 503.124642] [] ? context_tracking_user_exit+0x6f/0xf0 [ 503.124644] [] do_notify_resume+0xa2/0xd0 [ 503.124647] [] int_signal+0x12/0x17 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream ** Description changed: [ 2808.161850] BUG: Bad page map in process java pte:0320 pmd:e8048067 [ 2808.161860] addr:7f968a63a000 vm_flags:0870 anon_vma: (null) mapping: (null) index:7f968a63a [ 2808.161866] CPU: 0 PID: 18543 Comm: java Tainted: GB 3.13.0-24-generic #46-Ubuntu [ 2808.161868] 8800e7f623c0 8800e8277a98 81715a64 7f968a63a000 [ 2808.161871] 8800e8277ae0 81174183 0320 0007f968a63a [ 2808.161872] 8800e80481d0 0320 7f968a63a000 7f968a63b000 [ 2808.161874] Call Trace: [ 2808.161881] [] dump_stack+0x45/0x56 [ 2808.161884] [] print_bad_pte+0x1a3/0x250 [ 2808.161886] [] vm_normal_page+0x69/0x80 [ 2808.161888] [] unmap_page_range+0x3bb/0x7f0 [ 2808.161890] [] unmap_single_vma+0x81/0xf0 [ 2808.161892] [] unmap_vmas+0x49/0x90 [ 2808.161894] [] exit_mmap+0x9c/0x170 [ 2808.161898] [] ? __delayacct_add_tsk+0x153/0x170 [ 2808.161901] [] mmput+0x5c/0x120 [ 2808.161903] [] do_exit+0x26c/0xa50 [ 2808.161906] [] ? __unqueue_futex+0x31/0x60 [ 2808.161907] [] ? futex_wait+0x126/0x290 [ 2808.161909] [] do_group_exit+0x3f/0xa0 [ 2808.161912] [] get_signal_to_deliver+0x1d0/0x6f0 [ 2808.161916] [] do_signal+0x48/0x960 [ 2808.161919] [] ? sched_clock+0x9/0x10 [ 2808.161921] [] ? sched_clock_local+0x1d/0x80 [ 2808.161924] [] ? acct_account_cputime+0x1c/0x20 [ 2808.161925] [] ? account_user_time+0x8b/0xa0 [ 2808.161927] [] ? vtime_account_user+0x54/0x60 [ 2808.161929] [] do_notify_resume+0x69/0xb0 [ 2808.161932] [] int_signal+0x12/0x17 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 16 22:18 seq crw-rw 1 root audio 116, 33 Apr 16 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Apr 17 00:06:35 2014 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9e
[Kernel-packages] [Bug 1308796] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1308796/+attachment/4086539/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308796 Title: Bad page map in openjdk-7 Status in “linux” package in Ubuntu: Incomplete Bug description: [ 2808.161850] BUG: Bad page map in process java pte:0320 pmd:e8048067 [ 2808.161860] addr:7f968a63a000 vm_flags:0870 anon_vma: (null) mapping: (null) index:7f968a63a [ 2808.161866] CPU: 0 PID: 18543 Comm: java Tainted: GB 3.13.0-24-generic #46-Ubuntu [ 2808.161868] 8800e7f623c0 8800e8277a98 81715a64 7f968a63a000 [ 2808.161871] 8800e8277ae0 81174183 0320 0007f968a63a [ 2808.161872] 8800e80481d0 0320 7f968a63a000 7f968a63b000 [ 2808.161874] Call Trace: [ 2808.161881] [] dump_stack+0x45/0x56 [ 2808.161884] [] print_bad_pte+0x1a3/0x250 [ 2808.161886] [] vm_normal_page+0x69/0x80 [ 2808.161888] [] unmap_page_range+0x3bb/0x7f0 [ 2808.161890] [] unmap_single_vma+0x81/0xf0 [ 2808.161892] [] unmap_vmas+0x49/0x90 [ 2808.161894] [] exit_mmap+0x9c/0x170 [ 2808.161898] [] ? __delayacct_add_tsk+0x153/0x170 [ 2808.161901] [] mmput+0x5c/0x120 [ 2808.161903] [] do_exit+0x26c/0xa50 [ 2808.161906] [] ? __unqueue_futex+0x31/0x60 [ 2808.161907] [] ? futex_wait+0x126/0x290 [ 2808.161909] [] do_group_exit+0x3f/0xa0 [ 2808.161912] [] get_signal_to_deliver+0x1d0/0x6f0 [ 2808.161916] [] do_signal+0x48/0x960 [ 2808.161919] [] ? sched_clock+0x9/0x10 [ 2808.161921] [] ? sched_clock_local+0x1d/0x80 [ 2808.161924] [] ? acct_account_cputime+0x1c/0x20 [ 2808.161925] [] ? account_user_time+0x8b/0xa0 [ 2808.161927] [] ? vtime_account_user+0x54/0x60 [ 2808.161929] [] do_notify_resume+0x69/0xb0 [ 2808.161932] [] int_signal+0x12/0x17 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 16 22:18 seq crw-rw 1 root audio 116, 33 Apr 16 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Apr 17 00:06:35 2014 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 17 17:56 seq crw-rw 1 root audio 116, 33 Apr 17 17:56 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.04 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RfKill: Error:
[Kernel-packages] [Bug 1308796] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1308796/+attachment/4086542/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308796 Title: Bad page map in openjdk-7 Status in “linux” package in Ubuntu: Incomplete Bug description: [ 2808.161850] BUG: Bad page map in process java pte:0320 pmd:e8048067 [ 2808.161860] addr:7f968a63a000 vm_flags:0870 anon_vma: (null) mapping: (null) index:7f968a63a [ 2808.161866] CPU: 0 PID: 18543 Comm: java Tainted: GB 3.13.0-24-generic #46-Ubuntu [ 2808.161868] 8800e7f623c0 8800e8277a98 81715a64 7f968a63a000 [ 2808.161871] 8800e8277ae0 81174183 0320 0007f968a63a [ 2808.161872] 8800e80481d0 0320 7f968a63a000 7f968a63b000 [ 2808.161874] Call Trace: [ 2808.161881] [] dump_stack+0x45/0x56 [ 2808.161884] [] print_bad_pte+0x1a3/0x250 [ 2808.161886] [] vm_normal_page+0x69/0x80 [ 2808.161888] [] unmap_page_range+0x3bb/0x7f0 [ 2808.161890] [] unmap_single_vma+0x81/0xf0 [ 2808.161892] [] unmap_vmas+0x49/0x90 [ 2808.161894] [] exit_mmap+0x9c/0x170 [ 2808.161898] [] ? __delayacct_add_tsk+0x153/0x170 [ 2808.161901] [] mmput+0x5c/0x120 [ 2808.161903] [] do_exit+0x26c/0xa50 [ 2808.161906] [] ? __unqueue_futex+0x31/0x60 [ 2808.161907] [] ? futex_wait+0x126/0x290 [ 2808.161909] [] do_group_exit+0x3f/0xa0 [ 2808.161912] [] get_signal_to_deliver+0x1d0/0x6f0 [ 2808.161916] [] do_signal+0x48/0x960 [ 2808.161919] [] ? sched_clock+0x9/0x10 [ 2808.161921] [] ? sched_clock_local+0x1d/0x80 [ 2808.161924] [] ? acct_account_cputime+0x1c/0x20 [ 2808.161925] [] ? account_user_time+0x8b/0xa0 [ 2808.161927] [] ? vtime_account_user+0x54/0x60 [ 2808.161929] [] do_notify_resume+0x69/0xb0 [ 2808.161932] [] int_signal+0x12/0x17 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 16 22:18 seq crw-rw 1 root audio 116, 33 Apr 16 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Apr 17 00:06:35 2014 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 17 17:56 seq crw-rw 1 root audio 116, 33 Apr 17 17:56 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.04 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RfKill: Error: [Errno 2] No
[Kernel-packages] [Bug 1308796] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1308796/+attachment/4086540/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308796 Title: Bad page map in openjdk-7 Status in “linux” package in Ubuntu: Incomplete Bug description: [ 2808.161850] BUG: Bad page map in process java pte:0320 pmd:e8048067 [ 2808.161860] addr:7f968a63a000 vm_flags:0870 anon_vma: (null) mapping: (null) index:7f968a63a [ 2808.161866] CPU: 0 PID: 18543 Comm: java Tainted: GB 3.13.0-24-generic #46-Ubuntu [ 2808.161868] 8800e7f623c0 8800e8277a98 81715a64 7f968a63a000 [ 2808.161871] 8800e8277ae0 81174183 0320 0007f968a63a [ 2808.161872] 8800e80481d0 0320 7f968a63a000 7f968a63b000 [ 2808.161874] Call Trace: [ 2808.161881] [] dump_stack+0x45/0x56 [ 2808.161884] [] print_bad_pte+0x1a3/0x250 [ 2808.161886] [] vm_normal_page+0x69/0x80 [ 2808.161888] [] unmap_page_range+0x3bb/0x7f0 [ 2808.161890] [] unmap_single_vma+0x81/0xf0 [ 2808.161892] [] unmap_vmas+0x49/0x90 [ 2808.161894] [] exit_mmap+0x9c/0x170 [ 2808.161898] [] ? __delayacct_add_tsk+0x153/0x170 [ 2808.161901] [] mmput+0x5c/0x120 [ 2808.161903] [] do_exit+0x26c/0xa50 [ 2808.161906] [] ? __unqueue_futex+0x31/0x60 [ 2808.161907] [] ? futex_wait+0x126/0x290 [ 2808.161909] [] do_group_exit+0x3f/0xa0 [ 2808.161912] [] get_signal_to_deliver+0x1d0/0x6f0 [ 2808.161916] [] do_signal+0x48/0x960 [ 2808.161919] [] ? sched_clock+0x9/0x10 [ 2808.161921] [] ? sched_clock_local+0x1d/0x80 [ 2808.161924] [] ? acct_account_cputime+0x1c/0x20 [ 2808.161925] [] ? account_user_time+0x8b/0xa0 [ 2808.161927] [] ? vtime_account_user+0x54/0x60 [ 2808.161929] [] do_notify_resume+0x69/0xb0 [ 2808.161932] [] int_signal+0x12/0x17 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 16 22:18 seq crw-rw 1 root audio 116, 33 Apr 16 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Apr 17 00:06:35 2014 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 17 17:56 seq crw-rw 1 root audio 116, 33 Apr 17 17:56 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.04 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RfKill: Error: [Errn
[Kernel-packages] [Bug 1308796] Re: Bad page map in openjdk-7
apport information ** Tags added: apport-collected ** Description changed: [ 2808.161850] BUG: Bad page map in process java pte:0320 pmd:e8048067 [ 2808.161860] addr:7f968a63a000 vm_flags:0870 anon_vma: (null) mapping: (null) index:7f968a63a [ 2808.161866] CPU: 0 PID: 18543 Comm: java Tainted: GB 3.13.0-24-generic #46-Ubuntu [ 2808.161868] 8800e7f623c0 8800e8277a98 81715a64 7f968a63a000 [ 2808.161871] 8800e8277ae0 81174183 0320 0007f968a63a [ 2808.161872] 8800e80481d0 0320 7f968a63a000 7f968a63b000 [ 2808.161874] Call Trace: [ 2808.161881] [] dump_stack+0x45/0x56 [ 2808.161884] [] print_bad_pte+0x1a3/0x250 [ 2808.161886] [] vm_normal_page+0x69/0x80 [ 2808.161888] [] unmap_page_range+0x3bb/0x7f0 [ 2808.161890] [] unmap_single_vma+0x81/0xf0 [ 2808.161892] [] unmap_vmas+0x49/0x90 [ 2808.161894] [] exit_mmap+0x9c/0x170 [ 2808.161898] [] ? __delayacct_add_tsk+0x153/0x170 [ 2808.161901] [] mmput+0x5c/0x120 [ 2808.161903] [] do_exit+0x26c/0xa50 [ 2808.161906] [] ? __unqueue_futex+0x31/0x60 [ 2808.161907] [] ? futex_wait+0x126/0x290 [ 2808.161909] [] do_group_exit+0x3f/0xa0 [ 2808.161912] [] get_signal_to_deliver+0x1d0/0x6f0 [ 2808.161916] [] do_signal+0x48/0x960 [ 2808.161919] [] ? sched_clock+0x9/0x10 [ 2808.161921] [] ? sched_clock_local+0x1d/0x80 [ 2808.161924] [] ? acct_account_cputime+0x1c/0x20 [ 2808.161925] [] ? account_user_time+0x8b/0xa0 [ 2808.161927] [] ? vtime_account_user+0x54/0x60 [ 2808.161929] [] do_notify_resume+0x69/0xb0 [ 2808.161932] [] int_signal+0x12/0x17 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 16 22:18 seq crw-rw 1 root audio 116, 33 Apr 16 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Apr 17 00:06:35 2014 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Apr 17 17:56 seq + crw-rw 1 root audio 116, 33 Apr 17 17:56 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied + DistroRelease: Ubuntu 14.04 + Ec2AMI: ami-2ef19b1e + Ec2AMIManifest: (unknown) + Ec2AvailabilityZone: us-west-2a + Ec2InstanceType: m3.medium + Ec2Kernel: aki-fc8f11cc + Ec2Ramdisk: unavailable + IwConfig: Error: [Errno 2] No such file or directory + Lspci: Error: [Errno 2] No such file or directory + Lsusb: Error: [Errno 2] No such file or directory + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/zsh + ProcFB: + + ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro + ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty ec2-images + Uname: Linux 3.13.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + WifiSyslog: + + _MarkForUpload: True ** Attachment added: "HookError_source_linux.txt" https://bugs.launchpad.net/bugs/1308796/+attachment/4086537
[Kernel-packages] [Bug 1308796] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1308796/+attachment/4086541/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308796 Title: Bad page map in openjdk-7 Status in “linux” package in Ubuntu: Incomplete Bug description: [ 2808.161850] BUG: Bad page map in process java pte:0320 pmd:e8048067 [ 2808.161860] addr:7f968a63a000 vm_flags:0870 anon_vma: (null) mapping: (null) index:7f968a63a [ 2808.161866] CPU: 0 PID: 18543 Comm: java Tainted: GB 3.13.0-24-generic #46-Ubuntu [ 2808.161868] 8800e7f623c0 8800e8277a98 81715a64 7f968a63a000 [ 2808.161871] 8800e8277ae0 81174183 0320 0007f968a63a [ 2808.161872] 8800e80481d0 0320 7f968a63a000 7f968a63b000 [ 2808.161874] Call Trace: [ 2808.161881] [] dump_stack+0x45/0x56 [ 2808.161884] [] print_bad_pte+0x1a3/0x250 [ 2808.161886] [] vm_normal_page+0x69/0x80 [ 2808.161888] [] unmap_page_range+0x3bb/0x7f0 [ 2808.161890] [] unmap_single_vma+0x81/0xf0 [ 2808.161892] [] unmap_vmas+0x49/0x90 [ 2808.161894] [] exit_mmap+0x9c/0x170 [ 2808.161898] [] ? __delayacct_add_tsk+0x153/0x170 [ 2808.161901] [] mmput+0x5c/0x120 [ 2808.161903] [] do_exit+0x26c/0xa50 [ 2808.161906] [] ? __unqueue_futex+0x31/0x60 [ 2808.161907] [] ? futex_wait+0x126/0x290 [ 2808.161909] [] do_group_exit+0x3f/0xa0 [ 2808.161912] [] get_signal_to_deliver+0x1d0/0x6f0 [ 2808.161916] [] do_signal+0x48/0x960 [ 2808.161919] [] ? sched_clock+0x9/0x10 [ 2808.161921] [] ? sched_clock_local+0x1d/0x80 [ 2808.161924] [] ? acct_account_cputime+0x1c/0x20 [ 2808.161925] [] ? account_user_time+0x8b/0xa0 [ 2808.161927] [] ? vtime_account_user+0x54/0x60 [ 2808.161929] [] do_notify_resume+0x69/0xb0 [ 2808.161932] [] int_signal+0x12/0x17 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 16 22:18 seq crw-rw 1 root audio 116, 33 Apr 16 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Apr 17 00:06:35 2014 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 17 17:56 seq crw-rw 1 root audio 116, 33 Apr 17 17:56 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.04 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RfKill: Error: [Errno 2] No suc
[Kernel-packages] [Bug 1308796] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1308796/+attachment/4086538/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308796 Title: Bad page map in openjdk-7 Status in “linux” package in Ubuntu: Incomplete Bug description: [ 2808.161850] BUG: Bad page map in process java pte:0320 pmd:e8048067 [ 2808.161860] addr:7f968a63a000 vm_flags:0870 anon_vma: (null) mapping: (null) index:7f968a63a [ 2808.161866] CPU: 0 PID: 18543 Comm: java Tainted: GB 3.13.0-24-generic #46-Ubuntu [ 2808.161868] 8800e7f623c0 8800e8277a98 81715a64 7f968a63a000 [ 2808.161871] 8800e8277ae0 81174183 0320 0007f968a63a [ 2808.161872] 8800e80481d0 0320 7f968a63a000 7f968a63b000 [ 2808.161874] Call Trace: [ 2808.161881] [] dump_stack+0x45/0x56 [ 2808.161884] [] print_bad_pte+0x1a3/0x250 [ 2808.161886] [] vm_normal_page+0x69/0x80 [ 2808.161888] [] unmap_page_range+0x3bb/0x7f0 [ 2808.161890] [] unmap_single_vma+0x81/0xf0 [ 2808.161892] [] unmap_vmas+0x49/0x90 [ 2808.161894] [] exit_mmap+0x9c/0x170 [ 2808.161898] [] ? __delayacct_add_tsk+0x153/0x170 [ 2808.161901] [] mmput+0x5c/0x120 [ 2808.161903] [] do_exit+0x26c/0xa50 [ 2808.161906] [] ? __unqueue_futex+0x31/0x60 [ 2808.161907] [] ? futex_wait+0x126/0x290 [ 2808.161909] [] do_group_exit+0x3f/0xa0 [ 2808.161912] [] get_signal_to_deliver+0x1d0/0x6f0 [ 2808.161916] [] do_signal+0x48/0x960 [ 2808.161919] [] ? sched_clock+0x9/0x10 [ 2808.161921] [] ? sched_clock_local+0x1d/0x80 [ 2808.161924] [] ? acct_account_cputime+0x1c/0x20 [ 2808.161925] [] ? account_user_time+0x8b/0xa0 [ 2808.161927] [] ? vtime_account_user+0x54/0x60 [ 2808.161929] [] do_notify_resume+0x69/0xb0 [ 2808.161932] [] int_signal+0x12/0x17 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 16 22:18 seq crw-rw 1 root audio 116, 33 Apr 16 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Apr 17 00:06:35 2014 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 17 17:56 seq crw-rw 1 root audio 116, 33 Apr 17 17:56 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.04 Ec2AMI: ami-2ef19b1e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m3.medium Ec2Kernel: aki-fc8f11cc Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: ProcKernelCmdLine: root=UUID=ecdfe459-e35e-4416-a9c1-9ee71f9f93e7 ro ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RfKill: Error: [Errn
[Kernel-packages] [Bug 813935] Re: CVE-2011-1083
** Changed in: linux-armadaxp (Ubuntu Raring) Status: New => Won't Fix -- 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/813935 Title: CVE-2011-1083 Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: New 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Fix Released 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: New Status in “linux-fsl-imx51” source package in Lucid: Fix Released Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Fix Released Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Oneiric: Fix Released Status in “linux-armadaxp” source package in Oneiric: Invalid Status in “linux-ec2” source package in Oneiric: Invalid Status in “linux-fsl-imx51” source package in Oneiric: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: Invalid Status in “linux-lts-quantal” source package in Oneiric: Invalid Status in “linux-mvl-dove” source package in Oneiric: Invalid Status in “linux-ti-omap4” source package in Oneiric: Fix Released Status in “linux” source package in Precise: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: New 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: 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: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” 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: Won't Fix 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: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” 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 Hardy: Won't Fix Status in “linux-armadaxp” source package in Hardy: Invalid Status in “linux-ec2” source package in Hardy: Invalid Status in “linux-fsl-imx51” source package in Hardy: Invalid Status in “linux-lts-backport-maverick” source package in Hardy: Invalid Status in “linux-lts-backport-natty” source package in Hardy: Invalid Status in “linux-lts-backport-oneiric” source package in Hardy: Invalid Status in “linux-lts-quantal” source package in Hardy: Invalid Status in “linux-mvl-dove” source package in Hardy: Invalid Status in “linux-ti-omap4” source package in Hardy: Invalid Bug description: The epoll implementation in the Linux kernel 2.6.37.2 and earlier does not properly traverse a tree of epoll file d
[Kernel-packages] [Bug 706999] Re: CVE-2010-3448
** Changed in: linux-lts-raring (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: Invalid => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Invalid => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Quantal) Status: Invalid => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Raring) Status: Invalid => Won't Fix -- 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/706999 Title: CVE-2010-3448 Status in “linux” package in Ubuntu: Fix Released 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-linaro” package in Ubuntu: Won't Fix Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Won't Fix Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-qcm-msm” 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: Fix Released Status in “linux-linaro” source package in Lucid: Won't Fix Status in “linux-lts-backport-maverick” source package in Lucid: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Won't Fix Status in “linux-mvl-dove” source package in Lucid: Fix Released Status in “linux-qcm-msm” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux-linaro” source package in Oneiric: Won't Fix Status in “linux-qcm-msm” source package in Oneiric: Won't Fix 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-linaro” source package in Precise: New Status in “linux-lts-backport-maverick” source package in Precise: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Won't Fix Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-qcm-msm” source package in Precise: New 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: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-linaro” source package in Quantal: Won't Fix Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Won't Fix Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-qcm-msm” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid 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-linaro” source package in Raring: Won't Fix Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Won't Fix Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-qcm-msm” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Invalid Status in “linux-linaro” source package in Hardy: Won't Fix Status in
[Kernel-packages] [Bug 912227] Re: CVE-2011-4915
** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix -- 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/912227 Title: CVE-2011-4915 Status in “linux” package in Ubuntu: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: Won't Fix 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: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid 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-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New Status in “linux” source package in Trusty: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Invalid Status in “linux-lts-backport-natty” source package in Trusty: Invalid Status in “linux-lts-backport-oneiric” source package in Trusty: Invalid Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty:
[Kernel-packages] [Bug 912231] Re: CVE-2011-4917
** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix -- 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/912231 Title: CVE-2011-4917 Status in “linux” package in Ubuntu: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: Won't Fix 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: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid 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-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New Status in “linux” source package in Trusty: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Invalid Status in “linux-lts-backport-natty” source package in Trusty: Invalid Status in “linux-lts-backport-oneiric” source package in Trusty: Invalid Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty:
[Kernel-packages] [Bug 912230] Re: CVE-2011-4916
** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix -- 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/912230 Title: CVE-2011-4916 Status in “linux” package in Ubuntu: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: Won't Fix 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: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid 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-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New Status in “linux” source package in Trusty: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Invalid Status in “linux-lts-backport-natty” source package in Trusty: Invalid Status in “linux-lts-backport-oneiric” source package in Trusty: Invalid Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty:
[Kernel-packages] [Bug 927885] Re: CVE-2011-2393
** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix -- 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/927885 Title: CVE-2011-2393 Status in “linux” package in Ubuntu: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: 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-backport-oneiric” 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: Won't Fix 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: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid 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-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New Status in “linux” source package in Trusty: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Invalid Status in “linux-lts-backport-natty” source package in Trusty: Invalid Status in “linux-lts-backport-oneiric” source package in Trusty: Invalid Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trust
[Kernel-packages] [Bug 952828] Re: CVE-2012-1146
** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-oneiric (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu) Status: New => Won't Fix -- 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/952828 Title: CVE-2012-1146 Status in “linux” package in Ubuntu: Fix Released 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: New Status in “linux-lts-raring” package in Ubuntu: Won't Fix Status in “linux-lts-saucy” package in Ubuntu: New Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” 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: Fix Released Status in “linux-lts-backport-natty” source package in Lucid: Fix Released Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released Status in “linux-lts-quantal” source package in Lucid: New Status in “linux-lts-raring” source package in Lucid: Won't Fix Status in “linux-lts-saucy” source package in Lucid: New Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Maverick: Invalid Status in “linux-lts-backport-natty” source package in Maverick: Invalid Status in “linux-lts-backport-oneiric” source package in Maverick: Invalid Status in “linux-lts-backport-maverick” source package in Natty: Invalid Status in “linux-lts-backport-natty” source package in Natty: Invalid Status in “linux-lts-backport-oneiric” source package in Natty: Invalid Status in “linux-lts-backport-maverick” source package in Oneiric: Invalid Status in “linux-lts-backport-natty” source package in Oneiric: Invalid Status in “linux-lts-backport-oneiric” source package in Oneiric: 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: Won't Fix 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: 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: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: New Status in “linux-lts-raring” source package in Quantal: Won't Fix Status in “linux-lts-saucy” source package in Quantal: New 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 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 pack
[Kernel-packages] [Bug 1302225] Re: CVE-2014-2706
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1302225 Title: CVE-2014-2706 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: New Status in “linux-lts-raring” source package in Precise: Won't Fix 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 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” so
[Kernel-packages] [Bug 1306286] Re: CVE-2014-2739
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1306286 Title: CVE-2014-2739 Status in “linux” package in Ubuntu: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-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: New Status in “linux-lts-raring” source package in Precise: Won't Fix 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 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: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source pac
[Kernel-packages] [Bug 1302222] Re: CVE-2014-2678
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/130 Title: CVE-2014-2678 Status in “linux” package in Ubuntu: Fix Released 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 Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Won't Fix Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed 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 Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Fix Released Status in “
[Kernel-packages] [Bug 1302212] Re: CVE-2014-2672
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1302212 Title: CVE-2014-2672 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: 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: Won't Fix 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 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-i
[Kernel-packages] [Bug 1218959] Re: KVM virbr# no longer forwards multicast traffic by default (U12.04)
Hello Michael, or anyone else affected, Accepted libvirt into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libvirt/0.9.8-2ubuntu17.19 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libvirt (Ubuntu Precise) Status: Confirmed => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1218959 Title: KVM virbr# no longer forwards multicast traffic by default (U12.04) Status in “libvirt” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “libvirt” source package in Precise: Fix Committed Status in “linux” source package in Precise: Won't Fix Bug description: A recent kernel update (Apr 2013) has made it's way to U12.04.2 LTS (approx June-Aug 2013) and has stopped the (default) behaviour of automatically forwarding multicast traffic over virbr#. Some updates the bridge subsystem now, by default, disable multicast traffic without IGMP Querier being enabled on that bridge. The corresponding Fedora/RHEL bug tracks the progress/updates of this specific change in relation to Fedora. https://bugzilla.redhat.com/show_bug.cgi?id=880035 (I have yet to find a similar bug report in Ubuntu so I have created this bug to help the Ubuntu community identify multicast issues that may arise since April 2013 in U12.04 LTS and presumably other Ubuntu releases as backports are made and break regression testing.) Using the latest patches in U12.04.2 LTS this following addition, with some modifications, can be made to the udev rules will enable multicast on virbr# bridge: https://bugzilla.redhat.com/show_bug.cgi?id=880035#c38 While this is an improvement/correction to KVM bridge networking it has broken existing functionality in U12.04.2 LTS and broke regressed functionality that once worked. IMPACT: multicast is broken over libvirt bridges FIX: set a (new, introduced by a new kernel) toggle on the bridges TEST CASE: cat /sys/devices/virtual/net/virbr0/bridge/multicast_querier - if 0, then forwarding multicast will be broken. REGRESSION POTENTIAL: should be none. older kernels do not have the toggle, and failure to set it will be ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1218959/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1302219] Re: CVE-2014-2673
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1302219 Title: CVE-2014-2673 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: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: New Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Invalid 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: Invalid Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Invalid Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1176577] Re: [HP Compaq dc7700 Small Form Factor PC] mei unexpected reset in kernel 3.8
I installed Ubuntu 14.04 server on one of these HP Compaq dc7700 Small Form Factor PC machines. After the first boot (after install), the command prompt constantly gets messages that look like this: [ 1352.248013] mei_me :00:03.0: timer: connect/disconnect timeout. [ 1357.248022] mei_me :00:03.0: timer: connect/disconnect timeout. [ 1358.248033] mei_me :00:03.0: timer: connect/disconnect timeout. [ 1359.248053] mei_me :00:03.0: timer: connect/disconnect timeout. [ 135.2486063] mei_me :00:03.0: timer: connect/disconnect timeout. Every second this machine is on, logged in or not, these alerts bombard the terminal every second. ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1176577 Title: [HP Compaq dc7700 Small Form Factor PC] mei unexpected reset in kernel 3.8 Status in “linux” package in Ubuntu: Incomplete Status in “linux” package in Arch Linux: New Status in “linux” package in Fedora: Unknown Bug description: Right after upgrading kernel from 3.5 to 3.8 (Ubuntu 13.04), the syslog got flooded by a large number of such messages: (cut) May 5 15:33:15 compaq-aldo kernel: [ 205.064042] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:21 compaq-aldo kernel: [ 211.076029] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:27 compaq-aldo kernel: [ 217.088035] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:33 compaq-aldo kernel: [ 223.100039] mei :00:03.0: unexpected reset: dev_state = RESETING May 5 15:33:39 compaq-aldo kernel: [ 229.112045] mei :00:03.0: unexpected reset: dev_state = RESETING (cut) This was associated by non reliable ethernet functionality, i.e. transfer of large files from my Ubuntu box to a local NAS connected via ethernet got hanging with no other apparent errors or diagnostics: nautilus copy just stopped transferring data, leaving the copy window there with the progress bar stopped. I tried to reboot, but this behaviour is perfectly reproducible. This is one of the first syslog lines got from that kernel: May 5 15:30:15 compaq-aldo kernel: [0.00] Linux version 3.8.0-19-generic (buildd@roseapple) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #30-Ubuntu SMP Wed May 1 16:36:13 UTC 2013 (Ubuntu 3.8.0-19.30-generic 3.8.8) I attach the whole syslog from boot of that kernel. On the same box, launching a previsous kernel (3.5) works flawlessly. For the time being, I removed 3.8 kernel from my box, now running 3.5. Kind regards Aldo --- ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ldx2074 F pulseaudio /dev/snd/controlC0: ldx2074 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=32cc5d6d-43c1-4e97-a8b7-10b71aac3e29 InstallationDate: Installed on 2013-01-04 (121 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=38ce1d51-c3cf-438d-b395-f7c4744e2e37 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic i686 UpgradeStatus: Upgraded to raring on 2013-04-26 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark dmi.bios.date: 04/13/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.10 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC7451V4Q dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.10:bd04/13/2007:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1176577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More hel
[Kernel-packages] [Bug 1298117] Re: CVE-2014-0055
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1298117 Title: CVE-2014-0055 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: 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: Won't Fix 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: 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 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: Fix Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source p
[Kernel-packages] [Bug 1297743] Re: CVE-2014-2568
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1297743 Title: CVE-2014-2568 Status in “linux” package in Ubuntu: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-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: New Status in “linux-lts-raring” source package in Precise: Won't Fix 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 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: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source pac
[Kernel-packages] [Bug 1298119] Re: CVE-2014-0131
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1298119 Title: CVE-2014-0131 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: 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: Won't Fix 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 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” so
[Kernel-packages] [Bug 1297738] Re: CVE-2013-7339
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1297738 Title: CVE-2013-7339 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 Committed 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: Won't Fix Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Committed 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 Committed Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package i
[Kernel-packages] [Bug 1293721] Re: CVE-2014-0102
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1293721 Title: CVE-2014-0102 Status in “linux” package in Ubuntu: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-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: New Status in “linux-lts-raring” source package in Precise: Won't Fix 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 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: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source pac
[Kernel-packages] [Bug 1295090] Re: CVE-2014-2523
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1295090 Title: CVE-2014-2523 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: 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: 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: Won't Fix 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: 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 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: Fix Committed Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status
[Kernel-packages] [Bug 1293714] Re: CVE-2014-0101
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1293714 Title: CVE-2014-0101 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: 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: Won't Fix 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 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
[Kernel-packages] [Bug 1293726] Re: CVE-2014-2309
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1293726 Title: CVE-2014-2309 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: 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: Won't Fix 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 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-i
[Kernel-packages] [Bug 1293713] Re: CVE-2014-0100
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1293713 Title: CVE-2014-0100 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: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: New Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Invalid 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: Invalid Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Invalid Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1289728] Re: CVE-2014-0049
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1289728 Title: CVE-2014-0049 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 Committed Status in “linux-lts-raring” source package in Precise: Won't Fix Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid 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 Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty
[Kernel-packages] [Bug 1285051] Re: CVE-2014-0069
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New => Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Quantal) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Saucy) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New => Won't Fix -- 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/1285051 Title: CVE-2014-0069 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: 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: Won't Fix Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” 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 Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Inva
