[Kernel-packages] [Bug 1495983] Re: [Hyper-V] kernel panic occurs when installing Ubuntu Server 15.10 x32

[Chris Valean]

Joe, the MAX_PAGE_BUFFER_COUNT I think is automatically computed and not 
directly defined.
Please ensure that you're picking up the original patch and also the patch fix 
for it.

Ovidiu R (orusi) is from my team and his testing is correct.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1495983

Title:
  [Hyper-V] kernel panic occurs when installing Ubuntu Server 15.10 x32

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Incomplete
Status in linux source package in Vivid:
  Incomplete
Status in linux source package in Wily:
  In Progress

Bug description:
  Attempting to install the latest build of Ubuntu Server 15.10 (Wily
  Werewolf) x32 on Hyper-V, after beginning installation a kernel panic
  occurs. The console log from the serial output is attached.

  http://cdimage.ubuntu.com/ubuntu-server/daily/current/

  I tried with the builds from 14th and 15th of September with the same result. 
This bug does not affect x64 builds. 
  Tried to start the installation with different resources with no effect, 
kernel panic always occurs no matter the VM settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495983/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1494431] Re: [Hyper-V] netvsc support to set MTU reservation from guest

[Tim Gardner]

** Changed in: linux (Ubuntu Vivid)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

-- 
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/1494431

Title:
  [Hyper-V] netvsc support to set MTU reservation from guest

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  New
Status in linux source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Please incorporate the following upstream commits (and necessary pre-
  requisites )to the 4.2 kernel into 15.10, 15.04, 14.04 (including
  HWE), and 12.04 (including HWE). Network throughput is improved with
  proper setting of MTU in virtualized environments.

  hv_netvsc: Add support to set MTU reservation from guest side
  When packet encapsulation is in use, the MTU needs to be reduced for
  headroom reservation.
  The existing code takes the updated MTU value only from the host side.
  But vSwitch extensions, such as Open vSwitch, require the flexibility
  to change the MTU to different values from within a guest during the
  lifecycle of a vNIC, when the encapsulation protocol is changed. The
  patch supports this kind of MTU changes.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f9cbce34c34bcc05ea0dd78c8999bfe88b5b6b86

  hv_netvsc: Add close of RNDIS filter into change mtu call
  The current change mtu call only stops tx before removing RNDIS filter.
  In case ringbufer is not empty, the rndis_filter_device_remove() may
  hang on removing the buffers.

  This patch adds close of RNDIS filter before removing it, also a
  gradual waiting loop until the ring is empty. The change_mtu hang
  issue under heavy traffic is solved by this patch.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2de8530ba0c71a2fba02590681af0f3a2a187a9b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494431/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1499609] Re: CVE-2015-5283

[Steve Beattie]

** Changed in: linux (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux (Ubuntu Wily)
   Status: New => Fix Committed

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-mako (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-goldfish (Ubuntu Vivid)
   Status: New => Invalid

** Changed in: linux-flo (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/1499609

Title:
  CVE-2015-5283

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  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:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  Invalid
Status in linux-manta source package in Vivid:
  Invalid
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source 

[Kernel-packages] [Bug 1502032] Re: CVE-2015-7613

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-65.106

---
linux (3.13.0-65.106) trusty; urgency=low

  [ Upstream Kernel Changes ]

  * Initialize msg/shm IPC objects before doing ipc_addid()
- LP: #1502032
- CVE-2015-7613

 -- Luis Henriques   Fri, 02 Oct 2015
10:13:36 +0100

** Changed in: linux (Ubuntu Trusty)
   Status: New => 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/1502032

Title:
  CVE-2015-7613

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  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-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-ec2 

[Kernel-packages] [Bug 1502032] Re: CVE-2015-7613

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.19.0-30.34

---
linux (3.19.0-30.34) vivid; urgency=low

  [ Upstream Kernel Changes ]

  * Initialize msg/shm IPC objects before doing ipc_addid()
- LP: #1502032
- CVE-2015-7613

 -- Luis Henriques   Fri, 02 Oct 2015
10:14:53 +0100

** Changed in: linux (Ubuntu Vivid)
   Status: New => 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/1502032

Title:
  CVE-2015-7613

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  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-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-ec2 source 

[Kernel-packages] [Bug 1502032] Re: CVE-2015-7613

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.19.0-30.34

---
linux (3.19.0-30.34) vivid; urgency=low

  [ Upstream Kernel Changes ]

  * Initialize msg/shm IPC objects before doing ipc_addid()
- LP: #1502032
- CVE-2015-7613

 -- Luis Henriques   Fri, 02 Oct 2015
10:14:53 +0100

-- 
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/1502032

Title:
  CVE-2015-7613

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  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-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-ec2 source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  

[Kernel-packages] [Bug 1502032] Re: CVE-2015-7613

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-65.106

---
linux (3.13.0-65.106) trusty; urgency=low

  [ Upstream Kernel Changes ]

  * Initialize msg/shm IPC objects before doing ipc_addid()
- LP: #1502032
- CVE-2015-7613

 -- Luis Henriques   Fri, 02 Oct 2015
10:13:36 +0100

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => 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/1502032

Title:
  CVE-2015-7613

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  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-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in 

[Kernel-packages] [Bug 1502032] Re: CVE-2015-7613

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-vivid - 3.19.0-30.34~14.04.1

---
linux-lts-vivid (3.19.0-30.34~14.04.1) trusty; urgency=low

  [ Upstream Kernel Changes ]

  * Initialize msg/shm IPC objects before doing ipc_addid()
- LP: #1502032
- CVE-2015-7613

 -- Luis Henriques   Fri, 02 Oct 2015
11:07:55 +0100

** Changed in: linux (Ubuntu Vivid)
   Status: New => 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/1502032

Title:
  CVE-2015-7613

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  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-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  

[Kernel-packages] [Bug 1502032] Re: CVE-2015-7613

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-trusty -
3.13.0-65.106~precise1

---
linux-lts-trusty (3.13.0-65.106~precise1) precise; urgency=low

  [ Upstream Kernel Changes ]

  * Initialize msg/shm IPC objects before doing ipc_addid()
- LP: #1502032
- CVE-2015-7613

 -- Luis Henriques   Fri, 02 Oct 2015
21:54:52 +0100

** Changed in: linux (Ubuntu Trusty)
   Status: New => 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/1502032

Title:
  CVE-2015-7613

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  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-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in 

[Kernel-packages] [Bug 1502032] Re: CVE-2015-7613

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-utopic -
3.16.0-50.67~14.04.1

---
linux-lts-utopic (3.16.0-50.67~14.04.1) trusty; urgency=low

  [ Upstream Kernel Changes ]

  * Initialize msg/shm IPC objects before doing ipc_addid()
- LP: #1502032
- CVE-2015-7613

 -- Luis Henriques   Fri, 02 Oct 2015
10:40:16 +0100

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => 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/1502032

Title:
  CVE-2015-7613

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  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-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source 

[Kernel-packages] [Bug 1502032] Re: CVE-2015-7613

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-utopic -
3.16.0-50.67~14.04.1

---
linux-lts-utopic (3.16.0-50.67~14.04.1) trusty; urgency=low

  [ Upstream Kernel Changes ]

  * Initialize msg/shm IPC objects before doing ipc_addid()
- LP: #1502032
- CVE-2015-7613

 -- Luis Henriques   Fri, 02 Oct 2015
10:40:16 +0100

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: New => 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/1502032

Title:
  CVE-2015-7613

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  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-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source 

[Kernel-packages] [Bug 1503007] [NEW] mouse cursor disappears in Kubuntu with 3.19.0-30-generic kernel

[Alexus]

Public bug reported:

Mouse cursor disappears in Kubuntu with 3.19.0-30-generic kernel.
3.19.0-28 kernel - ok.


CPU: Intel(R) Core(TM) i5-3320M 
GPU: Intel® HD Graphics 4000
Ubuntu 14.04.3 LTS

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: intel kde

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1503007

Title:
  mouse cursor disappears in Kubuntu with 3.19.0-30-generic kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Mouse cursor disappears in Kubuntu with 3.19.0-30-generic kernel.
  3.19.0-28 kernel - ok.

  
  CPU: Intel(R) Core(TM) i5-3320M 
  GPU: Intel® HD Graphics 4000
  Ubuntu 14.04.3 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503007/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1484793] Re: CVE-2015-5156

[Steve Beattie]

** Changed in: linux (Ubuntu Precise)
   Status: New => Fix Committed

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1484793

Title:
  CVE-2015-5156

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Invalid
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-ec2 source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-fsl-imx51 source package in Wily:
  Invalid
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-backport-maverick source package in Wily:
  

[Kernel-packages] [Bug 1501345] Re: linux-image-3.13.0-65-generic 3.13.0-65 breaks Python based Serial communication

[Rob G.]

I also found it first in PySerial, but it affects everything down to the
underlying poll() implementation.  Demo C code is attached (compile with
-Wall -std=gnu99).  Under -63 the poll() call blocks for the 1 second
it's supposed to, a ping is sent once a second, and if you short pins
2-3 of the serial port the ping loops back and the code starts running
I/O bound; pinging as fast as it can until you remove the screwdriver.

Under -65 poll() returns immediately even with nothing to read and the
console I/O is the only thing restraining the process.

In short, this is a driver bug, not a Python specific thing, and most
likely breaks any code that relies on select, poll, or epoll for serial
I/O.

** Attachment added: "Code demonstrating poll() problem in 3.13.0-65-generic"
   
https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345/+attachment/4485041/+files/serialpoll.c

-- 
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/1501345

Title:
  linux-image-3.13.0-65-generic 3.13.0-65 breaks Python based Serial
  communication

Status in linux-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Today after updating to the linux-image-3.13.0-65-generic 3.13.0-65
  Kernel on Lubuntu 14.04.3 LTS two different programs that rely on
  PySerial quit working. miniterm.py and my ROS (Robot Operating System)
  based Python node quit working.

  When rebooted and selected 3.13.0-63-generic via GRUB everything
  worked again.

  Here are the steps to create the issue with miniterm.py, note that you
  need something connected via a USB to Serial adapter for this to work.
  I am working with a Parallax Activity Board, but an Arduino should
  also exhibit the same behavior.

  sudo apt install linux-image-3.13.0-65-generic
  sudo apt install linux-image-extra-3.13.0-65-generic
  reboot

   $ miniterm.py /dev/ttyUSB0 115200
  --- Miniterm on /dev/ttyUSB0: 115200,8,N,1 ---
  --- Quit: Ctrl+]  |  Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---

  --- exit ---
  Exception in thread Thread-1:
  Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
  self.run()
File "/usr/lib/python2.7/threading.py", line 763, in run
  self.__target(*self.__args, **self.__kwargs)
File "/usr/bin/miniterm.py", line 220, in reader
  data = character(self.serial.read(1))
File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 460, in 
read
  raise SerialException('device reports readiness to read but returned no 
data (device disconnected?)')
  SerialException: device reports readiness to read but returned no data 
(device disconnected?)

  Reverting to the 3.13.0-63 kernel allows miniterm.py and other Python
  Serial based programs to work normally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1494431] Re: [Hyper-V] netvsc support to set MTU reservation from guest

[Tim Gardner]

The backport for 3.13 is too complex. It appears to depends on commit
5b54dac856cb5bd6f33f4159012773e4a33704f7 ('hyperv: Add support for
virtual Receive Side Scaling (vRSS)') which is well beyond the scope of
what can be SRU'd.

** Changed in: linux (Ubuntu Trusty)
   Status: Triaged => Won't Fix

** Changed in: linux-lts-trusty (Ubuntu)
   Status: New => Won't Fix

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Won't Fix

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Importance: Undecided => Wishlist

-- 
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/1494431

Title:
  [Hyper-V] netvsc support to set MTU reservation from guest

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  Won't Fix
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Won't Fix
Status in linux-lts-utopic source package in Precise:
  In Progress
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Please incorporate the following upstream commits (and necessary pre-
  requisites )to the 4.2 kernel into 15.10, 15.04, 14.04 (including
  HWE), and 12.04 (including HWE). Network throughput is improved with
  proper setting of MTU in virtualized environments.

  hv_netvsc: Add support to set MTU reservation from guest side
  When packet encapsulation is in use, the MTU needs to be reduced for
  headroom reservation.
  The existing code takes the updated MTU value only from the host side.
  But vSwitch extensions, such as Open vSwitch, require the flexibility
  to change the MTU to different values from within a guest during the
  lifecycle of a vNIC, when the encapsulation protocol is changed. The
  patch supports this kind of MTU changes.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f9cbce34c34bcc05ea0dd78c8999bfe88b5b6b86

  hv_netvsc: Add close of RNDIS filter into change mtu call
  The current change mtu call only stops tx before removing RNDIS filter.
  In case ringbufer is not empty, the rndis_filter_device_remove() may
  hang on removing the buffers.

  This patch adds close of RNDIS filter before removing it, also a
  gradual waiting loop until the ring is empty. The change_mtu hang
  issue under heavy traffic is solved by this patch.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2de8530ba0c71a2fba02590681af0f3a2a187a9b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494431/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

[Brian Murray]

** Description changed:

  I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
- After upgrading the boot time is longer (what is negligible) but the more 
sever error is, that I cannot enter my passphrase when I see the crypt dialog.
+ After upgrading the boot time is longer (what is negligible) but the more 
severe error is, that I cannot enter my passphrase when I see the crypt dialog.
  I just see the dialog to enter my passphrase, but when I try to enter it, 
nothing appears in the textfield. I tried with the builtin laptop keyboard but 
also with an external USB keyboard.
  
  I thought about supplying more information, but things like the syslog
  are not helping apparently (I was not able to boot until the syslog
  would capture information...). If you need anything I can provide, I
  gladly help.
  
  [Test case]
  1. On an affected system boot into kernel 3.19.0-30
  
  [Solution]
  The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a 
real solution).
  
  PS.: Bugs like the following are either not applicable or the solution is not 
working for me:
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194

** Changed in: cryptsetup (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1500751

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

Status in cryptsetup package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
  After upgrading the boot time is longer (what is negligible) but the more 
severe error is, that I cannot enter my passphrase when I see the crypt dialog.
  I just see the dialog to enter my passphrase, but when I try to enter it, 
nothing appears in the textfield. I tried with the builtin laptop keyboard but 
also with an external USB keyboard.

  I thought about supplying more information, but things like the syslog
  are not helping apparently (I was not able to boot until the syslog
  would capture information...). If you need anything I can provide, I
  gladly help.

  [Test case]
  1. On an affected system boot into kernel 3.19.0-30

  [Solution]
  The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a 
real solution).

  PS.: Bugs like the following are either not applicable or the solution is not 
working for me:
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

[Scott Moser]

** 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/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1441108] Re: CVE-2015-2925

