[Kernel-packages] [Bug 1651534] modoc (ppc64el) - tests ran: 1, failed: 1

2016-12-21 Thread Brad Figg
tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-79.87-generic/modoc__3.19.0-79.87__2016-12-22_07-38-00/results-index.html

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

Title:
  linux: 3.19.0-79.87 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651534] onza (i386) - tests ran: 1, failed: 0

2016-12-21 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-79.87-generic/onza__3.19.0-79.87__2016-12-22_07-33-00/results-index.html

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

Title:
  linux: 3.19.0-79.87 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1516738] Re: Kernel memory leak introduced with 14.04 kernel when used with squid3

2016-12-21 Thread Enih
Please read this:
http://www.squid-cache.org/Doc/config/memory_pools/

To improve memory usage/performance of squid, please load jemalloc and
turn off memory_pools.

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

Title:
  Kernel memory leak introduced with 14.04 kernel when used with squid3

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have a Ubuntu 12.04.5 LTS running in a Hyper-V VM for several years.
  Since I updated the system a few days ago to Linux 3.13.0-68-generic x86_64, 
the machine hangs
  with out of memory after about 2 days of uptime. (occurred several times)

  With the kernel from July (3.13.0-4?-generic x86_64 or 3.13.0-5? - I don't 
remember) there was no problem
  running the machine several month without interruption.

  I'm currently monitoring /proc/meminfo and /proc/slabinfo and can sea a 
steady increase of
  Slab in meminfo.

  I also have a second VM without showing the problem. The VM with the leak is 
used as internet
  router and firewall. Two things apply to the VM the the other does not have:
  - vsftpd is running, some files are downloaded from the machine every few 
minutes to hours.
  - there is a "tcpdump -i eth0 -s 65535 -C 100 -W 10 -w /somefile" 
running all the time.

  The attached zip file contains the hourly logs of /proc/meminfo and 
/proc/slabinfo;
  *_151115_171444 are the first files after the last reboot.

  PS: Initially reported as Question:
  https://answers.launchpad.net/ubuntu/+question/274231

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

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


[Kernel-packages] [Bug 1642044] naumann (amd64) - tests ran: 33, failed: 0

2016-12-21 Thread Brad Figg
tests ran:  33, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-32.34~16.04.1-generic/naumann__4.8.0-32.34~16.04.1__2016-12-22_06-07-00/results-index.html

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

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651800] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0

2016-12-21 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-32.34-generic/s2lp6g002__4.8.0-32.34__2016-12-22_07-20-00/results-index.html

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

Title:
  linux: 4.8.0-34.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1651800] Re: linux: 4.8.0-34.36 -proposed tracker

2016-12-21 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-32.34-generic/kernel02__4.8.0-32.34__2016-12-22_07-19-00/results-index.html

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

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

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

** Description changed:

  This bug is for tracking the 4.8.0-34.36 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-stable-phase-changed:Thursday, 22. December 2016 07:17 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.8.0-34.36 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded
- kernel-stable-phase-changed:Thursday, 22. December 2016 07:17 UTC
- kernel-stable-phase:Uploaded

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

Title:
  linux: 4.8.0-34.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1645985] Re: ubuntu 1404_HWE_EOL kernel breaks Thinkpad T530 keyboard backlight operation

2016-12-21 Thread rich painter
** Tags added: kernel-fixed-upstream

** Tags removed: kernel-fixed-upstream

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

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

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

Title:
  ubuntu 1404_HWE_EOL kernel breaks Thinkpad T530 keyboard backlight
  operation

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using kernel 3.19.0-66-generic the keyboard backlight and screen-top
  illuminator work.

  However, after upgrading to kernel 4.4 the keyboard backlight and
  screen-top illuminator come on without hitting the special keys. When
  it returns from screen saver when I hit the return key these lights
  come on also.

  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  painter3092 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05f2d9dc-173d-41bc-8332-7d0a6e7394fa
  InstallationDate: Installed on 2014-11-23 (741 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 2359CTO
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=349d96ad-2412-45a5-b1d9-46eb9050bce1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-51.72~14.04.1-generic 4.4.30
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-51-generic N/A
   linux-backports-modules-4.4.0-51-generic  N/A
   linux-firmware1.127.22
  Tags:  trusty
  Uname: Linux 4.4.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/10/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETA5WW (2.65 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2359CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2359CTO
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1651534] onza (amd64) - tests ran: 1, failed: 0

2016-12-21 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-79.87-generic/onza__3.19.0-79.87__2016-12-22_07-08-00/results-index.html

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

Title:
  linux: 3.19.0-79.87 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651534] modoc (ppc64el) - tests ran: 1, failed: 0

2016-12-21 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-79.87-generic/modoc__3.19.0-79.87__2016-12-22_07-10-00/results-index.html

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

Title:
  linux: 3.19.0-79.87 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1604036] Re: Upgrade printer-driver-ptouch to support Brother QL-570

2016-12-21 Thread Jeremy Bicha
** No longer affects: libosinfo (Ubuntu)

** No longer affects: libosinfo (Ubuntu Xenial)

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

Title:
  Upgrade printer-driver-ptouch to support Brother QL-570

Status in hwdata package in Ubuntu:
  Confirmed
Status in ptouch-driver package in Ubuntu:
  Fix Released
Status in usbutils package in Ubuntu:
  Confirmed
Status in hwdata source package in Xenial:
  New
Status in ptouch-driver source package in Xenial:
  Triaged
Status in usbutils source package in Xenial:
  New

Bug description:
  Please, upgrade printer-driver-ptouch to support Brother QL-570
  P-touch Label Printer. See https://bitbucket.org/philpem/printer-
  driver-ptouch/issues/2/negativeprint-and-cutmedia-jobend-doesnt
  (motivate maintainers of printer-driver-ptouch to bump their version
  number and release a version that supports QL-570) and also upgrade
  usbutils to include https://usb-ids.gowdy.us/read/UD/04f9/2028

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

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


[Kernel-packages] [Bug 1651211] Re: linux-ti-omap4: 3.2.0-1498.125 -proposed tracker

2016-12-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-ti-omap4: 3.2.0-1498.125 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651207
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651212] Re: linux-armadaxp: 3.2.0-1681.108 -proposed tracker

2016-12-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-armadaxp: 3.2.0-1681.108 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-armadaxp source package in Precise:
  In Progress

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651207
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1645985] Re: ubuntu 1404_HWE_EOL kernel breaks Thinkpad T530 keyboard backlight operation

2016-12-21 Thread rich painter
downloaded into new directory:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/linux-headers-4.9.0-040900_4.9.0-040900.201612111631_all.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/linux-headers-4.9.0-040900-generic_4.9.0-040900.201612111631_amd64.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/linux-image-4.9.0-040900-generic_4.9.0-040900.201612111631_amd64.deb

Followed instructions here https://wiki.ubuntu.com/Kernel/MainlineBuilds

sudo dpkg -i *.deb

got some errors that I ignored since the kernel was installed OK for
grub.

rebooted 4.9 and it exhibited the same backlight problem reported here.

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

Title:
  ubuntu 1404_HWE_EOL kernel breaks Thinkpad T530 keyboard backlight
  operation

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using kernel 3.19.0-66-generic the keyboard backlight and screen-top
  illuminator work.

  However, after upgrading to kernel 4.4 the keyboard backlight and
  screen-top illuminator come on without hitting the special keys. When
  it returns from screen saver when I hit the return key these lights
  come on also.

  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  painter3092 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05f2d9dc-173d-41bc-8332-7d0a6e7394fa
  InstallationDate: Installed on 2014-11-23 (741 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 2359CTO
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=349d96ad-2412-45a5-b1d9-46eb9050bce1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-51.72~14.04.1-generic 4.4.30
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-51-generic N/A
   linux-backports-modules-4.4.0-51-generic  N/A
   linux-firmware1.127.22
  Tags:  trusty
  Uname: Linux 4.4.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/10/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETA5WW (2.65 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2359CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG4ETA5WW(2.65):bd09/10/2015:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2359CTO
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1651207] Re: linux: 3.2.0-120.163 -proposed tracker

2016-12-21 Thread Po-Hsu Lin
As per http://kernel.ubuntu.com/sru/sru-report.html no bug was marked as
verification-needed this time.

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/verification-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux: 3.2.0-120.163 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651534] Re: linux: 3.19.0-79.87 -proposed tracker

2016-12-21 Thread Po-Hsu Lin
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux: 3.19.0-79.87 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651800] Re: linux: 4.8.0-34.36 -proposed tracker

2016-12-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

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

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

Title:
  linux: 4.8.0-34.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

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

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


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

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

apport-collect 1651944

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

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

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

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

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

Title:
  Kernel panic when we call pipework to setup virtual network for docker
  containers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I found a kernel panic issue when I was using pipework to config the
  network of a docker container on an x86 board with all-snap image. The
  issue is related to the auditing module of Linux kernel. So it should
  be an issue of pc-kernel-snap.

  I created a simple test snap to reproduce the issue and upload it to github.
  https://github.com/pliu6/docker-snap-test

  Software environment to reproduce the bug:
  #snap list
  Name Version Rev  Developer  Notes
  core 16.04.1 714  canonical  -
  docker   1.11.2-956   canonical  devmode
  dockertest   0.0.1   x12 devmode
  pc   16.04-0.8   9canonical  -
  pc-kernel4.4.0-53-2  51   canonical  -

  The log is below:
  [  504.783341] BUG: unable to handle kernel paging request at 
