[Kernel-packages] [Bug 1364208] Re: linux: 3.2.0-69.103 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) = Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364208 Title: linux: 3.2.0-69.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lbm series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: New Bug description: This bug is for tracking the 3.2.0-69.103 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 02. September 2014 03:28 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 02. September 2014 03:28 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349225] Re: [ASUS N550JV] suspend/resume failure
Damien Mascord, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349225/comments/4 regarding this being fixed with an 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/1349225 Title: [ASUS N550JV] suspend/resume failure Status in “linux” package in Ubuntu: Invalid Bug description: Having trouble resuming from suspend. The whole system hangs upon resume. No mouse, no keyboard input. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-5-generic 3.16.0-5.10 ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tusker F pulseaudio /dev/snd/controlC0: tusker F pulseaudio Date: Mon Jul 28 09:46:59 2014 DuplicateSignature: suspend/resume:ASUSTeK COMPUTER INC. N550JV:N550JV.208 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=c4541296-d955-4f29-a07c-30d722cfff41 InstallationDate: Installed on 2014-07-17 (11 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520) InterpreterPath: /usr/bin/python3.4 MachineType: ASUSTeK COMPUTER INC. N550JV ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-5-generic.efi.signed root=UUID=332c2929-bd56-4038-9258-f342638a8de0 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.16.0-5-generic N/A linux-backports-modules-3.16.0-5-generic N/A linux-firmware1.132 SourcePackage: linux Title: [ASUSTeK COMPUTER INC. N550JV] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV 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.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JV 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/1349225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250241] Re: [Dell Inspiron 15R SE 7520] Bluetooth mouse constantly disconnecting
Rayner Pires, the next step is to fully reverse commit bisect the kernel in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? ** 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/1250241 Title: [Dell Inspiron 15R SE 7520] Bluetooth mouse constantly disconnecting Status in “linux” package in Ubuntu: Incomplete Bug description: Ubuntu is constantly disconnecting my bluetooth mouse. Actually, the pointing service is being interrupted due to constant queries on mouse's battery state. Every time the battery level is queried the bluetooth mouse stops moving and clicking, requering I manually open the bluetooth config panel, switch the mouse connection off, and then move and click the mouse some times until it gets connected and pointing again. The problem seems to be solved after I've killed upowerd process. Is it a bug on upower daemon? Briefly, what happens is: ubuntu queries the battery charge level of the mouse and it does stop pointing. After getting the battery level, the mouse pointing feature does not automatically return as it was. I'm running Ubuntu 12.04.3 x86_64, with kernel #66~precise1-Ubuntu (3.5.0-43-generic) --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2999 F pulseaudio CasperVersion: 1.336ubuntu1 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140111) MachineType: Dell Inc. Inspiron 7520 Package: linux (not installed) ProcFB: 0 radeondrmfb 1 inteldrmfb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.13.0-1-generic N/A linux-backports-modules-3.13.0-1-generic N/A linux-firmware1.121 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0DNMM8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/03/2012:svnDellInc.:pnInspiron7520:pvrA07:rvnDellInc.:rn0DNMM8:rvrA00:cvnDellInc.:ct8:cvrA07: dmi.product.name: Inspiron 7520 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2773 F pulseaudio CasperVersion: 1.340 DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 7520 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb 1 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- locale=pt_BR keyboard-configuration/layoutcode?=br keyboard-configuration/modelcode?=abnt2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 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-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/20/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0DNMM8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd02/20/2014:svnDellInc.:pnInspiron7520:pvrA11:rvnDellInc.:rn0DNMM8:rvrA00:cvnDellInc.:ct8:cvrA11: dmi.product.name: Inspiron 7520 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1364208] Re: linux: 3.2.0-69.103 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) = Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364208 Title: linux: 3.2.0-69.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: New Bug description: This bug is for tracking the 3.2.0-69.103 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 02. September 2014 03:28 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 02. September 2014 03:28 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1363032] Re: linux: 3.16.0-12.17 -proposed tracker
This bug was fixed in the package linux - 3.16.0-12.18
---
linux (3.16.0-12.18) utopic; urgency=low
[ Paolo Pisati ]
* Revert [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
/boot/dtb-(uname -r) to make flash-kernel happy
* Revert [Debian] dtb: don't remove a symlink dereferencing an existing
directory
* Revert [Debian] dtb: don't follow symlink when checking for a
directory
* Revert [Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb
* Revert [Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)
linux (3.16.0-12.17) utopic; urgency=low
[ Andy Whitcroft ]
* Release Tracking Bug
- LP: #1363032
* Revert [Config] Switch kernel to vmlinuz (from vmlinux) on ppc64el
[ dann frazier ]
* [Config] CONFIG_ARM_GIC_V3=y
[ Douglas Lehr ]
* SAUCE: (no-up) PCI: Increase BAR size quirk for IBM ipr SAS Crocodile
adapters
- LP: #1361364
[ Marc Dietrich ]
* [Config] arm/tegra/d-i: framebuffer and usb support for Tegra SoCs
[ Paolo Pisati ]
* [Config] armhf: REGULATOR_TWL4030=y
* [Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)
* [Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb
* [Debian] dtb: don't follow symlink when checking for a directory
* [Debian] dtb: don't remove a symlink dereferencing an existing
directory
* [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
/boot/dtb-(uname -r) to make flash-kernel happy
[ Stefan Bader ]
* SAUCE: x86/xen: Fix setup of 64bit kernel pagetables
- LP: #1350522
[ Upstream Kernel Changes ]
* drm/tegra: add MODULE_DEVICE_TABLEs
* kvm: iommu: fix the third parameter of kvm_iommu_put_pages
(CVE-2014-3601)
- LP: #1362443
- CVE-2014-3601
* isofs: Fix unbounded recursion when processing relocated directories
- LP: #1362447, #1362448
- CVE-2014-5472
* arm64/crypto: fix makefile rule for aes-glue-%.o
* irq-gic: remove file name from heading comment
* irqchip: gic: Move some bits of GICv2 to a library-type file
* irqchip: gic-v3: Initial support for GICv3
* arm64: GICv3 device tree binding documentation
* arm64: boot protocol documentation update for GICv3
* KVM: arm/arm64: vgic: move GICv2 registers to their own structure
* KVM: ARM: vgic: introduce vgic_ops and LR manipulation primitives
* KVM: ARM: vgic: abstract access to the ELRSR bitmap
* KVM: ARM: vgic: abstract EISR bitmap access
* KVM: ARM: vgic: abstract MISR decoding
* KVM: ARM: vgic: move underflow handling to vgic_ops
* KVM: ARM: vgic: abstract VMCR access
* KVM: ARM: vgic: introduce vgic_enable
* KVM: ARM: introduce vgic_params structure
* KVM: ARM: vgic: split GICv2 backend from the main vgic code
* KVM: ARM: vgic: revisit implementation of irqchip_in_kernel
* arm64: KVM: remove __kvm_hyp_code_{start,end} from hyp.S
* arm64: KVM: split GICv2 world switch from hyp code
* arm64: KVM: move HCR_EL2.{IMO,FMO} manipulation into the vgic switch
code
* KVM: ARM: vgic: add the GICv3 backend
* arm64: KVM: vgic: add GICv3 world switch
* arm64: KVM: vgic: enable GICv2 emulation on top on GICv3 hardware
* arm64: gicv3: Allow GICv3 compilation with older binutils
* arm64: KVM: GICv3: move system register access to msr_s/mrs_s
* KVM: arm64: GICv3: mandate page-aligned GICV region
-- Andy Whitcroft a...@canonical.com Mon, 01 Sep 2014 12:40:54 +0100
** Changed in: linux (Ubuntu Utopic)
Status: New = Fix Released
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3601
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-5472
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1363032
Title:
linux: 3.16.0-12.17 -proposed tracker
Status in Kernel Development Workflow:
In Progress
Status in Kernel Development Workflow package-testing series:
Confirmed
Status in Kernel Development Workflow prepare-package series:
Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
Fix Released
Status in Kernel Development Workflow promote-to-release series:
New
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Utopic:
Fix Released
Bug description:
This bug is for tracking the 3.16.0-12.17 upload package. This bug
will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-Prepare-package-start:Friday, 29. August 2014 10:53 UTC
kernel-phase-changed:Friday, 29. August 2014 20:00 UTC
kernel-Prepare-package-end:Friday, 29. August 2014 20:00 UTC
kernel-Package-testing-start:Friday, 29. August 2014 20:00 UTC
kernel-phase:PPA Testing
[Kernel-packages] [Bug 1361364] Re: The Crocodile bar overlap
This bug was fixed in the package linux - 3.16.0-12.18
---
linux (3.16.0-12.18) utopic; urgency=low
[ Paolo Pisati ]
* Revert [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
/boot/dtb-(uname -r) to make flash-kernel happy
* Revert [Debian] dtb: don't remove a symlink dereferencing an existing
directory
* Revert [Debian] dtb: don't follow symlink when checking for a
directory
* Revert [Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb
* Revert [Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)
linux (3.16.0-12.17) utopic; urgency=low
[ Andy Whitcroft ]
* Release Tracking Bug
- LP: #1363032
* Revert [Config] Switch kernel to vmlinuz (from vmlinux) on ppc64el
[ dann frazier ]
* [Config] CONFIG_ARM_GIC_V3=y
[ Douglas Lehr ]
* SAUCE: (no-up) PCI: Increase BAR size quirk for IBM ipr SAS Crocodile
adapters
- LP: #1361364
[ Marc Dietrich ]
* [Config] arm/tegra/d-i: framebuffer and usb support for Tegra SoCs
[ Paolo Pisati ]
* [Config] armhf: REGULATOR_TWL4030=y
* [Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)
* [Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb
* [Debian] dtb: don't follow symlink when checking for a directory
* [Debian] dtb: don't remove a symlink dereferencing an existing
directory
* [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
/boot/dtb-(uname -r) to make flash-kernel happy
[ Stefan Bader ]
* SAUCE: x86/xen: Fix setup of 64bit kernel pagetables
- LP: #1350522
[ Upstream Kernel Changes ]
* drm/tegra: add MODULE_DEVICE_TABLEs
* kvm: iommu: fix the third parameter of kvm_iommu_put_pages
(CVE-2014-3601)
- LP: #1362443
- CVE-2014-3601
* isofs: Fix unbounded recursion when processing relocated directories
- LP: #1362447, #1362448
- CVE-2014-5472
* arm64/crypto: fix makefile rule for aes-glue-%.o
* irq-gic: remove file name from heading comment
* irqchip: gic: Move some bits of GICv2 to a library-type file
* irqchip: gic-v3: Initial support for GICv3
* arm64: GICv3 device tree binding documentation
* arm64: boot protocol documentation update for GICv3
* KVM: arm/arm64: vgic: move GICv2 registers to their own structure
* KVM: ARM: vgic: introduce vgic_ops and LR manipulation primitives
* KVM: ARM: vgic: abstract access to the ELRSR bitmap
* KVM: ARM: vgic: abstract EISR bitmap access
* KVM: ARM: vgic: abstract MISR decoding
* KVM: ARM: vgic: move underflow handling to vgic_ops
* KVM: ARM: vgic: abstract VMCR access
* KVM: ARM: vgic: introduce vgic_enable
* KVM: ARM: introduce vgic_params structure
* KVM: ARM: vgic: split GICv2 backend from the main vgic code
* KVM: ARM: vgic: revisit implementation of irqchip_in_kernel
* arm64: KVM: remove __kvm_hyp_code_{start,end} from hyp.S
* arm64: KVM: split GICv2 world switch from hyp code
* arm64: KVM: move HCR_EL2.{IMO,FMO} manipulation into the vgic switch
code
* KVM: ARM: vgic: add the GICv3 backend
* arm64: KVM: vgic: add GICv3 world switch
* arm64: KVM: vgic: enable GICv2 emulation on top on GICv3 hardware
* arm64: gicv3: Allow GICv3 compilation with older binutils
* arm64: KVM: GICv3: move system register access to msr_s/mrs_s
* KVM: arm64: GICv3: mandate page-aligned GICV region
-- Andy Whitcroft a...@canonical.com Mon, 01 Sep 2014 12:40:54 +0100
** Changed in: linux (Ubuntu Utopic)
Status: Fix Committed = Fix Released
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3601
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-5472
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1361364
Title:
The Crocodile bar overlap
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Utopic:
Fix Released
Bug description:
Canonical,
Is it possible to accept the following patch into Canonical 14.10?
It fix a problem that is affecting a lot of machines on our side.
https://patchwork.ozlabs.org/patch/381836/
The patch was just submitted upstream at the moment, and I understand
that it should be accepted into upstream tree soon.
Thank you,
Breno
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1361364/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362447] Re: CVE-2014-5471
This bug was fixed in the package linux - 3.16.0-12.18
---
linux (3.16.0-12.18) utopic; urgency=low
[ Paolo Pisati ]
* Revert [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
/boot/dtb-(uname -r) to make flash-kernel happy
* Revert [Debian] dtb: don't remove a symlink dereferencing an existing
directory
* Revert [Debian] dtb: don't follow symlink when checking for a
directory
* Revert [Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb
* Revert [Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)
linux (3.16.0-12.17) utopic; urgency=low
[ Andy Whitcroft ]
* Release Tracking Bug
- LP: #1363032
* Revert [Config] Switch kernel to vmlinuz (from vmlinux) on ppc64el
[ dann frazier ]
* [Config] CONFIG_ARM_GIC_V3=y
[ Douglas Lehr ]
* SAUCE: (no-up) PCI: Increase BAR size quirk for IBM ipr SAS Crocodile
adapters
- LP: #1361364
[ Marc Dietrich ]
* [Config] arm/tegra/d-i: framebuffer and usb support for Tegra SoCs
[ Paolo Pisati ]
* [Config] armhf: REGULATOR_TWL4030=y
* [Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)
* [Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb
* [Debian] dtb: don't follow symlink when checking for a directory
* [Debian] dtb: don't remove a symlink dereferencing an existing
directory
* [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
/boot/dtb-(uname -r) to make flash-kernel happy
[ Stefan Bader ]
* SAUCE: x86/xen: Fix setup of 64bit kernel pagetables
- LP: #1350522
[ Upstream Kernel Changes ]
* drm/tegra: add MODULE_DEVICE_TABLEs
* kvm: iommu: fix the third parameter of kvm_iommu_put_pages
(CVE-2014-3601)
- LP: #1362443
- CVE-2014-3601
* isofs: Fix unbounded recursion when processing relocated directories
- LP: #1362447, #1362448
- CVE-2014-5472
* arm64/crypto: fix makefile rule for aes-glue-%.o
* irq-gic: remove file name from heading comment
* irqchip: gic: Move some bits of GICv2 to a library-type file
* irqchip: gic-v3: Initial support for GICv3
* arm64: GICv3 device tree binding documentation
* arm64: boot protocol documentation update for GICv3
* KVM: arm/arm64: vgic: move GICv2 registers to their own structure
* KVM: ARM: vgic: introduce vgic_ops and LR manipulation primitives
* KVM: ARM: vgic: abstract access to the ELRSR bitmap
* KVM: ARM: vgic: abstract EISR bitmap access
* KVM: ARM: vgic: abstract MISR decoding
* KVM: ARM: vgic: move underflow handling to vgic_ops
* KVM: ARM: vgic: abstract VMCR access
* KVM: ARM: vgic: introduce vgic_enable
* KVM: ARM: introduce vgic_params structure
* KVM: ARM: vgic: split GICv2 backend from the main vgic code
* KVM: ARM: vgic: revisit implementation of irqchip_in_kernel
* arm64: KVM: remove __kvm_hyp_code_{start,end} from hyp.S
* arm64: KVM: split GICv2 world switch from hyp code
* arm64: KVM: move HCR_EL2.{IMO,FMO} manipulation into the vgic switch
code
* KVM: ARM: vgic: add the GICv3 backend
* arm64: KVM: vgic: add GICv3 world switch
* arm64: KVM: vgic: enable GICv2 emulation on top on GICv3 hardware
* arm64: gicv3: Allow GICv3 compilation with older binutils
* arm64: KVM: GICv3: move system register access to msr_s/mrs_s
* KVM: arm64: GICv3: mandate page-aligned GICV region
-- Andy Whitcroft a...@canonical.com Mon, 01 Sep 2014 12:40:54 +0100
** Changed in: linux (Ubuntu Utopic)
Status: New = Fix Released
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3601
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-5472
--
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/1362447
Title:
CVE-2014-5471
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:
New
Status in “linux-lts-backport-natty” package in Ubuntu:
New
Status in “linux-lts-quantal” package in Ubuntu:
Invalid
Status in “linux-lts-raring” package in Ubuntu:
Invalid
Status in “linux-lts-saucy” package in Ubuntu:
Invalid
Status in “linux-mvl-dove” package in Ubuntu:
Invalid
Status in “linux-ti-omap4” package in Ubuntu:
Invalid
Status in “linux” source package in Lucid:
Fix Committed
Status in “linux-armadaxp” source package in Lucid:
Invalid
Status in “linux-ec2” source package in Lucid:
New
Status in “linux-fsl-imx51” source package in Lucid:
Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
New
Status in “linux-lts-backport-natty” source package in Lucid:
New
Status in “linux-lts-quantal” source package in Lucid:
Invalid
Status in “linux-lts-raring” source package in Lucid:
Invalid
Status
[Kernel-packages] [Bug 1362443] Re: CVE-2014-3601
This bug was fixed in the package linux - 3.16.0-12.18
---
linux (3.16.0-12.18) utopic; urgency=low
[ Paolo Pisati ]
* Revert [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
/boot/dtb-(uname -r) to make flash-kernel happy
* Revert [Debian] dtb: don't remove a symlink dereferencing an existing
directory
* Revert [Debian] dtb: don't follow symlink when checking for a
directory
* Revert [Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb
* Revert [Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)
linux (3.16.0-12.17) utopic; urgency=low
[ Andy Whitcroft ]
* Release Tracking Bug
- LP: #1363032
* Revert [Config] Switch kernel to vmlinuz (from vmlinux) on ppc64el
[ dann frazier ]
* [Config] CONFIG_ARM_GIC_V3=y
[ Douglas Lehr ]
* SAUCE: (no-up) PCI: Increase BAR size quirk for IBM ipr SAS Crocodile
adapters
- LP: #1361364
[ Marc Dietrich ]
* [Config] arm/tegra/d-i: framebuffer and usb support for Tegra SoCs
[ Paolo Pisati ]
* [Config] armhf: REGULATOR_TWL4030=y
* [Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)
* [Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb
* [Debian] dtb: don't follow symlink when checking for a directory
* [Debian] dtb: don't remove a symlink dereferencing an existing
directory
* [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
/boot/dtb-(uname -r) to make flash-kernel happy
[ Stefan Bader ]
* SAUCE: x86/xen: Fix setup of 64bit kernel pagetables
- LP: #1350522
[ Upstream Kernel Changes ]
* drm/tegra: add MODULE_DEVICE_TABLEs
* kvm: iommu: fix the third parameter of kvm_iommu_put_pages
(CVE-2014-3601)
- LP: #1362443
- CVE-2014-3601
* isofs: Fix unbounded recursion when processing relocated directories
- LP: #1362447, #1362448
- CVE-2014-5472
* arm64/crypto: fix makefile rule for aes-glue-%.o
* irq-gic: remove file name from heading comment
* irqchip: gic: Move some bits of GICv2 to a library-type file
* irqchip: gic-v3: Initial support for GICv3
* arm64: GICv3 device tree binding documentation
* arm64: boot protocol documentation update for GICv3
* KVM: arm/arm64: vgic: move GICv2 registers to their own structure
* KVM: ARM: vgic: introduce vgic_ops and LR manipulation primitives
* KVM: ARM: vgic: abstract access to the ELRSR bitmap
* KVM: ARM: vgic: abstract EISR bitmap access
* KVM: ARM: vgic: abstract MISR decoding
* KVM: ARM: vgic: move underflow handling to vgic_ops
* KVM: ARM: vgic: abstract VMCR access
* KVM: ARM: vgic: introduce vgic_enable
* KVM: ARM: introduce vgic_params structure
* KVM: ARM: vgic: split GICv2 backend from the main vgic code
* KVM: ARM: vgic: revisit implementation of irqchip_in_kernel
* arm64: KVM: remove __kvm_hyp_code_{start,end} from hyp.S
* arm64: KVM: split GICv2 world switch from hyp code
* arm64: KVM: move HCR_EL2.{IMO,FMO} manipulation into the vgic switch
code
* KVM: ARM: vgic: add the GICv3 backend
* arm64: KVM: vgic: add GICv3 world switch
* arm64: KVM: vgic: enable GICv2 emulation on top on GICv3 hardware
* arm64: gicv3: Allow GICv3 compilation with older binutils
* arm64: KVM: GICv3: move system register access to msr_s/mrs_s
* KVM: arm64: GICv3: mandate page-aligned GICV region
-- Andy Whitcroft a...@canonical.com Mon, 01 Sep 2014 12:40:54 +0100
** Changed in: linux (Ubuntu Utopic)
Status: New = Fix Released
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-5472
--
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/1362443
Title:
CVE-2014-3601
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:
New
Status in “linux-lts-backport-natty” package in Ubuntu:
New
Status in “linux-lts-quantal” package in Ubuntu:
Invalid
Status in “linux-lts-raring” package in Ubuntu:
Invalid
Status in “linux-lts-saucy” package in Ubuntu:
Invalid
Status in “linux-mvl-dove” package in Ubuntu:
Invalid
Status in “linux-ti-omap4” package in Ubuntu:
Invalid
Status in “linux” source package in Lucid:
Invalid
Status in “linux-armadaxp” source package in Lucid:
Invalid
Status in “linux-ec2” source package in Lucid:
Invalid
Status in “linux-fsl-imx51” source package in Lucid:
Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
New
Status in “linux-lts-backport-natty” source package in Lucid:
New
Status in “linux-lts-quantal” source package in Lucid:
Invalid
Status in “linux-lts-raring” source package in Lucid:
Invalid
Status in “linux-lts-saucy” source package in Lucid:
Invalid
Status in
[Kernel-packages] [Bug 1362448] Re: CVE-2014-5472
This bug was fixed in the package linux - 3.16.0-12.18
---
linux (3.16.0-12.18) utopic; urgency=low
[ Paolo Pisati ]
* Revert [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
/boot/dtb-(uname -r) to make flash-kernel happy
* Revert [Debian] dtb: don't remove a symlink dereferencing an existing
directory
* Revert [Debian] dtb: don't follow symlink when checking for a
directory
* Revert [Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb
* Revert [Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)
linux (3.16.0-12.17) utopic; urgency=low
[ Andy Whitcroft ]
* Release Tracking Bug
- LP: #1363032
* Revert [Config] Switch kernel to vmlinuz (from vmlinux) on ppc64el
[ dann frazier ]
* [Config] CONFIG_ARM_GIC_V3=y
[ Douglas Lehr ]
* SAUCE: (no-up) PCI: Increase BAR size quirk for IBM ipr SAS Crocodile
adapters
- LP: #1361364
[ Marc Dietrich ]
* [Config] arm/tegra/d-i: framebuffer and usb support for Tegra SoCs
[ Paolo Pisati ]
* [Config] armhf: REGULATOR_TWL4030=y
* [Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)
* [Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb
* [Debian] dtb: don't follow symlink when checking for a directory
* [Debian] dtb: don't remove a symlink dereferencing an existing
directory
* [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
/boot/dtb-(uname -r) to make flash-kernel happy
[ Stefan Bader ]
* SAUCE: x86/xen: Fix setup of 64bit kernel pagetables
- LP: #1350522
[ Upstream Kernel Changes ]
* drm/tegra: add MODULE_DEVICE_TABLEs
* kvm: iommu: fix the third parameter of kvm_iommu_put_pages
(CVE-2014-3601)
- LP: #1362443
- CVE-2014-3601
* isofs: Fix unbounded recursion when processing relocated directories
- LP: #1362447, #1362448
- CVE-2014-5472
* arm64/crypto: fix makefile rule for aes-glue-%.o
* irq-gic: remove file name from heading comment
* irqchip: gic: Move some bits of GICv2 to a library-type file
* irqchip: gic-v3: Initial support for GICv3
* arm64: GICv3 device tree binding documentation
* arm64: boot protocol documentation update for GICv3
* KVM: arm/arm64: vgic: move GICv2 registers to their own structure
* KVM: ARM: vgic: introduce vgic_ops and LR manipulation primitives
* KVM: ARM: vgic: abstract access to the ELRSR bitmap
* KVM: ARM: vgic: abstract EISR bitmap access
* KVM: ARM: vgic: abstract MISR decoding
* KVM: ARM: vgic: move underflow handling to vgic_ops
* KVM: ARM: vgic: abstract VMCR access
* KVM: ARM: vgic: introduce vgic_enable
* KVM: ARM: introduce vgic_params structure
* KVM: ARM: vgic: split GICv2 backend from the main vgic code
* KVM: ARM: vgic: revisit implementation of irqchip_in_kernel
* arm64: KVM: remove __kvm_hyp_code_{start,end} from hyp.S
* arm64: KVM: split GICv2 world switch from hyp code
* arm64: KVM: move HCR_EL2.{IMO,FMO} manipulation into the vgic switch
code
* KVM: ARM: vgic: add the GICv3 backend
* arm64: KVM: vgic: add GICv3 world switch
* arm64: KVM: vgic: enable GICv2 emulation on top on GICv3 hardware
* arm64: gicv3: Allow GICv3 compilation with older binutils
* arm64: KVM: GICv3: move system register access to msr_s/mrs_s
* KVM: arm64: GICv3: mandate page-aligned GICV region
-- Andy Whitcroft a...@canonical.com Mon, 01 Sep 2014 12:40:54 +0100
** Changed in: linux (Ubuntu Utopic)
Status: New = Fix Released
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3601
--
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/1362448
Title:
CVE-2014-5472
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:
New
Status in “linux-lts-backport-natty” package in Ubuntu:
New
Status in “linux-lts-quantal” package in Ubuntu:
Invalid
Status in “linux-lts-raring” package in Ubuntu:
Invalid
Status in “linux-lts-saucy” package in Ubuntu:
Invalid
Status in “linux-mvl-dove” package in Ubuntu:
Invalid
Status in “linux-ti-omap4” package in Ubuntu:
Invalid
Status in “linux” source package in Lucid:
Fix Committed
Status in “linux-armadaxp” source package in Lucid:
Invalid
Status in “linux-ec2” source package in Lucid:
New
Status in “linux-fsl-imx51” source package in Lucid:
Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
New
Status in “linux-lts-backport-natty” source package in Lucid:
New
Status in “linux-lts-quantal” source package in Lucid:
Invalid
Status in “linux-lts-raring” source package in Lucid:
Invalid
Status in “linux-lts-saucy” source package in Lucid:
Invalid
Status in
[Kernel-packages] [Bug 1350522] Re: EC2 kernel crash due to vmalloc
This bug was fixed in the package linux - 3.16.0-12.18
---
linux (3.16.0-12.18) utopic; urgency=low
[ Paolo Pisati ]
* Revert [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
/boot/dtb-(uname -r) to make flash-kernel happy
* Revert [Debian] dtb: don't remove a symlink dereferencing an existing
directory
* Revert [Debian] dtb: don't follow symlink when checking for a
directory
* Revert [Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb
* Revert [Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)
linux (3.16.0-12.17) utopic; urgency=low
[ Andy Whitcroft ]
* Release Tracking Bug
- LP: #1363032
* Revert [Config] Switch kernel to vmlinuz (from vmlinux) on ppc64el
[ dann frazier ]
* [Config] CONFIG_ARM_GIC_V3=y
[ Douglas Lehr ]
* SAUCE: (no-up) PCI: Increase BAR size quirk for IBM ipr SAS Crocodile
adapters
- LP: #1361364
[ Marc Dietrich ]
* [Config] arm/tegra/d-i: framebuffer and usb support for Tegra SoCs
[ Paolo Pisati ]
* [Config] armhf: REGULATOR_TWL4030=y
* [Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)
* [Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb
* [Debian] dtb: don't follow symlink when checking for a directory
* [Debian] dtb: don't remove a symlink dereferencing an existing
directory
* [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
/boot/dtb-(uname -r) to make flash-kernel happy
[ Stefan Bader ]
* SAUCE: x86/xen: Fix setup of 64bit kernel pagetables
- LP: #1350522
[ Upstream Kernel Changes ]
* drm/tegra: add MODULE_DEVICE_TABLEs
* kvm: iommu: fix the third parameter of kvm_iommu_put_pages
(CVE-2014-3601)
- LP: #1362443
- CVE-2014-3601
* isofs: Fix unbounded recursion when processing relocated directories
- LP: #1362447, #1362448
- CVE-2014-5472
* arm64/crypto: fix makefile rule for aes-glue-%.o
* irq-gic: remove file name from heading comment
* irqchip: gic: Move some bits of GICv2 to a library-type file
* irqchip: gic-v3: Initial support for GICv3
* arm64: GICv3 device tree binding documentation
* arm64: boot protocol documentation update for GICv3
* KVM: arm/arm64: vgic: move GICv2 registers to their own structure
* KVM: ARM: vgic: introduce vgic_ops and LR manipulation primitives
* KVM: ARM: vgic: abstract access to the ELRSR bitmap
* KVM: ARM: vgic: abstract EISR bitmap access
* KVM: ARM: vgic: abstract MISR decoding
* KVM: ARM: vgic: move underflow handling to vgic_ops
* KVM: ARM: vgic: abstract VMCR access
* KVM: ARM: vgic: introduce vgic_enable
* KVM: ARM: introduce vgic_params structure
* KVM: ARM: vgic: split GICv2 backend from the main vgic code
* KVM: ARM: vgic: revisit implementation of irqchip_in_kernel
* arm64: KVM: remove __kvm_hyp_code_{start,end} from hyp.S
* arm64: KVM: split GICv2 world switch from hyp code
* arm64: KVM: move HCR_EL2.{IMO,FMO} manipulation into the vgic switch
code
* KVM: ARM: vgic: add the GICv3 backend
* arm64: KVM: vgic: add GICv3 world switch
* arm64: KVM: vgic: enable GICv2 emulation on top on GICv3 hardware
* arm64: gicv3: Allow GICv3 compilation with older binutils
* arm64: KVM: GICv3: move system register access to msr_s/mrs_s
* KVM: arm64: GICv3: mandate page-aligned GICV region
-- Andy Whitcroft a...@canonical.com Mon, 01 Sep 2014 12:40:54 +0100
** Changed in: linux (Ubuntu Utopic)
Status: Fix Committed = Fix Released
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3601
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-5472
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1350522
Title:
EC2 kernel crash due to vmalloc
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Utopic:
Fix Released
Bug description:
During Alpha-2 automated testing, I saw the following in a log:
19:35:02 [2.475810] systemd-udevd[95]: starting version 204
19:35:02 [2.547049] [ cut here ]
19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at
/build/buildd/linux-3.16.0/mm/vmalloc.c:128
vmap_page_range_noflush+0x2d1/0x370()
19:35:02 [2.547069] Modules linked in:
19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted
3.16.0-6-generic #11-Ubuntu
19:35:02 [2.547077] 0009 880002defb98 81755538
19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88
0001
19:35:02 [2.547086] 880002fcfb00 c0391000
880002defbe0
19:35:02 [2.547090] Call Trace:
19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56
19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0
19:35:02 [2.547104]
[Kernel-packages] [Bug 1220146] Re: Need support for new Ralink Wifi card - Mediatek 7630 [14c3:7630]
@jahidulhamid I can't make my bluetooth working, wifi is ok, can you explain me step by step please because I'm new in Linux world? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1220146 Title: Need support for new Ralink Wifi card - Mediatek 7630 [14c3:7630] Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in The Linux Kernel: Confirmed Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Raring: Incomplete Status in “linux” source package in Saucy: Incomplete Status in “linux” package in Fedora: New Bug description: This device is appearing in some OEM machines, but driver is not yet available in mainline. The driver seems to be present in machines with pre-installed OS, but isn't available on the download-and-install versions! To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1220146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1287587] Re: [ASUSTeK Computer Inc. K53SD] suspend/resume failure
@pawel.jasinski I observed same behavior and independently arrived to the same conclusion. I suspend by pressing [fn]-[f1], then close the lid and pick up the laptop. Then on the other site I resume it from suspend. Case 1 : If the lid was closed immediately after pressing the key combo, everything is fine, laptop resumes when asked. Case 2 : If the lid was closed after a few seconds after pressing the key combo, laptop hangs on resume. After force reboot it says something prevented a previous reboot from finishing. Case 3 : If the lid was closed after waiting for the suspend to complete (power led blinking), everything is fine, laptop resumes when asked. I have been observing this behavior since Ubuntu 14.04 . Case 2 seldom happens, so I can't be sure it didn't happen with Ubuntu 13.10 that I used on the same laptop before. ( cd /var/log/ ; zgrep BUG $( ls -1b syslog syslog.1 syslog.?.gz syslog.??.gz syslog.???.gz | tac ; ) ; ) syslog.57.gz:Jun 29 16:57:26 n55sf-l kernel: [ 2761.992920] kernel BUG at /build/buildd/linux-3.13.0/drivers/misc/mei/hbm.c:787! syslog.57.gz:Jun 29 16:57:26 n55sf-l kernel: [ 2761.993765] BUG: unable to handle kernel paging request at ffd8 syslog.44.gz:Jul 12 19:20:04 n55sf-l kernel: [50310.39] kernel BUG at /build/buildd/linux-3.13.0/drivers/misc/mei/hbm.c:787! syslog.44.gz:Jul 12 19:20:04 n55sf-l kernel: [50310.334340] BUG: unable to handle kernel paging request at ffd8 syslog.32.gz:Jul 26 19:40:50 n55sf-l kernel: [93109.061480] kernel BUG at /build/buildd/linux-3.13.0/drivers/misc/mei/hbm.c:787! syslog.32.gz:Jul 26 19:40:50 n55sf-l kernel: [93109.062126] BUG: unable to handle kernel paging request at ffd8 syslog.28.gz:Aug 1 18:04:59 n55sf-l kernel: [19701.529305] kernel BUG at /build/buildd/linux-3.13.0/drivers/misc/mei/hbm.c:787! syslog.28.gz:Aug 1 18:04:59 n55sf-l kernel: [19701.530697] BUG: unable to handle kernel paging request at ffd8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1287587 Title: [ASUSTeK Computer Inc. K53SD] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu Trusty Tahr (development branch) Release:14.04 cat /proc/version_signature Ubuntu 3.13.0-14.34-generic 3.13.5 ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-14-generic 3.13.0-14.34 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 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: karma 2367 F pulseaudio CRDA: country RU: (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) Date: Tue Mar 4 16:00:38 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=c0e46d37-b5cd-43aa-94a7-4fa61e48c9a0 InstallationDate: Installed on 2012-09-30 (520 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.1) InterpreterPath: /usr/bin/python3.4 MachineType: ASUSTeK Computer Inc. K53SD 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-14-generic root=UUID=3a12bdbf-2c31-4f31-b854-e8f79e6888ad ro rootfstype=ext4 verbose resume=UUID=c0e46d37-b5cd-43aa-94a7-4fa61e48c9a0 crashkernel=384M-:128M 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-14-generic N/A linux-backports-modules-3.13.0-14-generic N/A linux-firmware 1.125 SourcePackage: linux Title: [ASUSTeK Computer Inc. K53SD] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2013-11-10 (113 days ago) UserGroups: dmi.bios.date: 03/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53SD.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53SD 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.:bvrK53SD.205:bd03/06/2012:svnASUSTeKComputerInc.:pnK53SD:pvr1.0:rvnASUSTeKComputerInc.:rnK53SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1287587] Re: [ASUSTeK Computer Inc. K53SD] suspend/resume failure
Oh, I forgot. The laptop involved in previous comment is Asus n55sf. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1287587 Title: [ASUSTeK Computer Inc. K53SD] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu Trusty Tahr (development branch) Release:14.04 cat /proc/version_signature Ubuntu 3.13.0-14.34-generic 3.13.5 ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-14-generic 3.13.0-14.34 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 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: karma 2367 F pulseaudio CRDA: country RU: (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) Date: Tue Mar 4 16:00:38 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=c0e46d37-b5cd-43aa-94a7-4fa61e48c9a0 InstallationDate: Installed on 2012-09-30 (520 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.1) InterpreterPath: /usr/bin/python3.4 MachineType: ASUSTeK Computer Inc. K53SD 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-14-generic root=UUID=3a12bdbf-2c31-4f31-b854-e8f79e6888ad ro rootfstype=ext4 verbose resume=UUID=c0e46d37-b5cd-43aa-94a7-4fa61e48c9a0 crashkernel=384M-:128M 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-14-generic N/A linux-backports-modules-3.13.0-14-generic N/A linux-firmware 1.125 SourcePackage: linux Title: [ASUSTeK Computer Inc. K53SD] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2013-11-10 (113 days ago) UserGroups: dmi.bios.date: 03/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53SD.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53SD 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.:bvrK53SD.205:bd03/06/2012:svnASUSTeKComputerInc.:pnK53SD:pvr1.0:rvnASUSTeKComputerInc.:rnK53SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53SD 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/1287587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1345897] Re: [Dell Inspiron 3541] High failures found in fwts klog test
the failures are form buggy firmware, set the method _PSR as NotSerialized, but
create the objects.
As from the ACPI spec mention,
Functions are equivalent to a Method that specifies NotSerialized. As such, a
function should not
create any named objects, since a second thread that might re-enter the
function will cause a fatal
error if an attempt is made to create the same named object twice.
Method (_PSR, 0, NotSerialized) // _PSR: Power Source
{
...
CreateWordField (XX00, Zero, SSZE)
CreateByteField (XX00, 0x02, ACST)
Store (0x03, SSZE)
Sleep (0x64)
If (Local0)
...
The _PSR method returns whether this power source device is currently online.
This causes temporarily cannot get the Power Source status online or not.
** Changed in: linux (Ubuntu)
Status: Incomplete = Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1345897
Title:
[Dell Inspiron 3541] High failures found in fwts klog test
Status in “linux” package in Ubuntu:
Won't Fix
Bug description:
CID: 201403-14859 Dell Inspiron 3541
The following HIGH kernel messages were found in fwts klog test:
High failures: 2
klog: HIGH Kernel message: [2.141589] ACPI Error: [SSZE] Namespace
lookup failure, AE_ALREADY_EXISTS (20131115/dsfield-211)
klog: HIGH Kernel message: [2.141609] ACPI Error: Method parse/execution
failed [\_SB_.AC__._PSR] (Node 88006835d410), AE_ALREADY_EXISTS
(20131115/psparse-536)
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
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1717 F pulseaudio
/dev/snd/controlC0: ubuntu 1717 F pulseaudio
CRDA:
country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
CurrentDesktop: Unity
Date: Sun Jul 20 22:44:13 2014
HibernationDevice: RESUME=UUID=43272c2a-1a8c-404b-8b62-9c6b53e1a765
InstallationDate: Installed on 2014-07-16 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: Dell Inc. Inspiron 3541
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed
root=UUID=4f3d06a7-1106-40c0-a15b-0657fd66a382 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: 03/20/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: Inspiron 3541
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrA00:bd03/20/2014:svnDellInc.:pnInspiron3541:pvrNotSpecified:rvnDellInc.:rnInspiron3541:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3541
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1345897/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1318551] Re: Kernel Panic - not syncing: An NMI occurred, please see the Integrated Management Log for details.
I've also tried to recompile the kernel disabling CONFIG_X86_PCC_CPUFREQ, but the resulting kernel is still crashing on boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318551 Title: Kernel Panic - not syncing: An NMI occurred, please see the Integrated Management Log for details. Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu Server 14.04 amd64 Linux global04-jobs2 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux HW: HP DL380p Gen8 / Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz / 256GB global04-jobs2 login: [203930.116834] Kernel panic - not syncing: An NMI occurred, please see the Integrated Management Log for details. [203930.116834] [203930.174171] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-24-generic #46-Ubuntu [203930.211766] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 02/10/2014 [203930.249588] b9792e2c349e 881fbfa06dd0 81715a64 a02c02d8 [203930.286130] 881fbfa06e48 8170ec65 0008 881fbfa06e58 [203930.322243] 881fbfa06df8 c90029274072 0001 [203930.358126] Call Trace: [203930.370201] NMI [81715a64] dump_stack+0x45/0x56 [203930.407285] [8170ec65] panic+0xc8/0x1d7 [203930.430907] [a02bf8fd] hpwdt_pretimeout+0xdd/0xdd [hpwdt] [203930.461560] [8101b7d9] ? sched_clock+0x9/0x10 [203930.487228] [8171f108] nmi_handle.isra.3+0x88/0x180 [203930.516179] [8171f3bd] do_nmi+0x1bd/0x340 [203930.540958] [8171e571] end_repeat_nmi+0x1e/0x2e [203930.567543] [813dfd78] ? intel_idle+0xd8/0x140 [203930.593928] [813dfd78] ? intel_idle+0xd8/0x140 [203930.619941] [813dfd78] ? intel_idle+0xd8/0x140 [203930.646100] EOE [815c9570] cpuidle_enter_state+0x40/0xc0 [203930.678933] [815c96a9] cpuidle_idle_call+0xb9/0x1f0 [203930.707409] [8101ceae] arch_cpu_idle+0xe/0x30 [203930.734325] [810beb85] cpu_startup_entry+0xc5/0x290 [203930.763715] [81703f37] rest_init+0x77/0x80 [203930.789115] [81d34f70] start_kernel+0x438/0x443 [203930.815958] [81d34941] ? repair_env_string+0x5c/0x5c [203930.844461] [81d34120] ? early_idt_handlers+0x120/0x120 [203930.874616] [81d345ee] x86_64_start_reservations+0x2a/0x2c [203930.907482] [81d34733] x86_64_start_kernel+0x143/0x152 [203930.942571] ERST: [Firmware Warn]: Firmware does not respond in time. [203930.983822] ERST: [Firmware Warn]: Firmware does not respond in time. [203931.026586] ERST: [Firmware Warn]: Firmware does not respond in time. [203931.068394] ERST: [Firmware Warn]: Firmware does not respond in time. [203931.110558] ERST: [Firmware Warn]: Firmware does not respond in time. [203931.151923] ERST: [Firmware Warn]: Firmware does not respond in time. [203931.189421] [ cut here ] [203931.212832] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/kernel/rcu/tree.c:508 rcu_eqs_exit_common.isra.48+0x110/0x120() [203931.269279] Modules linked in: veth bridge bonding dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c gpio_ich x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul sb_edac glue_helper 8021q ablk_helper cryptd hpwdt hpilo edac_core ioatdma lpc_ich psmouse garp serio_raw stp mrp llc acpi_power_meter ipmi_si mac_hid lp parport igb i2c_algo_bit tg3 dca ptp hpsa pps_core [203931.488907] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-24-generic #46-Ubuntu [203931.526932] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 02/10/2014 [203931.559891] 0009 881fbfa03ed0 81715a64 [203931.597473] 881fbfa03f08 810676bd 0001 0046 [203931.634669] 81c93398 881fbfa03f18 [203931.696007] Call Trace: [203931.708590] IRQ [81715a64] dump_stack+0x45/0x56 [203931.737818] [810676bd] warn_slowpath_common+0x7d/0xa0 [203931.767951] [8106779a] warn_slowpath_null+0x1a/0x20 [203931.797160] [810c8720] rcu_eqs_exit_common.isra.48+0x110/0x120 [203931.831002] [810caf05] rcu_irq_enter+0x75/0xa0 [203931.857924] [8106cea7] irq_enter+0x17/0xa0 [203931.883727] [8109894e] scheduler_ipi+0x4e/0x1d0 [203931.911444] [810404ca] smp_reschedule_interrupt+0x2a/0x30 [203931.943438] [8172781d] reschedule_interrupt+0x6d/0x80 [203931.973619] EOI NMI [8170ed33] ? panic+0x196/0x1d7 [203932.005056] [a02bf8fd] hpwdt_pretimeout+0xdd/0xdd [hpwdt] [203932.036609] [8101b7d9] ?
[Kernel-packages] [Bug 1364290] [NEW] linux-ti-omap4: version to be filled -proposed tracker
Public bug reported: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 02. September 2014 09:01 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 02. September 2014 09:01 UTC kernel-stable-master-bug:1364208 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/package-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: ubuntu-armel-kernel (ubuntu-armel-kernel) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Platform QA Team (canonical-platform-qa) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: ubuntu-armel-kernel (ubuntu-armel-kernel) Status: New ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: New ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Tags: armel kernel-release-tracking-bug precise ** Tags added: kernel-release-tracking-bug ** Tags added: armel ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Tags added: precise ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New = In Progress ** Changed in: kernel-sru-workflow Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Status: New = Invalid ** Changed in: kernel-sru-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/package-testing Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) = ubuntu-armel-kernel (ubuntu-armel-kernel) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) = Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in:
[Kernel-packages] [Bug 1364208] Re: linux: 3.2.0-69.103 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-lbm Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: Canonical Kernel Team (canonical-kernel-team) = Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364208 Title: linux: 3.2.0-69.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: New Bug description: This bug is for tracking the 3.2.0-69.103 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 02. September 2014 03:28 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Tuesday, 02. September 2014 09:08 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 09:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 09:08 UTC ppa-package-testing-start:Tuesday, 02. September 2014 09:08 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364290] Derivative package tracking bug
This tracking bug was opened to be worked from linux-3.2.0-69.103 update (bug 1364208) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1364290 Title: linux-ti-omap4: version to be filled -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 02. September 2014 09:01 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 02. September 2014 09:01 UTC kernel-stable-master-bug:1364208 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364291] [NEW] linux-armadaxp: version to be filled -proposed tracker
Public bug reported: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 02. September 2014 09:04 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 02. September 2014 09:04 UTC kernel-stable-master-bug:1364208 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/package-testing Importance: Medium Assignee: Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Platform QA Team (canonical-platform-qa) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Tags: armhf kernel-release-tracking-bug precise ** Tags added: kernel-release-tracking-bug ** Tags added: armhf ** Also affects: linux-armadaxp (Ubuntu Precise) Importance: Undecided Status: New ** Tags added: precise ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New = In Progress ** Changed in: kernel-sru-workflow Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Status: New = Invalid ** Changed in: kernel-sru-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/package-testing Assignee: (unassigned) = Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) = Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) = Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) = Ubuntu Stable Release Updates Team
[Kernel-packages] [Bug 1364291] Derivative package tracking bug
This tracking bug was opened to be worked from linux-3.2.0-69.103 update (bug 1364208) -- 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/1364291 Title: linux-armadaxp: version to be filled -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in “linux-armadaxp” package in Ubuntu: New Status in “linux-armadaxp” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 02. September 2014 09:04 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 02. September 2014 09:04 UTC kernel-stable-master-bug:1364208 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364208] Packages available
All builds are complete, packages in this bug can be copied to -proposed. Derivative packages from packages here can be worked on, the following tracking bugs were opened for them: linux-ti-omap4 - bug 1364290 linux-armadaxp - bug 1364291 linux-lowlatency - bug 1364293 ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New = Confirmed ** Changed in: kernel-sru-workflow/package-testing Status: New = In Progress ** Changed in: kernel-sru-workflow/package-testing Status: In Progress = Confirmed ** Description changed: This bug is for tracking the 3.2.0-69.103 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 02. September 2014 03:28 UTC - kernel-stable-phase:Prepare - kernel-stable-phase-changed:Tuesday, 02. September 2014 03:28 UTC + kernel-stable-phase:PPA Testing + kernel-stable-phase-changed:Tuesday, 02. September 2014 09:08 UTC + kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 09:08 UTC + kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 09:08 UTC + ppa-package-testing-start:Tuesday, 02. September 2014 09:08 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364208 Title: linux: 3.2.0-69.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: New Bug description: This bug is for tracking the 3.2.0-69.103 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 02. September 2014 03:28 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Tuesday, 02. September 2014 09:08 UTC kernel-stable-Prepare-package-end:Tuesday, 02. September 2014 09:08 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 02. September 2014 09:08 UTC ppa-package-testing-start:Tuesday, 02. September 2014 09:08 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1364208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1356236] Re: [Samsung NP900X3C-A05DE] iwlwifi 0000:01:00.0: fail to flush all tx fifo queues Q 2 with Centrino Advanced-N 6235 wireless card
Hi since I do not use the eduroam wireless network daily I couldn't test it earlier. Today I used it for about an hour with the 3.17.0-031700rc3-generic from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc3-utopic/ without any problems. I even stress tested the wireless for about 15 minutes by downloading a 1GB file. So for now I would say the problem disappeared with the 3.17 RC3. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1356236 Title: [Samsung NP900X3C-A05DE] iwlwifi :01:00.0: fail to flush all tx fifo queues Q 2 with Centrino Advanced-N 6235 wireless card Status in “linux” package in Ubuntu: Incomplete Bug description: The network I want to connect is a WPA-EAP wireless network called eduroam https://www.eduroam.org/ . My machine data: Wlan chip is a *-network description: Wireless interface product: Centrino Advanced-N 6235 vendor: Intel Corporation physical id: 0 bus info: pci@:01:00.0 logical name: wlan0 version: 24 serial: c8:f7:33:19:7e:f4 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=3.13.0-32-generic firmware=18.168.6.1 ip=172.19.3.235 latency=0 link=yes multicast=yes wireless=IEEE 802.11abg resources: irq:49 memory:f060-f0601fff ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: degenkolb 2203 F pulseaudio degenkolb 2587 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 13 10:32:45 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d7406378-f782-4cab-80d9-4fe3c2f4c94c InstallationDate: Installed on 2013-12-05 (250 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=04d6e506-7152-4b6c-b19f-3877e0710fc6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-06-18 (55 days ago) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P02ABK dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP900X3C-A05DE 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.:bvrP02ABK:bd09/19/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3C-A05DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/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/1356236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1345897] Re: [Dell Inspiron 3541] High failures found in fwts klog test
Ivan Hu, would the A02 BIOS address this issue via http://www.dell.com/support/home/us/en/04/product- support/product/inspiron-15-3541-laptop/drivers ? ** Tags removed: bios-outdated-a01 ** Tags added: bios-outdated-a02 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1345897 Title: [Dell Inspiron 3541] High failures found in fwts klog test Status in “linux” package in Ubuntu: Won't Fix Bug description: CID: 201403-14859 Dell Inspiron 3541 The following HIGH kernel messages were found in fwts klog test: High failures: 2 klog: HIGH Kernel message: [2.141589] ACPI Error: [SSZE] Namespace lookup failure, AE_ALREADY_EXISTS (20131115/dsfield-211) klog: HIGH Kernel message: [2.141609] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR] (Node 88006835d410), AE_ALREADY_EXISTS (20131115/psparse-536) 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 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1717 F pulseaudio /dev/snd/controlC0: ubuntu 1717 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Sun Jul 20 22:44:13 2014 HibernationDevice: RESUME=UUID=43272c2a-1a8c-404b-8b62-9c6b53e1a765 InstallationDate: Installed on 2014-07-16 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 3541 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=4f3d06a7-1106-40c0-a15b-0657fd66a382 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: 03/20/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: Inspiron 3541 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2014:svnDellInc.:pnInspiron3541:pvrNotSpecified:rvnDellInc.:rnInspiron3541:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3541 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1345897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1356236] Re: [Samsung NP900X3C-A05DE] iwlwifi 0000:01:00.0: fail to flush all tx fifo queues Q 2 with Centrino Advanced-N 6235 wireless card
cd311, the next step is to fully reverse commit bisect the kernel in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F . ** Tags added: kernel-fixed-upstream-3.17-rc3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1356236 Title: [Samsung NP900X3C-A05DE] iwlwifi :01:00.0: fail to flush all tx fifo queues Q 2 with Centrino Advanced-N 6235 wireless card Status in “linux” package in Ubuntu: Incomplete Bug description: The network I want to connect is a WPA-EAP wireless network called eduroam https://www.eduroam.org/ . My machine data: Wlan chip is a *-network description: Wireless interface product: Centrino Advanced-N 6235 vendor: Intel Corporation physical id: 0 bus info: pci@:01:00.0 logical name: wlan0 version: 24 serial: c8:f7:33:19:7e:f4 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=3.13.0-32-generic firmware=18.168.6.1 ip=172.19.3.235 latency=0 link=yes multicast=yes wireless=IEEE 802.11abg resources: irq:49 memory:f060-f0601fff ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: degenkolb 2203 F pulseaudio degenkolb 2587 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 13 10:32:45 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d7406378-f782-4cab-80d9-4fe3c2f4c94c InstallationDate: Installed on 2013-12-05 (250 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=04d6e506-7152-4b6c-b19f-3877e0710fc6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-06-18 (55 days ago) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P02ABK dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP900X3C-A05DE 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.:bvrP02ABK:bd09/19/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3C-A05DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/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/1356236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1356236] Re: [Samsung NP900X3C-A05DE] iwlwifi 0000:01:00.0: fail to flush all tx fifo queues Q 2 with Centrino Advanced-N 6235 wireless card
cd311, the next step is to fully reverse commit bisect the kernel in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1356236 Title: [Samsung NP900X3C-A05DE] iwlwifi :01:00.0: fail to flush all tx fifo queues Q 2 with Centrino Advanced-N 6235 wireless card Status in “linux” package in Ubuntu: Incomplete Bug description: The network I want to connect is a WPA-EAP wireless network called eduroam https://www.eduroam.org/ . My machine data: Wlan chip is a *-network description: Wireless interface product: Centrino Advanced-N 6235 vendor: Intel Corporation physical id: 0 bus info: pci@:01:00.0 logical name: wlan0 version: 24 serial: c8:f7:33:19:7e:f4 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=3.13.0-32-generic firmware=18.168.6.1 ip=172.19.3.235 latency=0 link=yes multicast=yes wireless=IEEE 802.11abg resources: irq:49 memory:f060-f0601fff ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: degenkolb 2203 F pulseaudio degenkolb 2587 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 13 10:32:45 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d7406378-f782-4cab-80d9-4fe3c2f4c94c InstallationDate: Installed on 2013-12-05 (250 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=04d6e506-7152-4b6c-b19f-3877e0710fc6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-06-18 (55 days ago) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P02ABK dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP900X3C-A05DE 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.:bvrP02ABK:bd09/19/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3C-A05DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/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/1356236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1329566] Re: [Lenovo ThinkPad X240] RTS5227 card reader not recognized on running Ubuntu 14.04
| From: Christopher M. Penalver | Date: Aug 30 01:04:59 2014 - | | Jim Bednar, spooky things like booting from Windows intermittently allow | somethings to work is uncommon, but not unheard of. It's more towards a | timing or firmware issue that linux is not dealing with properly, that | obviously Windows has proper support for. Sorry if I was unclear -- booting into Windows didn't cause Linux to work; it simply works fine in Windows, and only worked one time in Linux (for no reason I know of, but not on the same day as testing Windows), and otherwise has never worked in Linux. | Would you be able to boot into | http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc2-utopic/ for | a mainline test? I tried grabbing those .deb files (*all*.deb and *i386*.deb) and installing them into my live USB system (the one you asked me to set up last week). However, that system now no longer boots, probably just because of issues with it not quite being a real filesystem when installing the kernel .debs. I'm reluctant to try installing them on my real OS setup, out of fear of making it unbootable too, but if you think it's safe to do that I can try it. Jim -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1329566 Title: [Lenovo ThinkPad X240] RTS5227 card reader not recognized on running Ubuntu 14.04 Status in “linux” package in Ubuntu: Incomplete Bug description: According to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1153618, support for the RTS5227 SD card reader was added in 2013 for kernel version 3.5.0. However, SD cards are not recognized for my Lenovo Thinkpad X240 running the much later release Ubuntu 14.04 with kernel version 3.13.0, for which lspci reports: 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01) That appears to be the same symptom as when there was no support at all. Any idea what happened to the support for this SD card reader, or what I can do to work around it? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbednar1939 F pulseaudio /dev/snd/controlC1: jbednar1939 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 13 01:31:35 2014 HibernationDevice: RESUME=UUID=81e29d41-40af-46b4-a21b-65dc0926893f InstallationDate: Installed on 2014-04-18 (55 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 20AL007YUK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=6056689d-ecb4-4549-9682-f1c5b878caa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GIET67WW (2.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AL007YUK dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET67WW(2.17):bd01/08/2014:svnLENOVO:pn20AL007YUK:pvrThinkPadX240:rvnLENOVO:rn20AL007YUK:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AL007YUK dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1329566] Re: [Lenovo ThinkPad X240] RTS5227 card reader not recognized on running Ubuntu 14.04
Jim Bednar, please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc3-utopic/ . If for whatever reason it doesn't work out, one may uninstall it as advised in https://wiki.ubuntu.com/Kernel/MainlineBuilds . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1329566 Title: [Lenovo ThinkPad X240] RTS5227 card reader not recognized on running Ubuntu 14.04 Status in “linux” package in Ubuntu: Incomplete Bug description: According to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1153618, support for the RTS5227 SD card reader was added in 2013 for kernel version 3.5.0. However, SD cards are not recognized for my Lenovo Thinkpad X240 running the much later release Ubuntu 14.04 with kernel version 3.13.0, for which lspci reports: 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01) That appears to be the same symptom as when there was no support at all. Any idea what happened to the support for this SD card reader, or what I can do to work around it? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbednar1939 F pulseaudio /dev/snd/controlC1: jbednar1939 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 13 01:31:35 2014 HibernationDevice: RESUME=UUID=81e29d41-40af-46b4-a21b-65dc0926893f InstallationDate: Installed on 2014-04-18 (55 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 20AL007YUK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=6056689d-ecb4-4549-9682-f1c5b878caa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GIET67WW (2.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AL007YUK dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET67WW(2.17):bd01/08/2014:svnLENOVO:pn20AL007YUK:pvrThinkPadX240:rvnLENOVO:rn20AL007YUK:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AL007YUK dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1363655] Re: [System manufacturer System Product Name] suspend/resume failure [non-free: nvidia]
** Tags added: bios-outdated-2403 ** Summary changed: - [System manufacturer System Product Name] suspend/resume failure [non-free: nvidia] + [Asus P8Z77-V LX] suspend/resume failure [non-free: nvidia] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1363655 Title: [Asus P8Z77-V LX] suspend/resume failure [non-free: nvidia] Status in “linux” package in Ubuntu: Confirmed Bug description: I was trying to resume and my display never turned on. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-11-generic 3.16.0-11.16 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bdmurray 3864 F pulseaudio /dev/snd/controlC0: bdmurray 3864 F pulseaudio Date: Sun Aug 31 06:42:01 2014 DuplicateSignature: suspend/resume:System manufacturer System Product Name:2303 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=24b89185-eb5d-476c-ba6d-d71b78071334 InstallationDate: Installed on 2013-01-16 (591 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130116) InterpreterPath: /usr/bin/python3.4 MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 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.16.0-11-generic N/A linux-backports-modules-3.16.0-11-generic N/A linux-firmware 1.133 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: keucr SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: [System manufacturer System Product Name] suspend/resume failure [non-free: nvidia] UpgradeStatus: Upgraded to utopic on 2014-08-29 (1 days ago) UserGroups: dmi.bios.date: 12/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2303 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2303:bd12/05/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1363647] Re: Touchpad not detected Microstar E6239
Manuel Valle, thank you for reporting this and helping make Ubuntu better. Please boot into the default Ubuntu kernel (not a mainline one) and execute at a terminal: apport-collect 1363647 ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1363647 Title: Touchpad not detected Microstar E6239 Status in “linux” package in Ubuntu: Incomplete Bug description: No touchpad is detected. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: elementary OS 0.3 InstallationDate: Installed on 2014-08-30 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Package: linux (not installed) Tags: freya Uname: Linux 3.17.0-031700rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1363853] Re: [LENOVO 429149G] suspend/resume failure
** Tags added: bios-outdated-1.39 ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Summary changed: - [LENOVO 429149G] suspend/resume failure + [Lenovo ThinkPad X220] suspend/resume failure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1363853 Title: [Lenovo ThinkPad X220] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: No idea what happened. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-11-generic 3.16.0-11.16 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2818 F pulseaudio Date: Mon Sep 1 09:13:35 2014 DuplicateSignature: suspend/resume:LENOVO 429149G:8DET46WW (1.16 ) ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=e3968bc2-4b49-4bc2-a8f2-485b8cdd957f InstallationDate: Installed on 2013-12-22 (252 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131221) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 429149G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-11-generic root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d 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.16.0-11-generic N/A linux-backports-modules-3.16.0-11-generic N/A linux-firmware 1.133 SourcePackage: linux Title: [LENOVO 429149G] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G 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:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1363661] Re: no proprietary driver
ciryon, thank you for reporting this and helping make Ubuntu better. As per https://downloadcenter.intel.com/SearchResult.aspx?lang=engFamilyId=36ProductID=2780ProdId=2780 an update to your BIOS is available (0572). 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. As well, you don't have to create a new bug report. Once the BIOS is updated, then please mark this report Status Confirmed. For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Thank you for your understanding. ** Tags added: bios-outdated-0572 ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1363661 Title: no proprietary driver Status in “linux” package in Ubuntu: Incomplete Bug description: Hello I've switched from ubuntu 14.04 32 bits to 14.04 64 bits. In the additional driver tab of my system parametrers, the usual nvidia proprietary driver which wera appearing in the 32 bits version does not appears in the 64 bits version. As a workaround, I've installed this PPA : https://launchpad.net/~xorg-edgers/+archive/ubuntu/ppa but the system refuses to add the updates after this PPa is installed because it says the updates have not been verifiedI have not have this problem on 32 bits... --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1604c98d-ec9c-4c56-b311-87ad841b3f2c InstallationDate: Installed on 2014-08-31 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=2145f258-16d8-4edf-b411-7958d94b8fd4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DG33BU dmi.board.vendor: Intel Corporation dmi.board.version: AAD79951-406 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDG33BU:rvrAAD79951-406:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364333] [NEW] Num lock LED doesn't light up while Num lock state is on.
Public bug reported: Num lock LED doesn't light up while Num lock state is on. If you press Num lock key, it will be put to off. And when you press it again, it will be on and LED will on. In some cases LED will be off again while Num keys will continue to work same as Num LED is enabled. All above is true for logon screen, for desktop and for terminals by ctrl+alt+F[1-6]. Found it on multiple computers with numpad. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihor 2025 F pulseaudio Date: Tue Sep 2 13:57:03 2014 HibernationDevice: RESUME=UUID=22d29605-7b7f-4743-9e46-c30f09460dfa InstallationDate: Installed on 2014-08-07 (26 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0a0a156d-8fc5-473d-bb54-ef83d71e2feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd11/30/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1364333 Title: Num lock LED doesn't light up while Num lock state is on. Status in “linux” package in Ubuntu: Confirmed Bug description: Num lock LED doesn't light up while Num lock state is on. If you press Num lock key, it will be put to off. And when you press it again, it will be on and LED will on. In some cases LED will be off again while Num keys will continue to work same as Num LED is enabled. All above is true for logon screen, for desktop and for terminals by ctrl+alt+F[1-6]. Found it on multiple computers with numpad. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihor 2025 F pulseaudio Date: Tue Sep 2 13:57:03 2014 HibernationDevice: RESUME=UUID=22d29605-7b7f-4743-9e46-c30f09460dfa InstallationDate: Installed on 2014-08-07 (26 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0a0a156d-8fc5-473d-bb54-ef83d71e2feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX
[Kernel-packages] [Bug 1277741] Re: 15 sec timeout when mounting with nfs4
[code] ZL~# ZL~# time mount -t nfs 127.0.0.1:/home/victor0/samba/ /mnt real0m16.078s user0m0.004s sys 0m0.004s ZL~# [/code] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1277741 Title: 15 sec timeout when mounting with nfs4 Status in “linux” package in Ubuntu: Triaged Status in Fedora: Unknown Bug description: With the default nfs-common configuration (rpc.gssd not running), there is a 15 second delay when mounting an NFSv4 filesystem. After setting NEED_GSSD=yes and starting rpc.gssd, there is no delay. I don't know exactly when this was introduced. I reproduced it in trusty, in saucy, and in precise with the lts-saucy kernel, but not in raring. The patch series fixing this was merged recently and will be in 3.14: http://article.gmane.org/gmane.linux.nfs/60081 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4b9a445e3eeb8bd9278b1ae51c1b3a651e370cd6 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=89f842435c630f8426f414e6030bc2ffea0d6f81 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6aa23d76a7b549521a03b63b6d5b7880ea87eab7 Not part of the original series, but there are a few fixes on top of those: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3396f92f8be606ea485b0a82d4e7749a448b013b https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e2f0c83a9de331d9352185ca3642616c13127539 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=23e66ba97127ff3b064d4c6c5138aa34eafc492f Fedora and openSUSE have backported the fix to their 3.11-based kernels: http://pkgs.fedoraproject.org/cgit/kernel.git/commit/?h=f19id=6142d53dbe77431a4cc54f7ec80413b06f4ab182 http://pkgs.fedoraproject.org/cgit/kernel.git/commit/?h=f20id=a585abfb8457a34cf6a5e737aa5fd75dbfe2559b http://kernel.opensuse.org/cgit/kernel/commit/?h=openSUSE-13.1id=b2c797e218e1b2694f3e5d2d470bed6fb1b82009 http://kernel.opensuse.org/cgit/kernel/commit/?h=openSUSE-13.1id=b876acdd9ab5a5a81f7690ad0fc2f54ee83ac642 http://kernel.opensuse.org/cgit/kernel/commit/?h=openSUSE-13.1id=b4901f2cf60e02895336b8bde254c0eef07c09dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1277741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364125] Re: [Microsoft Corporation Surface Pro 2] suspend/resume failure
** Tags added: latest-bios-2.04.0950 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364125 Title: [Microsoft Corporation Surface Pro 2] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: Rebooted computer and the error came. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-12-generic 3.16.0-12.18 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petro 2166 F pulseaudio /dev/snd/controlC0: petro 2166 F pulseaudio Date: Sun Aug 31 21:11:53 2014 DuplicateSignature: suspend/resume:Microsoft Corporation Surface Pro 2:2.04.0950 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=be7a2161-a4f6-4318-a298-eea4a79e2c88 InstallationDate: Installed on 2014-08-28 (4 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140828) InterpreterPath: /usr/bin/python3.4 IwConfig: usb0 no wireless extensions. lono wireless extensions. MachineType: Microsoft Corporation Surface Pro 2 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-12-generic.efi.signed root=UUID=dd56f3c1-752b-4805-924e-6e1cb09a74bd 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.16.0-12-generic N/A linux-backports-modules-3.16.0-12-generic N/A linux-firmware 1.133 RfKill: SourcePackage: linux Title: [Microsoft Corporation Surface Pro 2] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.04.0950 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Surface Pro 2 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 11 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.04.0950:bd05/12/2014:svnMicrosoftCorporation:pnSurfacePro2:pvr1:rvnMicrosoftCorporation:rnSurfacePro2:rvr1:cvnMicrosoftCorporation:ct11:cvr1: dmi.product.name: Surface Pro 2 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364055] Re: [TOSHIBA Satellite P50-A] suspend/resume failure [non-free: nvidia]
Christopher, thank you for reporting this and helping make Ubuntu better. As per http://support.toshiba.com/support/modelHome?freeText=PSPMKU-04002Q an update to your BIOS is available (1.80). 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. As well, you don't have to create a new bug report. For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Once the BIOS is updated, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-1.80 ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364055 Title: [TOSHIBA Satellite P50-A] suspend/resume failure [non-free: nvidia] Status in “linux” package in Ubuntu: Incomplete Bug description: Error encountered at login splash screen Lubuntu 14.10 beta ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-11-generic 3.16.0-11.16 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: twowings 2209 F pulseaudio /dev/snd/controlC0: twowings 2209 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Mon Sep 1 06:36:26 2014 DuplicateSignature: suspend/resume:TOSHIBA Satellite P50-A:1.60 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=83be8256-f7f5-4a98-9d9f-c99fcc49cb57 InstallationDate: Installed on 2014-08-30 (1 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140826.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite P50-A ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-11-generic.efi.signed root=UUID=6e2bddc9-2cbc-41b4-bc73-191e517a0fb2 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.16.0-11-generic N/A linux-backports-modules-3.16.0-11-generic N/A linux-firmware 1.133 SourcePackage: linux StagingDrivers: keucr Title: [TOSHIBA Satellite P50-A] suspend/resume failure [non-free: nvidia] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/16/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.60 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10ST dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.60:bd01/16/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMKU-04002Q:rvnTOSHIBA:rnVG10ST:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Satellite P50-A dmi.product.version: PSPMKU-04002Q dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364333] 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/1364333 Title: Num lock LED doesn't light up while Num lock state is on. Status in “linux” package in Ubuntu: Incomplete Bug description: Num lock LED doesn't light up while Num lock state is on. If you press Num lock key, it will be put to off. And when you press it again, it will be on and LED will on. In some cases LED will be off again while Num keys will continue to work same as Num LED is enabled. All above is true for logon screen, for desktop and for terminals by ctrl+alt+F[1-6]. Found it on multiple computers with numpad. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihor 2025 F pulseaudio Date: Tue Sep 2 13:57:03 2014 HibernationDevice: RESUME=UUID=22d29605-7b7f-4743-9e46-c30f09460dfa InstallationDate: Installed on 2014-08-07 (26 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0a0a156d-8fc5-473d-bb54-ef83d71e2feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd11/30/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX: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/1364333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364333] Re: Num lock LED doesn't light up while Num lock state is on.
Ihor Romanyshyn, thank you for reporting this and helping make Ubuntu better. As per http://www.asus.com/Motherboards/M5A78LM_LX/HelpDesk_Download/ an update to your BIOS is available (1603). 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. As well, you don't have to create a new bug report. For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Once the BIOS is updated, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-1603 ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364333 Title: Num lock LED doesn't light up while Num lock state is on. Status in “linux” package in Ubuntu: Incomplete Bug description: Num lock LED doesn't light up while Num lock state is on. If you press Num lock key, it will be put to off. And when you press it again, it will be on and LED will on. In some cases LED will be off again while Num keys will continue to work same as Num LED is enabled. All above is true for logon screen, for desktop and for terminals by ctrl+alt+F[1-6]. Found it on multiple computers with numpad. This bug presents on v3.17-rc2-utopic too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihor 2025 F pulseaudio Date: Tue Sep 2 13:57:03 2014 HibernationDevice: RESUME=UUID=22d29605-7b7f-4743-9e46-c30f09460dfa InstallationDate: Installed on 2014-08-07 (26 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0a0a156d-8fc5-473d-bb54-ef83d71e2feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd11/30/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX: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/1364333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1363655] Re: [Asus P8Z77-V LX] suspend/resume failure [non-free: nvidia]
** Changed in: linux (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1363655 Title: [Asus P8Z77-V LX] suspend/resume failure [non-free: nvidia] Status in “linux” package in Ubuntu: Confirmed Bug description: I was trying to resume and my display never turned on. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-11-generic 3.16.0-11.16 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bdmurray 3864 F pulseaudio /dev/snd/controlC0: bdmurray 3864 F pulseaudio Date: Sun Aug 31 06:42:01 2014 DuplicateSignature: suspend/resume:System manufacturer System Product Name:2303 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=24b89185-eb5d-476c-ba6d-d71b78071334 InstallationDate: Installed on 2013-01-16 (591 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130116) InterpreterPath: /usr/bin/python3.4 MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 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.16.0-11-generic N/A linux-backports-modules-3.16.0-11-generic N/A linux-firmware 1.133 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: keucr SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: [System manufacturer System Product Name] suspend/resume failure [non-free: nvidia] UpgradeStatus: Upgraded to utopic on 2014-08-29 (1 days ago) UserGroups: dmi.bios.date: 12/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2303 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2303:bd12/05/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364148] Re: Backlight turned off since upgrade to 3.13.0-35
Gregory Lardiere, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested exactly shown as: kernel-fixed-upstream-3.17-rc3 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: latest-bios-1.15 ** Tags added: bisect-done ** Tags added: regression-update ** 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/1364148 Title: Backlight turned off since upgrade to 3.13.0-35 Status in “linux” package in Ubuntu: Incomplete Bug description: Since the upgrade to kernel 3.13.0-35 (from 3.13.0-34), the screen is very dark to the point it's unusable. Backlight seems completely turned off. Using the brightness keys doesn't help. It was working fine with 3.13.0-34. I found that the offending patch is drm/radeon: set default bl level to something reasonable. I reverted this patch and recompiled 3.13.0-35, and it solved the problem. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: greg 1962 F pulseaudio /dev/snd/pcmC2D0p: greg 1962 F...m pulseaudio /dev/snd/controlC1: greg 1962 F pulseaudio /dev/snd/controlC0: greg 1962 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=fa1d286a-7f50-4e1f-ae6c-9d48161e6c2d InstallationDate: Installed on 2010-07-03 (1521 days ago) InstallationMedia: Kubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427) MachineType: FUJITSU SIEMENS AMILO Xi 2550 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=7b8ed785-f136-4231-b6bd-5e175a9aef0b ro processor.max_cstate=1 radeon.dpm=1 quiet splash crashkernel=384M-:128M vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-08 (116 days ago) UserGroups: adm admin bluetooth cdrom dialout lpadmin plugdev sambashare vboxusers wireshark _MarkForUpload: True dmi.bios.date: 09/30/2008 dmi.bios.vendor: Phoenix dmi.bios.version: 1.15 dmi.board.name: F44 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 00030D005503B103 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnPhoenix:bvr1.15:bd09/30/2008:svnFUJITSUSIEMENS:pnAMILOXi2550:pvr:rvnFUJITSUSIEMENS:rnF44:rvr00030D005503B103:cvnFUJITSUSIEMENS:ct10:cvr: dmi.product.name: AMILO Xi 2550 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364148/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364333] Re: Num lock LED doesn't light up while Num lock state is on.
** Description changed: Num lock LED doesn't light up while Num lock state is on. If you press Num lock key, it will be put to off. And when you press it again, it will be on and LED will on. In some cases LED will be off again while Num keys will continue to work same as Num LED is enabled. All above is true for logon screen, for desktop and for terminals by ctrl+alt+F[1-6]. - Found it on multiple computers with numpad. + Found it on multiple computers with numpad. This bug presents on + v3.17-rc2-utopic too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ihor 2025 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ihor 2025 F pulseaudio Date: Tue Sep 2 13:57:03 2014 HibernationDevice: RESUME=UUID=22d29605-7b7f-4743-9e46-c30f09460dfa InstallationDate: Installed on 2014-08-07 (26 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: - eth0 no wireless extensions. - - lono wireless extensions. + eth0 no wireless extensions. + + lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0a0a156d-8fc5-473d-bb54-ef83d71e2feb ro quiet splash vt.handoff=7 PulseList: - Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied - No PulseAudio daemon running, or not running as session daemon. + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-3.13.0-35-generic N/A - linux-backports-modules-3.13.0-35-generic N/A - linux-firmware 1.127.5 + linux-restricted-modules-3.13.0-35-generic N/A + linux-backports-modules-3.13.0-35-generic N/A + linux-firmware 1.127.5 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd11/30/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX: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/1364333 Title: Num lock LED doesn't light up while Num lock state is on. Status in “linux” package in Ubuntu: Incomplete Bug description: Num lock LED doesn't light up while Num lock state is on. If you press Num lock key, it will be put to off. And when you press it again, it will be on and LED will on. In some cases LED will be off again while Num keys will continue to work same as Num LED is enabled. All above is true for logon screen, for desktop and for terminals by ctrl+alt+F[1-6]. Found it on multiple computers with numpad. This bug presents on v3.17-rc2-utopic too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihor 2025 F pulseaudio Date: Tue Sep 2 13:57:03 2014 HibernationDevice: RESUME=UUID=22d29605-7b7f-4743-9e46-c30f09460dfa InstallationDate: Installed on 2014-08-07 (26 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0a0a156d-8fc5-473d-bb54-ef83d71e2feb ro quiet splash vt.handoff=7 PulseList: Error:
[Kernel-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity
linux-image-3.16.0-12 booted O.K. several times this morning. I wouldn't know whether there is actually a fix for compiz or just whether the timing race of compiz/x is better. So as of 3.16.0-12 this problem has not reproduced over several boots. BTW, 3.17...rc3 still fails unless nomodeset. Waiting for rc4. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359299 Title: utopic 3.16.0-9 iso boots to desktop no unity Status in Unity: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “unity” package in Ubuntu: Confirmed Bug description: Intel Core 2 Duo 3 gHz 4 gb Lenovo Think Centre. Boots 3.16.0-6 amd64 fine, runs compiz 3D fine. Today's amd64 iso download, 20 August, boots to desktop cursor. No unity. Did ubuntu-bug from command line on the booted iso, saved report. Booted 3.10.0-6 and ran ubuntu-bug apport on the saved file. Planet Ubuntu asked for results on 3.16.0-9 so this is my result. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-9-generic 3.16.0-9.14 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CasperVersion: 1.341 Date: Wed Aug 20 16:57:57 2014 LiveMediaBuild: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140820) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/utopic-desktop-amd64.iso noprompt noeject SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1359299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1327670] Re: WiFi connects to AP, but doesn't work. Setting rate to auto fixes it.
Hi, this bug also affects me. The work around above (set rate to auto) lets me work around it but is a pain to run every time I login. I have a Packard Bell Easy Note TM laptop with an in-place upgrade of Ubuntu 14.04, kernel 3.13.0-35, and am using the rtl8192se driver. My wifi AP is a Virgin Media (a UK ISP) re-badged Netgear device. I've used this laptop and router for about 6 years without problems, including Ubuntu 10 and onwards, and there are plenty of other devices (Windows/iOS/Android) in the house that also work fine. The fault started on upgrade to 14.04. Can this fault please be prioritised, until I found this bug report my only other option was to stop using Ubuntu and move to a different distro... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327670 Title: WiFi connects to AP, but doesn't work. Setting rate to auto fixes it. Status in “linux” package in Ubuntu: Confirmed Bug description: Fresh 14.04 install on a Packard Bell Notebook. WiFi device: 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192SE Wireless LAN Controller (rev 10) rtl8192se kernel module If connecting to my home WiFi, it shows as connected, but there is no connectivity. I can't ping anything, not even the access point itself, althought DHCP settings are retrieved correctly. iwconfig reports a rate stuck at 1Mb/s, although link quality is 70/70 and Signal level -28dBm. If I set the rate to auto with iwconfig wlan0 rate auto, it switches to 54 Mb/s (max the AP supports) and everything seems to work fine (I used it for few hours now, downloaded few 100 MB, mostly Ubuntu packages). When connecting to an Android Hotspot, the problem doesn't occur, thus it seems to be AP dependent. Difference in dmesg between connecting to the bad and the good AP: When connecting to the bad one, it additionally shows this 2 lines: [10961.059621] rtl8192se :02:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP [10961.059626] rtl8192se :02:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP Don't know if that's related. I've been connected to this AP with a lot of devices (mainly mobile) without any issues. The AP is a Linksys WRT54GL with Tomato 1.28 firmware. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-firmware 1.127.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Sun Jun 8 02:20:45 2014 Dependencies: InstallationDate: Installed on 2014-06-07 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aida 1849 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=3b1b248a-c783-4dca-a900-1c7aa27863e5 InstallationDate: Installed on 2014-06-07 (11 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0402:9665 ALi Corp. Gateway Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Packard Bell EasyNote TK85 Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=ab640bfe-9bc6-4e2d-a1a9-747545b2e0db ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 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-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/24/2010 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: EasyNote TK85 dmi.board.vendor: Packard Bell dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version:
[Kernel-packages] [Bug 1364333] Re: Num lock LED doesn't light up while Num lock state is on.
** Description changed: Num lock LED doesn't light up while Num lock state is on. If you press Num lock key, it will be put to off. And when you press it again, it will be on and LED will on. In some cases LED will be off again while Num keys will continue to work same as Num LED is enabled. All above is true for logon screen, for desktop and for terminals by ctrl+alt+F[1-6]. Found it on multiple computers with numpad. This bug presents on - v3.17-rc2-utopic too. + v3.17-rc2-utopic and v3.17-rc3-utopic too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihor 2025 F pulseaudio Date: Tue Sep 2 13:57:03 2014 HibernationDevice: RESUME=UUID=22d29605-7b7f-4743-9e46-c30f09460dfa InstallationDate: Installed on 2014-08-07 (26 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0a0a156d-8fc5-473d-bb54-ef83d71e2feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd11/30/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX: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/1364333 Title: Num lock LED doesn't light up while Num lock state is on. Status in “linux” package in Ubuntu: Incomplete Bug description: Num lock LED doesn't light up while Num lock state is on. If you press Num lock key, it will be put to off. And when you press it again, it will be on and LED will on. In some cases LED will be off again while Num keys will continue to work same as Num LED is enabled. All above is true for logon screen, for desktop and for terminals by ctrl+alt+F[1-6]. Found it on multiple computers with numpad. This bug presents on v3.17-rc2-utopic and v3.17-rc3-utopic too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihor 2025 F pulseaudio Date: Tue Sep 2 13:57:03 2014 HibernationDevice: RESUME=UUID=22d29605-7b7f-4743-9e46-c30f09460dfa InstallationDate: Installed on 2014-08-07 (26 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0a0a156d-8fc5-473d-bb54-ef83d71e2feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor:
[Kernel-packages] [Bug 1274444] Update Released
The verification of the Stable Release Update for rsyslog has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/127 Title: echo string to /dev/kmsg fails to appear on /var/log/syslog Status in “linux” package in Ubuntu: Invalid Status in “rsyslog” package in Ubuntu: Fix Released Status in “rsyslog” source package in Precise: Fix Released Status in “rsyslog” source package in Trusty: Fix Released Bug description: [Impact] In the precise 3.2 series kernel writing strings to /dev/kmsg appears and dmesg and /var/log/syslog, in 3.5 series kernel this does not happen properly even with the equivalent userspace packages. This is because the default facility number in the kernel has changed from 0 to 1 for user-space generated kmsg entries. Because of this; rsyslog (or any affected sysloggers) need to accept non-kernel facility numbers. This change was introduced by this commit (in the linux kernel): 7ff9554bb578ba02166071d2d487b7fc7d860d62 [Test Case] Run the following script as root: #!/bin/bash STRING=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | head -c 32) # /var/log/syslog # this isn't necessary echo $STRING /dev/kmsg sleep 5 grep $STRING /var/log/syslog # This should return 0. [Regression Potential] Any scripts that rely on syslog output may finally see output produced by packages like init/systemd show up in syslog. This changes the default rsyslog.conf file settings but isn't a code change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1274444] Re: echo string to /dev/kmsg fails to appear on /var/log/syslog
This bug was fixed in the package rsyslog - 7.4.4-1ubuntu2.1 --- rsyslog (7.4.4-1ubuntu2.1) trusty; urgency=medium * Enable non-kernel facility klog messages. (LP: #127) -- Chris J Arges chris.j.ar...@ubuntu.com Tue, 19 Aug 2014 14:51:26 -0500 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/127 Title: echo string to /dev/kmsg fails to appear on /var/log/syslog Status in “linux” package in Ubuntu: Invalid Status in “rsyslog” package in Ubuntu: Fix Released Status in “rsyslog” source package in Precise: Fix Released Status in “rsyslog” source package in Trusty: Fix Released Bug description: [Impact] In the precise 3.2 series kernel writing strings to /dev/kmsg appears and dmesg and /var/log/syslog, in 3.5 series kernel this does not happen properly even with the equivalent userspace packages. This is because the default facility number in the kernel has changed from 0 to 1 for user-space generated kmsg entries. Because of this; rsyslog (or any affected sysloggers) need to accept non-kernel facility numbers. This change was introduced by this commit (in the linux kernel): 7ff9554bb578ba02166071d2d487b7fc7d860d62 [Test Case] Run the following script as root: #!/bin/bash STRING=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | head -c 32) # /var/log/syslog # this isn't necessary echo $STRING /dev/kmsg sleep 5 grep $STRING /var/log/syslog # This should return 0. [Regression Potential] Any scripts that rely on syslog output may finally see output produced by packages like init/systemd show up in syslog. This changes the default rsyslog.conf file settings but isn't a code change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1274444] Re: echo string to /dev/kmsg fails to appear on /var/log/syslog
This bug was fixed in the package rsyslog - 5.8.6-1ubuntu8.7 --- rsyslog (5.8.6-1ubuntu8.7) precise; urgency=medium * Enable non-kernel facility klog messages. (LP: #127) -- Chris J Arges chris.j.ar...@ubuntu.com Tue, 19 Aug 2014 15:00:53 -0500 ** Changed in: rsyslog (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: rsyslog (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/127 Title: echo string to /dev/kmsg fails to appear on /var/log/syslog Status in “linux” package in Ubuntu: Invalid Status in “rsyslog” package in Ubuntu: Fix Released Status in “rsyslog” source package in Precise: Fix Released Status in “rsyslog” source package in Trusty: Fix Released Bug description: [Impact] In the precise 3.2 series kernel writing strings to /dev/kmsg appears and dmesg and /var/log/syslog, in 3.5 series kernel this does not happen properly even with the equivalent userspace packages. This is because the default facility number in the kernel has changed from 0 to 1 for user-space generated kmsg entries. Because of this; rsyslog (or any affected sysloggers) need to accept non-kernel facility numbers. This change was introduced by this commit (in the linux kernel): 7ff9554bb578ba02166071d2d487b7fc7d860d62 [Test Case] Run the following script as root: #!/bin/bash STRING=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | head -c 32) # /var/log/syslog # this isn't necessary echo $STRING /dev/kmsg sleep 5 grep $STRING /var/log/syslog # This should return 0. [Regression Potential] Any scripts that rely on syslog output may finally see output produced by packages like init/systemd show up in syslog. This changes the default rsyslog.conf file settings but isn't a code change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1354975] Re: iwlwifi Intel 7260 Wifi disconnects
** Also affects: unitylinux Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1354975 Title: iwlwifi Intel 7260 Wifi disconnects Status in Unity Linux: New Status in “linux-firmware” package in Ubuntu: Incomplete Bug description: I experience frequent disconnects and auth issues, never more than 30 minutes without a disconnect. Sometimes dozens of disconnects in a few minutes. This happens with the default 7260-8 firmware. Tried replacing the -8 with -9 ucode. Failed to load due to API version. This loaded the -7 driver which seems to be more stable. Tested against 2.4ghz APs (Apple, Netgear, Linksys). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 2577 F pulseaudio /dev/snd/controlC1: steve 2577 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 10 17:49:06 2014 HibernationDevice: RESUME=UUID=374a0c1c-4ac2-456b-a67e-9ea54fe11fe6 InstallationDate: Installed on 2013-12-28 (225 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 12-9Q33 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=58deb355-7a09-440b-ade2-69a84fd74460 ro ipv6.disable=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-06 (35 days ago) dmi.bios.date: 05/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/06/2013:svnDellInc.:pnXPS12-9Q33:pvrA00:rvnDellInc.:rnXPS12-9Q33:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/unitylinux/+bug/1354975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1189721] Re: Ralink RT3290 needs bluetooth driver
Is there an update on this issue? I have been facing the same issue and can't use any bluetooth devices. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1189721 Title: Ralink RT3290 needs bluetooth driver Status in The Linux Kernel: New Status in “linux” package in Ubuntu: Confirmed Bug description: As of Raring Ubuntu has a wifi driver for the RT3290 that works out of the box. It still does not have bluetooth support. This thread in the Ubuntu forums links to a driver that is claimed to work: http://ubuntuforums.org/showthread.php?t=2115570 --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graeme 2412 F pulseaudio CRDA: country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70 InstallationDate: Installed on 2013-05-17 (144 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Hewlett-Packard HP ProBook 4540s MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/06/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.32 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4540s dmi.product.version: A1018C1100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1189721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364333] Re: Num lock LED doesn't light up while Num lock state is on.
Christopher, thank you! I'm updated BIOS and it works fine! ** 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/1364333 Title: Num lock LED doesn't light up while Num lock state is on. Status in “linux” package in Ubuntu: Invalid Bug description: Num lock LED doesn't light up while Num lock state is on. If you press Num lock key, it will be put to off. And when you press it again, it will be on and LED will on. In some cases LED will be off again while Num keys will continue to work same as Num LED is enabled. All above is true for logon screen, for desktop and for terminals by ctrl+alt+F[1-6]. Found it on multiple computers with numpad. This bug presents on v3.17-rc2-utopic and v3.17-rc3-utopic too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihor 2025 F pulseaudio Date: Tue Sep 2 13:57:03 2014 HibernationDevice: RESUME=UUID=22d29605-7b7f-4743-9e46-c30f09460dfa InstallationDate: Installed on 2014-08-07 (26 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0a0a156d-8fc5-473d-bb54-ef83d71e2feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd11/30/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX: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/1364333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364333] Re: Num lock LED doesn't light up while Num lock state is on.
sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date 1603 11/05/2013 ** Tags removed: bios-outdated-1603 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364333 Title: Num lock LED doesn't light up while Num lock state is on. Status in “linux” package in Ubuntu: Confirmed Bug description: Num lock LED doesn't light up while Num lock state is on. If you press Num lock key, it will be put to off. And when you press it again, it will be on and LED will on. In some cases LED will be off again while Num keys will continue to work same as Num LED is enabled. All above is true for logon screen, for desktop and for terminals by ctrl+alt+F[1-6]. Found it on multiple computers with numpad. This bug presents on v3.17-rc2-utopic and v3.17-rc3-utopic too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihor 2025 F pulseaudio Date: Tue Sep 2 13:57:03 2014 HibernationDevice: RESUME=UUID=22d29605-7b7f-4743-9e46-c30f09460dfa InstallationDate: Installed on 2014-08-07 (26 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0a0a156d-8fc5-473d-bb54-ef83d71e2feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd11/30/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX: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/1364333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1363661] Re: no proprietary driver
Hello I've updated my bios with an ISO image to version 572. After reboot, I wento to the update manager to check but the only additional drivers proposed are those given by the PPA (see my fist post). yann@yann-desktop:~$ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date [sudo] password for yann: DPP3510J.86A.0572.2009.0715.2346 07/15/2009 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1363661 Title: no proprietary driver Status in “linux” package in Ubuntu: Incomplete Bug description: Hello I've switched from ubuntu 14.04 32 bits to 14.04 64 bits. In the additional driver tab of my system parametrers, the usual nvidia proprietary driver which wera appearing in the 32 bits version does not appears in the 64 bits version. As a workaround, I've installed this PPA : https://launchpad.net/~xorg-edgers/+archive/ubuntu/ppa but the system refuses to add the updates after this PPa is installed because it says the updates have not been verifiedI have not have this problem on 32 bits... --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1604c98d-ec9c-4c56-b311-87ad841b3f2c InstallationDate: Installed on 2014-08-31 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=2145f258-16d8-4edf-b411-7958d94b8fd4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DG33BU dmi.board.vendor: Intel Corporation dmi.board.version: AAD79951-406 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDG33BU:rvrAAD79951-406:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364333] Re: Num lock LED doesn't light up while Num lock state is on.
Oops, still remain the same problem. Num lock LED switched off suddenly but numpad is working as Num lock is on. ** Changed in: linux (Ubuntu) Status: Invalid = 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/1364333 Title: Num lock LED doesn't light up while Num lock state is on. Status in “linux” package in Ubuntu: Confirmed Bug description: Num lock LED doesn't light up while Num lock state is on. If you press Num lock key, it will be put to off. And when you press it again, it will be on and LED will on. In some cases LED will be off again while Num keys will continue to work same as Num LED is enabled. All above is true for logon screen, for desktop and for terminals by ctrl+alt+F[1-6]. Found it on multiple computers with numpad. This bug presents on v3.17-rc2-utopic and v3.17-rc3-utopic too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihor 2025 F pulseaudio Date: Tue Sep 2 13:57:03 2014 HibernationDevice: RESUME=UUID=22d29605-7b7f-4743-9e46-c30f09460dfa InstallationDate: Installed on 2014-08-07 (26 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0a0a156d-8fc5-473d-bb54-ef83d71e2feb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd11/30/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX: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/1364333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364427] [NEW] kexeced kernel hung
You have been subscribed to a public bug: ---Problem Description--- kexec is not working with kernel 3.16 or later. The root cause is missing patch in the kexec-tools package provided with Ubuntu 14.04 and 14.10. ---uname output--- Linux qemu 3.16.0-10-generic #15-Ubuntu SMP Thu Aug 21 16:32:31 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Steps to Reproduce--- On a 14.10 guest or host, run : $ sudo kexec -l /boot/vmlinux --initrd=/boot/initrd.img-3.16.0-10-generic $ sudo kexec -e The kexeced kernel will hang here : [ 300.002862] Starting new kernel I'm in purgatory The root cause is the following kexec-tools's patch missing: 2ca220389d21 kexec/ppc64: move to device tree version 17 This patch is required to kexec kernel 3.16 and later. Among this patch, the following upstream pactches should be added to the current package : 335bad77fb07 kexec/ppc64: disabling exception handling when building the purgato 90853885a859 ppc64/purgatory: Device tree values should be read/stored in Big En In addition the following incoming patch should be applied : ppc64/kdump: Fix ELF header endianess (http://lists.infradead.org/pipermail/kexec/2014-July/012247.html) Another option to consider is to move to kexec-tools 2.0.7, and to apply the missing patches Is it possible to get this patches also applied to the kexec-tools shipped with 14.04 ? ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: New ** Tags: architecture-ppc64le bugnameltc-115353 severity-critical targetmilestone-inin1410 -- kexeced kernel hung https://bugs.launchpad.net/bugs/1364427 You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364427] Re: kexeced kernel hung
** Package changed: ubuntu = kexec-tools (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1364427 Title: kexeced kernel hung Status in “kexec-tools” package in Ubuntu: New Bug description: ---Problem Description--- kexec is not working with kernel 3.16 or later. The root cause is missing patch in the kexec-tools package provided with Ubuntu 14.04 and 14.10. ---uname output--- Linux qemu 3.16.0-10-generic #15-Ubuntu SMP Thu Aug 21 16:32:31 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Steps to Reproduce--- On a 14.10 guest or host, run : $ sudo kexec -l /boot/vmlinux --initrd=/boot/initrd.img-3.16.0-10-generic $ sudo kexec -e The kexeced kernel will hang here : [ 300.002862] Starting new kernel I'm in purgatory The root cause is the following kexec-tools's patch missing: 2ca220389d21 kexec/ppc64: move to device tree version 17 This patch is required to kexec kernel 3.16 and later. Among this patch, the following upstream pactches should be added to the current package : 335bad77fb07 kexec/ppc64: disabling exception handling when building the purgato 90853885a859 ppc64/purgatory: Device tree values should be read/stored in Big En In addition the following incoming patch should be applied : ppc64/kdump: Fix ELF header endianess (http://lists.infradead.org/pipermail/kexec/2014-July/012247.html) Another option to consider is to move to kexec-tools 2.0.7, and to apply the missing patches Is it possible to get this patches also applied to the kexec-tools shipped with 14.04 ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1364427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364008] Re: Cannot pair with Altavoz Vivaldi Bluetooth speaker
Note that this speaker is from the BQ store, so should work as a priority ** Changed in: bluez (Ubuntu) Importance: High = Critical -- 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/1364008 Title: Cannot pair with Altavoz Vivaldi Bluetooth speaker Status in “bluez” package in Ubuntu: New Bug description: krillin ubuntu-rtm/14.09-proposed build 9. bluez 4.101-0ubuntu19 armhf SUMMARY: Cannot pair with Avrha Altavoz Vivaldi Bluetooth speaker: http://www.bqreaders.com/gb/accessories-aquaris.html Device is Bluetooth v2.0 +EDR [Note that the other listed Bluetooth Speaker Strauss does work] STEPS: 1) Turn on speaker so that it is in pairing mode 2) On krillin attempt to pair with the speaker EXPECTED RESULT: The pairing should be successful ACTUAL RESULT: In the list of Bluetooth devices a greyed-out speaker icon is listed with the name '...' The name is never resolved and it is not possible to start a pairing request with the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1364008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1317602] Re: package linux-image-3.13.0-24-generic 3.13.0-24.46 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
I ran into this issue (or one very similar), and it seems that uninstalling ksplice (via apt-get remove ksplice ksplice-uptrack) resolved it for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1317602 Title: package linux-image-3.13.0-24-generic 3.13.0-24.46 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in “linux” package in Ubuntu: Confirmed Bug description: while installing an update ProblemType: Package 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 i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw' Date: Thu May 8 19:11:23 2014 DuplicateSignature: package:linux-image-3.13.0-24-generic:3.13.0-24.46:subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=56bc50ae-9d55-42ad-9ff5-6ece8d748bb3 InstallationDate: Installed on 2014-05-03 (5 days ago) InstallationMedia: It Lsusb: Bus 001 Device 002: ID 0cde:0006 Z-Com XG-300 802.11b Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: FUJITSU SIEMENS AMILO L Series ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/it--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.13.0-24-generic 3.13.0-24.46 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 11/25/2005 dmi.bios.vendor: FUJITSU SIEMENS dmi.bios.version: 1.0G-0031-0812 dmi.board.name: AMILO L7300 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: N/A dmi.modalias: dmi:bvnFUJITSUSIEMENS:bvr1.0G-0031-0812:bd11/25/2005:svnFUJITSUSIEMENS:pnAMILOLSeries:pvr:rvnFUJITSUSIEMENS:rnAMILOL7300:rvrNone:cvnFUJITSUSIEMENS:ct10:cvrN/A: dmi.product.name: AMILO L Series dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359146] Re: Kernel crash when mounting bcache on a vm with virtio
@tom-leiming I've tested this patch and I am able to mount a bcache device on top of virtio disks without hangs or the original BUG_ON on startup. Please add my 'Tested-By' in the patch upstream. Thanks, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359146 Title: Kernel crash when mounting bcache on a vm with virtio Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Fix Released Bug description: bcache used in a virtual machine: If you create a bcache device with caching device and backing device on virtio disks, it will let you do your work until you mount it where it crashes the virtual machine (virtual machine is utopic, host is trusty). For example: if your backing device is /dev/vdb, and your caching device is /dev/vdc: sudo make-bcache -B /dev/vdc -C /dev/vdb --writeback is ok mkfs.ext4 /dev/bcache0 -L bcache-test is ok but mount /dev/bcache0 /media/bcache make it crash, if I remember well one time I had a few seconds before crash, but I don't have any log files. qemu-system-x86 is version 2.0.0+dfsg-2ubuntu1.2 Re-installing, and using IDE virtual interface seems to create and mount the bcache device is ok. After bcache created an mounted successfully with IDE interfaces, switching to SATA, SCSI, and USB with booting and mounting seemed ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1356948] Comment bridged from LTC Bugzilla
--- Comment From wenxi...@us.ibm.com 2014-09-02 14:40 EDT--- petitboot patch is zImage.epapr in http://ausgsa.ibm.com/~wenxiong/public/. Thanks, Wendy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1356948 Title: ISST-KTE:PowerNV:UBUNTU14.10: Shiner Adapter ethernet port does not come up Status in “linux” package in Ubuntu: Triaged Bug description: ---Problem Description--- When trying to bring up an ethernet port on a Shiner Network adapter, the terminal outputs the following: root@podkvm:~# ifconfig eth7 up [ 3126.678507] bnx2x: [bnx2x_attn_int_deasserted2:4099(eth7)]CFC hw attention 0x2 [ 3126.678586] bnx2x: [bnx2x_attn_int_deasserted2:4102(eth7)]FATAL error from CFC [ 3136.698592] bnx2x: [bnx2x_state_wait:308(eth7)]timeout waiting for state 1 [ 3136.698678] bnx2x: [bnx2x_setup_queue:8625(eth7)]Queue(0) SETUP failed [ 3136.698688] bnx2x: [bnx2x_nic_load:2721(eth7)]Setup leading failed! SIOCSIFFLAGS: Device or resource busy modules loaded: root@podkvm:~# lsmod Module Size Used by rtc_generic 2711 0 powernv_rng 3244 0 ses10118 0 enclosure 12767 1 ses mlx4_en 118002 0 bnx2x 920334 0 lpfc 836357 0 mlx4_core 311074 1 mlx4_en mdio6270 1 bnx2x libcrc32c 1995 1 bnx2x ipr 142194 2 be2net144413 0 scsi_transport_fc 80636 1 lpfc scsi_tgt 18399 1 scsi_transport_fc vxlan 48609 2 be2net,mlx4_en ---uname output--- Linux podkvm 3.15.0-6-generic #11-Ubuntu SMP Thu Jun 12 00:40:49 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- System firmware: 1427A Machine Type = 8247-22L I can get the interface up on petitboot and on a 3.10 kernel used for PowerKVM installer. I can't do it for Ubuntu 14.04 kernel, based on 3.13. I can reproduce the same thing with a 3.13 kernel on another PowerNV system. However, it works on a PCI passthrough environment on PowerKVM, with both 14.04 kernel and 14.10. So, this is specific to PowerNV. I will try upstream kernel versions and see if it's possible to find a culprit. I collected this with msglevel options on the driver. The driver specific option SP, timer, interrupt, link, ifup, and probe. Cascardo. However, it works on a PCI passthrough environment on PowerKVM, with both 14.04 kernel and 14.10. So, this is specific to PowerNV. I will try upstream kernel versions and see if it's possible to find a culprit. I couldn't find Thadeu's kernel. I built the newer kernel + bnx2x driver from upstream, still saw the same failure. I will look into more. Thanks, Wendy Shiner info: root@podkvm:~# ethtool -i eth7 driver: bnx2x version: 1.78.19-0 firmware-version: bc 7.10.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1356948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350443] Re: Not able to load the kdump kernel and generate the dump in Ubuntu14.10 on Non virtualised system
** Changed in: makedumpfile (Ubuntu) Status: New = Confirmed ** Changed in: makedumpfile (Ubuntu) Assignee: (unassigned) = Taco Screen team (taco-screen-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1350443 Title: Not able to load the kdump kernel and generate the dump in Ubuntu14.10 on Non virtualised system Status in “makedumpfile” package in Ubuntu: Confirmed Bug description: ---Problem Description--- Not able to load the kdump kernel and save the vmcore in /var/crash/ ---uname output--- Linux lep8d 3.16.0-5-generic #10-Ubuntu SMP Mon Jul 21 16:17:25 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Steps to Reproduce--- Install a P8 machine with Ubuntu 14.10 in Non virtualised environment. Installed all the kexec-tools and kdump-tools packages. Then trying to start the kdump service and loading. root@lep8d:~# /etc/init.d/kdump-tools start Starting kdump-tools: Cannot open `/boot/vmlinuz-3.16.0-5-generic': No such file or directory * failed to load kdump kernel root@lep8d:~# echo $? 0 root@lep8d:~# kdump-config load Cannot open `/boot/vmlinuz-3.16.0-5-generic': No such file or directory * failed to load kdump kernel root@lep8d:~# ls -l /boot/vmlinux-3.16.0-5-generic -rw--- 1 root root 20712936 Jul 21 22:02 /boot/vmlinux-3.16.0-5-generic root@lep8d:~# root@lep8d:~# dpkg -l | grep kexec ii kexec-tools1:2.0.6-0ubuntu2 ppc64el tools to support fast kexec reboots ii pxe-kexec 0.2.4-3 ppc64el Fetch PXE configuration file and netboot using kexec root@lep8d:~# dpkg -l | grep kdump ii kdump-tools1.5.6-2 all scripts and tools for automating kdump (Linux crash dumps) root@lep8d:~# cat /sys/kernel/kexec_crash_loaded 0 root@lep8d:~# kdump-config show USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: current state:Not ready to kdump kexec command: no kexec command recorded root@lep8d:~# kdump-config status current state : Not ready to kdump Tried to manually trigger a crash as below: root@lep8d:~# sysctl -w kernel.sysrq=1 kernel.sysrq = 1 root@lep8d:~# cat /proc/sys/kernel/sysrq 1 root@lep8d:~# echo c /proc/sysrq-trigger [ 4252.703681] SysRq : Trigger a crash [ 4252.703773] Unable to handle kernel paging request for data at address 0x [ 4252.703779] Faulting instruction address: 0xc05b88f4 [ 4252.703807] Oops: Kernel access of bad area, sig: 11 [#1] [ 4252.703852] SMP NR_CPUS=2048 NUMA PowerNV [ 4252.703899] Modules linked in: dm_multipath scsi_dh shpchp powernv_rng uio_pdrv_genirq uio rtc_generic binfmt_misc parport_pc ppdev lp parport ses enclosure lpfc scsi_transport_fc ipr scsi_tgt [ 4252.704162] CPU: 76 PID: 4635 Comm: bash Not tainted 3.16.0-5-generic #10-Ubuntu [ 4252.704230] task: c01fdf7cbeb0 ti: c01fdf8e4000 task.ti: c01fdf8e4000 [ 4252.704298] NIP: c05b88f4 LR: c05b997c CTR: c05b88c0 [ 4252.704365] REGS: c01fdf8e79d0 TRAP: 0300 Not tainted (3.16.0-5-generic) [ 4252.704432] MSR: 90009033 SF,HV,EE,ME,IR,DR,RI,LE CR: 28422824 XER: 2000 [ 4252.704602] CFAR: c0009358 DAR: DSISR: 4200 SOFTE: 1 GPR00: c05b997c c01fdf8e7c50 c1346498 0063 GPR04: c00014305db0 c00014316618 00018010 c14ff2d8 GPR08: c0dd6498 0001 00018010 GPR12: c05b88c0 c7e50a00 010016f94818 1016e008 GPR16: 1013ad70 010016f9c958 1016fed0 1016e008 GPR20: 100c31e0 10171fc8 1016f840 GPR24: 1014d9b0 1014d0b0 0004 GPR28: c127eee8 0063 c125d6a0 c127f2a8 [ 4252.705502] NIP [c05b88f4] sysrq_handle_crash+0x34/0x50 [ 4252.705558] LR [c05b997c] __handle_sysrq+0xec/0x270 [ 4252.705604] Call Trace: [ 4252.705631] [c01fdf8e7c50] [c018e3f0] __acct_update_integrals+0x80/0x170 (unreliable) [ 4252.705722] [c01fdf8e7c70] [c05b997c] __handle_sysrq+0xec/0x270 [ 4252.705790] [c01fdf8e7d10] [c05ba138] write_sysrq_trigger+0x78/0xa0 [ 4252.705871] [c01fdf8e7d40] [c03141f0] proc_reg_write+0xb0/0x110 [ 4252.705940] [c01fdf8e7d90] [c028c07c] vfs_write+0xdc/0x260 [ 4252.706007] [c01fdf8e7de0] [c028ce1c] SyS_write+0x6c/0x110 [ 4252.706076] [c01fdf8e7e30]
[Kernel-packages] [Bug 1364478] [NEW] Cant update ubuntu 14.04
Public bug reported: I have a Dell xps l501x laptop and i have ubuntu on it. Its all fine but when i upgrade the 13.10 to 14.04 all was great, then when i updated it, the kernel had change and when i launch ubuntu with grub it says KERNEL PANIC, and i cant do anything so i installed again the 14.04 ubuntu and i cant update because of the kernel panic. 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 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jose 2616 F pulseaudio /dev/snd/controlC0: jose 2616 F pulseaudio /dev/snd/pcmC0D0p: jose 2616 F...m pulseaudio CurrentDesktop: GNOME Date: Tue Sep 2 10:54:27 2014 HibernationDevice: RESUME=UUID=d4032e13-fbe6-4b38-81a8-2d2f7dd78f38 InstallationDate: Installed on 2014-07-30 (34 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. XPS L501X ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=553625c4-a70e-457d-bdcd-2b638949581e 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd03/29/2011:svnDellInc.:pnXPSL501X:pvrA07:rvnDellInc.:rn:rvrA07:cvnDellInc.:ct8:cvrA07: dmi.product.name: XPS L501X dmi.product.version: A07 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1364478 Title: Cant update ubuntu 14.04 Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell xps l501x laptop and i have ubuntu on it. Its all fine but when i upgrade the 13.10 to 14.04 all was great, then when i updated it, the kernel had change and when i launch ubuntu with grub it says KERNEL PANIC, and i cant do anything so i installed again the 14.04 ubuntu and i cant update because of the kernel panic. 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 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jose 2616 F pulseaudio /dev/snd/controlC0: jose 2616 F pulseaudio /dev/snd/pcmC0D0p: jose 2616 F...m pulseaudio CurrentDesktop: GNOME Date: Tue Sep 2 10:54:27 2014 HibernationDevice: RESUME=UUID=d4032e13-fbe6-4b38-81a8-2d2f7dd78f38 InstallationDate: Installed on 2014-07-30 (34 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. XPS L501X ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=553625c4-a70e-457d-bdcd-2b638949581e 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd03/29/2011:svnDellInc.:pnXPSL501X:pvrA07:rvnDellInc.:rn:rvrA07:cvnDellInc.:ct8:cvrA07: dmi.product.name: XPS L501X dmi.product.version: A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364478] 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/1364478 Title: Cant update ubuntu 14.04 Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell xps l501x laptop and i have ubuntu on it. Its all fine but when i upgrade the 13.10 to 14.04 all was great, then when i updated it, the kernel had change and when i launch ubuntu with grub it says KERNEL PANIC, and i cant do anything so i installed again the 14.04 ubuntu and i cant update because of the kernel panic. 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 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jose 2616 F pulseaudio /dev/snd/controlC0: jose 2616 F pulseaudio /dev/snd/pcmC0D0p: jose 2616 F...m pulseaudio CurrentDesktop: GNOME Date: Tue Sep 2 10:54:27 2014 HibernationDevice: RESUME=UUID=d4032e13-fbe6-4b38-81a8-2d2f7dd78f38 InstallationDate: Installed on 2014-07-30 (34 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. XPS L501X ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=553625c4-a70e-457d-bdcd-2b638949581e 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd03/29/2011:svnDellInc.:pnXPSL501X:pvrA07:rvnDellInc.:rn:rvrA07:cvnDellInc.:ct8:cvrA07: dmi.product.name: XPS L501X dmi.product.version: A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1032874] Re: Mount command on extended partition hangs forever during install
** Changed in: linux (Ubuntu Precise) Assignee: Chris J Arges (arges) = (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1032874 Title: Mount command on extended partition hangs forever during install Status in “debian-installer-utils” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Triaged Status in “debian-installer-utils” source package in Precise: New Status in “linux” source package in Precise: Triaged Bug description: Re-installing Precise with kernels 3.2.0-26 or 3.2.0-27 from the precise-updates repo hangs forever when searching for install media on systems that do this from check-missing-firmware. The underlying problem is a hanging mount command. The problem doesn't exist using 3.2.0-23 in the precise repo. When the installer detects that it needs to load some missing firmware, it tries to mount every available partition as '/media'. If the hard drive is already partitioned and has an extended partition, the installer will try to mount the extended partition and hang indefinitely. Sending SIGKILL to the mount command does nothing. Eventually, the kernel will start logging 'INFO: task mount:3559 blocked for more than 120 seconds.' messages. To reproduce, on ThinkPad T420s (or most other laptops with wireless) that already has Ubuntu installed with an extended partition (for example, sda2): 1. Boot the kernel/initramfs for the network installer at /ubuntu/dists/precise/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/ 2. Select language and keyboard options 3. Installer hangs forever 4. Alt-F2 to another terminal 5. Run ps, see stalled mount command, like 'mount -tauto /dev/sda2 /media' On 3.2.0-23, the mount command will return immediately with an error, as expected (since mounting and extended partition doesn't make sense). Regardless of what hardware is used, running the mount command on an extended partition always stalls. The hardware only makes a difference in deciding whether the mount command is called during install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer-utils/+bug/1032874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 669641] Re: systemtap fails to discover installed debug modules
** No longer affects: linux (Ubuntu Lucid)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/669641
Title:
systemtap fails to discover installed debug modules
Status in Linaro Ubuntu Engineering Builds:
Fix Released
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Precise:
Fix Released
Status in “linux” source package in Quantal:
Fix Released
Status in “linux-2.6” package in Debian:
Fix Released
Bug description:
== Precise SRU Justification ==
Impact: When using systemtap with Ubuntu kernels, the proper debug
modules cannot be automatically discovered.
== Fix ==
This fix allows for the build system to insert the .gnu_debuglink
sections in the .ko files pointing to the full unstripped .ko in
/usr/lib/debug/.. in the dbgsym ddebs. In addition there are checks to
ensure the debug symbol actually exists before creating the
.gnu_debuglink section.
== Testcase ==
1) Install systemtap.
2) Run stap -l 'module(serio_raw).function(*)'
3) This should show list all the probe points for that module.
--
Binary package hint: systemtap
Even if the proper debug symbols are installed:
# stap -l 'kernel.function(acpi_*)' | sort
will succeed
and this will fail.
# stap -l 'module(ohci1394).function(*)' | sort
Now there's no shortage of blogs and wikis on how to work
around this but no one has seemingly ever investigated the root
cause. If one were to run this through strace you would find
the following.
open(/usr/lib/debug/.build-id/3b/6eb5a0f22ba2bc92c3c3f1fcb14fe7f31f3807.debug,
O_RDONLY) = -1 ENOENT (No such file or directory)
open(/lib/modules/2.6.32-25-generic/kernel/drivers/ieee1394/ohci1394.ko.debug,
O_RDONLY) = -1 ENOENT (No such file or directory)
open(/lib/modules/2.6.32-25-generic/kernel/drivers/ieee1394/.debug/ohci1394.ko.debug,
O_RDONLY) = -1 ENOENT (No such file or directory)
open(/usr/lib/debug/lib/modules/2.6.32-25-generic/kernel/drivers/ieee1394/ohci1394.ko.debug,
O_RDONLY) = -1 ENOENT (No such file or directory)
open(/lib/modules/2.6.32-25-generic/kernel/drivers/ieee1394/build/ohci1394.ko.debug,
O_RDONLY) = -1 ENOENT (No such file or directory)
Note that the path is correct, it's the name of the KO that stap is expecting
that is wrong,
Kernel debug symbols provided by Ubuntu are unstripped yet maintain the .ko
extension,
systemtap (actually libelf/elfutils) is expecting the filename to be
module.ko.debug.
After discussing this on #systemtap on Freenode, the following script was
proposed to
generate a symlink tree, by build id, in /usr/lib/debug, with the proper
extension. This
completely solves the issue, and is also of benefit to things like gdb and
oprofile.
#!/bin/sh
for file in `find /usr/lib/debug -name '*.ko' -print`
do
buildid=`eu-readelf -n $file| grep Build.ID: | awk '{print $3}'`
dir=`echo $buildid | cut -c1-2`
fn=`echo $buildid | cut -c3-`
mkdir -p /usr/lib/debug/.build-id/$dir
ln -s $file /usr/lib/debug/.build-id/$dir/$fn
ln -s $file /usr/lib/debug/.build-id/$dir/${fn}.debug
done
If we could integrate this into the ddeb postinstall script, the problem would
be solved.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-ubuntu/+bug/669641/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1000913] Re: K43SA hangs on suspend
** Changed in: linux (Ubuntu Precise)
Assignee: Chris J Arges (arges) = (unassigned)
** Changed in: linux (Ubuntu Precise)
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/1000913
Title:
K43SA hangs on suspend
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Precise:
Incomplete
Bug description:
Hi
K43SA hangs while suspending with
Linux K43SA 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
The hdd light comes up, but system never goes into suspend and seems
busy writing to disk.
-
Suspending system by force works
$ cat suspend.c
#include unistd.h
#include sys/io.h
#include stdint.h
#include stdio.h
/* PM1 Sleep types */
#define SLP_ON 0
#define SLP_ST_PCLK 1
#define SLP_S3 5
#define SLP_S5 6
#define SLP_SOFT_OFF 7
#define PM1a 0x0404
//cat /proc/ioports | grep PM1a_CNT_BLK
//0404-0405 : ACPI PM1a_CNT_BLK
int main(int argc, char **argv)
{
uint16_t val;
if (ioperm(PM1a, 2, 1) 0) {
printf(Cannot access port %d\n, PM1a);
exit(0);
}
val = inw(PM1a);
val = ~(7 10); /* Clear SLP_TYPE */
//val |= (SLP_SOFT_OFF 10); /* Soft power off */
//val |= (SLP_S5 10); /* Soft power off */
val |= (SLP_S3 10); /* Soft power off */
val |= (1 13); /* Trigger SLP_EN */
outw(val, PM1a);
}
-
Using pmdebug the below o/p is seen (
git://kernel.ubuntu.com/cking/pmdebug.git )
[pmdebug/locatehang] $ cat log
Looking for function that matches hash from the Magic Number from the kernel
log.
Magic: 12:64:42 maps to hash: a3d2c
Hash matches: acpi_hw_write_pm1_control() (address: 81383f8b)
The kernel probably wrote to the southbridge the magic to put the machine
into suspend or hibernate and then the machine hung. Generally this means
that the machine did not wake up and get back to the kernel resume
successfully
which normally indicates a BIOS issue.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ritesh 2559 F pulseaudio
/dev/snd/controlC0: ritesh 2559 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdff0 irq 56'
Mixer name : 'Realtek ALC269VB'
Components : 'HDA:10ec0269,10431b63,00100100'
Controls : 18
Simple ctrls : 10
Card1.Amixer.info:
Card hw:1 'Generic'/'HD-Audio Generic at 0xdfe4 irq 57'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 6
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=8358ef03-1e13-4598-8bd9-4d206a7efec2
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64
(20120201.2)
MachineType: ASUSTeK Computer Inc. K43SA
Package: linux (not installed)
ProcEnviron:
LANGUAGE=en_IN:en
TERM=xterm
PATH=(custom, no user)
LANG=en_IN
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.4.0-2-generic
root=/dev/mapper/K43SA-root ro security=selinux selinux=1
ProcVersionSignature: Ubuntu 3.4.0-2.6-generic 3.4.0-rc7
RelatedPackageVersions:
linux-restricted-modules-3.4.0-2-generic N/A
linux-backports-modules-3.4.0-2-generic N/A
linux-firmware 1.80
SourcePackage: linux
StagingDrivers: rts5139 mei
Tags: quantal running-unity staging quantal staging
Uname: Linux 3.4.0-2-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
dmi.bios.date: 08/18/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K43SA.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K43SA
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:
[Kernel-packages] [Bug 1270237] Re: prevent the conntrack table from filling up in the kernel
This patch was also released in: Ubuntu-lts-3.8.0-37.53 ** Changed in: linux-lts-raring (Ubuntu Precise) Assignee: Chris J Arges (arges) = (unassigned) ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Won't Fix = Fix Committed ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1270237 Title: prevent the conntrack table from filling up in the kernel 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 Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Bug description: [Impact] When running a server for an extended amount of time the conntrack table can fill up. Here is the netfilter discussion: http://www.spinics.net/lists/netfilter-devel/msg26759.html [Fix] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6547a221871f139cc56328a38105d47c14874cbe Present in 3.11 [Test Case] From the patch: When loose tracking is enabled (default), non-syn packets cause creation of new conntracks in established state with default timeout for established state (5 days). This causes the table to fill up with UNREPLIED when the 'new ack' packet happened to be the last-ack of a previous, already timed-out connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1153769] Re: perf stat problem - cycles event is not supported
Closing. Thanks ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1153769 Title: perf stat problem - cycles event is not supported Status in “linux” package in Ubuntu: Fix Released Bug description: When running with the latest Natty kernel 2.6.38-16.67, perf stat doesn't work. For example: # perf stat -e cycles ls Error: cycles event is not supported. Fatal: Not all events could be opened The following relevant messages are found in dmesg: [ 0.494517] Performance Events: PEBS fmt1+, Westmere events, Broken BIOS detected, using software events only. [ 0.505676] [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 38d is 330) This is related to this issue: http://h2.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03265132lang=encc=ustaskId=101prodSeriesId=4132829prodTypeId=3709945 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1153769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1173206] Re: Installation of 13.04 hangs at configuring bcmwl-kernel-source
This bug is confirmed on multiple forum posts and my personal experience. ** Changed in: bcmwl (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1173206 Title: Installation of 13.04 hangs at configuring bcmwl-kernel-source Status in “bcmwl” package in Ubuntu: Confirmed Bug description: Hello, I am trying to install 13.04 on an Acer Aspire 5024 laptop. Installation hangs at Configuring bcmwl-kernel-source and button Skip is greyed put so that I can't use it. From dmesg output I can also see two Call trace and these two lines that could be related to the problem: wl driver 6.20.155.1 (r326264) failed with code 21 Kernel BUG at f969b9da. Any hints on how to proceed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1173206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362443] Re: CVE-2014-3601
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1362443 Title: CVE-2014-3601 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: New 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: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: [kvm: invalid parameter passing in kvm_iommu_map_pages()] Break-Fix: fcd95807fb61e67d602610e7ff7129ed769e9fee 350b8bdd689cd2ab2c67c8a86a0be86cfa0751a7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1325941] Re: CVE-2014-3917
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1325941 Title: CVE-2014-3917 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-lts-trusty” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-lts-trusty” 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 Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-lts-trusty” 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 Committed 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-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-trusty” source package in Saucy: Invalid Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-lts-trusty” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-lts-trusty” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: kernel/auditsc.c in the Linux kernel through 3.14.5, when CONFIG_AUDITSYSCALL is enabled with certain syscall rules, allows local users to obtain potentially sensitive single-bit values from kernel memory or cause a denial of service (OOPS) via a large value of a syscall number. Break-Fix: - a3c54931199565930d6d84f4c3456f6440aefd41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325941/+subscriptions
[Kernel-packages] [Bug 1356318] Re: CVE-2014-5206
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Invalid = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1356318 Title: CVE-2014-5206 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Invalid Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The do_remount function in fs/namespace.c in the Linux kernel through 3.16.1 does not maintain the MNT_LOCK_READONLY bit across a remount of a bind mount, which allows local users to bypass an intended read-only restriction and defeat certain sandbox protection mechanisms via a mount -o remount command within a user namespace. Break-Fix: 0c55cfc4166d9a0f38de779bd4d75a90afbe7734 a6138db815df5ee542d848318e5dae681590fccd Break-Fix: 0c55cfc4166d9a0f38de779bd4d75a90afbe7734 07b645589dcda8b7a5249e096fece2a67556f0f4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1356318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339297] Re: CVE-2014-4653
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1339297 Title: CVE-2014-4653 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 does not ensure possession of a read/write lock, which allows local users to cause a denial of service (use-after-free) and obtain sensitive information from kernel memory by leveraging /dev/snd/controlCX access. Break-Fix: - fd9f26e4eca5d08a27d12c0933fceef76ed9663d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339306] Re: CVE-2014-4656
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1339306 Title: CVE-2014-4656 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflict function. Break-Fix: - ac902c112d90a89e59916f751c2745f4dbdbb4bd Break-Fix: - 883a1d49f0d77d30012f114b2e19fc141beb3e8e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339304] Re: CVE-2014-4655
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1339304 Title: CVE-2014-4655 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The snd_ctl_elem_add function in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 does not properly maintain the user_ctl_count value, which allows local users to cause a denial of service (integer overflow and limit bypass) by leveraging /dev/snd/controlCX access for a large number of SNDRV_CTL_IOCTL_ELEM_REPLACE ioctl calls. Break-Fix: - 82262a46627bebb0febcc26664746c25cef08563 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339303] Re: CVE-2014-4654
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1339303 Title: CVE-2014-4654 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The snd_ctl_elem_add function in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 does not check authorization for SNDRV_CTL_IOCTL_ELEM_REPLACE commands, which allows local users to remove kernel controls and cause a denial of service (use-after-free and system crash) by leveraging /dev/snd/controlCX access for an ioctl call. Break-Fix: - 82262a46627bebb0febcc26664746c25cef08563 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1336135] Re: CVE-2014-4667
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1336135 Title: CVE-2014-4667 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The sctp_association_free function in net/sctp/associola.c in the Linux kernel before 3.15.2 does not properly manage a certain backlog value, which allows remote attackers to cause a denial of service (socket outage) via a crafted SCTP packet. Break-Fix: de76e695a5ce19c121ba7e246b45f258be678a75 d3217b15a19a4779c39b212358a5c71d725822ee To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1336135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339294] Re: CVE-2014-4652
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1339294 Title: CVE-2014-4652 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: Race condition in the tlv handler functionality in the snd_ctl_elem_user_tlv function in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allows local users to obtain sensitive information from kernel memory by leveraging /dev/snd/controlCX access. Break-Fix: - 07f4d9d74a04aa7c72c5dae0ef97565f28f17b92 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333612] Re: CVE-2014-4027
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1333612 Title: CVE-2014-4027 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix 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 Released Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed 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” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The rd_build_device_space function in drivers/target/target_core_rd.c in the Linux kernel before 3.14 does not properly initialize a certain data structure, which allows local users to obtain sensitive information from ramdisk_mcp memory by leveraging access to a SCSI initiator. Break-Fix: c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 4442dc8a92b8f9ad8ee9e7f8438f4c04c03a22dc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333617] Re: CVE-2014-4171
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1333617 Title: CVE-2014-4171 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: 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: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed 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” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: mm/shmem.c in the Linux kernel through 3.15.1 does not properly implement the interaction between range notification and hole punching, which allows local users to cause a denial of service (i_mutex hold) by using the mmap system call to access a hole, as demonstrated by interfering with intended shmem activity by blocking completion of (1) an MADV_REMOVE madvise call or (2) an FALLOC_FL_PUNCH_HOLE fallocate call. Break-Fix: - f00cdc6df7d7cfcabb5b740911e6788cb0802bdb Break-Fix: - 8e205f779d1443a94b5ae81aa359cb535dd3021e Break-Fix: - b1a366500bd537b50c3aad26dc7df083ec03a448 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity
Regret that kernel 3.16.0-12 does NOT reliably resolve this problem. See post #30 above. I get exactly the same result with the -12 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359299 Title: utopic 3.16.0-9 iso boots to desktop no unity Status in Unity: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “unity” package in Ubuntu: Confirmed Bug description: Intel Core 2 Duo 3 gHz 4 gb Lenovo Think Centre. Boots 3.16.0-6 amd64 fine, runs compiz 3D fine. Today's amd64 iso download, 20 August, boots to desktop cursor. No unity. Did ubuntu-bug from command line on the booted iso, saved report. Booted 3.10.0-6 and ran ubuntu-bug apport on the saved file. Planet Ubuntu asked for results on 3.16.0-9 so this is my result. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-9-generic 3.16.0-9.14 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CasperVersion: 1.341 Date: Wed Aug 20 16:57:57 2014 LiveMediaBuild: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140820) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/utopic-desktop-amd64.iso noprompt noeject SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1359299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355196] Re: compiz fails with intel_do_flush_locked failed: Invalid argument
verified broken in 3.16.0-12-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1355196 Title: compiz fails with intel_do_flush_locked failed: Invalid argument Status in “linux” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: Recent upgrade and reboot/re-login left me with a generally unusable compiz/unity. On login, the desktop icons move back and forth several times, I believe this correlates with ~/.xesssion-errors 'unity main process ended' messages like: upstart: unity7 main process (7477) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (7910) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (7939) terminated with status 1 Further investigation showed that compiz was failing to start. Attempting to start it by hand shows: intel_do_flush_locked failed: Invalid argument Those same messages appear in ~/.cache/upstart/unity7.log. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140731.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,commands,mousepoll,grid,move,place,imgpng,session,vpswitch,resize,regex,gnomecompat,unitymtgrabhandles,wall,resizeinfo,animation,workarounds,fade,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Aug 11 09:53:07 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (1027 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2013-05-20 (448 days ago) --- .tmp.unity.support.test.0: ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: smoser 4190 F pulseaudio CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,commands,mousepoll,grid,move,place,imgpng,session,vpswitch,resize,regex,gnomecompat,unitymtgrabhandles,wall,resizeinfo,animation,workarounds,fade,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: 2013-05-20 08:14:41,880 DEBUG openCache() DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] InstallationDate: Installed on 2011-10-19 (1034 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: LENOVO 7417CTO Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=f9832678-e9fb-41c5-8edb-5edd5200ed0a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 Tags: utopic utopic ubuntu regression reproducible compiz-0.9 Uname: Linux 3.16.0-6-generic x86_64 UpgradeStatus: Upgraded to utopic on 2013-05-20 (456 days ago) UserGroups: adm admin cdrom dialout fuse kvm libvirtd lpadmin plugdev sambashare sbuild _MarkForUpload: True dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 7417CTO 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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn7417CTO:pvrThinkPadT400:rvnLENOVO:rn7417CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7417CTO dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.5-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.5-1ubuntu2
[Kernel-packages] [Bug 1362261] Re: CONFIG_DMA_CMA causes ttm performance problems/hangs
** Changed in: linux (Ubuntu Trusty) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362261 Title: CONFIG_DMA_CMA causes ttm performance problems/hangs Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Confirmed Status in “linux” source package in Utopic: Triaged Bug description: The x86_64 kernels have CONFIG_DMA_CMA enabled, this causes extrem hangs of at least the RADEON driver full discussion is here: http://lists.freedesktop.org/archives/dri- devel/2014-August/065842.html ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aschultz 2224 F pulseaudio /dev/snd/controlC1: aschultz 2224 F pulseaudio CurrentDesktop: XFCE Date: Wed Aug 27 18:57:02 2014 HibernationDevice: RESUME=UUID=702fb398-84d9-4e93-9b4b-980323bf2d53 MachineType: Hewlett-Packard HP EliteBook 8560w ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-10-generic root=UUID=9a10044a-a505-4049-b794-a0ab87709daa ro rootflags=subvol=@ quiet splash init=/lib/systemd/systemd vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-07-21 (37 days ago) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362448] Re: CVE-2014-5472
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1362448 Title: CVE-2014-5472 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: New 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: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: [unbound recursion in ISOFS - causes a deadlock in the mount process in inode_wait] Break-Fix: - 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362447] Re: CVE-2014-5471
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1362447 Title: CVE-2014-5471 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: New 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: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: [unbound recursion in ISOFS - crashes / reboots a kernel due to kernel stack overflow / corruption] Break-Fix: - 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1356323] Re: CVE-2014-5207
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Invalid = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1356323 Title: CVE-2014-5207 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Invalid Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: fs/namespace.c in the Linux kernel through 3.16.1 does not properly restrict clearing MNT_NODEV, MNT_NOSUID, and MNT_NOEXEC and changing MNT_ATIME_MASK during a remount of a bind mount, which allows local users to gain privileges, interfere with backups and auditing on systems that had atime enabled, or cause a denial of service (excessive filesystem updating) on systems that had atime disabled via a mount -o remount command within a user namespace. Break-Fix: 0c55cfc4166d9a0f38de779bd4d75a90afbe7734 9566d6742852c527bf5af38af5cbb878dad75705 Break-Fix: 0c55cfc4166d9a0f38de779bd4d75a90afbe7734 ffbc6f0ead47fa5a1dc9642b0331cb75c20a640e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1356323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364511] [NEW] CVE-2013-2595
*** This bug is a security vulnerability *** Public security bug reported: The device-initialization functionality in the MSM camera driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, enables MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap interface, which allows attackers to gain privileges via a crafted application. ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Utopic) Importance:
[Kernel-packages] [Bug 1364511] Re: CVE-2013-2595
CVE-2013-2595 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New = Invalid ** Description changed: - Placeholder + The device-initialization functionality in the MSM camera driver for the + Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) + Android contributions for MSM devices and other products, enables + MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap + interface, which allows attackers to gain privileges via a crafted + application. ** Changed in: linux-armadaxp (Ubuntu Precise) Importance: Undecided = Medium ** Changed in:
[Kernel-packages] [Bug 1364516] [NEW] CVE-2013-2597
*** This bug is a security vulnerability *** Public security bug reported: Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that leverages /dev/msm_acdb access and provides a large size value in an ioctl argument. ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu
[Kernel-packages] [Bug 1364516] Re: CVE-2013-2597
CVE-2013-2597 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New = Invalid ** Description changed: - Placeholder + Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c + in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in + Qualcomm Innovation Center (QuIC) Android contributions for MSM devices + and other products, allows attackers to gain privileges via an + application that leverages /dev/msm_acdb access and provides a large + size value in an ioctl argument. ** Changed in: linux-armadaxp (Ubuntu Precise) Importance: Undecided =
[Kernel-packages] [Bug 468025]
332996
http://coloringme.com/wp-content/youtube_schet.php
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/468025
Title:
[SAMSUNG ELECTRONICS CO., LTD. Q210/P210] late resume failure [non-
free: nvidia]
Status in “linux” package in Ubuntu:
Invalid
Bug description:
My laptop freezes while hibernating. After I rebooted Ubuntu asked me
to send crash report.
ProblemType: KernelOops
Annotation: This occured during a previous hibernate and prevented it from
resuming properly. The resume processing hung very near the end and will have
appeared to have completed normally.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: msemenkin 2346 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfc20 irq 22'
Mixer name : 'Nvidia MCP78 HDMI'
Components : 'HDA:10ec0262,144dc041,00100202
HDA:11c11040,2118144d,00100200 HDA:10de0003,10de0101,0010'
Controls : 27
Simple ctrls : 16
Date: Sun Nov 1 10:21:11 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: late resume
HibernationDevice: RESUME=UUID=efd393d0-1545-4008-96be-aca6f8215c04
InterpreterPath: /usr/bin/python2.6
MachineType: SAMSUNG ELECTRONICS CO., LTD. Q210/P210
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic-pae 2.6.31-14.48
ProcCmdLine: root=UUID=a81c4f4a-1b9d-4256-b754-40b1c9a9fcd2 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
linux-backports-modules-2.6.31-14-generic N/A
linux-firmware 1.24
SourcePackage: linux
Tags: resume hibernate resume-late-hang
Title: [SAMSUNG ELECTRONICS CO., LTD. Q210/P210] late resume failure
[non-free: nvidia]
Uname: Linux 2.6.31-14-generic i686
UserGroups:
dmi.bios.date: 10/17/2008
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 08LE.MP00.20081017.KSY
dmi.board.name: Q210/P210
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr08LE.MP00.20081017.KSY:bd10/17/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnQ210/P210:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnQ210/P210:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: Q210/P210
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/468025/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1331513] Re: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720
Bernard, We still haven't been able to reproduce the bug, but if you have time, please see if the following patches applied to your kernel help: [PATCH net v5 1/4] tg3: Limit minimum tx queue wakeup threshold http://marc.info/?l=linux-netdevm=140934527707734w=2 [PATCH net v5 2/4] tg3: Fix tx_pending check for MAX_SKB_FRAGS http://marc.info/?l=linux-netdevm=140934526407725w=2 [PATCH net v5 3/4] tg3: Move tx queue stop logic to its own function http://marc.info/?l=linux-netdevm=140934525507718w=2 [PATCH net v5 4/4] tg3: Fix tx_pending checks for tg3_tso_bug http://marc.info/?l=linux-netdevm=140934524407695w=2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1331513 Title: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720 Status in The Dell PowerEdge project: Triaged Status in “linux” package in Ubuntu: Triaged Bug description: we have a problem with Dell PowerEdge machines, having the Broadcom 5720 chip. We have this problem on generation 12 systems, across different models (R420, R620), with several combinations of bios firmwares, lifecycle firmwares, etc... We see this on several versions of the linux kernel, ranging from 3.2.x up tot 3.11, with several versions of the tg3 driver, including a manually compiled latest version (3.133d) loaded in a 3.11. The latest machine, where we can reproduce the problem has Ubuntu Precise installed, but we also see this behaviour on Debian machines. We run Xen on it, running HVM hosts on it. Storage is handled over iSCSI (and it is the iSCSI interface we can trigger this bug on in a reproducible way, while we have the impression it also happens on other interfaces, but there we don't have a solid case where we have e reproducible setup). All this info actually points into the direction of the tg3 driver and/or hardware below it not handling certain datastreams or data patterns correctly, and finally crashing the system. It seems unrelated to the version of kernel running, xen-version running, amount of VM's running, firmwares and revisions running, etc... We have been trying to pinpoint this for over a year now, being unable to actually create a scenario where we could reproduce this. As of this week, we finally found a specific setup where we could trigger the error within a reasonable time. The error is triggered by running a certain VM on the Xen stack, and inside that VM, importing a mysqldump in a running mysql on that VM. The VM has it's traffic on an iSCSI volume, so this effectually generates a datastream over the eth1 interface of the machine. Within a short amount of time, the system will crash in 2 steps. We first see a timeout on the tg3 driver on the eth1 interface (dmesg output section attached). This sometimes repeats two or three times, and finally, step 2, the machine freezes and reboots. While debugging, we noticed that the bug goes away when we disable sg offloading with ethtool. If you need any additional info, feel free to ask. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.11.0-19-generic 3.11.0-19.33~precise1 ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Jun 18 16:36 seq crw-rw---T 1 root audio 116, 33 Jun 18 16:36 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.6 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: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Jun 18 16:47:27 2014 HibernationDevice: RESUME=UUID=f3577e02-64e3-4cab-b6e7-f30efa111565 InstallationMedia: Ubuntu-Server 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) MachineType: Dell Inc. PowerEdge R420 MarkForUpload: True PciMultimedia: ProcFB: ProcKernelCmdLine: placeholder root=UUID=bbc71780-90bf-4647-b579-e48d5d8c2bce ro vga=0x317 RelatedPackageVersions: linux-restricted-modules-3.11.0-19-generic N/A linux-backports-modules-3.11.0-19-generic N/A linux-firmware 1.79.12 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux-lts-saucy UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.2 dmi.board.name: 0JD6X3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.2:bd01/20/2014:svnDellInc.:pnPowerEdgeR420:pvr:rvnDellInc.:rn0JD6X3:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R420
[Kernel-packages] [Bug 1356948] Comment bridged from LTC Bugzilla
--- Comment From thad...@br.ibm.com 2014-09-02 17:39 EDT--- This is probably what is going upstream. http://marc.info/?l=linux-netdevm=140964868503853w=2 Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1356948 Title: ISST-KTE:PowerNV:UBUNTU14.10: Shiner Adapter ethernet port does not come up Status in “linux” package in Ubuntu: Triaged Bug description: ---Problem Description--- When trying to bring up an ethernet port on a Shiner Network adapter, the terminal outputs the following: root@podkvm:~# ifconfig eth7 up [ 3126.678507] bnx2x: [bnx2x_attn_int_deasserted2:4099(eth7)]CFC hw attention 0x2 [ 3126.678586] bnx2x: [bnx2x_attn_int_deasserted2:4102(eth7)]FATAL error from CFC [ 3136.698592] bnx2x: [bnx2x_state_wait:308(eth7)]timeout waiting for state 1 [ 3136.698678] bnx2x: [bnx2x_setup_queue:8625(eth7)]Queue(0) SETUP failed [ 3136.698688] bnx2x: [bnx2x_nic_load:2721(eth7)]Setup leading failed! SIOCSIFFLAGS: Device or resource busy modules loaded: root@podkvm:~# lsmod Module Size Used by rtc_generic 2711 0 powernv_rng 3244 0 ses10118 0 enclosure 12767 1 ses mlx4_en 118002 0 bnx2x 920334 0 lpfc 836357 0 mlx4_core 311074 1 mlx4_en mdio6270 1 bnx2x libcrc32c 1995 1 bnx2x ipr 142194 2 be2net144413 0 scsi_transport_fc 80636 1 lpfc scsi_tgt 18399 1 scsi_transport_fc vxlan 48609 2 be2net,mlx4_en ---uname output--- Linux podkvm 3.15.0-6-generic #11-Ubuntu SMP Thu Jun 12 00:40:49 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- System firmware: 1427A Machine Type = 8247-22L I can get the interface up on petitboot and on a 3.10 kernel used for PowerKVM installer. I can't do it for Ubuntu 14.04 kernel, based on 3.13. I can reproduce the same thing with a 3.13 kernel on another PowerNV system. However, it works on a PCI passthrough environment on PowerKVM, with both 14.04 kernel and 14.10. So, this is specific to PowerNV. I will try upstream kernel versions and see if it's possible to find a culprit. I collected this with msglevel options on the driver. The driver specific option SP, timer, interrupt, link, ifup, and probe. Cascardo. However, it works on a PCI passthrough environment on PowerKVM, with both 14.04 kernel and 14.10. So, this is specific to PowerNV. I will try upstream kernel versions and see if it's possible to find a culprit. I couldn't find Thadeu's kernel. I built the newer kernel + bnx2x driver from upstream, still saw the same failure. I will look into more. Thanks, Wendy Shiner info: root@podkvm:~# ethtool -i eth7 driver: bnx2x version: 1.78.19-0 firmware-version: bc 7.10.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1356948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1341925] Re: [Dell Inspiron 11 - 3147] System will hang on reboot / poweroff
May I request that this bug be upgraded to high priority. (P1) As this is not just a 3147 issue and it's not ACPI related. If you look here. https://www.google.com/?gws_rd=ssl#q=ubuntu+14.04+won%27t+shut+downspell=1 This is being reported in the forums and across the web in a wide variety of hardware. Right now the solution is fairly straight forward. Install something other than 14.04. This also is reported in but 1346269 as well With different HW. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346269 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/1341925 Title: [Dell Inspiron 11 - 3147] System will hang on reboot / poweroff Status in HWE Next Project: Incomplete Status in “linux” package in Ubuntu: Incomplete Bug description: CID: 201403-14888 Dell Inspiron 11 - 3147 While rebooting this system, it will stuck on the Ubuntu splash screen, caps lock LED will be not responding. This issue happens right after 14.04 installation with USB stick. If you press F1 right after the Ubuntu splash screen appears, you will see the message indicating it's now rebooting: * Deactivating swap... [OK] * Unmounting local filesystems... [OK] * Will now restart Steps: 1. Install 14.04, reboot to desktop 2. Try to reboot again Expect result: * System could be reboot normally Actual result: * It will stuck on the Ubuntu splash screen, the only way to power it off is to hold the power button Same thing could be apply to Shut Down * Unmounting local filesystems... [OK] * Will now halt 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/controlC0: ubuntu 1431 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Mon Jul 14 22:25:58 2014 HibernationDevice: RESUME=UUID=b30f45e9-6fc7-4aa0-adff-37e7c87c19cd InstallationDate: Installed on 2014-07-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 11 - 3147 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=cc246aa9-85c1-49ac-b06b-6c0f4e37dbea 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: 05/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 00K010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A01 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd05/05/2014:svnDellInc.:pnInspiron11-3147:pvr:rvnDellInc.:rn00K010:rvrD02:cvnDellInc.:ct8:cvrA01: dmi.product.name: Inspiron 11 - 3147 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1341925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364539] [NEW] [Dell Inc. Latitude E7440] suspend/resume failure
Public bug reported: If relevant, I docked the laptop between suspending and resuming. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-11-generic 3.16.0-11.16 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael2707 F pulseaudio /dev/snd/controlC0: michael2707 F pulseaudio Date: Tue Sep 2 19:58:10 2014 DuplicateSignature: suspend/resume:Dell Inc. Latitude E7440:A10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=6d651e5a-075d-4911-a5ce-6710f7246853 InstallationDate: Installed on 2014-08-01 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Latitude E7440 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-11-generic N/A linux-backports-modules-3.16.0-11-generic N/A linux-firmware 1.132 SourcePackage: linux Title: [Dell Inc. Latitude E7440] suspend/resume failure UpgradeStatus: Upgraded to utopic on 2014-08-28 (5 days ago) UserGroups: dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume suspend utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364539 Title: [Dell Inc. Latitude E7440] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: If relevant, I docked the laptop between suspending and resuming. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-11-generic 3.16.0-11.16 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael2707 F pulseaudio /dev/snd/controlC0: michael2707 F pulseaudio Date: Tue Sep 2 19:58:10 2014 DuplicateSignature: suspend/resume:Dell Inc. Latitude E7440:A10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=6d651e5a-075d-4911-a5ce-6710f7246853 InstallationDate: Installed on 2014-08-01 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Latitude E7440 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-11-generic N/A linux-backports-modules-3.16.0-11-generic N/A linux-firmware 1.132 SourcePackage: linux Title: [Dell Inc. Latitude E7440] suspend/resume failure UpgradeStatus: Upgraded to utopic on 2014-08-28 (5 days ago) UserGroups: dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364539/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1364539] Re: [Dell Inc. Latitude E7440] suspend/resume failure
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364539 Title: [Dell Inc. Latitude E7440] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: If relevant, I docked the laptop between suspending and resuming. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-11-generic 3.16.0-11.16 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael2707 F pulseaudio /dev/snd/controlC0: michael2707 F pulseaudio Date: Tue Sep 2 19:58:10 2014 DuplicateSignature: suspend/resume:Dell Inc. Latitude E7440:A10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=6d651e5a-075d-4911-a5ce-6710f7246853 InstallationDate: Installed on 2014-08-01 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Latitude E7440 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-11-generic N/A linux-backports-modules-3.16.0-11-generic N/A linux-firmware 1.132 SourcePackage: linux Title: [Dell Inc. Latitude E7440] suspend/resume failure UpgradeStatus: Upgraded to utopic on 2014-08-28 (5 days ago) UserGroups: dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364546] [NEW] [] suspend/resume failure [non-free: nvidia]
Public bug reported: Turned off when it should have resumed (keyboard pressed). ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-12-generic 3.16.0-12.17 ProcVersionSignature: Ubuntu 3.16.0-12.17-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: peter 2842 F pulseaudio /dev/snd/controlC2: peter 2842 F pulseaudio /dev/snd/controlC0: peter 2842 F pulseaudio /dev/snd/controlC1: peter 2842 F pulseaudio Date: Tue Sep 2 19:55:07 2014 DuplicateSignature: suspend/resume:To Be Filled By O.E.M. To Be Filled By O.E.M.:P2.90 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-08-16 (16 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140816) InterpreterPath: /usr/bin/python3.4 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-12-generic root=UUID=a01a8a8f-61c7-4592-a658-643a4dcf297d 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.16.0-12-generic N/A linux-backports-modules-3.16.0-12-generic N/A linux-firmware 1.133 RfKill: SourcePackage: linux Title: [To Be Filled By O.E.M. To Be Filled By O.E.M.] suspend/resume failure [non-free: nvidia] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock 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.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume suspend utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364546 Title: [] suspend/resume failure [non-free: nvidia] Status in “linux” package in Ubuntu: New Bug description: Turned off when it should have resumed (keyboard pressed). ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-12-generic 3.16.0-12.17 ProcVersionSignature: Ubuntu 3.16.0-12.17-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: peter 2842 F pulseaudio /dev/snd/controlC2: peter 2842 F pulseaudio /dev/snd/controlC0: peter 2842 F pulseaudio /dev/snd/controlC1: peter 2842 F pulseaudio Date: Tue Sep 2 19:55:07 2014 DuplicateSignature: suspend/resume:To Be Filled By O.E.M. To Be Filled By O.E.M.:P2.90 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-08-16 (16 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140816) InterpreterPath: /usr/bin/python3.4 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-12-generic root=UUID=a01a8a8f-61c7-4592-a658-643a4dcf297d 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.16.0-12-generic N/A linux-backports-modules-3.16.0-12-generic N/A linux-firmware 1.133 RfKill: SourcePackage: linux Title: [To Be Filled By O.E.M. To Be Filled By O.E.M.]
[Kernel-packages] [Bug 1364546] Re: [] suspend/resume failure [non-free: nvidia]
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1364546 Title: [] suspend/resume failure [non-free: nvidia] Status in “linux” package in Ubuntu: New Bug description: Turned off when it should have resumed (keyboard pressed). ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-12-generic 3.16.0-12.17 ProcVersionSignature: Ubuntu 3.16.0-12.17-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: peter 2842 F pulseaudio /dev/snd/controlC2: peter 2842 F pulseaudio /dev/snd/controlC0: peter 2842 F pulseaudio /dev/snd/controlC1: peter 2842 F pulseaudio Date: Tue Sep 2 19:55:07 2014 DuplicateSignature: suspend/resume:To Be Filled By O.E.M. To Be Filled By O.E.M.:P2.90 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-08-16 (16 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140816) InterpreterPath: /usr/bin/python3.4 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-12-generic root=UUID=a01a8a8f-61c7-4592-a658-643a4dcf297d 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.16.0-12-generic N/A linux-backports-modules-3.16.0-12-generic N/A linux-firmware 1.133 RfKill: SourcePackage: linux Title: [To Be Filled By O.E.M. To Be Filled By O.E.M.] suspend/resume failure [non-free: nvidia] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock 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.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364148] Re: Backlight turned off since upgrade to 3.13.0-35
The bug is not fixed in upstream kernel 3.17-rc3. I have tested the kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc3-utopic/ ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-3.17-rc3 ** 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/1364148 Title: Backlight turned off since upgrade to 3.13.0-35 Status in “linux” package in Ubuntu: Confirmed Bug description: Since the upgrade to kernel 3.13.0-35 (from 3.13.0-34), the screen is very dark to the point it's unusable. Backlight seems completely turned off. Using the brightness keys doesn't help. It was working fine with 3.13.0-34. I found that the offending patch is drm/radeon: set default bl level to something reasonable. I reverted this patch and recompiled 3.13.0-35, and it solved the problem. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: greg 1962 F pulseaudio /dev/snd/pcmC2D0p: greg 1962 F...m pulseaudio /dev/snd/controlC1: greg 1962 F pulseaudio /dev/snd/controlC0: greg 1962 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=fa1d286a-7f50-4e1f-ae6c-9d48161e6c2d InstallationDate: Installed on 2010-07-03 (1521 days ago) InstallationMedia: Kubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427) MachineType: FUJITSU SIEMENS AMILO Xi 2550 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=7b8ed785-f136-4231-b6bd-5e175a9aef0b ro processor.max_cstate=1 radeon.dpm=1 quiet splash crashkernel=384M-:128M vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-08 (116 days ago) UserGroups: adm admin bluetooth cdrom dialout lpadmin plugdev sambashare vboxusers wireshark _MarkForUpload: True dmi.bios.date: 09/30/2008 dmi.bios.vendor: Phoenix dmi.bios.version: 1.15 dmi.board.name: F44 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 00030D005503B103 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnPhoenix:bvr1.15:bd09/30/2008:svnFUJITSUSIEMENS:pnAMILOXi2550:pvr:rvnFUJITSUSIEMENS:rnF44:rvr00030D005503B103:cvnFUJITSUSIEMENS:ct10:cvr: dmi.product.name: AMILO Xi 2550 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364148/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350443] Re: Not able to load the kdump kernel and generate the dump in Ubuntu14.10 on Non virtualised system
Is this a dup of 1324544? If so, can you please mark as a duplicate. If not, what other patch, besides the one contained in 1324544 is needed for this bug report? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1350443 Title: Not able to load the kdump kernel and generate the dump in Ubuntu14.10 on Non virtualised system Status in “makedumpfile” package in Ubuntu: Confirmed Bug description: ---Problem Description--- Not able to load the kdump kernel and save the vmcore in /var/crash/ ---uname output--- Linux lep8d 3.16.0-5-generic #10-Ubuntu SMP Mon Jul 21 16:17:25 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Steps to Reproduce--- Install a P8 machine with Ubuntu 14.10 in Non virtualised environment. Installed all the kexec-tools and kdump-tools packages. Then trying to start the kdump service and loading. root@lep8d:~# /etc/init.d/kdump-tools start Starting kdump-tools: Cannot open `/boot/vmlinuz-3.16.0-5-generic': No such file or directory * failed to load kdump kernel root@lep8d:~# echo $? 0 root@lep8d:~# kdump-config load Cannot open `/boot/vmlinuz-3.16.0-5-generic': No such file or directory * failed to load kdump kernel root@lep8d:~# ls -l /boot/vmlinux-3.16.0-5-generic -rw--- 1 root root 20712936 Jul 21 22:02 /boot/vmlinux-3.16.0-5-generic root@lep8d:~# root@lep8d:~# dpkg -l | grep kexec ii kexec-tools1:2.0.6-0ubuntu2 ppc64el tools to support fast kexec reboots ii pxe-kexec 0.2.4-3 ppc64el Fetch PXE configuration file and netboot using kexec root@lep8d:~# dpkg -l | grep kdump ii kdump-tools1.5.6-2 all scripts and tools for automating kdump (Linux crash dumps) root@lep8d:~# cat /sys/kernel/kexec_crash_loaded 0 root@lep8d:~# kdump-config show USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: current state:Not ready to kdump kexec command: no kexec command recorded root@lep8d:~# kdump-config status current state : Not ready to kdump Tried to manually trigger a crash as below: root@lep8d:~# sysctl -w kernel.sysrq=1 kernel.sysrq = 1 root@lep8d:~# cat /proc/sys/kernel/sysrq 1 root@lep8d:~# echo c /proc/sysrq-trigger [ 4252.703681] SysRq : Trigger a crash [ 4252.703773] Unable to handle kernel paging request for data at address 0x [ 4252.703779] Faulting instruction address: 0xc05b88f4 [ 4252.703807] Oops: Kernel access of bad area, sig: 11 [#1] [ 4252.703852] SMP NR_CPUS=2048 NUMA PowerNV [ 4252.703899] Modules linked in: dm_multipath scsi_dh shpchp powernv_rng uio_pdrv_genirq uio rtc_generic binfmt_misc parport_pc ppdev lp parport ses enclosure lpfc scsi_transport_fc ipr scsi_tgt [ 4252.704162] CPU: 76 PID: 4635 Comm: bash Not tainted 3.16.0-5-generic #10-Ubuntu [ 4252.704230] task: c01fdf7cbeb0 ti: c01fdf8e4000 task.ti: c01fdf8e4000 [ 4252.704298] NIP: c05b88f4 LR: c05b997c CTR: c05b88c0 [ 4252.704365] REGS: c01fdf8e79d0 TRAP: 0300 Not tainted (3.16.0-5-generic) [ 4252.704432] MSR: 90009033 SF,HV,EE,ME,IR,DR,RI,LE CR: 28422824 XER: 2000 [ 4252.704602] CFAR: c0009358 DAR: DSISR: 4200 SOFTE: 1 GPR00: c05b997c c01fdf8e7c50 c1346498 0063 GPR04: c00014305db0 c00014316618 00018010 c14ff2d8 GPR08: c0dd6498 0001 00018010 GPR12: c05b88c0 c7e50a00 010016f94818 1016e008 GPR16: 1013ad70 010016f9c958 1016fed0 1016e008 GPR20: 100c31e0 10171fc8 1016f840 GPR24: 1014d9b0 1014d0b0 0004 GPR28: c127eee8 0063 c125d6a0 c127f2a8 [ 4252.705502] NIP [c05b88f4] sysrq_handle_crash+0x34/0x50 [ 4252.705558] LR [c05b997c] __handle_sysrq+0xec/0x270 [ 4252.705604] Call Trace: [ 4252.705631] [c01fdf8e7c50] [c018e3f0] __acct_update_integrals+0x80/0x170 (unreliable) [ 4252.705722] [c01fdf8e7c70] [c05b997c] __handle_sysrq+0xec/0x270 [ 4252.705790] [c01fdf8e7d10] [c05ba138] write_sysrq_trigger+0x78/0xa0 [ 4252.705871] [c01fdf8e7d40] [c03141f0] proc_reg_write+0xb0/0x110 [ 4252.705940] [c01fdf8e7d90] [c028c07c] vfs_write+0xdc/0x260 [ 4252.706007] [c01fdf8e7de0] [c028ce1c] SyS_write+0x6c/0x110 [ 4252.706076] [c01fdf8e7e30]
[Kernel-packages] [Bug 1363361] Re: Machine does not wake up to wakeonlan magic packets after shutdown -h now
I just tried reproducing this on a different machine with an Intel Corporation 82579LM Gigabit Network Connection (rev 04) nic, and it worked. My problematic machine has Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 05) which differs only in revision number. So hopefully this is quite a bit more isolated than I originally believed. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Dave Chiluk (chiluk) ** Changed in: linux-lts-trusty (Ubuntu) Assignee: (unassigned) = Dave Chiluk (chiluk) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1363361 Title: Machine does not wake up to wakeonlan magic packets after shutdown -h now Status in “linux” package in Ubuntu: Incomplete Status in “linux-lts-trusty” package in Ubuntu: New Bug description: How to reproduce with linux-lts-trusty 1. Enable wake on lan in bios 2. Boot *(however you want to boot) 3. Check that device supports wakeonlan ethtool eth0 # the Wake-on: setting should include g 4. shutdown -h now 5. wakeonlan -i ip address mac address in my case /usr/bin/wakeonlan -i 192.168.1.91 38:60:77:86:bf:71 6. Watch how little happens. I already did a mainline bisect, and the v3.8.12-raring works great v3.8.13-raring fails miserably. I'll try to continue the bisect. I also verified that full trusty also experiences this issue. I should check if upstream mainline is also seeing this. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62~precise1 ProcVersionSignature: User Name 3.13.0-35.62~precise1-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sat Aug 30 06:53:01 2014 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364539] 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/1364539 Title: [Dell Inc. Latitude E7440] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: If relevant, I docked the laptop between suspending and resuming. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-11-generic 3.16.0-11.16 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael2707 F pulseaudio /dev/snd/controlC0: michael2707 F pulseaudio Date: Tue Sep 2 19:58:10 2014 DuplicateSignature: suspend/resume:Dell Inc. Latitude E7440:A10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=6d651e5a-075d-4911-a5ce-6710f7246853 InstallationDate: Installed on 2014-08-01 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Latitude E7440 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-11-generic N/A linux-backports-modules-3.16.0-11-generic N/A linux-firmware 1.132 SourcePackage: linux Title: [Dell Inc. Latitude E7440] suspend/resume failure UpgradeStatus: Upgraded to utopic on 2014-08-28 (5 days ago) UserGroups: dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