[Steve Beattie]

** Description changed:

  [It is possible to escape from bind mounts]
  
- Break-Fix: - -
+ Break-Fix: - cde93be45a8a90d8c264c776fab63487b5038a65
+ Break-Fix: - 397d425dc26da728396e66d392d5dcb8dac30c37

-- 
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/1441108

Title:
  CVE-2015-2925

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-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  New
Status in linux-armadaxp source package in Wily:
  Invalid

[Kernel-packages] [Bug 1502032] Re: CVE-2015-7613

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-vivid - 3.19.0-30.34~14.04.1

---
linux-lts-vivid (3.19.0-30.34~14.04.1) trusty; urgency=low

  [ Upstream Kernel Changes ]

  * Initialize msg/shm IPC objects before doing ipc_addid()
- LP: #1502032
- CVE-2015-7613

 -- Luis Henriques   Fri, 02 Oct 2015
11:07:55 +0100

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: New => 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/1502032

Title:
  CVE-2015-7613

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  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-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package 

[Kernel-packages] [Bug 1499612] Re: CVE-2015-7312

[Steve Beattie]

** Changed in: linux (Ubuntu Vivid)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1499612

Title:
  CVE-2015-7312

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-ec2 source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-fsl-imx51 source package in Wily:
  Invalid
Status in linux-goldfish source package in 

[Kernel-packages] [Bug 1494431] Re: [Hyper-V] netvsc support to set MTU reservation from guest

[Tim Gardner]

** Also affects: linux-lts-utopic (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-lts-utopic (Ubuntu)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Status: New => In Progress

** Changed in: linux-lts-utopic (Ubuntu Precise)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

-- 
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/1494431

Title:
  [Hyper-V] netvsc support to set MTU reservation from guest

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  New
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  In Progress
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Please incorporate the following upstream commits (and necessary pre-
  requisites )to the 4.2 kernel into 15.10, 15.04, 14.04 (including
  HWE), and 12.04 (including HWE). Network throughput is improved with
  proper setting of MTU in virtualized environments.

  hv_netvsc: Add support to set MTU reservation from guest side
  When packet encapsulation is in use, the MTU needs to be reduced for
  headroom reservation.
  The existing code takes the updated MTU value only from the host side.
  But vSwitch extensions, such as Open vSwitch, require the flexibility
  to change the MTU to different values from within a guest during the
  lifecycle of a vNIC, when the encapsulation protocol is changed. The
  patch supports this kind of MTU changes.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f9cbce34c34bcc05ea0dd78c8999bfe88b5b6b86

  hv_netvsc: Add close of RNDIS filter into change mtu call
  The current change mtu call only stops tx before removing RNDIS filter.
  In case ringbufer is not empty, the rndis_filter_device_remove() may
  hang on removing the buffers.

  This patch adds close of RNDIS filter before removing it, also a
  gradual waiting loop until the ring is empty. The change_mtu hang
  issue under heavy traffic is solved by this patch.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2de8530ba0c71a2fba02590681af0f3a2a187a9b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494431/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502982] Re: STCOP810:Firestone: frsfp6 EEH on Bluefin does not recover with Ubuntu

[Luciano Chavez]

** Package changed: ubuntu => linux (Ubuntu)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502982

Title:
  STCOP810:Firestone: frsfp6 EEH on Bluefin does not recover with Ubuntu

Status in linux package in Ubuntu:
  New

Bug description:
  Problem:
  ==
  Test Case Execution Record:

  95613: EEH_Firestone_Ubuntu 14.04.03_Bluefin_Standalone on frsfp6

  Error Injection Method: err_injct_inboundA

  Step 1. Start HTX (I used mdt.hdbuster & only ran htx on bluefin disks)
  Step 2. Inject EEH error

  bluefin is in slot P1-C4 (PCI0004)

   echo 0x8000 >
  /sys/kernel/debug/powerpc/PCI0004/err_injct_inboundA; sleep 1; echo
  0x0 > /sys/kernel/debug/powerpc/PCI0004/err_injct_inboundA

  Expected Result: Adapter/SAN disks to recover and htx still run

  Actual Result:  Adapter did not recover... continuous EEH errors until
  limit of 6 is reached in 1 hour

  There're two patches: one for skiboot firmware and another patch,
  which has been in upstream, was missed in ubuntu distro (at least
  15.04). The skiboot patch has been merged to upstream.

  c7192a4 PHB3: Fix wrong PE number in error injection (skiboot)
  2aa5cf9 powerpc/eeh: Fix missed PE#0 on P7IOC (linux)

  If I'm correct, I think this bug needs to be mirrored so that the
  Linux patch (commit 2aa5cf9) can be backported to ubuntu distro. With
  the patch backported to ubuntu 15.04, EEH works fine on Broadcom
  adapter (not exactly the one where the bug was reported initially):

  root@fstn2-p1:/# dmesg | grep EEH
  [0.216919] EEH: PowerNV platform initialized
  [0.570606] EEH: devices created
  [1.302482] EEH: PCI Enhanced I/O Error Handling Enabled
  [   90.566761] EEH: PHB location: Slot1
  [   90.567503] EEH: Frozen PHB#4-PE#0 detected
  [   90.567673] EEH: PE location: Slot1, PHB location: Slot1
  [   90.567930] EEH: Detected PCI bus error on PHB#4-PE#0
  [   90.567935] EEH: This PCI device has failed 1 times in the last hour
  [   90.567937] EEH: Notify device drivers to shutdown
  [   90.567985] EEH: Collect temporary log
  [   90.568971] EEH: Reset without hotplug activity
  [   94.585540] EEH: Notify device drivers the completion of reset
  [   94.585934] EEH: Notify device driver to resume

  

  The story about this bug is: Without commit 2aa5cf9 ("powerpc/eeh: Fix
  missed PE#0 on P7IOC"). PE#0 is regarded as invalid one. When kernel
  sees the frozen PE#0, the frozen state is cleared and dump the PHB
  diag-data, then try to recover it. When resetting the PE, the driver,
  which wasn't stopped by error_detected() completely, access the MMIO
  space and just causes another (recursive) EEH error. Eventually, the
  EEH recovery failed. During the PE reset, the I/O path for the PE
  should be frozen and MMIO access during the period should be dropped
  to avoid recursive EEH error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502982/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1503005] [NEW] linux: 3.19.0-31.35 -proposed tracker

[Brad Figg]

Public bug reported:

This bug is for tracking the 3.19.0-31.35 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, 05. October 2015 18:56 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Monday, 05. October 2015 18:56 UTC

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Platform QA Team (canonical-platform-qa)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux (Ubuntu Vivid)
 Importance: Medium
 Status: New


** Tags: block-proposed-vivid kernel-release-tracking-bug vivid

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-vivid

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Tags added: vivid

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed

[Kernel-packages] [Bug 1496073] Re: Request cherry-pick of upstream kernel patch which caps SECCOMP_RET_ERRNO to MAX_ERRNO

[Brad Figg]

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Vivid)
   Status: New => Fix Committed

** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1496073

Title:
  Request cherry-pick of upstream kernel patch which caps
  SECCOMP_RET_ERRNO to MAX_ERRNO

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  The seccomp regression tests are failing due to SRU kernels not having
  the relevant commit:

  Author: Kees Cook 
  Date:   Tue Feb 17 13:48:00 2015 -0800

  seccomp: cap SECCOMP_RET_ERRNO data to MAX_ERRNO

  The value resulting from the SECCOMP_RET_DATA mask could exceed MAX_ERRNO
  when setting errno during a SECCOMP_RET_ERRNO filter action.  This makes
  sure we have a reliable value being set, so that an invalid errno will not
  be ignored by userspace.

  Signed-off-by: Kees Cook 
  Reported-by: Dmitry V. Levin 
  Cc: Andy Lutomirski 
  Cc: Will Drewry 
  Signed-off-by: Andrew Morton 
  Signed-off-by: Linus Torvalds 

  SRU Justification

  Impact:
  Upstream regression tests are reporting errors.

  Test Case:
  Run the upstream regression tests and verify they are passing
  cleanly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496073/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1499606] Re: CVE-2015-5257

[Steve Beattie]

** Changed in: linux (Ubuntu Wily)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1499606

Title:
  CVE-2015-5257

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-ec2 source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-fsl-imx51 source package in Wily:
  Invalid
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-backport-maverick source package in Wily:
  New
Status in linux-lts-backport-natty source package in Wily:
  New
Status in linux-lts-quantal source package in 

[Kernel-packages] [Bug 1502032] Re: CVE-2015-7613

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-trusty -
3.13.0-65.106~precise1

---
linux-lts-trusty (3.13.0-65.106~precise1) precise; urgency=low

  [ Upstream Kernel Changes ]

  * Initialize msg/shm IPC objects before doing ipc_addid()
- LP: #1502032
- CVE-2015-7613

 -- Luis Henriques   Fri, 02 Oct 2015
21:54:52 +0100

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Fix Released

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => 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/1502032

Title:
  CVE-2015-7613

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  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-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid

[Kernel-packages] [Bug 1502982] [NEW] STCOP810:Firestone: frsfp6 EEH on Bluefin does not recover with Ubuntu

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Problem:
==
Test Case Execution Record:

95613: EEH_Firestone_Ubuntu 14.04.03_Bluefin_Standalone on frsfp6

Error Injection Method: err_injct_inboundA

Step 1. Start HTX (I used mdt.hdbuster & only ran htx on bluefin disks)
Step 2. Inject EEH error

bluefin is in slot P1-C4 (PCI0004)

 echo 0x8000 >
/sys/kernel/debug/powerpc/PCI0004/err_injct_inboundA; sleep 1; echo 0x0
> /sys/kernel/debug/powerpc/PCI0004/err_injct_inboundA

Expected Result: Adapter/SAN disks to recover and htx still run

Actual Result:  Adapter did not recover... continuous EEH errors until
limit of 6 is reached in 1 hour

There're two patches: one for skiboot firmware and another patch, which
has been in upstream, was missed in ubuntu distro (at least 15.04). The
skiboot patch has been merged to upstream.

c7192a4 PHB3: Fix wrong PE number in error injection (skiboot)
2aa5cf9 powerpc/eeh: Fix missed PE#0 on P7IOC (linux)

If I'm correct, I think this bug needs to be mirrored so that the Linux
patch (commit 2aa5cf9) can be backported to ubuntu distro. With the
patch backported to ubuntu 15.04, EEH works fine on Broadcom adapter
(not exactly the one where the bug was reported initially):

root@fstn2-p1:/# dmesg | grep EEH
[0.216919] EEH: PowerNV platform initialized
[0.570606] EEH: devices created
[1.302482] EEH: PCI Enhanced I/O Error Handling Enabled
[   90.566761] EEH: PHB location: Slot1
[   90.567503] EEH: Frozen PHB#4-PE#0 detected
[   90.567673] EEH: PE location: Slot1, PHB location: Slot1
[   90.567930] EEH: Detected PCI bus error on PHB#4-PE#0
[   90.567935] EEH: This PCI device has failed 1 times in the last hour
[   90.567937] EEH: Notify device drivers to shutdown
[   90.567985] EEH: Collect temporary log
[   90.568971] EEH: Reset without hotplug activity
[   94.585540] EEH: Notify device drivers the completion of reset
[   94.585934] EEH: Notify device driver to resume



The story about this bug is: Without commit 2aa5cf9 ("powerpc/eeh: Fix
missed PE#0 on P7IOC"). PE#0 is regarded as invalid one. When kernel
sees the frozen PE#0, the frozen state is cleared and dump the PHB diag-
data, then try to recover it. When resetting the PE, the driver, which
wasn't stopped by error_detected() completely, access the MMIO space and
just causes another (recursive) EEH error. Eventually, the EEH recovery
failed. During the PE reset, the I/O path for the PE should be frozen
and MMIO access during the period should be dropped to avoid recursive
EEH error.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-131243 severity-high 
targetmilestone-inin14043
-- 
STCOP810:Firestone: frsfp6 EEH on Bluefin does not recover with Ubuntu
https://bugs.launchpad.net/bugs/1502982
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 1448472] Re: I can not connect phone with bluetooth with Lexus 400 RX 400H

[Launchpad Bug Tracker]

[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1448472

Title:
  I can not connect phone with bluetooth with Lexus 400 RX 400H

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Both are detected each other but the connection is not done so I
  cantón not registre the phone un the car

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1448472/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1483494] Re: WIFI not working on Acer Aspire E5-573

[Sandeep Singh]

Thank you christoper for providing a latest iso tested image. I burned a
ISO and tried to check on my laptop.

This iso has a bug. After installation, when i restarted my laptop for a
very first time. I got a strange error and i couldn't able to use
anything.  Screenshot attached.

So many bugs. Now mouse pad is not even detecting. I don't think this is
ever gonna resolve. I bought a new laptop just for linux but now i have
no choice but to use windows(which i always hated).

Advice to those who love linux, don't ever purchase laptop with latest
hardware.


** Attachment added: "Screenshot from 2015-09-29 18-59-31.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483494/+attachment/4485342/+files/Screenshot%20from%202015-09-29%2018-59-31.jpg

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1483494

Title:
  WIFI not working on Acer Aspire E5-573

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have installed Linux Mint 17.2 Mate(64bit) on my new Acer Aspire
  E5-573.  I am having a problem with wifi. Wireless connection is not
  working, only wired connection is working.

  I have a Qualcomm Atheros Device 0042 Wifi card.

  Here is a output.

  splinter@splinter ~ $ inxi -Fxz
  System:Host: splinter Kernel: 3.16.0-38-generic x86_64 (64 bit, gcc: 
4.8.2) Desktop: N/A Distro: Linux Mint 17.2 Rafaela
  Machine:   System: Acer product: Aspire E5-573 version: V3.72
 Mobo: Acer model: ZORO_BH version: Type2 - A01 Board Version Bios: 