fff3 
  [  504.867186] IP: [] strlen+0x0/0x20 
  [  504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0  
  [  504.976588] Oops:  [#1] SMP  
  [  505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT 
nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack 
  iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c
  fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid 
i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables 
aut
  ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 
usb_storage ahci libahci 
  [  505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 
4.4.0-53-generic #74-Ubuntu 
  [  505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 
04/05/2014 
  [  505.787738] task: 880037637080 ti: 880061a7 task.ti: 
880061a7 
  [  505.877382] RIP: 0010:[]  [] 
strlen+0x0/0x20 
  [  505.966192] RSP: 0018:880061a73a20  EFLAGS: 00010246 
  [  506.029835] RAX: 880061a73b20 RBX: fff3 RCX: 
 
  [  506.115320] RDX: 014e RSI: fff3 RDI: 
fff3 
  [  506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 
880061a73a94 
  [  506.286283] R10: 000e R11: 88005c835131 R12: 
88007aff0480 
  [  506.371767] R13: 880037637080 R14: 81399fc0 R15: 
fff3 
  [  506.457251] FS:  7fa9f36aa740() GS:88007df0() 
knlGS: 
  [  506.554170] CS:  0010 DS:  ES:  CR0: 80050033 
  [  506.623014] CR2: fff3 CR3: 7853e000 CR4: 
06e0 
  [  506.708497] Stack: 
  [  506.732624]  81122a1a 88007aff0480 880061a73b00 
880061a73a60 
  [  506.822056]  8139a028 88007aff0480 880061a73b00 
880037637080 
  [  506.911490]  880061a73ad8 8136f088 812285c0 
880061a73af0 
  [  507.000926] Call Trace: 
  [  507.030263]  [] ? audit_log_untrustedstring+0x1a/0x30 
  [  507.109502]  [] audit_cb+0x68/0x3f0 
  [  507.170027]  [] common_lsm_audit+0x1b8/0x740 
  [  507.239910]  [] ? alloc_inode+0x50/0x90 
  [  507.304593]  [] ? prepend_path+0xc6/0x2a0 
  [  507.371358]  [] aa_audit+0x5f/0x170 
  [  507.431880]  [] audit_mount+0x152/0x160 
  [  507.496567]  [] match_mnt_path_str+0x1dd/0x490 
  [  507.568529]  [] ? dentry_path+0x18/0x70 
  [  507.633213]  [] match_mnt+0xda/0x150 
  [  507.694776]  [] aa_bind_mount+0x100/0x180 
  [  507.761540]  [] wrap_apparmor_sb_mount+0x1c0/0x270 
  [  507.837664]  [] security_sb_mount+0x57/0x80 
  [  507.906506]  [] do_mount+0xab/0xde0 
  [  507.967032]  [] ? __kmalloc_track_caller+0x1b4/0x250 
  [  508.045236]  [] ? hrtimer_try_to_cancel+0xd1/0x130 
  [  508.121361]  [] ? memdup_user+0x42/0x70 
  [  508.186042]  [] SyS_mount+0x9f/0x100 
  [  508.247607]  [] entry_SYSCALL_64_fastpath+0x16/0x71 
  [  508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f 
b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8
  0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7  
  [  508.564156] RIP  [] strlen+0x0/0x20 
  [  508.624889]  RSP  
  [  

[Kernel-packages] [Bug 1642044] naumann (amd64) - tests ran: 7, failed: 1

2016-12-21 Thread Brad Figg
tests ran:   7, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-32.34~16.04.1-generic/naumann__4.8.0-32.34~16.04.1__2016-12-22_02-09-00/results-index.html

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

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651629] Re: [Asus X200MA] Brightness keys don't work.

2016-12-21 Thread Matthew Brooks
Okay, the archive has it, and it's here:
https://www.spinics.net/lists/linux-acpi/msg71030.html

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

Title:
  [Asus X200MA] Brightness keys don't work.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1651944] [NEW] Kernel panic when we call pipework to setup virtual network for docker containers

2016-12-21 Thread Peng
Public bug reported:

I found a kernel panic issue when I was using pipework to config the
network of a docker container on an x86 board with all-snap image. The
issue is related to the auditing module of Linux kernel. So it should be
an issue of pc-kernel-snap.

I created a simple test snap to reproduce the issue and upload it to github.
https://github.com/pliu6/docker-snap-test

Software environment to reproduce the bug:
#snap list
Name Version Rev  Developer  Notes
core 16.04.1 714  canonical  -
docker   1.11.2-956   canonical  devmode
dockertest   0.0.1   x12 devmode
pc   16.04-0.8   9canonical  -
pc-kernel4.4.0-53-2  51   canonical  -

The log is below:
[  504.783341] BUG: unable to handle kernel paging request at fff3 
[  504.867186] IP: [] strlen+0x0/0x20 
[  504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0  
[  504.976588] Oops:  [#1] SMP  
[  505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT 
nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c
fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid 
i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables 
aut
ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage 
ahci libahci 
[  505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic 
#74-Ubuntu 
[  505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 
04/05/2014 
[  505.787738] task: 880037637080 ti: 880061a7 task.ti: 
880061a7 
[  505.877382] RIP: 0010:[]  [] 
strlen+0x0/0x20 
[  505.966192] RSP: 0018:880061a73a20  EFLAGS: 00010246 
[  506.029835] RAX: 880061a73b20 RBX: fff3 RCX: 
 
[  506.115320] RDX: 014e RSI: fff3 RDI: 
fff3 
[  506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 
880061a73a94 
[  506.286283] R10: 000e R11: 88005c835131 R12: 
88007aff0480 
[  506.371767] R13: 880037637080 R14: 81399fc0 R15: 
fff3 
[  506.457251] FS:  7fa9f36aa740() GS:88007df0() 
knlGS: 
[  506.554170] CS:  0010 DS:  ES:  CR0: 80050033 
[  506.623014] CR2: fff3 CR3: 7853e000 CR4: 
06e0 
[  506.708497] Stack: 
[  506.732624]  81122a1a 88007aff0480 880061a73b00 
880061a73a60 
[  506.822056]  8139a028 88007aff0480 880061a73b00 
880037637080 
[  506.911490]  880061a73ad8 8136f088 812285c0 
880061a73af0 
[  507.000926] Call Trace: 
[  507.030263]  [] ? audit_log_untrustedstring+0x1a/0x30 
[  507.109502]  [] audit_cb+0x68/0x3f0 
[  507.170027]  [] common_lsm_audit+0x1b8/0x740 
[  507.239910]  [] ? alloc_inode+0x50/0x90 
[  507.304593]  [] ? prepend_path+0xc6/0x2a0 
[  507.371358]  [] aa_audit+0x5f/0x170 
[  507.431880]  [] audit_mount+0x152/0x160 
[  507.496567]  [] match_mnt_path_str+0x1dd/0x490 
[  507.568529]  [] ? dentry_path+0x18/0x70 
[  507.633213]  [] match_mnt+0xda/0x150 
[  507.694776]  [] aa_bind_mount+0x100/0x180 
[  507.761540]  [] wrap_apparmor_sb_mount+0x1c0/0x270 
[  507.837664]  [] security_sb_mount+0x57/0x80 
[  507.906506]  [] do_mount+0xab/0xde0 
[  507.967032]  [] ? __kmalloc_track_caller+0x1b4/0x250 
[  508.045236]  [] ? hrtimer_try_to_cancel+0xd1/0x130 
[  508.121361]  [] ? memdup_user+0x42/0x70 
[  508.186042]  [] SyS_mount+0x9f/0x100 
[  508.247607]  [] entry_SYSCALL_64_fastpath+0x16/0x71 
[  508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f 
b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8
0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7  
[  508.564156] RIP  [] strlen+0x0/0x20 
[  508.624889]  RSP  
[  508.96] CR2: fff3 
[  508.706425] ---[ end trace 9a8196367a1a3630 ]---

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

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

Title:
  Kernel panic when we call pipework to setup virtual network for docker
  containers

Status in linux package in Ubuntu:
  New

Bug description:
  I found a kernel panic issue when I was using pipework to config the
  network of a docker container on an x86 board with all-snap image. The
  issue is related to the auditing module of Linux kernel. So it should
  be an issue of pc-kernel-snap.

  I created a simple test snap to reproduce the issue and upload it to github.
  https://github.com/pliu6/docker-snap-test

  Software environment to reproduce the bug:
  #snap list
  Name Version Rev  

[Kernel-packages] [Bug 1651005] Re: Unidentified Trackpad Synaptics

2016-12-21 Thread santi
Unfortunately I'm not using ubuntu right now, so no ubuntu-bug here.
Maybe Carl can do it?

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

Title:
  Unidentified Trackpad Synaptics

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently purchased a Sager NP8152-S / Clevo 650RP6 on which I am dual 
booting.
  See http://www.clevo.com/clevo_prodetail.asp?id=958=en

  The trackpad is not detected. xinput does not display a trackpad
  device nor is the device listed in cat /proc/bus/input/devices which
  is uploaded as a file entitled devices.

  The trackpad device is a Synaptics SMBus TouchPad.

  Please let me know if I incorrectly reported this bug as it is my
  first for Ubuntu. I followed the instructions listed on
  https://wiki.ubuntu.com/DebuggingTouchpadDetection in the section
  called "In case your Touchpad doesn't work at all (No response from
  the Touchpad)".

  Thank you!

  


  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-generic 4.8.0.30.39
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cmuell89   2587 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Dec 18 17:52:04 2016
  HibernationDevice: RESUME=UUID=a7e110fa-7d4d-4b96-8681-fb7acbb406a9
  InstallationDate: Installed on 2016-12-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc.
   Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65xRP
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed 
root=UUID=49d81fc1-d0a2-493f-9a49-c2a533f8d0a6 ro quiet splash i8042.nomux 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-12-19 (0 days ago)
  dmi.bios.date: 11/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08LS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65xRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08LS2:bd11/11/2016:svnNotebook:pnP65xRP:pvrNotApplicable:rvnNotebook:rnP65xRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65xRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Kernel-packages] [Bug 1624765] Re: wifi broke after 16.04 upgrade

2016-12-21 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  wifi broke after 16.04 upgrade

Status in linux package in Ubuntu:
  Expired

Bug description:
  I upgraded from ubuntu 14.04 LTS to ubuntu 16.04 LTS. My wifi was working 
fine in previous version. But, after upgrade wifi broke. It won't show any wifi 
networks and I couldn't enable wifi from ubuntu panel on top right corner. 
  I tried almost all suggestions in this page and few other askubuntu pages 
with same problem: 
  
http://askubuntu.com/questions/62166/siocsifflags-operation-not-possible-due-to-rf-kill
  But, nothing worked. 

  Here is my console output: 
  ~$ sudo rfkill list
  0: dell-rbtn: Wireless LAN
Soft blocked: yes
Hard blocked: yes
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  7: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

  Then, I ran "sudo rfkill unblock wifi" but that didn't fix anything.

  Finally, the only thing that worked was: 
  sudo modprobe -r dell-rbtn

  I don't even know if this is the right way to fix it. Please fix the
  16.04 kernel and OS upgrade package so that other users don't face
  this problem that cost me 2 days. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Sat Sep 17 15:13:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-19 (29 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  parag  3685 F pulseaudio
   /dev/snd/controlC1:  parag  3685 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=bad8d93e-83c4-40c0-aa97-00ac6c4e373e
  InstallationDate: Installed on 2016-08-19 (38 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 3542
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=206733db-103a-4078-847b-0a897121325e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 02RD2H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn02RD2H:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1622167] Re: ALPS touchpad driver doesn't work

2016-12-21 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  ALPS touchpad driver doesn't work

Status in linux package in Ubuntu:
  Expired

Bug description:
  First, the collected kernel version is wrong. I'm running
  4.4.0-36-generic, but inside ubuntu 14.04. Anyway, the touchpad
  refuses to act as a pointer mover. It will, if I let it, do tap to
  click (which is the last thing I want). But, as things stand, I'm
  forced to use the little button in the middle of the keyboard.
  Supposedly the 3.19 kernel was going to install a proper driver for
  the ALPS touchpad, and whilst at least I'm not now stuck with the
  generic driver and unable to turn off tap to click, I no longer have
  pointer movement.

  In the relevant bit of /proc I can see
  N: Name="AlpsPS/2 ALPS DualPoint TouchPad"

  xinput shows this

  jon@harada:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPadid=12   [slave  pointer 
 (2)]

  so I assume there is a real driver at work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-generic 3.13.0.95.103
  ProcVersionSignature: Ubuntu 4.4.0-36.55~14.04.1-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jon2099 F pulseaudio
   /dev/snd/controlC1:  jon2099 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Sep 10 14:24:35 2016
  HibernationDevice: RESUME=UUID=9d74fe15-1696-413a-9428-cf9b52730f3e
  InstallationDate: Installed on 2014-09-12 (728 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: TOSHIBA TECRA Z50-A
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=08d487a3-23ef-4d2a-916e-cafb168982ac ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.127.22
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA Z50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd12/26/2013:svnTOSHIBA:pnTECRAZ50-A:pvrPT545E-00G00VEN:rvnTOSHIBA:rnTECRAZ50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: TECRA Z50-A
  dmi.product.version: PT545E-00G00VEN
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1634315] Re: usb mouse pointer not working

2016-12-21 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  usb mouse pointer not working

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Yakkety:
  Expired

Bug description:
  USB mouse pointer not working when I ugraded my system from 16.04 to
  16.10, however if I type following two commands in terminal one after
  other, it works for that session but stops at restart, repeat the
  procedure it works command are sudo rmmod usbhid ... sudo modprobe
  usbhid, please help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunil  2104 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 18 06:19:57 2016
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=cb35bda9-ebc7-42a2-acf0-a49a5cbf5c36
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2016-09-25 (22 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: FUJITSU LIFEBOOK LH532
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=0467030c-3a59-4a54-a99e-4d7d9e9459e7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   06:20:14.226: The udisks-daemon is running (name-owner :1.113).
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (2 days ago)
  dmi.bios.date: 04/12/2012
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.08
  dmi.board.name: FJNBB1E
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.08:bd04/12/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1E:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK LH532
  dmi.sys.vendor: FUJITSU

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

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


[Kernel-packages] [Bug 1634315] Re: usb mouse pointer not working

2016-12-21 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu Yakkety) because there has been no activity
for 60 days.]

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

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

Title:
  usb mouse pointer not working

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Yakkety:
  Expired

Bug description:
  USB mouse pointer not working when I ugraded my system from 16.04 to
  16.10, however if I type following two commands in terminal one after
  other, it works for that session but stops at restart, repeat the
  procedure it works command are sudo rmmod usbhid ... sudo modprobe
  usbhid, please help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunil  2104 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 18 06:19:57 2016
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=cb35bda9-ebc7-42a2-acf0-a49a5cbf5c36
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2016-09-25 (22 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: FUJITSU LIFEBOOK LH532
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=0467030c-3a59-4a54-a99e-4d7d9e9459e7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   06:20:14.226: The udisks-daemon is running (name-owner :1.113).
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (2 days ago)
  dmi.bios.date: 04/12/2012
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.08
  dmi.board.name: FJNBB1E
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.08:bd04/12/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1E:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK LH532
  dmi.sys.vendor: FUJITSU

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

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


[Kernel-packages] [Bug 1651402] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0

2016-12-21 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-58.79-generic/ms10-35-mcdivittB0-kernel__4.4.0-58.79__2016-12-22_03-57-00/results-index.html

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

Title:
  linux: 4.4.0-58.79 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1649039] Re: USB 3.1 controller does weird magic: appears after Windows 10, disappears otherwise

2016-12-21 Thread Nazar Mokrynskyi
Here is my message on mailing list: https://marc.info/?l=linux-
usb=148237345520582

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

Title:
  USB 3.1 controller does weird magic: appears after Windows 10,
  disappears otherwise

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have motherboard GA-Z170X-UD5 TH with 2 USB Type-C (USB
  3.1/Thunderbolt 3) ports, BIOS version F20b.

  Both ports are "sleeping" on cold start - I can't boot from USB device
  plugged into any and both of these 2 USB Type-C ports. Ubuntu 17.04 as
  of December 11 doesn't see anything (no messages in dmesg).

  But magically situation changes when involve Windows 10 to the party.
  I boot into Windows PE based on Windows 10 and it happily see flash
  drive and my Nexus 6P connected to both ports.

  After this without unplugging mentioned devices I reboot into Ubuntu
  and "magic" - both flash drive and Nexus 6P work fine through these 2
  USB Type-C ports. Even though it works in Ubuntu, BIOS still doesn't
  see anything.

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd
  0b:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
Subsystem: Device :
Kernel driver in use: xhci_hcd

  But things are even more interesting: when I unplug either Nexus 6P or
  flash drive and then plug back - they still work fine! But as soon as
  I unplug both of them - Ubuntu doesn't see anything and doesn't post
  anything into dmesg until I boot into Windows 10 again. Interestingly,
  USB 3.1 controller disappears:

  nazar-pc  ~  lspci -d ::0c03 -k 

   
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Gigabyte Technology Co., Ltd Sunrise Point-H USB 3.0 xHCI 
Controller
Kernel driver in use: xhci_hcd

  nazar-pc  ~   cat /proc/version_signature   

   
  Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   3227 F pulseaudio
   /dev/snd/controlC1:  nazar-pc   3227 F pulseaudio
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro 
rootflags=subvol=root nosplash intel_pstate=disable 
initrd=/efi/ubuntu_efi_stub/initrd.img
  ProcVersionSignature: Ubuntu 4.9.0-10.11-lowlatency 4.9.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-10-lowlatency N/A
   linux-backports-modules-4.9.0-10-lowlatency  N/A
   linux-firmware   1.162
  RfKill: Error: [Errno 2] Немає такого файла або каталогу
  Tags:  zesty
  Uname: Linux 4.9.0-10-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20b
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd11/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: Z170X-UD5 TH
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

2016-12-21 Thread Jimmy Pan
@lpturoyo

Thank you very much, I can shutdown normally now. And my system was
already installing the latest packages before blacklisting nouveau, so
it should be safe to update.

Nonetheless, the shutdown problem should be related to nouveau.

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   

[Kernel-packages] [Bug 1643242] Re: ASUS ROG G752 ELAN1203:00 04F3:301E Touchpad detected but not working

2016-12-21 Thread RedRede
Is there any solution to this problem? I tested on openSuse also the
problem occurs.

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

Title:
  ASUS ROG G752 ELAN1203:00 04F3:301E Touchpad detected but not working

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Model: Laptop ASUS ROG G752 VM
  dual boot with Windows 10; security boot disabled; touchpad activated in uefi

  Touchpad: Name "ELAN1203:00 04F3:301E Touchpad" (see dmesg.txt)

  OS: Ubuntu 4.8.0-27.29-generic 4.8.1 (also tried 4.4.0 and some
  others)

  Symptoms:
  - Touchpad seems to be correctly recognized (see dmesg.txt and Xorg.0.log) 
but doesn't work.
  - evtest: no action on touchpad gets recognized (see evtest.txt)
  - synaptics driver shows some messages regarding "invalid pressure range" and 
"invalid finger width range" (see Xorg.0.log)

  At the moment I use a logitech usb mouse (see dmesg.txt/Xorg.0.log). I
  really want to use only Linux on my machine and banish windows from it
  so any help would be very appreciated! ;-)

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

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


[Kernel-packages] [Bug 1651851] Re: [190247-S5B|]Not all the NVMe can be detected when install Ubuntu 16.04 / 16.04.1 with system connected 12x NVMe

2016-12-21 Thread Leo-Chen
Hi 
I can't dump collect log for you ,because that system's would hang up at during 
OS installation .

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

Title:
  [190247-S5B|]Not all the NVMe can be detected when install Ubuntu
  16.04 / 16.04.1 with system connected 12x NVMe

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1. Setup system w/ NVMe full install
  2. Boot from PXE and install Ubuntu 16.04
  3. Check the NVMe detected at partition disk selection list.
  4. Not all the NVMe can be detected , and system cannot finished the 
installation.
  5. Pls refer to attachment only 3x NVMe detected.(800.2 GB x3 ;512.1 GB is 
M.2 device.)

  The system config:
  CPU:CPU,Skylake-EP,16 Core,2.4GHz,2666,B0,LGA 
3647,256KB/core,165W,22MB,QL28,949716,10.4GT/s,NA,NA,ES2,NA
  Storage:Intel P3700,SSDPE2MD800G4,PCI-e,800GB,Gen3 X4 U.2,2.5 - 15mm * 12

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

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


[Kernel-packages] [Bug 1642044] naumann (amd64) - tests ran: 10, failed: 1

2016-12-21 Thread Brad Figg
tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-32.34~16.04.1-generic/naumann__4.8.0-32.34~16.04.1__2016-12-22_00-22-00/results-index.html

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

Title:
  linux: 4.9.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651910] Re: radeon: black screen after upgrade from 14.04 to 16.04 on RS780

2016-12-21 Thread Chi-Thanh Christopher Nguyen
** Attachment added: "dmesg from kernel 4.4 with drm.debug=15"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651910/+attachment/4795002/+files/dmesg4.4.out

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

Title:
  radeon: black screen after upgrade from 14.04 to 16.04 on RS780

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 14.04 to 16.04, the screen will stay black
  after GRUB (backlight is on) when booting with the new 4.4 kernel
  (linux-image-4.4.0-57-generic).  Booting with the old 3.14 kernel will
  make the screen work again.

  This is on a BIOSTAR A780L mainboard, with the monitor connected via
  DVI.

  "ubuntu-bug linux" tells me that I appear to run a mainline kernel and
  cannot report anything (obviously, as the screen doesn't work if I
  boot the 16.04 kernel).

  $ cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  $ apt-cache policy linux-image-4.4.0-57-generic
  linux-image-4.4.0-57-generic:
Installed: 4.4.0-57.78
Candidate: 4.4.0-57.78
Version table:
   *** 4.4.0-57.78 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  Screen doesn't stay black

  4) What happened instead

  Screen stays black
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 3.14.79-031479-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-09-24 (88 days ago)
  UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1651910] Re: radeon: black screen after upgrade from 14.04 to 16.04 on RS780

2016-12-21 Thread Chi-Thanh Christopher Nguyen
** Attachment added: "dmesg from kernel 3.14 with drm.debug=15"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651910/+attachment/4795003/+files/dmesg3.14.out

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

Title:
  radeon: black screen after upgrade from 14.04 to 16.04 on RS780

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 14.04 to 16.04, the screen will stay black
  after GRUB (backlight is on) when booting with the new 4.4 kernel
  (linux-image-4.4.0-57-generic).  Booting with the old 3.14 kernel will
  make the screen work again.

  This is on a BIOSTAR A780L mainboard, with the monitor connected via
  DVI.

  "ubuntu-bug linux" tells me that I appear to run a mainline kernel and
  cannot report anything (obviously, as the screen doesn't work if I
  boot the 16.04 kernel).

  $ cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  $ apt-cache policy linux-image-4.4.0-57-generic
  linux-image-4.4.0-57-generic:
Installed: 4.4.0-57.78
Candidate: 4.4.0-57.78
Version table:
   *** 4.4.0-57.78 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  Screen doesn't stay black

  4) What happened instead

  Screen stays black
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 3.14.79-031479-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-09-24 (88 days ago)
  UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1651910] Re: radeon: black screen after upgrade from 14.04 to 16.04 on RS780

2016-12-21 Thread Chi-Thanh Christopher Nguyen
I also tried kernel 4.8 which seems to be the latest packaged for 16.04,
with the same result.

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

Title:
  radeon: black screen after upgrade from 14.04 to 16.04 on RS780

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 14.04 to 16.04, the screen will stay black
  after GRUB (backlight is on) when booting with the new 4.4 kernel
  (linux-image-4.4.0-57-generic).  Booting with the old 3.14 kernel will
  make the screen work again.

  This is on a BIOSTAR A780L mainboard, with the monitor connected via
  DVI.

  "ubuntu-bug linux" tells me that I appear to run a mainline kernel and
  cannot report anything (obviously, as the screen doesn't work if I
  boot the 16.04 kernel).

  $ cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  $ apt-cache policy linux-image-4.4.0-57-generic
  linux-image-4.4.0-57-generic:
Installed: 4.4.0-57.78
Candidate: 4.4.0-57.78
Version table:
   *** 4.4.0-57.78 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  Screen doesn't stay black

  4) What happened instead

  Screen stays black
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 3.14.79-031479-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-09-24 (88 days ago)
  UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1651910] Re: radeon: black screen after upgrade from 14.04 to 16.04 on RS780

2016-12-21 Thread Chi-Thanh Christopher Nguyen
apport-collect will give me the same output as ubuntu-bug, namely that I am not 
running an Ubuntu kernel and refuse to do anything else.
The official 16.04 kernel will only produce a black screen.

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

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

Title:
  radeon: black screen after upgrade from 14.04 to 16.04 on RS780

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 14.04 to 16.04, the screen will stay black
  after GRUB (backlight is on) when booting with the new 4.4 kernel
  (linux-image-4.4.0-57-generic).  Booting with the old 3.14 kernel will
  make the screen work again.

  This is on a BIOSTAR A780L mainboard, with the monitor connected via
  DVI.

  "ubuntu-bug linux" tells me that I appear to run a mainline kernel and
  cannot report anything (obviously, as the screen doesn't work if I
  boot the 16.04 kernel).

  $ cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  $ apt-cache policy linux-image-4.4.0-57-generic
  linux-image-4.4.0-57-generic:
Installed: 4.4.0-57.78
Candidate: 4.4.0-57.78
Version table:
   *** 4.4.0-57.78 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  Screen doesn't stay black

  4) What happened instead

  Screen stays black
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 3.14.79-031479-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-09-24 (88 days ago)
  UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare
  _MarkForUpload: True

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

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


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

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

apport-collect 1651910

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

Title:
  radeon: black screen after upgrade from 14.04 to 16.04 on RS780

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu 14.04 to 16.04, the screen will stay black
  after GRUB (backlight is on) when booting with the new 4.4 kernel
  (linux-image-4.4.0-57-generic).  Booting with the old 3.14 kernel will
  make the screen work again.

  This is on a BIOSTAR A780L mainboard, with the monitor connected via
  DVI.

  "ubuntu-bug linux" tells me that I appear to run a mainline kernel and
  cannot report anything (obviously, as the screen doesn't work if I
  boot the 16.04 kernel).

  $ cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  $ apt-cache policy linux-image-4.4.0-57-generic
  linux-image-4.4.0-57-generic:
Installed: 4.4.0-57.78
Candidate: 4.4.0-57.78
Version table:
   *** 4.4.0-57.78 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  Screen doesn't stay black

  4) What happened instead

  Screen stays black
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 3.14.79-031479-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-09-24 (88 days ago)
  UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1651629] Re: [Asus X200MA] Brightness keys don't work.

2016-12-21 Thread Matthew Brooks
Okay, I've sent the report. I'll keep an eye on the mailing list
archives and post a link when it's added there.

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

Title:
  [Asus X200MA] Brightness keys don't work.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1651197] Re: linux: 3.13.0-107.154 -proposed tracker

2016-12-21 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 3.13.0-107.154 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651204] Re: linux-lts-trusty: 3.13.0-107.154~precise1 -proposed tracker

