[Kernel-packages] [Bug 1508329] Re: CVE-2015-7799

2015-12-12 Thread Steve Beattie
** Changed in: linux-raspi2 (Ubuntu Xenial)
   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/1508329

Title:
  CVE-2015-7799

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-lts-wily 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-raspi2 package in Ubuntu:
  Fix Committed
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 Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily 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-raspi2 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:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 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-lts-wily 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-raspi2 source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package 

[Kernel-packages] [Bug 1510805] Re: CVE-2015-7990

2015-12-12 Thread Steve Beattie
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: New => Invalid

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

** Changed in: linux-lts-saucy (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/1510805

Title:
  CVE-2015-7990

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-lts-wily 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-raspi2 package in Ubuntu:
  New
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-lts-wily 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-raspi2 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-lts-wily 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-raspi2 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

[Kernel-packages] [Bug 1511577] Re: CVE-2015-8019

2015-12-12 Thread Steve Beattie
** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Invalid

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  CVE-2015-8019

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

[Kernel-packages] [Bug 1518483] Re: problem with PIE binaries and kernels <= 3.19

2015-12-12 Thread Steve Beattie
I've verified that the 3.19.0-41.46 kernel addresses the issue. Thanks!

** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

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

Title:
  problem with PIE binaries and kernels <= 3.19

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

Bug description:
  When bash is built as a Position Independent Executable (PIE), it very
  sporadically crashes due to some issue with memory layout in kernels
  before 4.2. I'm currently testing enabling PIE by default in gcc on
  amd64 for xenial, and some of my builds (e.g. cpio) are failing in the
  buildds with the following message emitted:

bash: xmalloc: .././locale.c:81: cannot allocate 2 bytes (0 bytes
  allocated)

  when the bash that is used is built as PIE. I have seen these failures
  on buildds where the host is running 3.13 and 3.19. I am also able to
  reproduce this locally on a machine running trusty with the stock
  trusty kernel. However, when I boot that same machine with the linux-
  lts-wily (4.2) kernel and retry the build with everything else exactly
  the same, the failure disappears.

  I discussed this a bit with Kees Cook, and he noted that some cleanups
  to the kernel's ASLR code happened in 4.1. Specifically, he noted:

commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86
Author: Michael Davidson 

  fs/binfmt_elf.c: fix bug in loading of PIE binaries
   
  However, that landed in stable and has been picked up in our kernels as 
668965be56ea0b2c45ed6bec84dc2088490ae6b1, landing in Ubuntu-3.13.0-56.93 and 
b51621abbcb4694b8d2842ce3a66006a60bba6e5 / Ubuntu-3.19.0-19.19.

  Kees also pointed out that he landed a series of patches from
  204db6ed17743000691d930368a5abd6ea541c58 until Michael Davidson's
  patch (i.e.
  
a87938b2e246b81b4fb713edb371a9fa3c5c3c86..204db6ed17743000691d930368a5abd6ea541c58
  ), and in particular, there's:

commit d1fd836dcf00d2028c700c7e44d2c23404062c90
Author: Kees Cook 

  mm: split ET_DYN ASLR from mmap ASLR
   
  Other fixes that I see to fs/binfmt_elf.c and arch/x86/mm/mmap.c look like 
they either occurred only in 4.3 or have already been backported via the stable 
kernels.

  I should also point out that these cleanups may address some of the
  ASLR failed tests that occur on non-x86 architectures for pre 4.2
  kernels.

  I am happy to test out kernels to try to address this. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-68-generic 3.13.0-68.111
  ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-68-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Nov 20 13:58:40 2015
  HibernationDevice: RESUME=UUID=dc63f523-507a-4f9d-aa30-a2e880199150
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Shuttle Inc SG33
  ProcEnviron:
   SHELL=/bin/bash
   TERM=screen
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic 
root=UUID=d30e91cf-3c43-41a9-a72d-c07d1be1d53e ro loop.max_loop=64 
rootflags=data=ordered nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-68-generic N/A
   linux-backports-modules-3.13.0-68-generic  N/A
   linux-firmware 1.127.18
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to trusty on 2014-04-16 (583 days ago)
  WpaSupplicantLog:
   
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: FG33
  dmi.board.vendor: Shuttle Inc
  dmi.board.version: V10
  dmi.chassis.type: 3
  dmi.chassis.vendor: Shuttle Inc
  dmi.chassis.version: G5
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/28/2007:svnShuttleInc:pnSG33:pvrV10:rvnShuttleInc:rnFG33:rvrV10:cvnShuttleInc:ct3:cvrG5:
  dmi.product.name: SG33
  dmi.product.version: V10
  dmi.sys.vendor: Shuttle Inc

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

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

[Kernel-packages] [Bug 1520878] Re: [MacBook8, 1] Speakers are muted

2015-12-12 Thread Christopher M. Penalver
Nell Hardcastle, this bug report is being closed due to your last
comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520878/comments/6
regarding you no longer have the hardware. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

Title:
  [MacBook8,1] Speakers are muted

Status in linux package in Ubuntu:
  Invalid

Bug description:
  There doesn't seem to be any way to unmute the laptop's speakers.
  Headphones work fine and I tried all of the available settings in
  alsamixer to see if any had an effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   nell   1292 F...m pulseaudio
   /dev/snd/controlC1:  nell   1292 F pulseaudio
nell   1676 F alsamixer
   /dev/snd/controlC0:  nell   1292 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov 28 20:54:52 2015
  IwConfig:
   enx00249b07662f  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Apple Inc. MacBook8,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=cda41380-82fb-4b7d-850e-c742811e2f45 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.153
  RfKill:
   
  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/31/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB81.88Z.0164.B08.1507311433
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-BE0E8AC46FE800CC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBook8,1
  dmi.chassis.asset.tag: Chassis Board Asset Tag#
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-BE0E8AC46FE800CC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB81.88Z.0164.B08.1507311433:bd07/31/2015:svnAppleInc.:pnMacBook8,1:pvr1.0:rvnAppleInc.:rnMac-BE0E8AC46FE800CC:rvrMacBook8,1:cvnAppleInc.:ct9:cvrMac-BE0E8AC46FE800CC:
  dmi.product.name: MacBook8,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1521749] Re: NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)

2015-12-12 Thread Christopher M. Penalver
hackeron, thank you for reporting this and helping make Ubuntu better.

As per https://downloadcenter.intel.com/product/85254/Intel-NUC-Kit-
NUC5CPYH an update to your computer's buggy and outdated BIOS is
available (0047). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement 
or not.
3) If the issue is still reproducible, please mark this report Status 
Confirmed. Otherwise, please mark this as Invalid.

Thank you for your understanding.

** Tags removed: 15.10 4.2.0 linux nuc nuc5cpyh
** Tags added: bios-outdated-0047

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