Insyde version: V1.11 date: 04/20/2015
  CPU:   Dual core Intel Core i3-4005U CPU (-HT-MCP-) cache: 3072 KB flags: 
(lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 6784.64 
 Clock Speeds: 1: 1700.00 MHz 2: 1700.00 MHz 3: 1700.066 MHz 4: 
1699.867 MHz
  Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller bus-ID: 
00:02.0 
 X.Org: 1.15.1 drivers: intel (unloaded: fbdev,vesa) Resolution: 
1366x768@60.0hz 
 GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa 
10.1.3 Direct Rendering: Yes
  Audio: Card-1: Intel Lynx Point-LP HD Audio Controller driver: 
snd_hda_intel bus-ID: 00:1b.0 
 Card-2: Intel Haswell-ULT HD Audio Controller driver: 
snd_hda_intel bus-ID: 00:03.0 
 Sound: Advanced Linux Sound Architecture ver: k3.16.0-38-generic
  Network:   Card-1: Qualcomm Atheros Device 0042 bus-ID: 03:00.0
 IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A
 Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller 
 driver: r8169 ver: 2.3LK-NAPI port: 3000 bus-ID: 02:00.0
 IF: eth0 state: down mac: 
  Drives:HDD Total Size: 1032.1GB (0.5% used) 1: id: /dev/sda model: 
WDC_WD10JPVX size: 1000.2GB 
 2: id: /dev/sdb model: SD/MMC size: 31.9GB 
  Partition: ID: / size: 230G used: 4.9G (3%) fs: ext4 ID: swap-1 size: 8.19GB 
used: 0.00GB (0%) fs: swap 
  RAID:  No RAID devices detected - /proc/mdstat and md_mod kernel raid 
module present
  Sensors:   System Temperatures: cpu: 41.0C mobo: N/A 
 Fan Speeds (in rpm): cpu: N/A 
  Info:  Processes: 189 Uptime: 19 min Memory: 336.0/3879.3MB Runlevel: 2 
Gcc sys: 4.8.4 
 Client: Shell (bash 4.3.11) inxi: 1.9.17

  
  splinter@splinter ~ $ sudo rfkill list all
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: acer-wireless: Wireless LAN
Soft blocked: no
Hard blocked: no

  Please help.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  splinter   1891 F pulseaudio
   /dev/snd/controlC0:  splinter   1891 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0483444a-0d9a-4215-b36b-4aee75fd9ec0
  InstallationDate: Installed on 2015-08-10 (0 days ago)
  InstallationMedia: Linux Mint 17.2 "Rafaela" - Release amd64 20150627
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Acer Aspire E5-573
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic 
root=UUID=ce5d744c-0341-42b5-af57-4da5721790d8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-38-generic N/A
   linux-backports-modules-3.16.0-38-generic  N/A
   linux-firmware 1.127.12
  Tags:  rafaela
  Uname: Linux 3.16.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board 

[Kernel-packages] [Bug 1503005] Re: linux: 3.19.0-31.35 -proposed tracker

[Brad Figg]

All builds are complete, packages in this bug can be copied to
-proposed.

Backport packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-lts-vivid (14.04.1) - bug 1503127

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.19.0-31.35 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, 05. October 2015 18:56 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Monday, 05. October 2015 18:56 UTC
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 05:02 UTC
+ kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 05:02 UTC
+ kernel-stable-phase-changed:Tuesday, 06. October 2015 05:02 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/1503005

Title:
  linux: 3.19.0-31.35 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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 package in Ubuntu:
  New
Status in linux source package in Vivid:
  New

Bug description:
  This bug is for tracking the 3.19.0-31.35 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, 05. October 2015 18:56 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-phase-changed:Tuesday, 06. October 2015 05:02 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1503005/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1448472] Re: I can not connect phone with bluetooth with Lexus 400 RX 400H

[Simon Fels]

** Tags added: after-bluez5 bluetooth

-- 
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/1448472

Title:
  I can not connect phone with bluetooth with Lexus 400 RX 400H

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Both are detected each other but the connection is not done so I
  cantón not registre the phone un the car

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1448472/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1482002] Re: package linux-image-3.19.0-25-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1482002

Title:
  package linux-image-3.19.0-25-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  Failed during ubuntu software updater session

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-25-generic (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  steve  1707 F pulseaudio
   /dev/snd/controlC0:  steve  1707 F pulseaudio
   /dev/snd/seq:timidity780 F timidity
  Date: Wed Aug  5 18:28:31 2015
  DuplicateSignature: package:linux-image-3.19.0-25-generic:(not 
installed):subprocess new pre-installation script returned error exit status 128
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=8a710210-dd15-48b7-9f67-8f1cdce60d2b
  InstallationDate: Installed on 2014-06-14 (418 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: MotherBoard By ZOTAC MotherBoard H77ITX-B-E
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic 
root=UUID=e861cb6b-01f5-4b5a-a9b5-1f53f6e81acd ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-22ubuntu1.1
  SourcePackage: linux
  Title: package linux-image-3.19.0-25-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (102 days ago)
  dmi.bios.date: 04/06/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A230P006
  dmi.board.asset.tag: NA
  dmi.board.name: H77ITX-B-E
  dmi.board.vendor: ZOTAC
  dmi.board.version: 01
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA230P006:bd04/06/2012:svnMotherBoardByZOTAC:pnMotherBoardH77ITX-B-E:pvrMotherBoard01:rvnZOTAC:rnH77ITX-B-E:rvr01:cvnNA:ct3:cvrNA:
  dmi.product.name: MotherBoard H77ITX-B-E
  dmi.product.version: MotherBoard 01
  dmi.sys.vendor: MotherBoard By ZOTAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482002/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1503127] [NEW] linux-lts-vivid: 3.19.0-31.35~14.04.1 -proposed tracker

[Brad Figg]

Public bug reported:

This bug is for tracking the 3.19.0-31.35~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, 06. October 2015 05:00 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Tuesday, 06. October 2015 05:00 UTC
kernel-stable-master-bug:1503005

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Platform QA Team (canonical-platform-qa)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-lts-vivid (Ubuntu Trusty)
 Importance: Medium
 Status: New


** Tags: block-proposed-trusty kernel-release-tracking-bug trusty

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-trusty

** Also affects: linux-lts-vivid (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Tags added: trusty

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: 

[Kernel-packages] [Bug 1503016] [NEW] linux: 4.2.0-15.17 -proposed tracker

[Tim Gardner]

Public bug reported:

This bug is for tracking the 4.2.0-15.17 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-Prepare-package-start:Monday, 05. October 2015 19:36 UTC
kernel-phase-changed:Monday, 05. October 2015 19:36 UTC
kernel-phase:Prepare

** Affects: kernel-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Wily)
 Importance: Undecided
 Status: Invalid


** Tags: block-proposed kernel-release-tracking-bug wily

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed

** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Tags added: wily

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: linux (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1503016

Title:
  linux: 4.2.0-15.17 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source 

[Kernel-packages] [Bug 1503007] Re: mouse cursor disappears in Kubuntu with 3.19.0-30-generic kernel

[Alexus]

# apport-collect 1503007
ERROR: Could not import module, is a package upgrade in progress?  Error: No 
module named PyKDE4.kdecore

# dpkg -l | grep pykde
ii  python3-pykde4  4:4.13.3-0ubuntu0.1 
amd64Python 3 bindings for the KDE Development Platform
ii  python3-pykde4-dbg  4:4.13.3-0ubuntu0.1 
amd64debugging symbols for PyKDE bindings for Python 3


** 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/1503007

Title:
  mouse cursor disappears in Kubuntu with 3.19.0-30-generic kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mouse cursor disappears in Kubuntu with 3.19.0-30-generic kernel.
  3.19.0-28 kernel - ok.

  
  CPU: Intel(R) Core(TM) i5-3320M 
  GPU: Intel® HD Graphics 4000
  Ubuntu 14.04.3 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503007/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

[Forest]

The Acer Aspire E5-571-53S1 (E 15) is also affected.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1500751

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

Status in cryptsetup package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
  After upgrading the boot time is longer (what is negligible) but the more 
severe error is, that I cannot enter my passphrase when I see the crypt dialog.
  I just see the dialog to enter my passphrase, but when I try to enter it, 
nothing appears in the textfield. I tried with the builtin laptop keyboard but 
also with an external USB keyboard.

  I thought about supplying more information, but things like the syslog
  are not helping apparently (I was not able to boot until the syslog
  would capture information...). If you need anything I can provide, I
  gladly help.

  [Test case]
  1. On an affected system boot into kernel 3.19.0-30

  [Solution]
  The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a 
real solution).

  PS.: Bugs like the following are either not applicable or the solution is not 
working for me:
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

[Scott Moser]

marked as confirmed.
I collected info running trusty kernel as current wily wont boot.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1503016] Re: linux: 4.2.0-15.17 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 4.2.0-15.17 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Monday, 05. October 2015 19:36 UTC
  kernel-phase-changed:Monday, 05. October 2015 19:36 UTC
  kernel-phase:Prepare
+ kernel-stable-Promote-to-proposed-end:Monday, 05. October 2015 20: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/1503016

Title:
  linux: 4.2.0-15.17 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Invalid

Bug description:
  This bug is for tracking the 4.2.0-15.17 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Monday, 05. October 2015 19:36 UTC
  kernel-phase-changed:Monday, 05. October 2015 19:36 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Monday, 05. October 2015 20:00 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1503016/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1503021] [NEW] linux: 3.13.0-66.107 -proposed tracker

[Brad Figg]

Public bug reported:

This bug is for tracking the 3.13.0-66.107 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, 05. October 2015 19:56 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Monday, 05. October 2015 19:56 UTC

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Platform QA Team (canonical-platform-qa)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Medium
 Status: New


** Tags: block-proposed-trusty kernel-release-tracking-bug trusty

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-trusty

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Tags added: trusty

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: 

[Kernel-packages] [Bug 1503007] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1503007

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/1503007

Title:
  mouse cursor disappears in Kubuntu with 3.19.0-30-generic kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Mouse cursor disappears in Kubuntu with 3.19.0-30-generic kernel.
  3.19.0-28 kernel - ok.

  
  CPU: Intel(R) Core(TM) i5-3320M 
  GPU: Intel® HD Graphics 4000
  Ubuntu 14.04.3 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503007/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] UdevLog.txt

[Scott Moser]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1502946/+attachment/4485087/+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/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] ProcModules.txt

[Scott Moser]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1502946/+attachment/4485085/+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/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bluez (Ubuntu)
   Status: New => Confirmed

-- 
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/1488170

Title:
  Bluetooth initiated after quitting airplane mode

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in urfkill package in Ubuntu:
  Confirmed

Bug description:
  This happens despite bluetooth not being enabled when entering
  airplane mode.

  On Aquaris E5 OTA-5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] BootDmesg.txt

[Scott Moser]

apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1502946/+attachment/4485081/+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/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502982] Re: STCOP810:Firestone: frsfp6 EEH on Bluefin does not recover with Ubuntu

[Tim Gardner]

** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
   Status: New

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Vivid)
   Status: New => Fix Released

** Changed in: linux (Ubuntu Vivid)
   Status: Fix Released => In Progress

** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux (Ubuntu Wily)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502982

Title:
  STCOP810:Firestone: frsfp6 EEH on Bluefin does not recover with Ubuntu

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Problem:
  ==
  Test Case Execution Record:

  95613: EEH_Firestone_Ubuntu 14.04.03_Bluefin_Standalone on frsfp6

  Error Injection Method: err_injct_inboundA

  Step 1. Start HTX (I used mdt.hdbuster & only ran htx on bluefin disks)
  Step 2. Inject EEH error

  bluefin is in slot P1-C4 (PCI0004)

   echo 0x8000 >
  /sys/kernel/debug/powerpc/PCI0004/err_injct_inboundA; sleep 1; echo
  0x0 > /sys/kernel/debug/powerpc/PCI0004/err_injct_inboundA

  Expected Result: Adapter/SAN disks to recover and htx still run

  Actual Result:  Adapter did not recover... continuous EEH errors until
  limit of 6 is reached in 1 hour

  There're two patches: one for skiboot firmware and another patch,
  which has been in upstream, was missed in ubuntu distro (at least
  15.04). The skiboot patch has been merged to upstream.

  c7192a4 PHB3: Fix wrong PE number in error injection (skiboot)
  2aa5cf9 powerpc/eeh: Fix missed PE#0 on P7IOC (linux)

  If I'm correct, I think this bug needs to be mirrored so that the
  Linux patch (commit 2aa5cf9) can be backported to ubuntu distro. With
  the patch backported to ubuntu 15.04, EEH works fine on Broadcom
  adapter (not exactly the one where the bug was reported initially):

  root@fstn2-p1:/# dmesg | grep EEH
  [0.216919] EEH: PowerNV platform initialized
  [0.570606] EEH: devices created
  [1.302482] EEH: PCI Enhanced I/O Error Handling Enabled
  [   90.566761] EEH: PHB location: Slot1
  [   90.567503] EEH: Frozen PHB#4-PE#0 detected
  [   90.567673] EEH: PE location: Slot1, PHB location: Slot1
  [   90.567930] EEH: Detected PCI bus error on PHB#4-PE#0
  [   90.567935] EEH: This PCI device has failed 1 times in the last hour
  [   90.567937] EEH: Notify device drivers to shutdown
  [   90.567985] EEH: Collect temporary log
  [   90.568971] EEH: Reset without hotplug activity
  [   94.585540] EEH: Notify device drivers the completion of reset
  [   94.585934] EEH: Notify device driver to resume

  

  The story about this bug is: Without commit 2aa5cf9 ("powerpc/eeh: Fix
  missed PE#0 on P7IOC"). PE#0 is regarded as invalid one. When kernel
  sees the frozen PE#0, the frozen state is cleared and dump the PHB
  diag-data, then try to recover it. When resetting the PE, the driver,
  which wasn't stopped by error_detected() completely, access the MMIO
  space and just causes another (recursive) EEH error. Eventually, the
  EEH recovery failed. During the PE reset, the I/O path for the PE
  should be frozen and MMIO access during the period should be dropped
  to avoid recursive EEH error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502982/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] WifiSyslog.txt

