[Kernel-packages] [Bug 1415153] Re: CVE-2011-1350
** Changed in: linux (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux (Ubuntu Precise) Status: New = Invalid ** Changed in: linux (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux (Ubuntu Vivid) 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/1415153 Title: CVE-2011-1350 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: New Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: New 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: New Status in linux-lts-raring package in Ubuntu: New Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: New Status in linux-lts-utopic package in Ubuntu: New Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: New Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: New Status in linux-ec2 source package in Lucid: New Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: New Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: New Status in linux-lts-raring source package in Lucid: New Status in linux-lts-saucy source package in Lucid: New Status in linux-lts-trusty source package in Lucid: New Status in linux-lts-utopic source package in Lucid: New Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: New Status in linux-ti-omap4 source package in Lucid: New Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: New 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: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: New 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: New Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: New Status in linux-ec2 source package in Trusty: New Status in linux-flo source package in Trusty: New Status in linux-fsl-imx51 source package in Trusty: New Status in linux-goldfish source package in Trusty: New 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: New Status in linux-lts-raring source package in Trusty: New Status in linux-lts-saucy source package in Trusty: New Status in linux-lts-trusty source package in Trusty: New Status in linux-lts-utopic source package in Trusty: New Status in linux-mako source package in Trusty: New Status in linux-manta source package in Trusty: New Status in linux-mvl-dove source package in Trusty: New Status in linux-ti-omap4 source package in Trusty: New Status in linux source package in Utopic: Invalid Status in linux-armadaxp source package in Utopic: New Status in linux-ec2 source package in Utopic: New Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: New Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: New Status in linux-lts-raring source package in Utopic: New Status in linux-lts-saucy source package in
[Kernel-packages] [Bug 1349804] Re: CVE-2014-5077
utopic, vivid are not affected according to http://people.canonical.com /~ubuntu-security/cve/2014/CVE-2014-5077.html ** Changed in: linux (Ubuntu Utopic) Status: Fix Committed = Invalid ** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1349804 Title: CVE-2014-5077 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-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 Lucid: Fix Released Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Fix Released Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-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: Fix Released Status in linux-lts-utopic 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-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 Utopic: Invalid Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in
[Kernel-packages] [Bug 1392008] Re: CVE-2014-7826
** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1392008 Title: CVE-2014-7826 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-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 Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-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: Fix Released Status in linux-lts-utopic 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-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 Utopic: Fix Released Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in
[Kernel-packages] [Bug 1436188] [NEW] bose soundlink color: bluetooth always disconnects 1 times
Public bug reported: Hello, I connect the bose soundlink bluethooth on my samsung desktop with Ubuntu 14.04 LTS 64bit when I start my destop, I turn on the bluethooth, and soundlink tells me that ubuntu-0 is connected. then 20 seconds after she is tell me that ubuntu-0 it is disconnected. I reconnected on ubuntu and then soundlink it works. But I always this problem. My soudlink works great with my other android devices ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth bose colour soundlink ** Attachment added: Capture bluetooth setting https://bugs.launchpad.net/bugs/1436188/+attachment/4355268/+files/Capture%20du%202015-03-25%2007%3A43%3A24.png -- 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/1436188 Title: bose soundlink color: bluetooth always disconnects 1 times Status in bluez package in Ubuntu: New Bug description: Hello, I connect the bose soundlink bluethooth on my samsung desktop with Ubuntu 14.04 LTS 64bit when I start my destop, I turn on the bluethooth, and soundlink tells me that ubuntu-0 is connected. then 20 seconds after she is tell me that ubuntu-0 it is disconnected. I reconnected on ubuntu and then soundlink it works. But I always this problem. My soudlink works great with my other android devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1436188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335314] Re: CVE-2014-4611
** Changed in: linux (Ubuntu) Status: Fix Committed = Invalid ** Changed in: linux (Ubuntu Utopic) Status: Fix Committed = Invalid ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New = Invalid ** Changed in: linux-lts-backport-natty (Ubuntu) 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/1335314 Title: CVE-2014-4611 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Released Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Saucy: Fix Released Status in linux-armadaxp source package in Saucy: Invalid Status in linux-ec2 source package in Saucy: Invalid Status in linux-fsl-imx51 source package in Saucy: Invalid Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux-lts-quantal source package in Saucy: Invalid Status in linux-lts-raring source package in Saucy: Invalid Status in linux-lts-saucy source package in Saucy: Invalid Status in linux-mvl-dove source package in Saucy: Invalid Status in linux-ti-omap4 source package in Saucy: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Invalid Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Bug description: Integer overflow in the LZ4 algorithm implementation, as used in Yann Collet LZ4 before r118 and in the lz4_uncompress function in lib/lz4/lz4_decompress.c in the Linux kernel before 3.15.2, on 32-bit platforms might allow context-dependent attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted Literal Run that would be improperly handled by programs not complying with an API
[Kernel-packages] [Bug 1413741] Re: CVE-2014-8159
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (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/1413741 Title: CVE-2014-8159 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-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-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 Lucid: Fix Released Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: New Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-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: Fix Released Status in linux-lts-utopic 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: 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-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 Utopic: Fix Released Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid
[Kernel-packages] [Bug 1156790] Re: CVE-2013-2546
** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156790 Title: CVE-2013-2546 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: New Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Invalid Status in linux-lts-backport-oneiric source package in Lucid: Invalid Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: New Status in linux-lts-saucy source package in Lucid: New Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: New Status in linux-lts-saucy source package in Trusty: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in
[Kernel-packages] [Bug 1156784] Re: CVE-2013-1860
** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156784 Title: CVE-2013-1860 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Released Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Fix Released Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Won't Fix Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: New Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric 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: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic
[Kernel-packages] [Bug 1156795] Re: CVE-2013-2547
** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156795 Title: CVE-2013-2547 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: New Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Invalid Status in linux-lts-backport-oneiric source package in Lucid: Invalid Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: New Status in linux-lts-saucy source package in Lucid: New Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: New Status in linux-lts-saucy source package in Trusty: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in
[Kernel-packages] [Bug 1156799] Re: CVE-2013-2548
** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1156799 Title: CVE-2013-2548 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: New Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Invalid Status in linux-lts-backport-oneiric source package in Lucid: Invalid Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: New Status in linux-lts-saucy source package in Lucid: New Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: New Status in linux-lts-saucy source package in Trusty: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in
[Kernel-packages] [Bug 1335313] Re: CVE-2014-4608
** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1335313 Title: CVE-2014-4608 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-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 Lucid: Fix Released Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Fix Released Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-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: Fix Released Status in linux-lts-raring source package in Precise: Fix Released Status in linux-lts-saucy source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Fix 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-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 Utopic: Fix Released Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal
[Kernel-packages] [Bug 1415158] Re: CVE-2011-1352
** Changed in: linux (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux (Ubuntu Precise) Status: New = Invalid ** Changed in: linux (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux (Ubuntu Vivid) 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/1415158 Title: CVE-2011-1352 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: New Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: New 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: New Status in linux-lts-raring package in Ubuntu: New Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: New Status in linux-lts-utopic package in Ubuntu: New Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: New Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: New Status in linux-ec2 source package in Lucid: New Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: New Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: New Status in linux-lts-raring source package in Lucid: New Status in linux-lts-saucy source package in Lucid: New Status in linux-lts-trusty source package in Lucid: New Status in linux-lts-utopic source package in Lucid: New Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: New Status in linux-ti-omap4 source package in Lucid: New Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: New 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: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: New 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: New Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: New Status in linux-ec2 source package in Trusty: New Status in linux-flo source package in Trusty: New Status in linux-fsl-imx51 source package in Trusty: New Status in linux-goldfish source package in Trusty: New 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: New Status in linux-lts-raring source package in Trusty: New Status in linux-lts-saucy source package in Trusty: New Status in linux-lts-trusty source package in Trusty: New Status in linux-lts-utopic source package in Trusty: New Status in linux-mako source package in Trusty: New Status in linux-manta source package in Trusty: New Status in linux-mvl-dove source package in Trusty: New Status in linux-ti-omap4 source package in Trusty: New Status in linux source package in Utopic: Invalid Status in linux-armadaxp source package in Utopic: New Status in linux-ec2 source package in Utopic: New Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: New Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: New Status in linux-lts-raring source package in Utopic: New Status in linux-lts-saucy source package in
[Kernel-packages] [Bug 1155022] Re: CVE-2013-1825
** Changed in: linux (Ubuntu) Status: New = Invalid ** Changed in: linux (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu) Status: New = Invalid ** Changed in: linux-ti-omap4 (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/1155022 Title: CVE-2013-1825 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Invalid Status in linux-lts-backport-oneiric source package in Lucid: Won't Fix Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Oneiric: Invalid Status in linux-armadaxp source package in Oneiric: Invalid Status in linux-ec2 source package in Oneiric: Invalid Status in linux-fsl-imx51 source package in Oneiric: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux-lts-quantal source package in Oneiric: Invalid Status in linux-mvl-dove source package in Oneiric: Invalid Status in linux-ti-omap4 source package in Oneiric: Won't Fix Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Quantal: Won't Fix Status in linux-armadaxp source package in Quantal: Won't Fix Status in linux-ec2 source package in Quantal: Invalid Status in linux-fsl-imx51 source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux-mvl-dove source package in Quantal: Invalid Status in linux-ti-omap4 source package in Quantal: Won't Fix Status in linux source package in Raring: Won't Fix Status in linux-armadaxp source package in Raring: Won't Fix Status in linux-ec2 source package in Raring: Invalid Status in linux-fsl-imx51 source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-quantal source package in Raring: Invalid Status in linux-mvl-dove source package in Raring: Invalid Status in linux-ti-omap4 source package in Raring: Won't Fix Status in linux source package in Hardy: Invalid Status in linux-armadaxp source package in Hardy: Invalid Status in linux-ec2 source package in Hardy: Invalid Status in linux-fsl-imx51 source package in Hardy: Invalid Status in linux-lts-backport-maverick source package in Hardy: Invalid Status in linux-lts-backport-natty source package in Hardy: Invalid Status in
[Kernel-packages] [Bug 1158263] Re: CVE-2013-1848
** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1158263 Title: CVE-2013-1848 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Won't Fix Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: New Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric 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: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source
[Kernel-packages] [Bug 1158965] Re: CVE-2013-2634
** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1158965 Title: CVE-2013-2634 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Released Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Fix Released Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Won't Fix Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: New Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric 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: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic
[Kernel-packages] [Bug 1341472] Re: CVE-2014-4943
** Changed in: linux (Ubuntu Utopic) Status: Fix Committed = Invalid ** Changed in: linux (Ubuntu) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1341472 Title: CVE-2014-4943 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Released Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Fix Released Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Fix Released Status in linux-lts-saucy source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-trusty source package in Saucy: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Invalid Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Bug description: The PPPoL2TP feature in net/l2tp/l2tp_ppp.c in the Linux kernel through 3.15.6 allows local users to gain privileges by leveraging data-structure differences between an l2tp socket and an inet socket. Break-Fix: - 3cf521f7dc87c031617fd47e4b7aa2593c2f3daf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1341472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1153811] Re: CVE-2013-0913
** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1153811 Title: CVE-2013-0913 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Won't Fix Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: New Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric 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: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source
[Kernel-packages] [Bug 1435509] Re: cciss: hangs in modprobe, prevents server from booting
** Description changed: I've upgraded an Ubuntu 10.04 LTS server to 12.04 LTS. It now fails to boot. More specifically, kernel 3.2.0-77 hangs in the cciss driver during initialization. The hardware is an HP ProLiant DL385 G2. The RAID controller is HP - Smart Array P400: + Smart Array P600: lspci -knn -s 06:01 06:01.0 RAID bus controller [0104]: Hewlett-Packard Company Smart Array P600 [103c:3220] Subsystem: Hewlett-Packard Company 3 Gb/s SAS RAID [103c:3225] Kernel driver in use: cciss Kernel modules: cciss I can observe the boot process over serial console (attached: serial-console.log). You can see the kernel messages about cciss being detected, udev messages about modprobe timing out followed by boot process timeouts and a failure to mount the root filesystem. You can also see hung task messages from the kernel (kworker/0:2 and modprobe are both hung inside cciss), and you can see some of my futile attempts to look around in the initramfs. I can boot an older kernel (2.6.32-73-server, left over from Ubuntu 10.04 LTS) just fine. I'm afraid dmesg and other bits of information collected by apport for this bug report will be misleadingly from that older kernel. = WORKAROUND = Add 'pci=noioapicreroute' to the kernel command line. = WORKAROUND = ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-77-generic 3.2.0-77.114 ProcVersionSignature: Ubuntu 2.6.32-73.141-server 2.6.32.63+drm33.26 Uname: Linux 2.6.32-73-server x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: aplay: device_list:252: no soundcards found... ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 ArecordDevices: arecord: device_list:252: no soundcards found... CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [8.816593] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 19.233266] eth0: no IPv6 routers present [ 79.512524] Clocksource tsc unstable (delta = -264288670 ns) Date: Mon Mar 23 19:07:30 2015 HibernationDevice: RESUME=UUID=06183660-d359-4e05-9f0f-941b61ae65cf IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. MachineType: HP ProLiant DL385 G2 MarkForUpload: True PciMultimedia: ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VGA16 VGA ProcKernelCmdLine: root=UUID=3241700a-e0ca-4d26-8a7f-4fa088b98e75 ro console=tty0 console=ttyS1,115200n8 RelatedPackageVersions: linux-restricted-modules-2.6.32-73-server N/A linux-backports-modules-2.6.32-73-server N/A linux-firmware1.79.18 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux UpgradeStatus: Upgraded to precise on 2015-03-20 (2 days ago) dmi.bios.date: 04/07/2007 dmi.bios.vendor: HP dmi.bios.version: A09 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrA09:bd04/07/2007:svnHP:pnProLiantDL385G2:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL385 G2 dmi.sys.vendor: HP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1435509 Title: cciss: hangs in modprobe, prevents server from booting Status in linux package in Ubuntu: Incomplete Bug description: I've upgraded an Ubuntu 10.04 LTS server to 12.04 LTS. It now fails to boot. More specifically, kernel 3.2.0-77 hangs in the cciss driver during initialization. The hardware is an HP ProLiant DL385 G2. The RAID controller is HP Smart Array P600: lspci -knn -s 06:01 06:01.0 RAID bus controller [0104]: Hewlett-Packard Company Smart Array P600 [103c:3220] Subsystem: Hewlett-Packard Company 3 Gb/s SAS RAID [103c:3225] Kernel driver in use: cciss Kernel modules: cciss I can observe the boot process over serial console (attached: serial-console.log). You can see the kernel messages about cciss being detected, udev messages about modprobe timing out followed by boot process timeouts and a failure to mount the root filesystem. You can also see hung task messages from the kernel (kworker/0:2 and modprobe are both hung inside cciss), and you can see some of my futile attempts to look around in the initramfs. I can boot an older kernel (2.6.32-73-server, left over from Ubuntu 10.04 LTS) just fine. I'm afraid dmesg and other bits of information collected by apport for this bug report will be misleadingly from that older kernel. = WORKAROUND = Add
[Kernel-packages] [Bug 1191915] Re: CVE-2013-1935
** Description changed: A flaw was found in the way KVM (Kernel-based Virtual Machine) initialized a guest's registered pv_eoi (paravirtualized end-of- interrupt) indication flag when entering the guest. An unprivileged guest user could potentially use this flaw to crash the host. + + Break-Fix: ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb + b463a6f744a263fccd7da14db1afdc880371a280 ** Changed in: linux (Ubuntu) Status: New = Invalid ** Changed in: linux (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu) 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/1191915 Title: CVE-2013-1935 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: New Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Invalid Status in linux-lts-backport-oneiric source package in Lucid: Invalid Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Won't Fix Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Quantal: Won't Fix Status in linux-armadaxp source package in Quantal: Won't Fix Status in linux-ec2 source package in Quantal: Invalid Status in linux-fsl-imx51 source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux-lts-raring source package in Quantal: Invalid Status in linux-mvl-dove source package in Quantal: Invalid Status in linux-ti-omap4 source package in Quantal: Won't Fix Status in linux source package in Raring: Won't Fix Status in linux-armadaxp source package in Raring: Invalid Status in linux-ec2 source package in Raring: Invalid Status in linux-fsl-imx51 source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-quantal source package in Raring: Invalid Status in linux-lts-raring source package in Raring: Invalid Status in linux-mvl-dove source package in Raring: Invalid Status in linux-ti-omap4 source package in Raring: Won't Fix Status in linux source package in Saucy: Won't Fix Status in linux-armadaxp source package in Saucy: Invalid Status in linux-ec2 source package in Saucy: Invalid Status in linux-fsl-imx51 source package in Saucy: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux-lts-quantal source package in Saucy: Invalid Status in linux-lts-raring source package in Saucy: Invalid Status in linux-mvl-dove source package in Saucy: Invalid Status in
[Kernel-packages] [Bug 1196796] Re: CVE-2013-2224
** Changed in: linux-ti-omap4 (Ubuntu) Status: New = Invalid ** Description changed: - IP_RETOPTS Buffer Poisoning DoS + A certain Red Hat patch for the Linux kernel 2.6.32 on Red Hat Enterprise + Linux (RHEL) 6 allows local users to cause a denial of service (invalid + free operation and system crash) or possibly gain privileges via a sendmsg + system call with the IP_RETOPTS option, as demonstrated by hemlock.c. + NOTE: this vulnerability exists because of an incorrect fix for + CVE-2012-3552. + + Break-Fix: - f6d8bd051c391c1c0458a30b2a7abcd939329259 ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Invalid ** Changed in: linux (Ubuntu) Status: New = Invalid ** Changed in: linux (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux (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/1196796 Title: CVE-2013-2224 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: New Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Invalid Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Won't Fix Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Quantal: Won't Fix Status in linux-armadaxp source package in Quantal: Won't Fix Status in linux-ec2 source package in Quantal: Invalid Status in linux-fsl-imx51 source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux-lts-raring source package in Quantal: Invalid Status in linux-mvl-dove source package in Quantal: Invalid Status in linux-ti-omap4 source package in Quantal: Won't Fix Status in linux source package in Raring: Won't Fix Status in linux-armadaxp source package in Raring: Invalid Status in linux-ec2 source package in Raring: Invalid Status in linux-fsl-imx51 source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-quantal source package in Raring: Invalid Status in linux-lts-raring source package in Raring: Invalid Status in linux-mvl-dove source package in Raring: Invalid Status in linux-ti-omap4 source package in Raring: Won't Fix Status in linux source package in Saucy: Won't Fix Status in linux-armadaxp source package in Saucy: Invalid Status in linux-ec2 source package in Saucy: Invalid Status in linux-fsl-imx51 source package in Saucy: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-quantal source package in Saucy: Invalid Status in linux-lts-raring source package in Saucy: Invalid Status in linux-mvl-dove source package in Saucy: Invalid Status in linux-ti-omap4 source package in Saucy: Won't Fix Bug description: A certain Red Hat patch for the Linux kernel 2.6.32 on Red Hat Enterprise Linux (RHEL) 6 allows local users to cause a denial of service (invalid free operation and system crash) or possibly gain privileges via a sendmsg system call with the
[Kernel-packages] [Bug 844361] Re: CVE-2011-1576
** Changed in: linux-ti-omap4 (Ubuntu) Status: Incomplete = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-backport-maverick in Ubuntu. https://bugs.launchpad.net/bugs/844361 Title: CVE-2011-1576 Status in linux package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Released Status in linux-ec2 source package in Lucid: Fix Released Status in linux-fsl-imx51 source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Lucid: Fix Released Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Fix Released Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Maverick: Fix Released Status in linux-ec2 source package in Maverick: Invalid Status in linux-fsl-imx51 source package in Maverick: Invalid Status in linux-lts-backport-maverick source package in Maverick: Invalid Status in linux-lts-backport-natty source package in Maverick: Invalid Status in linux-lts-backport-oneiric source package in Maverick: Invalid Status in linux-mvl-dove source package in Maverick: Fix Released Status in linux-ti-omap4 source package in Maverick: Fix Released Status in linux source package in Natty: Fix Released Status in linux-ec2 source package in Natty: Invalid Status in linux-fsl-imx51 source package in Natty: Invalid Status in linux-lts-backport-maverick source package in Natty: Invalid Status in linux-lts-backport-natty source package in Natty: Invalid Status in linux-lts-backport-oneiric source package in Natty: Invalid Status in linux-mvl-dove source package in Natty: Invalid Status in linux-ti-omap4 source package in Natty: Fix Released Status in linux source package in Oneiric: Invalid Status in linux-ec2 source package in Oneiric: Invalid Status in linux-fsl-imx51 source package in Oneiric: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux-mvl-dove source package in Oneiric: Invalid Status in linux-ti-omap4 source package in Oneiric: Won't Fix Status in linux source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Hardy: Invalid Status in linux-ec2 source package in Hardy: Invalid Status in linux-fsl-imx51 source package in Hardy: Invalid Status in linux-lts-backport-maverick source package in Hardy: Invalid Status in linux-lts-backport-natty source package in Hardy: Invalid Status in linux-lts-backport-oneiric source package in Hardy: Invalid Status in linux-mvl-dove source package in Hardy: Invalid Status in linux-ti-omap4 source package in Hardy: Invalid Bug description: The Generic Receive Offload (GRO) implementation in the Linux kernel 2.6.18 on Red Hat Enterprise Linux 5 and 2.6.32 on Red Hat Enterprise Linux 6, as used in Red Hat Enterprise Virtualization (RHEV) Hypervisor and other products, allows remote attackers to cause a denial of service via crafted VLAN packets that are processed by the napi_reuse_skb function, leading to (1) a memory leak or (2) memory corruption, a different vulnerability than CVE-2011-1478. Break-Fix: 5d0d9be8ef456afc6c3fb5f8aad06ef19b704b05 3701e51382a026cba10c60b03efabe534fba4ca4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/844361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1430341] Re: [Ubuntu 15.04] Enable perf to exploit 24x7 hardware counters
comment from launchpad, please ignore
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1430341
Title:
[Ubuntu 15.04] Enable perf to exploit 24x7 hardware counters
Status in linux package in Ubuntu:
Fix Released
Bug description:
== Comment: #0 - Breno Henrique Leitao bren...@br.ibm.com - 2014-11-06
12:52:04 ==
Enable perf tool to exploit POWER 24x7 hardware counters
Parts of the project:
a) Some patches upstream and done
b) Reset targets on remaining features still to be done (jit support, symbol
names)
== Comment: #16 - Breno Henrique Leitao bren...@br.ibm.com - 2015-02-24
08:06:45 ==
Initial patches already accepted by Canonical on 117275. Patchset posted to
community, waiting on
review. (I had posted a version of the patchset in Dec after fixing minor
comments. Waiting to hear back from community )
== Comment: #18 - Sukadev Bhattiprolu s...@us.ibm.com - 2015-02-25 16:18:34
==
There are two separate patch sets, one for the perf tool and other
for the kernel. They are both available in mainline 3.19-rc4.
=== Perf tool patches (4)
Patch 1/4:
http://marc.info/?l=linuxppc-embeddedm=142067974403807w=2
commit 688d4df
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Wed Jan 7 17:13:50 2015 -0800
perf tools: Support parsing parameterized events
Patch 2/4:
http://marc.info/?l=linux-kernelm=142067973603799w=2
commit aaea361
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Wed Jan 7 17:13:51 2015 -0800
perf tools: Extend format_alias() to include event parameters
Patch 3/4:
http://marc.info/?l=linux-kernelm=142067971103796w=2
commit 98a43e0
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Wed Jan 7 17:13:52 2015 -0800
perf Documentation: Add event parameters
Patch 4/4:
http://marc.info/?l=linux-kernelm=142067968803787w=2
commit f9ab9c1
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Wed Jan 7 17:13:53 2015 -0800
perf tools: Document parameterized and symbolic events
=== Kernel patches(7)
Patch 1/7:
http://marc.info/?l=linux-kernelm=142265456708471w=2
commit fd979c0
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:45:57 2015 -0800
perf: provide sysfs_show for struct perf_pmu_events_attr
Patch 2/7:
http://marc.info/?l=linux-kernelm=142265448108443w=2
commit f0405b8
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:45:58 2015 -0800
perf: add PMU_EVENT_ATTR_STRING() helper
Patch 3/7:
http://marc.info/?l=linux-kernelm=142265445208433w=2
commit e08e528
Author: suka...@linux.vnet.ibm.com suka...@linux.vnet.ibm.com
Date: Fri Jan 30 13:45:59 2015 -0800
perf: define EVENT_DEFINE_RANGE_FORMAT_LITE helper
Patch 4/7:
http://marc.info/?l=linux-kernelm=142265452008458w=2
commit 5c5cd7b
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:46:00 2015 -0800
powerpc/perf/hv-24x7: parse catalog and populate sysfs with
events
Patch 5/7:
http://marc.info/?l=linux-kernelm=142265450008450w=2
commit 9e9f601
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:46:01 2015 -0800
powerpc/perf/{hv-gpci, hv-common}: generate requests with
counters annotated
Patch 6/7:
http://marc.info/?l=linux-kernelm=142265448408446w=2
commit 97bf264
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:46:02 2015 -0800
powerpc/perf/hv-gpci: add the remaining gpci requests
Patch 7/7:
http://marc.info/?l=linux-kernelm=142265446008435w=2
commit 5c65670
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:46:03 2015 -0800
powerpc/perf/hv-24x7: Document sysfs event description entries
== Comment: #23 - Sukadev Bhattiprolu s...@us.ibm.com - 2015-02-26 13:22:13
==
Never mind.
'git describe' seems to think they are in 3.19-rcX but they are
not in 3.19.
$ git describe fd979c0
v3.19-rc2-62-gfd979c0
$ git describe aaea361
v3.19-rc4-172-gaaea361
They were merged on Feb 2, so they should be in 4.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1430341/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1312994] Re: CVE-2014-2851
** Changed in: linux (Ubuntu Utopic) Status: Fix Committed = Invalid ** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1312994 Title: CVE-2014-2851 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: Fix Committed Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-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-mako package in Ubuntu: Fix Committed Status in linux-manta package in Ubuntu: Fix Committed Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-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: Won't Fix Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Fix Released Status in linux-lts-saucy source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Won't Fix Status in linux-lts-backport-natty source package in Quantal: Won't Fix Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux 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: Won't Fix Status in linux-lts-backport-natty source package in Trusty: Won't Fix Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Invalid Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New
[Kernel-packages] [Bug 1430341] Comment bridged from LTC Bugzilla
--- Comment From bren...@br.ibm.com 2014-11-06 17:52 EDT---
--- Comment From bren...@br.ibm.com 2015-02-24 13:06 EDT---
--- Comment From s...@us.ibm.com 2015-02-25 21:18 EDT---
--- Comment From s...@us.ibm.com 2015-02-26 18:22 EDT---
Enable perf tool to exploit POWER 24x7 hardware counters
Parts of the project:
a) Some patches upstream and done
b) Reset targets on remaining features still to be done (jit support, symbol
names)
Initial patches already accepted by Canonical on 117275. Patchset posted to
community, waiting on
review. (I had posted a version of the patchset in Dec after fixing minor
comments. Waiting to hear back from community )
There are two separate patch sets, one for the perf tool and other
for the kernel. They are both available in mainline 3.19-rc4.
=== Perf tool patches (4)
Patch 1/4:
http://marc.info/?l=linuxppc-embeddedm=142067974403807w=2
commit 688d4df
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Wed Jan 7 17:13:50 2015 -0800
perf tools: Support parsing parameterized events
Patch 2/4:
http://marc.info/?l=linux-kernelm=142067973603799w=2
commit aaea361
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Wed Jan 7 17:13:51 2015 -0800
perf tools: Extend format_alias() to include event parameters
Patch 3/4:
http://marc.info/?l=linux-kernelm=142067971103796w=2
commit 98a43e0
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Wed Jan 7 17:13:52 2015 -0800
perf Documentation: Add event parameters
Patch 4/4:
http://marc.info/?l=linux-kernelm=142067968803787w=2
commit f9ab9c1
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Wed Jan 7 17:13:53 2015 -0800
perf tools: Document parameterized and symbolic events
=== Kernel patches(7)
Patch 1/7:
http://marc.info/?l=linux-kernelm=142265456708471w=2
commit fd979c0
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:45:57 2015 -0800
perf: provide sysfs_show for struct perf_pmu_events_attr
Patch 2/7:
http://marc.info/?l=linux-kernelm=142265448108443w=2
commit f0405b8
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:45:58 2015 -0800
perf: add PMU_EVENT_ATTR_STRING() helper
Patch 3/7:
http://marc.info/?l=linux-kernelm=142265445208433w=2
commit e08e528
Author: suka...@linux.vnet.ibm.com suka...@linux.vnet.ibm.com
Date: Fri Jan 30 13:45:59 2015 -0800
perf: define EVENT_DEFINE_RANGE_FORMAT_LITE helper
Patch 4/7:
http://marc.info/?l=linux-kernelm=142265452008458w=2
commit 5c5cd7b
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:46:00 2015 -0800
powerpc/perf/hv-24x7: parse catalog and populate sysfs with events
Patch 5/7:
http://marc.info/?l=linux-kernelm=142265450008450w=2
commit 9e9f601
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:46:01 2015 -0800
powerpc/perf/{hv-gpci, hv-common}: generate requests with counters
annotated
Patch 6/7:
http://marc.info/?l=linux-kernelm=142265448408446w=2
commit 97bf264
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:46:02 2015 -0800
powerpc/perf/hv-gpci: add the remaining gpci requests
Patch 7/7:
http://marc.info/?l=linux-kernelm=142265446008435w=2
commit 5c65670
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:46:03 2015 -0800
powerpc/perf/hv-24x7: Document sysfs event description entries
Never mind.
'git describe' seems to think they are in 3.19-rcX but they are
not in 3.19.
$ git describe fd979c0
v3.19-rc2-62-gfd979c0
$ git describe aaea361
v3.19-rc4-172-gaaea361
They were merged on Feb 2, so they should be in 4.0
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi
[Kernel-packages] [Bug 1430341] Comment bridged from LTC Bugzilla
--- Comment From bren...@br.ibm.com 2014-11-06 17:52 EDT---
--- Comment From bren...@br.ibm.com 2015-02-24 13:06 EDT---
--- Comment From s...@us.ibm.com 2015-02-25 21:18 EDT---
--- Comment From s...@us.ibm.com 2015-02-26 18:22 EDT---
Enable perf tool to exploit POWER 24x7 hardware counters
Parts of the project:
a) Some patches upstream and done
b) Reset targets on remaining features still to be done (jit support, symbol
names)
Initial patches already accepted by Canonical on 117275. Patchset posted to
community, waiting on
review. (I had posted a version of the patchset in Dec after fixing minor
comments. Waiting to hear back from community )
There are two separate patch sets, one for the perf tool and other
for the kernel. They are both available in mainline 3.19-rc4.
=== Perf tool patches (4)
Patch 1/4:
http://marc.info/?l=linuxppc-embeddedm=142067974403807w=2
commit 688d4df
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Wed Jan 7 17:13:50 2015 -0800
perf tools: Support parsing parameterized events
Patch 2/4:
http://marc.info/?l=linux-kernelm=142067973603799w=2
commit aaea361
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Wed Jan 7 17:13:51 2015 -0800
perf tools: Extend format_alias() to include event parameters
Patch 3/4:
http://marc.info/?l=linux-kernelm=142067971103796w=2
commit 98a43e0
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Wed Jan 7 17:13:52 2015 -0800
perf Documentation: Add event parameters
Patch 4/4:
http://marc.info/?l=linux-kernelm=142067968803787w=2
commit f9ab9c1
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Wed Jan 7 17:13:53 2015 -0800
perf tools: Document parameterized and symbolic events
=== Kernel patches(7)
Patch 1/7:
http://marc.info/?l=linux-kernelm=142265456708471w=2
commit fd979c0
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:45:57 2015 -0800
perf: provide sysfs_show for struct perf_pmu_events_attr
Patch 2/7:
http://marc.info/?l=linux-kernelm=142265448108443w=2
commit f0405b8
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:45:58 2015 -0800
perf: add PMU_EVENT_ATTR_STRING() helper
Patch 3/7:
http://marc.info/?l=linux-kernelm=142265445208433w=2
commit e08e528
Author: suka...@linux.vnet.ibm.com suka...@linux.vnet.ibm.com
Date: Fri Jan 30 13:45:59 2015 -0800
perf: define EVENT_DEFINE_RANGE_FORMAT_LITE helper
Patch 4/7:
http://marc.info/?l=linux-kernelm=142265452008458w=2
commit 5c5cd7b
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:46:00 2015 -0800
powerpc/perf/hv-24x7: parse catalog and populate sysfs with events
Patch 5/7:
http://marc.info/?l=linux-kernelm=142265450008450w=2
commit 9e9f601
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:46:01 2015 -0800
powerpc/perf/{hv-gpci, hv-common}: generate requests with counters
annotated
Patch 6/7:
http://marc.info/?l=linux-kernelm=142265448408446w=2
commit 97bf264
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:46:02 2015 -0800
powerpc/perf/hv-gpci: add the remaining gpci requests
Patch 7/7:
http://marc.info/?l=linux-kernelm=142265446008435w=2
commit 5c65670
Author: Cody P Schafer c...@linux.vnet.ibm.com
Date: Fri Jan 30 13:46:03 2015 -0800
powerpc/perf/hv-24x7: Document sysfs event description entries
Never mind.
'git describe' seems to think they are in 3.19-rcX but they are
not in 3.19.
$ git describe fd979c0
v3.19-rc2-62-gfd979c0
$ git describe aaea361
v3.19-rc4-172-gaaea361
They were merged on Feb 2, so they should be in 4.0
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi
[Kernel-packages] [Bug 1189824] Re: CVE-2011-2693
** Changed in: linux (Ubuntu) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu) 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/1189824 Title: CVE-2011-2693 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: New Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: New Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Invalid Status in linux-lts-backport-oneiric source package in Lucid: Invalid Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Won't Fix Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Quantal: Won't Fix Status in linux-armadaxp source package in Quantal: Won't Fix Status in linux-ec2 source package in Quantal: Invalid Status in linux-fsl-imx51 source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux-lts-raring source package in Quantal: Invalid Status in linux-mvl-dove source package in Quantal: Invalid Status in linux-ti-omap4 source package in Quantal: Won't Fix Status in linux source package in Raring: Won't Fix Status in linux-armadaxp source package in Raring: Invalid Status in linux-ec2 source package in Raring: Invalid Status in linux-fsl-imx51 source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-quantal source package in Raring: Invalid Status in linux-lts-raring source package in Raring: Invalid Status in linux-mvl-dove source package in Raring: Invalid Status in linux-ti-omap4 source package in Raring: Won't Fix Status in linux source package in Saucy: Won't Fix Status in linux-armadaxp source package in Saucy: Invalid Status in linux-ec2 source package in Saucy: Invalid Status in linux-fsl-imx51 source package in Saucy: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux-lts-quantal source package in Saucy: Invalid Status in linux-lts-raring source package in Saucy: Invalid Status in linux-mvl-dove source package in Saucy: Invalid Status in linux-ti-omap4 source package in Saucy: Won't Fix Bug description: The perf subsystem in the kernel package 2.6.32-122.el6.x86_64 in Red Hat Enterprise Linux (RHEL) 6 does not properly handle NMIs, which might allow local users to cause a denial of service (excessive log messages) via unspecified vectors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189824/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count
Jordan, which kernel version are you using to make your observations (thanks a lot for those, btw). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become free. Usage count Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Bug description: I currently running trusty latest patches and i get on these hardware and software: Ubuntu 3.13.0-43.72-generic 3.13.11.11 processor : 7 vendor_id : GenuineIntel cpu family: 6 model : 77 model name: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz stepping : 8 microcode : 0x11d cpu MHz : 2400.000 cache size: 1024 KB physical id : 0 siblings : 8 core id : 7 cpu cores : 8 apicid: 14 initial apicid: 14 fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 4799.48 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: somehow reproducable the subjected error, and lxc is working still but not more managable until a reboot. managable means every command hangs. I saw there are alot of bugs but they seams to relate to older version and are closed, so i decided to file a new one? I run alot of machine with trusty an lxc containers but only these kind of machines produces these errors, all other don't show these odd behavior. thx in advance meno To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1155018] Re: CVE-2012-6138
** Changed in: linux (Ubuntu) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu) Status: New = Invalid ** Description changed: - Linux kernel: various info leaks + ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2012-6536, + CVE-2012-6537, CVE-2012-6538, CVE-2012-6539, CVE-2012-6540, CVE-2012-6541, + CVE-2012-6542, CVE-2012-6543, CVE-2012-6544, CVE-2012-6545, CVE-2012-6546, + CVE-2012-6547, CVE-2012-6548, CVE-2012-6549. Reason: This candidate is a + duplicate of CVE-2012-6536, CVE-2012-6537, CVE-2012-6538, CVE-2012-6539, + CVE-2012-6540, CVE-2012-6541, CVE-2012-6542, CVE-2012-6543, CVE-2012-6544, + CVE-2012-6545, CVE-2012-6546, CVE-2012-6547, CVE-2012-6548, and + CVE-2012-6549. Notes: All CVE users should reference one or more of + CVE-2012-6536, CVE-2012-6537, CVE-2012-6538, CVE-2012-6539, CVE-2012-6540, + CVE-2012-6541, CVE-2012-6542, CVE-2012-6543, CVE-2012-6544, CVE-2012-6545, + CVE-2012-6546, CVE-2012-6547, CVE-2012-6548, and CVE-2012-6549 instead of + this candidate. All references and descriptions in this candidate have + been removed to prevent accidental usage. ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Lucid) 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/1155018 Title: CVE-2012-6138 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Invalid Status in linux-lts-backport-oneiric source package in Lucid: Won't Fix Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Oneiric: Invalid Status in linux-armadaxp source package in Oneiric: Invalid Status in linux-ec2 source package in Oneiric: Invalid Status in linux-fsl-imx51 source package in Oneiric: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux-lts-quantal source package in Oneiric: Invalid Status in linux-mvl-dove source package in Oneiric: Invalid Status in linux-ti-omap4 source package in Oneiric: Won't Fix Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Quantal: Won't Fix Status in linux-armadaxp source package in Quantal: Won't Fix Status in linux-ec2 source package in Quantal: Invalid Status in linux-fsl-imx51 source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux-mvl-dove source package in Quantal: Invalid Status in linux-ti-omap4 source package in Quantal: Won't Fix Status in linux source
[Kernel-packages] [Bug 1435400] rainier (amd64) - tests ran: 268, failed: 4
tests ran: 268, failed: 4; http://kernel.ubuntu.com/testing/rainier__3.16.0-34.45__2015-03-25_04-37-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/1435400 Title: linux: 3.16.0-34.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress 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 Utopic: New Bug description: This bug is for tracking the 3.16.0-34.45 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 15:55 UTC kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 24. March 2015 22:32 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 25. March 2015 00:00 UTC kernel-stable-Verification-testing-start:Wednesday, 25. March 2015 00:00 UTC kernel-stable-Certification-testing-start:Wednesday, 25. March 2015 00:00 UTC kernel-stable-Security-signoff-start:Wednesday, 25. March 2015 00:00 UTC kernel-stable-Regression-testing-start:Wednesday, 25. March 2015 00:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1435400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435728] Re: [HP Pavilion Notebook - 13-b208tu] Broadcom BCM43142 wireless fails to resume from suspend
Stuart Bishop, just to clarify, after resuming from suspend, does the following terminal command provide a WORKAROUND: rmmod bcmwl modprobe bcmwl ** Description changed: The wifi connection on the HP 13-b208tu laptop (Broadcom BCM4365) fails - during suspend or resume. + after computer resumes from suspend. This may be related to Bug 1432659. Also, per Bug 1434136 this laptop is running the latest version of the bios that boots Linux (F.24). Mar 23 22:55:48 aargh kernel: [ 3216.807039] PM: Syncing filesystems ... done. Mar 23 22:55:48 aargh kernel: [ 3216.822610] PM: Preparing system for mem sleep Mar 23 22:55:48 aargh kernel: [ 3216.822812] Freezing user space processes ... (elapsed 0.001 seconds) done. Mar 23 22:55:48 aargh kernel: [ 3216.824475] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Mar 23 22:55:48 aargh kernel: [ 3216.825619] PM: Entering mem sleep Mar 23 22:55:48 aargh kernel: [ 3216.825633] Suspending console(s) (use no_console_suspend to debug) Mar 23 22:55:48 aargh kernel: [ 3216.826983] sd 0:0:0:0: [sda] Synchronizing SCSI cache Mar 23 22:55:48 aargh kernel: [ 3216.828497] cfg80211: Calling CRDA to update world regulatory domain Mar 23 22:55:48 aargh kernel: [ 3216.835195] sd 0:0:0:0: [sda] Stopping disk Mar 23 22:55:48 aargh kernel: [ 3216.886782] i8042 aux 00:03: System wakeup disabled by ACPI Mar 23 22:55:48 aargh kernel: [ 3216.886805] i8042 kbd 00:02: System wakeup enabled by ACPI Mar 23 22:55:48 aargh kernel: [ 3217.893531] [drm:stop_ring [i915]] *ERROR* render ring : timed out trying to stop ring Mar 23 22:55:48 aargh kernel: [ 3217.901564] PM: suspend of devices complete after 1074.780 msecs Mar 23 22:55:48 aargh kernel: [ 3217.941598] PM: late suspend of devices complete after 39.977 msecs Mar 23 22:55:48 aargh kernel: [ 3217.942146] r8169 :04:00.0: System wakeup enabled by ACPI Mar 23 22:55:48 aargh kernel: [ 3217.942187] xhci_hcd :00:14.0: System wakeup enabled by ACPI Mar 23 22:55:48 aargh kernel: [ 3217.957869] PM: noirq suspend of devices complete after 16.253 msecs Mar 23 22:55:48 aargh kernel: [ 3217.958141] ACPI: Preparing to enter system sleep state S3 Mar 23 22:55:48 aargh kernel: [ 3218.025580] PM: Saving platform NVS memory Mar 23 22:55:48 aargh kernel: [ 3218.025586] Disabling non-boot CPUs ... Mar 23 22:55:48 aargh kernel: [ 3218.025609] intel_pstate CPU 1 exiting Mar 23 22:55:48 aargh kernel: [ 3218.025800] Broke affinity for irq 18 Mar 23 22:55:48 aargh kernel: [ 3218.026820] kvm: disabling virtualization on CPU1 Mar 23 22:55:48 aargh kernel: [ 3218.026825] smpboot: CPU 1 is now offline Mar 23 22:55:48 aargh kernel: [ 3218.027186] intel_pstate CPU 2 exiting Mar 23 22:55:48 aargh kernel: [ 3218.028368] kvm: disabling virtualization on CPU2 Mar 23 22:55:48 aargh kernel: [ 3218.028376] smpboot: CPU 2 is now offline Mar 23 22:55:48 aargh kernel: [ 3218.028681] intel_pstate CPU 3 exiting Mar 23 22:55:48 aargh kernel: [ 3218.028782] Broke affinity for irq 42 Mar 23 22:55:48 aargh kernel: [ 3218.029796] kvm: disabling virtualization on CPU3 Mar 23 22:55:48 aargh kernel: [ 3218.029808] smpboot: CPU 3 is now offline Mar 23 22:55:48 aargh kernel: [ 3218.032593] ACPI: Low-level resume complete Mar 23 22:55:48 aargh kernel: [ 3218.032659] PM: Restoring platform NVS memory Mar 23 22:55:48 aargh kernel: [ 3218.033062] Enabling non-boot CPUs ... Mar 23 22:55:48 aargh kernel: [ 3218.033105] x86: Booting SMP configuration: Mar 23 22:55:48 aargh kernel: [ 3218.033106] smpboot: Booting Node 0 Processor 1 APIC 0x2 Mar 23 22:55:48 aargh kernel: [ 3218.045557] kvm: enabling virtualization on CPU1 Mar 23 22:55:48 aargh kernel: [ 3218.047928] CPU1 is up Mar 23 22:55:48 aargh kernel: [ 3218.047959] smpboot: Booting Node 0 Processor 2 APIC 0x1 Mar 23 22:55:48 aargh kernel: [ 3218.060017] kvm: enabling virtualization on CPU2 Mar 23 22:55:48 aargh kernel: [ 3218.062313] CPU2 is up Mar 23 22:55:48 aargh kernel: [ 3218.062330] smpboot: Booting Node 0 Processor 3 APIC 0x3 Mar 23 22:55:48 aargh kernel: [ 3218.074403] kvm: enabling virtualization on CPU3 Mar 23 22:55:48 aargh kernel: [ 3218.076717] CPU3 is up Mar 23 22:55:48 aargh kernel: [ 3218.080064] ACPI: Waking up from system sleep state S3 Mar 23 22:55:48 aargh kernel: [ 3218.228368] xhci_hcd :00:14.0: System wakeup disabled by ACPI Mar 23 22:55:48 aargh kernel: [ 3218.244618] PM: noirq resume of devices complete after 16.316 msecs Mar 23 22:55:48 aargh kernel: [ 3218.268492] PM: early resume of devices complete after 23.814 msecs Mar 23 22:55:48 aargh kernel: [ 3218.268835] r8169 :04:00.0: System wakeup disabled by ACPI Mar 23 22:55:48 aargh kernel: [ 3218.270010] sd 0:0:0:0: [sda] Starting disk Mar 23 22:55:48 aargh kernel: [ 3218.313734] rtc_cmos 00:01: System wakeup disabled by ACPI Mar 23 22:55:48 aargh kernel: [ 3218.313750] i8042 kbd 00:02: System
[Kernel-packages] [Bug 1432659] Re: HP Pavilion 13-b208tu w/ Broadcom BCM43142 Wifi unstable, panics
** Description changed: This new laptop's wireless connection (HP Pavilion 13-b208tu, Broadcom - BCM43142) is disconnecting every few minutes. This corresponds to panics - and tracebacks in the kernel log. + BCM43142) is disconnecting every few minutes after coming up from a + restart or shutdown. This corresponds to panics and tracebacks in the + kernel log. The laptop was freshly installed with Ubuntu 14.10 (Utopic), and disconnections were seen. I then upgraded it to Ubuntu 15.04 (Vivid developement release), and am still experiencing the problem. The Broadcom proprietary driver is being used, and seems to be the only one available for this device. Mar 16 20:38:38 aargh kernel: [ 557.285585] [ cut here ] Mar 16 20:38:38 aargh kernel: [ 557.285646] WARNING: CPU: 0 PID: 523 at /build/buildd/linux-3.19.0/net/wireless/sme.c:800 cfg80211_roamed+0x91/0xa0 [cfg80211]() Mar 16 20:38:38 aargh kernel: [ 557.285652] Modules linked in: rfcomm bnep xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nls_iso8859_1 hp_wmi sparse_keymap snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi wl(POE) snd_hda_intel intel_rapl iosf_mbi x86_pkg_temp_thermal snd_hda_controller intel_powerclamp coretemp snd_hda_codec kvm_intel snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event joydev snd_rawmidi rtsx_pci_ms serio_raw snd_seq cfg80211 uvcvideo lpc_ich snd_seq_device videobuf2_vmalloc snd_timer videobuf2_memops videobuf2_core btusb v4l2_common bluetooth videodev media memstick mei_me mei shpchp snd soundcore 8250_fintek hp_accel hp_wireless lis3lv02d input_polldev acpi_pad mac_hid parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i915 psmouse ahci libahci r8169 i2c_algo_bit mii rtsx_pci drm_kms_helper drm wmi video Mar 16 20:38:38 aargh kernel: [ 557.285789] CPU: 0 PID: 523 Comm: wl_event_handle Tainted: PW OE 3.19.0-9-generic #9-Ubuntu Mar 16 20:38:38 aargh kernel: [ 557.285793] Hardware name: Hewlett-Packard HP Pavilion 13 Notebook PC /2340, BIOS F.23 11/13/2014 Mar 16 20:38:38 aargh kernel: [ 557.285798] c0709a78 880250fe3da8 817c09b5 0007 Mar 16 20:38:38 aargh kernel: [ 557.285804] 880250fe3de8 8107595a 88008ee99478 Mar 16 20:38:38 aargh kernel: [ 557.285809] 880250909000 88023bfc6a80 0099 88023bfc6900 Mar 16 20:38:38 aargh kernel: [ 557.285816] Call Trace: Mar 16 20:38:38 aargh kernel: [ 557.285831] [817c09b5] dump_stack+0x45/0x57 Mar 16 20:38:38 aargh kernel: [ 557.285841] [8107595a] warn_slowpath_common+0x8a/0xc0 Mar 16 20:38:38 aargh kernel: [ 557.285846] [81075a4a] warn_slowpath_null+0x1a/0x20 Mar 16 20:38:38 aargh kernel: [ 557.285873] [c06e5a81] cfg80211_roamed+0x91/0xa0 [cfg80211] Mar 16 20:38:38 aargh kernel: [ 557.285969] [c0ad59fb] wl_notify_roaming_status+0xcb/0x150 [wl] Mar 16 20:38:38 aargh kernel: [ 557.286044] [c0ad275a] wl_event_handler+0x6a/0x230 [wl] Mar 16 20:38:38 aargh kernel: [ 557.286122] [c0ad26f0] ? wl_free_wdev.isra.23+0x80/0x80 [wl] Mar 16 20:38:38 aargh kernel: [ 557.286144] [81094679] kthread+0xc9/0xe0 Mar 16 20:38:38 aargh kernel: [ 557.286153] [810945b0] ? kthread_create_on_node+0x1c0/0x1c0 Mar 16 20:38:38 aargh kernel: [ 557.286161] [817c7a3c] ret_from_fork+0x7c/0xb0 Mar 16 20:38:38 aargh kernel: [ 557.286169] [810945b0] ? kthread_create_on_node+0x1c0/0x1c0 Mar 16 20:38:38 aargh kernel: [ 557.286173] ---[ end trace 3fbf2d3851265ca6 ]--- Mar 16 20:38:44 aargh kernel: [ 563.512221] cfg80211: Calling CRDA to update world regulatory domain Mar 16 20:38:44 aargh kernel: [ 563.514217] cfg80211: World regulatory domain updated: Mar 16 20:38:44 aargh kernel: [ 563.514220] cfg80211: DFS Master region: unset Mar 16 20:38:44 aargh kernel: [ 563.514221] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Mar 16 20:38:44 aargh kernel: [ 563.514224] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Mar 16 20:38:44 aargh kernel: [ 563.514225] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Mar 16 20:38:44 aargh kernel: [ 563.514226] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm), (N/A) Mar 16 20:38:44 aargh kernel: [ 563.514227] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Mar 16 20:38:44 aargh kernel: [ 563.514229] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz),
[Kernel-packages] [Bug 1436327] [NEW] [Asus X751MD] touchpad
Public bug reported: doesn't work at all. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-33-generic 3.16.0-33.44~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 25 14:05:32 2015 InstallationDate: Installed on 2015-03-22 (2 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1436327 Title: [Asus X751MD] touchpad Status in linux-lts-utopic package in Ubuntu: New Bug description: doesn't work at all. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-33-generic 3.16.0-33.44~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 25 14:05:32 2015 InstallationDate: Installed on 2015-03-22 (2 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1436327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436319] Re: Unable to increase nr_requests...
apport information ** Tags added: apport-collected ec2-images trusty ** Description changed: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Mar 24 06:50 seq + crw-rw 1 root audio 116, 33 Mar 24 06:50 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.7 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 14.04 + Ec2AMI: ami-00a3 + Ec2AMIManifest: FIXME + Ec2AvailabilityZone: nova + Ec2InstanceType: ra.intel.ssd.xl4 + Ec2Kernel: aki-0002 + Ec2Ramdisk: ari-0002 + HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba + InstallationDate: Installed on 2014-04-16 (343 days ago) + InstallationMedia: + + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: OpenStack Foundation OpenStack Nova + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + SHELL=/bin/bash + TERM=vt100 + PATH=(custom, no user) + LANG=en_US.UTF-8 + XDG_RUNTIME_DIR=set + ProcFB: 0 cirrusdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 + ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.16.0-33-generic N/A + linux-backports-modules-3.16.0-33-generic N/A + linux-firmware 1.127.11 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty ec2-images + Uname: Linux 3.16.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 01/01/2011 + dmi.bios.vendor: Bochs + dmi.bios.version: Bochs + dmi.chassis.type: 1 + dmi.chassis.vendor: Bochs + dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.2:cvnBochs:ct1:cvr: + dmi.product.name: OpenStack Nova + dmi.product.version: 2013.2.2 + dmi.sys.vendor: OpenStack Foundation ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1436319/+attachment/4355572/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests... Status in linux package in Ubuntu: Confirmed Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 24 06:50 seq crw-rw 1 root audio 116, 33 Mar 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00a3 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ra.intel.ssd.xl4 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba InstallationDate: Installed on 2014-04-16 (343 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=vt100 PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as
[Kernel-packages] [Bug 1434863] Re: Fehlerwert 2
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1434863 Title: Fehlerwert 2 Status in linux package in Ubuntu: Confirmed Bug description: Alle Installationen enden mit dem Fehler: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück z.B.: E: linux-image-2.6.32-72-generic: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück E: linux-image-2.6.32-73-generic: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück E: linux-image-generic: Abhängigkeitsprobleme - lasse es unkonfiguriert ProblemType: Package DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-73-generic 2.6.32-73.141 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-72.139-generic 2.6.32.63+drm33.26 Uname: Linux 2.6.32-72-generic i686 NonfreeKernelModules: tusbd AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AptOrdering: linux-image-2.6.32-73-generic: Install linux-image-generic: Install linux-image-2.6.32-72-generic: Configure linux-image-2.6.32-73-generic: Configure linux-image-generic: Configure Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: woi2645 F pulseaudio CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd810 irq 16' Mixer name : 'C-Media CMI9880' Components : 'HDA:434d4980,70911462,00090402' Controls : 22 Simple ctrls : 13 Card1.Amixer.info: Card hw:1 'SAA7134'/'saa7134[0] at 0xd800 irq 17' Mixer name : 'SAA7134 Mixer' Components : '' Controls : 6 Simple ctrls : 3 Card2.Amixer.info: Card hw:2 'SAA7134_1'/'saa7134[1] at 0xd8002000 irq 20' Mixer name : 'SAA7134 Mixer' Components : '' Controls : 6 Simple ctrls : 3 Date: Sat Mar 21 18:48:35 2015 DpkgTerminalLog: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück HibernationDevice: RESUME=UUID=42b7d956-1957-4a05-87a4-146e32824bd8 MachineType: MEDIONPC MS-7091 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-72-generic root=UUID=fff2c08b-8ec8-4d95-9e5a-4d109cc25e8a ro quiet splash RelatedPackageVersions: linux-firmware 1.34.14 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: usbip vhci_hcd usbip_common_mod Title: [STAGING] dmi.bios.date: 01/27/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7091 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/27/2005:svnMEDIONPC:pnMS-7091:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7091:rvr:cvn:ct3:cvr: dmi.product.name: MS-7091 dmi.sys.vendor: MEDIONPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436319] [NEW] Unable to increase nr_requests...
Public bug reported: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests... Status in linux package in Ubuntu: New Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1432659] Re: HP Pavilion 13-b208tu w/ Broadcom BCM43142 Wifi unstable, panics
No problems during normal operation for a few days. The suspend/resume issue is a separate bug. Flagging this one INVALID. ** Changed in: bcmwl (Ubuntu) Status: Incomplete = Invalid -- 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/1432659 Title: HP Pavilion 13-b208tu w/ Broadcom BCM43142 Wifi unstable, panics Status in bcmwl package in Ubuntu: Invalid Bug description: This new laptop's wireless connection (HP Pavilion 13-b208tu, Broadcom BCM43142) is disconnecting every few minutes after coming up from a restart or shutdown. This corresponds to panics and tracebacks in the kernel log. The laptop was freshly installed with Ubuntu 14.10 (Utopic), and disconnections were seen. I then upgraded it to Ubuntu 15.04 (Vivid developement release), and am still experiencing the problem. The Broadcom proprietary driver is being used, and seems to be the only one available for this device. Mar 16 20:38:38 aargh kernel: [ 557.285585] [ cut here ] Mar 16 20:38:38 aargh kernel: [ 557.285646] WARNING: CPU: 0 PID: 523 at /build/buildd/linux-3.19.0/net/wireless/sme.c:800 cfg80211_roamed+0x91/0xa0 [cfg80211]() Mar 16 20:38:38 aargh kernel: [ 557.285652] Modules linked in: rfcomm bnep xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nls_iso8859_1 hp_wmi sparse_keymap snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi wl(POE) snd_hda_intel intel_rapl iosf_mbi x86_pkg_temp_thermal snd_hda_controller intel_powerclamp coretemp snd_hda_codec kvm_intel snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event joydev snd_rawmidi rtsx_pci_ms serio_raw snd_seq cfg80211 uvcvideo lpc_ich snd_seq_device videobuf2_vmalloc snd_timer videobuf2_memops videobuf2_core btusb v4l2_common bluetooth videodev media memstick mei_me mei shpchp snd soundcore 8250_fintek hp_accel hp_wireless lis3lv02d input_polldev acpi_pad mac_hid parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i915 psmouse ahci libahci r8169 i2c_algo_bit mii rtsx_pci drm_kms_helper drm wmi video Mar 16 20:38:38 aargh kernel: [ 557.285789] CPU: 0 PID: 523 Comm: wl_event_handle Tainted: PW OE 3.19.0-9-generic #9-Ubuntu Mar 16 20:38:38 aargh kernel: [ 557.285793] Hardware name: Hewlett-Packard HP Pavilion 13 Notebook PC /2340, BIOS F.23 11/13/2014 Mar 16 20:38:38 aargh kernel: [ 557.285798] c0709a78 880250fe3da8 817c09b5 0007 Mar 16 20:38:38 aargh kernel: [ 557.285804] 880250fe3de8 8107595a 88008ee99478 Mar 16 20:38:38 aargh kernel: [ 557.285809] 880250909000 88023bfc6a80 0099 88023bfc6900 Mar 16 20:38:38 aargh kernel: [ 557.285816] Call Trace: Mar 16 20:38:38 aargh kernel: [ 557.285831] [817c09b5] dump_stack+0x45/0x57 Mar 16 20:38:38 aargh kernel: [ 557.285841] [8107595a] warn_slowpath_common+0x8a/0xc0 Mar 16 20:38:38 aargh kernel: [ 557.285846] [81075a4a] warn_slowpath_null+0x1a/0x20 Mar 16 20:38:38 aargh kernel: [ 557.285873] [c06e5a81] cfg80211_roamed+0x91/0xa0 [cfg80211] Mar 16 20:38:38 aargh kernel: [ 557.285969] [c0ad59fb] wl_notify_roaming_status+0xcb/0x150 [wl] Mar 16 20:38:38 aargh kernel: [ 557.286044] [c0ad275a] wl_event_handler+0x6a/0x230 [wl] Mar 16 20:38:38 aargh kernel: [ 557.286122] [c0ad26f0] ? wl_free_wdev.isra.23+0x80/0x80 [wl] Mar 16 20:38:38 aargh kernel: [ 557.286144] [81094679] kthread+0xc9/0xe0 Mar 16 20:38:38 aargh kernel: [ 557.286153] [810945b0] ? kthread_create_on_node+0x1c0/0x1c0 Mar 16 20:38:38 aargh kernel: [ 557.286161] [817c7a3c] ret_from_fork+0x7c/0xb0 Mar 16 20:38:38 aargh kernel: [ 557.286169] [810945b0] ? kthread_create_on_node+0x1c0/0x1c0 Mar 16 20:38:38 aargh kernel: [ 557.286173] ---[ end trace 3fbf2d3851265ca6 ]--- Mar 16 20:38:44 aargh kernel: [ 563.512221] cfg80211: Calling CRDA to update world regulatory domain Mar 16 20:38:44 aargh kernel: [ 563.514217] cfg80211: World regulatory domain updated: Mar 16 20:38:44 aargh kernel: [ 563.514220] cfg80211: DFS Master region: unset Mar 16 20:38:44 aargh kernel: [ 563.514221] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Mar 16 20:38:44 aargh kernel: [ 563.514224] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Mar 16 20:38:44 aargh kernel: [ 563.514225] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Mar
[Kernel-packages] [Bug 1436319] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1436319/+attachment/4355575/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests... Status in linux package in Ubuntu: Confirmed Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 24 06:50 seq crw-rw 1 root audio 116, 33 Mar 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00a3 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ra.intel.ssd.xl4 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba InstallationDate: Installed on 2014-04-16 (343 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=vt100 PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435728] Re: [HP Pavilion Notebook - 13-b208tu] Broadcom BCM43142 wireless fails to resume from suspend
Mar 25 20:33:39 aargh kernel: [ 121.980963] PM: resume of devices complete after 754.239 msecs Mar 25 20:33:39 aargh kernel: [ 121.981208] [ cut here ] Mar 25 20:33:39 aargh kernel: [ 121.981216] WARNING: CPU: 2 PID: 457 at /build/buildd/linux-3.19.0/drivers/base/firmware_class.c:1126 _request_firmware+0x72e/0xbd0() Mar 25 20:33:39 aargh kernel: [ 121.981268] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables binfmt_misc rfcomm bnep nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic hp_wmi snd_hda_intel snd_hda_controller snd_hda_codec sparse_keymap snd_hwdep snd_pcm snd_seq_midi intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp snd_seq_midi_event kvm_intel snd_rawmidi kvm wl(POE) btusb joydev uvcvideo videobuf2_vmalloc serio_raw bluetooth snd_seq lpc_ich snd_seq_device videobuf2_memops snd_timer videobuf2_core v4l2_common videodev media cfg80211 rtsx_pci_ms memstick snd mei_me mei shpchp soundcore hp_accel lis3lv02d 8250_fintek input_polldev hp_wireless acpi_pad mac_hid parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper i915 cryptd psmouse i2c_algo_bit ahci drm_kms_helper libahci r8169 drm rtsx_pci mii wmi video Mar 25 20:33:39 aargh kernel: [ 121.981298] CPU: 2 PID: 457 Comm: kworker/u17:2 Tainted: P OE 3.19.0-9-generic #9-Ubuntu Mar 25 20:33:39 aargh kernel: [ 121.981300] Hardware name: Hewlett-Packard HP Pavilion 13 Notebook PC /2340, BIOS F.24 11/28/2014 Mar 25 20:33:39 aargh kernel: [ 121.981319] Workqueue: hci0 hci_power_on [bluetooth] Mar 25 20:33:39 aargh kernel: [ 121.981323] 81b0fa68 88008acfbb78 817c09b5 81c54d78 Mar 25 20:33:39 aargh kernel: [ 121.981326] 88008acfbbb8 8107595a 81517f6a Mar 25 20:33:39 aargh kernel: [ 121.981329] 88008acfbcd0 88023252ccc0 88008a86bb40 fff5 Mar 25 20:33:39 aargh kernel: [ 121.981330] Call Trace: Mar 25 20:33:39 aargh kernel: [ 121.981336] [817c09b5] dump_stack+0x45/0x57 Mar 25 20:33:39 aargh kernel: [ 121.981340] [8107595a] warn_slowpath_common+0x8a/0xc0 Mar 25 20:33:39 aargh kernel: [ 121.981345] [81517f6a] ? _request_firmware+0x5a/0xbd0 Mar 25 20:33:39 aargh kernel: [ 121.981347] [81075a4a] warn_slowpath_null+0x1a/0x20 Mar 25 20:33:39 aargh kernel: [ 121.981351] [8151863e] _request_firmware+0x72e/0xbd0 Mar 25 20:33:39 aargh kernel: [ 121.981355] [81518b15] request_firmware+0x35/0x50 Mar 25 20:33:39 aargh kernel: [ 121.981362] [c08ba869] btusb_setup_bcm_patchram+0x89/0x570 [btusb] Mar 25 20:33:39 aargh kernel: [ 121.981365] [8150f7e6] ? rpm_idle+0xd6/0x230 Mar 25 20:33:39 aargh kernel: [ 121.981382] [c082c561] hci_dev_do_open+0xe1/0xa90 [bluetooth] Mar 25 20:33:39 aargh kernel: [ 121.981386] [810135e0] ? __switch_to+0x150/0x5f0 Mar 25 20:33:39 aargh kernel: [ 121.981401] [c082d6f0] hci_power_on+0x40/0x200 [bluetooth] Mar 25 20:33:39 aargh kernel: [ 121.981405] [8108eb48] process_one_work+0x158/0x430 Mar 25 20:33:39 aargh kernel: [ 121.981408] [8108f5db] worker_thread+0x5b/0x530 Mar 25 20:33:39 aargh kernel: [ 121.981411] [8108f580] ? rescuer_thread+0x3a0/0x3a0 Mar 25 20:33:39 aargh kernel: [ 121.981414] [81094679] kthread+0xc9/0xe0 Mar 25 20:33:39 aargh kernel: [ 121.981419] [810945b0] ? kthread_create_on_node+0x1c0/0x1c0 Mar 25 20:33:39 aargh kernel: [ 121.981427] [817c7a3c] ret_from_fork+0x7c/0xb0 Mar 25 20:33:39 aargh kernel: [ 121.981432] [810945b0] ? kthread_create_on_node+0x1c0/0x1c0 Mar 25 20:33:39 aargh kernel: [ 121.981435] ---[ end trace e2b7bcbcd4bd79f4 ]--- Mar 25 20:33:39 aargh kernel: [ 121.981439] bluetooth hci0: firmware: brcm/BCM43142A0-0a5c-216c.hcd will not be loaded Mar 25 20:33:39 aargh kernel: [ 121.981443] Bluetooth: hci0: BCM: patch brcm/BCM43142A0-0a5c-216c.hcd not found Mar 25 20:33:39 aargh kernel: [ 121.981522] PM: Finishing wakeup. Mar 25 20:33:40 aargh kernel: [ 121.981524] Restarting tasks ... done. Mar 25 20:33:40 aargh kernel: [ 122.018506] cfg80211: World regulatory domain updated: Mar 25 20:33:40 aargh kernel: [ 122.018512] cfg80211: DFS Master region: unset Mar 25 20:33:40 aargh kernel: [ 122.018514] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Mar 25 20:33:40 aargh kernel: [ 122.018519] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Mar 25 20:33:40 aargh kernel: [ 122.018524] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz),
[Kernel-packages] [Bug 1436319] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1436319/+attachment/4355580/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests... Status in linux package in Ubuntu: Confirmed Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 24 06:50 seq crw-rw 1 root audio 116, 33 Mar 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00a3 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ra.intel.ssd.xl4 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba InstallationDate: Installed on 2014-04-16 (343 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=vt100 PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436319] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1436319/+attachment/4355578/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests... Status in linux package in Ubuntu: Confirmed Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 24 06:50 seq crw-rw 1 root audio 116, 33 Mar 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00a3 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ra.intel.ssd.xl4 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba InstallationDate: Installed on 2014-04-16 (343 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=vt100 PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435728] Re: [HP Pavilion Notebook - 13-b208tu] Broadcom BCM43142 wireless fails to resume from suspend
Looking a little closer, the 'wl' module looked promising. 'rmmod wl modprobe wl' does get everything back on its feet after the resume failure. -- 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/1435728 Title: [HP Pavilion Notebook - 13-b208tu] Broadcom BCM43142 wireless fails to resume from suspend Status in bcmwl package in Ubuntu: Incomplete Bug description: The wifi connection on the HP 13-b208tu laptop (Broadcom BCM4365) fails after computer resumes from suspend. This may be related to Bug 1432659. Also, per Bug 1434136 this laptop is running the latest version of the bios that boots Linux (F.24). Mar 23 22:55:48 aargh kernel: [ 3216.807039] PM: Syncing filesystems ... done. Mar 23 22:55:48 aargh kernel: [ 3216.822610] PM: Preparing system for mem sleep Mar 23 22:55:48 aargh kernel: [ 3216.822812] Freezing user space processes ... (elapsed 0.001 seconds) done. Mar 23 22:55:48 aargh kernel: [ 3216.824475] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Mar 23 22:55:48 aargh kernel: [ 3216.825619] PM: Entering mem sleep Mar 23 22:55:48 aargh kernel: [ 3216.825633] Suspending console(s) (use no_console_suspend to debug) Mar 23 22:55:48 aargh kernel: [ 3216.826983] sd 0:0:0:0: [sda] Synchronizing SCSI cache Mar 23 22:55:48 aargh kernel: [ 3216.828497] cfg80211: Calling CRDA to update world regulatory domain Mar 23 22:55:48 aargh kernel: [ 3216.835195] sd 0:0:0:0: [sda] Stopping disk Mar 23 22:55:48 aargh kernel: [ 3216.886782] i8042 aux 00:03: System wakeup disabled by ACPI Mar 23 22:55:48 aargh kernel: [ 3216.886805] i8042 kbd 00:02: System wakeup enabled by ACPI Mar 23 22:55:48 aargh kernel: [ 3217.893531] [drm:stop_ring [i915]] *ERROR* render ring : timed out trying to stop ring Mar 23 22:55:48 aargh kernel: [ 3217.901564] PM: suspend of devices complete after 1074.780 msecs Mar 23 22:55:48 aargh kernel: [ 3217.941598] PM: late suspend of devices complete after 39.977 msecs Mar 23 22:55:48 aargh kernel: [ 3217.942146] r8169 :04:00.0: System wakeup enabled by ACPI Mar 23 22:55:48 aargh kernel: [ 3217.942187] xhci_hcd :00:14.0: System wakeup enabled by ACPI Mar 23 22:55:48 aargh kernel: [ 3217.957869] PM: noirq suspend of devices complete after 16.253 msecs Mar 23 22:55:48 aargh kernel: [ 3217.958141] ACPI: Preparing to enter system sleep state S3 Mar 23 22:55:48 aargh kernel: [ 3218.025580] PM: Saving platform NVS memory Mar 23 22:55:48 aargh kernel: [ 3218.025586] Disabling non-boot CPUs ... Mar 23 22:55:48 aargh kernel: [ 3218.025609] intel_pstate CPU 1 exiting Mar 23 22:55:48 aargh kernel: [ 3218.025800] Broke affinity for irq 18 Mar 23 22:55:48 aargh kernel: [ 3218.026820] kvm: disabling virtualization on CPU1 Mar 23 22:55:48 aargh kernel: [ 3218.026825] smpboot: CPU 1 is now offline Mar 23 22:55:48 aargh kernel: [ 3218.027186] intel_pstate CPU 2 exiting Mar 23 22:55:48 aargh kernel: [ 3218.028368] kvm: disabling virtualization on CPU2 Mar 23 22:55:48 aargh kernel: [ 3218.028376] smpboot: CPU 2 is now offline Mar 23 22:55:48 aargh kernel: [ 3218.028681] intel_pstate CPU 3 exiting Mar 23 22:55:48 aargh kernel: [ 3218.028782] Broke affinity for irq 42 Mar 23 22:55:48 aargh kernel: [ 3218.029796] kvm: disabling virtualization on CPU3 Mar 23 22:55:48 aargh kernel: [ 3218.029808] smpboot: CPU 3 is now offline Mar 23 22:55:48 aargh kernel: [ 3218.032593] ACPI: Low-level resume complete Mar 23 22:55:48 aargh kernel: [ 3218.032659] PM: Restoring platform NVS memory Mar 23 22:55:48 aargh kernel: [ 3218.033062] Enabling non-boot CPUs ... Mar 23 22:55:48 aargh kernel: [ 3218.033105] x86: Booting SMP configuration: Mar 23 22:55:48 aargh kernel: [ 3218.033106] smpboot: Booting Node 0 Processor 1 APIC 0x2 Mar 23 22:55:48 aargh kernel: [ 3218.045557] kvm: enabling virtualization on CPU1 Mar 23 22:55:48 aargh kernel: [ 3218.047928] CPU1 is up Mar 23 22:55:48 aargh kernel: [ 3218.047959] smpboot: Booting Node 0 Processor 2 APIC 0x1 Mar 23 22:55:48 aargh kernel: [ 3218.060017] kvm: enabling virtualization on CPU2 Mar 23 22:55:48 aargh kernel: [ 3218.062313] CPU2 is up Mar 23 22:55:48 aargh kernel: [ 3218.062330] smpboot: Booting Node 0 Processor 3 APIC 0x3 Mar 23 22:55:48 aargh kernel: [ 3218.074403] kvm: enabling virtualization on CPU3 Mar 23 22:55:48 aargh kernel: [ 3218.076717] CPU3 is up Mar 23 22:55:48 aargh kernel: [ 3218.080064] ACPI: Waking up from system sleep state S3 Mar 23 22:55:48 aargh kernel: [ 3218.228368] xhci_hcd :00:14.0: System wakeup disabled by ACPI Mar 23 22:55:48 aargh kernel: [ 3218.244618] PM: noirq resume of devices complete after 16.316 msecs Mar 23 22:55:48 aargh kernel: [ 3218.268492] PM: early resume of devices complete after 23.814 msecs Mar 23 22:55:48 aargh kernel: [ 3218.268835] r8169 :04:00.0:
[Kernel-packages] [Bug 1436319] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1436319/+attachment/4355576/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests... Status in linux package in Ubuntu: Confirmed Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 24 06:50 seq crw-rw 1 root audio 116, 33 Mar 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00a3 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ra.intel.ssd.xl4 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba InstallationDate: Installed on 2014-04-16 (343 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=vt100 PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436319] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1436319/+attachment/4355579/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests... Status in linux package in Ubuntu: Confirmed Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 24 06:50 seq crw-rw 1 root audio 116, 33 Mar 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00a3 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ra.intel.ssd.xl4 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba InstallationDate: Installed on 2014-04-16 (343 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=vt100 PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436319] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1436319/+attachment/4355574/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests... Status in linux package in Ubuntu: Confirmed Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 24 06:50 seq crw-rw 1 root audio 116, 33 Mar 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00a3 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ra.intel.ssd.xl4 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba InstallationDate: Installed on 2014-04-16 (343 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=vt100 PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436319] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1436319/+attachment/4355577/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests... Status in linux package in Ubuntu: Confirmed Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 24 06:50 seq crw-rw 1 root audio 116, 33 Mar 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00a3 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ra.intel.ssd.xl4 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba InstallationDate: Installed on 2014-04-16 (343 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=vt100 PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435581] Re: linux-armadaxp: 3.2.0-1648.67 -proposed tracker
** Description changed: This bug is for tracking the 3.2.0-1648.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 22:03 UTC kernel-stable-master-bug:1435392 kernel-stable-Certification-testing-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Security-signoff-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 05:00 UTC kernel-stable-phase-changed:Tuesday, 24. March 2015 05:00 UTC + kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 12:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1435581 Title: linux-armadaxp: 3.2.0-1648.67 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1648.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 22:03 UTC kernel-stable-master-bug:1435392 kernel-stable-Certification-testing-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Security-signoff-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 05:00 UTC kernel-stable-phase-changed:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 12:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1435581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435579] Re: linux-ti-omap4: 3.2.0-1462.82 -proposed tracker
** Description changed: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 22:01 UTC - kernel-stable-phase:Prepare - kernel-stable-phase-changed:Monday, 23. March 2015 22:01 UTC kernel-stable-master-bug:1435392 + kernel-stable-phase:ReadyToBePackaged + kernel-stable-phase-changed:Wednesday, 25. March 2015 12:00 UTC + kernel-stable-Certification-testing-end:Wednesday, 25. March 2015 12:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1435579 Title: linux-ti-omap4: 3.2.0-1462.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Confirmed Status in Kernel SRU Workflow verification-testing series: New Status in linux-ti-omap4 package in Ubuntu: New Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 22:01 UTC kernel-stable-master-bug:1435392 kernel-stable-phase:ReadyToBePackaged kernel-stable-phase-changed:Wednesday, 25. March 2015 12:00 UTC kernel-stable-Certification-testing-end:Wednesday, 25. March 2015 12:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1435579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436319] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1436319 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/1436319 Title: Unable to increase nr_requests... Status in linux package in Ubuntu: Incomplete Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1432296] Re: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1432296 Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed) Status in bcmwl package in Ubuntu: Confirmed Bug description: unable to configure getting stuck everytime and since 1 month system is not getting shutdown ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic i686 ApportVersion: 2.14.1-0ubuntu3.7 AptOrdering: ap-hotspot: Remove dnsmasq: Remove hostapd: Remove bcmwl-kernel-source: Configure Architecture: i386 Date: Sun Mar 15 10:25:01 2015 DuplicateSignature: package:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.1:subprocess installed post-installation script was killed by signal (Killed) ErrorMessage: subprocess installed post-installation script was killed by signal (Killed) InstallationDate: Installed on 2014-10-24 (141 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1432296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435392] Re: linux: 3.2.0-80.116 -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.2.0-80.116 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 15:38 UTC - kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Monday, 23. March 2015 22:05 UTC kernel-stable-Promote-to-proposed-start:Monday, 23. March 2015 22:05 UTC - kernel-stable-phase-changed:Monday, 23. March 2015 22:05 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 12:00 UTC + kernel-stable-phase:Verification Testing + kernel-stable-phase-changed:Wednesday, 25. March 2015 13:00 UTC + kernel-stable-Verification-testing-start:Wednesday, 25. March 2015 13:00 UTC + kernel-stable-Certification-testing-start:Wednesday, 25. March 2015 13:00 UTC + kernel-stable-Security-signoff-start:Wednesday, 25. March 2015 13:00 UTC + kernel-stable-Regression-testing-start:Wednesday, 25. March 2015 13:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1435392 Title: linux: 3.2.0-80.116 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug is for tracking the 3.2.0-80.116 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 15:38 UTC kernel-stable-Prepare-package-end:Monday, 23. March 2015 22:05 UTC kernel-stable-Promote-to-proposed-start:Monday, 23. March 2015 22:05 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 12:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 25. March 2015 13:00 UTC kernel-stable-Verification-testing-start:Wednesday, 25. March 2015 13:00 UTC kernel-stable-Certification-testing-start:Wednesday, 25. March 2015 13:00 UTC kernel-stable-Security-signoff-start:Wednesday, 25. March 2015 13:00 UTC kernel-stable-Regression-testing-start:Wednesday, 25. March 2015 13:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1435392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435581] Re: linux-armadaxp: 3.2.0-1648.67 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New = In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: New = Confirmed ** Description changed: This bug is for tracking the 3.2.0-1648.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 22:03 UTC kernel-stable-master-bug:1435392 kernel-stable-Certification-testing-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Security-signoff-end:Tuesday, 24. March 2015 02:02 UTC - kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 05:00 UTC - kernel-stable-phase-changed:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 12:00 UTC + kernel-stable-phase:Verification Testing + kernel-stable-phase-changed:Wednesday, 25. March 2015 13:01 UTC + kernel-stable-Verification-testing-start:Wednesday, 25. March 2015 13:01 UTC + kernel-stable-Regression-testing-start:Wednesday, 25. March 2015 13:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1435581 Title: linux-armadaxp: 3.2.0-1648.67 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1648.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 22:03 UTC kernel-stable-master-bug:1435392 kernel-stable-Certification-testing-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Security-signoff-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 12:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 25. March 2015 13:01 UTC kernel-stable-Verification-testing-start:Wednesday, 25. March 2015 13:01 UTC kernel-stable-Regression-testing-start:Wednesday, 25. March 2015 13:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1435581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436319] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1436319/+attachment/4355573/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests... Status in linux package in Ubuntu: Confirmed Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 24 06:50 seq crw-rw 1 root audio 116, 33 Mar 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00a3 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ra.intel.ssd.xl4 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba InstallationDate: Installed on 2014-04-16 (343 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=vt100 PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436319] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1436319/+attachment/4355581/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests... Status in linux package in Ubuntu: Confirmed Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 24 06:50 seq crw-rw 1 root audio 116, 33 Mar 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00a3 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ra.intel.ssd.xl4 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba InstallationDate: Installed on 2014-04-16 (343 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=vt100 PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435946] Re: IBM Power8 PPC MAAS images booting with no network
I scrolled back on the console a bit and see this: cloud-init-nonet[18.87]: waiting 120 seconds for network device cloud-init-nonet[138.87]: gave up waiting for a network device. Cloud-init v. 0.7.5 running 'init' at Tue, 24 Mar 2015 22:49:21 +. Up 139.01 seconds. ci-info: +++Net device info ci-info: ++---+---+---+---+ ci-info: | Device | Up | Address |Mask | Hw-Address| ci-info: ++---+---+---+---+ ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | ci-info: | eth1 | False | . | . | a0:1d:48:b5:2e:e5 | ci-info: | eth0 | False | . | . | a0:1d:48:b5:2e:e4 | ci-info: ++---+---+---+---+ ci-info: !!!Route info failed 2015-03-24 22:51:28,113 - DataSourceMAAS.py[CRITICAL]: Giving up on md from ['http://10.229.32.21/MAAS/metadata//2012-03-01/meta-data/instance-id'] after 126 seconds 2015-03-24 22:51:28,113 - util.py[WARNING]: No instance datasource found! Likely bad things to come! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1435946 Title: IBM Power8 PPC MAAS images booting with no network Status in linux package in Ubuntu: Confirmed Bug description: The latest daily hwe-u image for MAAS seems to lack network connectivity. Along with the below error, I cannot ssh or ping the installation. I will follow up with further information once the machine becomes available in the coming weeks. Ubuntu 14.04.2 LTS ubuntu hvc0 ubuntu login: Can not apply stage final, no datasource found! Likely bad things to come! Traceback (most recent call last): File /usr/bin/cloud-init, line 318, in main_modules init.fetch() File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 308, in fetch return self._get_data_source() File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 236, in _get_data_source pkg_list) File /usr/lib/python2.7/dist-packages/cloudinit/sources/__init__.py, line 260, in find_source raise DataSourceNotFoundException(msg) DataSourceNotFoundException: Did not find any data source, searched classes: () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1435946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435581] Re: linux-armadaxp: 3.2.0-1648.67 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = In Progress -- 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/1435581 Title: linux-armadaxp: 3.2.0-1648.67 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1648.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 22:03 UTC kernel-stable-master-bug:1435392 kernel-stable-Certification-testing-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Security-signoff-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 12:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 25. March 2015 13:01 UTC kernel-stable-Verification-testing-start:Wednesday, 25. March 2015 13:01 UTC kernel-stable-Regression-testing-start:Wednesday, 25. March 2015 13:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1435581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436319] Re: Unable to increase nr_requests...
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc5-vivid/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests... Status in linux package in Ubuntu: Incomplete Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 24 06:50 seq crw-rw 1 root audio 116, 33 Mar 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00a3 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ra.intel.ssd.xl4 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba InstallationDate: Installed on 2014-04-16 (343 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=vt100 PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435946] Re: IBM Power8 PPC MAAS images booting with no network
My error is pretty similar: Can not apply stage final, no datasource found! Likely bad things to come! Traceback (most recent call last): File /usr/bin/cloud-init, line 318, in main_modules init.fetch() File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 308, in fetch return self._get_data_source() File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 236, in _get_data_source pkg_list) File /usr/lib/python2.7/dist-packages/cloudinit/sources/__init__.py, line 260, in find_source raise DataSourceNotFoundException(msg) DataSourceNotFoundException: Did not find any data source, searched classes: () Ubuntu 14.04.2 LTS ms10-21-anders2 ttyS0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1435946 Title: IBM Power8 PPC MAAS images booting with no network Status in linux package in Ubuntu: Confirmed Bug description: The latest daily hwe-u image for MAAS seems to lack network connectivity. Along with the below error, I cannot ssh or ping the installation. I will follow up with further information once the machine becomes available in the coming weeks. Ubuntu 14.04.2 LTS ubuntu hvc0 ubuntu login: Can not apply stage final, no datasource found! Likely bad things to come! Traceback (most recent call last): File /usr/bin/cloud-init, line 318, in main_modules init.fetch() File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 308, in fetch return self._get_data_source() File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 236, in _get_data_source pkg_list) File /usr/lib/python2.7/dist-packages/cloudinit/sources/__init__.py, line 260, in find_source raise DataSourceNotFoundException(msg) DataSourceNotFoundException: Did not find any data source, searched classes: () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1435946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435946] Re: IBM Power8 PPC MAAS images booting with no network
Also, I'm hitting this with a moonshot cartridge, so it may not be arch specific. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1435946 Title: IBM Power8 PPC MAAS images booting with no network Status in linux package in Ubuntu: Confirmed Bug description: The latest daily hwe-u image for MAAS seems to lack network connectivity. Along with the below error, I cannot ssh or ping the installation. I will follow up with further information once the machine becomes available in the coming weeks. Ubuntu 14.04.2 LTS ubuntu hvc0 ubuntu login: Can not apply stage final, no datasource found! Likely bad things to come! Traceback (most recent call last): File /usr/bin/cloud-init, line 318, in main_modules init.fetch() File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 308, in fetch return self._get_data_source() File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 236, in _get_data_source pkg_list) File /usr/lib/python2.7/dist-packages/cloudinit/sources/__init__.py, line 260, in find_source raise DataSourceNotFoundException(msg) DataSourceNotFoundException: Did not find any data source, searched classes: () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1435946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435946] Re: IBM Power8 PPC MAAS images booting with no network
I was able to also reproduce this. It does not happen after installation, but after rebooting one or two times. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1435946 Title: IBM Power8 PPC MAAS images booting with no network Status in linux package in Ubuntu: Confirmed Bug description: The latest daily hwe-u image for MAAS seems to lack network connectivity. Along with the below error, I cannot ssh or ping the installation. I will follow up with further information once the machine becomes available in the coming weeks. Ubuntu 14.04.2 LTS ubuntu hvc0 ubuntu login: Can not apply stage final, no datasource found! Likely bad things to come! Traceback (most recent call last): File /usr/bin/cloud-init, line 318, in main_modules init.fetch() File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 308, in fetch return self._get_data_source() File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 236, in _get_data_source pkg_list) File /usr/lib/python2.7/dist-packages/cloudinit/sources/__init__.py, line 260, in find_source raise DataSourceNotFoundException(msg) DataSourceNotFoundException: Did not find any data source, searched classes: () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1435946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1434842] Re: Due to lack of OSS kernel modules, have to recompile the kernel to enable sound in old games - aoss/padsp do not work
Two minor issues with Andy's test kernel: 1) The modules landed in linux-image, while they should be in linux-image-extra 2) You probably want to move the common* bit after the autogen bit, not before, so the format of the final blacklist file makes more sense to a human reading it. ie: right now, it looks like: #Autogen #common common.ko autogen.ko You probably wanted: #Autogen autogen.ko #common common.ko -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1434842 Title: Due to lack of OSS kernel modules, have to recompile the kernel to enable sound in old games - aoss/padsp do not work Status in linux package in Ubuntu: In Progress Bug description: I've had this issue since about 12.10 or whenever the oss modules with disable in the kernel. i.e CONFIG_SND_MIXER_OSS CONFIG_SND_PCM_OSS CONFIG_SND_PCM_OSS_PLUGINS Ubuntu is one of the few distros to take out these module from their kernel builds. On Debian, Fedora, Arch and Opensuse the modules are in the kernel (you usually have to manually load them (i.e they are present by default wbut disabled - with ubuntu the modules are actually removed.) There is one game in particular I play, it in an old obscure game called paintball2 - http://digitalpaint.org/ It uses OSS by default - it does have an SDL option too (which works in ubuntu) - but the SDL plugin is buggy. With all other distros I can just manually load the OSS modules, with Ubuntu I have to recompile the kernel in order to have OSS sound. Could we not change the policy and include the modules (the size difference will be basically none.) so at least people have the option to use them without the hassle to recompiling the kernel - its a PITA having to do it again each time there is an update. I know of aoss and padsp - these tools do not work (at least with this game), they never have in multiple machines (all have had intel HDA cards) i.e - aoss ./paintball2 LoadLibrary(./snd_oss.so) /dev/dsp: Invalid argument SNDDMA_Init: Could not mmap /dev/dsp. - -- no sound - padsp ./paintball2 Paintball 2 -- Version 2.0 execing configs/config.cfg Console initialized. --- sound initialization --- LoadLibrary(./snd_oss.so) SNDDMA_Init: Sorry, but your soundcard doesn't support trigger or mmap. (5100) - -- no sound. As soon as i recompile the kernel and add the modules it works fine. How can I get the modules re-added - there is no harm having them in the kernel but disabled on startup... ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-generic 3.16.0.31.32 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: morgan 2477 F pulseaudio /dev/snd/controlC0: morgan 2477 F pulseaudio CurrentDesktop: KDE Date: Sat Mar 21 15:24:46 2015 HibernationDevice: RESUME=UUID=c5ec1412-eab8-4557-a6e8-cb6856e167d8 InstallationDate: Installed on 2015-02-11 (37 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7758 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-31-generic root=UUID=79c952bd-d3f3-4bf7-9039-5260c0217d02 ro RelatedPackageVersions: linux-restricted-modules-3.16.0-31-generic N/A linux-backports-modules-3.16.0-31-generic N/A linux-firmware 1.138.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Mar 21 14:28:15 morgan-MS-7758 kernel: [ 8449.255485] perf interrupt took too long (2507 2500), lowering kernel.perf_event_max_sample_rate to 5 dmi.bios.date: 03/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1436375] [NEW] suspend/resume failure [non-free: fglrx]
Public bug reported: As ever, there are crashes unnoticed by me, but noticed by Ubuntu :s. I can't tell anything about the crush, except that is related with the AMD Catalyst driver (I have installed the 14.12 Omega version). ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-33-generic 3.16.0-33.44~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 NonfreeKernelModules: fglrx Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Wed Mar 25 10:00:41 2015 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2013-03-10 (744 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) InterpreterPath: /usr/bin/python3.4 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: linux-lts-utopic Title: suspend/resume failure [non-free: fglrx] UpgradeStatus: Upgraded to trusty on 2014-04-26 (333 days ago) UserGroups: ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume suspend trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1436375 Title: suspend/resume failure [non-free: fglrx] Status in linux-lts-utopic package in Ubuntu: New Bug description: As ever, there are crashes unnoticed by me, but noticed by Ubuntu :s. I can't tell anything about the crush, except that is related with the AMD Catalyst driver (I have installed the 14.12 Omega version). ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-33-generic 3.16.0-33.44~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 NonfreeKernelModules: fglrx Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Wed Mar 25 10:00:41 2015 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2013-03-10 (744 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) InterpreterPath: /usr/bin/python3.4 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: linux-lts-utopic Title: suspend/resume failure [non-free: fglrx] UpgradeStatus: Upgraded to trusty on 2014-04-26 (333 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1436375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436147] Re: Ubuntu 14.04 LTS support release does not return to signon screen after suspend mode is woken up
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc5-vivid/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436147 Title: Ubuntu 14.04 LTS support release does not return to signon screen after suspend mode is woken up Status in linux package in Ubuntu: Incomplete Bug description: I am running Ubnutu 14.04 LTS. I can put my computer into suspend mode successfully. But, when I try to waken the computer from suspend mode, I never get the signon screen. I just get a blank screen and linux seems to be in some type of loop. I have to power down my computer to get out of this situation. Quite annoying to say the least. Christopher M. Penalver said to assign/subscribe him to this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-46-generic 3.13.0-46.79 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1881 F pulseaudio /dev/snd/controlC1: michael1881 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 24 22:52:53 2015 HibernationDevice: RESUME=UUID=b002383e-573d-44a8-b7c8-0e2bb5f9e517 InstallationDate: Installed on 2014-07-14 (253 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=fe2c6d32-094c-40c4-8713-eee378320a08 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-46-generic N/A linux-backports-modules-3.13.0-46-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080009 dmi.board.name: P4P800SE dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: Rev 2.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080009:bd12/13/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerInc.:rnP4P800SE:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1331513] Re: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720
@Wonko, I've updated the driver to the latest version from broadcom.com, version 3.137h; and I am still experiencing a similar issue. However, when the driver crashes, sometimes (70%) chance that the machine is useable, and another 30% the machine is totally locked up. The NIC i am using is new, its product ID is 1687, and has an external PHY Rev. of 5762C. I am able to replicate it with the following methods: 1. Start the tg3 machine 2. from another machine: start 5 sessions, repetitively copy (scp with public key authentication) a 70 meg file back and forth to the tg3 machine in each session. (not sure if this is necessary) 3. create a 1GB file on the tg3 machine, with something like dd if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*100)) 4. from another machine: repetitively scp copy that 1GB file from the tg3 machine. This can be done with something like: while [ 0 ]; do scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file / done; I've done it about 40 times, and the tg3 machine will crash anywhere from 5 minutes to 50 minutes into the test. I am still scratching my head over this bug, and as a matter of fact, we are thinking about switching to an Intel or Realtek NIC, if we can not get this resolved soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1331513 Title: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720 Status in The Dell PowerEdge project: Triaged Status in linux package in Ubuntu: Triaged Bug description: we have a problem with Dell PowerEdge machines, having the Broadcom 5720 chip. We have this problem on generation 12 systems, across different models (R420, R620), with several combinations of bios firmwares, lifecycle firmwares, etc... We see this on several versions of the linux kernel, ranging from 3.2.x up tot 3.11, with several versions of the tg3 driver, including a manually compiled latest version (3.133d) loaded in a 3.11. The latest machine, where we can reproduce the problem has Ubuntu Precise installed, but we also see this behaviour on Debian machines. We run Xen on it, running HVM hosts on it. Storage is handled over iSCSI (and it is the iSCSI interface we can trigger this bug on in a reproducible way, while we have the impression it also happens on other interfaces, but there we don't have a solid case where we have e reproducible setup). All this info actually points into the direction of the tg3 driver and/or hardware below it not handling certain datastreams or data patterns correctly, and finally crashing the system. It seems unrelated to the version of kernel running, xen-version running, amount of VM's running, firmwares and revisions running, etc... We have been trying to pinpoint this for over a year now, being unable to actually create a scenario where we could reproduce this. As of this week, we finally found a specific setup where we could trigger the error within a reasonable time. The error is triggered by running a certain VM on the Xen stack, and inside that VM, importing a mysqldump in a running mysql on that VM. The VM has it's traffic on an iSCSI volume, so this effectually generates a datastream over the eth1 interface of the machine. Within a short amount of time, the system will crash in 2 steps. We first see a timeout on the tg3 driver on the eth1 interface (dmesg output section attached). This sometimes repeats two or three times, and finally, step 2, the machine freezes and reboots. While debugging, we noticed that the bug goes away when we disable sg offloading with ethtool. If you need any additional info, feel free to ask. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.11.0-19-generic 3.11.0-19.33~precise1 ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Jun 18 16:36 seq crw-rw---T 1 root audio 116, 33 Jun 18 16:36 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Jun 18 16:47:27 2014 HibernationDevice: RESUME=UUID=f3577e02-64e3-4cab-b6e7-f30efa111565 InstallationMedia: Ubuntu-Server 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) MachineType: Dell Inc. PowerEdge R420 MarkForUpload: True PciMultimedia: ProcFB: ProcKernelCmdLine: placeholder root=UUID=bbc71780-90bf-4647-b579-e48d5d8c2bce ro vga=0x317 RelatedPackageVersions: linux-restricted-modules-3.11.0-19-generic N/A
[Kernel-packages] [Bug 1435581] Re: linux-armadaxp: 3.2.0-1648.67 -proposed tracker
** Description changed: This bug is for tracking the 3.2.0-1648.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 22:03 UTC kernel-stable-master-bug:1435392 kernel-stable-Certification-testing-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Security-signoff-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 12:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 25. March 2015 13:01 UTC kernel-stable-Verification-testing-start:Wednesday, 25. March 2015 13:01 UTC kernel-stable-Regression-testing-start:Wednesday, 25. March 2015 13:01 UTC + kernel-stable-Regression-testing-end:Wednesday, 25. March 2015 15:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1435581 Title: linux-armadaxp: 3.2.0-1648.67 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1648.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 22:03 UTC kernel-stable-master-bug:1435392 kernel-stable-Certification-testing-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Security-signoff-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 12:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 25. March 2015 13:01 UTC kernel-stable-Verification-testing-start:Wednesday, 25. March 2015 13:01 UTC kernel-stable-Regression-testing-start:Wednesday, 25. March 2015 13:01 UTC kernel-stable-Regression-testing-end:Wednesday, 25. March 2015 15:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1435581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413540] Re: Trusty soft lockup issues with nested KVM
@smb - after repeating the test a few times, I too ran out of space with the default 8GB VM disk size, resulting in a paused VM. You'll have to re-create the VMs a little bit differently (--disk GB). ex: @L0: sudo uvt-kvm destroy trusty-vm sudo uvt-kvm create --memory 2048 --disk 40 trusty-vm release=trusty @L1: #repeat original repro ref: http://manpages.ubuntu.com/manpages/trusty/man1/uvt-kvm.1.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/1413540 Title: Trusty soft lockup issues with nested KVM Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Users of nested KVM for testing openstack have soft lockups as follows: PID: 22262 TASK: 8804274bb000 CPU: 1 COMMAND: qemu-system-x86 #0 [88043fd03d18] machine_kexec at 8104ac02 #1 [88043fd03d68] crash_kexec at 810e7203 #2 [88043fd03e30] panic at 81719ff4 #3 [88043fd03ea8] watchdog_timer_fn at 8110d7c5 #4 [88043fd03ed8] __run_hrtimer at 8108e787 #5 [88043fd03f18] hrtimer_interrupt at 8108ef4f #6 [88043fd03f80] local_apic_timer_interrupt at 81043537 #7 [88043fd03f98] smp_apic_timer_interrupt at 81733d4f #8 [88043fd03fb0] apic_timer_interrupt at 817326dd --- IRQ stack --- #9 [880426f0d958] apic_timer_interrupt at 817326dd [exception RIP: generic_exec_single+130] RIP: 810dbe62 RSP: 880426f0da00 RFLAGS: 0202 RAX: 0002 RBX: 880426f0d9d0 RCX: 0001 RDX: 8180ad60 RSI: RDI: 0286 RBP: 880426f0da30 R8: 8180ad48 R9: 88042713bc68 R10: 7fe7d1f2dbd0 R11: 0206 R12: 8804274bb000 R13: R14: 880407670280 R15: ORIG_RAX: ff10 CS: 0010 SS: 0018 #10 [880426f0da38] smp_call_function_single at 810dbf75 #11 [880426f0dab0] smp_call_function_many at 810dc3a6 #12 [880426f0db10] native_flush_tlb_others at 8105c8f7 #13 [880426f0db38] flush_tlb_mm_range at 8105c9cb #14 [880426f0db68] pmdp_splitting_flush at 8105b80d #15 [880426f0db88] __split_huge_page at 811ac90b #16 [880426f0dc20] split_huge_page_to_list at 811acfb8 #17 [880426f0dc48] __split_huge_page_pmd at 811ad956 #18 [880426f0dcc8] unmap_page_range at 8117728d #19 [880426f0dda0] unmap_single_vma at 81177341 #20 [880426f0ddd8] zap_page_range at 811784cd #21 [880426f0de90] sys_madvise at 81174fbf #22 [880426f0df80] system_call_fastpath at 8173196d RIP: 7fe7ca2cc647 RSP: 7fe7be9febf0 RFLAGS: 0293 RAX: 001c RBX: 8173196d RCX: RDX: 0004 RSI: 007fb000 RDI: 7fe7be1ff000 RBP: R8: R9: 7fe7d1cd2738 R10: 7fe7d1f2dbd0 R11: 0206 R12: 7fe7be9ff700 R13: 7fe7be9ff9c0 R14: R15: ORIG_RAX: 001c CS: 0033 SS: 002b [Test Case] - Deploy openstack on openstack - Run tempest on L1 cloud - Check kernel log of L1 nova-compute nodes (Although this may not necessarily be related to nested KVM) Potentially related: https://lkml.org/lkml/2014/11/14/656 -- Original Description: When installing qemu-kvm on a VM, KSM is enabled. I have encountered this problem in trusty:$ lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 14.04.1 LTS Release:14.04 Codename: trusty $ uname -a Linux juju-gema-machine-2 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The way to see the behaviour: 1) $ more /sys/kernel/mm/ksm/run 0 2) $ sudo apt-get install qemu-kvm 3) $ more /sys/kernel/mm/ksm/run 1 To see the soft lockups, deploy a cloud on a virtualised env like ctsstack, run tempest on it, the compute nodes of the virtualised deployment will eventually stop responding with (run tempest 2 times at least): 24096.072003] BUG: soft lockup - CPU#0 stuck for 23s! [qemu-system-x86:24791] [24124.072003] BUG: soft lockup - CPU#0 stuck for 23s! [qemu-system-x86:24791] [24152.072002] BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-x86:24791] [24180.072003] BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-x86:24791] [24208.072004] BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-x86:24791] [24236.072004] BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-x86:24791] [24264.072003] BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-x86:24791] I am not sure whether the problem is that we are
[Kernel-packages] [Bug 1435581] Re: linux-armadaxp: 3.2.0-1648.67 -proposed tracker
** Tags added: qa-testing-passed ** Changed in: kernel-sru-workflow/verification-testing Status: In Progress = Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1435581 Title: linux-armadaxp: 3.2.0-1648.67 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1648.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 22:03 UTC kernel-stable-master-bug:1435392 kernel-stable-Certification-testing-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Security-signoff-end:Tuesday, 24. March 2015 02:02 UTC kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 05:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 12:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 25. March 2015 13:01 UTC kernel-stable-Verification-testing-start:Wednesday, 25. March 2015 13:01 UTC kernel-stable-Regression-testing-start:Wednesday, 25. March 2015 13:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1435581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413540] Re: Trusty soft lockup issues with nested KVM
Hrmn... When I repeated the setup I seem to have triggered some kind of lockup even while bringing up l2. Of course hard to say without details of Ryan's dump. However mine seems to have backtraces in the log which remind me an awful lot of an issue related to punching holes into ext4 based qcow images. Chris had been working on something like this before... He is on a sprint this week. Anyway, my strace in the log: [ 1200.288031] INFO: task qemu-system-x86:4545 blocked for more than 120 seconds. [ 1200.288712] Not tainted 3.13.0-46-generic #77-Ubuntu [ 1200.289204] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 1200.289892] qemu-system-x86 D 88007fc134c0 0 4545 1 0x [ 1200.289895] 88007a9c5d28 0082 88007bbd3000 88007a9c5fd8 [ 1200.289897] 000134c0 000134c0 88007bbd3000 88007fc13d58 [ 1200.289898] 88007ffcdee8 0002 8114eef0 88007a9c5da0 [ 1200.289900] Call Trace: [ 1200.289906] [8114eef0] ? wait_on_page_read+0x60/0x60 [ 1200.289909] [817259fd] io_schedule+0x9d/0x140 [ 1200.289910] [8114eefe] sleep_on_page+0xe/0x20 [ 1200.289912] [81725e82] __wait_on_bit+0x62/0x90 [ 1200.289914] [8114ecbf] wait_on_page_bit+0x7f/0x90 [ 1200.289917] [810ab140] ? autoremove_wake_function+0x40/0x40 [ 1200.289919] [8115c4a1] ? pagevec_lookup_tag+0x21/0x30 [ 1200.289921] [8114edc9] filemap_fdatawait_range+0xf9/0x190 [ 1200.289923] [8115066f] filemap_write_and_wait_range+0x3f/0x70 [ 1200.289927] [8123bc4a] ext4_sync_file+0xba/0x320 [ 1200.289930] [811ede21] do_fsync+0x51/0x80 [ 1200.289931] [811ee0d3] SyS_fdatasync+0x13/0x20 [ 1200.289933] [81731d7d] system_call_fastpath+0x1a/0x1f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413540 Title: Trusty soft lockup issues with nested KVM Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Users of nested KVM for testing openstack have soft lockups as follows: PID: 22262 TASK: 8804274bb000 CPU: 1 COMMAND: qemu-system-x86 #0 [88043fd03d18] machine_kexec at 8104ac02 #1 [88043fd03d68] crash_kexec at 810e7203 #2 [88043fd03e30] panic at 81719ff4 #3 [88043fd03ea8] watchdog_timer_fn at 8110d7c5 #4 [88043fd03ed8] __run_hrtimer at 8108e787 #5 [88043fd03f18] hrtimer_interrupt at 8108ef4f #6 [88043fd03f80] local_apic_timer_interrupt at 81043537 #7 [88043fd03f98] smp_apic_timer_interrupt at 81733d4f #8 [88043fd03fb0] apic_timer_interrupt at 817326dd --- IRQ stack --- #9 [880426f0d958] apic_timer_interrupt at 817326dd [exception RIP: generic_exec_single+130] RIP: 810dbe62 RSP: 880426f0da00 RFLAGS: 0202 RAX: 0002 RBX: 880426f0d9d0 RCX: 0001 RDX: 8180ad60 RSI: RDI: 0286 RBP: 880426f0da30 R8: 8180ad48 R9: 88042713bc68 R10: 7fe7d1f2dbd0 R11: 0206 R12: 8804274bb000 R13: R14: 880407670280 R15: ORIG_RAX: ff10 CS: 0010 SS: 0018 #10 [880426f0da38] smp_call_function_single at 810dbf75 #11 [880426f0dab0] smp_call_function_many at 810dc3a6 #12 [880426f0db10] native_flush_tlb_others at 8105c8f7 #13 [880426f0db38] flush_tlb_mm_range at 8105c9cb #14 [880426f0db68] pmdp_splitting_flush at 8105b80d #15 [880426f0db88] __split_huge_page at 811ac90b #16 [880426f0dc20] split_huge_page_to_list at 811acfb8 #17 [880426f0dc48] __split_huge_page_pmd at 811ad956 #18 [880426f0dcc8] unmap_page_range at 8117728d #19 [880426f0dda0] unmap_single_vma at 81177341 #20 [880426f0ddd8] zap_page_range at 811784cd #21 [880426f0de90] sys_madvise at 81174fbf #22 [880426f0df80] system_call_fastpath at 8173196d RIP: 7fe7ca2cc647 RSP: 7fe7be9febf0 RFLAGS: 0293 RAX: 001c RBX: 8173196d RCX: RDX: 0004 RSI: 007fb000 RDI: 7fe7be1ff000 RBP: R8: R9: 7fe7d1cd2738 R10: 7fe7d1f2dbd0 R11: 0206 R12: 7fe7be9ff700 R13: 7fe7be9ff9c0 R14: R15: ORIG_RAX: 001c CS: 0033 SS: 002b [Test Case] - Deploy openstack on openstack - Run tempest on L1 cloud - Check kernel log of L1 nova-compute nodes (Although this may not necessarily be related to nested KVM)
[Kernel-packages] [Bug 1413540] Re: Trusty soft lockup issues with nested KVM
Yeah, will do. Just got distracted and wanted to ensure that the repro was not accidentally another form of failure path to the out of space issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413540 Title: Trusty soft lockup issues with nested KVM Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Users of nested KVM for testing openstack have soft lockups as follows: PID: 22262 TASK: 8804274bb000 CPU: 1 COMMAND: qemu-system-x86 #0 [88043fd03d18] machine_kexec at 8104ac02 #1 [88043fd03d68] crash_kexec at 810e7203 #2 [88043fd03e30] panic at 81719ff4 #3 [88043fd03ea8] watchdog_timer_fn at 8110d7c5 #4 [88043fd03ed8] __run_hrtimer at 8108e787 #5 [88043fd03f18] hrtimer_interrupt at 8108ef4f #6 [88043fd03f80] local_apic_timer_interrupt at 81043537 #7 [88043fd03f98] smp_apic_timer_interrupt at 81733d4f #8 [88043fd03fb0] apic_timer_interrupt at 817326dd --- IRQ stack --- #9 [880426f0d958] apic_timer_interrupt at 817326dd [exception RIP: generic_exec_single+130] RIP: 810dbe62 RSP: 880426f0da00 RFLAGS: 0202 RAX: 0002 RBX: 880426f0d9d0 RCX: 0001 RDX: 8180ad60 RSI: RDI: 0286 RBP: 880426f0da30 R8: 8180ad48 R9: 88042713bc68 R10: 7fe7d1f2dbd0 R11: 0206 R12: 8804274bb000 R13: R14: 880407670280 R15: ORIG_RAX: ff10 CS: 0010 SS: 0018 #10 [880426f0da38] smp_call_function_single at 810dbf75 #11 [880426f0dab0] smp_call_function_many at 810dc3a6 #12 [880426f0db10] native_flush_tlb_others at 8105c8f7 #13 [880426f0db38] flush_tlb_mm_range at 8105c9cb #14 [880426f0db68] pmdp_splitting_flush at 8105b80d #15 [880426f0db88] __split_huge_page at 811ac90b #16 [880426f0dc20] split_huge_page_to_list at 811acfb8 #17 [880426f0dc48] __split_huge_page_pmd at 811ad956 #18 [880426f0dcc8] unmap_page_range at 8117728d #19 [880426f0dda0] unmap_single_vma at 81177341 #20 [880426f0ddd8] zap_page_range at 811784cd #21 [880426f0de90] sys_madvise at 81174fbf #22 [880426f0df80] system_call_fastpath at 8173196d RIP: 7fe7ca2cc647 RSP: 7fe7be9febf0 RFLAGS: 0293 RAX: 001c RBX: 8173196d RCX: RDX: 0004 RSI: 007fb000 RDI: 7fe7be1ff000 RBP: R8: R9: 7fe7d1cd2738 R10: 7fe7d1f2dbd0 R11: 0206 R12: 7fe7be9ff700 R13: 7fe7be9ff9c0 R14: R15: ORIG_RAX: 001c CS: 0033 SS: 002b [Test Case] - Deploy openstack on openstack - Run tempest on L1 cloud - Check kernel log of L1 nova-compute nodes (Although this may not necessarily be related to nested KVM) Potentially related: https://lkml.org/lkml/2014/11/14/656 -- Original Description: When installing qemu-kvm on a VM, KSM is enabled. I have encountered this problem in trusty:$ lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 14.04.1 LTS Release:14.04 Codename: trusty $ uname -a Linux juju-gema-machine-2 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The way to see the behaviour: 1) $ more /sys/kernel/mm/ksm/run 0 2) $ sudo apt-get install qemu-kvm 3) $ more /sys/kernel/mm/ksm/run 1 To see the soft lockups, deploy a cloud on a virtualised env like ctsstack, run tempest on it, the compute nodes of the virtualised deployment will eventually stop responding with (run tempest 2 times at least): 24096.072003] BUG: soft lockup - CPU#0 stuck for 23s! [qemu-system-x86:24791] [24124.072003] BUG: soft lockup - CPU#0 stuck for 23s! [qemu-system-x86:24791] [24152.072002] BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-x86:24791] [24180.072003] BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-x86:24791] [24208.072004] BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-x86:24791] [24236.072004] BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-x86:24791] [24264.072003] BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-x86:24791] I am not sure whether the problem is that we are enabling KSM on a VM or the problem is that nested KSM is not behaving properly. Either way I can easily reproduce, please contact me if you need further details. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1435637] Re: linux-lts-utopic: 3.16.0-34.45~14.04.1 -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-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1435637 Title: linux-lts-utopic: 3.16.0-34.45~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-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-34.45~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, 24. March 2015 02:00 UTC kernel-stable-master-bug:1435400 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 19:01 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 19:01 UTC kernel-stable-phase-changed:Tuesday, 24. March 2015 19:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1435637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436132] Re: linux-lts-trusty: 3.13.0-49.81~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) = Kamal Mostafa (kamalmostafa) -- 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/1436132 Title: linux-lts-trusty: 3.13.0-49.81~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: New Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-49.81~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:Wednesday, 25. March 2015 02:02 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 25. March 2015 02:02 UTC kernel-stable-master-bug:1436016 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1436132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436016] Re: linux: 3.13.0-49.81 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-49.81 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, 24. March 2015 18:55 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 25. March 2015 02:03 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 25. March 2015 02:03 UTC kernel-stable-phase-changed:Wednesday, 25. March 2015 02:03 UTC + kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 17:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436016 Title: linux: 3.13.0-49.81 -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 package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-49.81 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, 24. March 2015 18:55 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 25. March 2015 02:03 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 25. March 2015 02:03 UTC kernel-stable-phase-changed:Wednesday, 25. March 2015 02:03 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 17:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1436016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435946] Re: IBM Power8 PPC MAAS images booting with no network
After re-deploying the node today, I'm unable to reproduce the bug. @Mike, can you see if you can still reproduce the bug once you have hardware? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1435946 Title: IBM Power8 PPC MAAS images booting with no network Status in linux package in Ubuntu: Confirmed Bug description: The latest daily hwe-u image for MAAS seems to lack network connectivity. Along with the below error, I cannot ssh or ping the installation. I will follow up with further information once the machine becomes available in the coming weeks. Ubuntu 14.04.2 LTS ubuntu hvc0 ubuntu login: Can not apply stage final, no datasource found! Likely bad things to come! Traceback (most recent call last): File /usr/bin/cloud-init, line 318, in main_modules init.fetch() File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 308, in fetch return self._get_data_source() File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 236, in _get_data_source pkg_list) File /usr/lib/python2.7/dist-packages/cloudinit/sources/__init__.py, line 260, in find_source raise DataSourceNotFoundException(msg) DataSourceNotFoundException: Did not find any data source, searched classes: () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1435946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1416847] Re: kerneloops on suspend from resume
I have the same hardware and I share the same problem. In fact, the kernel in use, is shared by both Ubuntu and Debian. I am on the Debian Jessie kernel. Like the OP, I tried with 3.19.2, but the problem exists. He was lucky to have survived 2 weeks. I can't survive more than 48 hrs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1416847 Title: kerneloops on suspend from resume Status in linux package in Ubuntu: Incomplete Bug description: Every third or fourth suspend failes on my Lenovo Yoga 2-13, I have to hard reset the notebook. Apportcheckresume informs me about an internel error on next boot, but I cannot find the cause of the problem in the crash report. $ uname -a Linux SandraOrange 3.16.0-29-generic #39-Ubuntu SMP Mon Dec 15 22:27:29 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sandra 2484 F pulseaudio /dev/snd/controlC1: sandra 2484 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c31e5706-71d4-4a32-993f-3b6f2a1bd3bb InstallationDate: Installed on 2015-01-19 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20344 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=3d93d64f-d67f-428f-b719-a51e43e9903f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-29-generic N/A linux-backports-modules-3.16.0-29-generic N/A linux-firmware 1.138.1 Tags: utopic Uname: Linux 3.16.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435637] Re: linux-lts-utopic: 3.16.0-34.45~14.04.1 -proposed tracker
** Description changed: This bug is for tracking the 3.16.0-34.45~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, 24. March 2015 02:00 UTC kernel-stable-master-bug:1435400 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 19:01 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 19:01 UTC kernel-stable-phase-changed:Tuesday, 24. March 2015 19:01 UTC + kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 17:29 UTC -- 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/1435637 Title: linux-lts-utopic: 3.16.0-34.45~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-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-34.45~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, 24. March 2015 02:00 UTC kernel-stable-master-bug:1435400 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 19:01 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 19:01 UTC kernel-stable-phase-changed:Tuesday, 24. March 2015 19:01 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 17:29 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1435637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435637] Re: linux-lts-utopic: 3.16.0-34.45~14.04.1 -proposed tracker
Promoted to proposed: linux-lts-utopic| 3.16.0-34.45~14.04.1 | trusty-proposed | source linux-meta-lts-utopic | 3.16.0.34.27 | trusty-proposed | source linux-signed-lts-utopic | 3.16.0-34.45~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-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1435637 Title: linux-lts-utopic: 3.16.0-34.45~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-utopic package in Ubuntu: New Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-34.45~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, 24. March 2015 02:00 UTC kernel-stable-master-bug:1435400 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 19:01 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 19:01 UTC kernel-stable-phase-changed:Tuesday, 24. March 2015 19:01 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 17:29 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1435637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1416847] Re: kerneloops on suspend from resume
While the Yoga 2 13 is in no way shipped by Lenovo, their acpi tables do
have an exception for _OSI(Linux). Which makes me wonder if that's just
to blacklist things.
Someone more knowledgable on this list may want to shed some light.
Method (_INI, 0, NotSerialized) // _INI: Initialize
{
Store (0x07D0, OSYS) /* \OSYS */
If (CondRefOf (\_OSI, Local0))
{
If (_OSI (Windows 2001))
{
Store (0x07D1, OSYS) /* \OSYS */
}
If (_OSI (Windows 2001 SP1))
{
Store (0x07D1, OSYS) /* \OSYS */
}
If (_OSI (Windows 2001 SP2))
{
Store (0x07D2, OSYS) /* \OSYS */
}
If (_OSI (Windows 2001.1))
{
Store (0x07D3, OSYS) /* \OSYS */
}
If (_OSI (Windows 2006))
{
Store (0x07D6, OSYS) /* \OSYS */
}
If (_OSI (Windows 2009))
{
Store (0x07D9, OSYS) /* \OSYS */
}
If (_OSI (Windows 2012))
{
Store (0x07DC, OSYS) /* \OSYS */
}
If (_OSI (Windows 2013))
{
Store (0x07DD, OSYS) /* \OSYS */
}
If (_OSI (Linux))
{
Store (0x03E8, OSYS) /* \OSYS */
}
}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1416847
Title:
kerneloops on suspend from resume
Status in linux package in Ubuntu:
Incomplete
Bug description:
Every third or fourth suspend failes on my Lenovo Yoga 2-13, I have to
hard reset the notebook.
Apportcheckresume informs me about an internel error on next boot, but
I cannot find the cause of the problem in the crash report.
$ uname -a
Linux SandraOrange 3.16.0-29-generic #39-Ubuntu SMP Mon Dec 15 22:27:29 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
---
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sandra 2484 F pulseaudio
/dev/snd/controlC1: sandra 2484 F pulseaudio
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=c31e5706-71d4-4a32-993f-3b6f2a1bd3bb
InstallationDate: Installed on 2015-01-19 (12 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64
(20141022.1)
MachineType: LENOVO 20344
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic
root=UUID=3d93d64f-d67f-428f-b719-a51e43e9903f ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-3.16.0-29-generic N/A
linux-backports-modules-3.16.0-29-generic N/A
linux-firmware 1.138.1
Tags: utopic
Uname: Linux 3.16.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 10/16/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 96CN29WW(V1.15)
dmi.board.asset.tag: 31900058WIN
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 31900058WIN
dmi.chassis.asset.tag: 31900058WIN
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 2 13
dmi.modalias:
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
dmi.product.name: 20344
dmi.product.version: Lenovo Yoga 2 13
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416847/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436319] Re: Unable to increase nr_requests...
echo 129 /sys/block/vda/queue/nr_requests bash: echo: write error: Invalid argument ** Summary changed: - Unable to increase nr_requests... + Unable to increase nr_requests Change The I/O Scheduler ... ** Summary changed: - Unable to increase nr_requests Change The I/O Scheduler ... + Unable to increase nr_requests change I/O scheduler ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests change I/O scheduler ... Status in linux package in Ubuntu: Confirmed Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 24 06:50 seq crw-rw 1 root audio 116, 33 Mar 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00a3 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ra.intel.ssd.xl4 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba InstallationDate: Installed on 2014-04-16 (343 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=vt100 PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436319] Re: Unable to increase nr_requests...
uname -a Linux test 4.0.0-04rc5-generic #201503230035 SMP Mon Mar 23 04:36:26 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux cat /sys/block/vda/queue/scheduler none ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436319 Title: Unable to increase nr_requests change I/O scheduler ... Status in linux package in Ubuntu: Confirmed Bug description: Anyone know why ubuntu utopic/trusty doesn’t allow to change nr_requests and I/O scheduler for instance that is running on the cloud running openstack havana? echo 129 /sys/block/vda/queue/nr_requests -bash: echo: write error: Invalid argument However values lower then 129 works. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 24 06:50 seq crw-rw 1 root audio 116, 33 Mar 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00a3 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ra.intel.ssd.xl4 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 HibernationDevice: RESUME=UUID=7b7c8950-fe4d-4322-9a60-48dadc7d5eba InstallationDate: Installed on 2014-04-16 (343 days ago) InstallationMedia: IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=vt100 PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=afee8cc2-d9a0-4f30-8454-94e974e89bf4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.2:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436016] Re: linux: 3.13.0-49.81 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed = Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Adam Conrad (adconrad) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436016 Title: linux: 3.13.0-49.81 -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 package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-49.81 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, 24. March 2015 18:55 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 25. March 2015 02:03 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 25. March 2015 02:03 UTC kernel-stable-phase-changed:Wednesday, 25. March 2015 02:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1436016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435579] Re: linux-ti-omap4: 3.2.0-1462.82 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) = Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1435579 Title: linux-ti-omap4: 3.2.0-1462.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Confirmed Status in Kernel SRU Workflow verification-testing series: New Status in linux-ti-omap4 package in Ubuntu: New Status in linux-ti-omap4 source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 22:01 UTC kernel-stable-master-bug:1435392 kernel-stable-phase:ReadyToBePackaged kernel-stable-phase-changed:Wednesday, 25. March 2015 12:00 UTC kernel-stable-Certification-testing-end:Wednesday, 25. March 2015 12:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1435579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436451] [NEW] can't power off when shutting down
You have been subscribed to a public bug: We have a dozen of HP laptop here running ubuntu and xubuntu 14.04 and 14.10 and, since few months, all of them can't power off when we try to shutdown them. Indeed, after few seconds of an apparent power off, the laptops restart. Please find attached, the dmesg result of one of them. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- can't power off when shutting down https://bugs.launchpad.net/bugs/1436451 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 1436451] Re: can't power off when shutting down
** Project changed: launchpad = 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/1436451 Title: can't power off when shutting down Status in linux package in Ubuntu: New Bug description: We have a dozen of HP laptop here running ubuntu and xubuntu 14.04 and 14.10 and, since few months, all of them can't power off when we try to shutdown them. Indeed, after few seconds of an apparent power off, the laptops restart. Please find attached, the dmesg result of one of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436451] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1436451 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 ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436451 Title: can't power off when shutting down Status in linux package in Ubuntu: Incomplete Bug description: We have a dozen of HP laptop here running ubuntu and xubuntu 14.04 and 14.10 and, since few months, all of them can't power off when we try to shutdown them. Indeed, after few seconds of an apparent power off, the laptops restart. Please find attached, the dmesg result of one of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1307236] Re: NVidia Issues - blurry text after upgrading from 13.10 to 14.04
Shehi's comment worked for me. Thanks to this. Same problem here, with GTX 760 on nvidia-346. Disabled FXAA, restart lightdm [sudo restart lightdm] and bam, fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1307236 Title: NVidia Issues - blurry text after upgrading from 13.10 to 14.04 Status in nvidia-settings package in Ubuntu: Expired Bug description: I have a System76 Bonoboo with a GeForce GTX 670MX I upgraded from 13.10 to 14.04 and after the upgrade finished I logged in and the text in the windows would get blurry until I refocused on the window and then get blurry again. I tried various nvidia installs (nvidia-common, nvidia-prime, etc.) and when I would reboot I would get the lightdm screen to authenticate but the dash panel would not appear after logging in. Looking at .xsessions I noticed: init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd respawning too fast, stopped My workaround has been: apt-get purge nvidia* and then to run NVIDIA-Linux-x86_64-331.49.run xrandr shows: Screen 0: minimum 8 x 8, current 3280 x 1080, maximum 16384 x 16384 LVDS-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 382mm x 215mm 1920x1080 60.0*+ 40.0 HDMI-0 connected 1360x768+1920+0 (normal left inverted right x axis y axis) 880mm x 506mm 1360x768 60.0*+ 1920x1080 59.9 60.1 60.0 1440x480 60.1 1280x768 59.9 1280x720 60.0 59.9 1024x768 60.0 800x60060.3 720x48059.9 60.1 640x48059.9 59.9 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) Let me know if any other information would be helpful. I have seen that there are some nvidia related issues that will hopefully be worked out. I just wanted to document my experience in case others have a similar problem. Peace - Anthony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1307236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1421379] Re: CVE-2015-1573
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Invalid ** Changed in: linux (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1421379 Title: CVE-2015-1573 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-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 Lucid: New Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: New Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-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-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: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: 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-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 Utopic: Invalid Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in
[Kernel-packages] [Bug 1435392] rainier (amd64) - tests ran: 147, failed: 2
tests ran: 147, failed: 2; http://kernel.ubuntu.com/testing/rainier__3.2.0-80.116__2015-03-25_17-23-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/1435392 Title: linux: 3.2.0-80.116 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug is for tracking the 3.2.0-80.116 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 23. March 2015 15:38 UTC kernel-stable-Prepare-package-end:Monday, 23. March 2015 22:05 UTC kernel-stable-Promote-to-proposed-start:Monday, 23. March 2015 22:05 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 25. March 2015 12:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 25. March 2015 13:00 UTC kernel-stable-Verification-testing-start:Wednesday, 25. March 2015 13:00 UTC kernel-stable-Certification-testing-start:Wednesday, 25. March 2015 13:00 UTC kernel-stable-Security-signoff-start:Wednesday, 25. March 2015 13:00 UTC kernel-stable-Regression-testing-start:Wednesday, 25. March 2015 13:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1435392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1407952] Re: CVE-2014-9428
** Changed in: linux-lts-trusty (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Trusty) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Utopic) Status: Fix Committed = Fix Released ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1407952 Title: CVE-2014-9428 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: 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-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-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: Fix Released Status in linux-lts-utopic 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-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 Utopic: Fix Released Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: Invalid Status in linux-lts-backport-maverick source package
[Kernel-packages] [Bug 1436511] [NEW] package linux-image-extra-3.13.0-48-generic 3.13.0-48.80 failed to install/upgrade: cannot copy extracted data for './lib/modules/3.13.0-48-generic/kernel/fs/ocfs
Public bug reported: Automatic updater causes a system crash and the system is coming up after a reboot without any usb support. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-48-generic 3.13.0-48.80 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic i686 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: admin 3263 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 25 20:02:01 2015 HibernationDevice: RESUME=UUID=ff214111-c4ef-4dbc-b3ea-32a6502a7262 InstallationDate: Installed on 2014-01-03 (446 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386 (20130820.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: bluechip Computer AG O.E.M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic root=UUID=3f43ba49-87ac-4e4f-8d71-30da73f55815 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-48-generic N/A linux-backports-modules-3.13.0-48-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-08-13 (223 days ago) dmi.bios.date: 03/05/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.name: G41MX 2.0/G41MX-K 2.0 dmi.board.vendor: FOXCONN dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd03/05/2010:svnbluechipComputerAG:pnO.E.M:pvr:rvnFOXCONN:rnG41MX2.0/G41MX-K2.0:rvr1.0:cvnO.E.M:ct3:cvr: dmi.product.name: O.E.M dmi.sys.vendor: bluechip Computer AG ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436511 Title: package linux-image-extra-3.13.0-48-generic 3.13.0-48.80 failed to install/upgrade: cannot copy extracted data for './lib/modules/3.13.0-48-generic/kernel/fs/ocfs2/dlm/ocfs2_dlm.ko' to '/lib/modules/3.13.0-48-generic/kernel/fs/ocfs2/dlm/ocfs2_dlm.ko.dpkg- new': unexpected end of file or stream Status in linux package in Ubuntu: New Bug description: Automatic updater causes a system crash and the system is coming up after a reboot without any usb support. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-48-generic 3.13.0-48.80 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic i686 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: admin 3263 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 25 20:02:01 2015 HibernationDevice: RESUME=UUID=ff214111-c4ef-4dbc-b3ea-32a6502a7262 InstallationDate: Installed on 2014-01-03 (446 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386 (20130820.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: bluechip Computer AG O.E.M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic root=UUID=3f43ba49-87ac-4e4f-8d71-30da73f55815 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-48-generic N/A linux-backports-modules-3.13.0-48-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-08-13 (223 days ago) dmi.bios.date: 03/05/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.name: G41MX 2.0/G41MX-K 2.0 dmi.board.vendor: FOXCONN dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd03/05/2010:svnbluechipComputerAG:pnO.E.M:pvr:rvnFOXCONN:rnG41MX2.0/G41MX-K2.0:rvr1.0:cvnO.E.M:ct3:cvr: dmi.product.name: O.E.M dmi.sys.vendor: bluechip Computer AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1220185] Re: CVE-2013-2888
trusty, vivid are not affected according to http://people.canonical.com /~ubuntu-security/cve/2013/CVE-2013-2888.html ** Changed in: linux (Ubuntu Trusty) Status: Fix Committed = Invalid ** Changed in: linux (Ubuntu Vivid) Status: Fix Committed = Invalid ** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) 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/1220185 Title: CVE-2013-2888 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Won't Fix Status in linux-lts-backport-natty package in Ubuntu: Won't Fix Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic 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 Lucid: Fix Released Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Fix Released Status in linux-flo source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-goldfish source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mako source package in Lucid: Invalid Status in linux-manta source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-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: Won't Fix Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Fix Released Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Won't Fix Status in linux-lts-backport-natty source package in Quantal: Won't Fix Status in linux-lts-backport-maverick source package in Raring: Won't Fix Status in linux-lts-backport-natty source package in Raring: Won't Fix Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Won't Fix Status in linux-lts-backport-natty source package in Trusty: Won't Fix Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-mako source package in
[Kernel-packages] [Bug 912227] Re: CVE-2011-4915
** Changed in: linux (Ubuntu Trusty) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/912227 Title: CVE-2011-4915 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: New Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: New Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Won't Fix Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Won't Fix Status in linux-lts-saucy source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Quantal: Won't Fix Status in linux-armadaxp source package in Quantal: Won't Fix Status in linux-ec2 source package in Quantal: Invalid Status in linux-fsl-imx51 source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux-lts-raring source package in Quantal: Invalid Status in linux-lts-saucy source package in Quantal: Invalid Status in linux-mvl-dove source package in Quantal: Invalid Status in linux-ti-omap4 source package in Quantal: Won't Fix Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux source package in Saucy: Won't Fix Status in linux-armadaxp source package in Saucy: Invalid Status in linux-ec2 source package in Saucy: Invalid Status in linux-fsl-imx51 source package in Saucy: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux-lts-quantal source package in Saucy: Invalid Status in linux-lts-raring source package in Saucy: Invalid Status in linux-lts-saucy source package in Saucy: Invalid Status in linux-mvl-dove source package in Saucy: Invalid Status in linux-ti-omap4 source package in Saucy: Won't Fix Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid Status in linux-lts-backport-oneiric source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Bug description: /proc/interrupts info
[Kernel-packages] [Bug 927885] Re: CVE-2011-2393
** Changed in: linux (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux (Ubuntu Utopic) 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/927885 Title: CVE-2011-2393 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: New Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: New Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Won't Fix Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Won't Fix Status in linux-lts-saucy source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid Status in linux-lts-backport-oneiric source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Invalid Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-lts-backport-maverick source package in Utopic: Invalid Status in linux-lts-backport-natty source package in Utopic: Invalid Status in linux-lts-backport-oneiric source package in Utopic: Invalid Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Bug description: The Neighbor Discovery (ND) protocol implementation in the IPv6 stack in FreeBSD, NetBSD, and possibly other BSD-based operating systems allows remote attackers to cause a denial of service (CPU consumption and device hang) by sending many Router Advertisement (RA) messages with
[Kernel-packages] [Bug 1435898] Re: Can not start (kde5) Desktop: Intel driver Failure
I have tested the 3.18 kernel from the repo and the problem remains. The oops messages are also the same. Since kde has worked with 3.18 in the past this seems very odd. I have tried to reset the settings in kde and see if that helps, but no luck with that. It could be that the kernel oops are only fatal to kde with the latest kde updates. Or it could be that the kernel oops are completly unrelated to my login problem ... Do you have an idea what I could do to localize the problem? ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1435898 Title: Can not start (kde5) Desktop: Intel driver Failure Status in linux package in Ubuntu: Confirmed Bug description: Kubuntu 15.04 start without problems to the display manager sddm. If I enter my password the display is blank for a second and then does kubuntu load forever the desktop environment. Dmesg shows several oopses in the intel driver: invalid max DP link bw val 0, using 1.62Gps and compute-config() on unknown output! I think this problem occurs since the update to 3.19.0-9. Kernel 4.0-rc5 tested with the same problem. --- ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 15.04 HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf InstallationDate: Installed on 2014-12-21 (93 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218) MachineType: LENOVO 20354 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 RelatedPackageVersions: linux-restricted-modules-3.19.0-10-generic N/A linux-backports-modules-3.19.0-10-generic N/A linux-firmware 1.143 Tags: vivid vivid Uname: Linux 3.19.0-10-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70: dmi.product.name: 20354 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1435898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1158970] Re: CVE-2013-2636
** Changed in: linux-ti-omap4 (Ubuntu) Status: Fix Committed = Invalid ** Changed in: linux (Ubuntu) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1158970 Title: CVE-2013-2636 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Invalid Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Invalid Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Invalid Status in linux-lts-backport-oneiric source package in Lucid: Invalid Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Oneiric: Invalid Status in linux-armadaxp source package in Oneiric: Invalid Status in linux-ec2 source package in Oneiric: Invalid Status in linux-fsl-imx51 source package in Oneiric: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux-lts-quantal source package in Oneiric: Invalid Status in linux-mvl-dove source package in Oneiric: Invalid Status in linux-ti-omap4 source package in Oneiric: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Quantal: Invalid Status in linux-armadaxp source package in Quantal: Invalid Status in linux-ec2 source package in Quantal: Invalid Status in linux-fsl-imx51 source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux-mvl-dove source package in Quantal: Invalid Status in linux-ti-omap4 source package in Quantal: Invalid Status in linux source package in Raring: Won't Fix Status in linux-armadaxp source package in Raring: Invalid Status in linux-ec2 source package in Raring: Invalid Status in linux-fsl-imx51 source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-quantal source package in Raring: Invalid Status in linux-mvl-dove source package in Raring: Invalid Status in linux-ti-omap4 source package in Raring: Won't Fix Status in linux source package in Hardy: Invalid Status in linux-armadaxp source package in Hardy: Invalid Status in linux-ec2 source package in Hardy: Invalid Status in linux-fsl-imx51 source package in Hardy: Invalid Status in linux-lts-backport-maverick source package in Hardy: Invalid Status in linux-lts-backport-natty source package in Hardy: Invalid Status in linux-lts-backport-oneiric source package in Hardy: Invalid Status in linux-lts-quantal source package in Hardy: Invalid Status in linux-mvl-dove source package in Hardy: Invalid Status in linux-ti-omap4 source package in Hardy: Invalid Bug description: net/bridge/br_mdb.c in the Linux kernel before 3.8.4 does not initialize certain structures, which allows local users to obtain sensitive information from kernel memory via a crafted application. Break-Fix:
[Kernel-packages] [Bug 1436511] 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/1436511 Title: package linux-image-extra-3.13.0-48-generic 3.13.0-48.80 failed to install/upgrade: cannot copy extracted data for './lib/modules/3.13.0-48-generic/kernel/fs/ocfs2/dlm/ocfs2_dlm.ko' to '/lib/modules/3.13.0-48-generic/kernel/fs/ocfs2/dlm/ocfs2_dlm.ko.dpkg- new': unexpected end of file or stream Status in linux package in Ubuntu: Confirmed Bug description: Automatic updater causes a system crash and the system is coming up after a reboot without any usb support. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-48-generic 3.13.0-48.80 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic i686 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: admin 3263 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 25 20:02:01 2015 HibernationDevice: RESUME=UUID=ff214111-c4ef-4dbc-b3ea-32a6502a7262 InstallationDate: Installed on 2014-01-03 (446 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386 (20130820.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: bluechip Computer AG O.E.M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic root=UUID=3f43ba49-87ac-4e4f-8d71-30da73f55815 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-48-generic N/A linux-backports-modules-3.13.0-48-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-08-13 (223 days ago) dmi.bios.date: 03/05/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.name: G41MX 2.0/G41MX-K 2.0 dmi.board.vendor: FOXCONN dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd03/05/2010:svnbluechipComputerAG:pnO.E.M:pvr:rvnFOXCONN:rnG41MX2.0/G41MX-K2.0:rvr1.0:cvnO.E.M:ct3:cvr: dmi.product.name: O.E.M dmi.sys.vendor: bluechip Computer AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1364516] Re: CVE-2013-2597
** Description changed: Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that leverages /dev/msm_acdb access and provides a large size value in an ioctl argument. + + Break-Fix: - I8230fdb00a7b57d398929e8ab0eb6587476f3db1 ** Description changed: Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that leverages /dev/msm_acdb access and provides a large size value in an ioctl argument. Break-Fix: - I8230fdb00a7b57d398929e8ab0eb6587476f3db1 + Break-Fix: - I4a5b5ca5212bea32b671027d68a66367c5d4c4e7 ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New = Invalid ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New = Invalid ** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux (Ubuntu) Status: New = Invalid ** Changed in: linux (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux (Ubuntu Utopic) 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/1364516 Title: CVE-2013-2597 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: New Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: New Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Invalid Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy
[Kernel-packages] [Bug 912230] Re: CVE-2011-4916
** Changed in: linux (Ubuntu Trusty) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/912230 Title: CVE-2011-4916 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: New Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: New Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Won't Fix Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Won't Fix Status in linux-lts-saucy source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Quantal: Won't Fix Status in linux-armadaxp source package in Quantal: Won't Fix Status in linux-ec2 source package in Quantal: Invalid Status in linux-fsl-imx51 source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux-lts-raring source package in Quantal: Invalid Status in linux-lts-saucy source package in Quantal: Invalid Status in linux-mvl-dove source package in Quantal: Invalid Status in linux-ti-omap4 source package in Quantal: Won't Fix Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux source package in Saucy: Won't Fix Status in linux-armadaxp source package in Saucy: Invalid Status in linux-ec2 source package in Saucy: Invalid Status in linux-fsl-imx51 source package in Saucy: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux-lts-quantal source package in Saucy: Invalid Status in linux-lts-raring source package in Saucy: Invalid Status in linux-lts-saucy source package in Saucy: Invalid Status in linux-mvl-dove source package in Saucy: Invalid Status in linux-ti-omap4 source package in Saucy: Won't Fix Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid Status in linux-lts-backport-oneiric source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Bug description: /dev/pts/, /dev/tty*
[Kernel-packages] [Bug 1416847] Re: kerneloops on suspend from resume
Errr: While the Yoga 2 13 is in no way supported by Lenovo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1416847 Title: kerneloops on suspend from resume Status in linux package in Ubuntu: Incomplete Bug description: Every third or fourth suspend failes on my Lenovo Yoga 2-13, I have to hard reset the notebook. Apportcheckresume informs me about an internel error on next boot, but I cannot find the cause of the problem in the crash report. $ uname -a Linux SandraOrange 3.16.0-29-generic #39-Ubuntu SMP Mon Dec 15 22:27:29 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sandra 2484 F pulseaudio /dev/snd/controlC1: sandra 2484 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c31e5706-71d4-4a32-993f-3b6f2a1bd3bb InstallationDate: Installed on 2015-01-19 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20344 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=3d93d64f-d67f-428f-b719-a51e43e9903f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-29-generic N/A linux-backports-modules-3.16.0-29-generic N/A linux-firmware 1.138.1 Tags: utopic Uname: Linux 3.16.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1416847] Re: kerneloops on suspend from resume
I've tried all kernels from 3.16 to 4.0 and none delivered reliable suspend-resume: lately it seems that 48hrs is indeed the max duration to survive. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1416847 Title: kerneloops on suspend from resume Status in linux package in Ubuntu: Incomplete Bug description: Every third or fourth suspend failes on my Lenovo Yoga 2-13, I have to hard reset the notebook. Apportcheckresume informs me about an internel error on next boot, but I cannot find the cause of the problem in the crash report. $ uname -a Linux SandraOrange 3.16.0-29-generic #39-Ubuntu SMP Mon Dec 15 22:27:29 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sandra 2484 F pulseaudio /dev/snd/controlC1: sandra 2484 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=c31e5706-71d4-4a32-993f-3b6f2a1bd3bb InstallationDate: Installed on 2015-01-19 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20344 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=3d93d64f-d67f-428f-b719-a51e43e9903f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-29-generic N/A linux-backports-modules-3.16.0-29-generic N/A linux-firmware 1.138.1 Tags: utopic Uname: Linux 3.16.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 912231] Re: CVE-2011-4917
** Changed in: linux (Ubuntu Trusty) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/912231 Title: CVE-2011-4917 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: New Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: New Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Won't Fix Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Won't Fix Status in linux-lts-saucy source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Quantal: Won't Fix Status in linux-armadaxp source package in Quantal: Won't Fix Status in linux-ec2 source package in Quantal: Invalid Status in linux-fsl-imx51 source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux-lts-raring source package in Quantal: Invalid Status in linux-lts-saucy source package in Quantal: Invalid Status in linux-mvl-dove source package in Quantal: Invalid Status in linux-ti-omap4 source package in Quantal: Won't Fix Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux source package in Saucy: Won't Fix Status in linux-armadaxp source package in Saucy: Invalid Status in linux-ec2 source package in Saucy: Invalid Status in linux-fsl-imx51 source package in Saucy: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux-lts-quantal source package in Saucy: Invalid Status in linux-lts-raring source package in Saucy: Invalid Status in linux-lts-saucy source package in Saucy: Invalid Status in linux-mvl-dove source package in Saucy: Invalid Status in linux-ti-omap4 source package in Saucy: Won't Fix Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid Status in linux-lts-backport-oneiric source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Bug description: /proc/stat info
[Kernel-packages] [Bug 1364511] Re: CVE-2013-2595
** Changed in: linux (Ubuntu) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Invalid ** Description changed: The device-initialization functionality in the MSM camera driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, enables MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap interface, which allows attackers to gain privileges via a crafted application. + + Break-Fix: - If014e6d152786b508c8e7ee6c53631913cd4cfcf ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New = Invalid ** Changed in: linux (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-backport-maverick (Ubuntu) Status: New = Invalid ** Changed in: linux-lts-backport-maverick (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-backport-maverick (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-backport-maverick (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux-lts-backport-natty (Ubuntu) Status: New = Invalid ** Changed in: linux-lts-backport-natty (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-backport-natty (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-backport-natty (Ubuntu Utopic) 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/1364511 Title: CVE-2013-2595 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: New Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: New Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Invalid Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Invalid Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-lts-backport-maverick source package in Utopic: Invalid Status in linux-lts-backport-natty source package in Utopic: Invalid Status in
