[Kernel-packages] [Bug 1483922] onza (amd64) - tests ran: 180, failed: 1
tests ran: 180, failed: 1; http://kernel.ubuntu.com/testing/onza__3.19.0-26.28~14.04.1__2015-08-14_03-42-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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~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: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484799] Re: CVE-2015-5707
CVE-2015-5707 ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-mvl-dove (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-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Wily) Status: New => Invali
[Kernel-packages] [Bug 1484799] [NEW] CVE-2015-5707
*** This bug is a security vulnerability *** Public security bug reported: [Integer overflow in SCSI generic driver] Break-Fix: 10db10d144c0248f285242f79daf6b9de6b00a62 451a2886b6bf90e2fb378f7c46c655450fb96e81 Break-Fix: bc917be8105993c256338ad1189650364a741483 fdc81f45e9f57858da6351836507fbcf1b7583ee ** Affects: linux (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: In
[Kernel-packages] [Bug 1484797] Re: CVE-2015-5706
CVE-2015-5706 ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Vivid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Wily) Status: New => Invalid ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-mvl-dove (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-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Precise)
[Kernel-packages] [Bug 1484797] [NEW] CVE-2015-5706
*** This bug is a security vulnerability *** Public security bug reported: [Use-after-free in path lookup] Break-Fix: 60545d0d4610b02e55f65d141c95b18ccf855b6e f15133df088ecadd141ea1907f2c96df67c729f0 ** Affects: linux (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: Fix Committed ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: Fix Committed ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: Fix Committed ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: Fix Committed ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty)
[Kernel-packages] [Bug 1484793] Re: CVE-2015-5156
CVE-2015-5156 ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-mvl-dove (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-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-mako (Ubuntu Precise) Status: New =
[Kernel-packages] [Bug 1484793] [NEW] CVE-2015-5156
*** This bug is a security vulnerability *** Public security bug reported: [virt-io max-skb-frags heap overflow] ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affec
[Kernel-packages] [Bug 1484792] Re: CVE-2015-2877
CVE-2015-2877 ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-mvl-dove (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-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-mako (Ubuntu Precise) Status: New =
[Kernel-packages] [Bug 1484792] [NEW] CVE-2015-2877
*** This bug is a security vulnerability *** Public security bug reported: ASLR base address leak of co-located VMs ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-goldfish (Ubuntu) Importance: Low Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Low Status: New ** Affects: linux-manta (Ubuntu) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Low Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Low Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-armadaxp (Ubuntu Vivid) Im
[Kernel-packages] [Bug 1481039] Re: CVE-2015-5697
** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Description changed: [information leak in md driver] - Break-Fix: - 77ba0569d4c8389c0a2162ab0c7c16a6f3b199e4 + Break-Fix: - b6878d9e03043695dbf3fa1caa6dfc09db225b16 -- 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/1481039 Title: CVE-2015-5697 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-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: New Status in linux-armadaxp source package in Precise: New 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: Invalid Status in linux-lts-trusty source package in Precise: New 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: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-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: New Status in linux-lts-vivid source package in Trusty: New 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: New 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: Fix Committed 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 i
[Kernel-packages] [Bug 1483922] larsen (i386) - tests ran: 153, failed: 0
tests ran: 153, failed: 0; http://kernel.ubuntu.com/testing/larsen__3.19.0-26.28~14.04.1__2015-08-14_02-25-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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~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: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1461599] Re: Trying to install Ubuntu 14.04, but system rebootin again and again
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1461599 Title: Trying to install Ubuntu 14.04, but system rebootin again and again Status in linux package in Ubuntu: Expired Bug description: Today when I tried to install ubuntu-14.04.2-desktop-i386 using a bootable USB(using Universal-USB-Installer-1.9.6.0), then after showing me initial 4 steps system started rebooting. Any further attempts in installing it resulted in the same bug. This bug is not letting me install Ubuntu 14.04 on my hardware and it is affecting a few more users too. --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2726 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity CurrentDmesg: [ 25.275952] tg3 :05:00.0 eth0: Flow control is off for TX and off for RX [ 25.275975] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 26.774375] init: plymouth-upstart-bridge main process ended, respawning [ 26.793819] init: plymouth-upstart-bridge main process ended, respawning [ 232.074319] perf interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 DistroRelease: Ubuntu 14.04 IwConfig: lono wireless extensions. eth0 no wireless extensions. LiveMediaBuild: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) MachineType: Acer, inc. Aspire 4720Z Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid initrd=/casper/initrd.lz quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 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 Tags: trusty Uname: Linux 3.16.0-30-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/18/2008 dmi.bios.vendor: Acer dmi.bios.version: v1.3808 dmi.board.name: Nestos dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3808:bd02/18/2008:svnAcer,inc.:pnAspire4720Z:pvrNotApplicable:rvnAcer,Inc.:rnNestos:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 4720Z dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1423608] Re: [Dell Precision M3800] suspend/resume failure when lid open/closed [non-free: nvidia]
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1423608 Title: [Dell Precision M3800] suspend/resume failure when lid open/closed [non-free: nvidia] Status in linux package in Ubuntu: Expired Bug description: This bugs symptoms look very similar to others on Launchpad. Basically the computer (under 14.04 distro) fails to resume after suspending when closing the lid. It happens every now and then and after a week or two EVERY suspend results in a failure to resume. I tried a few different Nvidia drivers (331, 331-updates, X.org) and changed the kernel a few times. I have tried to keep this bug report free from the all the different (and confusing) trials so this bug corresponds to one of the latest kernels (3.16.0-30-generic) and the recommended Nvidia driver. ProblemType: KernelOops 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 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Thu Feb 19 10:01:22 2015 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1423324748 Failure: suspend/resume InstallationDate: Installed on 2012-04-02 (1052 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) InterpreterPath: /usr/bin/python3.4 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: linux-lts-utopic Title: suspend/resume failure [non-free: nvidia] UpgradeStatus: Upgraded to trusty on 2014-11-06 (105 days ago) UserGroups: --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aham 2287 F pulseaudio /dev/snd/controlC1: aham 2287 F pulseaudio /dev/snd/pcmC1D0c: aham 2287 F...m pulseaudio /dev/snd/pcmC1D0p: aham 2287 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=81558bef-b616-4e06-b864-56688bf5b927 InstallationDate: Installed on 2012-04-02 (1148 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Dell Inc. Dell Precision M3800 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=d6596aa5-b90f-4e07-8e4b-f2d0e2cfa261 ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 RelatedPackageVersions: linux-restricted-modules-3.13.0-52-generic N/A linux-backports-modules-3.13.0-52-generic N/A linux-firmware 1.127.12 Tags: trusty Uname: Linux 3.13.0-52-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-11-06 (201 days ago) UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare vboxusers _MarkForUpload: True dmi.bios.date: 12/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/18/2013:svnDellInc.:pnDellPrecisionM3800:pvrA02:rvnDellInc.:rnDellPrecisionM3800:rvrA02:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436940] Re: Atheros wifi 168c:0041(QCA6164) is not supported
With the new files, I still get the ath10k/QCA6174/hw2.1/firmware-4.bin errors. Does the kernel need to be updated for a new driver that looks for a -5 firmware? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436940 Title: Atheros wifi 168c:0041(QCA6164) is not supported Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Confirmed Bug description: The atheros wireless device (168c:0041) isn't supported by the ath10k_pci kernel driver. Found in several laptop models: Lenovo G50-45 Lenovo G50-80 Lenovo Edge 15 Lenovo Z70 Lenovo G50-45 Lenovo Flex 3-1470 Lenovo Yoga 3 11 Samsung ATIV Book 9 NP930X2K ProblemType: BugDistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicholas 1695 F pulseaudio /dev/snd/controlC1: nicholas 1695 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 26 09:47:16 2015 HibernationDevice: RESUME=UUID=5b068cd8-e60a-49b9-a88e-1581bb6b3dc1 InstallationDate: Installed on 2015-03-25 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:0652 Acer, Inc Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=e52867c5-0b50-42fb-8288-f30765f926c5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware1.143SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-26 (0 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN69WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN69WW:bd06/20/2014:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1472165] Re: CVE-2015-5366
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1472165 Title: CVE-2015-5366 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: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed 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: Fix Committed 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 pa
[Kernel-packages] [Bug 1472160] Re: CVE-2015-5364
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1472160 Title: CVE-2015-5364 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: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed 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: Fix Committed 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 pa
[Kernel-packages] [Bug 1483922] onibi (i386) - tests ran: 153, failed: 0
tests ran: 153, failed: 0; http://kernel.ubuntu.com/testing/onibi__3.19.0-26.28~14.04.1__2015-08-14_01-26-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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~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: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483922] rainier (i386) - tests ran: 153, failed: 0
tests ran: 153, failed: 0; http://kernel.ubuntu.com/testing/rainier__3.19.0-26.28~14.04.1__2015-08-14_01-39-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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~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: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483893] onza (i386) - tests ran: 147, failed: 1
tests ran: 147, failed: 1; http://kernel.ubuntu.com/testing/onza__3.13.0-62.102~precise1__2015-08-14_01-18-00/results-index.html -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~precise1 -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-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462173] Re: CVE-2015-4167
** Description changed: - [fs: udf kernel oops] + The udf_read_inode function in fs/udf/inode.c in the Linux kernel before + 3.19.1 does not validate certain length values, which allows local users + to cause a denial of service (incorrect data representation or integer + overflow, and OOPS) via a crafted UDF filesystem. Break-Fix: - 23b133bdc452aa441fcb9b82cbf6dd05cfd342d0 -- 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/1462173 Title: CVE-2015-4167 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: 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: 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: Fix Released 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: 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: New Status in linux-lts-backport-natty source package in Utopic: New 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-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 sour
[Kernel-packages] [Bug 1484769] Re: needs to be looked ASAP
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/1484769 Title: needs to be looked ASAP Status in b43-fwcutter package in Ubuntu: New Bug description: I have just updated this recently but it cannot work with airmon-ng. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: firmware-b43-installer 1:018-2 ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18 Uname: Linux 3.13.0-51-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 CurrentDesktop: Unity Date: Fri Aug 14 02:29:16 2015 InstallationDate: Installed on 2015-04-22 (113 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all SourcePackage: b43-fwcutter UpgradeStatus: Upgraded to trusty on 2015-04-27 (108 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1484769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483922] fozzie (i386) - tests ran: 153, failed: 0
tests ran: 153, failed: 0; http://kernel.ubuntu.com/testing/fozzie__3.19.0-26.28~14.04.1__2015-08-14_00-49-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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~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: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1453256] Re: CVE-2015-3636
** Description changed: - ipv4: Missing sk_nulls_node_init() in ping_unhash() allows local kernel - privileges escalation via use-after-free. + The ping_unhash function in net/ipv4/ping.c in the Linux kernel before + 4.0.3 does not initialize a certain list data structure during an unhash + operation, which allows local users to gain privileges or cause a denial + of service (use-after-free and system crash) by leveraging the ability + to make a SOCK_DGRAM socket system call for the IPPROTO_ICMP or + IPPROTO_ICMPV6 protocol, and then making a connect system call after a + disconnect. Break-Fix: c319b4d76b9e583a5d88d6bf190e079c4e43213d a134f083e79fb4c3d0a925691e732c56911b4326 -- 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/1453256 Title: CVE-2015-3636 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: 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: 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: Fix Released 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 Vivi
[Kernel-packages] [Bug 1483922] larsen (amd64) - tests ran: 180, failed: 2
tests ran: 180, failed: 2; http://kernel.ubuntu.com/testing/larsen__3.19.0-26.28~14.04.1__2015-08-13_23-12-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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~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: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483922] tarf (i386) - tests ran: 153, failed: 0
tests ran: 153, failed: 0; http://kernel.ubuntu.com/testing/tarf__3.19.0-26.28~14.04.1__2015-08-14_00-10-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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~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: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1477026] Re: CVE-2015-3290
** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1477026 Title: CVE-2015-3290 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: Confirmed 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 packa
[Kernel-packages] [Bug 1478819] Re: CVE-2015-3291
** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Invalid ** Description changed: Malicious user code can cause some fraction of NMIs to be ignored. - Break-Fix: - 810bc075f78ff2c221536eb3008eac6a492dba2d + Break-Fix: 3f3c8b8c4b2a34776c3470142a7c8baafcda6eb0 + 810bc075f78ff2c221536eb3008eac6a492dba2d -- 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/1478819 Title: CVE-2015-3291 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 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-arma
[Kernel-packages] [Bug 1484221] Re: Kernel panic on HID bluetooth device disconnect
It sure does. Thanks! Will that commit make it's way to the kernels in the ubuntu repos? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484221 Title: Kernel panic on HID bluetooth device disconnect Status in linux package in Ubuntu: Triaged Bug description: With 4.1.0-3-generic on Ubuntu Wily/15.10 x86_64, I get a kernel panic every time my bluetooth mouse disconnects. This bug has been reported previously for Redhat and Arch: https://bugzilla.redhat.com/show_bug.cgi?id=1250279 https://bugs.archlinux.org/task/45787?string=%5Blinux%5D The details of the trace are attached to those reports. My trace is pretty much identical. A patch has been released that is going to appear in kernel 4.2: http://www.spinics.net/lists/linux-input/msg40330.html Would it be possible to add it as Ubuntu patch? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483922] rainier (amd64) - tests ran: 180, failed: 1
tests ran: 180, failed: 1; http://kernel.ubuntu.com/testing/rainier__3.19.0-26.28~14.04.1__2015-08-13_23-04-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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~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: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1471096] Re: CVE-2015-3212
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1471096 Title: CVE-2015-3212 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: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed 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 Committed 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 Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-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 Committed 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: 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 Committed 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 sour
[Kernel-packages] [Bug 1483922] onibi (amd64) - tests ran: 180, failed: 1
tests ran: 180, failed: 1; http://kernel.ubuntu.com/testing/onibi__3.19.0-26.28~14.04.1__2015-08-13_22-40-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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~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: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483893] onza (amd64) - tests ran: 148, failed: 1
tests ran: 148, failed: 1; http://kernel.ubuntu.com/testing/onza__3.13.0-62.102~precise1__2015-08-13_22-57-00/results-index.html -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~precise1 -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-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462170] Re: CVE-2015-1805
** Description changed: - A flaw was found in the way pipe_iov_copy_from_user() and - pipe_iov_copy_to_user() functions handled iovecs remaining len - accounting on failed atomic access. An unprivileged local user could - this flaw to crash the system or, potentially, escalate their privileges - on the system. + The (1) pipe_read and (2) pipe_write implementations in fs/pipe.c in the + Linux kernel before 3.16 do not properly consider the side effects of + failed __copy_to_user_inatomic and __copy_from_user_inatomic calls, + which allows local users to cause a denial of service (system crash) or + possibly gain privileges via a crafted application, aka an "I/O vector + array overrun." Break-Fix: - f0d1bec9d58d4c038d0ac958c9af82be6eb18045 Break-Fix: - 637b58c2887e5e57850865839cc75f59184b23d1 -- 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/1462170 Title: CVE-2015-1805 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: 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: 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: Fix Released 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: 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: New Status in linux-lts-backport-natty source package in Utopic: New 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-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 i
[Kernel-packages] [Bug 1483922] fozzie (amd64) - tests ran: 180, failed: 1
tests ran: 180, failed: 1; http://kernel.ubuntu.com/testing/fozzie__3.19.0-26.28~14.04.1__2015-08-13_22-17-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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~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: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483922] tarf (amd64) - tests ran: 180, failed: 1
tests ran: 180, failed: 1; http://kernel.ubuntu.com/testing/tarf__3.19.0-26.28~14.04.1__2015-08-13_22-03-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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~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: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483893] larsen (i386) - tests ran: 147, failed: 1
tests ran: 147, failed: 1; http://kernel.ubuntu.com/testing/larsen__3.13.0-62.102~precise1__2015-08-13_20-55-00/results-index.html -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~precise1 -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-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
** Changed in: bcmwl (Ubuntu) Assignee: Louis Bouchard (louis-bouchard) => Rafael David Tinoco (inaddy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in Dell Sputnik: Confirmed Status in bcmwl package in Ubuntu: In Progress Bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483893] rainier (i386) - tests ran: 147, failed: 1
tests ran: 147, failed: 1; http://kernel.ubuntu.com/testing/rainier__3.13.0-62.102~precise1__2015-08-13_20-39-00/results-index.html -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~precise1 -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-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483790] onza (i386) - tests ran: 153, failed: 1
tests ran: 153, failed: 1; http://kernel.ubuntu.com/testing/onza__3.16.0-46.62~14.04.1__2015-08-13_19-57-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/1483790 Title: linux-lts-utopic: 3.16.0-46.62~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: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-46.62~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:Tuesday, 11. August 2015 15:10 UTC kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 01:02 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 01:02 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 12. August 2015 16:12 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 12. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Wednesday, 12. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Wednesday, 12. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 12. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 12. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483893] onibi (i386) - tests ran: 147, failed: 1
tests ran: 147, failed: 1; http://kernel.ubuntu.com/testing/onibi__3.13.0-62.102~precise1__2015-08-13_20-36-00/results-index.html -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~precise1 -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-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Not sure why "no longer effects" has been placed here, we've acked the latest test kernel and are looking forward to this fix going out. -- 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: New 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 1429250] Re: crash cannot find stack info on ppc64le
** Branch linked: lp:ubuntu/trusty-proposed/crash -- 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 - 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 - 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 - 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 - 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 matter. Since, there are no issue
[Kernel-packages] [Bug 1483893] fozzie (i386) - tests ran: 147, failed: 1
tests ran: 147, failed: 1; http://kernel.ubuntu.com/testing/fozzie__3.13.0-62.102~precise1__2015-08-13_20-24-00/results-index.html -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~precise1 -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-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Hello bugproxy, or anyone else affected, Accepted crash into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/crash/7.0.3-3ubuntu4.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: crash (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to 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 - 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 - 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 - 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 - 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
[Kernel-packages] [Bug 1483893] tarf (i386) - tests ran: 147, failed: 1
tests ran: 147, failed: 1; http://kernel.ubuntu.com/testing/tarf__3.13.0-62.102~precise1__2015-08-13_20-14-00/results-index.html -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~precise1 -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-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484616] Re: pstate_idle is broken on 4.1, high fan speed when idle
** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484616 Title: pstate_idle is broken on 4.1, high fan speed when idle Status in linux package in Ubuntu: Confirmed Bug description: The system has high fan speed even when idle. Overall, the fan never gets to a fan speed as low as with the 3.13 kernel. When running the kernel with intel_pstate=disable, i get much more governor choices, and when selecting "powersave" with this, i get much better behavior, just as with the 3.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1764 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 13 19:29:31 2015 HibernationDevice: RESUME=UUID=46d75d9b-22b0-497f-b169-c644d6e0df61 InstallationDate: Installed on 2015-02-05 (188 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150205) MachineType: Dell Inc. Dell System XPS L502X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=2f827672-ff82-4172-b6cc-5235e95473e8 ro quiet splash intel_pstate=disable 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 UpgradeStatus: Upgraded to wily on 2015-05-28 (76 days ago) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484587] Re: CPU frequency management fails to re-engage on resume from suspend
** Changed in: pm-utils (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: pm-utils (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484587 Title: CPU frequency management fails to re-engage on resume from suspend Status in linux package in Ubuntu: Confirmed Status in pm-utils package in Ubuntu: Confirmed Bug description: Behavior: CPU frequency management fails to re-engage on resume from suspend. On resume, the CPUs are stuck around a single frequency (usually a low idle frequency). I use indicator-cpufreq for manual governor control. On resume, indicator-cpufreq indicates the low frequency state in its live cpu performance display in the icon. However, in its governor menu, it still shows as in use whichever governor was selected before suspend, even though that governor is not actually or properly controlling the CPU state. Upon manually switching to the unused governor in indicator-cpufreq, this behavior resolves, and the newly-chosen governor begins performing its duties. I can then immediately switch back to the desired (pre-suspend) governor with no issues. PM logs appear to show a successful resume of cpu frequency management, even though the modules did not actually gain effective control of the processor frequencies. Expected behavior: On resume, the CPU frequencies should continue being managed as they were before suspend without the need for manual user input. Also, in the event that they do not, an error/warning should appear -- if not to the user, then in the pm suspend/resume logs. Other information that may or may not be relevant: On this system, the "powersave" governor is always automatically chosen at startup, although not until a minute or so after session login. The choice of an alternate governor "performance" from indicator-cpufreq is not persistent across reboots. Further, if I manually toggle the governors at the beginning of my first session after boot, and I settle on "performance", some automated script will force it back to "powersave" at the usual time about a minute after login. To use the "performance" governor, I must select it after waiting an interval following login, and I must always switch to powersave and back to performance after each resume from suspend. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3887 F pulseaudio /dev/snd/controlC1: adam 3887 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 13 11:41:27 2015 InstallationDate: Installed on 2014-08-10 (368 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ENVY 15 x360 PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 22D6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 89.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 15 x360 PC dmi.product.version: 0974100022405F0420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483922] 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-26.28~14.04.1__2015-08-13_18-37-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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~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: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479031] Re: attached block devices not showing up
Here is a PPA with a fix for this: https://pad.lv/ppa/ddstreet/lp1479031 There was no code change required; the only change is the acpiphp driver is built-in, instead of a module. During boot, when the pci-acpi driver is loaded, it enumerates the bus. Later when the acpiphp driver is loaded, it registers for any pci-acpi hotplug events. Between the pci-acpi driver loading and the acpiphp driver loading, any pci acpi hotplug events are lost, since the bus was already enumerated and there is no driver monitoring hotplugs. Currently (without this PPA), pci-acpi is built-in, and enumerates the pci acpi devices/buses during boot. The acpiphp driver is a module, however, and therefore loads much later - more than 4 seconds later, in my brief tests. With this PPA, the acpiphp driver is built-in, and loads a fraction of a second after the pci-acpi driver - less than 1/4 second in my brief tests. So to clarify, this does not eliminate the window of time where pci acpi hotplug events will be lost, it only reduces it from multiple seconds, down to a small fraction of a second. You can check the size of the window where hotplug events will be lost with: # dmesg | grep "ACPI: bus type pci" [0.230350] ACPI: bus type pci registered # dmesg | grep "acpiphp: ACPI" [0.517999] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 that's not the exact window, since pci enumeration happens after the bus type is registered, so it's a bit smaller than that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1479031 Title: attached block devices not showing up Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: In Progress Bug description: I have Ubuntu Precise guests running in kvm to which I attach volumes immediately after boot. Sometimes I notice that the devices do not show up in the guest e.g. they are not visible in /proc/partitions and dmesg boot log shows no sign of then being noticed. Qemu itself shows that the devices are attached and if I do a rescan within the guest the devices appear. A reboot also cause the devices to appear. So, it feels like there is enough evidence to suggest that the devices were properly attached by qemu/seabios but they just didn't get noticed by the guest. This issue is reproducible with Precise running 3.2, 3.5 (lts-quantal) and 3.8 (lts-raring) kernels but not as of 3.11 (lts-saucy) so it would appear that something changed between 3.8 and 3.11 that resolved this issue and if we can identify it we should backport to 3.2. I am able to reproduce this issue using Openstack to spin up vms and attach volumes using the following script: http://pastebin.ubuntu.com/11954253/ I hit this issue with 1/2 instances. As a workaround one can rescan and the device shows up: echo 1 | sudo tee /sys/bus/pci/rescan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483893] larsen (amd64) - tests ran: 148, failed: 2
tests ran: 148, failed: 2; http://kernel.ubuntu.com/testing/larsen__3.13.0-62.102~precise1__2015-08-13_18-34-00/results-index.html -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~precise1 -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-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483893] onibi (amd64) - tests ran: 148, failed: 1
tests ran: 148, failed: 1; http://kernel.ubuntu.com/testing/onibi__3.13.0-62.102~precise1__2015-08-13_18-28-00/results-index.html -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~precise1 -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-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483893] rainier (amd64) - tests ran: 148, failed: 1
tests ran: 148, failed: 1; http://kernel.ubuntu.com/testing/rainier__3.13.0-62.102~precise1__2015-08-13_18-34-00/results-index.html -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~precise1 -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-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller
Sorry I misunderstood, I'm guessing if you go back to v3.16 it would be fine? Perhaps something about the build is wrong at the checkout preventing that. There are two ways to try proceeding: git bisect skip (trys to pick another commit) and see if it builds PPC64LE checkout v3.18 or 3.17 and see if you can get a PPC64LE to test from them -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475166 Title: Ubuntu 15.04 Install Error with Avago Controller Status in linux package in Ubuntu: Triaged Bug description: Hello Canonical Team We are running to an issue installing ubuntu PPC64LE 15.04 full blown image on our servers (with RAID controller). Installation hangs around 70% of progress. An important part of our configuration is Avago RAID controller: 9361-8i Firmware version we used is 4.300.00-4429, and the package is 24.10.0-0002. IMPORTANT: It has to be noted that with same hardware configuration 14.10 full blown image installs fine. Dmesg logs are attached: Looking at dmesg logs point out that: LSI (avago) driver loads fine During further interaction with raid volume during the installation process, firmware errors are seen [ 196.991417] megasas: FW status 0x3 [ 196.999376] megasas: FW status 0x3 [ 197.007376] megasas: FW status 0x3 Further down the process I/O errors are thrown [ 217.438664] Buffer I/O error on device sda2, logical block 22052864 [ 217.438671] Buffer I/O error on device sda2, logical block 22052865 [ 217.438678] Buffer I/O error on device sda2, logical block 22052866 [ 217.438686] Buffer I/O error on device sda2, logical block 22052867 Full dmesg log is attached. Snippet is pasted below highlighting: It can be noted that there’s a Mellanox Connectx 3 pro card with some test Firmware on our setup. We can Ignore any diagnostic messages from that card in dmesg logs for the purpose of this bug. Thanks Adi Gangidi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483893] fozzie (amd64) - tests ran: 148, failed: 1
tests ran: 148, failed: 1; http://kernel.ubuntu.com/testing/fozzie__3.13.0-62.102~precise1__2015-08-13_18-29-00/results-index.html -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~precise1 -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-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483893] tarf (amd64) - tests ran: 148, failed: 1
tests ran: 148, failed: 1; http://kernel.ubuntu.com/testing/tarf__3.13.0-62.102~precise1__2015-08-13_18-30-00/results-index.html -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~precise1 -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-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller
As I mentioned in my Comment 18 I can't get further with bisection since: I am at a bisect state between 3.16 and 3.19 where I can't generate a Little Indian kernel deb package. (PPC64LE). All it generates is a POWERPC deb. Console doesn't let me customize it in the config make oldconfig stage, So after 'git bisect' and checkout to bisected state make -j `getconf _NPROCESSORS_ONLN` deb-pkg LOCALVERSION=-custom now generates POWERPC arch images instead of PPC64LE. For example: linux-headers-3.18.0-custom_3.18.0-custom-2_powerpc.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475166 Title: Ubuntu 15.04 Install Error with Avago Controller Status in linux package in Ubuntu: Triaged Bug description: Hello Canonical Team We are running to an issue installing ubuntu PPC64LE 15.04 full blown image on our servers (with RAID controller). Installation hangs around 70% of progress. An important part of our configuration is Avago RAID controller: 9361-8i Firmware version we used is 4.300.00-4429, and the package is 24.10.0-0002. IMPORTANT: It has to be noted that with same hardware configuration 14.10 full blown image installs fine. Dmesg logs are attached: Looking at dmesg logs point out that: LSI (avago) driver loads fine During further interaction with raid volume during the installation process, firmware errors are seen [ 196.991417] megasas: FW status 0x3 [ 196.999376] megasas: FW status 0x3 [ 197.007376] megasas: FW status 0x3 Further down the process I/O errors are thrown [ 217.438664] Buffer I/O error on device sda2, logical block 22052864 [ 217.438671] Buffer I/O error on device sda2, logical block 22052865 [ 217.438678] Buffer I/O error on device sda2, logical block 22052866 [ 217.438686] Buffer I/O error on device sda2, logical block 22052867 Full dmesg log is attached. Snippet is pasted below highlighting: It can be noted that there’s a Mellanox Connectx 3 pro card with some test Firmware on our setup. We can Ignore any diagnostic messages from that card in dmesg logs for the purpose of this bug. Thanks Adi Gangidi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1469482] Re: Installer initrd missing kernel module for ib_ipoib network installation
I think that Mellanox wants us to enable full IPoIB PXE support. For that to happen I plan to: - Enumerate the needs for it to happen (enable proper modules, preseed support, etc) - Show test results using HW they provided us - Propose fixes I'll be working on this for the next few days using an IB lab. 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/1469482 Title: Installer initrd missing kernel module for ib_ipoib network installation Status in linux package in Ubuntu: Confirmed Status in linux-lts-vivid package in Ubuntu: New Status in linux source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Bug description: The initrd.gz found at the path [1] on Ubuntu 14.04.3 iso from [2] URL doesn't contain [3] kernel modules. This modules needed for network installation over ib_ipoib. To check if the modules aren't exist run: # lsinitrd install/netboot/ubuntu-installer/amd64/initrd.gz | grep infiniband [1] - install/netboot/ubuntu-installer/amd64/initrd.gz [2] - http://cdimage.ubuntu.com/ubuntu-server/trusty/daily/current/ [3] - ib_addr, ib_core, ib_cm, ib_sa, mlx4_core, mlx4_ib, mlx5_core, mlx5_ib, ib_mad, ib_ipoib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483790] onza (amd64) - tests ran: 180, failed: 3
tests ran: 180, failed: 3; http://kernel.ubuntu.com/testing/onza__3.16.0-46.62~14.04.1__2015-08-13_16-58-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/1483790 Title: linux-lts-utopic: 3.16.0-46.62~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: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-46.62~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:Tuesday, 11. August 2015 15:10 UTC kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 01:02 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 01:02 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 12. August 2015 16:12 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 12. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Wednesday, 12. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Wednesday, 12. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 12. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 12. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1469482] Re: Installer initrd missing kernel module for ib_ipoib network installation
** Also affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-vivid (Ubuntu Trusty) Importance: Undecided Status: New -- 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/1469482 Title: Installer initrd missing kernel module for ib_ipoib network installation Status in linux package in Ubuntu: Confirmed Status in linux-lts-vivid package in Ubuntu: New Status in linux source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Bug description: The initrd.gz found at the path [1] on Ubuntu 14.04.3 iso from [2] URL doesn't contain [3] kernel modules. This modules needed for network installation over ib_ipoib. To check if the modules aren't exist run: # lsinitrd install/netboot/ubuntu-installer/amd64/initrd.gz | grep infiniband [1] - install/netboot/ubuntu-installer/amd64/initrd.gz [2] - http://cdimage.ubuntu.com/ubuntu-server/trusty/daily/current/ [3] - ib_addr, ib_core, ib_cm, ib_sa, mlx4_core, mlx4_ib, mlx5_core, mlx5_ib, ib_mad, ib_ipoib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1469482] Re: Installer initrd missing kernel module for ib_ipoib network installation
** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1469482 Title: Installer initrd missing kernel module for ib_ipoib network installation Status in linux package in Ubuntu: Confirmed Bug description: The initrd.gz found at the path [1] on Ubuntu 14.04.3 iso from [2] URL doesn't contain [3] kernel modules. This modules needed for network installation over ib_ipoib. To check if the modules aren't exist run: # lsinitrd install/netboot/ubuntu-installer/amd64/initrd.gz | grep infiniband [1] - install/netboot/ubuntu-installer/amd64/initrd.gz [2] - http://cdimage.ubuntu.com/ubuntu-server/trusty/daily/current/ [3] - ib_addr, ib_core, ib_cm, ib_sa, mlx4_core, mlx4_ib, mlx5_core, mlx5_ib, ib_mad, ib_ipoib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller
Sorry, I forgot that was also in C#17. I just wanted to minimize the chance the kernel build/git operations would be affected by the IO issues. Sticking with 14.10 for the bisection is perfect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475166 Title: Ubuntu 15.04 Install Error with Avago Controller Status in linux package in Ubuntu: Triaged Bug description: Hello Canonical Team We are running to an issue installing ubuntu PPC64LE 15.04 full blown image on our servers (with RAID controller). Installation hangs around 70% of progress. An important part of our configuration is Avago RAID controller: 9361-8i Firmware version we used is 4.300.00-4429, and the package is 24.10.0-0002. IMPORTANT: It has to be noted that with same hardware configuration 14.10 full blown image installs fine. Dmesg logs are attached: Looking at dmesg logs point out that: LSI (avago) driver loads fine During further interaction with raid volume during the installation process, firmware errors are seen [ 196.991417] megasas: FW status 0x3 [ 196.999376] megasas: FW status 0x3 [ 197.007376] megasas: FW status 0x3 Further down the process I/O errors are thrown [ 217.438664] Buffer I/O error on device sda2, logical block 22052864 [ 217.438671] Buffer I/O error on device sda2, logical block 22052865 [ 217.438678] Buffer I/O error on device sda2, logical block 22052866 [ 217.438686] Buffer I/O error on device sda2, logical block 22052867 Full dmesg log is attached. Snippet is pasted below highlighting: It can be noted that there’s a Mellanox Connectx 3 pro card with some test Firmware on our setup. We can Ignore any diagnostic messages from that card in dmesg logs for the purpose of this bug. Thanks Adi Gangidi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483893] Re: linux-lts-trusty: 3.13.0-62.102~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New => In Progress ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Description changed: This bug is for tracking the 3.13.0-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 - kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC - kernel-stable-phase-changed:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC + kernel-stable-phase:Verification & Testing + kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC + kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC + kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC + kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC + proposed-announcement-sent:True + kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~precise1 -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-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:01 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483922] Re: linux-lts-vivid: 3.19.0-26.28~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New => In Progress ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Description changed: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 - kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC - kernel-stable-phase-changed:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC + kernel-stable-phase:Verification & Testing + kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC + kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC + kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC + kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC + proposed-announcement-sent:True + kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC -- 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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~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: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 13. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Thursday, 13. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Thursday, 13. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 13. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484616] 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/1484616 Title: pstate_idle is broken on 4.1, high fan speed when idle Status in linux package in Ubuntu: Confirmed Bug description: The system has high fan speed even when idle. Overall, the fan never gets to a fan speed as low as with the 3.13 kernel. When running the kernel with intel_pstate=disable, i get much more governor choices, and when selecting "powersave" with this, i get much better behavior, just as with the 3.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1764 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 13 19:29:31 2015 HibernationDevice: RESUME=UUID=46d75d9b-22b0-497f-b169-c644d6e0df61 InstallationDate: Installed on 2015-02-05 (188 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150205) MachineType: Dell Inc. Dell System XPS L502X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=2f827672-ff82-4172-b6cc-5235e95473e8 ro quiet splash intel_pstate=disable 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 UpgradeStatus: Upgraded to wily on 2015-05-28 (76 days ago) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484616] [NEW] pstate_idle is broken on 4.1, high fan speed when idle
Public bug reported: The system has high fan speed even when idle. Overall, the fan never gets to a fan speed as low as with the 3.13 kernel. When running the kernel with intel_pstate=disable, i get much more governor choices, and when selecting "powersave" with this, i get much better behavior, just as with the 3.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1764 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 13 19:29:31 2015 HibernationDevice: RESUME=UUID=46d75d9b-22b0-497f-b169-c644d6e0df61 InstallationDate: Installed on 2015-02-05 (188 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150205) MachineType: Dell Inc. Dell System XPS L502X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=2f827672-ff82-4172-b6cc-5235e95473e8 ro quiet splash intel_pstate=disable 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 UpgradeStatus: Upgraded to wily on 2015-05-28 (76 days ago) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. ** 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/1484616 Title: pstate_idle is broken on 4.1, high fan speed when idle Status in linux package in Ubuntu: New Bug description: The system has high fan speed even when idle. Overall, the fan never gets to a fan speed as low as with the 3.13 kernel. When running the kernel with intel_pstate=disable, i get much more governor choices, and when selecting "powersave" with this, i get much better behavior, just as with the 3.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1764 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 13 19:29:31 2015 HibernationDevice: RESUME=UUID=46d75d9b-22b0-497f-b169-c644d6e0df61 InstallationDate: Installed on 2015-02-05 (188 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150205) MachineType: Dell Inc. Dell System XPS L502X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=2f827672-ff82-4172-b6cc-5235e95473e8 ro quiet splash intel_pstate=disable 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 UpgradeStatus: Upgraded to wily on 2015-05-28 (76 days ago) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484616] Re: pstate_idle is broken on 4.1, high fan speed when idle
I ran the system with intel_pstate=disable when filing the bug, but the buggy behaviour is without that option. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484616 Title: pstate_idle is broken on 4.1, high fan speed when idle Status in linux package in Ubuntu: New Bug description: The system has high fan speed even when idle. Overall, the fan never gets to a fan speed as low as with the 3.13 kernel. When running the kernel with intel_pstate=disable, i get much more governor choices, and when selecting "powersave" with this, i get much better behavior, just as with the 3.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1764 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 13 19:29:31 2015 HibernationDevice: RESUME=UUID=46d75d9b-22b0-497f-b169-c644d6e0df61 InstallationDate: Installed on 2015-02-05 (188 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150205) MachineType: Dell Inc. Dell System XPS L502X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=2f827672-ff82-4172-b6cc-5235e95473e8 ro quiet splash intel_pstate=disable 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 UpgradeStatus: Upgraded to wily on 2015-05-28 (76 days ago) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller
1) Yes there is a consistent I/O error like the one i attached in my last comment for v 3.19 and v 4.1 dmesg. This happens across multiple reboots 2)Yes, it was the I/O corruption that caused it. Regarding what you recommended in C17 regarding installing 15.04 on SATA and stuff. I am not sure why that is different from trying the 14.10 and 3.19 kernel which is giving the error anyways. I did try creating a new ext4 partition in this 14.10 3.19 combination and running FIO on it which gave me bunch of I/O errors. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475166 Title: Ubuntu 15.04 Install Error with Avago Controller Status in linux package in Ubuntu: Triaged Bug description: Hello Canonical Team We are running to an issue installing ubuntu PPC64LE 15.04 full blown image on our servers (with RAID controller). Installation hangs around 70% of progress. An important part of our configuration is Avago RAID controller: 9361-8i Firmware version we used is 4.300.00-4429, and the package is 24.10.0-0002. IMPORTANT: It has to be noted that with same hardware configuration 14.10 full blown image installs fine. Dmesg logs are attached: Looking at dmesg logs point out that: LSI (avago) driver loads fine During further interaction with raid volume during the installation process, firmware errors are seen [ 196.991417] megasas: FW status 0x3 [ 196.999376] megasas: FW status 0x3 [ 197.007376] megasas: FW status 0x3 Further down the process I/O errors are thrown [ 217.438664] Buffer I/O error on device sda2, logical block 22052864 [ 217.438671] Buffer I/O error on device sda2, logical block 22052865 [ 217.438678] Buffer I/O error on device sda2, logical block 22052866 [ 217.438686] Buffer I/O error on device sda2, logical block 22052867 Full dmesg log is attached. Snippet is pasted below highlighting: It can be noted that there’s a Mellanox Connectx 3 pro card with some test Firmware on our setup. We can Ignore any diagnostic messages from that card in dmesg logs for the purpose of this bug. Thanks Adi Gangidi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483893] Re: linux-lts-trusty: 3.13.0-62.102~precise1 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-phase-changed:Wednesday, 12. August 2015 21:01 UTC + kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC -- 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~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: 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: 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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-phase-changed:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483922] Re: linux-lts-vivid: 3.19.0-26.28~14.04.1 -proposed tracker
** Description changed: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-phase-changed:Wednesday, 12. August 2015 23:01 UTC + kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC -- 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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-phase-changed:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483893] Re: linux-lts-trusty: 3.13.0-62.102~precise1 -proposed tracker
Promoted to proposed: linux-lts-trusty| 3.13.0-62.102~precise1 | precise-proposed | source linux-signed-lts-trusty | 3.13.0-62.102~precise1 | precise-proposed | source ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => 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/1483893 Title: linux-lts-trusty: 3.13.0-62.102~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: 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: 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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-phase-changed:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:56 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483922] Re: linux-lts-vivid: 3.19.0-26.28~14.04.1 -proposed tracker
Promoted to proposed: linux-lts-vivid| 3.19.0-26.28~14.04.1 | trusty-proposed | source linux-signed-lts-vivid | 3.19.0-26.28~14.04.1 | trusty-proposed | source ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Released -- 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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-phase-changed:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 13. August 2015 16:57 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: linux (Ubuntu Utopic) Status: In Progress => Fix Committed ** Also affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-lts-utopic (Ubuntu Precise) ** No longer affects: linux-lts-utopic (Ubuntu Utopic) ** No longer affects: linux-lts-utopic (Ubuntu Vivid) ** No longer affects: linux-lts-utopic (Ubuntu Wily) ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: New 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 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported
This is it. Kernel 3.19 is the man. Nothing has worked before I switched to this kernel but now it's working. Thanks everybody! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported Status in HWE Next: Triaged Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Triaged Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C 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.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. Qualcomm Atheros Device [168c:003e] (rev 20) mainline commit d63955b33b3bee45d784ffdfafeb93076c765660 [6.221281] ath10k_pci :02:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0 [6.417386] ath10k_pci :02:00.0: Direct firmware load for ath10k/cal-pci-:02:00.0.bin failed with error -2 [6.417404] ath10k_pci :02:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2 [6.417407] ath10k_pci :02:00.0: failed to load spec board file, falling back to generic: -2 [6.417416] ath10k_pci :02:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board.bin failed with error -2 [6.417418] ath10k_pci :02:00.0: failed to fetch generic board data: -2 [6.417420] ath10k_pci :02:00.0: failed to fetch board file: -2 [6.417421] ath10k_pci :02:00.0: could not fetch firmware files (-2) [6.417423] ath10k_pci :02:00.0: could not probe fw (-2) failed to find it in https://github.com/kvalo/ath10k-firmware or https://github.com/sumdog/ath10k-firmware To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1383184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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."
** Changed in: linux (Ubuntu Vivid) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1484587] Re: CPU frequency management fails to re-engage on resume from suspend
I have tried to recreate this with the following two mainline kernels: v4.2-rc6-unstable v4.2.0-999 (201508130157) However, it is somewhat difficult to compare the behavior apples-to- apples the way I normally do, as cpupower is not available for those kernels (no linux-tools packages installed for them). I would appreciate any advice on the best way to show the problem's presence/absence in an objective or definitive way across kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484587 Title: CPU frequency management fails to re-engage on resume from suspend Status in linux package in Ubuntu: Confirmed Status in pm-utils package in Ubuntu: New Bug description: Behavior: CPU frequency management fails to re-engage on resume from suspend. On resume, the CPUs are stuck around a single frequency (usually a low idle frequency). I use indicator-cpufreq for manual governor control. On resume, indicator-cpufreq indicates the low frequency state in its live cpu performance display in the icon. However, in its governor menu, it still shows as in use whichever governor was selected before suspend, even though that governor is not actually or properly controlling the CPU state. Upon manually switching to the unused governor in indicator-cpufreq, this behavior resolves, and the newly-chosen governor begins performing its duties. I can then immediately switch back to the desired (pre-suspend) governor with no issues. PM logs appear to show a successful resume of cpu frequency management, even though the modules did not actually gain effective control of the processor frequencies. Expected behavior: On resume, the CPU frequencies should continue being managed as they were before suspend without the need for manual user input. Also, in the event that they do not, an error/warning should appear -- if not to the user, then in the pm suspend/resume logs. Other information that may or may not be relevant: On this system, the "powersave" governor is always automatically chosen at startup, although not until a minute or so after session login. The choice of an alternate governor "performance" from indicator-cpufreq is not persistent across reboots. Further, if I manually toggle the governors at the beginning of my first session after boot, and I settle on "performance", some automated script will force it back to "powersave" at the usual time about a minute after login. To use the "performance" governor, I must select it after waiting an interval following login, and I must always switch to powersave and back to performance after each resume from suspend. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3887 F pulseaudio /dev/snd/controlC1: adam 3887 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 13 11:41:27 2015 InstallationDate: Installed on 2014-08-10 (368 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ENVY 15 x360 PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 22D6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 89.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 15 x360 PC dmi.product.version: 0974100022405F0420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483657] onza (i386) - tests ran: 153, failed: 0
tests ran: 153, failed: 0; http://kernel.ubuntu.com/testing/onza__3.13.0-62.102__2015-08-13_13-54-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/1483657 Title: linux: 3.13.0-62.102 -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: Confirmed Bug description: This bug is for tracking the 3.13.0-62.102 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 11. August 2015 11:08 UTC kernel-stable-Prepare-package-end:Tuesday, 11. August 2015 21:05 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 11. August 2015 21:05 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 12. August 2015 16:12 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 12. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Wednesday, 12. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Wednesday, 12. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 12. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 12. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484497] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1484497 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484497 Title: [Wily] wakes up green drives without a valid reason Status in linux package in Ubuntu: Incomplete Bug description: Hi, a minimalist Wily server install, around 4.5 GiB small does cause endless spin downs and spin ups, so that green drives get damaged. I maintain an around 37.5 GiB large Arch Linux install, quasi using the same software used by the Wily install and in addition a little bit more software, which isn't used by the Wily install. For Arch Linux I don't experience this issue. I expect the same for an Ubuntu install. I'm already hunting the culprit, see https://lists.ubuntu.com/archives/ubuntu-studio-devel/2015-August/006570.html and https://lists.ubuntu.com/archives/ubuntu-studio-devel/2015-August/006571.html, but run out of ideas. The claim the install is 2 GiB small is a typo, the backup archive is of that size. However, assumed Ubuntu won't contribute to http://andrewmcconnell.photoshelter.com/gallery/GoLuiBLHIsmM this "feature" should be removed from the defaults. $ lsb_release -rd Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 Regards, Ralf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475608] Re: bluetooth dual sim
** Also affects: telepathy-ofono (Ubuntu) Importance: Undecided Status: New -- 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/1475608 Title: bluetooth dual sim Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Bug description: Hi, I have a BQ phone with 2 SIM-cards. When connected to my handsfree-set (built-in radio set Opel), it shows the provider of my 2nd SIM. When someone phones me on SIM 1, it doesn't go to the hands-free set. But I when I answer the phone (while still connected with BT), I cannot hear the other person, nor does he hear me. Calls on SIM 2 are working as expected. Regards, Carl To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1475608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484497] Re: [Wily] wakes up green drives without a valid reason
** 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/1484497 Title: [Wily] wakes up green drives without a valid reason Status in linux package in Ubuntu: New Bug description: Hi, a minimalist Wily server install, around 4.5 GiB small does cause endless spin downs and spin ups, so that green drives get damaged. I maintain an around 37.5 GiB large Arch Linux install, quasi using the same software used by the Wily install and in addition a little bit more software, which isn't used by the Wily install. For Arch Linux I don't experience this issue. I expect the same for an Ubuntu install. I'm already hunting the culprit, see https://lists.ubuntu.com/archives/ubuntu-studio-devel/2015-August/006570.html and https://lists.ubuntu.com/archives/ubuntu-studio-devel/2015-August/006571.html, but run out of ideas. The claim the install is 2 GiB small is a typo, the backup archive is of that size. However, assumed Ubuntu won't contribute to http://andrewmcconnell.photoshelter.com/gallery/GoLuiBLHIsmM this "feature" should be removed from the defaults. $ lsb_release -rd Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 Regards, Ralf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475608] Re: bluetooth dual sim
thanks, that could be the same issue than bug #1418040 ** Package changed: bluez-btsco (Ubuntu) => bluez (Ubuntu) ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- 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/1475608 Title: bluetooth dual sim Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Bug description: Hi, I have a BQ phone with 2 SIM-cards. When connected to my handsfree-set (built-in radio set Opel), it shows the provider of my 2nd SIM. When someone phones me on SIM 1, it doesn't go to the hands-free set. But I when I answer the phone (while still connected with BT), I cannot hear the other person, nor does he hear me. Calls on SIM 2 are working as expected. Regards, Carl To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1475608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483922] Re: linux-lts-vivid: 3.19.0-26.28~14.04.1 -proposed tracker
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-vivid -- 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/1483922 Title: linux-lts-vivid: 3.19.0-26.28~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-26.28~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:Tuesday, 11. August 2015 23:01 UTC kernel-stable-master-bug:1483630 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 23:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 23:01 UTC kernel-stable-phase-changed:Wednesday, 12. August 2015 23:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484497] [NEW] [Wily] wakes up green drives without a valid reason
You have been subscribed to a public bug: Hi, a minimalist Wily server install, around 4.5 GiB small does cause endless spin downs and spin ups, so that green drives get damaged. I maintain an around 37.5 GiB large Arch Linux install, quasi using the same software used by the Wily install and in addition a little bit more software, which isn't used by the Wily install. For Arch Linux I don't experience this issue. I expect the same for an Ubuntu install. I'm already hunting the culprit, see https://lists.ubuntu.com/archives/ubuntu-studio-devel/2015-August/006570.html and https://lists.ubuntu.com/archives/ubuntu-studio-devel/2015-August/006571.html, but run out of ideas. The claim the install is 2 GiB small is a typo, the backup archive is of that size. However, assumed Ubuntu won't contribute to http://andrewmcconnell.photoshelter.com/gallery/GoLuiBLHIsmM this "feature" should be removed from the defaults. $ lsb_release -rd Description:Ubuntu Wily Werewolf (development branch) Release:15.10 Regards, Ralf ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- [Wily] wakes up green drives without a valid reason https://bugs.launchpad.net/bugs/1484497 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 1484587] Re: CPU frequency management fails to re-engage on resume from suspend
** Attachment added: "kern.log from session in which cpu freq control failed on resume from suspend" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484587/+attachment/227/+files/kern_log_cpu_resume_bug.txt ** Also affects: pm-utils (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/1484587 Title: CPU frequency management fails to re-engage on resume from suspend Status in linux package in Ubuntu: Confirmed Status in pm-utils package in Ubuntu: New Bug description: Behavior: CPU frequency management fails to re-engage on resume from suspend. On resume, the CPUs are stuck around a single frequency (usually a low idle frequency). I use indicator-cpufreq for manual governor control. On resume, indicator-cpufreq indicates the low frequency state in its live cpu performance display in the icon. However, in its governor menu, it still shows as in use whichever governor was selected before suspend, even though that governor is not actually or properly controlling the CPU state. Upon manually switching to the unused governor in indicator-cpufreq, this behavior resolves, and the newly-chosen governor begins performing its duties. I can then immediately switch back to the desired (pre-suspend) governor with no issues. PM logs appear to show a successful resume of cpu frequency management, even though the modules did not actually gain effective control of the processor frequencies. Expected behavior: On resume, the CPU frequencies should continue being managed as they were before suspend without the need for manual user input. Also, in the event that they do not, an error/warning should appear -- if not to the user, then in the pm suspend/resume logs. Other information that may or may not be relevant: On this system, the "powersave" governor is always automatically chosen at startup, although not until a minute or so after session login. The choice of an alternate governor "performance" from indicator-cpufreq is not persistent across reboots. Further, if I manually toggle the governors at the beginning of my first session after boot, and I settle on "performance", some automated script will force it back to "powersave" at the usual time about a minute after login. To use the "performance" governor, I must select it after waiting an interval following login, and I must always switch to powersave and back to performance after each resume from suspend. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3887 F pulseaudio /dev/snd/controlC1: adam 3887 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 13 11:41:27 2015 InstallationDate: Installed on 2014-08-10 (368 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ENVY 15 x360 PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 22D6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 89.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 15 x360 PC dmi.product.version: 0974100022405F0420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484587] 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/1484587 Title: CPU frequency management fails to re-engage on resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: Behavior: CPU frequency management fails to re-engage on resume from suspend. On resume, the CPUs are stuck around a single frequency (usually a low idle frequency). I use indicator-cpufreq for manual governor control. On resume, indicator-cpufreq indicates the low frequency state in its live cpu performance display in the icon. However, in its governor menu, it still shows as in use whichever governor was selected before suspend, even though that governor is not actually or properly controlling the CPU state. Upon manually switching to the unused governor in indicator-cpufreq, this behavior resolves, and the newly-chosen governor begins performing its duties. I can then immediately switch back to the desired (pre-suspend) governor with no issues. PM logs appear to show a successful resume of cpu frequency management, even though the modules did not actually gain effective control of the processor frequencies. Expected behavior: On resume, the CPU frequencies should continue being managed as they were before suspend without the need for manual user input. Also, in the event that they do not, an error/warning should appear -- if not to the user, then in the pm suspend/resume logs. Other information that may or may not be relevant: On this system, the "powersave" governor is always automatically chosen at startup, although not until a minute or so after session login. The choice of an alternate governor "performance" from indicator-cpufreq is not persistent across reboots. Further, if I manually toggle the governors at the beginning of my first session after boot, and I settle on "performance", some automated script will force it back to "powersave" at the usual time about a minute after login. To use the "performance" governor, I must select it after waiting an interval following login, and I must always switch to powersave and back to performance after each resume from suspend. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3887 F pulseaudio /dev/snd/controlC1: adam 3887 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 13 11:41:27 2015 InstallationDate: Installed on 2014-08-10 (368 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ENVY 15 x360 PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 22D6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 89.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 15 x360 PC dmi.product.version: 0974100022405F0420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475608] [NEW] bluetooth dual sim
You have been subscribed to a public bug: Hi, I have a BQ phone with 2 SIM-cards. When connected to my handsfree-set (built-in radio set Opel), it shows the provider of my 2nd SIM. When someone phones me on SIM 1, it doesn't go to the hands-free set. But I when I answer the phone (while still connected with BT), I cannot hear the other person, nor does he hear me. Calls on SIM 2 are working as expected. Regards, Carl ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- bluetooth dual sim https://bugs.launchpad.net/bugs/1475608 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez 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 1294283] Re: Memory balloning in Hyper-V generation 2 does not work
Hi Joshua, I found an evaluation copy of Hyper-V Server[0]. Do you happen to know if the evaluation copy will limit what type of tests can be performed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1294283 Title: Memory balloning in Hyper-V generation 2 does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: The generation 2 VM has been assinged a memory range of 512 MiB- 4096MiB with a starting memory of 512 MiB. It should get additional memory when needed, but the total available memory in the VM stays at the intial 512 MiB and the kernel starts swapping instead of allocating more memory from the host. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Mar 18 19:28:54 2014 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (6 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2673d21f-4b48-43f1-9b06-8c141a492700 InstallationDate: Installed on 2014-03-29 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed root=UUID=cccf5e59-012e-4ab5-a6ba-08850e60aba1 ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-22-generic N/A linux-backports-modules-3.13.0-22-generic N/A linux-firmware 1.127 RfKill: Tags: trusty Uname: Linux 3.13.0-22-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/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.mo
[Kernel-packages] [Bug 1294283] Re: Memory balloning in Hyper-V generation 2 does not work
That still does not answer if you are asking me to test anything. I probably do not have anything to add here, especially since I upgraded the host system to Windows 10 in the mean time, any result would be therefore not exactly comparable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1294283 Title: Memory balloning in Hyper-V generation 2 does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: The generation 2 VM has been assinged a memory range of 512 MiB- 4096MiB with a starting memory of 512 MiB. It should get additional memory when needed, but the total available memory in the VM stays at the intial 512 MiB and the kernel starts swapping instead of allocating more memory from the host. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Mar 18 19:28:54 2014 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (6 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2673d21f-4b48-43f1-9b06-8c141a492700 InstallationDate: Installed on 2014-03-29 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed root=UUID=cccf5e59-012e-4ab5-a6ba-08850e60aba1 ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-22-generic N/A linux-backports-modules-3.13.0-22-generic N/A linux-firmware 1.127 RfKill: Tags: trusty Uname: Linux 3.13.0-22-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/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.ve
[Kernel-packages] [Bug 1483893] Re: linux-lts-trusty: 3.13.0-62.102~precise1 -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-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1483893 Title: linux-lts-trusty: 3.13.0-62.102~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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-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-62.102~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:Tuesday, 11. August 2015 21:03 UTC kernel-stable-master-bug:1483657 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 21:01 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 21:01 UTC kernel-stable-phase-changed:Wednesday, 12. August 2015 21:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484587] [NEW] CPU frequency management fails to re-engage on resume from suspend
Public bug reported: Behavior: CPU frequency management fails to re-engage on resume from suspend. On resume, the CPUs are stuck around a single frequency (usually a low idle frequency). I use indicator-cpufreq for manual governor control. On resume, indicator-cpufreq indicates the low frequency state in its live cpu performance display in the icon. However, in its governor menu, it still shows as in use whichever governor was selected before suspend, even though that governor is not actually or properly controlling the CPU state. Upon manually switching to the unused governor in indicator-cpufreq, this behavior resolves, and the newly-chosen governor begins performing its duties. I can then immediately switch back to the desired (pre- suspend) governor with no issues. PM logs appear to show a successful resume of cpu frequency management, even though the modules did not actually gain effective control of the processor frequencies. Expected behavior: On resume, the CPU frequencies should continue being managed as they were before suspend without the need for manual user input. Also, in the event that they do not, an error/warning should appear -- if not to the user, then in the pm suspend/resume logs. Other information that may or may not be relevant: On this system, the "powersave" governor is always automatically chosen at startup, although not until a minute or so after session login. The choice of an alternate governor "performance" from indicator-cpufreq is not persistent across reboots. Further, if I manually toggle the governors at the beginning of my first session after boot, and I settle on "performance", some automated script will force it back to "powersave" at the usual time about a minute after login. To use the "performance" governor, I must select it after waiting an interval following login, and I must always switch to powersave and back to performance after each resume from suspend. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3887 F pulseaudio /dev/snd/controlC1: adam 3887 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 13 11:41:27 2015 InstallationDate: Installed on 2014-08-10 (368 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ENVY 15 x360 PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 22D6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 89.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 15 x360 PC dmi.product.version: 0974100022405F0420180 dmi.sys.vendor: Hewlett-Packard ** 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/1484587 Title: CPU frequency management fails to re-engage on resume from suspend Status in linux package in Ubuntu: New Bug description: Behavior: CPU frequency management fails to re-engage on resume from suspend. On resume, the CPUs are stuck around a single frequency (usually a low idle frequency). I use indicator-cpufreq for manual governor control. On resume, indicator-cpufreq indicates the low frequency state in its live cpu performance display in the icon. However, in its governor menu, it still shows as in use whichever governor was selected before suspend, even though that governor is not actually or properly controlling the CPU state. Upon manually switching to the unused governor in indicator-cpufreq, this behavior resolves, and the newly-chosen governor begins performing its duties. I can then immediately switch back to the desired (pre-suspend) governor with no issues. PM logs appear to show a successful resume of cpu frequency management, even though the modules did not actually gain effective control of the processor frequencies.
[Kernel-packages] [Bug 1294283] Re: Memory balloning in Hyper-V generation 2 does not work
We're happy to help with the setup of a test case, and we can test things on our systems as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1294283 Title: Memory balloning in Hyper-V generation 2 does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: The generation 2 VM has been assinged a memory range of 512 MiB- 4096MiB with a starting memory of 512 MiB. It should get additional memory when needed, but the total available memory in the VM stays at the intial 512 MiB and the kernel starts swapping instead of allocating more memory from the host. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Mar 18 19:28:54 2014 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (6 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2673d21f-4b48-43f1-9b06-8c141a492700 InstallationDate: Installed on 2014-03-29 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed root=UUID=cccf5e59-012e-4ab5-a6ba-08850e60aba1 ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-22-generic N/A linux-backports-modules-3.13.0-22-generic N/A linux-firmware 1.127 RfKill: Tags: trusty Uname: Linux 3.13.0-22-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/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIRelease
[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller
1) I would definitely recommend booting up/checking the logs multiple times on every leg of the test to ensure that it gets a consistent result. 2) I don't understand how this would have happened. It does occur to me that if we're dealing with possible IO corruption there could be other issues too, I'd suggest: If you can reproduce without having the OS or Kernel code on the Avago controller that would be the best option. (like I described in C#17) If not, reboot back to the stable v3.16 kernel before doing any git or build commands. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475166 Title: Ubuntu 15.04 Install Error with Avago Controller Status in linux package in Ubuntu: Triaged Bug description: Hello Canonical Team We are running to an issue installing ubuntu PPC64LE 15.04 full blown image on our servers (with RAID controller). Installation hangs around 70% of progress. An important part of our configuration is Avago RAID controller: 9361-8i Firmware version we used is 4.300.00-4429, and the package is 24.10.0-0002. IMPORTANT: It has to be noted that with same hardware configuration 14.10 full blown image installs fine. Dmesg logs are attached: Looking at dmesg logs point out that: LSI (avago) driver loads fine During further interaction with raid volume during the installation process, firmware errors are seen [ 196.991417] megasas: FW status 0x3 [ 196.999376] megasas: FW status 0x3 [ 197.007376] megasas: FW status 0x3 Further down the process I/O errors are thrown [ 217.438664] Buffer I/O error on device sda2, logical block 22052864 [ 217.438671] Buffer I/O error on device sda2, logical block 22052865 [ 217.438678] Buffer I/O error on device sda2, logical block 22052866 [ 217.438686] Buffer I/O error on device sda2, logical block 22052867 Full dmesg log is attached. Snippet is pasted below highlighting: It can be noted that there’s a Mellanox Connectx 3 pro card with some test Firmware on our setup. We can Ignore any diagnostic messages from that card in dmesg logs for the purpose of this bug. Thanks Adi Gangidi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1476900] Re: Backport Intel 8260 Wifi/BT firmwares
Rahul: In order for your wifi to work you either need to be running running kernel version 4.1 or later or else be using a iwlwifi backport driver from that kernel version or later. The standard kernels for 14.04 and 15.04 do not support this hardware (at least not with any publicly released version of the firmware), but the kernel in wily does. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1476900 Title: Backport Intel 8260 Wifi/BT firmwares Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Trusty: Fix Released Status in linux-firmware source package in Vivid: Fix Released Bug description: Both Intel 8260 Wifi and Bluetooth firmwares are now available in mainline linux-firmware and has been tested. Vivid currently doesn't support Intel 8260 Wifi and BT, and need to backport the firmwares. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1476900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1294283] Re: Memory balloning in Hyper-V generation 2 does not work
@Joshua do you mean me? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1294283 Title: Memory balloning in Hyper-V generation 2 does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: The generation 2 VM has been assinged a memory range of 512 MiB- 4096MiB with a starting memory of 512 MiB. It should get additional memory when needed, but the total available memory in the VM stays at the intial 512 MiB and the kernel starts swapping instead of allocating more memory from the host. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Mar 18 19:28:54 2014 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (6 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2673d21f-4b48-43f1-9b06-8c141a492700 InstallationDate: Installed on 2014-03-29 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed root=UUID=cccf5e59-012e-4ab5-a6ba-08850e60aba1 ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-22-generic N/A linux-backports-modules-3.13.0-22-generic N/A linux-firmware 1.127 RfKill: Tags: trusty Uname: Linux 3.13.0-22-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/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIR
[Kernel-packages] [Bug 1294283] Re: Memory balloning in Hyper-V generation 2 does not work
Do you need our assistance in setting up tests of this particular function on Hyper-V? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1294283 Title: Memory balloning in Hyper-V generation 2 does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: The generation 2 VM has been assinged a memory range of 512 MiB- 4096MiB with a starting memory of 512 MiB. It should get additional memory when needed, but the total available memory in the VM stays at the intial 512 MiB and the kernel starts swapping instead of allocating more memory from the host. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Mar 18 19:28:54 2014 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (6 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2673d21f-4b48-43f1-9b06-8c141a492700 InstallationDate: Installed on 2014-03-29 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed root=UUID=cccf5e59-012e-4ab5-a6ba-08850e60aba1 ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-22-generic N/A linux-backports-modules-3.13.0-22-generic N/A linux-firmware 1.127 RfKill: Tags: trusty Uname: Linux 3.13.0-22-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/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/2
[Kernel-packages] [Bug 1484556] Re: package linux-headers-3.13.0-57 3.13.0-57.95 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484556 Title: package linux-headers-3.13.0-57 3.13.0-57.95 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Confirmed Bug description: error appeared during sy stem update. I think linux-headers was higher than 3.13.0.57 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-headers-3.13.0-57 3.13.0-57.95 ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22 Uname: Linux 3.13.0-58-generic i686 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 1976 F pulseaudio Date: Thu Aug 13 08:10:44 2015 DuplicateSignature: package:linux-headers-3.13.0-57:3.13.0-57.95:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=bd4563b7-e601-4deb-b669-9a43546dc9c7 InstallationDate: Installed on 2013-10-07 (675 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: Acer Aspire 1430 PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-58-generic root=UUID=6f98f555-a7b3-4823-b978-0dd1d58d8c61 ro splash quiet 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 SourcePackage: linux Title: package linux-headers-3.13.0-57 3.13.0-57.95 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-08-21 (356 days ago) dmi.bios.date: 09/28/2010 dmi.bios.vendor: INSYDE dmi.bios.version: V1.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JV10_CS dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.20:bd09/28/2010:svnAcer:pnAspire1430:pvrV1.20:rvnIntelCorp.:rnJV10_CS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1430 dmi.product.version: V1.20 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484556] 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/1484556 Title: package linux-headers-3.13.0-57 3.13.0-57.95 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Confirmed Bug description: error appeared during sy stem update. I think linux-headers was higher than 3.13.0.57 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-headers-3.13.0-57 3.13.0-57.95 ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22 Uname: Linux 3.13.0-58-generic i686 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 1976 F pulseaudio Date: Thu Aug 13 08:10:44 2015 DuplicateSignature: package:linux-headers-3.13.0-57:3.13.0-57.95:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=bd4563b7-e601-4deb-b669-9a43546dc9c7 InstallationDate: Installed on 2013-10-07 (675 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: Acer Aspire 1430 PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-58-generic root=UUID=6f98f555-a7b3-4823-b978-0dd1d58d8c61 ro splash quiet 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 SourcePackage: linux Title: package linux-headers-3.13.0-57 3.13.0-57.95 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-08-21 (356 days ago) dmi.bios.date: 09/28/2010 dmi.bios.vendor: INSYDE dmi.bios.version: V1.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JV10_CS dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.20:bd09/28/2010:svnAcer:pnAspire1430:pvrV1.20:rvnIntelCorp.:rnJV10_CS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1430 dmi.product.version: V1.20 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484556] [NEW] package linux-headers-3.13.0-57 3.13.0-57.95 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co
Public bug reported: error appeared during sy stem update. I think linux-headers was higher than 3.13.0.57 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-headers-3.13.0-57 3.13.0-57.95 ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22 Uname: Linux 3.13.0-58-generic i686 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 1976 F pulseaudio Date: Thu Aug 13 08:10:44 2015 DuplicateSignature: package:linux-headers-3.13.0-57:3.13.0-57.95:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=bd4563b7-e601-4deb-b669-9a43546dc9c7 InstallationDate: Installed on 2013-10-07 (675 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: Acer Aspire 1430 PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-58-generic root=UUID=6f98f555-a7b3-4823-b978-0dd1d58d8c61 ro splash quiet 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 SourcePackage: linux Title: package linux-headers-3.13.0-57 3.13.0-57.95 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-08-21 (356 days ago) dmi.bios.date: 09/28/2010 dmi.bios.vendor: INSYDE dmi.bios.version: V1.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JV10_CS dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.20:bd09/28/2010:svnAcer:pnAspire1430:pvrV1.20:rvnIntelCorp.:rnJV10_CS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1430 dmi.product.version: V1.20 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-package i386 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/1484556 Title: package linux-headers-3.13.0-57 3.13.0-57.95 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Confirmed Bug description: error appeared during sy stem update. I think linux-headers was higher than 3.13.0.57 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-headers-3.13.0-57 3.13.0-57.95 ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22 Uname: Linux 3.13.0-58-generic i686 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 1976 F pulseaudio Date: Thu Aug 13 08:10:44 2015 DuplicateSignature: package:linux-headers-3.13.0-57:3.13.0-57.95:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=bd4563b7-e601-4deb-b669-9a43546dc9c7 InstallationDate: Installed on 2013-10-07 (675 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: Acer Aspire 1430 PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-58-generic root=UUID=6f98f555-a7b3-4823-b978-0dd1d58d8c61 ro splash quiet 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 SourcePackage: linux Title: package linux-headers-3.13.0-57 3.13.0-57.95 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-08-21 (356 days ago) dmi.bios.date: 09/28/2010 dmi.bios.vendor: INSYDE dmi.bios.version: V1.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JV10_CS dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.20:bd09/28/2010:svnAcer:pnAspire1430:pvrV1.20:rvnIntelCorp.:rnJV10_CS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1430 dmi.product.version: V1.20 dmi.sys.vendor: Acer To manage
[Kernel-packages] [Bug 1476900] Re: Backport Intel 8260 Wifi/BT firmwares
I have updated the firmware with 1.127.15, still my Wifi doesnot work. My lap top has intel 8260 Wifi Hardware -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1476900 Title: Backport Intel 8260 Wifi/BT firmwares Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Trusty: Fix Released Status in linux-firmware source package in Vivid: Fix Released Bug description: Both Intel 8260 Wifi and Bluetooth firmwares are now available in mainline linux-firmware and has been tested. Vivid currently doesn't support Intel 8260 Wifi and BT, and need to backport the firmwares. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1476900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483790] larsen (i386) - tests ran: 153, failed: 1
tests ran: 153, failed: 1; http://kernel.ubuntu.com/testing/larsen__3.16.0-46.62~14.04.1__2015-08-13_11-15-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/1483790 Title: linux-lts-utopic: 3.16.0-46.62~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: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-46.62~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:Tuesday, 11. August 2015 15:10 UTC kernel-stable-Prepare-package-end:Wednesday, 12. August 2015 01:02 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 12. August 2015 01:02 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 12. August 2015 16:12 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 12. August 2015 18:02 UTC kernel-stable-Verification-testing-start:Wednesday, 12. August 2015 18:02 UTC kernel-stable-Certification-testing-start:Wednesday, 12. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 12. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 12. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483657] onza (amd64) - tests ran: 180, failed: 2
tests ran: 180, failed: 2; http://kernel.ubuntu.com/testing/onza__3.13.0-62.102__2015-08-13_10-56-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/1483657 Title: linux: 3.13.0-62.102 -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: Confirmed Bug description: This bug is for tracking the 3.13.0-62.102 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 11. August 2015 11:08 UTC kernel-stable-Prepare-package-end:Tuesday, 11. August 2015 21:05 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 11. August 2015 21:05 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 12. August 2015 16:12 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 12. August 2015 18:01 UTC kernel-stable-Verification-testing-start:Wednesday, 12. August 2015 18:01 UTC kernel-stable-Certification-testing-start:Wednesday, 12. August 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 12. August 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 12. August 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1483657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