[Scott Moser]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1502946/+attachment/4485088/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] Lspci.txt

[Scott Moser]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1502946/+attachment/4485082/+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/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] ProcCpuinfo.txt

[Scott Moser]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1502946/+attachment/4485083/+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/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

[Scott Moser]

apport information

** Tags added: apport-collected trusty uec-images

** Description changed:

  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.
  
  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
+ --- 
+ AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.14.1-0ubuntu3.15
+ Architecture: arm64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ CRDA: Error: [Errno 2] No such file or directory
+ CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
+ DistroRelease: Ubuntu 14.04
+ IwConfig:
+  lono wireless extensions.
+  
+  eth1  no wireless extensions.
+  
+  eth0  no wireless extensions.
+ Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=screen
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  
+ ProcKernelCmdLine: console=ttyS0,9600n8r ro
+ ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-63-generic N/A
+  linux-backports-modules-3.13.0-63-generic  N/A
+  linux-firmware 1.127.15
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  trusty uec-images
+ Uname: Linux 3.13.0-63-generic aarch64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
+ _MarkForUpload: True

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1502946/+attachment/4485080/+files/AudioDevicesInUse.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/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
 

[Kernel-packages] [Bug 1502946] ProcInterrupts.txt

[Scott Moser]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1502946/+attachment/4485084/+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/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: urfkill (Ubuntu)
   Status: New => Confirmed

-- 
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/1488170

Title:
  Bluetooth initiated after quitting airplane mode

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in urfkill package in Ubuntu:
  Confirmed

Bug description:
  This happens despite bluetooth not being enabled when entering
  airplane mode.

  On Aquaris E5 OTA-5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] UdevDb.txt

[Scott Moser]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1502946/+attachment/4485086/+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/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1498667] Re: [Toshiba P50W-B00F] Touchscreen no longer working

[George Jones]

I have the same problem. My Toshiba laptop model is: P55W-B5112. Running
Ubuntu 15.10 Beta 2.

Oct  5 16:17:50 MyPC kernel: [ 1476.918097] usb 1-4: new full-speed USB device 
number 34 using xhci_hcd
Oct  5 16:17:50 MyPC kernel: [ 1477.048381] usb 1-4: New USB device found, 
idVendor=04f3, idProduct=0381
Oct  5 16:17:50 MyPC kernel: [ 1477.048384] usb 1-4: New USB device strings: 
Mfr=4, Product=14, SerialNumber=0
Oct  5 16:17:50 MyPC kernel: [ 1477.048386] usb 1-4: Product: Touchscreen
Oct  5 16:17:50 MyPC kernel: [ 1477.048387] usb 1-4: Manufacturer: ELAN
Oct  5 16:17:50 MyPC kernel: [ 1477.048503] usb 1-4: ep 0x2 - rounding interval 
to 64 microframes, ep desc says 80 microframes
Oct  5 16:17:50 MyPC kernel: [ 1477.057939] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.0C6A/input/input6356
Oct  5 16:17:50 MyPC kernel: [ 1477.058103] hid-multitouch 0003:04F3:0381.0C6A: 
input,hiddev0,hidraw3: USB HID v1.10 Device [ELAN Touchscreen] on 
usb-:00:14.0-4/input0
Oct  5 16:17:50 MyPC kernel: [ 1477.069991] usb 1-4: USB disconnect, device 
number 34
Oct  5 16:17:50 MyPC kernel: [ 1477.394506] usb 1-4: new full-speed USB device 
number 35 using xhci_hcd
Oct  5 16:17:50 MyPC kernel: [ 1477.524796] usb 1-4: New USB device found, 
idVendor=04f3, idProduct=0381
Oct  5 16:17:50 MyPC kernel: [ 1477.524799] usb 1-4: New USB device strings: 
Mfr=4, Product=14, SerialNumber=0
Oct  5 16:17:50 MyPC kernel: [ 1477.524800] usb 1-4: Product: Touchscreen
Oct  5 16:17:50 MyPC kernel: [ 1477.524802] usb 1-4: Manufacturer: ELAN
Oct  5 16:17:50 MyPC kernel: [ 1477.524918] usb 1-4: ep 0x2 - rounding interval 
to 64 microframes, ep desc says 80 microframes
Oct  5 16:17:50 MyPC kernel: [ 1477.533441] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.0C6B/input/input6358
Oct  5 16:17:50 MyPC kernel: [ 1477.533623] hid-multitouch 0003:04F3:0381.0C6B: 
input,hiddev0,hidraw3: USB HID v1.10 Device [ELAN Touchscreen] on 
usb-:00:14.0-4/input0
Oct  5 16:17:50 MyPC kernel: [ 1477.545535] usb 1-4: USB disconnect, device 
number 35
Oct  5 16:17:50 MyPC kernel: [ 1477.870913] usb 1-4: new full-speed USB device 
number 36 using xhci_hcd
Oct  5 16:17:51 MyPC kernel: [ 1478.000939] usb 1-4: New USB device found, 
idVendor=04f3, idProduct=0381
Oct  5 16:17:51 MyPC kernel: [ 1478.000942] usb 1-4: New USB device strings: 
Mfr=4, Product=14, SerialNumber=0
Oct  5 16:17:51 MyPC kernel: [ 1478.000944] usb 1-4: Product: Touchscreen
Oct  5 16:17:51 MyPC kernel: [ 1478.000945] usb 1-4: Manufacturer: ELAN
Oct  5 16:17:51 MyPC kernel: [ 1478.001063] usb 1-4: ep 0x2 - rounding interval 
to 64 microframes, ep desc says 80 microframes
Oct  5 16:17:51 MyPC kernel: [ 1478.009713] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.0C6C/input/input6360
Oct  5 16:17:51 MyPC kernel: [ 1478.063364] hid-multitouch 0003:04F3:0381.0C6C: 
input,hiddev0,hidraw3: USB HID v1.10 Device [ELAN Touchscreen] on 
usb-:00:14.0-4/input0
Oct  5 16:17:51 MyPC kernel: [ 1478.063441] usb 1-4: USB disconnect, device 
number 36

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1498667

Title:
  [Toshiba P50W-B00F] Touchscreen no longer working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometime in the last month or so my touchscreen stopped working on my
  Toshiba P50W. The dmesg log shows it constantly reconnecting to it:

  [  556.407964] usb 1-4: new full-speed USB device number 119 using xhci_hcd
  [  556.538341] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381
  [  556.538347] usb 1-4: New USB device strings: Mfr=4, Product=14, 
SerialNumber=0
  [  556.538349] usb 1-4: Product: Touchscreen
  [  556.538351] usb 1-4: Manufacturer: ELAN
  [  556.538505] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc 
says 80 microframes
  [  556.547788] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A1/input/input2374
  [  556.600478] hid-multitouch 0003:04F3:0381.04A1: input,hiddev0,hidraw4: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0
  [  556.600584] usb 1-4: USB disconnect, device number 119

  [  556.860456] usb 1-4: new full-speed USB device number 120 using xhci_hcd
  [  556.990494] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381
  [  556.990500] usb 1-4: New USB device strings: Mfr=4, Product=14, 
SerialNumber=0
  [  556.990503] usb 1-4: Product: Touchscreen
  [  556.990506] usb 1-4: Manufacturer: ELAN
  [  556.990755] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc 
says 80 microframes
  [  557.001248] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A2/input/input2376
  [  557.002517] hid-multitouch 0003:04F3:0381.04A2: input,hiddev0,hidraw4: USB 

Re: [Kernel-packages] [Bug 1499203] Re: memory leak in hv_storvsc (3.13.0-63-generic)

[Oskar Liljeblad]

After a couple of days of uptime with 3.13.0-59 it seems there are no leaks, at
least not like before. There are no kmalloc-512 allocations by hv_storsvc at
all. Total Slab memory is 3.63% of MemTotal, and SUnreclaim is 0.41%. (4GB
MemTotal.)

Regards,

Oskar Liljeblad

On Wednesday, September 30, 2015 at 20:28, Oskar Liljeblad wrote:
> Hi! I've installed the 3.13.0-59 kernel below on one of the (most)
> troubled machines. We should be able to see results in less than a
> day or so. I will get back to you!
> 
> Thanks
> 
> Oskar
> 
> On Wednesday, September 30, 2015 at 17:46, Joseph Salisbury wrote:
> > I'd like to see if this is a regression.  Would it be possible for you to 
> > test the Ubuntu-3.13.0-59 kernel?  It can be downloaded from:
> > https://launchpad.net/~ubuntu-security/+archive/ubuntu/ppa/+build/7723132
> > 
> > You would need to install the linux-image and linux-image-extra .deb
> > packages.
> > 
> > Thanks in advance!
> > 
> > ** Also affects: linux (Ubuntu Trusty)
> >Importance: Undecided
> >Status: New
> > 
> > ** Changed in: linux (Ubuntu Trusty)
> >Importance: Undecided => High
> > 
> > ** Changed in: linux (Ubuntu)
> >Importance: Medium => High
> > 
> > ** Changed in: linux (Ubuntu Trusty)
> >Status: New => Confirmed
> > 
> > -- 
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1499203
> > 
> > Title:
> >   memory leak in hv_storvsc (3.13.0-63-generic)
> > 
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499203/+subscriptions
> >

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1499203

Title:
  memory leak in hv_storvsc (3.13.0-63-generic)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed

Bug description:
  Slab and SUnreclaim values in /proc/meminfo keep increasing. On one
  servers it reached 85% of physical memory after 14 days - but on most
  other servers it increases more slowly. I checked /proc/slabinfo and
  almost all allocations were in kmalloc-512. So I enabled
  "slub_debug=U,kmalloc-512" on one server, and after only 24h of uptime
  11% of the memory was used by kmalloc-512 and unreclaimable. With
  debugging enabled I could see the following in
  /sys/kernel/slab/kmalloc-512/alloc_calls:

  521294 storvsc_queuecommand+0x359/0x790 [hv_storvsc]
  age=161922/955116/20882927 pid=1-41545

  All other counters were below 2000. In
  /sys/kernel/slab/kmalloc-512/free_calls I see the following:

  516823  age=4315783846 pid=0

  The hv_storvsc module is for Hyper-V. We are (unfortunately) running
  Hyper-V 6.3.9600.16384 with Microsoft System Center 2012 R2 Update
  rollup 3 for all the servers with this issue.

  Kernels are stock linux-image-3.13.0-63-generic, 3.13.0-63.103,
  x86_64, from Ubuntu 14.04 LTS . /proc/version_signature contains:

Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25

  No output from lspci -vnvn. The problem described above happens on
  both single and multicore virtual machines. CPU in hypervisors are
  E5-2630 v2 @ 2.60GHz. Let me know if you need more info or if I can do
  more debugging.

  Regards,

  Oskar Liljeblad
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 24 00:31 seq
   crw-rw 1 root audio 116, 33 Sep 24 00:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [59081.977909] systemd-udevd[26480]: starting version 204
   [59124.051974] init: systemd-logind main process (756) killed by TERM signal
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-09-09 (380 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic.efi.signed 
root=UUID=f4d228d6-2eee-40fc-bf3f-633e46fa8301 ro slub_debug=U,kmalloc-512
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  

[Kernel-packages] [Bug 1502772] [NEW] Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

Public bug reported:

Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

** 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/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in linux package in Ubuntu:
  New

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1491850] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From vsand...@in.ibm.com 2015-10-05 06:43 EDT---
YUECHANG E. MEI 2015-10-01 10:56:02 EDT