Title:
  NUC NUC5CPYH Does not boot on Ubuntu 15.10 (linux-image-4.2.0-19)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Intel NUC NUC5CPYH. This is the unit:
  http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5cpyh.html

  It boots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-
  image-3.19.0-34-generic -- but when I try to boot with  linux-
  image-4.2.0-19-generic  I simply see the following:

  https://www.dropbox.com/s/y2c9i87kafvwsq1/IMG_1476.jpg?dl=0

  The keyboard stops responding after this line: systemd[1]: Started
  udev Kernel Device Manager.

  Here is output from lspci -vnvn < http://pastie.org/10596250 - I am
  running headless, so there is no Xorg (or any other X server)
  installed.

  - I tried adding GRUB_CMDLINE_LINUX="nomodeset" (also: noacpi noapic)
  - I tried disabling devices in the bios like audio
  - Tried selecting "Ubuntu, with Linux 4.2.0-19-generic (recovery mode)" from 
the list, it does not boot into the recovery console either :(
  - I tried installing a clean 15.10 version on a blank hard drive (with 
debootstrap so latest packages)

  I am able to boot if I add systemd.unit=emergency.target to the kernel
  line. I can run "systemctl start networking" for example and it works,
  but if I run "systemctl start apport" (or ssh even) - I see this and
  the system freezes:

  https://www.dropbox.com/s/gmpse7bx0c70e4v/IMG_1479.jpg?dl=0

  I am not sure how to troubleshoot further. When I reboot and select
  Kernel 3.19, there is nothing in /var/log/syslog or journalctl from
  the failed boot :(

  Any suggestions?

  - EDIT: It seems downgrading from the latest PY0044 BIOS version to
  PY0043 allows me to boot the system, but it freezes if running
  "reboot" - more details in this bug report:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201

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

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


[Kernel-packages] [Bug 1522201] Re: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)

2015-12-12 Thread Christopher M. Penalver
hackeron, thank you for reporting this and helping make Ubuntu better.

As per https://downloadcenter.intel.com/product/85254/Intel-NUC-Kit-
NUC5CPYH an update to your computer's buggy and outdated BIOS is
available (0047). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement 
or not.
3) If the issue is still reproducible, please mark this report Status 
Confirmed. Otherwise, please mark this as Invalid.

Thank you for your understanding.

** Changed in: linux (Ubuntu)
   Importance: Critical => High

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

Title:
  NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Intel NUC NUC5CPYH. This is the unit:
  http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5cpyh.html

  It boots and reboots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with
  linux-image-3.19.0-34-generic -- but when I try to boot with linux-
  image-4.2.0-19-generic on the latest PY0044 BIOS version, it freezes
  on boot almost every time, reported bug here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749

  If I downgrade the BIOS to PY0043, it boots most of the time, but when
  I run "reboot" it freezes almost every single time. This is what I see
  on the screen when it freezes:

  https://www.dropbox.com/s/fxy4opcqwnmjmwo/IMG_1489.jpg?dl=0

  I am also attaching the full syslog, dmesg and the relevant part of
  the syslog when the system froze.

  I tried to boot with acpi_osi="Windows 2013" as well as Windows 2015
  and Windows 2009, that did not seem to make any difference.

  Any ideas?

  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10

  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=4fa37335-eed0-4580-ae4b-62c996dfc275 ro vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

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

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


[Kernel-packages] [Bug 1525569] Re: CVE-2015-8539

2015-12-12 Thread Steve Beattie
CVE-2015-8539

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

