[Kernel-packages] [Bug 1485102] cavac (amd64) - tests ran: 71, failed: 68
tests ran: 71, failed: 68; http://kernel.ubuntu.com/testing/cavac__3.13.0-63.103__2015-08-18_06-30-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485102 Title: linux: 3.13.0-63.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-63.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:Friday, 14. August 2015 19:58 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457852] Re: [Dell Optiplex 9020] Shut down causes restart if USB3 enabled
Let's check with Dell and see whether we can get BIOS update...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1457852
Title:
[Dell Optiplex 9020] Shut down causes restart if USB3 enabled
Status in linux package in Ubuntu:
Triaged
Bug description:
Description:Ubuntu 14.04.2 LTS
Release:14.04
linux-image-3.13.0-49-generic version 3.13.0-49.83
I have a large number of Dell Optiplex 9020 machines, and when they
are asked to shutdown with e.g. shutdown -h now, they shut down
successfully and then approximately four seconds later they start up
again.
This problem only happens if the system's USB3 ports are enabled.
If I reinstate the code removed from xhci-pci.c in the diff.gz:
if (pdev-vendor == PCI_VENDOR_ID_INTEL
- (pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI ||
-pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI)) {
- /* Workaround for occasional spurious wakeups from S5 (or
-* any other sleep) on Haswell machines with LPT and LPT-LP
-* with the new Intel BIOS
-*/
- /* Limit the quirk to only known vendors, as this triggers
-* yet another BIOS bug on some other machines
-* https://bugzilla.kernel.org/show_bug.cgi?id=66171
-*/
- if (pdev-subsystem_vendor == PCI_VENDOR_ID_HP)
- xhci-quirks |= XHCI_SPURIOUS_WAKEUP;
+ pdev-device == PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI) {
+ xhci-quirks |= XHCI_SPURIOUS_REBOOT;
}
and add msleep(1000) to xhci.c as suggested at http://www.gossamer-
threads.com/lists/linux/kernel/1713011
...shutdown shuts the machine down as expected.
I attach the output of lspci -mnn.
(S)
---
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lightdm1990 F pulseaudio
/dev/snd/controlC0: lightdm1990 F pulseaudio
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/CayenneSys00-swap
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
MachineType: Dell Inc. OptiPlex 9020
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic
root=/dev/mapper/CayenneSys00-root ro biosdevname=0 quiet
ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
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-49-generic N/A
linux-backports-modules-3.13.0-49-generic N/A
linux-firmware 1.127.11
RfKill:
Tags: trusty
Uname: Linux 3.13.0-49-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: wheel
_MarkForUpload: True
dmi.bios.date: 11/20/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 06X1TJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 9020
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/1457852/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485113] onibi (amd64) - tests ran: 194, failed: 1
tests ran: 194, failed: 1; http://kernel.ubuntu.com/testing/onibi__3.19.0-27.29__2015-08-18_07-36-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485113 Title: linux: 3.19.0-27.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-27.29 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:Friday, 14. August 2015 20:50 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485184] ms10-35-mcdivittB0 (arm64) - tests ran: 153, failed: 5
tests ran: 153, failed: 5; http://kernel.ubuntu.com/testing/ms10-35-mcdivittB0__3.19.0-27.29~14.04.1__2015-08-18_08-27-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1485184 Title: linux-lts-vivid: 3.19.0-27.29~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: New Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-27.29~14.04.1 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:Saturday, 15. August 2015 07:02 UTC kernel-stable-master-bug:1485113 kernel-stable-Prepare-package-end:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-start:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:04 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1443888] Re: No sound on ThinkPad docking station
I guess that's not necessary any more. I got an update today with Kernel 3.19.0-26 and it works now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1443888 Title: No sound on ThinkPad docking station Status in linux package in Ubuntu: Incomplete Bug description: I have a Thinkpad T450s. The sound works normally unless it is plugged in to the docking station (a ThinkPad Ultra Dock). If speakers are plugged in to the dock, the internal speakers get disabled correctly, but the output of the docking station does not work. Speakers which are plugged in directly on the Laptop still work. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-13-generic 3.19.0-13.13 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1739 F pulseaudio /dev/snd/controlC1: daniel 1739 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 14 12:58:35 2015 HibernationDevice: RESUME=UUID=a67a91aa-8c15-4693-be37-7c177747bc39 InstallationDate: Installed on 2015-04-04 (9 days ago) InstallationMedia: It MachineType: LENOVO 20BWS03E00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic root=UUID=1643390a-82a8-405a-b938-057879ff3c9c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-13-generic N/A linux-backports-modules-3.19.0-13-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-04 (9 days ago) dmi.bios.date: 12/23/2014 dmi.bios.vendor: LENOVO dmi.bios.version: JBET41WW (1.06 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS03E00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET41WW(1.06):bd12/23/2014:svnLENOVO:pn20BWS03E00:pvrThinkPadT450s:rvnLENOVO:rn20BWS03E00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS03E00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485910] Re: ALSA: usb-audio: Don't attempt to get Lifecam HD-5000 sample rate
g 18 10:33:50 hostname kernel: usb 3-1.4: 3:1: cannot get freq at ep 0x82 Aug 18 10:33:55 hostname pulseaudio[1602]: [pulseaudio] alsa-util.c: Unable to set sw params: Permission denied Aug 18 10:33:55 hostname pulseaudio[1602]: [pulseaudio] alsa-source.c: Failed to set software parameters: Permission denied Aug 18 10:33:55 hostname kernel: usb 3-1.4: 3:1: cannot get freq at ep 0x82 Aug 18 10:33:55 hostname pulseaudio[1602]: [pulseaudio] main.c: Failed to acquire org.PulseAudio1: org.freedesktop.DBus.Error.Disconnected: Connection is closed Aug 18 10:33:55 hostname pulseaudio[2438]: [pulseaudio] pid.c: Daemon already running. Aug 18 10:33:55 hostname pulseaudio[2441]: [pulseaudio] pid.c: Daemon already running. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485910 Title: ALSA: usb-audio: Don't attempt to get Lifecam HD-5000 sample rate Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with my Lifecam HD-5000. I get timeouts an error- messages with snd-indicator. After searching online I found out there is a problem with the Lifecam not support getting the sample rate. The problem has been fixed upstream in the kernel-sources, see https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/sound/usb?h=linux-3.18.yid=b978d2f62a4c2385b2991a9c73eb70943706bb45 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daniel 2319 F pulseaudio /dev/snd/controlC1: daniel 2319 F pulseaudio /dev/snd/controlC0: daniel 2319 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 18 10:45:53 2015 HibernationDevice: RESUME=UUID=0538bdc9-e4d3-40db-9b4d-df007a205a15 InstallationDate: Installed on 2010-07-03 (1871 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=08269aa3-c22e-46ec-893c-cc8965ef213d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-24 (115 days ago) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: Z97 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.:bvrP1.50:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme4: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/1485910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485910] [NEW] ALSA: usb-audio: Don't attempt to get Lifecam HD-5000 sample rate
Public bug reported: I have a problem with my Lifecam HD-5000. I get timeouts an error- messages with snd-indicator. After searching online I found out there is a problem with the Lifecam not support getting the sample rate. The problem has been fixed upstream in the kernel-sources, see https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/sound/usb?h=linux-3.18.yid=b978d2f62a4c2385b2991a9c73eb70943706bb45 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daniel 2319 F pulseaudio /dev/snd/controlC1: daniel 2319 F pulseaudio /dev/snd/controlC0: daniel 2319 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 18 10:45:53 2015 HibernationDevice: RESUME=UUID=0538bdc9-e4d3-40db-9b4d-df007a205a15 InstallationDate: Installed on 2010-07-03 (1871 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=08269aa3-c22e-46ec-893c-cc8965ef213d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-24 (115 days ago) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: Z97 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.:bvrP1.50:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme4: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-bug vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485910 Title: ALSA: usb-audio: Don't attempt to get Lifecam HD-5000 sample rate Status in linux package in Ubuntu: New Bug description: I have a problem with my Lifecam HD-5000. I get timeouts an error- messages with snd-indicator. After searching online I found out there is a problem with the Lifecam not support getting the sample rate. The problem has been fixed upstream in the kernel-sources, see https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/sound/usb?h=linux-3.18.yid=b978d2f62a4c2385b2991a9c73eb70943706bb45 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daniel 2319 F pulseaudio /dev/snd/controlC1: daniel 2319 F pulseaudio /dev/snd/controlC0: daniel 2319 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 18 10:45:53 2015 HibernationDevice: RESUME=UUID=0538bdc9-e4d3-40db-9b4d-df007a205a15 InstallationDate: Installed on 2010-07-03 (1871 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=08269aa3-c22e-46ec-893c-cc8965ef213d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-24 (115 days ago) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: Z97 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:
[Kernel-packages] [Bug 1485102] fozzie (i386) - tests ran: 153, failed: 0
tests ran: 153, failed: 0; http://kernel.ubuntu.com/testing/fozzie__3.13.0-63.103__2015-08-18_07-09-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485102 Title: linux: 3.13.0-63.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-63.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:Friday, 14. August 2015 19:58 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485102] fozzie (amd64) - tests ran: 180, failed: 1
tests ran: 180, failed: 1; http://kernel.ubuntu.com/testing/fozzie__3.13.0-63.103__2015-08-18_04-09-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485102 Title: linux: 3.13.0-63.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-63.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:Friday, 14. August 2015 19:58 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1448519] Re: Logitech K400 cannot type in LUKS passphrase at boot
Hi, I had the same problem with a K800 Keyboard from Logitech. a better way would be to edit the file /etc/initramfs-tools/modules and add hid-logitech-hidpp there. Then it is sufficiant to to sudo update-initramfs -c -k $(uname -r) for the running kernel (or -k all for all kernels). Confirmed with Logitech K800, Ubuntu 14.04.3, 3.19.0-26-generic (64bit) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1448519 Title: Logitech K400 cannot type in LUKS passphrase at boot Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Xubuntu 15.04 (which uses the linux- image-3.19.0-15-generic kernel), I can no longer type in my LUKS passphrase (or even press Control-Alt-Delete to reboot the machine) at boot using my Logitech K400 wireless USB keyboard. Thankfully, the linux-image-3.16.0-34-generic kernel (which does not suffer from this problem) still existed on my machine from my previous Xubuntu 14.10 installation. So I am using that kernel as a workaround: 1. Boot the computer. 2. Wait for the BIOS splash screen to pass. 2. Quickly press the Escape key repeatedly until the GRUB boot menu appears. If I don't do this quickly enough, I encounter the LUKS passphrase screen where my Logitech K400 wireless USB keyboard does not work. 3. Press the Down arrow key to choose the second menu item called Advanced Ubuntu Options. 4. Press the Down arrow key several times to choose the menu item called linux-image-3.16.0-34-generic. 5. Press the Enter key. 6. Now the LUKS passphrase screen will appear where my Logitech K400 wireless USB keyboard will work correctly because the linux-image-3.16.0-34-generic kernel was booted instead of the problematic linux-image-3.19.0-15-generic kernel. Please fix the linux-image-3.19.0-15-generic kernel's build recipe to include support for the Logitech K400 wireless USB keyboard. Thanks for your consideration. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: manillu1474 F pulseaudio /dev/snd/controlC0: manillu1474 F pulseaudio CurrentDesktop: XFCE Date: Sat Apr 25 11:19:01 2015 HibernationDevice: RESUME=UUID=d26576da-66da-4d47-85de-4cd8782e43c5 InstallationDate: Installed on 2015-02-28 (55 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-34-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-34-generic N/A linux-backports-modules-3.16.0-34-generic N/A linux-firmware 1.143 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) dmi.bios.date: 02/17/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.01 dmi.board.name: H81M-ITX 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.01:bd02/17/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH81M-ITX: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/1448519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485102] larsen (i386) - tests ran: 153, failed: 0
tests ran: 153, failed: 0; http://kernel.ubuntu.com/testing/larsen__3.13.0-63.103__2015-08-18_08-18-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485102 Title: linux: 3.13.0-63.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-63.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:Friday, 14. August 2015 19:58 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485102] onza (i386) - tests ran: 153, failed: 0
tests ran: 153, failed: 0; http://kernel.ubuntu.com/testing/onza__3.13.0-63.103__2015-08-18_07-46-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485102 Title: linux: 3.13.0-63.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-63.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:Friday, 14. August 2015 19:58 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485102] onibi (amd64) - tests ran: 180, failed: 2
tests ran: 180, failed: 2; http://kernel.ubuntu.com/testing/onibi__3.13.0-63.103__2015-08-18_04-21-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485102 Title: linux: 3.13.0-63.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-63.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:Friday, 14. August 2015 19:58 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1472384] Re: grub-install doesn't include raid5rec.mod
With the latest Wily image I still get the same error. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1472384 Title: grub-install doesn't include raid5rec.mod Status in linux package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 14.04.2 using the official install medium onto my NAS. My NAS contains three drives which I run in a RAID5 configuration with LVM on top. I setup each drive to have a 128MB EFI partition which stores grubx64.efi and put the rest of the drive under the RAID5+LVM configuration. The Ubuntu 14.04.2 and 15.04 installs were happy to let me do that however when I try to boot into the freshly installed system the GRUB command prompt came up. While I was able to see the LVM partitions using ls I couldn't access them because I needed raid5rec.mod. I booted into a live CD and used grub-mkimage to create a grubx64.efi image which had raid5rec.mod, and all the other modules I needed to boot, embedded into grubx64.efi. Possible resolutions 1. Store all grub modules on the EFI partition 2. Modify grub-install to create grubx64.efi with all block/file system modules embedded into the image needed to access the partition which contains the grub modules --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.16.0-43-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/NAS-SWAP InstallationDate: Installed on 2015-07-07 (0 days ago) InstallationMedia: Ubuntu-Server 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-43-generic.efi.signed root=/dev/mapper/NAS-ROOT ro nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13 RelatedPackageVersions: linux-restricted-modules-3.16.0-43-generic N/A linux-backports-modules-3.16.0-43-generic N/A linux-firmware 1.127.12 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.16.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/14/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: AM1M-A 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.:bvr1201:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnAM1M-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485127] ms10-35-mcdivittB0 (arm64) - tests ran: 153, failed: 5
tests ran: 153, failed: 5; http://kernel.ubuntu.com/testing/ms10-35-mcdivittB0__3.16.0-47.63~14.04.1__2015-08-18_05-42-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1485127 Title: linux-lts-utopic: 3.16.0-47.63~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-47.63~14.04.1 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:Friday, 14. August 2015 22:17 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485102] larsen (amd64) - tests ran: 180, failed: 5
tests ran: 180, failed: 5; http://kernel.ubuntu.com/testing/larsen__3.13.0-63.103__2015-08-18_05-08-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485102 Title: linux: 3.13.0-63.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-63.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:Friday, 14. August 2015 19:58 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485102] tarf (i386) - tests ran: 153, failed: 0
tests ran: 153, failed: 0; http://kernel.ubuntu.com/testing/tarf__3.13.0-63.103__2015-08-18_06-04-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485102 Title: linux: 3.13.0-63.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-63.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:Friday, 14. August 2015 19:58 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463653] Re: crash subcommand bt -a displays incomplete information
*** This bug is a duplicate of bug 1429250 *** https://bugs.launchpad.net/bugs/1429250 --- Comment From pt...@cn.ibm.com 2015-08-18 07:53 EDT--- (In reply to comment #16) (In reply to comment #15) (In reply to comment #14) This is basically the same bug as #1429250, but targeting 14.04 branch Looks like there is no update for crash yet: % dpkg -l crash Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=- =- == ii crash7.0.3-3ubuntu4.2 ppc64el kernel debugging utility, allowing gdb like syntax Hi Ping, The update is supposedly in trusty-proposed as mentioned here: https://bugzilla.linux.ibm.com/show_bug.cgi?id=120594#c23 If you didn't try the steps mentioned there, can you try now and update the bug accordingly? Thanks Hari I can confirm that this bug has been fixed with the 7.0.3-3ubuntu4.3. ** Bug watch added: bugzilla.linux.ibm.com/ #120594 https://bugzilla.linux.ibm.com/show_bug.cgi?id=120594 -- 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/1463653 Title: crash subcommand bt -a displays incomplete information Status in makedumpfile package in Ubuntu: New Bug description: ---Steps to Reproduce--- 1) Using latest daily ISO install 14.04.02 as a Power VM guest. The LPAR has vTPM functionality enabled. 2) Upgrade the kernel to 3.19 level (3.19.0-18-generic) 3) Configure kdump. A fix is required to configure kdump. Refer to defect (https://bugzilla.linux.ibm.com/show_bug.cgi?id=125712) 4) Trigger a dump. Dump is captured successfully. 5) Install dbgsym package for the kernel 6) Use crash to analyze the dump. Crash tool is able to read the dump. But it fails to list back trace for CPUS using bt command. # crash /usr/lib/debug/boot/vmlinux-3.19.0-18-generic dump.201506040624 crash 7.0.3 Copyright (C) 2002-2013 Red Hat, Inc. Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation Copyright (C) 1999-2006 Hewlett-Packard Co Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited Copyright (C) 2006, 2007 VA Linux Systems Japan K.K. Copyright (C) 2005, 2011 NEC Corporation Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc. Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc. This program is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Enter help copying to see the conditions. This program has absolutely no warranty. Enter help warranty for details. GNU gdb (GDB) 7.6 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as powerpc64le-unknown-linux-gnu... KERNEL: /usr/lib/debug/boot/vmlinux-3.19.0-18-generic DUMPFILE: dump.201506040624 [PARTIAL DUMP] CPUS: 16 DATE: Wed Dec 31 19:00:00 1969 UPTIME: 00:02:32 LOAD AVERAGE: 0.01, 0.01, 0.01 TASKS: 245 NODENAME: alp9 RELEASE: 3.19.0-18-generic VERSION: #18~14.04.1-Ubuntu SMP Wed May 20 09:40:36 UTC 2015 MACHINE: ppc64le (3724 Mhz) MEMORY: 100 GB PANIC: Oops: System Reset, sig: 6 [#1] (check log for details) PID: 0 COMMAND: swapper/0 TASK: c13cca80 (1 of 16) [THREAD_INFO: c1448000] CPU: 0 STATE: TASK_RUNNING (PANIC) crash bt -a PID: 0 TASK: c13cca80 CPU: 0 COMMAND: swapper/0 PID: 0 TASK: c003dbf3b3c0 CPU: 1 COMMAND: swapper/1 PID: 0 TASK: c003dbf39f00 CPU: 2 COMMAND: swapper/2 PID: 0 TASK: c003dbf38a40 CPU: 3 COMMAND: swapper/3 PID: 0 TASK: c003dbf37580 CPU: 4 COMMAND: swapper/4 PID: 0 TASK: c003dbf360c0 CPU: 5 COMMAND: swapper/5 PID: 0 TASK: c003dbf34c00 CPU: 6 COMMAND: swapper/6 PID: 0 TASK: c003dbf33740 CPU: 7 COMMAND: swapper/7 PID: 0 TASK: c003dbf32280 CPU: 8 COMMAND: swapper/8 PID: 0 TASK: c003dbf30dc0 CPU: 9 COMMAND: swapper/9 PID: 0 TASK: c003dbf2f900 CPU: 10 COMMAND: swapper/10 PID: 0 TASK: c003dbf2e440 CPU: 11 COMMAND: swapper/11 PID: 0 TASK: c003dbf2cf80 CPU: 12 COMMAND: swapper/12
[Kernel-packages] [Bug 1485162] Re: linux-ti-omap4: 3.2.0-1470.91 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges (arges) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1485162 Title: linux-ti-omap4: 3.2.0-1470.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the 3.2.0-1470.91 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:Saturday, 15. August 2015 03:01 UTC kernel-stable-master-bug:1485081 kernel-stable-Certification-testing-end:Monday, 17. August 2015 19:02 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Monday, 17. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Monday, 17. August 2015 23:01 UTC kernel-stable-phase-changed:Monday, 17. August 2015 23:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485113] modoc (ppc64el) - tests ran: 170, failed: 5
tests ran: 170, failed: 5; http://kernel.ubuntu.com/testing/modoc__3.19.0-27.29__2015-08-18_01-52-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485113 Title: linux: 3.19.0-27.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-27.29 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:Friday, 14. August 2015 20:50 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485164] Re: linux-armadaxp: 3.2.0-1655.77 -proposed tracker
** Description changed: This bug is for tracking the 3.2.0-1655.77 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:Saturday, 15. August 2015 03:03 UTC kernel-stable-master-bug:1485081 kernel-stable-Certification-testing-end:Monday, 17. August 2015 03:01 UTC kernel-stable-Security-signoff-end:Monday, 17. August 2015 03:01 UTC kernel-stable-Prepare-package-end:Monday, 17. August 2015 06:02 UTC kernel-stable-Promote-to-proposed-start:Monday, 17. August 2015 06:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 18. August 2015 00:03 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 02:01 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 02:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 02:01 UTC + kernel-stable-Regression-testing-end:Tuesday, 18. August 2015 06:00 UTC -- 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/1485164 Title: linux-armadaxp: 3.2.0-1655.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1655.77 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:Saturday, 15. August 2015 03:03 UTC kernel-stable-master-bug:1485081 kernel-stable-Certification-testing-end:Monday, 17. August 2015 03:01 UTC kernel-stable-Security-signoff-end:Monday, 17. August 2015 03:01 UTC kernel-stable-Prepare-package-end:Monday, 17. August 2015 06:02 UTC kernel-stable-Promote-to-proposed-start:Monday, 17. August 2015 06:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 18. August 2015 00:03 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 02:01 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 02:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 02:01 UTC kernel-stable-Regression-testing-end:Tuesday, 18. August 2015 06:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1483366] Re: Lenovo E540: Brightness control does not work
Hi! Thanks for your advice! The procedure you adviced me was near limits of my linux and Ubuntu using skills. But I can infrom this problem is solved currently this way. I suddenly adjusted the audio level from laptop button to zero. That somehow reseted the brightness function also, and it has been working okay since then. Regards, Toni Leino 2015-08-13 0:25 GMT+03:00 Joseph Salisbury joseph.salisb...@canonical.com: Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.2 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-rc6-unstable/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1483366 Title: Lenovo E540: Brightness control does not work Status in linux package in Ubuntu: Incomplete Bug description: After last Ubuntu updates, brightness control buttons stopped to work, brightness is stuck on maximum. When pressing key to reduce brightness, indicator shows up as it should, but doesn't let to reduce the indicator any step lower. Running Ubuntu 14.04 LTS. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lenovou2662 F pulseaudio /dev/snd/controlC1: lenovou2662 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=0b3d8bde-fcba-4eb8-8ec0-9218338b66ad InstallationDate: Installed on 2015-02-14 (176 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 20C6003QMS Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=c4dc0d94-61b2-4b8b-b547-79fea553646b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 RelatedPackageVersions: linux-restricted-modules-3.13.0-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 Tags: trusty Uname: Linux 3.13.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2014 dmi.bios.vendor: LENOVO dmi.bios.version: J9ET93WW (2.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6003QMS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ET93WW(2.13):bd08/29/2014:svnLENOVO:pn20C6003QMS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6003QMS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C6003QMS dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483366/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483366 Title: Lenovo E540: Brightness control does not work Status in linux package in Ubuntu: Incomplete Bug description: After last Ubuntu updates, brightness control buttons stopped to work, brightness is stuck on maximum. When pressing key to reduce brightness, indicator shows up as it should, but doesn't let to reduce the indicator any step lower. Running Ubuntu 14.04 LTS. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lenovou2662 F pulseaudio /dev/snd/controlC1: lenovou2662 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=0b3d8bde-fcba-4eb8-8ec0-9218338b66ad InstallationDate: Installed on 2015-02-14 (176 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 20C6003QMS Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=c4dc0d94-61b2-4b8b-b547-79fea553646b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 RelatedPackageVersions:
[Kernel-packages] [Bug 1485081] cavac (i386) - tests ran: 4, failed: 2
tests ran: 4, failed: 2; http://kernel.ubuntu.com/testing/cavac__3.2.0-90.128__2015-08-18_02-39-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485081 Title: linux: 3.2.0-90.128 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress 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-90.128 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:Friday, 14. August 2015 18:50 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 03:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 03:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:00 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:00 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:00 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485102] onza (amd64) - tests ran: 180, failed: 3
tests ran: 180, failed: 3; http://kernel.ubuntu.com/testing/onza__3.13.0-63.103__2015-08-18_05-01-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485102 Title: linux: 3.13.0-63.103 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-63.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:Friday, 14. August 2015 19:58 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 05:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:01 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: Fix Released Status in crash source package in Trusty: Fix Committed Bug description: SRU Justification [Impact] crash's sub-command cannot show stack frame of active tasks on ppc64le systems. [Test Case] 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied [Fix] https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 [Regression potential] This is easily testable and only affects ppc64le systems. This has already been backported to vivid without issue. -- Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Further, this is more of an alternative approach for getting backtrace. So, the problem I mentioned here doesn't have any issues in terms of functionality with regard to this bug or any other for that
[Kernel-packages] [Bug 1485113] fozzie (amd64) - tests ran: 194, failed: 1
tests ran: 194, failed: 1; http://kernel.ubuntu.com/testing/fozzie__3.19.0-27.29__2015-08-18_09-31-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485113 Title: linux: 3.19.0-27.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-27.29 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:Friday, 14. August 2015 20:50 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479945] Re: fglrx module fails to build with 3.19.0-26
*** This bug is a duplicate of bug 1479913 *** https://bugs.launchpad.net/bugs/1479913 This kernel has been rolled out now, with the broken, GPL-violating module still present. I had to roll back to 3.19.0-25 as suggested above. https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1485821 Should this have really been released, if it has been known about for weeks? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1479945 Title: fglrx module fails to build with 3.19.0-26 Status in linux package in Ubuntu: Confirmed Bug description: This update broke fglrx here (and so my graphical environment). I tested with the fglrx from standard repositories and with the latest driver from the amd website. Same error in both cases. If fails during the DKMS build: Error! Bad return status for module build on kernel: 3.19.0-26-generic (x86_64) Consult /var/lib/dkms/fglrx-core/15.200/build/make.log for more information. $ cat /var/lib/dkms/fglrx-core/15.200/build/make.log DKMS make.log for fglrx-core-15.200 for kernel 3.19.0-26-generic (x86_64) jeudi 30 juillet 2015, 21:14:39 (UTC+0200) /usr/sbin/dkms: ligne 74 : cd: /var/lib/dkms/fglrx/15.200/build: Aucun fichier ou dossier de ce type AMD kernel module generator version 2.1 doing Makefile based build for kernel 2.6.x and higher rm -rf *.c *.h *.o *.ko *.a .??* *.symvers make -C /lib/modules/3.19.0-26-generic/build SUBDIRS=/var/lib/dkms/fglrx-core/15.200/build/2.6.x modules make[1]: Entering directory '/usr/src/linux-headers-3.19.0-26-generic' CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.o /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:6424:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function] static int KCL_fpu_save_init(struct task_struct *tsk) ^ CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_acpi.o /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_acpi.c:832:20: warning: ‘KCL_ACPI_Slot_No_Hotplug’ defined but not used [-Wunused-function] static acpi_status KCL_ACPI_Slot_No_Hotplug(KCL_ACPI_DevHandle handle, u32 lvl, void *data, void **rv) ^ CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_agp.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_debug.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_ioctl.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_io.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_pci.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_str.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_iommu.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_wait.o LD [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/fglrx.o Building modules, stage 2. MODPOST 1 modules FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'pci_ignore_hotplug' scripts/Makefile.modpost:90: recipe for target '__modpost' failed make[2]: *** [__modpost] Error 1 Makefile:1397: recipe for target 'modules' failed make[1]: *** [modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-3.19.0-26-generic' Makefile:88: recipe for target 'kmod_build' failed make: *** [kmod_build] Error 2 build failed with return value 2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.27 ProcVersionSignature: Ubuntu 3.19.0-26.27-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1716 F pulseaudio /dev/snd/controlC1: nicolas1716 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 30 21:16:29 2015 HibernationDevice: RESUME=UUID=f723849e-aa39-4a8d-b7f4-87d4f4cbdd95 InstallationDate: Installed on 2015-04-24 (97 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7752 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=040f612d-29f0-46e5-961f-dd5deb7df33b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143.2 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G45
[Kernel-packages] [Bug 1443888] Re: No sound on ThinkPad docking station
Daniel Saier, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443888/comments/21 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/1443888 Title: No sound on ThinkPad docking station Status in linux package in Ubuntu: Invalid Bug description: I have a Thinkpad T450s. The sound works normally unless it is plugged in to the docking station (a ThinkPad Ultra Dock). If speakers are plugged in to the dock, the internal speakers get disabled correctly, but the output of the docking station does not work. Speakers which are plugged in directly on the Laptop still work. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-13-generic 3.19.0-13.13 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1739 F pulseaudio /dev/snd/controlC1: daniel 1739 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 14 12:58:35 2015 HibernationDevice: RESUME=UUID=a67a91aa-8c15-4693-be37-7c177747bc39 InstallationDate: Installed on 2015-04-04 (9 days ago) InstallationMedia: It MachineType: LENOVO 20BWS03E00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic root=UUID=1643390a-82a8-405a-b938-057879ff3c9c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-13-generic N/A linux-backports-modules-3.19.0-13-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-04 (9 days ago) dmi.bios.date: 12/23/2014 dmi.bios.vendor: LENOVO dmi.bios.version: JBET41WW (1.06 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS03E00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET41WW(1.06):bd12/23/2014:svnLENOVO:pn20BWS03E00:pvrThinkPadT450s:rvnLENOVO:rn20BWS03E00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS03E00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479945] Re: fglrx module fails to build with 3.19.0-26
Possible cause and solution here: http://askubuntu.com/questions/655906/broken-fglrx-dkms-module-on- latest-ubuntu-updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1479945 Title: fglrx module fails to build with 3.19.0-26 Status in linux package in Ubuntu: Confirmed Bug description: This update broke fglrx here (and so my graphical environment). I tested with the fglrx from standard repositories and with the latest driver from the amd website. Same error in both cases. If fails during the DKMS build: Error! Bad return status for module build on kernel: 3.19.0-26-generic (x86_64) Consult /var/lib/dkms/fglrx-core/15.200/build/make.log for more information. $ cat /var/lib/dkms/fglrx-core/15.200/build/make.log DKMS make.log for fglrx-core-15.200 for kernel 3.19.0-26-generic (x86_64) jeudi 30 juillet 2015, 21:14:39 (UTC+0200) /usr/sbin/dkms: ligne 74 : cd: /var/lib/dkms/fglrx/15.200/build: Aucun fichier ou dossier de ce type AMD kernel module generator version 2.1 doing Makefile based build for kernel 2.6.x and higher rm -rf *.c *.h *.o *.ko *.a .??* *.symvers make -C /lib/modules/3.19.0-26-generic/build SUBDIRS=/var/lib/dkms/fglrx-core/15.200/build/2.6.x modules make[1]: Entering directory '/usr/src/linux-headers-3.19.0-26-generic' CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.o /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:6424:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function] static int KCL_fpu_save_init(struct task_struct *tsk) ^ CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_acpi.o /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_acpi.c:832:20: warning: ‘KCL_ACPI_Slot_No_Hotplug’ defined but not used [-Wunused-function] static acpi_status KCL_ACPI_Slot_No_Hotplug(KCL_ACPI_DevHandle handle, u32 lvl, void *data, void **rv) ^ CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_agp.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_debug.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_ioctl.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_io.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_pci.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_str.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_iommu.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_wait.o LD [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/fglrx.o Building modules, stage 2. MODPOST 1 modules FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'pci_ignore_hotplug' scripts/Makefile.modpost:90: recipe for target '__modpost' failed make[2]: *** [__modpost] Error 1 Makefile:1397: recipe for target 'modules' failed make[1]: *** [modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-3.19.0-26-generic' Makefile:88: recipe for target 'kmod_build' failed make: *** [kmod_build] Error 2 build failed with return value 2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.27 ProcVersionSignature: Ubuntu 3.19.0-26.27-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1716 F pulseaudio /dev/snd/controlC1: nicolas1716 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 30 21:16:29 2015 HibernationDevice: RESUME=UUID=f723849e-aa39-4a8d-b7f4-87d4f4cbdd95 InstallationDate: Installed on 2015-04-24 (97 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7752 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=040f612d-29f0-46e5-961f-dd5deb7df33b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143.2 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G45 (MS-7752) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
** Changed in: linux (Ubuntu) Status: Expired = 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/1451387 Title: Ubuntu UEFI install locks out UEFI firmware Status in linux package in Ubuntu: Confirmed Bug description: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/comments/74 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 4 16:57:39 2015 InstallationDate: Installed on 2010-01-01 (1949 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rut1480 F pulseaudio rut7079 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=d4bb392e-90ed-41a3-9d30-fa457fefb25b InstallationDate: Installed on 2010-01-01 (1949 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: FUJITSU LIFEBOOK LH532 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=e8258103-326b-4708-b64f-6306d0eb0a01 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 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.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.127.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.16.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/24/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.10 dmi.board.name: FJNBB1F dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1F:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK LH532 dmi.sys.vendor: FUJITSU --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rut2207 F pulseaudio DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=8fd2670c-4060-4d14-8f27-b9f806fe2ce7 InstallationDate: Installed on 2015-05-06 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: FUJITSU LIFEBOOK LH532 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed root=UUID=3129a485-81a2-48ef-be95-ef9c9a57be3e ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 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.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/24/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.10 dmi.board.name: FJNBB1F dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1F:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK LH532 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1450910] Re: Watchdog detected hard LOCKUP on cpu 9
TK, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450910/comments/16 regarding this being fixed with a BIOS update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: linux (Ubuntu) Status: Expired = 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/1450910 Title: Watchdog detected hard LOCKUP on cpu 9 Status in linux package in Ubuntu: Invalid Bug description: Experiencing system lockups while idle on Ubuntu 14.04.2, kernel 3.16.0-36. Appears to be related to Bug 1004313 Description: Ubuntu 14.04.2 LTS Release: 14.04 Attached are the details from syslog: ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-36-generic 3.16.0-36.48~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-36.48~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 Date: Fri May 1 13:27:07 2015 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 1 11:30 seq crw-rw 1 root audio 116, 33 May 1 11:30 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [22218.731864] init: tty1 main process ended, respawning DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=65cea15a-996b-45f6-80fe-200ee1f11ab4 MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-36-generic root=UUID=8070b71a-7af3-4a37-a8a6-679255d4ee49 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-36.48~14.04.1-generic 3.16.7-ckt9 RelatedPackageVersions: linux-restricted-modules-3.16.0-36-generic N/A linux-backports-modules-3.16.0-36-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.16.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/17/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.2 dmi.board.name: 03XKDV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.2:bd11/17/2014:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn03XKDV:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: Triaged Status in lxc package in Ubuntu: New Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, rm: cannot remove ‘mntpt/foo’: Operation not permitted strace shows, unlinkat(AT_FDCWD, mntpt/foo, AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel (3.19). The bug does not occur on ubuntu 14.04.2 with the default linux- generic 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, overlayfs: allow unprivileged mounts is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the filesystem underlying overlayfs is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a virtual machine (qemu-system-x86_64). The host is ubuntu 14.04.2 with the default 3.13 kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486020] [NEW] Ubuntu boots to CLI tty1 instead of unity-greeter after latest kernel update
Public bug reported: After updating to kernel 3.19.0-26.28, Ubuntu no longer boots to unity- greeter, instead, it boots to CLI tty1. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Aug 18 14:16:45 2015 InstallationDate: Installed on 2015-06-16 (62 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug regression-update trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1486020 Title: Ubuntu boots to CLI tty1 instead of unity-greeter after latest kernel update Status in linux-lts-vivid package in Ubuntu: New Bug description: After updating to kernel 3.19.0-26.28, Ubuntu no longer boots to unity-greeter, instead, it boots to CLI tty1. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Aug 18 14:16:45 2015 InstallationDate: Installed on 2015-06-16 (62 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1486020/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485378] Re: [REGRESSION] bluetooth visibility turns off
Thanks, that's due to the change from https://launchpad.net/ubuntu/+source/bluez/4.101-0ubuntu24 ** Changed in: bluez (Ubuntu) Importance: Undecided = Low ** Changed in: bluez (Ubuntu) Status: New = Confirmed ** Summary changed: - [REGRESSION] bluetooth visibility turns off + [REGRESSION] bluetooth visibility turns off by itself after 3 minutes -- 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/1485378 Title: [REGRESSION] bluetooth visibility turns off by itself after 3 minutes Status in bluez package in Ubuntu: Confirmed Bug description: I had Ubuntu 14.04 and I had the Bluetooth Visibility set to On. (in the submenu under the bluetooth tray icon, where it reads Visible) It used to be always on, I didn't have to turn it on every time I wanted my computer to be visible. I upgraded to 14.10 and then to 15.04, and then when failing to send a file over bluetooth to my computer, I found out Visible was off. I turned it on, and it worked. However, after a few minutes, it had turned off again. I can't find a setting anywhere to automatically turn off after N seconds. It would make sense to have that. If there is, it should be accessible through Bluetooth settings. If such a settings doesn't exist and once turned on bluetooth visibility is supposed to remain on, then there's some bug which is causing it to randomly turn off. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 16 23:17:42 2015 InstallationDate: Installed on 2013-10-11 (674 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to vivid on 2015-08-15 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:630 acl:0 sco:0 events:40 errors:0 TX bytes:988 acl:0 sco:0 commands:40 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1485378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479945] Re: fglrx module fails to build with 3.19.0-26
*** This bug is a duplicate of bug 1479913 *** https://bugs.launchpad.net/bugs/1479913 ** This bug has been marked a duplicate of bug 1479913 SRU request: fglrx.ko fails because of backported GPL-only 'pci_ignore_hotplug' symbol -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1479945 Title: fglrx module fails to build with 3.19.0-26 Status in linux package in Ubuntu: Confirmed Bug description: This update broke fglrx here (and so my graphical environment). I tested with the fglrx from standard repositories and with the latest driver from the amd website. Same error in both cases. If fails during the DKMS build: Error! Bad return status for module build on kernel: 3.19.0-26-generic (x86_64) Consult /var/lib/dkms/fglrx-core/15.200/build/make.log for more information. $ cat /var/lib/dkms/fglrx-core/15.200/build/make.log DKMS make.log for fglrx-core-15.200 for kernel 3.19.0-26-generic (x86_64) jeudi 30 juillet 2015, 21:14:39 (UTC+0200) /usr/sbin/dkms: ligne 74 : cd: /var/lib/dkms/fglrx/15.200/build: Aucun fichier ou dossier de ce type AMD kernel module generator version 2.1 doing Makefile based build for kernel 2.6.x and higher rm -rf *.c *.h *.o *.ko *.a .??* *.symvers make -C /lib/modules/3.19.0-26-generic/build SUBDIRS=/var/lib/dkms/fglrx-core/15.200/build/2.6.x modules make[1]: Entering directory '/usr/src/linux-headers-3.19.0-26-generic' CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.o /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:6424:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function] static int KCL_fpu_save_init(struct task_struct *tsk) ^ CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_acpi.o /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_acpi.c:832:20: warning: ‘KCL_ACPI_Slot_No_Hotplug’ defined but not used [-Wunused-function] static acpi_status KCL_ACPI_Slot_No_Hotplug(KCL_ACPI_DevHandle handle, u32 lvl, void *data, void **rv) ^ CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_agp.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_debug.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_ioctl.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_io.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_pci.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_str.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_iommu.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl.o CC [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/kcl_wait.o LD [M] /var/lib/dkms/fglrx-core/15.200/build/2.6.x/fglrx.o Building modules, stage 2. MODPOST 1 modules FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'pci_ignore_hotplug' scripts/Makefile.modpost:90: recipe for target '__modpost' failed make[2]: *** [__modpost] Error 1 Makefile:1397: recipe for target 'modules' failed make[1]: *** [modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-3.19.0-26-generic' Makefile:88: recipe for target 'kmod_build' failed make: *** [kmod_build] Error 2 build failed with return value 2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.27 ProcVersionSignature: Ubuntu 3.19.0-26.27-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1716 F pulseaudio /dev/snd/controlC1: nicolas1716 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 30 21:16:29 2015 HibernationDevice: RESUME=UUID=f723849e-aa39-4a8d-b7f4-87d4f4cbdd95 InstallationDate: Installed on 2015-04-24 (97 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7752 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=040f612d-29f0-46e5-961f-dd5deb7df33b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143.2 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G45 (MS-7752) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3
[Kernel-packages] [Bug 1016299] Re: CVE-2012-2372
** Changed in: linux (Ubuntu Vivid) Status: Fix Released = Invalid ** Changed in: linux (Ubuntu Vivid) Assignee: Andy Whitcroft (apw) = (unassigned) ** Changed in: linux (Ubuntu Wily) Status: Fix Released = Invalid ** Changed in: linux (Ubuntu Wily) Assignee: Andy Whitcroft (apw) = (unassigned) ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Invalid ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Invalid ** Changed in: linux-lts-trusty (Ubuntu Precise) Status: Fix Committed = Invalid ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: Fix Committed = Invalid ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: Fix Committed = Invalid ** Description changed: The rds_ib_xmit function in net/rds/ib_send.c in the Reliable Datagram - Sockets (RDS) protocol implementation in the Linux kernel 3.7.4 and - earlier allows local users to cause a denial of service (BUG_ON and - kernel panic) by establishing an RDS connection with the source IP - address equal to the IPoIB interface's own IP address, as demonstrated - by rds-ping. + Sockets (RDS) protocol implementation in the Linux kernel 3.7.4 and earlier + allows local users to cause a denial of service (BUG_ON and kernel panic) + by establishing an RDS connection with the source IP address equal to the + IPoIB interface's own IP address, as demonstrated by rds-ping. Break-Fix: 639b321b4d8f4e412bfbb2a4a19bfebc1e68ace4 local-2012-2372 -- 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/1016299 Title: CVE-2012-2372 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Fix Released Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Natty: Invalid Status in linux-lts-backport-natty source package in Natty: Invalid Status in linux-lts-backport-oneiric source package in Natty: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package
[Kernel-packages] [Bug 1485113] onza (amd64) - tests ran: 197, failed: 2
tests ran: 197, failed: 2; http://kernel.ubuntu.com/testing/onza__3.19.0-27.29__2015-08-18_10-45-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485113 Title: linux: 3.19.0-27.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-27.29 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:Friday, 14. August 2015 20:50 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486153] Re: fglrx-core: fglrx-core kernel module failed to build
** Description changed: After the upgrade to kernel version 3.19.0-26-generic fglrx fails to build the needed DKMS module and renders the GUI non-functional. Had to remove all fglrx packages to get a working Xsession again. Converting back to 3.19.0-25 solved the DKMS module building problem. + + + DKMS make.log for fglrx-core-15.200 for kernel 3.19.0-26-generic (x86_64) + ... + FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'pci_ignore_hotplug' + ... + ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: - + ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 BootLog: - + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 3.19.0-26-generic Date: Tue Aug 18 19:12:54 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.200, 3.19.0-25-generic, x86_64: installed GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) -Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] + Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) + Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2015-08-07 (10 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageVersion: (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=19317e49-95e5-41ee-8908-8a05165ac80c ro vga=0x0368 quiet splash nomodeset video=uvesafb:mode_option=1920x1080-24,mtrr=3,scroll=ywrap vt.handoff=7 RelatedPackageVersions: - dpkg 1.17.25ubuntu1 - apt 1.0.9.7ubuntu4.1 + dpkg 1.17.25ubuntu1 + apt 1.0.9.7ubuntu4.1 SourcePackage: fglrx-installer Title: fglrx-core (not installed): fglrx-core kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/09/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Aug 18 19:13:52 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: fglrx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486153 Title: fglrx-core: fglrx-core kernel module failed to build Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade to kernel version 3.19.0-26-generic fglrx fails to build the needed DKMS module and renders the GUI non-functional. Had to remove all fglrx packages to get a working Xsession again. Converting back to 3.19.0-25 solved the DKMS module building problem. DKMS make.log for fglrx-core-15.200 for kernel 3.19.0-26-generic (x86_64) ... FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'pci_ignore_hotplug' ... ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu1
[Kernel-packages] [Bug 1481490] Re: Add sfc to nic-modules udeb
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1481490 Title: Add sfc to nic-modules udeb Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: == [Trusty][Vivid]SRU Justification == It is being requested that we add the sfc driver to the nic-modules udeb to facilitate PXE booting nodes with Solarflare network adapters. == Fix == Add the sfc driver to our nic-modules udeb. This is being requested for Trusty and Vivid. Note, this has already been applied to Wily master-next. == Testing == I've done test builds of Wily, Vivid, and Trusty and can confirm the sfc driver is seeded into the nic-modules udeb: $ dpkg -c nic-modules-4.2.0-3-generic-di_4.2.0-3.3_amd64.udeb | grep sfc.ko -rw-r--r-- root/root495305 2015-08-04 22:17 ./lib/modules/4.2.0-3-generic/kernel/drivers/net/ethernet/sfc/sfc.ko $ dpkg -c nic-modules-3.19.0-26-generic-di_3.19.0-26.27_amd64.udeb | grep sfc.ko -rw-r--r-- root/root464452 2015-08-04 22:21 ./lib/modules/3.19.0-26-generic/kernel/drivers/net/ethernet/sfc/sfc.ko $ dpkg -c nic-modules-3.13.0-62-generic-di_3.13.0-62.101_amd64.udeb | grep sfc.ko -rw-r--r-- root/root436284 2015-08-04 22:22 ./lib/modules/3.13.0-62-generic/kernel/drivers/net/ethernet/sfc/sfc.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481490] Re: Add sfc to nic-modules udeb
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1481490 Title: Add sfc to nic-modules udeb Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: == [Trusty][Vivid]SRU Justification == It is being requested that we add the sfc driver to the nic-modules udeb to facilitate PXE booting nodes with Solarflare network adapters. == Fix == Add the sfc driver to our nic-modules udeb. This is being requested for Trusty and Vivid. Note, this has already been applied to Wily master-next. == Testing == I've done test builds of Wily, Vivid, and Trusty and can confirm the sfc driver is seeded into the nic-modules udeb: $ dpkg -c nic-modules-4.2.0-3-generic-di_4.2.0-3.3_amd64.udeb | grep sfc.ko -rw-r--r-- root/root495305 2015-08-04 22:17 ./lib/modules/4.2.0-3-generic/kernel/drivers/net/ethernet/sfc/sfc.ko $ dpkg -c nic-modules-3.19.0-26-generic-di_3.19.0-26.27_amd64.udeb | grep sfc.ko -rw-r--r-- root/root464452 2015-08-04 22:21 ./lib/modules/3.19.0-26-generic/kernel/drivers/net/ethernet/sfc/sfc.ko $ dpkg -c nic-modules-3.13.0-62-generic-di_3.13.0-62.101_amd64.udeb | grep sfc.ko -rw-r--r-- root/root436284 2015-08-04 22:22 ./lib/modules/3.13.0-62-generic/kernel/drivers/net/ethernet/sfc/sfc.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1454892] Re: [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling the host
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1454892 Title: [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling the host Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Fix Committed Status in linux source package in Precise: Confirmed Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Released Bug description: hv_netvsc: Use the xmit_more skb flag to optimize signaling the host Based on the information given to this driver (via the xmit_more skb flag), we can defer signaling the host if more packets are on the way. This will help make the host more efficient since it can potentially process a larger batch of packets. Implement this optimization. Upstream commit: https://git.kernel.org/cgit/linux/kernel/git/davem /net-next.git/commit/?id=82fa3c776e5abba7ed6e4b4f4983d14731c37d6a This commit may imply other commits previously requested, for example https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452074 Requested for all typical Hyper-V targets: 15.10, 15.04, 14.10, 14.04, 14.04 HWE, 12.02, and 12.02 HWE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479468] Re: OverlayFS: Wrong mnt_id and path reported in /proc
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-vivid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1479468
Title:
OverlayFS: Wrong mnt_id and path reported in /proc
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Vivid:
Fix Committed
Bug description:
SRU Justification:
[Impact]
I am running Ubuntu Vivid (3.19.0-22-generic #22-Ubuntu SMP Tue Jun 16
17:15:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux). There are two
issues in OverlayFS as follows:
1. /proc/pid/fdinfo/fd reports wrong mnt_id (non-existent in
/proc/pid/mountinfo)
2. /proc/pid/fd/fd shows incorrect path for the symlink target
[Fix]
These problems can be easily reproduced with the shell script below.
Fortunately, both problems have been fixed in the upstream's master
branch of the kernel via the following commits:
torvalds 4.0: 155e35d4d VFS: Introduce inode-getting helpers for
layered/unioned fs environments (this is already in ubuntu-vivid)
torvalds 4.0: df1a085af VFS: Add a fallthrough flag for marking virtual
dentries
torvalds 4.2-rc2: f25801ee4 overlay: Call ovl_drop_write() earlier in
ovl_dentry_open()
torvalds 4.2-rc2: 4bacc9c92 overlayfs: Make f_path always point to the
overlay and f_inode to the underlay
torvalds 4.2-rc2: 9391dd00d fix a braino in ovl_d_select_inode()
(The commit df1a085af may technically not be needed but it prevents a
conflict when applying 4bacc9c92.)
[Test Case]
Simple script to reproduce the problem:
#!/bin/bash
set -eu
ERROR=0
setup() {
setup_mount
start_python /dev/null 21
BASH_PID=$!
PYTHON_PID=$(ps -C python | awk '/python/ { print $1 }')
sleep 1
}
setup_mount() {
mkdir overlay_test
cd overlay_test
mkdir a b c z
sudo mount -t overlay -o lowerdir=a,upperdir=b,workdir=c overlayfs z
}
start_python() {
python EOF
import time
fd = open(z/file, w)
time.sleep(10)
EOF
}
check_path() {
WD=$(pwd)
if ! ls -l /proc/$PYTHON_PID/fd | grep -qw $WD/z/file; then
ERROR=1
echo ERROR! expected $WD/z/file
set -x
ls -l /proc/$PYTHON_PID/fd
set +x
fi
}
check_mnt_id() {
FDINFO_MNT_ID=$(awk '/mnt_id:/ { print $2 }' /proc/$PYTHON_PID/fdinfo/3)
MOUNTINFO_MNT_ID=$(awk '/overlayfs/ { print $1 }' /proc/self/mountinfo)
if [[ $FDINFO_MNT_ID -ne $MOUNTINFO_MNT_ID ]]; then
ERROR=1
echo ERROR! mnt_id $FDINFO_MNT_ID not in /proc/self/mountinfo
set -x
cat /proc/$PYTHON_PID/fdinfo/3
cat /proc/self/mountinfo
set +x
fi
}
finish() {
kill -INT $PYTHON_PID /dev/null 21
sudo umount z
cd $ORIG_WD
rm -rf overlay_test
}
main() {
ORIG_WD=$(pwd)
setup
check_path
check_mnt_id
finish
[[ $ERROR -eq 0 ]] echo OverlayFS looks good.
}
main
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479468/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480142] Re: Need support for Pericom PCIe Serial Card [12d8:7952]
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480142 Title: Need support for Pericom PCIe Serial Card [12d8:7952] Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: Pericom PCIe Serial Card [12d8:7952] doesn't work. Still in progress of upstreaming the fix to mainline. SRU Justification: Impact: https://launchpad.net/bugs/1475481 Fix: from vendor, upstreamed by Adam, accepted by Greg's tty-next by now. Testcase: already tested on a dell laptop, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1480142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484486] Re: [i915 gen8/gen9] Add workarounds to fix hang bugs etc
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484486 Title: [i915 gen8/gen9] Add workarounds to fix hang bugs etc Status in linux package in Ubuntu: Triaged Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Triaged Bug description: 4.3 will have a bunch of workarounds to fix silicon bugs and other bugfixes that need to be backported to both vivid and wily. Some are for gen8 chips which also allow cherry-picking the gen9 ones. drm/i915/skl WaDisableSbeCacheDispatchPortSharing drm/i915/skl: Don't expose the top most plane on gen9 display drm/i915/skl: revert duplicated WaBarrierPerformanceFixDisable:skl drm/i915:skl: Add WaEnableGapsTsvCreditFix drm/i915/gen9: Add WaSetDisablePixMaskCammingAndRhwoInCommonSliceChicken drm/i915/gen9: Add WaFlushCoherentL3CacheLinesAtContextSwitch workaround drm/i915: Update wa_ctx_emit() macro as per kernel coding guidelines drm/i915/gen9: Add WaDisableCtxRestoreArbitration workaround drm/i915: Enable WA batch buffers for Gen9 drm/i915/gen9: Implement WaDisableKillLogic for gen 9 drm/i915: Update WaFlushCoherentL3CacheLinesAtContextSwitch drm/i915/gen8: Add WaClearSlmSpaceAtContextSwitch workaround drm/i915: Bail out early if WA batch is not available for given Gen drm/i915/gen8: Add WaFlushCoherentL3CacheLinesAtContextSwitch workaround drm/i915/gen8: Add WaDisableCtxRestoreArbitration workaround drm/i915/gen8: Re-order init pipe_control in lrc mode drm/i915/gen8: Add infrastructure to initialize WA batch buffers drm/i915: Move WaBarrierPerformanceFixDisable:skl to skl code from chv code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1478513] Re: MFG:Firestone, Linux Error message: SYSPARAM: Opal sysparam node not found
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1478513 Title: MFG:Firestone, Linux Error message: SYSPARAM: Opal sysparam node not found Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Fix Committed Bug description: SRU Justification [Impact] When using Firestone POWER8 hardware, the following message gets printed to the kernel log: SYSPARAM: Opal sysparam node not found [Test Case] 1) Boot affected hardware. 2) dmesg | grep 'Opal sysparam node not found' [Fix] $ git describe --contains 38c0488770983b2654f075540cc1fc71f55b6df5 v4.2-rc1~135^2~144 -- == Comment: #0 - Application Cdeadmin cdead...@us.ibm.com - 2015-07-22 11:35:05 == == Comment: #1 - Application Cdeadmin cdead...@us.ibm.com - 2015-07-22 11:35:06 == State: Open by: knodelk on 22 July 2015 10:25:15 The following message is being posted to the linux message log on Firestone systems, and we need to know what action to take. - is this caused by a code bug that needs to be fixed? - does the message indicate a real hardware problem? or can the message be ignore? Until we here otherwise, manufacturing is ignoring this message dmesg --level=alert,crit,err SYSPARAM: Opal sysparam node not found system is running with the following code levels: ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 14.04.2 LTS \n \l Kernel Version: 3.16.0-30-generic HTX Version: htxubuntu-343 == Comment: #2 - MAMATHA INAMDAR mainam...@in.ibm.com - 2015-07-27 06:18:20 == SYSPARAM: Opal sysparam node not found we get this warning on firestone system for every boot because For OpenPower BMC machines we do not place any sysparams in the device tree. This issue is addressed in the attached patch and patch is available in upstream. We need to backport following patch in ubuntu to address this issue. Commit ID:38c0488770983b2654f075540cc1fc71f55b6df5 0001-powerpc-powernv-Silence-SYSPARAM-warning-on-boot.patch == Comment: #3 - MAMATHA INAMDAR mainam...@in.ibm.com - 2015-07-27 06:25:34 == Please find upstream commit ID link https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=38c0488770983b2654f075540cc1fc71f55b6df5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484531] Re: [i915 SKL] Add support for VGA output
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484531 Title: [i915 SKL] Add support for VGA output Status in linux package in Ubuntu: Triaged Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Triaged Bug description: Current i915 driver (4.2) does not support VGA output on SKL. It needs a bunch of cherry-picks and some backports. Some are not applied upstream yet, but are being tested to meet OEM schedule.. drm/i915/skl: Enable DDI-E drm/i915/skl: Adding DDI_E power well domain drm/i915: Adding break for one case drm/i915/skl: DDI-E and DDI-A shares 4 lanes. drm/i915: Enable HDMI on DDI-E drm/i915: eDP can be present on DDI-E drm/i915/skl: enable DDI-E hotplug drm/i915: Set alternate aux for DDI-E drm/i915: Set power domain for DDI-E drm/i915: Handle HPD when it has actually occurred drm/i915: abstract away platform specific parts from hpd handling drm/i915: simplify condition for digital port drm/i915: merge the two hpd loops in intel_hpd_irq_handler to one drm/i915: put back the indent in intel_hpd_irq_handler drm/i915: simplify conditions for skipping the 2nd hpd loop iterations drm/i915: add for_each_hpd_pin to iterate over hotplug pins drm/i915: group all hotplug related fields into a new struct in dev_priv drm/i915: reduce indent in intel_hpd_irq_handler drm/i915: reduce duplicate conditions in i9xx_hpd_irq_handler drm/i915: reduce indent in i9xx_hpd_irq_handler To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484482] Re: [i915_bpo] Sync to 4.2-rc6
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484482 Title: [i915_bpo] Sync to 4.2-rc6 Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Fix Committed Bug description: We need to add a few commits from upstream to i915_bpo and drm/drm_atomic* in order to be better in sync with it. 6ea76f3cade4734 drm/atomic-helpers: Make encoder picking more robust 3b8a684bd6cbc13 drm/atomic-helper: Add an atomice best_encoder callback 27667f4744fc5a0 i915: temporary fix for DP MST docking station NULL pointer dereference 2465ff6217f1b63 drm/atomic: Extract needs_modeset function 9b5edbf7a462b7c drm/atomic: Clear crtc_state-active in drm_atomic_helper_set_config. 57744aa7cfb5969 drm/atomic: add all affected planes in drm_atomic_helper_check_modeset e01e9f75a0c4e6c drm/atomic: add drm_atomic_add_affected_planes de28d0212a3ea7b drm/atomic: add commit_planes_on_crtc helper 60f207a5b6d8f23 drm/atomic: fix out of bounds read in for_each_*_in_state helpers 047fe6e6db9161e drm/i915: Allow parsing of variable size child device entries from VBT 459485ad3513bce drm/i915: Fixup dp mst encoder selection 5eb3e5a5e11d14f drm/i915: Declare the swizzling unknown for L-shaped configurations d0e30adc42d979e drm/i915: Mark PIN_USER binding as GLOBAL_BIND without the aliasing ppgtt ee0a227b7ac6e75 drm/i915: Replace WARN inside I915_READ64_2x32 with retry loop 648a9bc5308d952 drm/i915: Use two 32bit reads for select 64bit REG_READ ioctls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483214] Re: ipmi_si module spams kernel log with ipmi_si 00:05: Could not set the global enables: 0xcc.
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483214 Title: ipmi_si module spams kernel log with ipmi_si 00:05: Could not set the global enables: 0xcc. Status in linux package in Ubuntu: Fix Released Status in openipmi package in Ubuntu: Invalid Status in linux source package in Vivid: Fix Committed Status in openipmi source package in Vivid: Invalid Bug description: Hello, after upgrading my system to 14.04.3 LTS and installing the Vivid-LTS- Enablement-Stack the kernel log of my system is spammed with the following message by the impi_si kernel module: ... [ 2268.244383] ipmi_si 00:05: Could not set the global enables: 0xcc. [ 2269.451974] ipmi_si 00:05: Could not set the global enables: 0xcc. [ 2270.252290] ipmi_si 00:05: Could not set the global enables: 0xcc. [ 2271.452749] ipmi_si 00:05: Could not set the global enables: 0xcc. [ 2272.253057] ipmi_si 00:05: Could not set the global enables: 0xcc. ... This bug is already known to the ipmi_si kernel module maintainer and seems to be fixed in 4.0+ kernels. Is it possible to backport this fix to the Vivid 3.19 kernel? Please see this mail thread: https://www.mail-archive.com/openipmi- develo...@lists.sourceforge.net/msg02425.html IPMI functionality seems to be unaffected by this bug but as I said it spams the kernel log and that is rather annoying. System information: lsb_release -rd: Description:Ubuntu 14.04.3 LTS Release:14.04 apt-cache policy openipmi: openipmi: Installiert: 2.0.18-0ubuntu7.1 Installationskandidat: 2.0.18-0ubuntu7.1 Versionstabelle: *** 2.0.18-0ubuntu7.1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.0.18-0ubuntu7 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Greetings, Felix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1440949] Re: [Dell Inspiron 3543] Wireless key does not work on 14.04.2
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1440949 Title: [Dell Inspiron 3543] Wireless key does not work on 14.04.2 Status in HWE Next: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-lts-utopic package in Ubuntu: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux-lts-utopic source package in Vivid: New Bug description: CID: 201408-15437 Dell Inspiron 3543 The wireless key does not work on this system at all with14.04.2 (3.16 kernel) Maybe it's related to the udev - systemd migration (similar to bug 1434442) ubuntu@201408-15437:~$ sudo showkey -k [sudo] password for ubuntu: kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 240 press keycode 240 release keycode 29 press ^Ccaught signal 2, cleaning up... ubuntu@201408-15437:~$ nothing could be detected by sudo showkey -s ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-33-generic 3.16.0-33.44~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 6 22:17:20 2015 InstallationDate: Installed on 2015-04-03 (3 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1440949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486153] [NEW] fglrx-core: fglrx-core kernel module failed to build
You have been subscribed to a public bug: After the upgrade to kernel version 3.19.0-26-generic fglrx fails to build the needed DKMS module and renders the GUI non-functional. Had to remove all fglrx packages to get a working Xsession again. Converting back to 3.19.0-25 solved the DKMS module building problem. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 3.19.0-26-generic Date: Tue Aug 18 19:12:54 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.200, 3.19.0-25-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2015-08-07 (10 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageVersion: (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=19317e49-95e5-41ee-8908-8a05165ac80c ro vga=0x0368 quiet splash nomodeset video=uvesafb:mode_option=1920x1080-24,mtrr=3,scroll=ywrap vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: fglrx-installer Title: fglrx-core (not installed): fglrx-core kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/09/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Aug 18 19:13:52 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: fglrx ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 ubuntu vivid -- fglrx-core: fglrx-core kernel module failed to build https://bugs.launchpad.net/bugs/1486153 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
(confirmed here on my wily laptop - thanks for reporting this) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, rm: cannot remove ‘mntpt/foo’: Operation not permitted strace shows, unlinkat(AT_FDCWD, mntpt/foo, AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel (3.19). The bug does not occur on ubuntu 14.04.2 with the default linux- generic 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, overlayfs: allow unprivileged mounts is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the filesystem underlying overlayfs is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a virtual machine (qemu-system-x86_64). The host is ubuntu 14.04.2 with the default 3.13 kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485173] Re: linux-lts-trusty: 3.13.0-63.104~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: New = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1485173 Title: linux-lts-trusty: 3.13.0-63.104~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: New Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-63.104~precise1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Saturday, 15. August 2015 05:03 UTC kernel-stable-master-bug:1485102 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Sunday, 16. August 2015 12:02 UTC kernel-stable-Promote-to-proposed-start:Sunday, 16. August 2015 12:02 UTC kernel-stable-phase-changed:Sunday, 16. August 2015 12:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1469488] Re: Suspend crashes ubuntu every now and then
Updated to 4.2-rc6. Let's see what happens... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1469488 Title: Suspend crashes ubuntu every now and then Status in linux package in Ubuntu: Incomplete Bug description: Once every 5 or so suspends, ubuntu crashes immediately: power leds are still indicating the hardware is running, monitor falls asleep as on successful suspend, cannot ctr-alt-fn into terminal, cannot ssh into ubuntu, logs show no errors... ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-21-generic 3.19.0-21.21 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: izak 1957 F...m pulseaudio /dev/snd/pcmC1D0p: izak 1957 F...m pulseaudio /dev/snd/controlC0: izak 1957 F pulseaudio /dev/snd/controlC1: izak 1957 F pulseaudio CurrentDesktop: Unity Date: Sun Jun 28 11:28:11 2015 HibernationDevice: RESUME=UUID=4226b1a5-ebed-4bf9-afa2-33431caa2763 InstallationDate: Installed on 2014-10-24 (246 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-04 (54 days ago) dmi.bios.date: 09/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2012 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2012:bd09/30/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486153] [NEW] fglrx-core: fglrx-core kernel module failed to build
Public bug reported: After the upgrade to kernel version 3.19.0-26-generic fglrx fails to build the needed DKMS module and renders the GUI non-functional. Had to remove all fglrx packages to get a working Xsession again. Converting back to 3.19.0-25 solved the DKMS module building problem. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 3.19.0-26-generic Date: Tue Aug 18 19:12:54 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.200, 3.19.0-25-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2015-08-07 (10 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageVersion: (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=19317e49-95e5-41ee-8908-8a05165ac80c ro vga=0x0368 quiet splash nomodeset video=uvesafb:mode_option=1920x1080-24,mtrr=3,scroll=ywrap vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: fglrx-installer Title: fglrx-core (not installed): fglrx-core kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/09/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Aug 18 19:13:52 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: fglrx ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package compiz-0.9 ubuntu vivid ** Package changed: fglrx-installer (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486153 Title: fglrx-core: fglrx-core kernel module failed to build Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade to kernel version 3.19.0-26-generic fglrx fails to build the needed DKMS module and renders the GUI non-functional. Had to remove all fglrx packages to get a working Xsession again. Converting back to 3.19.0-25 solved the DKMS module building problem. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 3.19.0-26-generic Date: Tue Aug 18 19:12:54 2015 DistUpgraded: Fresh install
[Kernel-packages] [Bug 1206200] Re: CVE-2013-1060
** Changed in: linux (Ubuntu Vivid) Status: Fix Released = Invalid ** Changed in: linux (Ubuntu Wily) Status: Fix Released = Invalid ** Changed in: linux (Ubuntu Vivid) Assignee: Andy Whitcroft (apw) = (unassigned) ** Changed in: linux (Ubuntu Wily) Assignee: Andy Whitcroft (apw) = (unassigned) -- 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/1206200 Title: CVE-2013-1060 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-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: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-mako source package in Wily: New
[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
I don't quite get the point underlying Serge's preceding comment, so I'll describe the problem I'm experiencing with lxc and see whether Serge classifies it as a bug. On an ubuntu-vivid (amd64) host, create an unprivileged vivid container named 'vivid', lxc-create -n vivid -t download -- -d ubuntu -r vivid -a amd64 Start and attach to the container and create foo/bar.txt . Stop the container. Then form a second container named vivid_overlay, lxc-clone -s -B overlayfs vivid vivid_overlay Start and attach to vivid_overlay. Delete bar.txt (this should succeed). Attempt to delete foo. I get Operation not permitted, even as root in the container. The same issue arises if I replace the overlay container with an ephemeral container, lxc-start-ephemeral -o vivid -n vivid_ephemeral -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: Invalid Status in lxc package in Ubuntu: Invalid Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, rm: cannot remove ‘mntpt/foo’: Operation not permitted strace shows, unlinkat(AT_FDCWD, mntpt/foo, AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel (3.19). The bug does not occur on ubuntu 14.04.2 with the default linux- generic 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, overlayfs: allow unprivileged mounts is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the filesystem underlying overlayfs is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a virtual machine (qemu-system-x86_64). The host is ubuntu 14.04.2 with the default 3.13 kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463445] Re: CVE-2015-4003
** Changed in: linux (Ubuntu Wily) Status: Fix Released = 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/1463445 Title: CVE-2015-4003 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status
[Kernel-packages] [Bug 1486188] [NEW] hid_magicmouse freeze periodicaly and on rmmod
Public bug reported: hid_magicmouse freeze periodicaly and on rmmod ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: boot/vmlinuz-4.1.0-3-generic] ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: svlad 3269 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 18 21:34:14 2015 HibernationDevice: RESUME=UUID=4f6f6cec-e985-44ce-b7ba-e7afe11819e1 InstallationDate: Installed on 2015-08-07 (10 days ago) InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150807) MachineType: System manufacturer P5K-E ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 SourcePackage: linux UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1305 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1305:bd06/19/2009:svnSystemmanufacturer:pnP5K-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5K-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486188 Title: hid_magicmouse freeze periodicaly and on rmmod Status in linux package in Ubuntu: New Bug description: hid_magicmouse freeze periodicaly and on rmmod ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: boot/vmlinuz-4.1.0-3-generic] ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: svlad 3269 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 18 21:34:14 2015 HibernationDevice: RESUME=UUID=4f6f6cec-e985-44ce-b7ba-e7afe11819e1 InstallationDate: Installed on 2015-08-07 (10 days ago) InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150807) MachineType: System manufacturer P5K-E ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 SourcePackage: linux UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1305 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1305:bd06/19/2009:svnSystemmanufacturer:pnP5K-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5K-E 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/1486188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485127] onibi (i386) - tests ran: 153, failed: 1
tests ran: 153, failed: 1; http://kernel.ubuntu.com/testing/onibi__3.16.0-47.63~14.04.1__2015-08-18_16-53-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1485127 Title: linux-lts-utopic: 3.16.0-47.63~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-47.63~14.04.1 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:Friday, 14. August 2015 22:17 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1143815] Re: CVE-2013-1767
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Wily) Status: New = Invalid ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: Fix Committed = 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/1143815 Title: CVE-2013-1767 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: 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-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid Status in linux-lts-backport-oneiric source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty:
[Kernel-packages] [Bug 1485173] Re: linux-lts-trusty: 3.13.0-63.104~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released = New ** Changed in: kernel-sru-workflow/package-testing Status: Confirmed = New ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released = New ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed = New ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released = New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1485173 Title: linux-lts-trusty: 3.13.0-63.104~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: New Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-63.104~precise1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Saturday, 15. August 2015 05:03 UTC kernel-stable-master-bug:1485102 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Sunday, 16. August 2015 12:02 UTC kernel-stable-Promote-to-proposed-start:Sunday, 16. August 2015 12:02 UTC kernel-stable-phase-changed:Sunday, 16. August 2015 12:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486147] [NEW] package linux-image-extra-3.13.0-62-generic 3.13.0-62.102 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: was removing/trying to remove old kernels with this command /etc/kernel/postinst.d/apt-auto-removal and apt-get auto-remove ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ris2550 F pulseaudio /dev/snd/controlC0: ris2550 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Aug 18 08:07:45 2015 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=170b4129-57c6-43d9-b974-80ea94c8255b InstallationDate: Installed on 2014-02-04 (559 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130214) MachineType: Hewlett-Packard HP Compaq dc5850 Small Form Factor ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-62-generic root=/dev/mapper/hostname-root ro quiet splash 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-9ubuntu1.3 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-62-generic 3.13.0-62.102 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-05-30 (444 days ago) dmi.bios.date: 02/26/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F6 v03.04 dmi.board.name: 3029h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9250PD9 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F6v03.04:bd02/26/2009:svnHewlett-Packard:pnHPCompaqdc5850SmallFormFactor:pvr:rvnHewlett-Packard:rn3029h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq dc5850 Small Form Factor dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486147 Title: package linux-image-extra-3.13.0-62-generic 3.13.0-62.102 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux package in Ubuntu: New Bug description: was removing/trying to remove old kernels with this command /etc/kernel/postinst.d/apt-auto-removal and apt-get auto-remove ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ris2550 F pulseaudio /dev/snd/controlC0: ris2550 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Aug 18 08:07:45 2015 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=170b4129-57c6-43d9-b974-80ea94c8255b InstallationDate: Installed on 2014-02-04 (559 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130214) MachineType: Hewlett-Packard HP Compaq dc5850 Small Form Factor ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-62-generic root=/dev/mapper/hostname-root ro quiet splash 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-9ubuntu1.3 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-62-generic 3.13.0-62.102 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-05-30 (444 days ago) dmi.bios.date: 02/26/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F6 v03.04 dmi.board.name: 3029h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9250PD9 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F6v03.04:bd02/26/2009:svnHewlett-Packard:pnHPCompaqdc5850SmallFormFactor:pvr:rvnHewlett-Packard:rn3029h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq dc5850 Small Form Factor dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486147/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1486146] [NEW] recvfrom SYSCALL infinite loop/deadlock chewing 100% CPU (MSG_PEEK|MSG_WAITALL)
Public bug reported: In a multi-threaded pthreads process running on Ubuntu 14.04 AMD64 (with over 1000 threads) which uses real time FIFO scheduling, we occasionally see calls to recv() with flags (MSG_PEEK | MSG_WAITALL) get stuck in an infinte loop or deadlock meaning the threads lock up chewing as much CPU as they can (due to FIFO scheduling) while stuck inside recv(). Here's an example gdb back trace: [Switching to thread 4 (Thread 0x7f6040546700 (LWP 27251))] #0 0x7f6231d2f7eb in __libc_recv (fd=fd@entry=146, buf=buf@entry=0x7f6040543600, n=n@entry=5, flags=-1, flags@entry=258) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33 33 ../sysdeps/unix/sysv/linux/x86_64/recv.c: No such file or directory. (gdb) bt #0 0x7f6231d2f7eb in __libc_recv (fd=fd@entry=146, buf=buf@entry=0x7f6040543600, n=n@entry=5, flags=-1, flags@entry=258) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33 #1 0x00421945 in recv (__flags=258, __n=5, __buf=0x7f6040543600, __fd=146) at /usr/include/x86_64-linux-gnu/bits/socket2.h:44 [snip] The socket is a TCP socket in blocking mode, the recv() call is inside an outer loop with a counter, and I've checked the counter with gdb and it's always at 1, meaning that I'm sure that the outer loop isn't the problem, the thread is indeed deadlocked inside the recv() internals. Other nodes: * There always seems to be 2 or more threads deadlocked in the same place (same recv() call but with distinct FDs) * The threads calling recv() have cancellation disbaled by previously executing: thread_setcancelstate(PTHREAD_CANCEL_DISABLE, NULL); I've even tried adding a poll() call for POLLRDNORM on the socket before calling recv() with MSG_PEEK | MSG_WAITALL flags to try to make sure there's data available on the socket before calling *recv()*, but it makes no difference. So, I don't know what is wrong here, I've read all the recv() documentation and believe that recv() is being used correctly, the only conclusion I can come to is that there is a bug in libc recv() when using flags MSG_PEEK | MSG_WAITALL with thousands of pthreads running. ** Affects: linux Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: High Status: Triaged ** Tags: kernel-da-key trusty ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Status: New = Triaged ** Bug watch added: Linux Kernel Bug Tracker #99461 http://bugzilla.kernel.org/show_bug.cgi?id=99461 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=99461 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486146 Title: recvfrom SYSCALL infinite loop/deadlock chewing 100% CPU (MSG_PEEK|MSG_WAITALL) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: In a multi-threaded pthreads process running on Ubuntu 14.04 AMD64 (with over 1000 threads) which uses real time FIFO scheduling, we occasionally see calls to recv() with flags (MSG_PEEK | MSG_WAITALL) get stuck in an infinte loop or deadlock meaning the threads lock up chewing as much CPU as they can (due to FIFO scheduling) while stuck inside recv(). Here's an example gdb back trace: [Switching to thread 4 (Thread 0x7f6040546700 (LWP 27251))] #0 0x7f6231d2f7eb in __libc_recv (fd=fd@entry=146, buf=buf@entry=0x7f6040543600, n=n@entry=5, flags=-1, flags@entry=258) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33 33 ../sysdeps/unix/sysv/linux/x86_64/recv.c: No such file or directory. (gdb) bt #0 0x7f6231d2f7eb in __libc_recv (fd=fd@entry=146, buf=buf@entry=0x7f6040543600, n=n@entry=5, flags=-1, flags@entry=258) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33 #1 0x00421945 in recv (__flags=258, __n=5, __buf=0x7f6040543600, __fd=146) at /usr/include/x86_64-linux-gnu/bits/socket2.h:44 [snip] The socket is a TCP socket in blocking mode, the recv() call is inside an outer loop with a counter, and I've checked the counter with gdb and it's always at 1, meaning that I'm sure that the outer loop isn't the problem, the thread is indeed deadlocked inside the recv() internals. Other nodes: * There always seems to be 2 or more threads deadlocked in the same place (same recv() call but with distinct FDs) * The threads calling recv() have cancellation disbaled by previously executing: thread_setcancelstate(PTHREAD_CANCEL_DISABLE, NULL); I've even tried adding a poll() call for POLLRDNORM on the socket before calling recv() with MSG_PEEK | MSG_WAITALL flags to try to make sure there's data available on the socket before calling *recv()*, but it makes no difference. So, I don't know what is wrong here, I've read all the recv() documentation and believe that recv() is being used correctly, the only
[Kernel-packages] [Bug 1486146] Re: recvfrom SYSCALL infinite loop/deadlock chewing 100% CPU (MSG_PEEK|MSG_WAITALL)
According to the upstream bug: This bug is now fixed in the net tree: https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=dfbafc995304ebb9a9b03f65083e6e9cea143b20; This commit is already applied to mainline: $ git describe --contains dfbafc995304ebb9a9b03f65083e6e9cea143b20 v4.2-rc5~9^2~26 commit dfbafc995304ebb9a9b03f65083e6e9cea143b20 Author: Sabrina Dubroca s...@queasysnail.net Date: Fri Jul 24 18:19:25 2015 +0200 tcp: fix recv with flags MSG_WAITALL | MSG_PEEK -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486146 Title: recvfrom SYSCALL infinite loop/deadlock chewing 100% CPU (MSG_PEEK|MSG_WAITALL) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: In a multi-threaded pthreads process running on Ubuntu 14.04 AMD64 (with over 1000 threads) which uses real time FIFO scheduling, we occasionally see calls to recv() with flags (MSG_PEEK | MSG_WAITALL) get stuck in an infinte loop or deadlock meaning the threads lock up chewing as much CPU as they can (due to FIFO scheduling) while stuck inside recv(). Here's an example gdb back trace: [Switching to thread 4 (Thread 0x7f6040546700 (LWP 27251))] #0 0x7f6231d2f7eb in __libc_recv (fd=fd@entry=146, buf=buf@entry=0x7f6040543600, n=n@entry=5, flags=-1, flags@entry=258) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33 33 ../sysdeps/unix/sysv/linux/x86_64/recv.c: No such file or directory. (gdb) bt #0 0x7f6231d2f7eb in __libc_recv (fd=fd@entry=146, buf=buf@entry=0x7f6040543600, n=n@entry=5, flags=-1, flags@entry=258) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33 #1 0x00421945 in recv (__flags=258, __n=5, __buf=0x7f6040543600, __fd=146) at /usr/include/x86_64-linux-gnu/bits/socket2.h:44 [snip] The socket is a TCP socket in blocking mode, the recv() call is inside an outer loop with a counter, and I've checked the counter with gdb and it's always at 1, meaning that I'm sure that the outer loop isn't the problem, the thread is indeed deadlocked inside the recv() internals. Other nodes: * There always seems to be 2 or more threads deadlocked in the same place (same recv() call but with distinct FDs) * The threads calling recv() have cancellation disbaled by previously executing: thread_setcancelstate(PTHREAD_CANCEL_DISABLE, NULL); I've even tried adding a poll() call for POLLRDNORM on the socket before calling recv() with MSG_PEEK | MSG_WAITALL flags to try to make sure there's data available on the socket before calling *recv()*, but it makes no difference. So, I don't know what is wrong here, I've read all the recv() documentation and believe that recv() is being used correctly, the only conclusion I can come to is that there is a bug in libc recv() when using flags MSG_PEEK | MSG_WAITALL with thousands of pthreads running. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1486146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1152788] Re: CVE-2013-1792
** Changed in: linux (Ubuntu Trusty) Assignee: Luis Henriques (henrix) = (unassigned) ** Changed in: linux (Ubuntu Vivid) Assignee: Luis Henriques (henrix) = (unassigned) ** Changed in: linux (Ubuntu Wily) Assignee: Luis Henriques (henrix) = (unassigned) -- 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/1152788 Title: CVE-2013-1792 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid Status in linux-lts-backport-oneiric source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty:
[Kernel-packages] [Bug 1485127] fozzie (amd64) - tests ran: 180, failed: 2
tests ran: 180, failed: 2; http://kernel.ubuntu.com/testing/fozzie__3.16.0-47.63~14.04.1__2015-08-18_15-17-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1485127 Title: linux-lts-utopic: 3.16.0-47.63~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-47.63~14.04.1 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:Friday, 14. August 2015 22:17 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486163] [NEW] package linux-image-extra-3.16.0-46-generic 3.16.0-46.62~14.04.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado
Public bug reported: Erro de instalação de programa ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.16.0-46-generic 3.16.0-46.62~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14 Uname: Linux 3.16.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Aug 18 14:20:53 2015 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2015-06-21 (58 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic Title: package linux-image-extra-3.16.0-46-generic 3.16.0-46.62~14.04.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1486163 Title: package linux-image-extra-3.16.0-46-generic 3.16.0-46.62~14.04.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado Status in linux-lts-utopic package in Ubuntu: New Bug description: Erro de instalação de programa ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.16.0-46-generic 3.16.0-46.62~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14 Uname: Linux 3.16.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Aug 18 14:20:53 2015 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2015-06-21 (58 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic Title: package linux-image-extra-3.16.0-46-generic 3.16.0-46.62~14.04.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1486163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 899466] Re: CVE-2011-2203
** Changed in: linux (Ubuntu Wily) Status: Fix Released = Invalid ** Changed in: linux (Ubuntu Vivid) Status: Fix Released = Invalid ** Changed in: linux (Ubuntu Trusty) Status: Fix Released = Invalid ** Changed in: linux (Ubuntu Precise) Status: Fix Released = Invalid ** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Released = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Released = Invalid ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: Fix Committed = 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/899466 Title: CVE-2011-2203 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Fix Released Status in linux-lts-backport-natty source package in Lucid: Fix Released Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid Status in linux-lts-backport-oneiric source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty:
[Kernel-packages] [Bug 1457807] Re: CVE-2015-4036
** Changed in: linux (Ubuntu Wily) Status: Fix Released = 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/1457807 Title: CVE-2015-4036 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: Invalid Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package
[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
Ah, sorry. I thought you were trying to manually delete the whole container (instead of using lxc-destroy). ** Changed in: lxc (Ubuntu) Status: Invalid = New ** Changed in: linux (Ubuntu) Status: Invalid = New ** Changed in: linux (Ubuntu) Status: New = Confirmed ** Changed in: lxc (Ubuntu) Status: New = Confirmed ** Changed in: lxc (Ubuntu) Importance: Undecided = Medium ** Changed in: lxc (Ubuntu) Importance: Medium = High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, rm: cannot remove ‘mntpt/foo’: Operation not permitted strace shows, unlinkat(AT_FDCWD, mntpt/foo, AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel (3.19). The bug does not occur on ubuntu 14.04.2 with the default linux- generic 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, overlayfs: allow unprivileged mounts is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the filesystem underlying overlayfs is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a virtual machine (qemu-system-x86_64). The host is ubuntu 14.04.2 with the default 3.13 kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486153] 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/1486153 Title: fglrx-core: fglrx-core kernel module failed to build Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade to kernel version 3.19.0-26-generic fglrx fails to build the needed DKMS module and renders the GUI non-functional. Had to remove all fglrx packages to get a working Xsession again. Converting back to 3.19.0-25 solved the DKMS module building problem. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 3.19.0-26-generic Date: Tue Aug 18 19:12:54 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.200, 3.19.0-25-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2015-08-07 (10 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageVersion: (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=19317e49-95e5-41ee-8908-8a05165ac80c ro vga=0x0368 quiet splash nomodeset video=uvesafb:mode_option=1920x1080-24,mtrr=3,scroll=ywrap vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: fglrx-installer Title: fglrx-core (not installed): fglrx-core kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/09/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Aug 18 19:13:52 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486147] 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/1486147 Title: package linux-image-extra-3.13.0-62-generic 3.13.0-62.102 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: was removing/trying to remove old kernels with this command /etc/kernel/postinst.d/apt-auto-removal and apt-get auto-remove ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ris2550 F pulseaudio /dev/snd/controlC0: ris2550 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Aug 18 08:07:45 2015 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=170b4129-57c6-43d9-b974-80ea94c8255b InstallationDate: Installed on 2014-02-04 (559 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130214) MachineType: Hewlett-Packard HP Compaq dc5850 Small Form Factor ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-62-generic root=/dev/mapper/hostname-root ro quiet splash 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-9ubuntu1.3 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-62-generic 3.13.0-62.102 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-05-30 (444 days ago) dmi.bios.date: 02/26/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F6 v03.04 dmi.board.name: 3029h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA9250PD9 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F6v03.04:bd02/26/2009:svnHewlett-Packard:pnHPCompaqdc5850SmallFormFactor:pvr:rvnHewlett-Packard:rn3029h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq dc5850 Small Form Factor dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438504] Re: CVE-2015-2666
** Changed in: linux (Ubuntu Vivid) Status: Fix Released = Invalid ** Changed in: linux (Ubuntu Wily) Status: Fix Released = Invalid ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: Fix Committed = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Invalid = Won't Fix ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Invalid = Won't Fix ** No longer affects: linux-lts-backport-maverick (Ubuntu) ** No longer affects: linux-lts-backport-maverick (Ubuntu Lucid) ** No longer affects: linux-lts-backport-maverick (Ubuntu Precise) ** No longer affects: linux-lts-backport-maverick (Ubuntu Trusty) ** No longer affects: linux-lts-backport-maverick (Ubuntu Utopic) ** No longer affects: linux-lts-backport-maverick (Ubuntu Vivid) ** No longer affects: linux-lts-backport-maverick (Ubuntu Wily) ** No longer affects: linux-lts-backport-natty (Ubuntu Wily) ** No longer affects: linux-lts-backport-natty (Ubuntu Vivid) ** No longer affects: linux-lts-backport-natty (Ubuntu Utopic) ** No longer affects: linux-lts-backport-natty (Ubuntu Trusty) ** No longer affects: linux-lts-backport-natty (Ubuntu Precise) ** No longer affects: linux-lts-backport-natty (Ubuntu Lucid) ** No longer affects: linux-lts-backport-natty (Ubuntu) ** Description changed: - [execution in the early microcode loader x86/intel] Guard against stack - overflow in the loader mc_saved_tmp is a static array allocated on the - stack, we need to make sure mc_saved_count stays within its bounds, - otherwise we're overflowing the stack in _save_mc(). A specially crafted - microcode header could lead to a kernel crash or potentially kernel - execution. + Stack-based buffer overflow in the get_matching_model_microcode function in + arch/x86/kernel/cpu/microcode/intel_early.c in the Linux kernel before 4.0 + allows context-dependent attackers to gain privileges by constructing a + crafted microcode header and leveraging root privileges for write access to + the initrd. Break-Fix: ec400ddeff200b068ddc6c70f7321f49ecf32ed5 f84598bd7c851f8b0bf8cd0d7c3be0d73c432ff4 -- 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/1438504 Title: CVE-2015-2666 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Won't Fix Status in linux-lts-saucy source package in Precise: Won't Fix Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty:
[Kernel-packages] [Bug 1485173] Re: linux-lts-trusty: 3.13.0-63.104~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Brad Figg (brad-figg) = Luis Henriques (henrix) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1485173 Title: linux-lts-trusty: 3.13.0-63.104~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: New Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-63.104~precise1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Saturday, 15. August 2015 05:03 UTC kernel-stable-master-bug:1485102 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Sunday, 16. August 2015 12:02 UTC kernel-stable-Promote-to-proposed-start:Sunday, 16. August 2015 12:02 UTC kernel-stable-phase-changed:Sunday, 16. August 2015 12:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485113] larsen (i386) - tests ran: 167, failed: 0
tests ran: 167, failed: 0; http://kernel.ubuntu.com/testing/larsen__3.19.0-27.29__2015-08-18_14-55-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485113 Title: linux: 3.19.0-27.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-27.29 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:Friday, 14. August 2015 20:50 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486188] 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/1486188 Title: hid_magicmouse freeze periodicaly and on rmmod Status in linux package in Ubuntu: Confirmed Bug description: hid_magicmouse freeze periodicaly and on rmmod ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: boot/vmlinuz-4.1.0-3-generic] ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: svlad 3269 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 18 21:34:14 2015 HibernationDevice: RESUME=UUID=4f6f6cec-e985-44ce-b7ba-e7afe11819e1 InstallationDate: Installed on 2015-08-07 (10 days ago) InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150807) MachineType: System manufacturer P5K-E ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 SourcePackage: linux UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1305 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1305:bd06/19/2009:svnSystemmanufacturer:pnP5K-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5K-E 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/1486188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485173] Re: linux-lts-trusty: 3.13.0-63.104~precise1 -proposed tracker
** Changed in: linux-lts-trusty (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1485173 Title: linux-lts-trusty: 3.13.0-63.104~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-63.104~precise1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Saturday, 15. August 2015 05:03 UTC kernel-stable-master-bug:1485102 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Sunday, 16. August 2015 12:02 UTC kernel-stable-Promote-to-proposed-start:Sunday, 16. August 2015 12:02 UTC kernel-stable-phase-changed:Sunday, 16. August 2015 12:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485127] fozzie (i386) - tests ran: 153, failed: 1
tests ran: 153, failed: 1; http://kernel.ubuntu.com/testing/fozzie__3.16.0-47.63~14.04.1__2015-08-18_17-45-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1485127 Title: linux-lts-utopic: 3.16.0-47.63~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-47.63~14.04.1 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:Friday, 14. August 2015 22:17 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458876] Comment bridged from LTC Bugzilla
--- Comment From stros...@us.ibm.com 2015-08-18 21:27 EDT--- The patches for seccomp mode 2 support are queued for 4.3; as they were developed against 4.2, I would expect them to apply cleanly to the Ubuntu 15.10 kernel. I am willing to help with backporting if they don't, or if other modifications to the Ubuntu kernel cause issues with applying them. There were 11 patches in the patchset: [PATCH 01/11] powerpc/kernel: Switch to using MAX_ERRNO https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-July/131601.html [PATCH 02/11] powerpc/kernel: Change the do_syscall_trace_enter() API https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-July/131602.html [PATCH 03/11] powerpc: Drop unused syscall_get_error() https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-July/131603.html [PATCH 04/11] powerpc: Don't negate error in syscall_set_return_value() https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-July/131604.html [PATCH 05/11] powerpc: Rework syscall_get_arguments() so there is only one loop https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-July/131605.html [PATCH 06/11] powerpc: Use orig_gpr3 in syscall_get_arguments() https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-July/131606.html [PATCH 07/11] powerpc: Change syscall_get_nr() to return int https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-July/131607.html [PATCH 08/11] powerpc/kernel: Add SIG_SYS support for compat tasks https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-July/131608.html [PATCH 09/11] powerpc/kernel: Enable seccomp filter https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-July/131609.html [PATCH 10/11] selftests/seccomp: Make seccomp tests work on big endian https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-July/131610.html [PATCH 11/11] selftests/seccomp: Add powerpc support https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-July/131611.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458876 Title: [Ubuntu 15.10] Add seccomp mode 2 to the Ubuntu Power LE kernel Status in linux package in Ubuntu: Confirmed Bug description: seccomp mode 2 involves the parsing of BPF (Berkeley Packet Filter) configuration files to define system call filtering. Mode 2 is not currently supported on Power; this feature covers the addition of this support, which likely includes updates to the kernel and to libseccomp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486180] [NEW] Kernel OOPS during DLPAR operation with Fibre Channel adapter
You have been subscribed to a public bug: -- Problem Description -- Kernel OOPS during DLPAR operation with Fibre Channel adapter ---uname output--- 4.1.0-1-generic ---Additional Hardware Info--- Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) Machine Type = POWER8 ---Steps to Reproduce--- 1) Install Ubuntu 15.10 on a Power VM LPAR. 2) Configure and start rtas_errd daemon 3) Via HMC try to add a Fibre channel adapter via dynamic partitioning During the operation following OOPS message is observed Oops output: !!! 00E0806 Fcode, Copyright (c) 2000-2012 Emulex !!! Version 3.10x2 !!! 00E0806 Fcode, Copyright (c) 2000-2012 Emulex !!! Version 3.10x2 [ 8696.808703] PCI host bridge /pci@8002020 ranges: [ 8696.808708] MEM 0x0003ff84..0x0003ff847eff - 0x8000 [ 8696.808716] PCI: I/O resource not set for host bridge /pci@8002020 (domain 1) [ 8696.808761] PCI host bridge to bus 0001:01 [ 8696.808765] pci_bus 0001:01: root bus resource [mem 0x3ff84-0x3ff847eff] (bus address [0x8000-0xfeff]) [ 8696.808768] pci_bus 0001:01: root bus resource [bus 01-ff] [ 8696.897390] rpaphp: Slot [U78C7.001.RCH0042-P1-C8] registered [ 8696.897395] rpadlpar_io: slot PHB 32 added [ 8696.972155] Emulex LightPulse Fibre Channel SCSI driver 10.5.0.0. [ 8696.972157] Copyright(c) 2004-2015 Emulex. All rights reserved. [ 8696.972438] lpfc 0001:01:00.1: enabling device (0140 - 0142) [ 8696.976145] Unable to handle kernel paging request for data at address 0x000c [ 8696.976174] Faulting instruction address: 0xc0084cc4 [ 8696.976182] Oops: Kernel access of bad area, sig: 11 [#1] [ 8696.976188] SMP NR_CPUS=2048 NUMA pSeries [ 8696.976196] Modules linked in: lpfc(+) scsi_transport_fc rpadlpar_io rpaphp rtc_generic pseries_rng autofs4 [ 8696.976220] CPU: 3 PID: 1426 Comm: systemd-udevd Not tainted 4.1.0-1-generic #1~dogfoodv1-Ubuntu [ 8696.976230] task: c003857737e0 ti: c000fd08c000 task.ti: c000fd08c000 [ 8696.976239] NIP: c0084cc4 LR: c0084ca8 CTR: [ 8696.976247] REGS: c000fd08f0f0 TRAP: 0300 Not tainted (4.1.0-1-generic) [ 8696.976255] MSR: 80019033 SF,EE,ME,IR,DR,RI,LE CR: 8222 XER: 2000 [ 8696.976278] CFAR: c0008468 DAR: 000c DSISR: 4000 SOFTE: 1 GPR00: c0084ca8 c000fd08f370 c14bda00 GPR04: 0001 c000fd08f408 0003 d2c31e60 GPR08: c13bda00 c003873e6b80 d2ca7c98 GPR12: 8800 ce831b00 d29421f8 38ca4522 GPR16: c000fd08fdc0 c000fd08fe04 d2941878 c000fc8054c0 GPR20: d238 d238 d2ccff90 GPR24: c165074c c0038e17e000 c13b5e00 c0038e17e000 GPR28: c13b5e28 ca590600 c13b5df0 c13b5e20 [ 8696.976396] NIP [c0084cc4] enable_ddw+0x254/0x7b0 [ 8696.976405] LR [c0084ca8] enable_ddw+0x238/0x7b0 [ 8696.976411] Call Trace: [ 8696.976419] [c000fd08f370] [c0084ca8] enable_ddw+0x238/0x7b0 (unreliable) [ 8696.976431] [c000fd08f4b0] [c00866d8] dma_set_mask_pSeriesLP+0x218/0x2a0 [ 8696.976444] [c000fd08f540] [c0023528] dma_set_mask+0x58/0xa0 [ 8696.976474] [c000fd08f570] [d2c71280] lpfc_pci_probe_one+0xb0/0xc50 [lpfc] [ 8696.976486] [c000fd08f610] [c05987fc] local_pci_probe+0x6c/0x140 [ 8696.976497] [c000fd08f6a0] [c0598a28] pci_device_probe+0x158/0x1e0 [ 8696.976510] [c000fd08f700] [c067b744] driver_probe_device+0x1c4/0x5a0 [ 8696.976522] [c000fd08f790] [c067bcdc] __driver_attach+0x11c/0x120 [ 8696.976533] [c000fd08f7d0] [c067854c] bus_for_each_dev+0x9c/0x110 [ 8696.976544] [c000fd08f820] [c067adbc] driver_attach+0x3c/0x60 [ 8696.976555] [c000fd08f850] [c067a768] bus_add_driver+0x208/0x320 [ 8696.976565] [c000fd08f8e0] [c067c99c] driver_register+0x9c/0x180 [ 8696.976576] [c000fd08f950] [c05978ec] __pci_register_driver+0x6c/0x90 [ 8696.976604] [c000fd08f990] [d2ca7848] lpfc_init+0x17c/0x1d8 [lpfc] [ 8696.976617] [c000fd08fa20] [c000b42c] do_one_initcall+0x12c/0x280 [ 8696.976628] [c000fd08faf0] [c0a6c7c8] do_init_module+0x98/0x238 [ 8696.976640] [c000fd08fb80] [c0163fa4] load_module+0x1354/0x14d0 [ 8696.976651] [c000fd08fd50] [c01643d0] SyS_finit_module+0xc0/0x120 [ 8696.976662] [c000fd08fe30] [c00091fc] system_call+0x38/0xb4 [ 8696.976669] Instruction dump: [ 8696.976675] 7fa3eb78 38842388 38a10090 38c3 488345a5 6000 2fa3 409e0170 [ 8696.976694] 2fb9 419e0438 ea7902f0
[Kernel-packages] [Bug 1486180] Re: Kernel OOPS during DLPAR operation with Fibre Channel adapter
** Package changed: ubuntu = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486180 Title: Kernel OOPS during DLPAR operation with Fibre Channel adapter Status in linux package in Ubuntu: New Bug description: -- Problem Description -- Kernel OOPS during DLPAR operation with Fibre Channel adapter ---uname output--- 4.1.0-1-generic ---Additional Hardware Info--- Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) Machine Type = POWER8 ---Steps to Reproduce--- 1) Install Ubuntu 15.10 on a Power VM LPAR. 2) Configure and start rtas_errd daemon 3) Via HMC try to add a Fibre channel adapter via dynamic partitioning During the operation following OOPS message is observed Oops output: !!! 00E0806 Fcode, Copyright (c) 2000-2012 Emulex !!! Version 3.10x2 !!! 00E0806 Fcode, Copyright (c) 2000-2012 Emulex !!! Version 3.10x2 [ 8696.808703] PCI host bridge /pci@8002020 ranges: [ 8696.808708] MEM 0x0003ff84..0x0003ff847eff - 0x8000 [ 8696.808716] PCI: I/O resource not set for host bridge /pci@8002020 (domain 1) [ 8696.808761] PCI host bridge to bus 0001:01 [ 8696.808765] pci_bus 0001:01: root bus resource [mem 0x3ff84-0x3ff847eff] (bus address [0x8000-0xfeff]) [ 8696.808768] pci_bus 0001:01: root bus resource [bus 01-ff] [ 8696.897390] rpaphp: Slot [U78C7.001.RCH0042-P1-C8] registered [ 8696.897395] rpadlpar_io: slot PHB 32 added [ 8696.972155] Emulex LightPulse Fibre Channel SCSI driver 10.5.0.0. [ 8696.972157] Copyright(c) 2004-2015 Emulex. All rights reserved. [ 8696.972438] lpfc 0001:01:00.1: enabling device (0140 - 0142) [ 8696.976145] Unable to handle kernel paging request for data at address 0x000c [ 8696.976174] Faulting instruction address: 0xc0084cc4 [ 8696.976182] Oops: Kernel access of bad area, sig: 11 [#1] [ 8696.976188] SMP NR_CPUS=2048 NUMA pSeries [ 8696.976196] Modules linked in: lpfc(+) scsi_transport_fc rpadlpar_io rpaphp rtc_generic pseries_rng autofs4 [ 8696.976220] CPU: 3 PID: 1426 Comm: systemd-udevd Not tainted 4.1.0-1-generic #1~dogfoodv1-Ubuntu [ 8696.976230] task: c003857737e0 ti: c000fd08c000 task.ti: c000fd08c000 [ 8696.976239] NIP: c0084cc4 LR: c0084ca8 CTR: [ 8696.976247] REGS: c000fd08f0f0 TRAP: 0300 Not tainted (4.1.0-1-generic) [ 8696.976255] MSR: 80019033 SF,EE,ME,IR,DR,RI,LE CR: 8222 XER: 2000 [ 8696.976278] CFAR: c0008468 DAR: 000c DSISR: 4000 SOFTE: 1 GPR00: c0084ca8 c000fd08f370 c14bda00 GPR04: 0001 c000fd08f408 0003 d2c31e60 GPR08: c13bda00 c003873e6b80 d2ca7c98 GPR12: 8800 ce831b00 d29421f8 38ca4522 GPR16: c000fd08fdc0 c000fd08fe04 d2941878 c000fc8054c0 GPR20: d238 d238 d2ccff90 GPR24: c165074c c0038e17e000 c13b5e00 c0038e17e000 GPR28: c13b5e28 ca590600 c13b5df0 c13b5e20 [ 8696.976396] NIP [c0084cc4] enable_ddw+0x254/0x7b0 [ 8696.976405] LR [c0084ca8] enable_ddw+0x238/0x7b0 [ 8696.976411] Call Trace: [ 8696.976419] [c000fd08f370] [c0084ca8] enable_ddw+0x238/0x7b0 (unreliable) [ 8696.976431] [c000fd08f4b0] [c00866d8] dma_set_mask_pSeriesLP+0x218/0x2a0 [ 8696.976444] [c000fd08f540] [c0023528] dma_set_mask+0x58/0xa0 [ 8696.976474] [c000fd08f570] [d2c71280] lpfc_pci_probe_one+0xb0/0xc50 [lpfc] [ 8696.976486] [c000fd08f610] [c05987fc] local_pci_probe+0x6c/0x140 [ 8696.976497] [c000fd08f6a0] [c0598a28] pci_device_probe+0x158/0x1e0 [ 8696.976510] [c000fd08f700] [c067b744] driver_probe_device+0x1c4/0x5a0 [ 8696.976522] [c000fd08f790] [c067bcdc] __driver_attach+0x11c/0x120 [ 8696.976533] [c000fd08f7d0] [c067854c] bus_for_each_dev+0x9c/0x110 [ 8696.976544] [c000fd08f820] [c067adbc] driver_attach+0x3c/0x60 [ 8696.976555] [c000fd08f850] [c067a768] bus_add_driver+0x208/0x320 [ 8696.976565] [c000fd08f8e0] [c067c99c] driver_register+0x9c/0x180 [ 8696.976576] [c000fd08f950] [c05978ec] __pci_register_driver+0x6c/0x90 [ 8696.976604] [c000fd08f990] [d2ca7848] lpfc_init+0x17c/0x1d8 [lpfc] [ 8696.976617] [c000fd08fa20] [c000b42c] do_one_initcall+0x12c/0x280 [ 8696.976628] [c000fd08faf0]
[Kernel-packages] [Bug 1480894] Re: Frequency in Psafe after an OCC reset cycle while using performance governor
** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: New = Triaged ** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) = Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480894 Title: Frequency in Psafe after an OCC reset cycle while using performance governor Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Shilpasri G. Bhat shigb...@in.ibm.com - 2015-05-08 14:27:37 == ---Problem Description--- Frequency is not restored on a reset-cycle of OCC which can lead to performance degradation when using performance-governor. When OCC is reset it forces the cpu to safe frequency, after OCC becomes active again the frequency is not restored to max frequency if the governor is performance-governor or to the last requested frequency for other static governors. Contact Information = Shilpasri G Bhat / shilpa.b...@linux.vnet.ibm.com ---Steps to Reproduce--- 1) select performance governor 2) OCC reset cycle Fix for this is posted to lkml: https://lkml.org/lkml/2015/5/4/136 == Comment: #1 - Shilpasri G. Bhat shigb...@in.ibm.com - 2015-08-03 06:56:15 == Fyi ... v4 of the patches which were posted at https://lkml.org/lkml/2015/7/13/375 ([PATCH v4 0/6] powernv: cpufreq: Report frequency throttle by OCC) with the following 6 patches: cpufreq: powernv: Handle throttling due to Pmax capping at chip level powerpc/powernv: Add definition of OPAL_MSG_OCC message type cpufreq: powernv: Register for OCC related opal_message notification cpufreq: powernv: Call throttle_check() on receiving OCC_THROTTLE cpufreq: powernv: Report Psafe only if PMSR.psafe_mode_active bit is set cpufreq: powernv: Restore cpu frequency to policy-cur on unthrottling . ... is now accepted upstream as follows: 1) https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=053819e0bf8407746cc5febf7a4947bee50377b4 (cpufreq: powernv: Handle throttling due to Pmax capping at chip level) . 2) https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=196ba2d514a13f6af1b3d78de71ce74ed2fc8bdc (powerpc/powernv: Add definition of OPAL_MSG_OCC message type) . 3) https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=cb166fa937a2fbc14badcafca86202354c34a213 (cpufreq: powernv: Register for OCC related opal_message notification) . 4) https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=735366fc407755626058218fc8d0430735a669ac (cpufreq: powernv: Call throttle_check() on receiving OCC_THROTTLE) . 5) https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=3dd3ebe5bb3837aeac28a23f8f22b97cb84abab6 (cpufreq: powernv: Report Psafe only if PMSR.psafe_mode_active bit is set) . 6) https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=227942809b52f23cda414858b635c0285f11de00 (cpufreq: powernv: Restore cpu frequency to policy-cur on unthrottling) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485127] larsen (amd64) - tests ran: 180, failed: 5
tests ran: 180, failed: 5; http://kernel.ubuntu.com/testing/larsen__3.16.0-47.63~14.04.1__2015-08-18_18-31-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1485127 Title: linux-lts-utopic: 3.16.0-47.63~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-47.63~14.04.1 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:Friday, 14. August 2015 22:17 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485113] tarf (i386) - tests ran: 170, failed: 1
tests ran: 170, failed: 1; http://kernel.ubuntu.com/testing/tarf__3.19.0-27.29__2015-08-18_15-20-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485113 Title: linux: 3.19.0-27.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-27.29 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:Friday, 14. August 2015 20:50 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485184] fozzie (amd64) - tests ran: 180, failed: 1
tests ran: 180, failed: 1; http://kernel.ubuntu.com/testing/fozzie__3.19.0-27.29~14.04.1__2015-08-18_20-11-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1485184 Title: linux-lts-vivid: 3.19.0-27.29~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: New Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-27.29~14.04.1 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:Saturday, 15. August 2015 07:02 UTC kernel-stable-master-bug:1485113 kernel-stable-Prepare-package-end:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-start:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:04 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480894] Re: Frequency in Psafe after an OCC reset cycle while using performance governor
** Package changed: ubuntu = linux (Ubuntu) ** Changed in: linux (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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1480894 Title: Frequency in Psafe after an OCC reset cycle while using performance governor Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Shilpasri G. Bhat shigb...@in.ibm.com - 2015-05-08 14:27:37 == ---Problem Description--- Frequency is not restored on a reset-cycle of OCC which can lead to performance degradation when using performance-governor. When OCC is reset it forces the cpu to safe frequency, after OCC becomes active again the frequency is not restored to max frequency if the governor is performance-governor or to the last requested frequency for other static governors. Contact Information = Shilpasri G Bhat / shilpa.b...@linux.vnet.ibm.com ---Steps to Reproduce--- 1) select performance governor 2) OCC reset cycle Fix for this is posted to lkml: https://lkml.org/lkml/2015/5/4/136 == Comment: #1 - Shilpasri G. Bhat shigb...@in.ibm.com - 2015-08-03 06:56:15 == Fyi ... v4 of the patches which were posted at https://lkml.org/lkml/2015/7/13/375 ([PATCH v4 0/6] powernv: cpufreq: Report frequency throttle by OCC) with the following 6 patches: cpufreq: powernv: Handle throttling due to Pmax capping at chip level powerpc/powernv: Add definition of OPAL_MSG_OCC message type cpufreq: powernv: Register for OCC related opal_message notification cpufreq: powernv: Call throttle_check() on receiving OCC_THROTTLE cpufreq: powernv: Report Psafe only if PMSR.psafe_mode_active bit is set cpufreq: powernv: Restore cpu frequency to policy-cur on unthrottling . ... is now accepted upstream as follows: 1) https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=053819e0bf8407746cc5febf7a4947bee50377b4 (cpufreq: powernv: Handle throttling due to Pmax capping at chip level) . 2) https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=196ba2d514a13f6af1b3d78de71ce74ed2fc8bdc (powerpc/powernv: Add definition of OPAL_MSG_OCC message type) . 3) https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=cb166fa937a2fbc14badcafca86202354c34a213 (cpufreq: powernv: Register for OCC related opal_message notification) . 4) https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=735366fc407755626058218fc8d0430735a669ac (cpufreq: powernv: Call throttle_check() on receiving OCC_THROTTLE) . 5) https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=3dd3ebe5bb3837aeac28a23f8f22b97cb84abab6 (cpufreq: powernv: Report Psafe only if PMSR.psafe_mode_active bit is set) . 6) https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=227942809b52f23cda414858b635c0285f11de00 (cpufreq: powernv: Restore cpu frequency to policy-cur on unthrottling) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485184] onibi (amd64) - tests ran: 180, failed: 1
tests ran: 180, failed: 1; http://kernel.ubuntu.com/testing/onibi__3.19.0-27.29~14.04.1__2015-08-18_19-43-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1485184 Title: linux-lts-vivid: 3.19.0-27.29~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: New Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-27.29~14.04.1 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:Saturday, 15. August 2015 07:02 UTC kernel-stable-master-bug:1485113 kernel-stable-Prepare-package-end:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-start:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:04 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1482304] Re: Upgrade i40e and i40evf driver to latest
So I ended up upgrading the NVM to the latest version (f4.33.31377 a1.2 n4.42 e191b): https://downloadcenter.intel.com/download/24769/NVM-Update-Utility-for- Intel-Ethernet-Converged-Network-Adapter-XL710-X710-Series The 0.3.36-k now refuses to work at all throwing these messages into dmesg (no random kernel panic with the latest NVM, just doesn't work at all): [1.602924] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 0.3.36-k [1.602926] i40e: Copyright (c) 2013 - 2014 Intel Corporation. [1.613938] i40e :05:00.0: f4.33 a1.2 n04.42 e8000191b [1.613940] i40e :05:00.0: init_adminq failed: -65 expecting API 01.01 [1.613999] i40e: probe of :05:00.0 failed with error -65 [1.634901] i40e :05:00.1: Initial pf_reset failed: -15 [1.634962] i40e: probe of :05:00.1 failed with error -15 [1.646010] i40e :88:00.0: f4.33 a1.2 n04.42 e8000191b [1.646013] i40e :88:00.0: init_adminq failed: -65 expecting API 01.01 [1.646079] i40e: probe of :88:00.0 failed with error -65 [1.666925] i40e :88:00.1: Initial pf_reset failed: -15 [1.667004] i40e: probe of :88:00.1 failed with error -15 I then installed linux-generic-lts-vivid and that works without issue: root@ubuntu:~# ethtool -i p1p2 driver: i40e version: 1.2.2-k firmware-version: f4.33 a1.2 n04.42 e8000191b bus-info: :05:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no root@ubuntu:~# uname -a Linux ubuntu 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1482304 Title: Upgrade i40e and i40evf driver to latest Status in linux package in Ubuntu: Confirmed Bug description: It appears that the latest i40e driver in Trusty is 0.3.36-k. We've been experiencing some kernel panics with this driver and have found that it looks like bringing the driver up to the latest 1.2.48 has alleviated some of the kernel panics on boot. Is this something we could look at getting upgraded to a more modern revision of the driver? Thanks Output of Panic (Using Intel x710) [3.143088] i40e :05:00.0 p1p1: NIC Link is Up [3.301138] Switched to clocksource tsc [6.216639] random: nonblocking pool is initialized [8.934783] [ cut here ] [8.934805] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280() [8.934808] NETDEV WATCHDOG: p1p1 (i40e): transmit queue 0 timed out [8.934828] Modules linked in: joydev hid_generic 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 glue_helper ablk_helper cryptd serio_raw usbhid hid lpc_ich hpilo ioatdma dca ipmi_si shpchp wmi acpi_power_meter mac_hid lp parport psmouse i40e vxlan ip_tunnel ptp hpsa pps_core [8.934874] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-57-generic #95-Ubuntu [8.934877] Hardware name: HP ProLiant DL380 Gen9, BIOS P89 05/06/2015 [8.934878] 0009 88103fc03d98 817232f0 88103fc03de0 [8.934891] 88103fc03dd0 8106784d 881028d18000 [8.934895] 881023734f40 0040 88103fc03e30 [8.934904] Call Trace: [8.934905] IRQ [817232f0] dump_stack+0x45/0x56 [8.934921] [8106784d] warn_slowpath_common+0x7d/0xa0 [8.934925] [810678bc] warn_slowpath_fmt+0x4c/0x50 [8.934928] [816479d6] dev_watchdog+0x276/0x280 [8.934935] [81647760] ? dev_graft_qdisc+0x80/0x80 [8.934942] [810744e6] call_timer_fn+0x36/0x100 [8.934946] [81647760] ? dev_graft_qdisc+0x80/0x80 [8.934950] [8107547f] run_timer_softirq+0x1ef/0x2f0 [8.934957] [8106ccbc] __do_softirq+0xec/0x2c0 [8.934961] [8106d205] irq_exit+0x105/0x110 [8.934971] [81736195] smp_apic_timer_interrupt+0x45/0x60 [8.934976] [81734b1d] apic_timer_interrupt+0x6d/0x80 [8.934977] EOI [815d55d2] ? cpuidle_enter_state+0x52/0xc0 [8.934986] [815d56f9] cpuidle_idle_call+0xb9/0x1f0 [8.934994] [8101d3ee] arch_cpu_idle+0xe/0x30 [8.935000] [810bf205] cpu_startup_entry+0xc5/0x290 [8.935008] [817114f7] rest_init+0x77/0x80 [8.935016] [81d34f70] start_kernel+0x438/0x443 [8.935021] [81d34941] ? repair_env_string+0x5c/0x5c [8.935023] [81d34120] ? early_idt_handlers+0x120/0x120 [8.935027] [81d345ee] x86_64_start_reservations+0x2a/0x2c [8.935030]
[Kernel-packages] [Bug 1486153] Re: fglrx-core: fglrx-core kernel module failed to build
*** This bug is a duplicate of bug 1479913 *** https://bugs.launchpad.net/bugs/1479913 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1479913, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1479913 SRU request: fglrx.ko fails because of backported GPL-only 'pci_ignore_hotplug' symbol -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486153 Title: fglrx-core: fglrx-core kernel module failed to build Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade to kernel version 3.19.0-26-generic fglrx fails to build the needed DKMS module and renders the GUI non-functional. Had to remove all fglrx packages to get a working Xsession again. Converting back to 3.19.0-25 solved the DKMS module building problem. DKMS make.log for fglrx-core-15.200 for kernel 3.19.0-26-generic (x86_64) ... FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'pci_ignore_hotplug' ... ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 3.19.0-26-generic Date: Tue Aug 18 19:12:54 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.200, 3.19.0-25-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2015-08-07 (10 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageVersion: (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=19317e49-95e5-41ee-8908-8a05165ac80c ro vga=0x0368 quiet splash nomodeset video=uvesafb:mode_option=1920x1080-24,mtrr=3,scroll=ywrap vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: fglrx-installer Title: fglrx-core (not installed): fglrx-core kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/09/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Aug 18 19:13:52 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: fglrx To manage notifications about this bug go to:
[Kernel-packages] [Bug 1486316] JournalErrors.txt
apport information ** Attachment added: JournalErrors.txt https://bugs.launchpad.net/bugs/1486316/+attachment/4447936/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486316 Title: lpc_ich: Resource conflict(s) found affecting gpio_ich Status in linux package in Ubuntu: New Bug description: This nearly identical to the following bug: (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1027370). (sorry not sure how to make links here) however, this is not effecting iTCO_wdt, but is effecting gpio_ich ACPI Warning: SystemIO range 0x0828-0x082F conflicts with OpRegion 0x0800-0x084F (\PMRG) (20150410/utaddress-254) [ ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver lpc_ich: Resource conflict(s) found affecting gpio_ich This error occurs in 15,04 and the latest build of 15.10. i meant to post this up with the last report i made but i ended up getting distracted. sorry. LSB: Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 --- ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: testusr1632 F...m pulseaudio /dev/snd/controlC0: testusr1632 F pulseaudio /dev/snd/controlC1: testusr1632 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=df53ef11-a582-4795-81e6-4666c7ba9eb7 InstallationDate: Installed on 2015-08-15 (3 days ago) InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150815.1) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: Gateway FX6840 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=2244254b-eee5-4fa6-bb16-d4e811b01f42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 RfKill: Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.1.0-3-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FX6840 dmi.board.vendor: Gateway dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd05/17/2010:svnGateway:pnFX6840:pvr:rvnGateway:rnFX6840:rvr:cvnGateway:ct3:cvr: dmi.product.name: FX6840 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486316] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1486316/+attachment/4447945/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486316 Title: lpc_ich: Resource conflict(s) found affecting gpio_ich Status in linux package in Ubuntu: New Bug description: This nearly identical to the following bug: (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1027370). (sorry not sure how to make links here) however, this is not effecting iTCO_wdt, but is effecting gpio_ich ACPI Warning: SystemIO range 0x0828-0x082F conflicts with OpRegion 0x0800-0x084F (\PMRG) (20150410/utaddress-254) [ ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver lpc_ich: Resource conflict(s) found affecting gpio_ich This error occurs in 15,04 and the latest build of 15.10. i meant to post this up with the last report i made but i ended up getting distracted. sorry. LSB: Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 --- ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: testusr1632 F...m pulseaudio /dev/snd/controlC0: testusr1632 F pulseaudio /dev/snd/controlC1: testusr1632 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=df53ef11-a582-4795-81e6-4666c7ba9eb7 InstallationDate: Installed on 2015-08-15 (3 days ago) InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150815.1) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: Gateway FX6840 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=2244254b-eee5-4fa6-bb16-d4e811b01f42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 RfKill: Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.1.0-3-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FX6840 dmi.board.vendor: Gateway dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd05/17/2010:svnGateway:pnFX6840:pvr:rvnGateway:rnFX6840:rvr:cvnGateway:ct3:cvr: dmi.product.name: FX6840 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486316] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1486316/+attachment/4447943/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486316 Title: lpc_ich: Resource conflict(s) found affecting gpio_ich Status in linux package in Ubuntu: New Bug description: This nearly identical to the following bug: (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1027370). (sorry not sure how to make links here) however, this is not effecting iTCO_wdt, but is effecting gpio_ich ACPI Warning: SystemIO range 0x0828-0x082F conflicts with OpRegion 0x0800-0x084F (\PMRG) (20150410/utaddress-254) [ ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver lpc_ich: Resource conflict(s) found affecting gpio_ich This error occurs in 15,04 and the latest build of 15.10. i meant to post this up with the last report i made but i ended up getting distracted. sorry. LSB: Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 --- ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: testusr1632 F...m pulseaudio /dev/snd/controlC0: testusr1632 F pulseaudio /dev/snd/controlC1: testusr1632 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=df53ef11-a582-4795-81e6-4666c7ba9eb7 InstallationDate: Installed on 2015-08-15 (3 days ago) InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150815.1) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: Gateway FX6840 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=2244254b-eee5-4fa6-bb16-d4e811b01f42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 RfKill: Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.1.0-3-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FX6840 dmi.board.vendor: Gateway dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd05/17/2010:svnGateway:pnFX6840:pvr:rvnGateway:rnFX6840:rvr:cvnGateway:ct3:cvr: dmi.product.name: FX6840 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486316] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1486316/+attachment/4447942/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486316 Title: lpc_ich: Resource conflict(s) found affecting gpio_ich Status in linux package in Ubuntu: New Bug description: This nearly identical to the following bug: (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1027370). (sorry not sure how to make links here) however, this is not effecting iTCO_wdt, but is effecting gpio_ich ACPI Warning: SystemIO range 0x0828-0x082F conflicts with OpRegion 0x0800-0x084F (\PMRG) (20150410/utaddress-254) [ ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver lpc_ich: Resource conflict(s) found affecting gpio_ich This error occurs in 15,04 and the latest build of 15.10. i meant to post this up with the last report i made but i ended up getting distracted. sorry. LSB: Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 --- ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: testusr1632 F...m pulseaudio /dev/snd/controlC0: testusr1632 F pulseaudio /dev/snd/controlC1: testusr1632 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=df53ef11-a582-4795-81e6-4666c7ba9eb7 InstallationDate: Installed on 2015-08-15 (3 days ago) InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150815.1) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: Gateway FX6840 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=2244254b-eee5-4fa6-bb16-d4e811b01f42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 RfKill: Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.1.0-3-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FX6840 dmi.board.vendor: Gateway dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd05/17/2010:svnGateway:pnFX6840:pvr:rvnGateway:rnFX6840:rvr:cvnGateway:ct3:cvr: dmi.product.name: FX6840 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486316] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1486316/+attachment/4447944/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486316 Title: lpc_ich: Resource conflict(s) found affecting gpio_ich Status in linux package in Ubuntu: New Bug description: This nearly identical to the following bug: (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1027370). (sorry not sure how to make links here) however, this is not effecting iTCO_wdt, but is effecting gpio_ich ACPI Warning: SystemIO range 0x0828-0x082F conflicts with OpRegion 0x0800-0x084F (\PMRG) (20150410/utaddress-254) [ ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver lpc_ich: Resource conflict(s) found affecting gpio_ich This error occurs in 15,04 and the latest build of 15.10. i meant to post this up with the last report i made but i ended up getting distracted. sorry. LSB: Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 --- ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: testusr1632 F...m pulseaudio /dev/snd/controlC0: testusr1632 F pulseaudio /dev/snd/controlC1: testusr1632 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=df53ef11-a582-4795-81e6-4666c7ba9eb7 InstallationDate: Installed on 2015-08-15 (3 days ago) InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150815.1) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: Gateway FX6840 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=2244254b-eee5-4fa6-bb16-d4e811b01f42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 RfKill: Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.1.0-3-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FX6840 dmi.board.vendor: Gateway dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd05/17/2010:svnGateway:pnFX6840:pvr:rvnGateway:rnFX6840:rvr:cvnGateway:ct3:cvr: dmi.product.name: FX6840 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1486316] 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/1486316 Title: lpc_ich: Resource conflict(s) found affecting gpio_ich Status in linux package in Ubuntu: Confirmed Bug description: This nearly identical to the following bug: (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1027370). (sorry not sure how to make links here) however, this is not effecting iTCO_wdt, but is effecting gpio_ich ACPI Warning: SystemIO range 0x0828-0x082F conflicts with OpRegion 0x0800-0x084F (\PMRG) (20150410/utaddress-254) [ ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver lpc_ich: Resource conflict(s) found affecting gpio_ich This error occurs in 15,04 and the latest build of 15.10. i meant to post this up with the last report i made but i ended up getting distracted. sorry. LSB: Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 --- ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: testusr1632 F...m pulseaudio /dev/snd/controlC0: testusr1632 F pulseaudio /dev/snd/controlC1: testusr1632 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=df53ef11-a582-4795-81e6-4666c7ba9eb7 InstallationDate: Installed on 2015-08-15 (3 days ago) InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150815.1) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: Gateway FX6840 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=2244254b-eee5-4fa6-bb16-d4e811b01f42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 RfKill: Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.1.0-3-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FX6840 dmi.board.vendor: Gateway dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd05/17/2010:svnGateway:pnFX6840:pvr:rvnGateway:rnFX6840:rvr:cvnGateway:ct3:cvr: dmi.product.name: FX6840 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1129192] Re: CVE-2013-0871
** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: Fix Committed = 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/1129192 Title: CVE-2013-0871 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: 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-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid Status in linux-lts-backport-oneiric source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Invalid Status in linux-lts-backport-natty source package in Utopic: Invalid Status in
[Kernel-packages] [Bug 1486330] [NEW] package linux-image-3.19.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: Tried to update when the system showed an update popover. Few days back there were space concerns with /boot and then the old images were removed. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CRDA: country IN: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (N/A, 20), (N/A) (5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 40), (N/A, 20), (N/A) Date: Wed Aug 19 09:03:27 2015 DuplicateSignature: package:linux-image-3.19.0-26-generic:(not installed):subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=f77e51c8-a4f7-4167-8487-25bc12667ab0 InstallationDate: Installed on 2015-06-30 (49 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Dell Inc. Latitude E7440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro noprompt 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 N/A SourcePackage: linux Title: package linux-image-3.19.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4: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-package vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486330 Title: package linux-image-3.19.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: Tried to update when the system showed an update popover. Few days back there were space concerns with /boot and then the old images were removed. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CRDA: country IN: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (N/A, 20), (N/A) (5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 40), (N/A, 20), (N/A) Date: Wed Aug 19 09:03:27 2015 DuplicateSignature: package:linux-image-3.19.0-26-generic:(not installed):subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=f77e51c8-a4f7-4167-8487-25bc12667ab0 InstallationDate: Installed on 2015-06-30 (49 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Dell Inc. Latitude E7440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro noprompt 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 N/A SourcePackage: linux Title: package linux-image-3.19.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage
[Kernel-packages] [Bug 1485113] onza (i386) - tests ran: 170, failed: 1
tests ran: 170, failed: 1; http://kernel.ubuntu.com/testing/onza__3.19.0-27.29__2015-08-18_18-36-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485113 Title: linux: 3.19.0-27.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: New Bug description: This bug is for tracking the 3.19.0-27.29 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:Friday, 14. August 2015 20:50 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:02 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485127] tarf (i386) - tests ran: 153, failed: 1
tests ran: 153, failed: 1; http://kernel.ubuntu.com/testing/tarf__3.16.0-47.63~14.04.1__2015-08-19_00-30-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1485127 Title: linux-lts-utopic: 3.16.0-47.63~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-47.63~14.04.1 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:Friday, 14. August 2015 22:17 UTC kernel-stable-Prepare-package-end:Saturday, 15. August 2015 07:04 UTC kernel-stable-Promote-to-proposed-start:Saturday, 15. August 2015 07:04 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:03 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485184] larsen (amd64) - tests ran: 180, failed: 1
tests ran: 180, failed: 1; http://kernel.ubuntu.com/testing/larsen__3.19.0-27.29~14.04.1__2015-08-19_00-53-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1485184 Title: linux-lts-vivid: 3.19.0-27.29~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: New Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-27.29~14.04.1 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:Saturday, 15. August 2015 07:02 UTC kernel-stable-master-bug:1485113 kernel-stable-Prepare-package-end:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-start:Sunday, 16. August 2015 12:03 UTC kernel-stable-Promote-to-proposed-end:Monday, 17. August 2015 23:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Verification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Certification-testing-start:Tuesday, 18. August 2015 00:04 UTC kernel-stable-Security-signoff-start:Tuesday, 18. August 2015 00:04 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 18. August 2015 00:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1485184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