(In reply to comment #18)
> Hello,
>
> The interesting part of the log is :
>
> Processing triggers for systemd (225-1ubuntu4) ...
> Error getting authority: Error initializing authority: Error calling
> StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached
> (g-io-error-quark, 24)
> Failed to execute operation: Connection timed out
> dpkg: error processing package systemd (--unpack):
> subprocess installed post-installation script returned error exit status 1
>
> The interesting line is :
>
> Error getting authority: Error initializing authority: Error calling
> StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached
> (g-io-error-quark, 24)
>
> which leads to LP: #1447654 : installing policykit-1 hangs under systemd
>
> This was fixed in policykit-1 (0.105-10). Can you please check which version
> you have ?

We have policykit-1 (0.105-11), but it isn't installed successfully. I
know we have a workaround for this problem. The workaround is to install
policykit-1 first and install Linux-crashdump after that. My question is
can we fix this problem or should we document this workaround for Ubuntu
15.10?

root@callalp3:~# dpkg -l | grep policykit
iU  policykit-10.105-11ubuntu1 ppc64el  
framework for managing administrative policies and privileges

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491850

Title:
  ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages

Status in crashdump package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - YUECHANG E. MEI  - 2015-09-02 12:57:52 ==
  ---Problem Description---
  We tried to install linux-crashdump package (using "apt-get install 
linux-crashdump") in Ubuntu 15.10 lpar, but fails and hit some errors. Since we 
have similar bug 122925 open in Ubuntu 15.04 (LP bug# LP1436448), we used the 
work around in bug 122925 and the linux-crashdump get install successfully.

  Error we see when we install linux-crashdump:

  root@conelp2:~# apt-get install linux-crashdump
  
  
  Unpacking linux-crashdump (4.1.0.3.3) ...
  Selecting previously unselected package policykit-1.
  Preparing to unpack .../policykit-1_0.105-11_ppc64el.deb ...
  Unpacking policykit-1 (0.105-11) ...
  Processing triggers for man-db (2.7.2-1) ...
  Processing triggers for shared-mime-info (1.3-1) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (224-2ubuntu2) ...
  Error getting authority: Error initializing authority: Error calling 
StartServiceByName for org.freedesktop.PolicyKit1: 
GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 
'org.freedesktop.PolicyKit1': timed out (g-dbus-error-quark, 20)
  Failed to execute operation: Connection timed out
  dpkg: error processing package systemd (--unpack):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for dbus (1.9.20-1ubuntu2) ...
  Errors were encountered while processing:
   systemd
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  root@conelp2:~# dpkg -l | grep linux-crashdump
  iU  linux-crashdump   4.1.0.3.3   ppc64el 
 Linux kernel crashdump setup for the latest generic kernel

   
  ---uname output---
  Linux conelp2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:23:44 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = n/a 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Install Ubuntu 15.10 in a lpar
  2. Login as root, and run "apt-get update".
  3. Install linux-crashdump packages, run "apt-get install linux-crashdump", 
then you will see the error
   

  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Yuechang (Erin) Mei /ye...@us.ibm.com,  Raja  
Sunkari /rajas...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crashdump/+bug/1491850/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1502772

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/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1494236] Re: 10de:1292 Optirun does not run as kernel does not recognise 3D Controller NVIDIA

[Jim Richards]

Updates ASUS to BIOS 403. Using optirun gives same output in dmesg -
that pci is not a vga device and fps is running slow at max 60 fps.
(Should be several hundred to thousand).

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
X550LB.403
06/26/2014

$ optirun glxgears 
primus: warning: dropping a frame to avoid deadlock
251 frames in 5.3 seconds = 47.262 FPS
268 frames in 5.0 seconds = 53.501 FPS

$ dmesg | fgrep vgaar
[0.277697] vgaarb: setting as boot device: PCI::00:02.0
[0.277700] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
[0.277704] vgaarb: loaded
[0.277706] vgaarb: bridge control possible :00:02.0
[2.761036] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[  453.256105] vgaarb: this pci device is not a vga device
[  453.719283] vgaarb: this pci device is not a vga device


** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Tags removed: bios-outdated-403

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1494236

Title:
  10de:1292 Optirun does not run as kernel does not recognise 3D
  Controller NVIDIA

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  $ lspci -nn
  00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a16] (rev 09)
  ...
  04:00.0 3D controller [0302]: NVIDIA Corporation GK208M [GeForce GT 740M] 
[10de:1292] (rev ff)

  $ dmesg | fgrep vgaar
  [ 0.243143] vgaarb: setting as boot device: PCI::00:02.0
  [ 0.243145] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [ 0.243150] vgaarb: loaded
  [ 0.243152] vgaarb: bridge control possible :00:02.0
  [ 2.766514] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [ 2336.771620] vgaarb: this pci device is not a vga device
  [ 2337.170566] vgaarb: this pci device is not a vga device
  [ 2415.373308] vgaarb: this pci device is not a vga device
  [ 2415.734668] vgaarb: this pci device is not a vga device

  $ uname -a
  Linux flat 3.19.0-26-generic #28-Ubuntu SMP Tue Aug 11 14:16:32 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-26-generic 3.19.0-26.28
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  grumpy 2187 F pulseaudio
   /dev/snd/controlC1:  grumpy 2187 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep 10 20:11:34 2015
  HibernationDevice: RESUME=UUID=0f0470a9-ab37-4ceb-b408-3ff836a8ed03
  InstallationDate: Installed on 2015-05-19 (114 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 003 Device 002: ID 8087:8000 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5606 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550LB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed 
root=UUID=6dbeeb75-7225-4474-8a0f-5b0447421785 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-26-generic N/A
   linux-backports-modules-3.19.0-26-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LB.402
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LB.402:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnX550LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494236/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Keng-Yu Lin]

** 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/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Also affects: debian-installer (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/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502781] [NEW] Bluetooth 0930:021c not working in Ubuntu 15.10

[P.L. Lucas]

Public bug reported:

Ubuntu detects the bluetooth hardware (it shows the bluetooth icon in
the status bar), and I can turn it on or off and set the visibility and
such. However, it is never able to find any bluetooth device.

"lsusb" shows:

  Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012
Bluetooth

"rfkill list" output:
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

"hciconfig -a" output:
  hci0: Type: BR/EDR  Bus: USB
  BD Address: 18:CF:5E:09:55:43  ACL MTU: 1022:8  SCO MTU: 183:5
  UP RUNNING 
  RX bytes:1313 acl:0 sco:0 events:88 errors:0
  TX bytes:3200 acl:0 sco:0 commands:87 errors:0
  Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x8f
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
  Link policy: RSWITCH HOLD SNIFF 
  Link mode: SLAVE ACCEPT 
  Name: 'lucas-Leon'
  Class: 0x0c010c
  Service Classes: Rendering, Capturing
  Device Class: Computer, Laptop
  HCI Version: 4.1 (0x7)  Revision: 0x1102
  LMP Version: 4.0 (0x6)  Subversion: 0x1
  Manufacturer: Atheros Communications, Inc. (69)

Thanks for your help.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-14-generic 4.2.0-14.16
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lucas  1143 F pulseaudio
 /dev/snd/controlC1:  lucas  1143 F pulseaudio
CurrentDesktop: Unity
Date: Mon Oct  5 09:19:20 2015
HibernationDevice: RESUME=UUID=58bcbcd9-672f-4530-b8b5-775f76fc9187
InstallationDate: Installed on 2015-10-04 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer
 Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012 Bluetooth
 Bus 001 Device 002: ID 04f2:b433 Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Toshiba Leon
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-14-generic 
root=UUID=a107b544-64af-4e74-89a7-2c0e9fe8ce8d ro rootflags=subvol=@ 
tpm_tis.interrupts=0 modprobe.blacklist=ehci_pci quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-14-generic N/A
 linux-backports-modules-4.2.0-14-generic  N/A
 linux-firmware1.148
SourcePackage: linux
UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/26/2014
dmi.bios.vendor: coreboot
dmi.chassis.type: 3
dmi.chassis.vendor: Toshiba
dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/26/2014:svnToshiba:pnLeon:pvr1.0:cvnToshiba:ct3:cvr:
dmi.product.name: Leon
dmi.product.version: 1.0
dmi.sys.vendor: Toshiba

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

** Attachment added: "Output from "lspci -vnvn > lspci-vnvn.log" and "cat 
/proc/version_signature""
   https://bugs.launchpad.net/bugs/1502781/+attachment/4484363/+files/logs.zip

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502781

Title:
  Bluetooth 0930:021c not working in Ubuntu 15.10

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu detects the bluetooth hardware (it shows the bluetooth icon in
  the status bar), and I can turn it on or off and set the visibility
  and such. However, it is never able to find any bluetooth device.

  "lsusb" shows:

Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012
  Bluetooth

  "rfkill list" output:
1: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
2: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  "hciconfig -a" output:
hci0:   Type: BR/EDR  Bus: USB
  BD Address: 18:CF:5E:09:55:43  ACL MTU: 1022:8  SCO MTU: 183:5
  UP RUNNING 
  RX bytes:1313 acl:0 sco:0 events:88 errors:0
  TX bytes:3200 acl:0 sco:0 commands:87 errors:0
  Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x8f
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
  Link policy: RSWITCH HOLD SNIFF 
  Link mode: SLAVE ACCEPT 
  Name: 'lucas-Leon'
  Class: 0x0c010c
  Service Classes: Rendering, Capturing
  Device Class: Computer, Laptop
  HCI Version: 4.1 (0x7)  Revision: 0x1102
  LMP Version: 4.0 (0x6)  Subversion: 0x1
  Manufacturer: Atheros Communications, Inc. (69)

  Thanks for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  

[Kernel-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting

[Jan Rathmann]

The lasted upstream kernel I could test was 4.2.3, because with 4.3 the
compilation and installation of the Nvidia kernel module fails, and I
can only test with the propritary Nvidia driver because suspend doesn't
work properly with Nouveau on my card.

** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.2.3

** 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/1450396

Title:
  Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-
  lan setting

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  === Update: This bug was reported from BIOS version F13 of my board,
  in the meantime I upgraded to the most recent version F14, but this
  had no impact on the bug. ===

  Hello,

  using Suspend-to-RAM on my system has stopped working reliably on
  Vivid when booting with Systemd. When I try to suspend my PC the
  following happens:

  - PC turns off
  - PC unwantedly wakes up (turns on) by itself again. This time span until it 
turns on again can reach from a second (almost immediately) until two or three 
minutes.
  - In a few cases (<25%), the PC stays suspended properly.

  A way to workaround this problem is to boot my PC with Upstart instead
  of Systemd, then this problem never happens (and has never happened in
  any of the previous Ubuntu versions since 2008). Thus it seems to be a
  bug somehow related to Systemd.

  Other steps I have tried to solve the problem (without any success):

  - Checking BIOS settings, all options are set that way that the PC should 
never wake up by any event other than pressing the power button.
  - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device 
could cause wake up events. This lists my USB controller, but deactivating it 
(with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the 
problem. Also suspend while running Upstart works fine despite the USB 
controller listed as "enabled".

  In the system logs I could see no hint what causes the undesired wake-
  ups.

  Allthough there is one factor which seems to have a certain influence:
  If I close programs like Pidgin, Skype or Firefox that cause
  continuous network traffic, the chance is higher that my PC will stay
  suspened (while runinng Systemd).

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 11:24:46 2015
  InstallationDate: Installed on 2015-04-16 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450396/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1487524] Re: 14e4:43ba Broadcom BCM43602 not seeing 5Ghz range

[Christopher M. Penalver]

** Summary changed:

- Broadcom BCM43602 not seeing 5Ghz range
+ 14e4:43ba Broadcom BCM43602 not seeing 5Ghz range

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1487524

Title:
  14e4:43ba Broadcom BCM43602 not seeing 5Ghz range

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On a MacbookPro12,1 (2015 model), the wireless works with the brcmfmac
  on a wily install out of the box, but can't see any APs on the 5GHz
  range even though there are APs broadcasting on 5Ghz.

  03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless 
LAN SoC (rev 01)
Subsystem: Apple Inc. Device 0152
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: brcmfmac

  $ sudo iwlist wlp3s0 scan|grep Freq
  Frequency:2.412 GHz (Channel 1)
  Frequency:2.422 GHz (Channel 3)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: 
boot/vmlinuz-4.1.0-3-generic]
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  jbarnett   1545 F pulseaudio
   /dev/snd/controlC2:  jbarnett   1545 F pulseaudio
   /dev/snd/controlC1:  jbarnett   1545 F pulseaudio
   /dev/snd/controlC0:  jbarnett   1545 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Aug 21 08:46:15 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945
  InstallationDate: Installed on 2015-08-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  MachineType: Apple Inc. MacBookPro11,4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware   1.146
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B04.1506051511
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1487524/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502781] Status changed to Confirmed

[Brad Figg]

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/1502781

Title:
  Bluetooth 0930:021c not working in Ubuntu 15.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu detects the bluetooth hardware (it shows the bluetooth icon in
  the status bar), and I can turn it on or off and set the visibility
  and such. However, it is never able to find any bluetooth device.

  "lsusb" shows:

Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012
  Bluetooth

  "rfkill list" output:
1: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
2: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  "hciconfig -a" output:
hci0:   Type: BR/EDR  Bus: USB
  BD Address: 18:CF:5E:09:55:43  ACL MTU: 1022:8  SCO MTU: 183:5
  UP RUNNING 
  RX bytes:1313 acl:0 sco:0 events:88 errors:0
  TX bytes:3200 acl:0 sco:0 commands:87 errors:0
  Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x8f
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
  Link policy: RSWITCH HOLD SNIFF 
  Link mode: SLAVE ACCEPT 
  Name: 'lucas-Leon'
  Class: 0x0c010c
  Service Classes: Rendering, Capturing
  Device Class: Computer, Laptop
  HCI Version: 4.1 (0x7)  Revision: 0x1102
  LMP Version: 4.0 (0x6)  Subversion: 0x1
  Manufacturer: Atheros Communications, Inc. (69)

  Thanks for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lucas  1143 F pulseaudio
   /dev/snd/controlC1:  lucas  1143 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct  5 09:19:20 2015
  HibernationDevice: RESUME=UUID=58bcbcd9-672f-4530-b8b5-775f76fc9187
  InstallationDate: Installed on 2015-10-04 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer
   Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012 Bluetooth
   Bus 001 Device 002: ID 04f2:b433 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Toshiba Leon
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-14-generic 
root=UUID=a107b544-64af-4e74-89a7-2c0e9fe8ce8d ro rootflags=subvol=@ 
tpm_tis.interrupts=0 modprobe.blacklist=ehci_pci quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.148
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: Toshiba
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/26/2014:svnToshiba:pnLeon:pvr1.0:cvnToshiba:ct3:cvr:
  dmi.product.name: Leon
  dmi.product.version: 1.0
  dmi.sys.vendor: Toshiba

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502781/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502792] [NEW] [Dell Inspiron 5552][8086:22b1] X didn't use hardware acceleration

[Yung Shen]

Public bug reported:

it's a fresh installed 14.04.1(kernel 3.13) with system software
upgraded to 14.04.3.

unity does not fully supported because there is no 3d acceleration with
this intel graphic.

as in contrast, 14.04.3 with 3.19 kernel the graphic works just fine.


ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26
Uname: Linux 3.13.0-65-generic x86_64
.tmp.unity.support.test.1:

ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Oct  5 15:58:31 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms, 15.09.00, 3.13.0-65-generic, x86_64: installed
 tp-smapi, 0.41, 3.13.0-65-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:06d8]