2016-12-21 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux-lts-trusty: 3.13.0-107.154~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-107.154~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651197
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651910] ProcEnviron.txt

2016-12-21 Thread Chi-Thanh Christopher Nguyen
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1651910/+attachment/4795001/+files/ProcEnviron.txt

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

Title:
  radeon: black screen after upgrade from 14.04 to 16.04 on RS780

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 14.04 to 16.04, the screen will stay black
  after GRUB (backlight is on) when booting with the new 4.4 kernel
  (linux-image-4.4.0-57-generic).  Booting with the old 3.14 kernel will
  make the screen work again.

  This is on a BIOSTAR A780L mainboard, with the monitor connected via
  DVI.

  "ubuntu-bug linux" tells me that I appear to run a mainline kernel and
  cannot report anything (obviously, as the screen doesn't work if I
  boot the 16.04 kernel).

  $ cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  $ apt-cache policy linux-image-4.4.0-57-generic
  linux-image-4.4.0-57-generic:
Installed: 4.4.0-57.78
Candidate: 4.4.0-57.78
Version table:
   *** 4.4.0-57.78 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  Screen doesn't stay black

  4) What happened instead

  Screen stays black
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 3.14.79-031479-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-09-24 (88 days ago)
  UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1651211] Re: linux-ti-omap4: 3.2.0-1498.125 -proposed tracker