** Also affects: linux-fsl-imx51 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-mvl-dove (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-ec2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-maverick (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

** Also affects: linux-fsl-imx51 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-mvl-dove (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-ec2 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-maverick (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: 

[Kernel-packages] [Bug 1525569] [NEW] CVE-2015-8539

2015-12-12 Thread Steve Beattie
*** This bug is a security vulnerability ***

Public security bug reported:

[Fix handling of stored error in a negatively instantiated user key]

Break-Fix: - 096fe9eaea40a17e125569f9e657e34cdb6d73bd

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-ec2 (Ubuntu)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-fsl-imx51 (Ubuntu)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-lts-backport-maverick (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-lts-wily (Ubuntu)
 Importance: Medium
 Status: Invalid

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

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

** Affects: linux-mvl-dove (Ubuntu)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux-ec2 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-fsl-imx51 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-backport-maverick (Ubuntu Precise)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Precise)
 Importance: Undecided
 Status: New

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

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

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

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

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-mvl-dove (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Medium
 Status: New

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

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-ec2 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-fsl-imx51 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-backport-maverick (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

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

** Affects: 

[Kernel-packages] [Bug 1506914] Re: Screen brightness not working using keyboard shortcut fn+F5/F6 not working.

2015-12-12 Thread Christopher M. Penalver
Vidvranjek, which 4.4 kernel specifically did you test?

>"Should I report it as a separate bug?"

No, as that kernel is not supported here in Launchpad.

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

Title:
  Screen brightness not working using keyboard shortcut fn+F5/F6 not
  working.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  The fix is editing /etc/default/grub and replacing 

   GRUB_CMDLINE_LINUX_DEFAULT=""
  with
   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  run $ sudo update-grub
  reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.5
  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
  CurrentDesktop: Unity
  Date: Fri Oct 16 17:27:47 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:11cd]
 Subsystem: ASUSTeK Computer Inc. Device [1043:11cd]
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  MachineType: ASUSTeK COMPUTER INC. G550JK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=9a6cce6e-ddfb-40c7-a64c-823140602164 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G550JK.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G550JK
  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.:bvrG550JK.204:bd08/11/2014:svnASUSTeKCOMPUTERINC.:pnG550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Sat Oct 10 11:46:59 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [GLAMOR] failed to initialise EGL
   NOUVEAU(G0): Error creating GPU channel: -19
   NOUVEAU(G0): Error initialising acceleration.  Falling back to NoAccel
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12876 
   vendor SDC
  xserver.version: 2:1.17.1-0ubuntu3.1

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

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


[Kernel-packages] [Bug 1520878] Re: [MacBook8, 1] Speakers are muted

2015-12-12 Thread Nell Hardcastle
I no longer have the hardware to test with, 4.4-rc3 is the most recent
version I tested.

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

Title:
  [MacBook8,1] Speakers are muted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There doesn't seem to be any way to unmute the laptop's speakers.
  Headphones work fine and I tried all of the available settings in
  alsamixer to see if any had an effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   nell   1292 F...m pulseaudio
   /dev/snd/controlC1:  nell   1292 F pulseaudio
nell   1676 F alsamixer
   /dev/snd/controlC0:  nell   1292 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov 28 20:54:52 2015
  IwConfig:
   enx00249b07662f  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Apple Inc. MacBook8,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=cda41380-82fb-4b7d-850e-c742811e2f45 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.153
  RfKill:
   
  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/31/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB81.88Z.0164.B08.1507311433
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-BE0E8AC46FE800CC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBook8,1
  dmi.chassis.asset.tag: Chassis Board Asset Tag#
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-BE0E8AC46FE800CC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB81.88Z.0164.B08.1507311433:bd07/31/2015:svnAppleInc.:pnMacBook8,1:pvr1.0:rvnAppleInc.:rnMac-BE0E8AC46FE800CC:rvrMacBook8,1:cvnAppleInc.:ct9:cvrMac-BE0E8AC46FE800CC:
  dmi.product.name: MacBook8,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1516750] Re: CVE-2015-5327

2015-12-12 Thread Steve Beattie
** Changed in: linux-raspi2 (Ubuntu Xenial)
   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/1516750

Title:
  CVE-2015-5327

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

[Kernel-packages] [Bug 1509563] Re: CVE-2015-7837

2015-12-12 Thread Steve Beattie
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: New => Invalid

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

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

Title:
  CVE-2015-7837

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-lts-wily 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-raspi2 package in Ubuntu:
  New
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-lts-wily 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-raspi2 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-lts-wily 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-raspi2 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-lts-wily 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-raspi2 source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package 

[Kernel-packages] [Bug 1513297] Re: XE500C12-K01US Samsung Chromebook 2 Ubuntu 14.04 touchpad not responsive

2015-12-12 Thread rgkirch
I don't have a URL for the patch. He emailed it to me so that I could
start using it right away. I don't know when it will be a part of the
kernel.

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

Title:
  XE500C12-K01US Samsung Chromebook 2 Ubuntu 14.04 touchpad not
  responsive

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The touchpad is not responsive at all. It worked fine with chomium os
  but not ubuntu. I'm totally willing to work with you guys to get this
  fixed. Ubuntu 14.04.3 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Nov  4 22:14:54 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation ValleyView Gen7 [8086:0f31]
  InstallationDate: Installed on 2015-11-04 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 2232:1068  
   Bus 001 Device 005: ID 04e8:6863 Samsung Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Winky
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=ee476124-1af2-4cf8-8bd6-f0bcf555b924 ro acpi_backlight=vendor
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd09/19/2014:svnGOOGLE:pnWinky:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Winky
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  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.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  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: Wed Nov  4 19:45:44 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4188 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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


[Kernel-packages] [Bug 1465439] Re: "Can't eject cd rom : Inappropriate ioctl for device"

2015-12-12 Thread Elven Decker
I have the same issue.  I suspect something unique about our DVD drives
or the way they are defined.

sudo lshw -C disk gives

  *-cdrom
   description: DVD reader
   product: COMBO SOHC-4836V
   vendor: LITE-ON
   physical id: 0.0.0
   bus info: scsi@0:0.0.0
   logical name: /dev/cdrom
   logical name: /dev/cdrw
   logical name: /dev/dvd
   logical name: /dev/sr0
   logical name: /mnt/cdrom
   version: SG$4
   capabilities: removable audio cd-r cd-rw dvd
   configuration: ansiversion=5 mount.fstype=udf 
mount.options=ro,relatime,utf8 state=mounted status=nodisc

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

Title:
  "Can't eject cd rom : Inappropriate ioctl for device"

Status in linux package in Ubuntu:
  Expired

Bug description:
  Can't eject an empty CD-Rom tray.

  None of the things suggested here
  (https://bugs.launchpad.net/ubuntu/+source/udev/+bug/875543) work. At
  best, working from a console, I get the message above. At worst, the
  CD drawer "grunts" as though trying to eject, but doesn't open.

  Using a paperclip to push the hidden manual release does work, and
  once the tray has a CD in it, it ejects every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  geoff  1662 F pulseaudio
geoff  1965 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDesktop: LXDE
  Date: Tue Jun 16 11:28:07 2015
  HibernationDevice: RESUME=UUID=eac9009f-2935-4961-9d6f-db25ad14f170
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 320
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=8b5a8fc6-806e-425f-a86c-3eec3f7836b0 ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-45-generic N/A
   linux-backports-modules-3.13.0-45-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.2
  dmi.board.name: 0MH651
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.2:bd12/04/2006:svnDellInc.:pnOptiPlex320:pvr:rvnDellInc.:rn0MH651:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: OptiPlex 320
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1525598] [NEW] aMule unable to connect to kad 3.13.0-71

2015-12-12 Thread Pablo Merighi
Public bug reported:

The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
Description:Ubuntu 14.04.3 LTS
Release:14.04

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


** Tags: 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/1525598

Title:
  aMule unable to connect to kad 3.13.0-71

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

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

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


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

2015-12-12 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1525598

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: trusty

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

Title:
  aMule unable to connect to kad 3.13.0-71

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

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

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


[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

2015-12-12 Thread Nucleo
Hello,

the above fix, copying files into the correct location worked until this
upgrade came through:

upgrade network-manager:amd64 1.0.4-0ubuntu5.1 1.0.4-0ubuntu5.2

now it seems ath10k is not loading.

if I do a manual sudo modprobe force ath10k_pci

it lists in lsmod, but networkmanager seems to not care. maybe this is a
network manager problem, not for this post?

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Status in HWE Next:
  Fix Released
Status in HWE Next wily series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux-firmware source package in Wily:
  Fix Released

Bug description:
  =

  CURRENT STATUS:

  Wily(15.10) could not work with and don't need Adam's dkms package 1.0
  or 1.1

  Wily(15.10) has already fixed the driver part, and the firmware part
  is in progress.

  For now, you guys could use 15.10(purge the ath10k-dkms if you tried
  installing it), and make a copy of
  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/

  15.10 will work in a week by a simple `apt upgrade`

  Distros before 15.10(lower than 4.2 kernel) please keep using the
  dkms(which will be relocated soon)

  =

  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  ---
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.

   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

  Qualcomm Atheros Device [168c:003e] (rev 20)

  mainline commit d63955b33b3bee45d784ffdfafeb93076c765660

  [6.221281] ath10k_pci :02:00.0: pci irq msi interrupts 1 irq_mode 0 
reset_mode 0
  [6.417386] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [6.417404] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2
  [6.417407] ath10k_pci :02:00.0: failed to load spec board file, 
falling back to generic: -2
  [6.417416] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board.bin failed with error -2
  [6.417418] ath10k_pci :02:00.0: failed to fetch generic board data: -2
  [6.417420] ath10k_pci :02:00.0: failed to fetch board file: -2
  [  

[Kernel-packages] [Bug 1476211] Re: kswapd takes 100% CPU although there is no swap

2015-12-12 Thread cp
Update: Even with no swap (partition/file) attached the kswapd0 is
generating 100% cpu load.

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

Title:
  kswapd takes 100% CPU although there is no swap

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a notebook with neither swap partition nor swap file (because of
  SSD and surplus of RAM), kswapd0 suddenly runs amok and takes 100% of
  CPU activity. When this happens, usually at most 5.5 of 8 GB RAM were
  in use, so there is no reason to swap.

  This happens so suddenly, that no user input is possible anymore, eg.
  I can barely switch to tty to kill processes that take most RAM. The
  processor becomes extremely hot and I can only turn the computer off
  and reboot. I  consider this as critical and harmful to my hardware.

  I noticed that Ubuntu installs by default with swappiness 60. Now I
  changed that to 10 because I would never encounter the case that 8GB
  are in use, but it didn't have an effect.

  Expected behavior:
  - on systems without RAM, kswapd should never attempt to swap
  - if there is not enough RAM, kernel should kill processes to free up RAM
  - no process should be able to claim so much CPU activity, that the computer 
becomes unresponsive (it should always be possible to control/stop/kill 
processes over tty)

  Actual behavior:
  - kswapd tries to swap although there is no swap space

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-22-generic 3.19.0-22.22
  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:  andreas2368 F pulseaudio
   /dev/snd/controlC0:  andreas2368 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 20 12:49:24 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-06-06 (43 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20266
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic 
root=UUID=8a0dc2f3-fcf3-4e5b-8e23-1441bd36e3dc ro noprompt persistent quiet 
splash acpi_backlight=vendor vt.handoff=7 init=/sbin/upstart
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-22-generic N/A
   linux-backports-modules-3.19.0-22-generic  N/A
   linux-firmware 1.143.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1140716]

2015-12-12 Thread Chris Wilson
*** Bug 93331 has been marked as a duplicate of this bug. ***

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

Title:
  [regression] 3.5.0-26-generic and  3.2.0-39-generic GPU hangs on
  Sandybridge

Status in DRI:
  In Progress
Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-quantal source package in Precise:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in mesa source package in Precise:
  Triaged
Status in linux source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux source package in Raring:
  Invalid
Status in linux-lts-quantal source package in Raring:
  Invalid
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  I'm getting errors about GPU hangs every minute or so (usually only
  when using FF and scrolling a webpage or something). I also get an
  annoying ubuntu dialog saying there is a "system error".

  This didn't happen with 3.5.0-24-generic.

  Here is the dmesg:
  [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.658405] [ cut here ]
  [26285.658472] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26285.658474] Hardware name: SATELLITE Z830
  [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm 
arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel 
snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep 
iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi 
rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer 
snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap 
soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei 
video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc 
lp parport e1000e ahci libahci [last unloaded: sdhci]
  [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic 
#40-Ubuntu
  [26285.658539] Call Trace:
  [26285.658549]  [] warn_slowpath_common+0x7f/0xc0
  [26285.658553]  [] warn_slowpath_null+0x1a/0x20
  [26285.658569]  [] gen6_enable_rps+0x706/0x710 [i915]
  [26285.658584]  [] intel_modeset_init_hw+0x66/0xa0 [i915]
  [26285.658595]  [] i915_reset+0x1a4/0x6e0 [i915]
  [26285.658601]  [] ? __switch_to+0x12b/0x420
  [26285.658612]  [] i915_error_work_func+0xc3/0x110 [i915]
  [26285.658618]  [] process_one_work+0x12a/0x420
  [26285.658629]  [] ? gen6_pm_rps_work+0xe0/0xe0 [i915]
  [26285.658632]  [] worker_thread+0x12e/0x2f0
  [26285.658636]  [] ? manage_workers.isra.26+0x200/0x200
  [26285.658640]  [] kthread+0x93/0xa0
  [26285.658644]  [] kernel_thread_helper+0x4/0x10
  [26285.658649]  [] ? kthread_freezable_should_stop+0x70/0x70
  [26285.658652]  [] ? gs_change+0x13/0x13
  [26285.658654] ---[ end trace 59c6162fdfcbffee ]---
  [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.384285] [ cut here ]
  [26932.384354] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26932.384356] Hardware name: SATELLITE Z830
  [26932.384358] Modules linked in: sdhci_pci 

[Kernel-packages] [Bug 1492764] Re: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)

2015-12-12 Thread Bug Watch Updater
Launchpad has imported 10 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=91511.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-07-30T17:38:44+00:00 Gabriele-mzt wrote:

Created attachment 117467
dmesg - warning when switching from X to tty

Using 4.2-rc4 on my Haswell laptop I get the warning you can see in the
dmesg attached whenever I switch from X to tty. The same happens using
4.2-rc1.

This never happened before.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492764/comments/0


On 2015-08-25T23:58:04+00:00 Gabriele-mzt wrote:

This issue seems to have been fixed in v4.2-rc8. Closing this.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492764/comments/1


On 2015-08-31T09:38:37+00:00 Jonathan McDowell wrote:

I am seeing this on a Dell E7240 (Haswell) freshly booted into 4.2. The
issue was not seen on 4.1.2 or previous.

[ 2698.293746] [drm:check_crtc_state] *ERROR* mismatch in ips_enabled (expected 
1, found 0)
[ 2698.293753] [ cut here ]
[ 2698.293761] WARNING: CPU: 0 PID: 1833 at 
drivers/gpu/drm/i915/intel_display.c:12324 check_crtc_state+0x8ab/0xfd0()
[ 2698.293763] pipe state doesn't match!
[ 2698.293780] Modules linked in: fuse ctr ccm xt_addrtype xt_conntrack 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat 
nf_conntrack bridge stp llc dm_thin_pool dm_persistent_data dm_bio_prison 
dm_bufio libcrc32c loop binfmt_misc bnep nfsd auth_rpcgss oid_registry nfs_acl 
nfs lockd grace fscache sunrpc arc4 nls_utf8 nls_cp437 vfat fat qmi_wwan 
uvcvideo videobuf2_vmalloc videobuf2_memops iwlmvm videobuf2_core cdc_mbim 
v4l2_common cdc_ncm cdc_wdm videodev usbnet mii mac80211 media 
snd_hda_codec_hdmi dell_smm_hwmon intel_rapl iosf_mbi x86_pkg_temp_thermal 
intel_powerclamp btusb snd_hda_codec_realtek snd_hda_codec_generic joydev 
iwlwifi btintel bluetooth pcspkr efivars i2c_i801 sg snd_hda_intel cfg80211 
snd_hda_codec
[ 2698.293911]  snd_hwdep snd_hda_core snd_pcm snd_timer tpm_tis 8250 
serial_core evdev battery ac processor md_mod tpm_rng tpm rng_core efivarfs 
autofs4 btrfs xor raid6_pq algif_skcipher af_alg crct10dif_pclmul crc32_pclmul 
crc32c_intel ghash_clmulni_intel ehci_pci ehci_hcd sdhci_pci xhci_pci xhci_hcd 
thermal sdhci_acpi sdhci mmc_core i2c_hid hid jitterentropy_rng sha256_ssse3 
sha256_generic hmac drbg ansi_cprng
[ 2698.293977] CPU: 0 PID: 1833 Comm: Xorg Not tainted 4.2.0 #1
[ 2698.293980] Hardware name: Dell Inc. Latitude E7240/07RPNV, BIOS A15 
05/19/2015
[ 2698.293998]   819c26e0 816898ee 
8804030bf858
[ 2698.294004]  810b394c 8800d5ba9400 88040c3d1000 
88040ab4
[ 2698.294009]  0001 88040c3d1350 810b39c5 
819f0f1f
[ 2698.294015] Call Trace:
[ 2698.294024]  [] ? dump_stack+0x40/0x50
[ 2698.294048]  [] ? warn_slowpath_common+0x7c/0xb0
[ 2698.294054]  [] ? warn_slowpath_fmt+0x45/0x50
[ 2698.294059]  [] ? check_crtc_state+0x8ab/0xfd0
[ 2698.294066]  [] ? i915_get_crtc_scanoutpos+0x18b/0x230
[ 2698.294093]  [] ? intel_modeset_check_state+0x206/0xb10
[ 2698.294101]  [] ? intel_crtc_set_config+0x529/0x590
[ 2698.294108]  [] ? drm_crtc_check_viewport+0x27/0xe0
[ 2698.294130]  [] ? drm_mode_set_config_internal+0x59/0xf0
[ 2698.294137]  [] ? drm_mode_setcrtc+0x17f/0x4d0
[ 2698.294143]  [] ? drm_ioctl+0x16d/0x550
[ 2698.294151]  [] ? evdev_read+0xc0/0x2c0 [evdev]
[ 2698.294175]  [] ? do_vfs_ioctl+0x2be/0x490
[ 2698.294183]  [] ? recalc_sigpending+0x12/0x50
[ 2698.294189]  [] ? SyS_ioctl+0x71/0x80
[ 2698.294194]  [] ? SyS_rt_sigprocmask+0x60/0xa0
[ 2698.294217]  [] ? entry_SYSCALL_64_fastpath+0x12/0x6a
[ 2698.294221] ---[ end trace c252f4cf31b49867 ]---

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492764/comments/2


On 2015-09-01T16:13:31+00:00 Freedesktop-3 wrote:

Reverting d2944cf21305c754fa8b2d6c1eea05ad5dad7944 fixes 4.2 for me.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492764/comments/3


On 2015-09-02T11:57:24+00:00 Jani-nikula wrote:

(In reply to Emil Renner Berthing from comment #3)
> Reverting d2944cf21305c754fa8b2d6c1eea05ad5dad7944 fixes 4.2 for me.

commit d2944cf21305c754fa8b2d6c1eea05ad5dad7944
Author: Maarten Lankhorst 
Date:   Tue Aug 11 12:31:11 2015 +0200

drm/i915: Commit planes on each 

[Kernel-packages] [Bug 1520988] Re: Copy of large files from USB3 card reader fails mid-way

2015-12-12 Thread Kevin Brubeck Unhammer
jsalisbury, I tried the 4.4.0-040400rc3 kernel, but it never found my
harddrive (it gave up waiting for root device, couldn't find it by uuid,
dropped me to ash/initramfs, couldn't even use my usb keyboard so had to
long-press power to reboot). Does this warrant a new bug, or are there
new settings that should be applied when trying 4.4?

penalvch, the update from Lenovo is for Broadwell systems; mine is a
Haswell. I tried the newest .exe, but it won't install from my Windows
dual-boot (saying it's incompatible), just like the page
http://support.lenovo.com/no/nn/products/desktops-and-all-in-
ones/lenovo-a-series-all-in-ones/lenovo-a740-all-in-
one/downloads/DS102570 claims. This is the same machine as in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463422/comments/8

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

Title:
  Copy of large files from USB3 card reader fails mid-way

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've got a "Lexar Professional Workflow XR1" CF card reader that
  supports USB3, and has worked fine for regular JPG/CR2 images (sizes
  up to about 20 MB), but when I tried some videos (which were 170MB and
  up), the copy would fail around midway with "Error Splicing File:
  Input/Output Error" from Thunar, and dmesg showed messages like:

  [  +9,232995] usb 2-3: Disable of device-initiated U1 failed.
  [  +5,006028] usb 2-3: Disable of device-initiated U2 failed.
  [  +0,168540] usb 2-3: reset SuperSpeed USB device number 10 using xhci_hcd
  [  +1,126795] sd 12:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [  +0,11] sd 12:0:0:0: [sdb] Sense Key : Unit Attention [current] 
  [  +0,07] sd 12:0:0:0: [sdb] Add. Sense: Not ready to ready change, 
medium may have changed
  [  +0,06] sd 12:0:0:0: [sdb] CDB: Read(10) 28 00 00 67 53 ce 00 00 02 00
  [  +0,05] blk_update_request: I/O error, dev sdb, sector 6771662
  [  +0,08] Buffer I/O error on dev sdb1, logical block 3385704, async page 
read
  [ +10,494574] usb 2-3: Disable of device-initiated U1 failed.
  [  +5,006046] usb 2-3: Disable of device-initiated U2 failed.
  [  +0,168624] usb 2-3: reset SuperSpeed USB device number 10 using xhci_hcd
  [  +1,126823] sd 12:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [  +0,09] sd 12:0:0:0: [sdb] Sense Key : Unit Attention [current] 
  [  +0,05] sd 12:0:0:0: [sdb] Add. Sense: Not ready to ready change, 
medium may have changed
  [  +0,05] sd 12:0:0:0: [sdb] CDB: Read(10) 28 00 00 68 53 76 00 00 02 00
  [  +0,03] blk_update_request: I/O error, dev sdb, sector 6837110
  [  +0,07] Buffer I/O error on dev sdb1, logical block 3418428, async page 
read

  I tried a fsck.vfat, but that didn't help. Ejecting and unmounting, I
  was able to copy one file, but not the rest (tried a couple times,
  just got the same errors).

  This computer only has USB3 ports. So I tried another computer
  (running Xubuntu 14.04) that had a non-USB3-port, and there the copy
  worked just fine.

  
  On connecting, dmesg says:

  [nov.29 20:56] usb 2-3: new SuperSpeed USB device number 12 using xhci_hcd
  [  +0,018698] usb 2-3: New USB device found, idVendor=05dc, idProduct=ba02
  [  +0,08] usb 2-3: New USB device strings: Mfr=3, Product=4, 
SerialNumber=5
  [  +0,05] usb 2-3: Product: WorkflowCFR1
  [  +0,03] usb 2-3: Manufacturer: Lexar
  [  +0,04] usb 2-3: SerialNumber: 5018
  [  +0,002362] usb-storage 2-3:1.0: USB Mass Storage device detected
  [  +0,000135] scsi host14: usb-storage 2-3:1.0
  [  +1,000955] scsi 14:0:0:0: Direct-Access LexarWorkflowCFR1 0822 
PQ: 0 ANSI: 6
  [  +0,000297] sd 14:0:0:0: Attached scsi generic sg1 type 0
  [  +1,104094] sd 14:0:0:0: [sdb] 62537328 512-byte logical blocks: (32.0 
GB/29.8 GiB)
  [  +0,000598] sd 14:0:0:0: [sdb] Write Protect is off
  [  +0,09] sd 14:0:0:0: [sdb] Mode Sense: 23 00 00 00
  [  +0,000646] sd 14:0:0:0: [sdb] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
  [  +0,004239]  sdb: sdb1
  [  +0,001969] sd 14:0:0:0: [sdb] Attached SCSI removable disk

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kiwibird   1912 F pulseaudio
   /dev/snd/controlC1:  kiwibird   1912 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Nov 29 20:52:51 2015
  HibernationDevice: RESUME=UUID=dc4226ca-3ebe-4611-95ac-c1a0ccbb7d7a
  InstallationDate: Installed on 2015-06-04 (178 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: LENOVO F0AM
  ProcFB: 0 inteldrmfb

[Kernel-packages] [Bug 1476211] Re: kswapd takes 100% CPU although there is no swap

2015-12-12 Thread cp
After upgrading to Xubuntu 15.10 on 2 home server boxes I am
experiencing a similar problem: kswapd0 uses 99,9% of CPU. The only way
to make it stop is to issue the swapoff command. When I try to issue
swapon again it automatically produces 99,9% of CPU load again. (Even if
the swap isn’t getting filled)

Any clue about that? It’s really annoying.

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

Title:
  kswapd takes 100% CPU although there is no swap

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a notebook with neither swap partition nor swap file (because of
  SSD and surplus of RAM), kswapd0 suddenly runs amok and takes 100% of
  CPU activity. When this happens, usually at most 5.5 of 8 GB RAM were
  in use, so there is no reason to swap.

  This happens so suddenly, that no user input is possible anymore, eg.
  I can barely switch to tty to kill processes that take most RAM. The
  processor becomes extremely hot and I can only turn the computer off
  and reboot. I  consider this as critical and harmful to my hardware.

  I noticed that Ubuntu installs by default with swappiness 60. Now I
  changed that to 10 because I would never encounter the case that 8GB
  are in use, but it didn't have an effect.

  Expected behavior:
  - on systems without RAM, kswapd should never attempt to swap
  - if there is not enough RAM, kernel should kill processes to free up RAM
  - no process should be able to claim so much CPU activity, that the computer 
becomes unresponsive (it should always be possible to control/stop/kill 
processes over tty)

  Actual behavior:
  - kswapd tries to swap although there is no swap space

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-22-generic 3.19.0-22.22
  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:  andreas2368 F pulseaudio
   /dev/snd/controlC0:  andreas2368 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 20 12:49:24 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-06-06 (43 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20266
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic 
root=UUID=8a0dc2f3-fcf3-4e5b-8e23-1441bd36e3dc ro noprompt persistent quiet 
splash acpi_backlight=vendor vt.handoff=7 init=/sbin/upstart
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-22-generic N/A
   linux-backports-modules-3.19.0-22-generic  N/A
   linux-firmware 1.143.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1525582] [NEW] share files

2015-12-12 Thread Josué
Public bug reported:

Not sure if it comes here... but well.
In ubuntu touch (OTA 8) using gallery, camera or other apps an option to share 
through bluetooth is missing...

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


** Tags: bluetooth share touch

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

Title:
  share files

Status in bluez package in Ubuntu:
  New

Bug description:
  Not sure if it comes here... but well.
  In ubuntu touch (OTA 8) using gallery, camera or other apps an option to 
share through bluetooth is missing...

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

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


[Kernel-packages] [Bug 1525570] [NEW] CVE-2015-8543

2015-12-12 Thread Steve Beattie
*** This bug is a security vulnerability ***

Public security bug reported:

[IPv6 connect causes a denial of service]

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-ec2 (Ubuntu)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-fsl-imx51 (Ubuntu)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-lts-backport-maverick (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-lts-wily (Ubuntu)
 Importance: Medium
 Status: Invalid

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

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

** Affects: linux-mvl-dove (Ubuntu)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux-ec2 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-fsl-imx51 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-backport-maverick (Ubuntu Precise)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Precise)
 Importance: Undecided
 Status: New

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

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

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

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

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-mvl-dove (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Medium
 Status: New

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

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-ec2 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-fsl-imx51 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-backport-maverick (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

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

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

** Affects: 

[Kernel-packages] [Bug 1525570] Re: CVE-2015-8543

2015-12-12 Thread Steve Beattie
CVE-2015-8543

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

** Also affects: linux-fsl-imx51 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-mvl-dove (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-ec2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-maverick (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

** Also affects: linux-fsl-imx51 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-mvl-dove (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-ec2 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-maverick (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: 

[Kernel-packages] [Bug 1521848] Re: Toshiba Satellite L50-AST2NX3 touchpad does not work after kernal update

2015-12-12 Thread Seaver Thorn
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.4-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/1521848

Title:
  Toshiba Satellite L50-AST2NX3 touchpad does not work after kernal
  update

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Ever since 2 days ago, I cannot get the touchpad on my Toshiba Laptop
  to work with Ubuntu. It works fine on Windows (dual booting.) It
  worked before that, and i'm guessing an update messed something up.
  This happened once before, but an update fixed the issue before I
  reported it. I'm not sure what the deal is, but let me know if there's
  anything else I can provide to help you fix the issue.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seaver 2039 F pulseaudio
   /dev/snd/controlC1:  seaver 2039 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec  1 23:21:06 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-03 (28 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: TOSHIBA Satellite L50-A
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=f06955e3-4b16-46c5-839b-eccf9692643a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.2
  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: 04/28/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  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.80:bd04/28/2014:svnTOSHIBA:pnSatelliteL50-A:pvrPSKLJU-00D004:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L50-A
  dmi.product.version: PSKLJU-00D004
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1525509] Re: regression on 4.3.x: i945/Display corruption (before X, X never starts))

2015-12-12 Thread Dave Gilbert
The 4.4.0-999-generic daily (201512120150) seems to work.
Although there's a whole bunch of slowpath warnings in the logs.
(I say seems to work - I'm running it now in KDE apparently OK; on the first 
boot the desktop didn't complete starting up but ti wasn't obvious why, X was 
still responsive just apps didn't start; but that seems different?)

Here's the current boot warnings in the working 4.4:
[4.012238] [ cut here ]
[4.012339] WARNING: CPU: 0 PID: 143 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:1407 
assert_planes_disabled+0x102/0x140 [i915]()
[4.012358] plane B assertion failure, should be off on pipe B but is still 
active
[4.012373] Modules linked in: psmouse sdhci_pci pata_acpi(+) i915(+) e100 
mii firewire_ohci i2c_algo_bit drm_kms_helper sdhci syscopyarea sysfillrect 
firewire_core sysimgblt crc_itu_t fb_sys_fops drm fjes video
[4.012436] CPU: 0 PID: 143 Comm: systemd-udevd Not tainted 
4.4.0-999-generic #201512120150
[4.012452] Hardware name: TOSHIBA Equium A100/MPAD-MSAE Customer Reference 
Boards, BIOS 2.1010/23/2006
[4.012468]   9cbb9ea2 8800354a3608 
813c8b04
[4.012487]  8800354a3650 8800354a3640 8107d692 
88003567
[4.012506]  0001 0042 0042 
880035670034
[4.012525] Call Trace:
[4.012541]  [] dump_stack+0x44/0x60
[4.012555]  [] warn_slowpath_common+0x82/0xc0
[4.012567]  [] warn_slowpath_fmt+0x5c/0x80
[4.012626]  [] ? gen2_read32+0x28/0x90 [i915]
[4.012670]  [] assert_planes_disabled+0x102/0x140 [i915]
[4.012715]  [] intel_disable_pipe+0x4b/0x2c0 [i915]
[4.012745]  [] ? drm_crtc_vblank_get+0x1c/0x20 [drm]
[4.012790]  [] i9xx_crtc_disable+0x7f/0x450 [i915]
[4.012834]  [] ? intel_crtc_disable_planes+0xdc/0xf0 
[i915]
[4.012881]  [] intel_crtc_disable_noatomic+0x66/0xe0 
[i915]
[4.012928]  [] intel_modeset_setup_hw_state+0xac1/0xdd0 
[i915]
[4.012977]  [] intel_modeset_init+0x939/0x11e0 [i915]
[4.013026]  [] i915_driver_load+0xaf8/0xf30 [i915]
[4.013036]  [] ? netlink_broadcast_filtered+0x137/0x3c0
[4.013044]  [] ? cleanup_uevent_env+0x10/0x10
[4.013052]  [] ? kobject_uevent_env+0x15b/0x640
[4.013060]  [] ? get_device+0x17/0x20
[4.013068]  [] ? klist_class_dev_get+0x15/0x20
[4.013077]  [] ? klist_node_init+0x37/0x50
[4.013084]  [] ? klist_add_tail+0x20/0x50
[4.013091]  [] ? device_add+0x232/0x680
[4.013112]  [] drm_dev_register+0xa7/0xb0 [drm]
[4.013133]  [] drm_get_pci_dev+0x8d/0x1e0 [drm]
[4.013169]  [] i915_pci_probe+0x34/0x50 [i915]
[4.013179]  [] local_pci_probe+0x45/0xa0
[4.013187]  [] pci_device_probe+0x103/0x150
[4.013194]  [] driver_probe_device+0x222/0x4a0
[4.013202]  [] __driver_attach+0x84/0x90
[4.013209]  [] ? driver_probe_device+0x4a0/0x4a0
[4.013217]  [] bus_for_each_dev+0x6c/0xc0
[4.013224]  [] driver_attach+0x1e/0x20
[4.013231]  [] bus_add_driver+0x1eb/0x280
[4.013238]  [] driver_register+0x60/0xe0
[4.013246]  [] __pci_register_driver+0x4c/0x50
[4.013266]  [] drm_pci_init+0xe0/0x110 [drm]
[4.013274]  [] ? 0xc023d000
[4.013304]  [] i915_init+0x92/0x99 [i915]
[4.013313]  [] do_one_initcall+0xb3/0x200
[4.013321]  [] ? __vunmap+0x91/0xe0
[4.013329]  [] ? kmem_cache_alloc_trace+0x16b/0x1d0
[4.013336]  [] ? kfree+0x115/0x130
[4.013345]  [] do_init_module+0x5f/0x1e5
[4.013353]  [] load_module+0x1603/0x1b70
[4.013361]  [] ? __symbol_put+0x60/0x60
[4.013371]  [] ? kernel_read+0x50/0x80
[4.013378]  [] SyS_finit_module+0xb9/0xf0
[4.013387]  [] entry_SYSCALL_64_fastpath+0x16/0x75
[4.013394] ---[ end trace 3fb1b9aef1f5 ]---
[4.036648] [drm] initialized overlay support
[4.036677] [drm] Initialized i915 1.6.0 20151010 for :00:02.0 on minor 0
[4.056412] [ cut here ]
[4.056491] WARNING: CPU: 1 PID: 6 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:11683 
intel_plane_atomic_calc_changes+0x567/0x6c0 [i915]()
[4.056503] WARN_ON(was_visible)
[4.056506] Modules linked in:
[4.056512]  psmouse sdhci_pci pata_acpi i915 e100 mii firewire_ohci 
i2c_algo_bit drm_kms_helper sdhci syscopyarea sysfillrect firewire_core 
sysimgblt crc_itu_t fb_sys_fops drm fjes video
[4.056547] CPU: 1 PID: 6 Comm: kworker/u4:0 Tainted: GW   
4.4.0-999-generic #201512120150
[4.056558] Hardware name: TOSHIBA Equium A100/MPAD-MSAE Customer Reference 
Boards, BIOS 2.1010/23/2006
[4.056572] Workqueue: events_unbound async_run_entry_fn
[4.056579]   6a781c97 8800bb7df888 
813c8b04
[4.056590]  8800bb7df8d0 8800bb7df8c0 8107d692 
0001
[4.056601]  880035a0f000 88003551f900 8800bb2b 
0001
[4.056613] Call Trace:
[4.056623]  [] 

[Kernel-packages] [Bug 1525587] [NEW] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)

2015-12-12 Thread Lothar-dierkes
Public bug reported:

[  +0,145801] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
ips_enabled (expected 1, found 0)
[  +0,03] [ cut here ]
[  +0,16] WARNING: CPU: 0 PID: 980 at 
/build/linux-1vdNXv/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12328 
check_crtc_state+0x2c5/0x440 [i915]()
[  +0,01] pipe state doesn't match!
[  +0,01] Modules linked in: rfcomm bnep arc4 hp_wmi joydev sparse_keymap 
intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm snd_hda_co
[  +0,41]  drm_kms_helper e1000e ahci drm libahci ptp pps_core wmi video
[  +0,07] CPU: 0 PID: 980 Comm: Xorg Tainted: GW   
4.2.0-21-generic #25-Ubuntu
[  +0,02] Hardware name: Hewlett-Packard HP EliteBook 850 G1/198F, BIOS L71 
Ver. 01.30 12/09/2014
[  +0,01]   af849558 8802319977c8 
817e9449
[  +0,03]   880231997820 880231997808 
8107b3d6
[  +0,02]  880231997848 8802319978b0 880230e64800 
0001


[  +0,145801] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
ips_enabled (expected 1, found 0)
[  +0,03] [ cut here ]
[  +0,16] WARNING: CPU: 0 PID: 980 at 
/build/linux-1vdNXv/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12328 
check_crtc_state+0x2c5/0x440 [i915]()
[  +0,01] pipe state doesn't match!
[  +0,01] Modules linked in: rfcomm bnep arc4 hp_wmi joydev sparse_keymap 
intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm snd_hda_co
[  +0,41]  drm_kms_helper e1000e ahci drm libahci ptp pps_core wmi video
[  +0,07] CPU: 0 PID: 980 Comm: Xorg Tainted: GW   
4.2.0-21-generic #25-Ubuntu
[  +0,02] Hardware name: Hewlett-Packard HP EliteBook 850 G1/198F, BIOS L71 
Ver. 01.30 12/09/2014
[  +0,01]   af849558 8802319977c8 
817e9449
[  +0,03]   880231997820 880231997808 
8107b3d6
[  +0,02]  880231997848 8802319978b0 880230e64800 
0001
[  +0,02] Call Trace:
[  +0,06]  [] dump_stack+0x45/0x57
[  +0,05]  [] warn_slowpath_common+0x86/0xc0
[  +0,03]  [] warn_slowpath_fmt+0x55/0x70
[  +0,13]  [] ? intel_pipe_config_compare+0xb31/0xc60 
[i915]
[  +0,11]  [] check_crtc_state+0x2c5/0x440 [i915]
[  +0,16]  [] intel_modeset_check_state+0x21d/0x6d0 [i915]
[  +0,13]  [] intel_crtc_set_config+0x4c7/0x580 [i915]
[  +0,14]  [] ? drm_mode_create+0x25/0x60 [drm]
[  +0,09]  [] drm_mode_set_config_internal+0x66/0x100 
[drm]
[  +0,10]  [] drm_mode_setcrtc+0x3e9/0x500 [drm]
[  +0,06]  [] drm_ioctl+0x125/0x610 [drm]
[  +0,08]  [] ? drm_mode_setplane+0x1b0/0x1b0 [drm]
[  +0,03]  [] do_vfs_ioctl+0x295/0x480
[  +0,03]  [] ? __set_task_blocked+0x41/0xa0
[  +0,02]  [] SyS_ioctl+0x79/0x90
[  +0,03]  [] ? SyS_rt_sigprocmask+0x8e/0xc0
[  +0,03]  [] entry_SYSCALL_64_fastpath+0x16/0x75
[  +0,02] ---[ end trace cf5c10366430704f ]---

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-21-generic 4.2.0-21.25
ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
Uname: Linux 4.2.0-21-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  bs-ldi 1818 F pulseaudio
 /dev/snd/controlC0:  bs-ldi 1818 F pulseaudio
CurrentDesktop: Unity
Date: Sat Dec 12 23:58:03 2015
HibernationDevice: RESUME=UUID=6db9b5a5-d21c-4127-a751-53b667523027
InstallationDate: Installed on 2015-05-28 (198 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Hewlett-Packard HP EliteBook 850 G1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic 
root=UUID=3aa3d587-358c-4744-a494-2ae77f32588c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-21-generic N/A
 linux-backports-modules-4.2.0-21-generic  N/A
 linux-firmware1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-10-23 (50 days ago)
dmi.bios.date: 12/09/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.30
dmi.board.name: 198F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.55
dmi.chassis.asset.tag: CNU425C9T6
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.30:bd12/09/2014:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.55:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 850 G1
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug package-from-proposed wily

-- 
You received 

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

2015-12-12 Thread 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/1525587

Title:
   [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in
  ips_enabled (expected 1, found 0)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [  +0,145801] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
ips_enabled (expected 1, found 0)
  [  +0,03] [ cut here ]
  [  +0,16] WARNING: CPU: 0 PID: 980 at 
/build/linux-1vdNXv/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12328 
check_crtc_state+0x2c5/0x440 [i915]()
  [  +0,01] pipe state doesn't match!
  [  +0,01] Modules linked in: rfcomm bnep arc4 hp_wmi joydev sparse_keymap 
intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm snd_hda_co
  [  +0,41]  drm_kms_helper e1000e ahci drm libahci ptp pps_core wmi video
  [  +0,07] CPU: 0 PID: 980 Comm: Xorg Tainted: GW   
4.2.0-21-generic #25-Ubuntu
  [  +0,02] Hardware name: Hewlett-Packard HP EliteBook 850 G1/198F, BIOS 
L71 Ver. 01.30 12/09/2014
  [  +0,01]   af849558 8802319977c8 
817e9449
  [  +0,03]   880231997820 880231997808 
8107b3d6
  [  +0,02]  880231997848 8802319978b0 880230e64800 
0001

  
  [  +0,145801] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
ips_enabled (expected 1, found 0)
  [  +0,03] [ cut here ]
  [  +0,16] WARNING: CPU: 0 PID: 980 at 
/build/linux-1vdNXv/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12328 
check_crtc_state+0x2c5/0x440 [i915]()
  [  +0,01] pipe state doesn't match!
  [  +0,01] Modules linked in: rfcomm bnep arc4 hp_wmi joydev sparse_keymap 
intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm snd_hda_co
  [  +0,41]  drm_kms_helper e1000e ahci drm libahci ptp pps_core wmi video
  [  +0,07] CPU: 0 PID: 980 Comm: Xorg Tainted: GW   
4.2.0-21-generic #25-Ubuntu
  [  +0,02] Hardware name: Hewlett-Packard HP EliteBook 850 G1/198F, BIOS 
L71 Ver. 01.30 12/09/2014
  [  +0,01]   af849558 8802319977c8 
817e9449
  [  +0,03]   880231997820 880231997808 
8107b3d6
  [  +0,02]  880231997848 8802319978b0 880230e64800 
0001
  [  +0,02] Call Trace:
  [  +0,06]  [] dump_stack+0x45/0x57
  [  +0,05]  [] warn_slowpath_common+0x86/0xc0
  [  +0,03]  [] warn_slowpath_fmt+0x55/0x70
  [  +0,13]  [] ? intel_pipe_config_compare+0xb31/0xc60 
[i915]
  [  +0,11]  [] check_crtc_state+0x2c5/0x440 [i915]
  [  +0,16]  [] intel_modeset_check_state+0x21d/0x6d0 
[i915]
  [  +0,13]  [] intel_crtc_set_config+0x4c7/0x580 [i915]
  [  +0,14]  [] ? drm_mode_create+0x25/0x60 [drm]
  [  +0,09]  [] drm_mode_set_config_internal+0x66/0x100 
[drm]
  [  +0,10]  [] drm_mode_setcrtc+0x3e9/0x500 [drm]
  [  +0,06]  [] drm_ioctl+0x125/0x610 [drm]
  [  +0,08]  [] ? drm_mode_setplane+0x1b0/0x1b0 [drm]
  [  +0,03]  [] do_vfs_ioctl+0x295/0x480
  [  +0,03]  [] ? __set_task_blocked+0x41/0xa0
  [  +0,02]  [] SyS_ioctl+0x79/0x90
  [  +0,03]  [] ? SyS_rt_sigprocmask+0x8e/0xc0
  [  +0,03]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  +0,02] ---[ end trace cf5c10366430704f ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-21-generic 4.2.0-21.25
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bs-ldi 1818 F pulseaudio
   /dev/snd/controlC0:  bs-ldi 1818 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Dec 12 23:58:03 2015
  HibernationDevice: RESUME=UUID=6db9b5a5-d21c-4127-a751-53b667523027
  InstallationDate: Installed on 2015-05-28 (198 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP EliteBook 850 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic 
root=UUID=3aa3d587-358c-4744-a494-2ae77f32588c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-21-generic N/A
   linux-backports-modules-4.2.0-21-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-23 (50 days ago)
  dmi.bios.date: 12/09/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.30
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 

<    1   2