InstallationDate: Installed on 2015-10-02 (3 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Inspiron 5552
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic.efi.signed 
root=UUID=4bad80b9-c053-4817-825c-3dba80ae58d1 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.4.8
dmi.board.name: Inspiron 5552
dmi.board.vendor: Dell Inc.
dmi.board.version: 000
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.4.8
dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.8:bd06/10/2015:svnDellInc.:pnInspiron5552:pvr0.4.8:rvnDellInc.:rnInspiron5552:rvr000:cvnDellInc.:ct8:cvr0.4.8:
dmi.product.name: Inspiron 5552
dmi.product.version: 0.4.8
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Oct  5 15:50:31 2015
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.15.1-0ubuntu2.7

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 201506-18422 amd64 apport-bug blocks-hwcert compiz-0.9 trusty ubuntu

** Description changed:

- it's a fresh installed 14.04.1(kernel 3.13) with system upgraded to
- 14.04.3.
+ it's a fresh installed 14.04.1(kernel 3.13) with system software
+ upgraded to 14.04.3.
  
  unity does not fully supported because there is no 3d acceleration with
  this intel graphic.
+ 
+ as in contrast, 14.04.3 with 3.19 kernel the graphic works just fine.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  .tmp.unity.support.test.1:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct  5 15:58:31 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
-  fwts-efi-runtime-dkms, 15.09.00, 3.13.0-65-generic, x86_64: installed
-  tp-smapi, 0.41, 3.13.0-65-generic, x86_64: installed
+  fwts-efi-runtime-dkms, 15.09.00, 3.13.0-65-generic, x86_64: installed
+  tp-smapi, 0.41, 3.13.0-65-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
-Subsystem: Dell Device [1028:06d8]
+  Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
+    Subsystem: Dell Device [1028:06d8]
  InstallationDate: Installed on 2015-10-02 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
 

[Kernel-packages] [Bug 1502792] Re: [Dell Inspiron 5552][8086:22b1] X didn't use hardware acceleration

[Brad Figg]

** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502792

Title:
   [Dell Inspiron 5552][8086:22b1] X didn't use hardware acceleration

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  it's a fresh installed 14.04.1(kernel 3.13) with system software
  upgraded to 14.04.3.

  unity does not fully supported because there is no 3d acceleration
  with this intel graphic.

  as in contrast, 14.04.3 with 3.19 kernel the graphic works just fine.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct  5 15:58:31 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 15.09.00, 3.13.0-65-generic, x86_64: installed
   tp-smapi, 0.41, 3.13.0-65-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:06d8]
  InstallationDate: Installed on 2015-10-02 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 5552
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic.efi.signed 
root=UUID=4bad80b9-c053-4817-825c-3dba80ae58d1 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.8
  dmi.board.name: Inspiron 5552
  dmi.board.vendor: Dell Inc.
  dmi.board.version: 000
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.4.8
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.8:bd06/10/2015:svnDellInc.:pnInspiron5552:pvr0.4.8:rvnDellInc.:rnInspiron5552:rvr000:cvnDellInc.:ct8:cvr0.4.8:
  dmi.product.name: Inspiron 5552
  dmi.product.version: 0.4.8
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Oct  5 15:50:31 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1502792/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502800] [NEW] Upgrade from 14.04 LTS to 15.04

[Francesco]

Public bug reported:

When I start the upgrading to version 15.04, tell me as impossible
because an upgrade from 'trusty' to 'vivid' is not supported with this
tool.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-65-generic 3.13.0-65.105
ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26
Uname: Linux 3.13.0-65-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  utente 1436 F pulseaudio
 /dev/snd/controlC0:  utente 1436 F pulseaudio
CurrentDesktop: Unity
Date: Mon Oct  5 10:25:58 2015
HibernationDevice: RESUME=UUID=0c72b14e-01dd-4a7d-bd73-c3f43fc24069
InstallationDate: Installed on 2015-04-08 (179 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic 
root=UUID=7c616abd-1b28-45a4-af34-aa1f47264783 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-65-generic N/A
 linux-backports-modules-3.13.0-65-generic  N/A
 linux-firmware 1.127.16
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2015-10-05 (0 days ago)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1807
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502800

Title:
  Upgrade from 14.04 LTS to 15.04

Status in linux package in Ubuntu:
  New

Bug description:
  When I start the upgrading to version 15.04, tell me as impossible
  because an upgrade from 'trusty' to 'vivid' is not supported with this
  tool.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-65-generic 3.13.0-65.105
  ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  utente 1436 F pulseaudio
   /dev/snd/controlC0:  utente 1436 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct  5 10:25:58 2015
  HibernationDevice: RESUME=UUID=0c72b14e-01dd-4a7d-bd73-c3f43fc24069
  InstallationDate: Installed on 2015-04-08 (179 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic 
root=UUID=7c616abd-1b28-45a4-af34-aa1f47264783 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-65-generic N/A
   linux-backports-modules-3.13.0-65-generic  N/A
   linux-firmware 1.127.16
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2015-10-05 (0 days ago)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D:rvrRev1.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/1502800/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502781] Re: Bluetooth 0930:021c not working in Ubuntu 15.10

[Pilot6]

Did you add "new_id" for btusb? It looks like you did, because this id
is not in btusb.

I will build a deb later with btusb and ath3k for testing.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502781

Title:
  Bluetooth 0930:021c not working in Ubuntu 15.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu detects the bluetooth hardware (it shows the bluetooth icon in
  the status bar), and I can turn it on or off and set the visibility
  and such. However, it is never able to find any bluetooth device.

  "lsusb" shows:

Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012
  Bluetooth

  "rfkill list" output:
1: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
2: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  "hciconfig -a" output:
hci0:   Type: BR/EDR  Bus: USB
  BD Address: 18:CF:5E:09:55:43  ACL MTU: 1022:8  SCO MTU: 183:5
  UP RUNNING 
  RX bytes:1313 acl:0 sco:0 events:88 errors:0
  TX bytes:3200 acl:0 sco:0 commands:87 errors:0
  Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x8f
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
  Link policy: RSWITCH HOLD SNIFF 
  Link mode: SLAVE ACCEPT 
  Name: 'lucas-Leon'
  Class: 0x0c010c
  Service Classes: Rendering, Capturing
  Device Class: Computer, Laptop
  HCI Version: 4.1 (0x7)  Revision: 0x1102
  LMP Version: 4.0 (0x6)  Subversion: 0x1
  Manufacturer: Atheros Communications, Inc. (69)

  Thanks for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lucas  1143 F pulseaudio
   /dev/snd/controlC1:  lucas  1143 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct  5 09:19:20 2015
  HibernationDevice: RESUME=UUID=58bcbcd9-672f-4530-b8b5-775f76fc9187
  InstallationDate: Installed on 2015-10-04 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer
   Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012 Bluetooth
   Bus 001 Device 002: ID 04f2:b433 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Toshiba Leon
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-14-generic 
root=UUID=a107b544-64af-4e74-89a7-2c0e9fe8ce8d ro rootflags=subvol=@ 
tpm_tis.interrupts=0 modprobe.blacklist=ehci_pci quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.148
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: Toshiba
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/26/2014:svnToshiba:pnLeon:pvr1.0:cvnToshiba:ct3:cvr:
  dmi.product.name: Leon
  dmi.product.version: 1.0
  dmi.sys.vendor: Toshiba

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502781/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1494236] Re: 10de:1292 Optirun does not run as kernel does not recognise 3D Controller NVIDIA

[Christopher M. Penalver]

Jim Richards, could you please test the latest upstream kernel available
from the very top line at the top of the page from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release
names are irrelevant for testing, and please do not test the daily
folder)? Install instructions are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow
additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this
report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags added: latest-bios-403

** Attachment removed: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494236/+attachment/4460410/+files/lspci-vnvn.log

** Changed in: linux (Ubuntu)
   Importance: Low => 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/1494236

Title:
  10de:1292 Optirun does not run as kernel does not recognise 3D
  Controller NVIDIA

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lspci -nn
  00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a16] (rev 09)
  ...
  04:00.0 3D controller [0302]: NVIDIA Corporation GK208M [GeForce GT 740M] 
[10de:1292] (rev ff)

  $ dmesg | fgrep vgaar
  [ 0.243143] vgaarb: setting as boot device: PCI::00:02.0
  [ 0.243145] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [ 0.243150] vgaarb: loaded
  [ 0.243152] vgaarb: bridge control possible :00:02.0
  [ 2.766514] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [ 2336.771620] vgaarb: this pci device is not a vga device
  [ 2337.170566] vgaarb: this pci device is not a vga device
  [ 2415.373308] vgaarb: this pci device is not a vga device
  [ 2415.734668] vgaarb: this pci device is not a vga device

  $ uname -a
  Linux flat 3.19.0-26-generic #28-Ubuntu SMP Tue Aug 11 14:16:32 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-26-generic 3.19.0-26.28
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  grumpy 2187 F pulseaudio
   /dev/snd/controlC1:  grumpy 2187 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep 10 20:11:34 2015
  HibernationDevice: RESUME=UUID=0f0470a9-ab37-4ceb-b408-3ff836a8ed03
  InstallationDate: Installed on 2015-05-19 (114 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 003 Device 002: ID 8087:8000 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5606 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550LB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed 
root=UUID=6dbeeb75-7225-4474-8a0f-5b0447421785 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-26-generic N/A
   linux-backports-modules-3.19.0-26-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LB.402
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  

[Kernel-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting

[Jan Rathmann]

Disregard my last comment - I did a test anyway with 4.3-rc4 and Nouveau
and supending with Nouveau worked at least one time so I could reproduce
and confirm the bug for 4.3-rc4.

** Tags removed: kernel-bug-exists-upstream-4.2.3
** Tags added: kernel-bug-exists-upstream-4.3-rc4

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1450396

Title:
  Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-
  lan setting

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  === Update: This bug was reported from BIOS version F13 of my board,
  in the meantime I upgraded to the most recent version F14, but this
  had no impact on the bug. ===

  Hello,

  using Suspend-to-RAM on my system has stopped working reliably on
  Vivid when booting with Systemd. When I try to suspend my PC the
  following happens:

  - PC turns off
  - PC unwantedly wakes up (turns on) by itself again. This time span until it 
turns on again can reach from a second (almost immediately) until two or three 
minutes.
  - In a few cases (<25%), the PC stays suspended properly.

  A way to workaround this problem is to boot my PC with Upstart instead
  of Systemd, then this problem never happens (and has never happened in
  any of the previous Ubuntu versions since 2008). Thus it seems to be a
  bug somehow related to Systemd.

  Other steps I have tried to solve the problem (without any success):

  - Checking BIOS settings, all options are set that way that the PC should 
never wake up by any event other than pressing the power button.
  - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device 
could cause wake up events. This lists my USB controller, but deactivating it 
(with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the 
problem. Also suspend while running Upstart works fine despite the USB 
controller listed as "enabled".

  In the system logs I could see no hint what causes the undesired wake-
  ups.

  Allthough there is one factor which seems to have a certain influence:
  If I close programs like Pidgin, Skype or Firefox that cause
  continuous network traffic, the chance is higher that my PC will stay
  suspened (while runinng Systemd).

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 11:24:46 2015
  InstallationDate: Installed on 2015-04-16 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450396/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502792] Status changed to Confirmed

[Brad Figg]

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/1502792

Title:
   [Dell Inspiron 5552][8086:22b1] X didn't use hardware acceleration

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  it's a fresh installed 14.04.1(kernel 3.13) with system software
  upgraded to 14.04.3.

  unity does not fully supported because there is no 3d acceleration
  with this intel graphic.

  as in contrast, 14.04.3 with 3.19 kernel the graphic works just fine.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct  5 15:58:31 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 15.09.00, 3.13.0-65-generic, x86_64: installed
   tp-smapi, 0.41, 3.13.0-65-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:06d8]
  InstallationDate: Installed on 2015-10-02 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 5552
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic.efi.signed 
root=UUID=4bad80b9-c053-4817-825c-3dba80ae58d1 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.8
  dmi.board.name: Inspiron 5552
  dmi.board.vendor: Dell Inc.
  dmi.board.version: 000
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.4.8
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.8:bd06/10/2015:svnDellInc.:pnInspiron5552:pvr0.4.8:rvnDellInc.:rnInspiron5552:rvr000:cvnDellInc.:ct8:cvr0.4.8:
  dmi.product.name: Inspiron 5552
  dmi.product.version: 0.4.8
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Oct  5 15:50:31 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1502792/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1265110] Re: [HP Pavilion 15] Wireless key is not working

[Po-Hsu Lin]

Verified on 3.13.0-65, wireless key works on 201307-13902 and
201307-14029

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1265110

Title:
  [HP Pavilion 15] Wireless key is not working

Status in linux package in Ubuntu:
  Invalid

Bug description:
  CID: 201307-13902 HP Pavilion 15

  The wireless key is not working on this system

  Steps:
  1. Install 12.04.3 + update (3.8.0-34)
  2. Press the wireless key to see if it can turn on/off the wireless connection

  Expected result:
  * Wireless key shold work properly

  Actual result:
  * Wireless key not responding, however, the wireless still can be disabled by 
using the NetworkManager

  Debugging information:
  "showkey" command - key press events were not detected
  "xev" command - key press events were not detected
  "acpi_listen" - key press events were not detected

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.8.0-34-generic 3.8.0-34.49~precise1
  ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-34-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: Generic_1 [HD-Audio Generic], device 0: ALC282 Analog [ALC282 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1764 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1764 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xf034 irq 80'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100500'
 Controls  : 7
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Generic_1'/'HD-Audio Generic at 0xf0344000 irq 81'
 Mixer name : 'Realtek ALC282'
 Components : 'HDA:10ec0282,103c216f,0013'
 Controls  : 20
 Simple ctrls  : 9
  Date: Tue Dec 31 10:37:28 2013
  HibernationDevice: RESUME=UUID=0653ac45-af83-4721-a85f-456bb73e61eb
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic 
root=UUID=16cb3b7b-0655-4a92-99e7-6c865bbe60fa ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-34-generic N/A
   linux-backports-modules-3.8.0-34-generic  N/A
   linux-firmware1.79.9
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-lts-raring
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: B.0C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 31.0E
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrB.0C:bd07/12/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr088D1200591620100:rvnHewlett-Packard:rn216F:rvr31.0E:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g4 Notebook PC
  dmi.product.version: 088D1200591620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265110/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502800] Status changed to Confirmed

[Brad Figg]

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/1502800

Title:
  Upgrade from 14.04 LTS to 15.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I start the upgrading to version 15.04, tell me as impossible
  because an upgrade from 'trusty' to 'vivid' is not supported with this
  tool.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-65-generic 3.13.0-65.105
  ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  utente 1436 F pulseaudio
   /dev/snd/controlC0:  utente 1436 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct  5 10:25:58 2015
  HibernationDevice: RESUME=UUID=0c72b14e-01dd-4a7d-bd73-c3f43fc24069
  InstallationDate: Installed on 2015-04-08 (179 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic 
root=UUID=7c616abd-1b28-45a4-af34-aa1f47264783 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-65-generic N/A
   linux-backports-modules-3.13.0-65-generic  N/A
   linux-firmware 1.127.16
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2015-10-05 (0 days ago)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D:rvrRev1.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/1502800/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting

[Christopher M. Penalver]

Jan Rathmann, to clarify:
1) If you use nvidia with 4.2.3, are you able to suspend with the WORKAROUND 
noted in 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450396/comments/22 ?