2016-12-21 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux-ti-omap4: 3.2.0-1498.125 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651207
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651212] Re: linux-armadaxp: 3.2.0-1681.108 -proposed tracker

2016-12-21 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux-armadaxp: 3.2.0-1681.108 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-armadaxp source package in Precise:
  In Progress

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651207
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651534] Re: linux: 3.19.0-79.87 -proposed tracker

2016-12-21 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 3.19.0-79.87 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651207] Re: linux: 3.2.0-120.163 -proposed tracker

2016-12-21 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 3.2.0-120.163 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651402] Re: linux: 4.4.0-58.79 -proposed tracker

2016-12-21 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.4.0-58.79 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651910] JournalErrors.txt

2016-12-21 Thread Chi-Thanh Christopher Nguyen
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1651910/+attachment/4795000/+files/JournalErrors.txt

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

Title:
  radeon: black screen after upgrade from 14.04 to 16.04 on RS780

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 14.04 to 16.04, the screen will stay black
  after GRUB (backlight is on) when booting with the new 4.4 kernel
  (linux-image-4.4.0-57-generic).  Booting with the old 3.14 kernel will
  make the screen work again.

  This is on a BIOSTAR A780L mainboard, with the monitor connected via
  DVI.

  "ubuntu-bug linux" tells me that I appear to run a mainline kernel and
  cannot report anything (obviously, as the screen doesn't work if I
  boot the 16.04 kernel).

  $ cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  $ apt-cache policy linux-image-4.4.0-57-generic
  linux-image-4.4.0-57-generic:
Installed: 4.4.0-57.78
Candidate: 4.4.0-57.78
Version table:
   *** 4.4.0-57.78 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  Screen doesn't stay black

  4) What happened instead

  Screen stays black
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 3.14.79-031479-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-09-24 (88 days ago)
  UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1651910] Re: radeon: black screen after upgrade from 14.04 to 16.04 on RS780

2016-12-21 Thread Chi-Thanh Christopher Nguyen
apport information

** Tags added: apport-collected xenial

** Description changed:

  After upgrading from Ubuntu 14.04 to 16.04, the screen will stay black
  after GRUB (backlight is on) when booting with the new 4.4 kernel
  (linux-image-4.4.0-57-generic).  Booting with the old 3.14 kernel will
  make the screen work again.
  
  This is on a BIOSTAR A780L mainboard, with the monitor connected via
  DVI.
  
  "ubuntu-bug linux" tells me that I appear to run a mainline kernel and
  cannot report anything (obviously, as the screen doesn't work if I boot
  the 16.04 kernel).
  
  $ cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory
  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
  -> About Ubuntu
  
  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  
  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center
  
  $ apt-cache policy linux-image-4.4.0-57-generic
  linux-image-4.4.0-57-generic:
Installed: 4.4.0-57.78
Candidate: 4.4.0-57.78
Version table:
   *** 4.4.0-57.78 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  
  3) What you expected to happen
  
  Screen doesn't stay black
  
  4) What happened instead
  
  Screen stays black
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.4
+ Architecture: amd64
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 16.04
+ Package: xorg 1:7.7+13ubuntu3
+ PackageArchitecture: amd64
+ Tags:  xenial
+ Uname: Linux 3.14.79-031479-generic x86_64
+ UpgradeStatus: Upgraded to xenial on 2016-09-24 (88 days ago)
+ UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1651910/+attachment/4794999/+files/Dependencies.txt

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

Title:
  radeon: black screen after upgrade from 14.04 to 16.04 on RS780

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 14.04 to 16.04, the screen will stay black
  after GRUB (backlight is on) when booting with the new 4.4 kernel
  (linux-image-4.4.0-57-generic).  Booting with the old 3.14 kernel will
  make the screen work again.

  This is on a BIOSTAR A780L mainboard, with the monitor connected via
  DVI.

  "ubuntu-bug linux" tells me that I appear to run a mainline kernel and
  cannot report anything (obviously, as the screen doesn't work if I
  boot the 16.04 kernel).

  $ cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  $ apt-cache policy linux-image-4.4.0-57-generic
  linux-image-4.4.0-57-generic:
Installed: 4.4.0-57.78
Candidate: 4.4.0-57.78
Version table:
   *** 4.4.0-57.78 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  Screen doesn't stay black

  4) What happened instead

  Screen stays black
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 3.14.79-031479-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-09-24 (88 days ago)
  UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1651910] [NEW] radeon: black screen after upgrade from 14.04 to 16.04 on RS780

2016-12-21 Thread Chi-Thanh Christopher Nguyen
Public bug reported:

After upgrading from Ubuntu 14.04 to 16.04, the screen will stay black
after GRUB (backlight is on) when booting with the new 4.4 kernel
(linux-image-4.4.0-57-generic).  Booting with the old 3.14 kernel will
make the screen work again.

This is on a BIOSTAR A780L mainboard, with the monitor connected via
DVI.

"ubuntu-bug linux" tells me that I appear to run a mainline kernel and
cannot report anything (obviously, as the screen doesn't work if I boot
the 16.04 kernel).

$ cat /proc/version_signature > version.log
cat: /proc/version_signature: No such file or directory

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

$ apt-cache policy linux-image-4.4.0-57-generic
linux-image-4.4.0-57-generic:
  Installed: 4.4.0-57.78
  Candidate: 4.4.0-57.78
  Version table:
 *** 4.4.0-57.78 500
500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status

3) What you expected to happen

Screen doesn't stay black

4) What happened instead

Screen stays black

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

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1651910/+attachment/4794998/+files/lspci-vnvn.log

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

Title:
  radeon: black screen after upgrade from 14.04 to 16.04 on RS780

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 14.04 to 16.04, the screen will stay black
  after GRUB (backlight is on) when booting with the new 4.4 kernel
  (linux-image-4.4.0-57-generic).  Booting with the old 3.14 kernel will
  make the screen work again.

  This is on a BIOSTAR A780L mainboard, with the monitor connected via
  DVI.

  "ubuntu-bug linux" tells me that I appear to run a mainline kernel and
  cannot report anything (obviously, as the screen doesn't work if I
  boot the 16.04 kernel).

  $ cat /proc/version_signature > version.log
  cat: /proc/version_signature: No such file or directory

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  $ apt-cache policy linux-image-4.4.0-57-generic
  linux-image-4.4.0-57-generic:
Installed: 4.4.0-57.78
Candidate: 4.4.0-57.78
Version table:
   *** 4.4.0-57.78 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  Screen doesn't stay black

  4) What happened instead

  Screen stays black

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

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


[Kernel-packages] [Bug 1651539] Re: linux-lts-vivid: 3.19.0-79.87~14.04.1 -proposed tracker

2016-12-21 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-lts-vivid: 3.19.0-79.87~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-79.87~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651534
  phase: Packaging

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

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


[Kernel-packages] [Bug 1638990] Re: nvidia-367 with kernel 4.4.0-45-generic won't boot

2016-12-21 Thread Alberto Salvia Novella
@ Christopher M. Penalver

I would recommend that the only criteria to take into account when
setting bug importances is their impact alone.

If the OS renders their system broken, most people told me that they
will simply quit it. Most of them that I have installed Ubuntu don't
understand workarounds written in English.

The official documentation is broken and outdated, because one or two
people are preventing it from changing.

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

Title:
  nvidia-367 with kernel 4.4.0-45-generic won't boot

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  After I upgraded the nvidia drivers, I could no longer boot via kernel
  4.4.0-45-generic.

  WORKAROUND: Use nouveau.

  WORKAROUND: Boot with already installed kernel 4.4.0-31-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lost   2248 F pulseaudio
   /dev/snd/controlC0:  lost   2248 F pulseaudio
   /dev/snd/controlC1:  lost   2248 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Nov  3 12:12:55 2016
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (1 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/xubuntu--vg-root ro nomodeset quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1651800] Re: linux: 4.8.0-34.36 -proposed tracker

2016-12-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

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

** Description changed:

  This bug is for tracking the 4.8.0-34.36 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-stable-phase-changed:Wednesday, 21. December 2016 16:34 UTC
- kernel-stable-phase:Packaging
- 
  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging
+ kernel-stable-phase-changed:Wednesday, 21. December 2016 23:35 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.8.0-34.36 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
- phase: Packaging
- kernel-stable-phase-changed:Wednesday, 21. December 2016 23:35 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux: 4.8.0-34.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2016-12-21 Thread Daniel Jose
I exhibited similar symptoms when installing Ubuntu 16.04.1 LTS on an Asus 
x541u VivoBook Max system. When performing the installation, the logs would 
fill up with these errors and eventually fail because of lack of disk space.  I 
found the following thread helpful...
http://www.gossamer-threads.com/lists/linux/kernel/2250177

The workaround for me was to hold left SHIFT, edit the grub menu and add
the pcie_aspm=off kernel parameter to suppress the messages during the
installation and every subsequent boot.  Adding these options to the
grub configuration after installing was the long-term workaround.

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

Title:
  AER: Corrected error received: id=00e0

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent 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.153
  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: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1651402] Re: linux: 4.4.0-58.79 -proposed tracker

2016-12-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the 4.4.0-58.79 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 21. December 2016 23:32 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 4.4.0-58.79 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
- phase: Uploaded
- kernel-stable-phase-changed:Wednesday, 21. December 2016 23:32 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.4.0-58.79 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 671979] Re: Repeated (spurious?) pcieport errors in logs (PCIe Bus Error)

2016-12-21 Thread Daniel Jose
I exhibited similar symptoms when installing Ubuntu 16.04.1 LTS on an Asus 
x541u VivoBook Max system. When performing the installation, the logs would 
fill up with these errors and eventually fail because of lack of disk space.  I 
found the following thread helpful...
http://www.gossamer-threads.com/lists/linux/kernel/2250177

The workaround for me was to hold left SHIFT, edit the grub menu and add
the pcie_aspm=off kernel parameter to suppress the messages during the
installation and every subsequent boot.  Adding these options to the
grub configuration after installing was the long-term workaround.

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

Title:
  Repeated (spurious?) pcieport errors in logs (PCIe Bus Error)

Status in linux package in Ubuntu:
  Expired

Bug description:
  On a newly bought laptop (Asus G53JW), on Ubuntu 10.10 (linux-
  image-2.6.35-22-generic), logs fill up from messages like this:

  [ 1108.493365] pcieport :00:03.0: AER: Corrected error received: id=0018
  [ 1108.493378] pcieport :00:03.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=0018(Receiver ID)
  [ 1108.493385] pcieport :00:03.0:   device [8086:d138] error 
status/mask=0001/1100
  [ 1108.493391] pcieport :00:03.0:[ 0] Receiver Error

  They appear shortly after boot. Everything seems to be nevertheless
  working. However, the logs get filled up by these messages, and can
  quickly swell up to GB size.

  Not sure if this is related: I've also experienced some ~20s hangs
  when using the proprietary Nvidia drivers in heavy 3D graphics, which
  may be related. However, these errors appear also without using those
  drivers (or having the "nvidia" ever been loaded) -- the attached
  debug info is from a boot without the proprietary drivers.

  I'll try to follow up with tests with the mainline kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: linux-image-generic 2.6.35.22.23
  Regression: No
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC259 Analog [ALC259 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pauli  3114 F pulseaudio
   /dev/snd/seq:timidity   2730 F timidity
  CRDA: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xdc60 irq 53'
 Mixer name : 'Realtek ALC259'
 Components : 'HDA:10ec0269,10431083,00100100'
 Controls  : 16
 Simple ctrls  : 9
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xd608 irq 17'
 Mixer name : 'Nvidia ID 11'
 Components : 'HDA:10de0011,10de0101,00100100'
 Controls  : 0
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  Date: Sat Nov  6 22:55:18 2010
  HibernationDevice: RESUME=UUID=f5613820-aab4-45b0-a68f-19397460bb5c
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: ASUSTeK Computer Inc. G53JW
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-22-generic root=/dev/mapper/main-root 
ro single
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: linux-firmware 1.38
  SourcePackage: linux
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G53JW.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G53JW
  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.:bvrG53JW.209:bd10/05/2010:svnASUSTeKComputerInc.:pnG53JW:pvr1.0:rvnASUSTeKComputerInc.:rnG53JW:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: G53JW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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


[Kernel-packages] [Bug 1651539] Re: linux-lts-vivid: 3.19.0-79.87~14.04.1 -proposed tracker

2016-12-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

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

** Description changed:

  This bug is for tracking the 3.19.0-79.87~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651534
  phase: Packaging

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

Title:
  linux-lts-vivid: 3.19.0-79.87~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-79.87~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651534
  phase: Packaging

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

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


[Kernel-packages] [Bug 1651539] Re: linux-lts-vivid: 3.19.0-79.87~14.04.1 -proposed tracker

2016-12-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

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

Title:
  linux-lts-vivid: 3.19.0-79.87~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-79.87~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651534
  phase: Packaging

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

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


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

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

apport-collect 1651609

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

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

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

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

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

Title:
  Missing hugepages in xenial on 4.4.0-36-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When spawning multiple VMs and then shutting then down there are
  hugepages that are unaccounted for, they don't show up in "ipcs -m" or
  on in /dev/hugepages/

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

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


[Kernel-packages] [Bug 1651534] Re: linux: 3.19.0-79.87 -proposed tracker

2016-12-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.19.0-79.87 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-stable-phase-changed:Tuesday, 20. December 2016 17:45 UTC
- kernel-stable-phase:Packaging
- 
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging
+ kernel-stable-phase-changed:Wednesday, 21. December 2016 22:34 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 3.19.0-79.87 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
- phase: Packaging
- kernel-stable-phase-changed:Wednesday, 21. December 2016 22:34 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 3.19.0-79.87 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651629] Re: [Asus X200MA] Brightness keys don't work.

2016-12-21 Thread Christopher M. Penalver
Matthew Brooks, the issue you are reporting is an upstream one. Could
you please report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO Rafael J. Wysocki and Len Brown CC linux-acpi)?

Please provide a direct URL to your post to the mailing list when it
becomes available so that it may be tracked.

Thank you for your help.

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

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

Title:
  [Asus X200MA] Brightness keys don't work.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1590844] Re: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

2016-12-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: telephony-service (Ubuntu)
   Status: New => Confirmed

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

Title:
  Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

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

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


[Kernel-packages] [Bug 1590844] Re: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

2016-12-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

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

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