2) If you use nouveau with 4.3-rc4, are you able to suspend with the
WORKAROUND noted in
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450396/comments/22
?

3) Could you please provide the missing information following
https://wiki.ubuntu.com/DebuggingKernelSuspend ?

** 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/1450396

Title:
  Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-
  lan setting

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  === Update: This bug was reported from BIOS version F13 of my board,
  in the meantime I upgraded to the most recent version F14, but this
  had no impact on the bug. ===

  Hello,

  using Suspend-to-RAM on my system has stopped working reliably on
  Vivid when booting with Systemd. When I try to suspend my PC the
  following happens:

  - PC turns off
  - PC unwantedly wakes up (turns on) by itself again. This time span until it 
turns on again can reach from a second (almost immediately) until two or three 
minutes.
  - In a few cases (<25%), the PC stays suspended properly.

  A way to workaround this problem is to boot my PC with Upstart instead
  of Systemd, then this problem never happens (and has never happened in
  any of the previous Ubuntu versions since 2008). Thus it seems to be a
  bug somehow related to Systemd.

  Other steps I have tried to solve the problem (without any success):

  - Checking BIOS settings, all options are set that way that the PC should 
never wake up by any event other than pressing the power button.
  - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device 
could cause wake up events. This lists my USB controller, but deactivating it 
(with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the 
problem. Also suspend while running Upstart works fine despite the USB 
controller listed as "enabled".

  In the system logs I could see no hint what causes the undesired wake-
  ups.

  Allthough there is one factor which seems to have a certain influence:
  If I close programs like Pidgin, Skype or Firefox that cause
  continuous network traffic, the chance is higher that my PC will stay
  suspened (while runinng Systemd).

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 11:24:46 2015
  InstallationDate: Installed on 2015-04-16 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450396/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1498291] rukbah (amd64) - tests ran: 2, failed: 1

[Brad Figg]

tests ran:   2, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-65.105~precise1/rukbah__3.13.0-65.105~precise1__2015-10-05_06-16-00/results-index.html

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1498291

Title:
  linux-lts-trusty: 3.13.0-65.105~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released

Bug description:
  This bug is for tracking the 3.13.0-65.105~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 22. September 2015 04:03 UTC
  kernel-stable-master-bug:1498108
  kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 20:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 20:01 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 23. September 2015 20:22 UTC
  kernel-stable-Verification-testing-start:Wednesday, 23. September 2015 22:01 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 23. September 2015 22:01 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 23. September 2015 22:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 23. September 2015 22:01 UTC
  kernel-stable-Security-signoff-end:Thursday, 24. September 2015 08:01 UTC
  kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:01 UTC
  kernel-stable-Certification-testing-end:Friday, 25. September 2015 09:01 UTC
  kernel-stable-Promote-to-updates-start:Friday, 25. September 2015 16:08 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Tuesday, 29. September 2015 14:08 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 14:08 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1498291/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502504] Re: Alsamixer doesn't show "Line in".

[Xtien]

You open alsamixer, you see that there's no control for "Line in", what
do you need logs for?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502504

Title:
  Alsamixer doesn't show "Line in".

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I re-installed Ubuntu, and I found that "line in" from the sound card
  wouldn't play. I use my PC for TV audio: TV audio out in PC sound card
  in, and it plays. But, like when I installed Ubuntu a couple of years
  ago, that doesn't work by default.

  I started Alsamixer in a shell, but that doesn't have a control for
  "line in". The sound panel doesn't help either. As it turns out, found
  that on a forum, you need to install gnome-alsamixer. That does have a
  control for "Line" which you can unmute, and have sound.

  I think this is a bug. Alsamixer should have the same features as
  gnome-alsamixer, in Unity you shouldn't need a gnome feature.

  I have Ubuntu 15.04, with the latest updates. I have an MSI X99S
  Xpower AC motherboard with integrated intel audio.

  version:Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502504/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1500854] Re: linux: 3.2.0-92.130 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1500854

Title:
  linux: 3.2.0-92.130 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.2.0-92.130 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, 29. September 2015 12:55 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 29. September 2015 12:55 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1500854/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1478492] Re: MFG:Firestone, Linux Error message: unable to open rtc device

[bugproxy]

** Tags removed: architecture-ppc64
** Tags added: architecture-ppc64le

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1478492

Title:
  MFG:Firestone, Linux Error message: unable to open rtc device

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2015-07-22 12:35:06 ==

  
  == Comment: #1 - Application Cdeadmin  - 2015-07-22 
12:35:08 ==
   State: Open by: knodelk on 22 July 2015 11:26:27 

  he following message is being posted to the linux message log on Firestone 
systems, and we need to know what action to take.
   - is this caused by a code bug that needs to be fixed?
   - does the message indicate a real hardware problem? 
 or can the message be ignore?

  Until we here otherwise, manufacturing is ignoring this message

  dmesg --level=alert,crit,err


  /build/buildd/linux-lts-utopic-3.16.0/drivers/rtc/hctosys.c: unable to open 
rtc device (rtc0)

  system is running with the following code levels: 
 ver 1.5.4.3 - OS, HTX, Firmware and Machine details

 OS: GNU/Linux
 OS Version: Ubuntu 14.04.2 LTS \n \l
 Kernel Version: 3.16.0-30-generic
HTX Version: htxubuntu-343

  
  == Comment: #2 - MAMATHA INAMDAR  - 2015-07-23 02:10:00 
==
  Neelesh,
  Can you please comment on this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478492/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1487524] Re: 14e4:43ba Broadcom BCM43602 not seeing 5Ghz range

[Christopher M. Penalver]

** Tags removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.2-rc8
** Tags added: cherry-pick kernel-fixed-upstream

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1487524

Title:
  14e4:43ba Broadcom BCM43602 not seeing 5Ghz range

Status in Linux:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed

Bug description:
  On a MacbookPro12,1 (2015 model), the wireless works with the brcmfmac
  on a wily install out of the box, but can't see any APs on the 5GHz
  range even though there are APs broadcasting on 5Ghz.

  03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless 
LAN SoC (rev 01)
Subsystem: Apple Inc. Device 0152
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: brcmfmac

  $ sudo iwlist wlp3s0 scan|grep Freq
  Frequency:2.412 GHz (Channel 1)
  Frequency:2.422 GHz (Channel 3)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: 
boot/vmlinuz-4.1.0-3-generic]
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  jbarnett   1545 F pulseaudio
   /dev/snd/controlC2:  jbarnett   1545 F pulseaudio
   /dev/snd/controlC1:  jbarnett   1545 F pulseaudio
   /dev/snd/controlC0:  jbarnett   1545 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Aug 21 08:46:15 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945
  InstallationDate: Installed on 2015-08-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  MachineType: Apple Inc. MacBookPro11,4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware   1.146
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B04.1506051511
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1487524/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502598] Re: Boot hangs on encryption password prompt on 3.19.0-30

[Christopher M. Penalver]

Troy Ready, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502598

Title:
  Boot hangs on encryption password prompt on 3.19.0-30

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Starting with kernel 3.19.0-30-generic, the password prompt for my
  disk encryption password hangs at boot.

  I can workaround the issue by booting with kernel 3.19.0-28-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-28-generic 3.19.0-28.30
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mark   1788 F pulseaudio
   /dev/snd/controlC0:  mark   1788 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct  4 07:22:53 2015
  HibernationDevice: RESUME=UUID=4392843b-ec3d-442b-8159-f2e4bed58105
  InstallationDate: Installed on 2015-09-20 (14 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502598/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1173681] Re: 168c:002b [Asus U32U] asus_nb_wmi AR9285 ath9k not working after updating to Ubuntu 13.04 Raring

[Christopher M. Penalver]

Xorso, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1173681

Title:
  168c:002b [Asus U32U] asus_nb_wmi AR9285 ath9k not working after
  updating to Ubuntu 13.04 Raring

Status in Linux:
  Invalid
Status in Linux Deepin:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  update: updated the BIOS to the latest version but the problem
  persists.

  Booting with the older kernel (latest linux kernel from 12.10) every thing 
works fine. After upgrading to Raring Ringtail Ubuntu 13.04, with the new 
kernel, hardware get blocked/disabled and wireless doesn't work:
  0: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: yes
  1: asus-wlan: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  WORKAROUND - is only applicable to Asus Notebooks/netbooks that use the 
"asus_nb_wmi" driver:
  Create and edit asus_nb_wmi.conf file with this command:
  sudo echo "options asus_nb_wmi wapf=4" | sudo tee 
/etc/modprobe.d/asus_nb_wmi.conf

  For more detailed info of the workaround please see:
  http://ubuntuforums.org/showthread.php?t=2181558

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-19-generic 3.8.0-19.29
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  x  1822 F pulseaudio
  CurrentDmesg:
   [  370.100280] r8169 :04:00.2 eth1: link up
   [  370.100322] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
   [  891.718748] systemd-hostnamed[2649]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
   [14119.241628] rtsx_pci :04:00.0: vpd r/w failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update.
  Date: Sat Apr 27 17:31:51 2013
  HibernationDevice: RESUME=UUID=e417e9f2-b63e-4b79-9be4-c21f55547205
  InstallationDate: Installed on 2012-07-13 (287 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: ASUSTeK Computer Inc. U32U
  MarkForUpload: True
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=3ad9d88b-a7a5-460f-ba15-a78dd7f2fc94 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-04-27 (0 days ago)
  dmi.bios.date: 12/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U32U.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U32U
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU32U.204:bd12/16/2011:svnASUSTeKComputerInc.:pnU32U:pvr1.0:rvnASUSTeKComputerInc.:rnU32U:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: U32U
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1173681/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1498667] Re: [Toshiba P50W-B00F] Touchscreen no longer working

[Christopher M. Penalver]

George Jones, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1498667

Title:
  [Toshiba P50W-B00F] Touchscreen no longer working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometime in the last month or so my touchscreen stopped working on my
  Toshiba P50W. The dmesg log shows it constantly reconnecting to it:

  [  556.407964] usb 1-4: new full-speed USB device number 119 using xhci_hcd
  [  556.538341] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381
  [  556.538347] usb 1-4: New USB device strings: Mfr=4, Product=14, 
SerialNumber=0
  [  556.538349] usb 1-4: Product: Touchscreen
  [  556.538351] usb 1-4: Manufacturer: ELAN
  [  556.538505] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc 
says 80 microframes
  [  556.547788] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A1/input/input2374
  [  556.600478] hid-multitouch 0003:04F3:0381.04A1: input,hiddev0,hidraw4: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0
  [  556.600584] usb 1-4: USB disconnect, device number 119

  [  556.860456] usb 1-4: new full-speed USB device number 120 using xhci_hcd
  [  556.990494] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381
  [  556.990500] usb 1-4: New USB device strings: Mfr=4, Product=14, 
SerialNumber=0
  [  556.990503] usb 1-4: Product: Touchscreen
  [  556.990506] usb 1-4: Manufacturer: ELAN
  [  556.990755] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc 
says 80 microframes
  [  557.001248] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A2/input/input2376
  [  557.002517] hid-multitouch 0003:04F3:0381.04A2: input,hiddev0,hidraw4: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0
  [  557.013831] usb 1-4: USB disconnect, device number 120

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-11-generic 4.2.0-11.13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bob2041 F pulseaudio
   /dev/snd/controlC0:  bob2041 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 23 09:46:25 2015
  HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12
  InstallationDate: Installed on 2013-12-26 (635 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite P50W-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-11-generic N/A
   linux-backports-modules-4.2.0-11-generic  N/A
   linux-firmware1.148
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2013-12-26 (635 days ago)
  dmi.bios.date: 08/08/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P50W-B
  dmi.product.version: PSVP2A-00F002
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498667/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1277959] Re: [Asus 1015E] Fn+F2 is not working for activating/deactivating wifi

[Christopher M. Penalver]

Xorso, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1277959

Title:
  [Asus 1015E] Fn+F2 is not working for activating/deactivating wifi

Status in linux package in Ubuntu:
  Expired

Bug description:
  Fn+F2 is not working for activating/deactivating wifi.
  Also wifi led is not working (led located on netbook case)
  I have an ASUS 1015E-DS03 netbook with Ubuntu 12.04 LTS.

  Linux ASUS-1015E-DS03 3.8.0-35-generic #52~precise1-Ubuntu SMP Thu Jan
  30 17:24:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  The problem maybe in asus_nb_wmi driver.
  Related to https://bugs.launchpad.net/bugs/1173681.

  description: Wireless interface
 product: AR9485 Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlan0
 version: 01
 serial: 6c:71:d9:7f:70:6b
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list rom ethernet 
physical wireless
 configuration: broadcast=yes driver=ath9k 
driverversion=3.8.0-35-generic firmware=N/A ip=192.168.1.47 latency=0 link=yes 
multicast=yes wireless=IEEE 802.11bgn
 resources: irq:17 memory:f7d0-f7d7 memory:f7d8-f7d8

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.8.0-35-generic 3.8.0-35.52~precise1
  ProcVersionSignature: Ubuntu 3.8.0-35.52~precise1-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-35-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1836 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e1 irq 44'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,1043115d,00100100 
HDA:80862806,80860101,0010'
 Controls  : 24
 Simple ctrls  : 9
  Date: Sat Feb  8 17:41:06 2014
  HibernationDevice: RESUME=UUID=046c9b4b-4f3f-45e2-8edf-e79abc412d11
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: ASUSTeK COMPUTER INC. 1015E
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic 
root=UUID=671caa58-b12e-4d13-a74e-a34bd55cff02 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-35-generic N/A
   linux-backports-modules-3.8.0-35-generic  N/A
   linux-firmware1.94
  SourcePackage: linux-lts-raring
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1015E.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 1015E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1015E.303:bd03/15/2013:svnASUSTeKCOMPUTERINC.:pn1015E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rn1015E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: 1015E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1277959/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1497627] Re: Periodically video will freeze for no reason at all and no specific time between freezes.

[Christopher M. Penalver]

chris pollock, to gather clarity to your Description:
>"What I expect to happen is the video to not freeze every so often."