[Kernel-packages] [Bug 1651609] Re: Missing hugepages in xenial on 4.4.0-36-generic

2016-12-21 Thread Dragan S.
** Package changed: ethtool (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Missing hugepages in xenial on 4.4.0-36-generic

Status in linux package in Ubuntu:
  New

Bug description:
  When spawning multiple VMs and then shutting then down there are
  hugepages that are unaccounted for, they don't show up in "ipcs -m" or
  on in /dev/hugepages/

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

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


[Kernel-packages] [Bug 1651609] [NEW] Missing hugepages in xenial on 4.4.0-36-generic

2016-12-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When spawning multiple VMs and then shutting then down there are
hugepages that are unaccounted for, they don't show up in "ipcs -m" or
on in /dev/hugepages/

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Dragan S. (dragan-s)
 Status: New


** Tags: sts
-- 
Missing hugepages in xenial on 4.4.0-36-generic
https://bugs.launchpad.net/bugs/1651609
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1638788] Re: [MacBookAir5, 2] Resumes immediately after suspend

2016-12-21 Thread Christopher M. Penalver
Eugene, it will help immensely if you filed a new report with the Ubuntu 
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  [MacBookAir5,2] Resumes immediately after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  with default settings the laptop will immediately resume after sending
  to sleep (regardless of by closing the LID or though the menu option
  "suspend")

  the workaround is disabling the LID ACPI action by running:

  echo LID0 >/proc/acpi/wakeup

  this will fix the problem. obviously however just simply opening the
  lid won't wake the laptop anymore. so one has to manually press the
  power button.

  (I used ubuntu-bug linux, so hopefully all info should be attached)
  I'm running out of the box, up2date yakkety. without any external
  repos or custom compiled applications

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-26-generic 4.8.0-26.28
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  toby   2327 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov  2 21:49:50 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ba2577eb-f563-46c3-adb9-47967c8c5851
  InstallationDate: Installed on 2016-10-17 (16 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Apple Inc. MacBookAir5,2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic.efi.signed 
root=UUID=add8c949-ae19-4310-aede-4a9007ea7514 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-generic N/A
   linux-backports-modules-4.8.0-26-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B04.1509111654
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2E6FAB96566FE58C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2E6FAB96566FE58C
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B04.1509111654:bd09/11/2015:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
  dmi.product.name: MacBookAir5,2
  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/1638788/+subscriptions

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


[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

2016-12-21 Thread turoyo dee
@dspjmr,

in my setup, I do not bother to install/run nvidia, and boot/shutdown works 
fine.
during the times I have accidentally updated the kernel ( due to some other 
package installation ), I only experience the boot issue ( and it is very 
random, about 1 of 5 or maybe 1 of 8 boots ).

The only time I ever experience shutdown problem is on vanilla install ( step 1 
in my setup )
but once I get the intel-microcode and blacklist nouveau, everything works fine.

@penalvch,

ok, I'll check, I just landed on these bug reports via google.

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 

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

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

apport-collect 1651851

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

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

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

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

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

Title:
  [190247-S5B|]Not all the NVMe can be detected when install Ubuntu
  16.04 / 16.04.1 with system connected 12x NVMe

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1. Setup system w/ NVMe full install
  2. Boot from PXE and install Ubuntu 16.04
  3. Check the NVMe detected at partition disk selection list.
  4. Not all the NVMe can be detected , and system cannot finished the 
installation.
  5. Pls refer to attachment only 3x NVMe detected.(800.2 GB x3 ;512.1 GB is 
M.2 device.)

  The system config:
  CPU:CPU,Skylake-EP,16 Core,2.4GHz,2666,B0,LGA 
3647,256KB/core,165W,22MB,QL28,949716,10.4GT/s,NA,NA,ES2,NA
  Storage:Intel P3700,SSDPE2MD800G4,PCI-e,800GB,Gen3 X4 U.2,2.5 - 15mm * 12

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

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


[Kernel-packages] [Bug 1638788] Re: [MacBookAir5, 2] Resumes immediately after suspend

2016-12-21 Thread Eugene
I have tested linux-image-4.9.0-040900-generic - bug is still here: my laptop 
always resumes from suspend by itself (as well as with 4.8.0-32-generic)
with left from upgrade linux-image-4.4.0-47-generic - laptop suspends as well


root@spectre:~# acpitool -w | grep enabled
  51. PWRBS4*enabled   platform:PNP0C0C:00

Laptop is HP Spectre 13 X5B66EA#ACB

Can I provide some info to help to fix it?

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

Title:
  [MacBookAir5,2] Resumes immediately after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  with default settings the laptop will immediately resume after sending
  to sleep (regardless of by closing the LID or though the menu option
  "suspend")

  the workaround is disabling the LID ACPI action by running:

  echo LID0 >/proc/acpi/wakeup

  this will fix the problem. obviously however just simply opening the
  lid won't wake the laptop anymore. so one has to manually press the
  power button.

  (I used ubuntu-bug linux, so hopefully all info should be attached)
  I'm running out of the box, up2date yakkety. without any external
  repos or custom compiled applications

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-26-generic 4.8.0-26.28
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  toby   2327 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov  2 21:49:50 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ba2577eb-f563-46c3-adb9-47967c8c5851
  InstallationDate: Installed on 2016-10-17 (16 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Apple Inc. MacBookAir5,2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic.efi.signed 
root=UUID=add8c949-ae19-4310-aede-4a9007ea7514 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-generic N/A
   linux-backports-modules-4.8.0-26-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B04.1509111654
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2E6FAB96566FE58C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2E6FAB96566FE58C
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B04.1509111654:bd09/11/2015:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
  dmi.product.name: MacBookAir5,2
  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/1638788/+subscriptions

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


[Kernel-packages] [Bug 1651629] Re: [Asus X200MA] Brightness keys don't work.

2016-12-21 Thread Matthew Brooks
With just "video.use_bios_initial_backlight=0", the brightness keys do
nothing, and the gnome brightness slider works.

With just "acpi_osi=", the brightness keys are recognized, and the
brightness meter changes, but the actual screen brightness doesn't
change at all. The gnome brightness slider also doesn't change the
brightness when using this parameter.

With just "atkbd.softraw=0", "showkey -s" produces no output when
pressing the backlight keys.

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

Title:
  [Asus X200MA] Brightness keys don't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1651629] Re: [Asus X200MA] Brightness keys don't work.

2016-12-21 Thread Matthew Brooks
Using "acpi_backlight=vendor" and also creating the "80-backlight.conf"
file with the contents shown on that page, results in the brightness
keys still doing nothing, and the gnome brightness slider not working.

The /sys/class/backlight/intel_backlight/brightness file still works
fine though.

I think that's everything in the workaround section there. But let me
know if there's anything else I need to check or anything.

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

Title:
  [Asus X200MA] Brightness keys don't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1651851] [NEW] [190247-S5B|]Not all the NVMe can be detected when install Ubuntu 16.04 / 16.04.1 with system connected 12x NVMe

2016-12-21 Thread Mark W Wenning
Public bug reported:

1. Setup system w/ NVMe full install
2. Boot from PXE and install Ubuntu 16.04
3. Check the NVMe detected at partition disk selection list.
4. Not all the NVMe can be detected , and system cannot finished the 
installation.
5. Pls refer to attachment only 3x NVMe detected.(800.2 GB x3 ;512.1 GB is M.2 
device.)

The system config:
CPU:CPU,Skylake-EP,16 Core,2.4GHz,2666,B0,LGA 
3647,256KB/core,165W,22MB,QL28,949716,10.4GT/s,NA,NA,ES2,NA
Storage:Intel P3700,SSDPE2MD800G4,PCI-e,800GB,Gen3 X4 U.2,2.5 - 15mm * 12

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

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

Title:
  [190247-S5B|]Not all the NVMe can be detected when install Ubuntu
  16.04 / 16.04.1 with system connected 12x NVMe

Status in linux package in Ubuntu:
  New

Bug description:
  1. Setup system w/ NVMe full install
  2. Boot from PXE and install Ubuntu 16.04
  3. Check the NVMe detected at partition disk selection list.
  4. Not all the NVMe can be detected , and system cannot finished the 
installation.
  5. Pls refer to attachment only 3x NVMe detected.(800.2 GB x3 ;512.1 GB is 
M.2 device.)

  The system config:
  CPU:CPU,Skylake-EP,16 Core,2.4GHz,2666,B0,LGA 
3647,256KB/core,165W,22MB,QL28,949716,10.4GT/s,NA,NA,ES2,NA
  Storage:Intel P3700,SSDPE2MD800G4,PCI-e,800GB,Gen3 X4 U.2,2.5 - 15mm * 12

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

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


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

2016-12-21 Thread Heiko Sieger
apport information

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

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

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
   /dev/snd/controlC0:  heiko  2688 F pulseaudio
   /dev/snd/controlC2:  heiko  2688 F pulseaudio
   /dev/snd/controlC1:  heiko  2688 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
  InstallationDate: Installed on 2015-12-03 (383 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  serena
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev 

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

2016-12-21 Thread Heiko Sieger
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1651846/+attachment/4794938/+files/UdevDb.txt

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
   /dev/snd/controlC0:  heiko  2688 F pulseaudio
   /dev/snd/controlC2:  heiko  2688 F pulseaudio
   /dev/snd/controlC1:  heiko  2688 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
  InstallationDate: Installed on 2015-12-03 (383 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  serena
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2014
  dmi.bios.vendor: 

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

2016-12-21 Thread Heiko Sieger
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1651846/+attachment/4794933/+files/ProcCpuinfo.txt

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
   /dev/snd/controlC0:  heiko  2688 F pulseaudio
   /dev/snd/controlC2:  heiko  2688 F pulseaudio
   /dev/snd/controlC1:  heiko  2688 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
  InstallationDate: Installed on 2015-12-03 (383 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  serena
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2014
  

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

2016-12-21 Thread Heiko Sieger
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1651846/+attachment/4794936/+files/ProcModules.txt

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
   /dev/snd/controlC0:  heiko  2688 F pulseaudio
   /dev/snd/controlC2:  heiko  2688 F pulseaudio
   /dev/snd/controlC1:  heiko  2688 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
  InstallationDate: Installed on 2015-12-03 (383 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  serena
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2014
  

[Kernel-packages] [Bug 1651846] Re: ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't compile/install

2016-12-21 Thread Heiko Sieger
apport information

** Tags added: apport-collected serena

** Description changed:

  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04
  
  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status
  
  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."
  
  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.
  
  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:
  
  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
+  /dev/snd/controlC0:  heiko  2688 F pulseaudio
+  /dev/snd/controlC2:  heiko  2688 F pulseaudio
+  /dev/snd/controlC1:  heiko  2688 F pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Linux 18.1
+ HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
+ InstallationDate: Installed on 2015-12-03 (383 days ago)
+ InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
+ MachineType: System manufacturer System Product Name
+ NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
+ ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
+ RelatedPackageVersions:
+  linux-restricted-modules-4.8.0-30-generic N/A
+  linux-backports-modules-4.8.0-30-generic  N/A
+  linux-firmware1.157.6
+ RfKill:
+  
+ Tags:  serena
+ Uname: Linux 4.8.0-30-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/25/2014
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 4801
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: SABERTOOTH X79
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Asset-1234567890
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Chassis Manufacture
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 

[Kernel-packages] [Bug 1651846] PulseList.txt

2016-12-21 Thread Heiko Sieger
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1651846/+attachment/4794937/+files/PulseList.txt

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
   /dev/snd/controlC0:  heiko  2688 F pulseaudio
   /dev/snd/controlC2:  heiko  2688 F pulseaudio
   /dev/snd/controlC1:  heiko  2688 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
  InstallationDate: Installed on 2015-12-03 (383 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  serena
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2014
  

[Kernel-packages] [Bug 1651846] CurrentDmesg.txt

2016-12-21 Thread Heiko Sieger
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1651846/+attachment/4794928/+files/CurrentDmesg.txt

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
   /dev/snd/controlC0:  heiko  2688 F pulseaudio
   /dev/snd/controlC2:  heiko  2688 F pulseaudio
   /dev/snd/controlC1:  heiko  2688 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
  InstallationDate: Installed on 2015-12-03 (383 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  serena
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2014
  

[Kernel-packages] [Bug 1651846] JournalErrors.txt

2016-12-21 Thread Heiko Sieger
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1651846/+attachment/4794930/+files/JournalErrors.txt

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
   /dev/snd/controlC0:  heiko  2688 F pulseaudio
   /dev/snd/controlC2:  heiko  2688 F pulseaudio
   /dev/snd/controlC1:  heiko  2688 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
  InstallationDate: Installed on 2015-12-03 (383 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  serena
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2014
  

[Kernel-packages] [Bug 1651846] ProcEnviron.txt

2016-12-21 Thread Heiko Sieger
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1651846/+attachment/4794934/+files/ProcEnviron.txt

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
   /dev/snd/controlC0:  heiko  2688 F pulseaudio
   /dev/snd/controlC2:  heiko  2688 F pulseaudio
   /dev/snd/controlC1:  heiko  2688 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
  InstallationDate: Installed on 2015-12-03 (383 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  serena
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2014
  

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

2016-12-21 Thread Heiko Sieger
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1651846/+attachment/4794935/+files/ProcInterrupts.txt

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
   /dev/snd/controlC0:  heiko  2688 F pulseaudio
   /dev/snd/controlC2:  heiko  2688 F pulseaudio
   /dev/snd/controlC1:  heiko  2688 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
  InstallationDate: Installed on 2015-12-03 (383 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  serena
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2014
  

[Kernel-packages] [Bug 1651846] Lsusb.txt

2016-12-21 Thread Heiko Sieger
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1651846/+attachment/4794932/+files/Lsusb.txt

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
   /dev/snd/controlC0:  heiko  2688 F pulseaudio
   /dev/snd/controlC2:  heiko  2688 F pulseaudio
   /dev/snd/controlC1:  heiko  2688 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
  InstallationDate: Installed on 2015-12-03 (383 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  serena
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2014
  dmi.bios.vendor: 

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

2016-12-21 Thread Heiko Sieger
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1651846/+attachment/4794931/+files/Lspci.txt

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
   /dev/snd/controlC0:  heiko  2688 F pulseaudio
   /dev/snd/controlC2:  heiko  2688 F pulseaudio
   /dev/snd/controlC1:  heiko  2688 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
  InstallationDate: Installed on 2015-12-03 (383 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  serena
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2014
  dmi.bios.vendor: 

[Kernel-packages] [Bug 1651846] CRDA.txt

2016-12-21 Thread Heiko Sieger
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1651846/+attachment/4794927/+files/CRDA.txt

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
   /dev/snd/controlC0:  heiko  2688 F pulseaudio
   /dev/snd/controlC2:  heiko  2688 F pulseaudio
   /dev/snd/controlC1:  heiko  2688 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
  InstallationDate: Installed on 2015-12-03 (383 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  serena
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2014
  dmi.bios.vendor: 

[Kernel-packages] [Bug 1651846] IwConfig.txt

2016-12-21 Thread Heiko Sieger
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1651846/+attachment/4794929/+files/IwConfig.txt

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   heiko  2688 F...m pulseaudio
   /dev/snd/controlC0:  heiko  2688 F pulseaudio
   /dev/snd/controlC2:  heiko  2688 F pulseaudio
   /dev/snd/controlC1:  heiko  2688 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175
  InstallationDate: Installed on 2015-12-03 (383 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 
ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  Tags:  serena
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/25/2014
  

[Kernel-packages] [Bug 1651629] Re: [Asus X200MA] Brightness keys don't work.

2016-12-21 Thread Matthew Brooks
** Attachment added: "lslabacklight"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651629/+attachment/4794924/+files/lslabacklight

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

Title:
  [Asus X200MA] Brightness keys don't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1651629] Re: [Asus X200MA] Brightness keys don't work.

2016-12-21 Thread Matthew Brooks
Booting with "acpi_backlight=vendor", the brightness keys do nothing,
and the gnome brightness slider breaks.

The /sys/class/backlight/intel_backlight/brightness file still works.
I don't know if it's important, but the "max_brightness" is 7812, which might 
be an unusual range. Setting brightness to 8, as recommended by the workaround 
steps, makes the screen way too dark to see anything. I usually have it at 
about 4000 or so.


Anyway, I'm attaching the "vendorbacklight" and "lslabacklight" files that 
where generated, and I'm going to test the atkbd.softraw-0 parameter next. I'll 
report back with it's results.

** Attachment added: "vendorbacklight"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651629/+attachment/4794923/+files/vendorbacklight

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

Title:
  [Asus X200MA] Brightness keys don't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

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

apport-collect 1651846

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

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

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

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

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
  wnd->net_dev->trans_start = jiffies;
  ^
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.59/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'

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

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


[Kernel-packages] [Bug 1651846] [NEW] ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't compile/install

2016-12-21 Thread Heiko Sieger
Public bug reported:

Description:Linux Mint 18.1 Serena
Ubuntu 16.04

Package:
ndiswrapper:
  Installed: 1.59-6
  Candidate: 1.59-6
  Version table:
 *** 1.59-6 500
500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status

When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
"Building initial module for 4.8.0-30-generic
Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

The same happens when re-installing via Synaptic. Synaptic reports
"Changes applied" (doesn't report failure), but in fact there is no
ndiswrapper module in /var/lib/dkms/ndiswrapper.

Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
ד' דצמ 21 12:20:38 IST 2016
make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
  LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
  MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
  MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h
  CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/crt.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/hal.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/loader.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ndis.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/pnp.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/proc.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/rtl.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o
/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’:
/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct 
net_device’ has no member named ‘trans_start’
wnd->net_dev->trans_start = jiffies;
^
scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed
make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1
Makefile:1489: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.59/build' 
failed
make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2
make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic'

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


** Tags: ndiswrapper

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

Title:
  ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't
  compile/install

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Linux Mint 18.1 Serena
  Ubuntu 16.04

  Package:
  ndiswrapper:
Installed: 1.59-6
Candidate: 1.59-6
Version table:
   *** 1.59-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), 
ndiswrapper returns the following error:
  "Building initial module for 4.8.0-30-generic
  Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information."

  The same happens when re-installing via Synaptic. Synaptic reports
  "Changes applied" (doesn't report failure), but in fact there is no
  ndiswrapper module in /var/lib/dkms/ndiswrapper.

  Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log:

  DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64)
  ד' דצמ 21 12:20:38 IST 2016
  make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic'
LD  /var/lib/dkms/ndiswrapper/1.59/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h
MKSTUBS 

[Kernel-packages] [Bug 1651212] Re: linux-armadaxp: 3.2.0-1681.108 -proposed tracker

2016-12-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.2.0-1681.108 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651207
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 21. December 2016 20:17 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 3.2.0-1681.108 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651207
- phase: Uploaded
- kernel-stable-phase-changed:Wednesday, 21. December 2016 20:17 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-armadaxp: 3.2.0-1681.108 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-armadaxp source package in Precise:
  In Progress

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651207
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651211] Re: linux-ti-omap4: 3.2.0-1498.125 -proposed tracker

2016-12-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

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

Title:
  linux-ti-omap4: 3.2.0-1498.125 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651207
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651629] Re: [Asus X200MA] Brightness keys don't work.

2016-12-21 Thread Christopher M. Penalver
Matthew Brooks, could you please advise if a WORKAROUND exists via
https://wiki.ubuntu.com/Kernel/Debugging/Backlight ?

** Summary changed:

- [Asus X200M] Brightness keys don't work.
+ [Asus X200MA] Brightness keys don't work.

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

Title:
  [Asus X200MA] Brightness keys don't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1611583] Re: [Asus F556UA] Trackpad scrolling not working

2016-12-21 Thread Christopher M. Penalver
** Description changed:

  I just got an ASUS F556UA-AS54 laptop and of course I immediately
  deleted windows and installed ubuntu ;). Everything works fine, except
  that the trackpad doesn't seem to be recognized properly. I am certain
  that I have the bug on this page:
  
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.
  
  It works for basic functions (clicking, tracking), but I can't scroll or
  do other things a trackpad should do. And, just like the page said, the
  options for my trackpad are missing in the mouse and touchpad settings.
  It's just the single page for the mouse. I've attached the three files
  that the page asked for. Thanks in advance for any help!
  
+ WORKAROUND: https://github.com/vlasenko/hid-asus-fte-dkms
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  aidan  3577 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  aidan  3577 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  9 22:34:45 2016
  HibernationDevice: RESUME=UUID=f6b45d13-6efe-4691-b3b9-f96ef5f74e84
  InstallationDate: Installed on 2016-08-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 13d3:3496 IMC Networks 
-  Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
-  Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 13d3:3496 IMC Networks
+  Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp.
+  Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X556UA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=ff9e8c9c-7769-45e7-a3ec-962cd53292cf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-34-generic N/A
-  linux-backports-modules-4.4.0-34-generic  N/A
-  linux-firmware1.157.2
+  linux-restricted-modules-4.4.0-34-generic N/A
+  linux-backports-modules-4.4.0-34-generic  N/A
+  linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UA.402
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UA.402:bd03/09/2016:svnASUSTeKCOMPUTERINC.:pnX556UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X556UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  [Asus F556UA] Trackpad scrolling not working

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I just got an ASUS F556UA-AS54 laptop and of course I immediately
  deleted windows and installed ubuntu ;). Everything works fine, except
  that the trackpad doesn't seem to be recognized properly. I am certain
  that I have the bug on this page:

  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

  It works for basic functions (clicking, tracking), but I can't scroll
  or do other things a trackpad should do. And, just like the page said,
  the options for my trackpad are missing in the mouse and touchpad
  settings. It's just the single page for the mouse. I've attached the
  three files that the page asked for. Thanks in advance for any help!

  WORKAROUND: https://github.com/vlasenko/hid-asus-fte-dkms

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aidan  3577 F 

[Kernel-packages] [Bug 1651204] Re: linux-lts-trusty: 3.13.0-107.154~precise1 -proposed tracker

2016-12-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

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

Title:
  linux-lts-trusty: 3.13.0-107.154~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-107.154~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1651197
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651207] Re: linux: 3.2.0-120.163 -proposed tracker

2016-12-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the 3.2.0-120.163 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-stable-phase:Packaging
- kernel-stable-phase-changed:Monday, 19. December 2016 18:34 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging
+ kernel-stable-phase-changed:Wednesday, 21. December 2016 20:04 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 3.2.0-120.163 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
- phase: Packaging
- kernel-stable-phase-changed:Wednesday, 21. December 2016 20:04 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 3.2.0-120.163 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651197] Re: linux: 3.13.0-107.154 -proposed tracker

2016-12-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the 3.13.0-107.154 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 21. December 2016 19:53 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 3.13.0-107.154 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
- phase: Uploaded
- kernel-stable-phase-changed:Wednesday, 21. December 2016 19:53 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 3.13.0-107.154 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1651629] Re: [Asus X200M] Brightness keys don't work.

2016-12-21 Thread Matthew Brooks
Since I forgot to add this before posting, I should specify that I made
sure to test those parameters with the mainline 4.9 kernel, and not just
the standard Ubuntu one.

Both gave the same results.

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

Title:
  [Asus X200M] Brightness keys don't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1651629] Re: [Asus X200M] Brightness keys don't work.

2016-12-21 Thread Matthew Brooks
That does not make the brightness keys work, unfortunately.

Using those causes the keys to be recognized by the system, and the
popup showing the brightness level will come up and indicate that the
brightness is being changed, but the actual screen brightness doesn't
get changed.

Using those parameters also makes the Gnome brightness slider stop
changing the brightness.

Piping a number to the /sys/class/backlight/intel_backlight/brightness
file still actually changes the brightness when using those parameters,
the same as it does without them.

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

Title:
  [Asus X200M] Brightness keys don't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fn + F5 or F6 is supposed to lower or raise the brightness
  respectively. By default, nothing happens when pushing the
  buttons.Editing the grub config to add "acpi_osi=" to the kernel
  command line seems to make the buttons get recognized, and the
  brightness popup displays, but the actual brightness doesn't change.

  WORKAROUND: Pipe a number into
  "/sys/class/backlight/intel_backlight/brightness", or use the
  brightness slider that shows up in the drop-down from the Gnome status
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alicethegorgon   1381 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 20 20:53:38 2016
  HibernationDevice: RESUME=UUID=563d2c5e-63fe-4f34-b709-343b0d736c48
  InstallationDate: Installed on 2016-12-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 0bda:5605 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0457:1029 Silicon Integrated Systems Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=2ead8d38-6489-4a46-848c-77ea3d7e2ef8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1611583] Re: [Asus F556UA] Trackpad scrolling not working

2016-12-21 Thread Aidan Hodge
Thank you so much, that driver works perfectly!

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

Title:
  [Asus F556UA] Trackpad scrolling not working

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I just got an ASUS F556UA-AS54 laptop and of course I immediately
  deleted windows and installed ubuntu ;). Everything works fine, except
  that the trackpad doesn't seem to be recognized properly. I am certain
  that I have the bug on this page:

  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

  It works for basic functions (clicking, tracking), but I can't scroll
  or do other things a trackpad should do. And, just like the page said,
  the options for my trackpad are missing in the mouse and touchpad
  settings. It's just the single page for the mouse. I've attached the
  three files that the page asked for. Thanks in advance for any help!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aidan  3577 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  9 22:34:45 2016
  HibernationDevice: RESUME=UUID=f6b45d13-6efe-4691-b3b9-f96ef5f74e84
  InstallationDate: Installed on 2016-08-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:3496 IMC Networks 
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X556UA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=ff9e8c9c-7769-45e7-a3ec-962cd53292cf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UA.402
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UA.402:bd03/09/2016:svnASUSTeKCOMPUTERINC.:pnX556UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X556UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1651199] Re: 16.04 - Kernel panic on docker server

2016-12-21 Thread Mike Kaplinskiy
I also noticed that one of the boxes wasn't upgraded (for whatever
reason) and has not had any panics in the last few days. The kernel
version on that box is: Linux ip-10-0-26-30.us-west-2.compute.internal
4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:48:03 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux

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

Title:
  16.04 - Kernel panic on docker server

Status in Linux:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  [31016.057405] BUG: unable to handle kernel paging request at 82c4801e6bda
  [31016.061249] IP: [] __xen_evtchn_do_upcall+0x43/0x80
  [31016.061380] PGD 0 
  [31016.061380] Oops: 0010 [#1] SMP 
  [31016.061380] Modules linked in: binfmt_misc xt_REDIRECT nf_nat_redirect 
veth xt_comment xt_mark ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user 
xfrm_algo xt_addrtype iptable_filter xt_conntrack br_netfilter bridge stp llc 
overlay xt_nat xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables isofs ppdev serio_raw 
parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd ixgbevf psmouse floppy
  [31016.061380] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.4.0-53-generic 
#74-Ubuntu
  [31016.061380] Hardware name: Xen HVM domU, BIOS 4.2.amazon 11/11/2016
  [31016.061380] task: 880406496040 ti: 8804064e task.ti: 
8804064e
  [31016.061380] RIP: 0010:[]  [] 
__xen_evtchn_do_upcall+0x43/0x80
  [31016.061380] RSP: 0018:88040fc43f78  EFLAGS: 00010082
  [31016.061380] RAX:  RBX: 88040fc4b840 RCX: 
0001
  [31016.061380] RDX: fffe RSI: 000123a0 RDI: 
88040fc43f30
  [31016.061380] RBP: 88040fc43f90 R08: f24a R09: 
0001
  [31016.061380] R10: 0001 R11:  R12: 
0001
  [31016.061380] R13: 0003 R14:  R15: 
8804064e
  [31016.178419] FS:  () GS:88040fc4() 
knlGS:
  [31016.178419] CS:  0010 DS:  ES:  CR0: 80050033
  [31016.178419] CR2: 82c4801e6bda CR3: 000204f2f000 CR4: 
001406e0
  [31016.178419] DR0:  DR1:  DR2: 

  [31016.178419] DR3:  DR6: fffe0ff0 DR7: 
0400
  [31016.178419] Stack:
  [31016.178419]   0003  
88040fc43fa8
  [31016.178419]  814d6bc0 81f36a00 8804064e3e90 
81837f32
  [31016.178419]  8804064e3de8   8804064e  

  [31016.178419] Call Trace:
  [31016.178419]   
  [31016.178419]  [] xen_evtchn_do_upcall+0x30/0x40
  [31016.178419]  [] xen_hvm_callback_vector+0x82/0x90
  [31016.178419]   
  [31016.178419]  [] ? native_safe_halt+0x6/0x10
  [31016.178419]  [] default_idle+0x1e/0xe0
  [31016.239315]  [] arch_cpu_idle+0xf/0x20
  [31016.239899]  [] default_idle_call+0x2a/0x40
  [31016.239899]  [] cpu_startup_entry+0x2f1/0x350
  [31016.239899]  [] start_secondary+0x154/0x190
  [31016.239899] Code: 01 00 00 00 65 44 8b 2d dc 56 b3 7e c6 03 00 44 89 e0 65 
0f c1 05 2e d8 b3 7e 85 c0 75 35 48 8b 05 63 ce d0 00 44 89 ef ff 50 50 <9c> 58 
0f 1f 44 00 00 f6 c4 02 75 23 65 8b 05 0a d8 b3 7e 65 c7 
  [31016.239899] RIP  [] __xen_evtchn_do_upcall+0x43/0x80
  [31016.239899]  RSP 
  [31016.239899] CR2: 82c4801e6bda
  [31016.239899] ---[ end trace 5b3e8ea32013e327 ]---
  [31016.239899] Kernel panic - not syncing: Fatal exception in interrupt
  [31016.239899] Kernel Offset: disabled

  
  We believe this appeared in the last 1-2mo of releases, since this started 
happening after we did a `apt-get upgrade` on our machines after a bit of a 
pause. These are EC2 m4.xlarge servers running Ubuntu 16.04.1. They are 
Kubernetes minions, so I assume docker is likely the trigger.

  Unfortunately there aren't really any interesting logs in journalctl
  from the previous boot prior to the panic.

  Let me know what I can do to debug further.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 19 15:56 seq
   crw-rw 1 root audio 116, 33 Dec 19 15:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 

[Kernel-packages] [Bug 1511844] Re: [Acer Aspire ES1-711] System freezes occasionally

2016-12-21 Thread Xwarman
penalvch, excuse me. I will do that in January, asap. I had some trouble
with apport, therefore it was difficult to do so.

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

Title:
  [Acer Aspire ES1-711] System freezes occasionally

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally my system freezes totally in 15.04 and 15.10. Switching
  to Console via Ctrl-Alt-F1 or rebooting via Ctrl-Alt-Del does not
  work.

  Some days my system will run for many hours without any problem,  and
  on other days I experience 2 or 3 freezes in an hour time.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  freek  2223 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 30 21:11:26 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=c4065390-4392-460d-b828-37b12c4605cb
  InstallationDate: Installed on 2015-07-13 (108 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Acer Aspire ES1-711
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=772134c4-7cb5-40d6-b0c7-a6bc4a98efe5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-27 (2 days ago)
  dmi.bios.date: 11/07/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA70_BM
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd11/07/2014:svnAcer:pnAspireES1-711:pvrV1.05:rvnAcer:rnEA70_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire ES1-711
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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

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


  1   2   3   >