Could you please provide specifically how often (ex. # times per day)?

To clarify
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/comments/47
does 4.3-rc4 allow you to test to this?

To clarify
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/comments/48
you are still using v4.2.3-unstable?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1497627

Title:
  Periodically video will freeze for no reason at all and no specific
  time between freezes.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  What I expect to happen is the video to not freeze every so often.
  What happened is that the video froze. This has been going on for over a 
year. It doesn't matter if I have any applications open such as Evolution or 
Firefox. It could happen any time during the day when I'm working on the 
computer or during the night when it's the most idle. Once the video freezes 
the cursor can still be moved around the desktop however clicking on anything 
does not work. During this time all background process and cronjobs continue to 
run.

  ---
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  2095 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bb329dc0-0642-4b6a-876a-12c2f02fb7f6
  InstallationDate: Installed on 2014-10-24 (332 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 780
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=4254a7e9-429b-4f53-a08c-ae7ff839b98f ro drm.debug=0xe plymouth:debug
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0C27VV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: LE0006476
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502944] Re: Laptop built-in keyboard is not working after kernel upgrade

[Christopher M. Penalver]

Robin Green, thank you for reporting this and helping make Ubuntu
better. Could you please provide the full computer model as noted on the
sticker of the computer itself (not from the Bug Description)?

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502944

Title:
  Laptop built-in keyboard is not working after kernel upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot enter my encryption password to unlock the hard drive because
  the keyboard does not work.

  Old working kernel: 3.19.0-28-generic
  Non-working kernel: 3.19.0-30-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-28-generic 3.19.0-28.30
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robin  1800 F pulseaudio
   /dev/snd/controlC1:  robin  1800 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Oct  5 16:37:40 2015
  HibernationDevice: RESUME=UUID=805a7dda-9be7-4a44-aaed-bbd91cc56268
  InstallationDate: Installed on 2015-05-05 (152 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   tun0  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216c Broadcom Corp. 
   Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 3938:1031  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2293
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn2293:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502944/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1503007] Re: mouse cursor disappears in Kubuntu with 3.19.0-30-generic kernel

[Christopher M. Penalver]

Alexus, could you please boot into http://cdimage.ubuntu.com/daily-
live/current/ and then perform the apport-collect?

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1503007

Title:
  mouse cursor disappears in Kubuntu with 3.19.0-30-generic kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Mouse cursor disappears in Kubuntu with 3.19.0-30-generic kernel.
  3.19.0-28 kernel - ok.

  
  CPU: Intel(R) Core(TM) i5-3320M 
  GPU: Intel® HD Graphics 4000
  Ubuntu 14.04.3 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503007/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1503005] Re: linux: 3.19.0-31.35 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1503005

Title:
  linux: 3.19.0-31.35 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-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 package in Ubuntu:
  New
Status in linux source package in Vivid:
  New

Bug description:
  This bug is for tracking the 3.19.0-31.35 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, 05. October 2015 18:56 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Monday, 05. October 2015 18:56 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1503005/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1503021] Re: linux: 3.13.0-66.107 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1503021

Title:
  linux: 3.13.0-66.107 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-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 package in Ubuntu:
  New
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.13.0-66.107 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, 05. October 2015 19:56 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Monday, 05. October 2015 19:56 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1503021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

[Craig Magina]

Here is a bit more of that code for context:

static int __init numa_register_memblks(struct numa_meminfo *mi)
{
unsigned long uninitialized_var(pfn_align);
int i, nid;

/* Account for nodes with cpus and no memory */
node_possible_map = numa_nodes_parsed;
numa_nodemask_from_meminfo(_possible_map, mi);
if (WARN_ON(nodes_empty(node_possible_map)))
return -EINVAL;

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

[Craig Magina]

The dump stack comes from this according to the trace:
if (WARN_ON(nodes_empty(node_possible_map)))

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

[Craig Magina]

ARM64 NUMA was added and enabled in 4.2.0-13.15, which apparently breaks
on the m400.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

[Scott Moser]

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502946

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1497627] Re: Periodically video will freeze for no reason at all and no specific time between freezes.

[chris pollock]

Currently no freeze yet though the uptime is only 19:33:45 up 2 days,
10:27. How long do you wish me to go if I don't see a freeze? Should I
drop to the kernel before this one at any time?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1497627

Title:
  Periodically video will freeze for no reason at all and no specific
  time between freezes.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  What I expect to happen is the video to not freeze every so often.
  What happened is that the video froze. This has been going on for over a 
year. It doesn't matter if I have any applications open such as Evolution or 
Firefox. It could happen any time during the day when I'm working on the 
computer or during the night when it's the most idle. Once the video freezes 
the cursor can still be moved around the desktop however clicking on anything 
does not work. During this time all background process and cronjobs continue to 
run.

  ---
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  2095 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bb329dc0-0642-4b6a-876a-12c2f02fb7f6
  InstallationDate: Installed on 2014-10-24 (332 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 780
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=4254a7e9-429b-4f53-a08c-ae7ff839b98f ro drm.debug=0xe plymouth:debug
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0C27VV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: LE0006476
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Wily:
  New
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1277959] Re: [Asus 1015E] Fn+F2 is not working for activating/deactivating wifi

[Xorso]

Same here!
Ubuntu 15.04
Asus B451JA

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1277959

Title:
  [Asus 1015E] Fn+F2 is not working for activating/deactivating wifi

Status in linux package in Ubuntu:
  Expired

Bug description:
  Fn+F2 is not working for activating/deactivating wifi.
  Also wifi led is not working (led located on netbook case)
  I have an ASUS 1015E-DS03 netbook with Ubuntu 12.04 LTS.

  Linux ASUS-1015E-DS03 3.8.0-35-generic #52~precise1-Ubuntu SMP Thu Jan
  30 17:24:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  The problem maybe in asus_nb_wmi driver.
  Related to https://bugs.launchpad.net/bugs/1173681.

  description: Wireless interface
 product: AR9485 Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlan0
 version: 01
 serial: 6c:71:d9:7f:70:6b
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list rom ethernet 
physical wireless
 configuration: broadcast=yes driver=ath9k 
driverversion=3.8.0-35-generic firmware=N/A ip=192.168.1.47 latency=0 link=yes 
multicast=yes wireless=IEEE 802.11bgn
 resources: irq:17 memory:f7d0-f7d7 memory:f7d8-f7d8

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.8.0-35-generic 3.8.0-35.52~precise1
  ProcVersionSignature: Ubuntu 3.8.0-35.52~precise1-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-35-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1836 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e1 irq 44'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,1043115d,00100100 
HDA:80862806,80860101,0010'
 Controls  : 24
 Simple ctrls  : 9
  Date: Sat Feb  8 17:41:06 2014
  HibernationDevice: RESUME=UUID=046c9b4b-4f3f-45e2-8edf-e79abc412d11
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: ASUSTeK COMPUTER INC. 1015E
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic 
root=UUID=671caa58-b12e-4d13-a74e-a34bd55cff02 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-35-generic N/A
   linux-backports-modules-3.8.0-35-generic  N/A
   linux-firmware1.94
  SourcePackage: linux-lts-raring
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1015E.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 1015E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1015E.303:bd03/15/2013:svnASUSTeKCOMPUTERINC.:pn1015E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rn1015E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: 1015E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1277959/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1436940] Re: Atheros wifi 168c:0041(QCA6174) is not supported

[Jeremy]

I got a confirmation that my DKMS version works with kernel 3.19, it
uses the backports-20150903 and atondwal firmware files

wget https://www.dropbox.com/s/nmgb5li6sd6i7ij/backath10k-dkms_2.0_all.deb
dpkg -i backath10k-dkms_2.0_all.deb

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1436940

Title:
  Atheros wifi 168c:0041(QCA6174) is not supported

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in linux source package in Wily:
  Confirmed

Bug description:
  The atheros wireless device (168c:0041) isn't supported by the
  ath10k_pci kernel driver.

  Found in several laptop models:

  Lenovo Z70
  Lenovo G50-45
  Lenovo G50-80
  Lenovo Edge 15
  Lenovo Yoga 3 11
  Lenovo Flex 3-1470
  Samsung ATIV Book 9 NP930X2K

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-9-generic 3.19.0-9.9
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicholas   1695 F pulseaudio
   /dev/snd/controlC1:  nicholas   1695 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 26 09:47:16 2015
  HibernationDevice: RESUME=UUID=5b068cd8-e60a-49b9-a88e-1581bb6b3dc1
  InstallationDate: Installed on 2015-03-25 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 003: ID 5986:0652 Acer, Inc
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80E5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=e52867c5-0b50-42fb-8288-f30765f926c5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-9-generic N/A
   linux-backports-modules-3.19.0-9-generic  N/A
   linux-firmware1.143SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-03-26 (0 days ago)
  dmi.bios.date: 06/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN69WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN69WW:bd06/20/2014:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.name: 80E5
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436940/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1173681] Re: 168c:002b [Asus U32U] asus_nb_wmi AR9285 ath9k not working after updating to Ubuntu 13.04 Raring

[Xorso]

Same here
Ubuntu 15.04
Asus B451JA
The tutorial helped:
http://ubuntuforums.org/showthread.php?t=2181558

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1173681

Title:
  168c:002b [Asus U32U] asus_nb_wmi AR9285 ath9k not working after
  updating to Ubuntu 13.04 Raring

Status in Linux:
  Invalid
Status in Linux Deepin:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  update: updated the BIOS to the latest version but the problem
  persists.

  Booting with the older kernel (latest linux kernel from 12.10) every thing 
works fine. After upgrading to Raring Ringtail Ubuntu 13.04, with the new 
kernel, hardware get blocked/disabled and wireless doesn't work:
  0: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: yes
  1: asus-wlan: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  WORKAROUND - is only applicable to Asus Notebooks/netbooks that use the 
"asus_nb_wmi" driver:
  Create and edit asus_nb_wmi.conf file with this command:
  sudo echo "options asus_nb_wmi wapf=4" | sudo tee 
/etc/modprobe.d/asus_nb_wmi.conf

  For more detailed info of the workaround please see:
  http://ubuntuforums.org/showthread.php?t=2181558

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-19-generic 3.8.0-19.29
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  x  1822 F pulseaudio
  CurrentDmesg:
   [  370.100280] r8169 :04:00.2 eth1: link up
   [  370.100322] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
   [  891.718748] systemd-hostnamed[2649]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
   [14119.241628] rtsx_pci :04:00.0: vpd r/w failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update.
  Date: Sat Apr 27 17:31:51 2013
  HibernationDevice: RESUME=UUID=e417e9f2-b63e-4b79-9be4-c21f55547205
  InstallationDate: Installed on 2012-07-13 (287 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: ASUSTeK Computer Inc. U32U
  MarkForUpload: True
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=3ad9d88b-a7a5-460f-ba15-a78dd7f2fc94 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-04-27 (0 days ago)
  dmi.bios.date: 12/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U32U.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U32U
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU32U.204:bd12/16/2011:svnASUSTeKComputerInc.:pnU32U:pvr1.0:rvnASUSTeKComputerInc.:rnU32U:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: U32U
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1173681/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1500854] Re: linux: 3.2.0-92.130 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1500854

Title:
  linux: 3.2.0-92.130 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-lbm series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.2.0-92.130 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, 29. September 2015 12:55 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 29. September 2015 12:55 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1500854/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1447790] Re: bluetooth not working after upgrading to 15.04

[BarryD9545]

I can send from Ubuntu to a Nexus 5, but cannot send from the phone to
Ubuntu, transfer starts, but no "accept" notification comes up.

Setting to always accept has no positive effect.

Pull down from notification shows only "Send Files..." for phone.
 Win7 laptop has no problems sending.receiving, and has all options in menu 
(Connection, Browse Files..., Send Files...)

Win7 has no problem send/receive to/from phone.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1447790

Title:
  bluetooth not working after upgrading to 15.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  Similar issue was already reported as #1406014

  After upgrading to 15.04 bluetooth is not working anymore:
  kernel: [9.421402] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A0-0a5c-21e6.hcd failed with error -2
  kernel: [9.421404] Bluetooth: hci0: BCM: patch 
brcm/BCM20702A0-0a5c-21e6.hcd not found

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dk 2597 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Apr 23 21:32:57 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=bc6f6d34-2f04-49c4-b1e0-00c509b8c0fb
  InstallationDate: Installed on 2013-08-16 (615 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: LENOVO 3460CLG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed 
root=UUID=895c87ae-1331-4119-acf2-4c54a7287e3b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago)
  dmi.bios.date: 06/12/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3460CLG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ETA7WW(2.67):bd06/12/2014:svnLENOVO:pn3460CLG:pvrThinkPadX1Carbon:rvnLENOVO:rn3460CLG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3460CLG
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447790/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1497627] Re: Periodically video will freeze for no reason at all and no specific time between freezes.

[chris pollock]

It's usually once a day but not every day. For instance I've gone as
many as 10 or 15 days without a freeze but as few as 1 1/2 days which
happened just recently. 4.3-rc4 would start the initial boot then all I
would see is a black screen. I've gathered the syslog info from that
boot attempt and attached it.  It must be completing the boot process
however since I can SSH into the system from my tablet and run 'sudo
reboot'. I could try again and post the dmesg or anything else you'd
like me to post. I'm still using 4.2.3-unstable dated 3 Oct 2015 and as
I stated above for the almost 2 1/2 days I had it running I had no
freezes. Also the video flickering when switching desktop windows has
stopped.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1497627

Title:
  Periodically video will freeze for no reason at all and no specific
  time between freezes.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  What I expect to happen is the video to not freeze every so often.
  What happened is that the video froze. This has been going on for over a 
year. It doesn't matter if I have any applications open such as Evolution or 
Firefox. It could happen any time during the day when I'm working on the 
computer or during the night when it's the most idle. Once the video freezes 
the cursor can still be moved around the desktop however clicking on anything 
does not work. During this time all background process and cronjobs continue to 
run.

  ---
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  2095 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bb329dc0-0642-4b6a-876a-12c2f02fb7f6
  InstallationDate: Installed on 2014-10-24 (332 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 780
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=4254a7e9-429b-4f53-a08c-ae7ff839b98f ro drm.debug=0xe plymouth:debug
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0C27VV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: LE0006476
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp