date:20161027

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-46.67/onibi__4.4.0-46.67__2016-10-28_04-13-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/1635242

Title:
  linux: 4.4.0-46.67 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  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 Xenial:
  Confirmed

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

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

  -- 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/1635242/+subscriptions

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

[Kernel-packages] [Bug 1541496] Re: Synaptics Touchpad does not work on C15b notebook

[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/1541496

Title:
  Synaptics Touchpad does not work on C15b notebook

Status in linux package in Ubuntu:
  Expired

Bug description:
  After installing Ubuntu 14.04 LTS on my Pegatron C15b notebook, the
  touchpad does not work. This is a dual-boot system, with Windows 10.
  On Windows 10, the Touchpad works fine.

  WORKAROUND: Use kernel parameter:
  i8042.noloop=1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb  3 18:39:57 2016
  InstallationDate: Installed on 2015-11-28 (67 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: Upgraded to trusty on 2016-02-02 (0 days ago)
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  evy1991 F pulseaudio
   /dev/snd/controlC0:  evy1991 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=fde56f96-3316-49fe-938e-7b6cf461984a
  InstallationDate: Installed on 2015-11-28 (99 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: PEGATRON CORPORATION C15B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-51-generic.efi.signed 
root=UUID=140b6e5c-90b9-485b-930a-bd1bc953c21d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-51-generic N/A
   linux-backports-modules-3.19.0-51-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-51-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2016-02-02 (33 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C15B.616
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: C15B
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC15B.616:bd03/18/2014:svnPEGATRONCORPORATION:pnC15B:pvr1.0:rvnPEGATRONCORPORATION:rnC15B:rvr1.0:cvnPEGATRONComputerInc.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: C15B
  dmi.product.version: 1.0
  dmi.sys.vendor: PEGATRON CORPORATION

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

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

[Kernel-packages] [Bug 1376581] Re: DisplayPort monitor not properly detected via HP ultraslim docking station 2013

[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/1376581

Title:
  DisplayPort monitor not properly detected via HP ultraslim docking
  station 2013

Status in linux package in Ubuntu:
  Expired

Bug description:
  DisplayPort monitor not properly detected via HP ultraslim docking
  station 2013

  My configuration:
  - Ubuntu 14.04, with all updates (3.13.0-36.63-generic 3.13.11.6)
  - EliteBook 850 G1 connected to a HP ultraslim docking station 2013.
  - 1 Dell 2209WA connected to the VGA port of the docking
  - 1 Dell P2414H connected to the DP of the docking

  Currently I have the lateste fglrx (14.301.1001), but if was the same
  with the version from Ubuntu repo.

  This is the output from xrandr:
  Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
  eDP1 connected (normal left inverted right x axis y axis)
     1920x1080  60.4 +   59.9 40.3
     1680x1050  60.0 59.9
     1600x1024  60.2
     1400x1050  60.0
     1280x1024  60.0
     1440x900   59.9
     1280x960   60.0
     1360x768   59.8 60.0
     1152x864   60.0
     1024x768   60.0
     800x60060.3 56.2
     640x48059.9
  DP1 disconnected (normal left inverted right x axis y axis)
  HDMI1 disconnected (normal left inverted right x axis y axis)
  DP2 connected primary 1680x1050+0+0 (normal left inverted right x axis y 
axis) 474mm x 296mm
     1680x1050  60.0*+
     1280x1024  75.0 60.0
     1152x864   75.0
     1024x768   75.1 60.0
     800x60075.0 60.3
     640x48075.0 60.0
     720x40070.1
  HDMI2 disconnected (normal left inverted right x axis y axis)

  There is some scrambled image displayed on the DP monitor like in the
  attached image.

  ---
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  amaguran   2383 F pulseaudio
   /dev/snd/controlC2:  amaguran   2383 F pulseaudio
   /dev/snd/controlC0:  amaguran   2383 F pulseaudio
   /dev/snd/controlC1:  amaguran   2383 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-06-08 (135 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP EliteBook 850 G1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic 
root=UUID=26de6228-15cb-4089-8788-f4a0fd918347 ro splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/28/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.20
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.55
  dmi.chassis.asset.tag: CNU4199369
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.20:bd07/28/2014:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.55:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 850 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1582581] Re: bluetooth don't work after upgrade to ubuntu 16.04 from 14.04

[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/1582581

Title:
  bluetooth don't work after upgrade to ubuntu 16.04 from 14.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  after upgrade to ubuntu 16.04 i can't turn on bluetooth on my laptop .
  try reinstall bluez and other bluetooth application same as blueman
  and bluetooth but don't solve problem

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluetooth 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 17 12:19:09 2016
  InstallationDate: Installed on 2016-01-20 (117 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. CX61 2PC
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=f7f87f61-f0ae-47eb-a4a3-272785b96347 ro quiet splash 
intel_pstate=disable i915.lvds_downclock=1 drm.vblankoffdelay=1 
i915.semaphores=1 i915_enable_rc6=1 i915_enable_fbc=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-05-13 (3 days ago)
  dmi.bios.date: 11/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GDIMS.60Q
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16GD
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: CX61 2PC
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GDIMS.60Q:bd11/10/2014:svnMicro-StarInternationalCo.,Ltd.:pnCX612PC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GD:rvrREV1.0:cvnCX612PC:ct10:cvrN/A:
  dmi.product.name: CX61 2PC
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 40:E2:30:F9:2C:4D  ACL MTU: 820:8  SCO MTU: 255:16
DOWN INIT RUNNING 
RX bytes:1274 acl:0 sco:0 events:129 errors:0
TX bytes:25311 acl:0 sco:0 commands:136 errors:0

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

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

[Kernel-packages] [Bug 1584371] Re: Touchpad not working

[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/1584371

Title:
  Touchpad not working

Status in linux package in Ubuntu:
  Expired

Bug description:
  The touchpad of my laptop sometimes doesn't work at all (from boot to
  halt). I am unable to determine when exactly this happens. The
  touchpad worked correctly on the live CD version of Ubuntu. My
  external USB mouse works correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  felix  1402 F pulseaudio
   /dev/snd/controlC1:  felix  1402 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat May 21 19:07:52 2016
  HibernationDevice: RESUME=UUID=658879f1-ea6f-47c7-bd5f-bf6129ecf2f9
  InstallationDate: Installed on 2016-05-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: GIGABYTE P25
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=639c5dff-dc4e-447d-97b5-75f5bd3befe8 ro quiet splash i8042.reset 
i8042.nomux i8042.nopnp i8042.noloop vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P25.30D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P25
  dmi.board.vendor: GIGABYTE
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP25.30D:bd11/12/2013:svnGIGABYTE:pnP25:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnP25:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: P25
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: GIGABYTE

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

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

[Kernel-packages] [Bug 1568573] Re: [Lenovo Thinkpad T460] Ultra Dock external displays not detected after suspend/resume cycle

[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/1568573

Title:
  [Lenovo Thinkpad T460] Ultra Dock external displays not detected after
  suspend/resume cycle

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,
  System is Thinkpad T460, Skylake graphics, Thinkpad Ultra dock. DVI and HDMI 
displays connected via dock. 4.4.0-18.

  After a suspend-resume cycle, when the laptop is docked the dock
  connected external displays are not initialized/connected. If I
  disconnect the displays from the dock and connect them directly to the
  laptop, they are initialized successfully and can be configured via
  xrandr etc.

  If the laptop is power cycled, the displays can be used normally until
  the next suspend-resume cycle.

  Example from relevant dmesg:
  [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many 
voltage retries, give up
  [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many 
voltage retries, give up
  [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many 
voltage retries, give up
  [drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to train DP, 
aborting
  [drm:intel_dp_set_idle_link_train [i915_bpo]] *ERROR* Timed out waiting for 
DP idle patterns
  [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many 
voltage retries, give up
  [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many 
voltage retries, give up
  [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many 
voltage retries, give up

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ryan   1838 F pulseaudio
  Date: Sun Apr 10 09:39:32 2016
  HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d
  InstallationDate: Installed on 2015-09-21 (201 days ago)
  InstallationMedia: It
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FNCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic 
root=/dev/mapper/it--vg-root ro quiet
  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-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-24 (45 days ago)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FNCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FNCTO1WW
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1634892] Re: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error

2016-10-27 Thread Yoshi Kadokawa

Had the same Invalid argument error in 3.14-rc1 as well,
but for 3.15.0-031500, I could set the parameter successfully.

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

Title:
  Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or
  later causes 'invalid argument' error

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-trusty package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress

Bug description:
  Setting net.ipv4.neigh.default.gc_thresh1/2/3 on the 3.13.0-96-generic
  kernel and below worked fine using the following:

  $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128
  128

  As of 3.13.0-97-generic, though, it no longer works as expected:

  $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128
  error: "Invalid argument" setting key "net.ipv4.neigh.default.gc_thresh1"

  There are two potentially related revisions in the -97 release -
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts-
  backport-trusty&id=563cf19389d8e999e69d6c94995966aeaf7c3a08 and
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts-
  backport-trusty&id=7b82096b0ebc9bf487b390fe970d66ffa5a5774e.

  The expected behavior is that changing neighbor table settings works
  using 'sysctl -w' with the same values as before the -97 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-98-generic 3.13.0-98.145~precise1
  ProcVersionSignature: Ubuntu 3.13.0-98.145~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-98-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-98-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1p', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  CurrentDmesg: [4.586115] NET: Registered protocol family 40
  Date: Wed Oct 19 06:13:36 2016
  HibernationDevice: RESUME=UUID=d32abfeb-623f-4c11-ae4a-a7babe8c2139
  InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release 
amd64 (20140806.1)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic 
root=UUID=febea164-78c3-4d3a-a0ce-0f09990df608 ro find_preseed=/preseed.cfg 
noprompt quiet
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-98-generic N/A
   linux-backports-modules-3.13.0-98-generic  N/A
   linux-firmware 1.79.16
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1636537] Re: linux: 3.2.0-115.157 -proposed tracker

2016-10-27 Thread Po-Hsu Lin

As per http://kernel.ubuntu.com/sru/sru-report.html
No verification-needed bugs this time.

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

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

Title:
  linux: 3.2.0-115.157 -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:
  Fix Released
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:
  Confirmed

Bug description:
  This bug is for tracking the 3.2.0-115.157 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/1636537/+subscriptions

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

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

This change was made by a bot.

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

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

Title:
  Xubuntu 16.10: drm errors causing slow boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have been getting drm errors since updating to 16.10 causing slow
  boot times. Ex:

  
3.830465] jhm-Inspiron-1520 kernel: input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input5

  [   13.792249] jhm-Inspiron-1520 kernel:
  [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR*
  [CRTC:26:pipe A] flip_done timed out

  
  There is ten second gap in the above adjacent lines. I have a few of these in 
the journal log.
  These errors also cause Xorg to stall during mode setting also, as seen in 
the adjacent Xorg.0.log file.

  [55.988] (II) modeset(0): Output VGA-1 has no monitor section
  [66.615] (II) modeset(0): Output SVIDEO-1 has no monitor section

  Using the Ubuntu test kernels, the best result I have gotten is from
  kernel 4.5.6. At 4.6.0 the wheels start to come off the wagon.  At
  4.9.0 rc1 the boot stopped at the busybox initrd shell.

  4.8.0 fails decompressing the hibernate image as well.

  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 i686
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhm1262 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Oct 27 17:02:19 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=bd7562ce-d720-4e95-995e-48f0ec1a77aa
  InstallationDate: Installed on 2016-10-12 (15 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  MachineType: Dell Inc. Inspiron 1520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=5dc9cf92-93d8-4e84-826d-6b4d5f6e1c0d ro plymouth:debug=1 
vesafb.invalid=1
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-generic N/A
   linux-backports-modules-4.8.0-26-generic  N/A
   linux-firmware1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (12 days ago)
  dmi.bios.date: 02/03/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0KY767
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd02/03/2008:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn0KY767:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1520
  dmi.sys.vendor: Dell Inc.

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

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

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

This change was made by a bot.

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

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

Title:
  HP printer no longer working after upgrade.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My HP-Deskjet-F2100-series printer stopped working after upgrade from 16.04 
to 16.10. It worked fine in 16.04. I've tried several different printing jobs, 
and it's the same for every one, it prints half of a page and then stops. I 
have a laptop with 16.04 on it, and when I tried the printer there it worked 
fine.
Thank you for your time.

  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
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robin  2394 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 27 18:46:42 2016
  HibernationDevice: RESUME=UUID=ad90ea5b-2c52-473c-8431-7a785290e6d4
  InstallationDate: Installed on 2016-10-25 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s10   no wireless extensions.
  MachineType: Acer Aspire X3400G
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=6166bf8f-97c2-4915-8e8d-3b3e57c10816 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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-27 (0 days ago)
  dmi.bios.date: 06/01/2010
  dmi.bios.vendor: AMI
  dmi.bios.version: P01-B2
  dmi.board.name: Aspire X3400G
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAMI:bvrP01-B2:bd06/01/2010:svnAcer:pnAspireX3400G:pvr:rvnAcer:rnAspireX3400G:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Aspire X3400G
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1637347] [NEW] Xubuntu 16.10: drm errors causing slow boot

2016-10-27 Thread Jeff

Public bug reported:

I have been getting drm errors since updating to 16.10 causing slow boot
times. Ex:


  3.830465] jhm-Inspiron-1520 kernel: input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input5

[   13.792249] jhm-Inspiron-1520 kernel:
[drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR*
[CRTC:26:pipe A] flip_done timed out


There is ten second gap in the above adjacent lines. I have a few of these in 
the journal log.
These errors also cause Xorg to stall during mode setting also, as seen in the 
adjacent Xorg.0.log file.

[55.988] (II) modeset(0): Output VGA-1 has no monitor section
[66.615] (II) modeset(0): Output SVIDEO-1 has no monitor section

Using the Ubuntu test kernels, the best result I have gotten is from
kernel 4.5.6. At 4.6.0 the wheels start to come off the wagon.  At 4.9.0
rc1 the boot stopped at the busybox initrd shell.

4.8.0 fails decompressing the hibernate image as well.

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 i686
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jhm1262 F pulseaudio
CurrentDesktop: XFCE
Date: Thu Oct 27 17:02:19 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=bd7562ce-d720-4e95-995e-48f0ec1a77aa
InstallationDate: Installed on 2016-10-12 (15 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: Dell Inc. Inspiron 1520
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=5dc9cf92-93d8-4e84-826d-6b4d5f6e1c0d ro plymouth:debug=1 
vesafb.invalid=1
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-26-generic N/A
 linux-backports-modules-4.8.0-26-generic  N/A
 linux-firmware1.161
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2016-10-15 (12 days ago)
dmi.bios.date: 02/03/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0KY767
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd02/03/2008:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn0KY767:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1520
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-bug i386 yakkety

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

Title:
  Xubuntu 16.10: drm errors causing slow boot

Status in linux package in Ubuntu:
  New

Bug description:
  I have been getting drm errors since updating to 16.10 causing slow
  boot times. Ex:

  
3.830465] jhm-Inspiron-1520 kernel: input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input5

  [   13.792249] jhm-Inspiron-1520 kernel:
  [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR*
  [CRTC:26:pipe A] flip_done timed out

  
  There is ten second gap in the above adjacent lines. I have a few of these in 
the journal log.
  These errors also cause Xorg to stall during mode setting also, as seen in 
the adjacent Xorg.0.log file.

  [55.988] (II) modeset(0): Output VGA-1 has no monitor section
  [66.615] (II) modeset(0): Output SVIDEO-1 has no monitor section

  Using the Ubuntu test kernels, the best result I have gotten is from
  kernel 4.5.6. At 4.6.0 the wheels start to come off the wagon.  At
  4.9.0 rc1 the boot stopped at the busybox initrd shell.

  4.8.0 fails decompressing the hibernate image as well.

  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 i686
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhm1262 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Oct 27 17:02:19 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=bd7562ce-d720-4e95-995e-48f0ec1a77aa
  InstallationDate: Installed on 2016-10-12 (15 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  MachineType: Dell Inc. Inspiron 1520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=5dc9cf92-93d8-4e84-826d-6b4d5f6e1c0d ro plymouth:debug=1 
vesafb.invalid=1
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-generic N/A
   linux-backports-modules-4.8.0-26-generic  N/A
   linux-firmware1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Upgrade

[Kernel-packages] [Bug 1637346] [NEW] HP printer no longer working after upgrade.

2016-10-27 Thread Robin Hicks

Public bug reported:

My HP-Deskjet-F2100-series printer stopped working after upgrade from 16.04 to 
16.10. It worked fine in 16.04. I've tried several different printing jobs, and 
it's the same for every one, it prints half of a page and then stops. I have a 
laptop with 16.04 on it, and when I tried the printer there it worked fine.
  Thank you for your time.

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
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  robin  2394 F pulseaudio
CurrentDesktop: Unity
Date: Thu Oct 27 18:46:42 2016
HibernationDevice: RESUME=UUID=ad90ea5b-2c52-473c-8431-7a785290e6d4
InstallationDate: Installed on 2016-10-25 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 lono wireless extensions.
 
 enp0s10   no wireless extensions.
MachineType: Acer Aspire X3400G
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=6166bf8f-97c2-4915-8e8d-3b3e57c10816 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
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2016-10-27 (0 days ago)
dmi.bios.date: 06/01/2010
dmi.bios.vendor: AMI
dmi.bios.version: P01-B2
dmi.board.name: Aspire X3400G
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAMI:bvrP01-B2:bd06/01/2010:svnAcer:pnAspireX3400G:pvr:rvnAcer:rnAspireX3400G:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Aspire X3400G
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug yakkety

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

Title:
  HP printer no longer working after upgrade.

Status in linux package in Ubuntu:
  New

Bug description:
  My HP-Deskjet-F2100-series printer stopped working after upgrade from 16.04 
to 16.10. It worked fine in 16.04. I've tried several different printing jobs, 
and it's the same for every one, it prints half of a page and then stops. I 
have a laptop with 16.04 on it, and when I tried the printer there it worked 
fine.
Thank you for your time.

  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
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robin  2394 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 27 18:46:42 2016
  HibernationDevice: RESUME=UUID=ad90ea5b-2c52-473c-8431-7a785290e6d4
  InstallationDate: Installed on 2016-10-25 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s10   no wireless extensions.
  MachineType: Acer Aspire X3400G
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=6166bf8f-97c2-4915-8e8d-3b3e57c10816 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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-27 (0 days ago)
  dmi.bios.date: 06/01/2010
  dmi.bios.vendor: AMI
  dmi.bios.version: P01-B2
  dmi.board.name: Aspire X3400G
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAMI:bvrP01-B2:bd06/01/2010:svnAcer:pnAspireX3400G:pvr:rvnAcer:rnAspireX3400G:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Aspire X3400G
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1636539] Re: linux-ti-omap4: 3.2.0-1493.120 -proposed tracker

2016-10-27 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/1636539

Title:
  linux-ti-omap4: 3.2.0-1493.120 -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 3.2.0-1493.120 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: 1636537
  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/1636539/+subscriptions

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

[Kernel-packages] [Bug 1636537] Re: linux: 3.2.0-115.157 -proposed tracker

2016-10-27 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/1636537

Title:
  linux: 3.2.0-115.157 -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:
  Confirmed

Bug description:
  This bug is for tracking the 3.2.0-115.157 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/1636537/+subscriptions

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

[Kernel-packages] [Bug 1636541] Re: linux-armadaxp: 3.2.0-1677.104 -proposed tracker

2016-10-27 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/1636541

Title:
  linux-armadaxp: 3.2.0-1677.104 -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-1677.104 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: 1636537
  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/1636541/+subscriptions

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

[Kernel-packages] [Bug 1597961] Re: Qualcomm Atheros Bluetooth 4.0 not working on Ubuntu 16.04

2016-10-27 Thread Antonio Vinicius Menezes Medeiros

Tested the latest upstream kernel from
https://wiki.ubuntu.com/KernelMainlineBuilds currently 4.8.4 on Ubuntu
16.04. My Bluetooth adapter was not recognized.

vinicius@viny-notebook:~$ uname -a
Linux viny-notebook 4.8.4-040804-generic #201610220733 SMP Sat Oct 22 11:35:18 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
vinicius@viny-notebook:~$ lspci -knn | grep Net -A2; lsusb
03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: Lite-On Communications Inc QCA9565 / AR9565 Wireless Network 
Adapter [11ad:0803]
Kernel driver in use: ath9k
Kernel modules: ath9k
Bus 001 Device 002: ID 8087:8001 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
Bus 002 Device 003: ID 1bcf:2c81 Sunplus Innovation Technology Inc. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
vinicius@viny-notebook:~$ dmesg | grep -i bluetooth
[   11.453799] Bluetooth: Core ver 2.21
[   11.453822] Bluetooth: HCI device and connection manager initialized
[   11.453825] Bluetooth: HCI socket layer initialized
[   11.453827] Bluetooth: L2CAP socket layer initialized
[   11.453833] Bluetooth: SCO socket layer initialized
[   54.059133] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   54.059135] Bluetooth: BNEP filters: protocol multicast
[   54.059139] Bluetooth: BNEP socket layer initialized
vinicius@viny-notebook:~$ usb-devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 2
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=04.08
S:  Manufacturer=Linux 4.8.4-040804-generic ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=:00:1d.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 8
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=8087 ProdID=8001 Rev=00.03
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh=11
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=04.08
S:  Manufacturer=Linux 4.8.4-040804-generic xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=:00:14.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=02 Lev=01 Prnt=01 Port=06 Cnt=01 Dev#=  3 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1bcf ProdID=2c81 Rev=00.05
S:  Manufacturer=NC2141103M50708908LM05
S:  Product=HD WebCam
C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
I:  If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo

T:  Bus=02 Lev=01 Prnt=01 Port=07 Cnt=02 Dev#=  4 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs=  1
P:  Vendor=0bda ProdID=0129 Rev=39.60
S:  Manufacturer=Generic
S:  Product=USB2.0-CRW
S:  SerialNumber=2010020139600
C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=06 Prot=50 Driver=rtsx_usb

T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 4
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev=04.08
S:  Manufacturer=Linux 4.8.4-040804-generic xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=:00:14.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
vinicius@viny-notebook:~$ 

This time the transceiver for my wireless keyboard + mouse was
disconnected.

I'm going to download Ubuntu 16.10 and see if it recognizes my Bluetooth
adapter.

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

Title:
  Qualcomm Atheros Bluetooth 4.0 not working on Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While using Windows with my Acer Aspire E5-573, I'm able to use the Bluetooth:
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: Lite-On Communications Inc QCA9565 / AR9565 Wireless Network 
Adapter [11ad:0803]

  I've installed Ubuntu 16.04 in dual boot. While using Ubuntu, the
  Bluetooth adapter is the only piece of hardware that does not work.

  $ dmesg | grep -i bluetooth
  [   20.905534] Bluetooth: Core ver 2.21
  [   20.905548] Bluetooth: HCI device and connection manager initialized
  [   20.905551] Bluetooth: HCI socket layer initialized
  [   20.905553] Bluetooth: L2CAP socket layer initialized
  [   20.905557] B

[Kernel-packages] [Bug 1634892] Re: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error

2016-10-27 Thread Joseph Salisbury

We might need to perform a "Reverse" bisect to identify the fix that
prevented this commit from being reverted in newer kernel versions.

Can you first confirm that the bug also exists in upstream v3.14-rc1?  It can 
be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc1-trusty/

If the bug DOES also exist in v3.14-rc1, then test v3.15:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-utopic/

We can decide the next step based on the results of these two test.

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

Title:
  Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or
  later causes 'invalid argument' error

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-trusty package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress

Bug description:
  Setting net.ipv4.neigh.default.gc_thresh1/2/3 on the 3.13.0-96-generic
  kernel and below worked fine using the following:

  $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128
  128

  As of 3.13.0-97-generic, though, it no longer works as expected:

  $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128
  error: "Invalid argument" setting key "net.ipv4.neigh.default.gc_thresh1"

  There are two potentially related revisions in the -97 release -
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts-
  backport-trusty&id=563cf19389d8e999e69d6c94995966aeaf7c3a08 and
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts-
  backport-trusty&id=7b82096b0ebc9bf487b390fe970d66ffa5a5774e.

  The expected behavior is that changing neighbor table settings works
  using 'sysctl -w' with the same values as before the -97 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-98-generic 3.13.0-98.145~precise1
  ProcVersionSignature: Ubuntu 3.13.0-98.145~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-98-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-98-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1p', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  CurrentDmesg: [4.586115] NET: Registered protocol family 40
  Date: Wed Oct 19 06:13:36 2016
  HibernationDevice: RESUME=UUID=d32abfeb-623f-4c11-ae4a-a7babe8c2139
  InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release 
amd64 (20140806.1)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic 
root=UUID=febea164-78c3-4d3a-a0ce-0f09990df608 ro find_preseed=/preseed.cfg 
noprompt quiet
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-98-generic N/A
   linux-backports-modules-3.13.0-98-generic  N/A
   linux-firmware 1.79.16
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1636541] Re: linux-armadaxp: 3.2.0-1677.104 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => 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-1677.104 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: 1636537
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Thursday, 27. October 2016 23:32 UTC

** Description changed:

  This bug is for tracking the 3.2.0-1677.104 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: 1636537
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Thursday, 27. October 2016 23:32 UTC
+ 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/1636541

Title:
  linux-armadaxp: 3.2.0-1677.104 -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-1677.104 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: 1636537
  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/1636541/+subscriptions

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

Re: [Kernel-packages] [Bug 1637303] [NEW] Move some device drivers build from kernel built-in to modules

2016-10-27 Thread Dimitri John Ledkov

Last time i have tried this the virtio modules did not end up in the d-i
udebs or in the cloud images initrd. The result was failure to install in
KVM and failure to boot cloud images. When these are moved to modules could
we make that virtio modules end up in the udebs & main linux-image deb &
cloud images' initrd? If all that works - virtio could be modules on all
architectures.

On 27 Oct 2016 21:00, "bugproxy"  wrote:

> Public bug reported:
>
> Some drivers in Ubuntu are built as kernel built-in components, not
> allowing some module interesting features like blacklist on boot
> command-line or module removal/replacement. Also, modules has debug
> advantages compared to built-in kernel components, like the possibility
> to easy build custom-debug modules against kernel tree and replace them
> using modprobe on running system.
>
> This feature is a request to Canonical move some currently built-in
> drivers to module build system on Power platform, by changing the kernel
> config file.
>
> The drivers in question are: tg3, virtio-blk and virtio-net.
> The kernel config file parameters related to those 3 drivers are:
>
> CONFIG_TIGON3, CONFIG_VIRTIO_BLK and CONFIG_VIRTIO_NET.
> They all are currently set as "=y"; we're requesting a change to "=m".
>
> Thanks in advance,
>
>
> Guilherme
>
> ** Affects: linux (Ubuntu)
>  Importance: Undecided
>  Assignee: Canonical Kernel Team (canonical-kernel-team)
>  Status: New
>
>
> ** Tags: architecture-ppc64le bugnameltc-147981 severity-high
> targetmilestone-inin1704
>
> ** Tags added: architecture-ppc64le bugnameltc-147981 severity-high
> targetmilestone-inin1704
>
> ** Changed in: ubuntu
>  Assignee: (unassigned) => Taco Screen team (taco-screen-team)
>
> ** Package changed: ubuntu => linux (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to Ubuntu.
> Matching subscriptions: architecture-ppc64le
> https://bugs.launchpad.net/bugs/1637303
>
> Title:
>   Move some device drivers build from kernel built-in to modules
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1637303/+subscriptions
>

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

Title:
  Move some device drivers build from kernel built-in to modules

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Some drivers in Ubuntu are built as kernel built-in components, not
  allowing some module interesting features like blacklist on boot
  command-line or module removal/replacement. Also, modules has debug
  advantages compared to built-in kernel components, like the
  possibility to easy build custom-debug modules against kernel tree and
  replace them using modprobe on running system.

  This feature is a request to Canonical move some currently built-in
  drivers to module build system on Power platform, by changing the
  kernel config file.

  The drivers in question are: tg3, virtio-blk and virtio-net.
  The kernel config file parameters related to those 3 drivers are:

  CONFIG_TIGON3, CONFIG_VIRTIO_BLK and CONFIG_VIRTIO_NET.
  They all are currently set as "=y"; we're requesting a change to "=m".

  Thanks in advance,

  Guilherme

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

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

[Kernel-packages] [Bug 1636537] Re: linux: 3.2.0-115.157 -proposed tracker

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

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

Title:
  linux: 3.2.0-115.157 -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:
  Confirmed

Bug description:
  This bug is for tracking the 3.2.0-115.157 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/1636537/+subscriptions

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

[Kernel-packages] [Bug 1626749] Re: autofs set $USER to "root" instead of current user

2016-10-27 Thread Fabio

FYI ...and also with kernel 4.4.0-45.

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  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-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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

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

This change was made by a bot.

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

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

Title:
  Secondary monitor blanks out randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When hooked up to a second monitor it will blank out occastionally.
  Same issue on two external monitors. Both hooked up via MiniDisplay
  port.

  Every time it happens i have a the following log in my dmesg:

  [47192.964713] [drm:intel_cpu_fifo_underrun_irq_handler [i915]]
  *ERROR* CPU pipe B FIFO underrun

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-generic 4.8.0.26.35
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  bbennett   2693 F pulseaudio
   /dev/snd/controlC1:  bbennett   2693 F pulseaudio
   /dev/snd/controlC0:  bbennett   2693 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 27 16:03:21 2016
  HibernationDevice: RESUME=UUID=872ed834-8bdc-4c58-a9ab-6c0ad9ec3ca8
  InstallationDate: Installed on 2016-10-17 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20FRS0XT00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-26-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root 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: 03/30/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET38W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS0XT00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET38W(1.12):bd03/30/2016:svnLENOVO:pn20FRS0XT00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FRS0XT00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FRS0XT00
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1616214] Re: Macbook Air resumes immediately after suspend

2016-10-27 Thread Balint Reczey

Same on Debian with 3.16.36-1+deb8u2

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

Title:
   Macbook Air resumes immediately after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Based on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311724
  I am opening this bug to tackle the issue of a Macbook Air that
  resumes immediately after suspending.

  I have the exact same symptoms as those described in the first bug.
  The first suspend on battery power works without any issues. After
  that, even trying the 2x pm-suspend method doesn't work.

  Here's an excerpt from dmesg showing the suspend:

  [11363.316508] PM: Syncing filesystems ... done.
  [11363.683228] PM: Preparing system for sleep (mem)
  [11363.683388] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [11363.685415] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [11363.686602] PM: Suspending system (mem)
  [11363.686629] Suspending console(s) (use no_console_suspend to debug)
  [11363.686839] sd 1:0:0:0: [sda] Synchronizing SCSI cache
  [11363.686890] sd 1:0:0:0: [sda] Stopping disk
  [11363.689056] R8188EU: INFO indicate disassoc
  [11364.057112] PM: suspend of devices complete after 370.364 msecs
  [11364.079232] PM: late suspend of devices complete after 22.117 msecs
  [11364.079400] thunderbolt :07:00.0: suspending...
  [11364.079620] thunderbolt :07:00.0: stopping RX ring 0
  [11364.079623] thunderbolt :07:00.0: disabling interrupt at register 
0x38200 bit 12 (0x1001 -> 0x1)
  [11364.079628] thunderbolt :07:00.0: stopping TX ring 0
  [11364.079631] thunderbolt :07:00.0: disabling interrupt at register 
0x38200 bit 0 (0x1 -> 0x0)
  [11364.079633] thunderbolt :07:00.0: control channel stopped
  [11364.079634] thunderbolt :07:00.0: suspend finished
  [11364.080060] xhci_hcd :00:14.0: System wakeup enabled by ACPI
  [11364.095334] pcieport :05:00.0: quirk: cutting power to thunderbolt 
controller...
  [11364.506336] mba6x_bl: Invalid response at reg: 0x1 (len: 24)
  [11364.733532] mba6x_bl: failed to set brightness
  [11364.733583] PM: noirq suspend of devices complete after 654.350 msecs
  [11364.733853] ACPI: Preparing to enter system sleep state S3
  [11364.763238] ACPI : EC: EC stopped
  [11364.763238] PM: Saving platform NVS memory
  [11364.763240] Disabling non-boot CPUs ...
  [11364.763530] Broke affinity for irq 49
  [11364.764553] smpboot: CPU 1 is now offline
  [11364.776286] Broke affinity for irq 18
  [11364.776293] Broke affinity for irq 44
  [11364.776299] Broke affinity for irq 46
  [11364.776305] Broke affinity for irq 48
  [11364.776309] Broke affinity for irq 49
  [11364.777347] smpboot: CPU 2 is now offline
  [11364.787918] Broke affinity for irq 8
  [11364.787921] Broke affinity for irq 9
  [11364.787924] Broke affinity for irq 16
  [11364.787927] Broke affinity for irq 18
  [11364.787930] Broke affinity for irq 44
  [11364.787933] Broke affinity for irq 45
  [11364.787935] Broke affinity for irq 46
  [11364.787937] Broke affinity for irq 47
  [11364.787940] Broke affinity for irq 48
  [11364.787942] Broke affinity for irq 49
  [11364.787945] Broke affinity for irq 54
  [11364.788969] smpboot: CPU 3 is now offline
  [11364.805918] ACPI: Low-level resume complete
  [11364.806002] ACPI : EC: EC started
  [11364.806004] PM: Restoring platform NVS memory
  [11364.806415] Enabling non-boot CPUs ...
  [11364.826307] x86: Booting SMP configuration:
  [11364.826309] smpboot: Booting Node 0 Processor 1 APIC 0x2
  [11364.837869]  cache: parent cpu1 should not be sleeping
  [11364.838662] CPU1 is up
  [11365.018821] smpboot: Booting Node 0 Processor 2 APIC 0x1
  [11365.074966]  cache: parent cpu2 should not be sleeping
  [11365.075057] CPU2 is up
  [11365.273364] smpboot: Booting Node 0 Processor 3 APIC 0x3
  [11365.325736]  cache: parent cpu3 should not be sleeping
  [11365.350542] CPU3 is up
  [11365.354192] ACPI: Waking up from system sleep state S3
  [11365.430255] xhci_hcd :00:14.0: System wakeup disabled by ACPI
  [11365.431123] pcieport :06:03.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [11365.431125] pcieport :06:04.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [11365.431219] pcieport :06:05.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [11365.431309] pcieport :06:06.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [11365.446161] thunderbolt :07:00.0: resuming...
  [11365.446162] thunderbolt :07:00.0: control channel starting...
  [11365.446165] thunderbolt :07:00.0: starting TX ring 0
  [11365.446171] thunderbolt :07:00.0: enabling interrupt at register 
0x38200 bit 0 (0x0 -> 0x1)
  [11365.446172] thunderbolt :07:00.0: starting RX ring 0
  [11365.446177] thunderbolt :07:00.

[Kernel-packages] [Bug 1636647] Re: perf stat interval display broken on 4.4.x

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

Title:
  perf stat interval display broken on 4.4.x

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  perf stat with interval display (-I flag) gives incorrect results
  because the following perf/urgent patch has not been applied.  (It's
  not in upstream longterm 4.4 either.)

  https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
  
stable.git/commit/tools/perf/util/stat.c?id=51fd2df1e882a3c2a3f4b6c9ff243a93c9046dba

  # cat /proc/version_signature
  Ubuntu 4.4.0-34.53-generic 4.4.15

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

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

[Kernel-packages] [Bug 1637329] [NEW] Secondary monitor blanks out randomly

2016-10-27 Thread nemith

Public bug reported:

When hooked up to a second monitor it will blank out occastionally.
Same issue on two external monitors. Both hooked up via MiniDisplay
port.

Every time it happens i have a the following log in my dmesg:

[47192.964713] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR*
CPU pipe B FIFO underrun

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-generic 4.8.0.26.35
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  bbennett   2693 F pulseaudio
 /dev/snd/controlC1:  bbennett   2693 F pulseaudio
 /dev/snd/controlC0:  bbennett   2693 F pulseaudio
CurrentDesktop: Unity
Date: Thu Oct 27 16:03:21 2016
HibernationDevice: RESUME=UUID=872ed834-8bdc-4c58-a9ab-6c0ad9ec3ca8
InstallationDate: Installed on 2016-10-17 (10 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: LENOVO 20FRS0XT00
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-26-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root 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: 03/30/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET38W (1.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FRS0XT00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET38W(1.12):bd03/30/2016:svnLENOVO:pn20FRS0XT00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FRS0XT00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20FRS0XT00
dmi.product.version: ThinkPad X1 Carbon 4th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Secondary monitor blanks out randomly

Status in linux package in Ubuntu:
  New

Bug description:
  When hooked up to a second monitor it will blank out occastionally.
  Same issue on two external monitors. Both hooked up via MiniDisplay
  port.

  Every time it happens i have a the following log in my dmesg:

  [47192.964713] [drm:intel_cpu_fifo_underrun_irq_handler [i915]]
  *ERROR* CPU pipe B FIFO underrun

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-generic 4.8.0.26.35
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  bbennett   2693 F pulseaudio
   /dev/snd/controlC1:  bbennett   2693 F pulseaudio
   /dev/snd/controlC0:  bbennett   2693 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 27 16:03:21 2016
  HibernationDevice: RESUME=UUID=872ed834-8bdc-4c58-a9ab-6c0ad9ec3ca8
  InstallationDate: Installed on 2016-10-17 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20FRS0XT00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-26-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root 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: 03/30/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET38W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS0XT00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET38W(1.12):bd03/30/2016:svnLENOVO:pn20FRS0XT00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FRS0XT00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FRS0XT00
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1636647] Re: perf stat interval display broken on 4.4.x

** Attachment added: "lspci-vvnn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636647/+attachment/4768418/+files/lspci-vvnn.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/1636647

Title:
  perf stat interval display broken on 4.4.x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  perf stat with interval display (-I flag) gives incorrect results
  because the following perf/urgent patch has not been applied.  (It's
  not in upstream longterm 4.4 either.)

  https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
  
stable.git/commit/tools/perf/util/stat.c?id=51fd2df1e882a3c2a3f4b6c9ff243a93c9046dba

  # cat /proc/version_signature
  Ubuntu 4.4.0-34.53-generic 4.4.15

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

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

[Kernel-packages] [Bug 1636647] Re: perf stat interval display broken on 4.4.x

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636647/+attachment/4768417/+files/dmesg.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/1636647

Title:
  perf stat interval display broken on 4.4.x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  perf stat with interval display (-I flag) gives incorrect results
  because the following perf/urgent patch has not been applied.  (It's
  not in upstream longterm 4.4 either.)

  https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
  
stable.git/commit/tools/perf/util/stat.c?id=51fd2df1e882a3c2a3f4b6c9ff243a93c9046dba

  # cat /proc/version_signature
  Ubuntu 4.4.0-34.53-generic 4.4.15

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

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

[Kernel-packages] [Bug 1636647] Re: perf stat interval display broken on 4.4.x

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636647/+attachment/4768409/+files/version.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/1636647

Title:
  perf stat interval display broken on 4.4.x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  perf stat with interval display (-I flag) gives incorrect results
  because the following perf/urgent patch has not been applied.  (It's
  not in upstream longterm 4.4 either.)

  https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
  
stable.git/commit/tools/perf/util/stat.c?id=51fd2df1e882a3c2a3f4b6c9ff243a93c9046dba

  # cat /proc/version_signature
  Ubuntu 4.4.0-34.53-generic 4.4.15

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

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

[Kernel-packages] [Bug 1636647] Re: perf stat interval display broken on 4.4.x

** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636647/+attachment/4768408/+files/uname-a.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/1636647

Title:
  perf stat interval display broken on 4.4.x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  perf stat with interval display (-I flag) gives incorrect results
  because the following perf/urgent patch has not been applied.  (It's
  not in upstream longterm 4.4 either.)

  https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
  
stable.git/commit/tools/perf/util/stat.c?id=51fd2df1e882a3c2a3f4b6c9ff243a93c9046dba

  # cat /proc/version_signature
  Ubuntu 4.4.0-34.53-generic 4.4.15

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

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

[Kernel-packages] [Bug 1637303] Re: Move some device drivers build from kernel built-in to modules

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)

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

Title:
  Move some device drivers build from kernel built-in to modules

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Some drivers in Ubuntu are built as kernel built-in components, not
  allowing some module interesting features like blacklist on boot
  command-line or module removal/replacement. Also, modules has debug
  advantages compared to built-in kernel components, like the
  possibility to easy build custom-debug modules against kernel tree and
  replace them using modprobe on running system.

  This feature is a request to Canonical move some currently built-in
  drivers to module build system on Power platform, by changing the
  kernel config file.

  The drivers in question are: tg3, virtio-blk and virtio-net.
  The kernel config file parameters related to those 3 drivers are:

  CONFIG_TIGON3, CONFIG_VIRTIO_BLK and CONFIG_VIRTIO_NET.
  They all are currently set as "=y"; we're requesting a change to "=m".

  Thanks in advance,


  Guilherme

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

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

[Kernel-packages] [Bug 1630063] Re: specific USB devices disconnect and don't reconnect

2016-10-27 Thread Martin

This "HcDoneHead not written back; disabled" bug also affects me with
the device "ID 08bb:27c4 Texas Instruments" on the 4.8.4 Kernel from
Ubuntu mainline. With the kernel 4.7.10 it works without problems.

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

Title:
  specific USB devices disconnect and don't reconnect

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  2 USB ports randomly disconnect and don't reconnect (it's always the
  same two), and in dmesg all I get is

  "
  [ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled
  [ 1276.916467] ohci-pci :00:12.0: HC died; cleaning up
  [ 1276.916553] usb 3-1: USB disconnect, device number 2
  [ 1277.017302] usb 3-2: USB disconnect, device number 3
  "
  This only started happening when Yakkety went to the 4.8 branch, with 4.7 
branch this doesn't occur, hence the bug report since it's unlikely that a 
hardware failure will only stick to one OS and one branch of the kernel for 
that OS. (these USB ports don't randomly die on Windows or BSD, I've tested 
that in the past couple of days)

  
  kernel version: 4.8.0.17.27
  Ubuntu version
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  c_smith2213 F pulseaudio
   /dev/snd/controlC0:  c_smith2213 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1a29baaa-55ea-4817-ba45-8c618f65ec4b
  InstallationDate: Installed on 2016-10-03 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161002)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic 
root=/dev/mapper/Linux-root ro nomodeset quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-78LMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1637303] Re: Move some device drivers build from kernel built-in to modules

https://lists.ubuntu.com/archives/kernel-team/2016-October/080636.html
https://lists.ubuntu.com/archives/kernel-team/2016-October/080637.html

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: New

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

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

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

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

Title:
  Move some device drivers build from kernel built-in to modules

Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  New

Bug description:
  Some drivers in Ubuntu are built as kernel built-in components, not
  allowing some module interesting features like blacklist on boot
  command-line or module removal/replacement. Also, modules has debug
  advantages compared to built-in kernel components, like the
  possibility to easy build custom-debug modules against kernel tree and
  replace them using modprobe on running system.

  This feature is a request to Canonical move some currently built-in
  drivers to module build system on Power platform, by changing the
  kernel config file.

  The drivers in question are: tg3, virtio-blk and virtio-net.
  The kernel config file parameters related to those 3 drivers are:

  CONFIG_TIGON3, CONFIG_VIRTIO_BLK and CONFIG_VIRTIO_NET.
  They all are currently set as "=y"; we're requesting a change to "=m".

  Thanks in advance,


  Guilherme

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

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

[Kernel-packages] [Bug 1608236] Re: Regression: S-video output does not work

2016-10-27 Thread Joseph Salisbury

Thanks for all the testing, I will contact the patch author for
feedback.  Can you run one additional test?  Can you test the latest
mainline kernel to see if there is already a fix for the bug?  The
4.9-rc2 kernel can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc2/

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

Title:
  Regression: S-video output does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Regression. S-video output can not be used. It works by 4.4.0-22-generic.
  xrandr tells on 4.4.0-31-generic:

  TV1 unknown connection (normal left inverted right x axis y axis)
 848x480   50.00 +
 640x480   50.00 +
 1024x768  50.00  
 800x600   50.00

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1573 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jul 31 17:15:16 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (94 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 89224MG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/06
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 63ET13WW
  dmi.board.name: CAPELL VALLEY(NAPA) CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 89224MG
  dmi.product.version: 3000 C200
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1636539] Re: linux-ti-omap4: 3.2.0-1493.120 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => 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-1493.120 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: 1636537
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Thursday, 27. October 2016 20:04 UTC

** Description changed:

  This bug is for tracking the 3.2.0-1493.120 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: 1636537
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Thursday, 27. October 2016 20:04 UTC
+ 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-ti-omap4 in Ubuntu.
https://bugs.launchpad.net/bugs/1636539

Title:
  linux-ti-omap4: 3.2.0-1493.120 -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 3.2.0-1493.120 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: 1636537
  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/1636539/+subscriptions

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

[Kernel-packages] [Bug 1636537] Re: linux: 3.2.0-115.157 -proposed tracker

** 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: In Progress => 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-115.157 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:Promoted to proposed
+ kernel-stable-phase-changed:Thursday, 27. October 2016 20:04 UTC

** Description changed:

  This bug is for tracking the 3.2.0-115.157 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:Promoted to proposed
- kernel-stable-phase-changed:Thursday, 27. October 2016 20:04 UTC
+ 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/1636537

Title:
  linux: 3.2.0-115.157 -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-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:
  Confirmed

Bug description:
  This bug is for tracking the 3.2.0-115.157 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/1636537/+subscriptions

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

[Kernel-packages] [Bug 1637303] Re: Move some device drivers build from kernel built-in to modules

2016-10-27 Thread Leann Ogasawara

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  Move some device drivers build from kernel built-in to modules

Status in linux package in Ubuntu:
  New

Bug description:
  Some drivers in Ubuntu are built as kernel built-in components, not
  allowing some module interesting features like blacklist on boot
  command-line or module removal/replacement. Also, modules has debug
  advantages compared to built-in kernel components, like the
  possibility to easy build custom-debug modules against kernel tree and
  replace them using modprobe on running system.

  This feature is a request to Canonical move some currently built-in
  drivers to module build system on Power platform, by changing the
  kernel config file.

  The drivers in question are: tg3, virtio-blk and virtio-net.
  The kernel config file parameters related to those 3 drivers are:

  CONFIG_TIGON3, CONFIG_VIRTIO_BLK and CONFIG_VIRTIO_NET.
  They all are currently set as "=y"; we're requesting a change to "=m".

  Thanks in advance,


  Guilherme

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

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

[Kernel-packages] [Bug 1637303] [NEW] Move some device drivers build from kernel built-in to modules

2016-10-27 Thread bugproxy

Public bug reported:

Some drivers in Ubuntu are built as kernel built-in components, not
allowing some module interesting features like blacklist on boot
command-line or module removal/replacement. Also, modules has debug
advantages compared to built-in kernel components, like the possibility
to easy build custom-debug modules against kernel tree and replace them
using modprobe on running system.

This feature is a request to Canonical move some currently built-in
drivers to module build system on Power platform, by changing the kernel
config file.

The drivers in question are: tg3, virtio-blk and virtio-net.
The kernel config file parameters related to those 3 drivers are:

CONFIG_TIGON3, CONFIG_VIRTIO_BLK and CONFIG_VIRTIO_NET.
They all are currently set as "=y"; we're requesting a change to "=m".

Thanks in advance,


Guilherme

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-147981 severity-high 
targetmilestone-inin1704

** Tags added: architecture-ppc64le bugnameltc-147981 severity-high
targetmilestone-inin1704

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

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

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

Title:
  Move some device drivers build from kernel built-in to modules

Status in linux package in Ubuntu:
  New

Bug description:
  Some drivers in Ubuntu are built as kernel built-in components, not
  allowing some module interesting features like blacklist on boot
  command-line or module removal/replacement. Also, modules has debug
  advantages compared to built-in kernel components, like the
  possibility to easy build custom-debug modules against kernel tree and
  replace them using modprobe on running system.

  This feature is a request to Canonical move some currently built-in
  drivers to module build system on Power platform, by changing the
  kernel config file.

  The drivers in question are: tg3, virtio-blk and virtio-net.
  The kernel config file parameters related to those 3 drivers are:

  CONFIG_TIGON3, CONFIG_VIRTIO_BLK and CONFIG_VIRTIO_NET.
  They all are currently set as "=y"; we're requesting a change to "=m".

  Thanks in advance,


  Guilherme

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

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

[Kernel-packages] [Bug 1637303] [NEW] Move some device drivers build from kernel built-in to modules

You have been subscribed to a public bug:

Some drivers in Ubuntu are built as kernel built-in components, not
allowing some module interesting features like blacklist on boot
command-line or module removal/replacement. Also, modules has debug
advantages compared to built-in kernel components, like the possibility
to easy build custom-debug modules against kernel tree and replace them
using modprobe on running system.

This feature is a request to Canonical move some currently built-in
drivers to module build system on Power platform, by changing the kernel
config file.

The drivers in question are: tg3, virtio-blk and virtio-net.
The kernel config file parameters related to those 3 drivers are:

CONFIG_TIGON3, CONFIG_VIRTIO_BLK and CONFIG_VIRTIO_NET.
They all are currently set as "=y"; we're requesting a change to "=m".

Thanks in advance,


Guilherme

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


** Tags: architecture-ppc64le bugnameltc-147981 severity-high 
targetmilestone-inin1704
-- 
Move some device drivers build from kernel built-in to modules
https://bugs.launchpad.net/bugs/1637303
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 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

2016-10-27 Thread Rob Knop

I am having this problem too.  I'm not sure the root of the problem.
It's intermittent.  Sometimes machines boot, sometimes they do not.
Sometimes they boot, but then fail to mount an nfs filesystem.  (In
those cases, top shows mount.nfs using 100% of the CPU.  I can't kill
the process, and I can't reboot... the "reboot" command tells me that it
times out.  Hurray, systemd... sigh.)

The machine in question has nvidia-352 and Linux 4.4.0-45 installed.

I couldn't figure out if the problem was kernel, NFS, systemd, or
nvidia.  Finding this bug suggests to me that the problem is kernel.
However, the errors I'm getting suggest that it's "mount.nfs" that is
the process that's stuck.

This only started happening a few days ago when I did an apt-get
upgrade.  I probably hadn't upgraded for a few weeks before that.

Any hope of this bug getting fixed any time soon?  It sounds like
there's a fix out there upstream; is there, really?

-- 
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
  De

[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel

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

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

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

** Also affects: zfs-linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Zesty)
   Importance: Medium
 Assignee: Colin Ian King (colin-king)
   Status: Triaged

** Also affects: zfs-linux (Ubuntu Zesty)
   Importance: Medium
 Assignee: Colin Ian King (colin-king)
   Status: New

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

Title:
  zfs: importing zpool with vdev on zvol hangs kernel

Status in linux package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in zfs-linux source package in Xenial:
  New
Status in linux source package in Yakkety:
  New
Status in zfs-linux source package in Yakkety:
  New
Status in linux source package in Zesty:
  Triaged
Status in zfs-linux source package in Zesty:
  New

Bug description:
  [SRU Request][Xenial][Yakkety]

  if a zvol of an existing, already imported zpool is a vdev of another
  zpool, a call to "zpool import" will everything zfs related. the stack
  trace is as follows:

  [] taskq_wait+0x74/0xe0 [spl]
  [] taskq_destroy+0x4b/0x100 [spl]
  [] vdev_open_children+0x12d/0x180 [zfs]
  [] vdev_root_open+0x3c/0xc0 [zfs]
  [] vdev_open+0xf5/0x4d0 [zfs]
  [] spa_load+0x39e/0x1c60 [zfs]
  [] spa_tryimport+0xad/0x450 [zfs]
  [] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
  [] zfsdev_ioctl+0x44b/0x4e0 [zfs]
  [] do_vfs_ioctl+0x29f/0x490
  [] SyS_ioctl+0x79/0x90
  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [] 0x

  [Fix]
  zfsutils-linux:

  Zesty: https://launchpadlibrarian.net/290907232/zfs-
  linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz

  Yakkety, likewise
  Xenial, likewise

  Sync'd fixes into kernel repos, patches in:
  http://kernel.ubuntu.com/~cking/zfs-lp-1636517

  [Regression Potential]

  Minimal. This just touched one line in the zfs module
  module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h

  Tested and passes with the ubuntu kernel team autotest client zfs
  regression tests.

  =

  I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged
  in 4.4.0-6.21), which added a second parameter to lookup_bdev without
  patching the zfs module (which needs to special case the vdev-on-zvol
  case, and uses this exact method only in this special casing code
  path).

  attached you can find the output of "zfs send -R" ing such a zvol
  ("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
  by "zpool import" should reproduce the hang.

  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
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 25 15:46 seq
   crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Oct 25 15:49:51 2016
  HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
  InstallationDate: Installed on 2016-10-25 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/hostname--vg-root ro
  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: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.7
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.pr

[Kernel-packages] [Bug 1612006] Re: I2C touchpad does not work on AMD platform

2016-10-27 Thread Alex Hung

AMD sent two more patches to fix this issue completely:

commit e084448b5d26bfebe8a7b9c43bb57e685567563d
Author: Agrawal, Nitesh-kumar 
Date:   Fri Sep 9 15:18:09 2016 +

pinctrl/amd: switch to using a bool for level

The earlier patch can be simplified by using a bool
to indicate level trigger.

Reviewed-by: Pankaj Sen 
Signed-off-by: Nitesh Kumar Agrawal 
[Fixup to earlier manually applied patch]
Signed-off-by: Linus Walleij 

commit 499c7196dd182ba513ccb9620ee22aed3f9096fd
Author: Agrawal, Nitesh-kumar 
Date:   Wed Aug 31 08:50:49 2016 +

pinctrl/amd: Configure GPIO register using BIOS settings

In the function amd_gpio_irq_set_type, use the settings provided by
the BIOS,when the LevelTrig is Edge and activeLevel is HIGH, to configure
the GPIO registers. Ignore the settings from client.

Reviewed-by: Pankaj Sen 
Signed-off-by:Nitesh Kumar Agrawal 
Signed-off-by: Linus Walleij 

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

Title:
  I2C touchpad does not work on AMD platform

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Recent AMD platform has problems with I2C touchpads because its GPIO
  controller is not configured correctly.

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

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

[Kernel-packages] [Bug 1636330] Re: guest experiencing Transmit Timeouts on CX4

https://lists.ubuntu.com/archives/kernel-team/2016-October/080630.html
https://lists.ubuntu.com/archives/kernel-team/2016-October/080629.html

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: New

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

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

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

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)

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

Title:
  guest experiencing Transmit Timeouts on CX4

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This patch fixes a race condition that was reintroduced in the 4.8
  kernel, as part of the P9 changes, after having been originally fixed
  in 3.19. The effect of the race condition is that a secondary thread
  can start trying to execute code from the guest while the thread is
  still in hypervisor mode, so it can cause many different symptoms, one
  of which seems to be the timebase corruption that leads to the lockup
  in ktime_get_ts64. It could cause other problems such as CPU cores
  locking up hard or memory corruption.

  This patch is only needed on the host. It should be applied to any 4.8
  kernel being used as a host, including the Ubuntu 16.10 kernel.

  Hi Paul
  I built a kernel with your patch and put at the host and in the guest. I can 
still see some ktime_get_ts64 at the host. The guest dmesg is clean.

  This patch fixes another race condition I found in the fastsleep code.
  Please apply this patch as well and test.

  Sure will do and provide feedback.

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

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

[Kernel-packages] [Bug 1612006] Re: I2C touchpad does not work on AMD platform

2016-10-27 Thread Alex Hung

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

Title:
  I2C touchpad does not work on AMD platform

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Recent AMD platform has problems with I2C touchpads because its GPIO
  controller is not configured correctly.

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

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

[Kernel-packages] [Bug 1636625] Re: Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile

https://lists.ubuntu.com/archives/kernel-team/2016-October/080628.html

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

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

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

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

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

Title:
  Syntax error extra parenthesis linux-headers-3.13.0-100/Makefile

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  In Progress

Bug description:
  Recommended change: remove incorrect extra ) character

  root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile
  615c615
  < -fstack-protector not supported by compiler)
  ---
  > -fstack-protector not supported by compiler))

  This bug causes driver builds to fail like this

  make[1]: Entering directory `/usr/src/linux-headers-3.13.0-100-generic'
  /usr/src/linux-headers-3.13.0-100-generic/arch/x86/Makefile:111: 
CONFIG_X86_X32 enabled but no binutils support
  Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR: -fstack-protector not 
supported by compiler
  Makefile:614: *** missing separator. Stop.
  make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-100-generic'
  make: *** [all] Error 2
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=93497dab-63bb-4998-9e07-583b6fbd6493
  InstallationDate: Installed on 2014-09-03 (784 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  IwConfig:
   bond0 no wireless extensions.
   
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: HP ProLiant ML110 G5
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic 
root=UUID=2083fcba-62cb-427d-abb2-cacc50e14374 ro text nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-100-generic N/A
   linux-backports-modules-3.13.0-100-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-100-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: HP
  dmi.bios.version: O15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: ProLiant ML110 G5
  dmi.board.vendor: Wistron Corporation
  dmi.board.version: NA
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHP:bvrO15:bd10/25/2010:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnProLiantML110G5:rvrNA:cvnHP:ct7:cvrN/A:
  dmi.product.name: ProLiant ML110 G5
  dmi.product.version: NA
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1636733] Re: [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default

2016-10-27 Thread bugproxy

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1610

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

Title:
  [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default

Status in linux package in Ubuntu:
  Fix Released
Status in kernel-package source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in kernel-package source package in Yakkety:
  New
Status in linux source package in Yakkety:
  In Progress
Status in kernel-package source package in Zesty:
  Invalid
Status in linux source package in Zesty:
  Fix Released

Bug description:
  == Comment: #0 - SRIKANTH B. AITHAL  - 2016-10-26 
01:40:39 ==
  ---Problem Description---
  vfio_pci is not loaded by default on Ubuntu 16.10 host boot. All VFIO related 
tasks would fail without that module. For instance I was trying to boot guest 
with QEMU directly and it was failing complaining 
"/sys/bus/pci/drivers/vfio-pci/new_id" not present.

  root@c158f2u09os:~# lsmod | grep -i vfio
  root@c158f2u09os:~# modprobe vfio_pci <-- need to load explicitly
  root@c158f2u09os:~# lsmod | grep -i vfio
  vfio_pci   51735  0
  irqbypass   5567  1 vfio_pci
  vfio_iommu_spapr_tce14567  0
  vfio_virqfd 4859  1 vfio_pci
  vfio   31351  2 vfio_iommu_spapr_tce,vfio_pci
  vfio_spapr_eeh  3441  2 vfio_iommu_spapr_tce,vfio_pci

  Either 
  > we need to have these modules loaded by kernel by default 
  or 
  > we need to update https://wiki.ubuntu.com/ppc64el/CommonQuestions telling 
customers to load vfio_pci module explicitly before attempting any vfio tasks.
   
  Contact Information = Srikanth/bssrika...@in.ibm.com 
   
  ---uname output---
  Linux c158f2u09os 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:41:40 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. After booting into Ubuntu 16.10, see if vfio_pci modules are loaded:
  root@c158f2u09os:~# lsmod | grep -i vfio
  2. After that we need to manually load vfio_pci
  root@c158f2u09os:~# modprobe vfio_pci
  root@c158f2u09os:~#

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

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

[Kernel-packages] [Bug 1636541] Re: linux-armadaxp: 3.2.0-1677.104 -proposed tracker

2016-10-27 Thread Andy Whitcroft

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

Title:
  linux-armadaxp: 3.2.0-1677.104 -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:
  In Progress
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-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-1677.104 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: 1636537
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1636539] Re: linux-ti-omap4: 3.2.0-1493.120 -proposed tracker

2016-10-27 Thread Andy Whitcroft

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

Title:
  linux-ti-omap4: 3.2.0-1493.120 -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:
  In Progress
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:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 3.2.0-1493.120 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: 1636537
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1636537] Re: linux: 3.2.0-115.157 -proposed tracker

2016-10-27 Thread Andy Whitcroft

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

Title:
  linux: 3.2.0-115.157 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
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 Precise:
  Confirmed

Bug description:
  This bug is for tracking the 3.2.0-115.157 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/1636537/+subscriptions

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

[Kernel-packages] [Bug 1636733] Re: [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default

https://lists.ubuntu.com/archives/kernel-team/2016-October/080626.html

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

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

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

** Changed in: kernel-package (Ubuntu Zesty)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)

** No longer affects: kernel-package (Ubuntu)

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

Title:
  [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default

Status in linux package in Ubuntu:
  Fix Released
Status in kernel-package source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in kernel-package source package in Yakkety:
  New
Status in linux source package in Yakkety:
  In Progress
Status in kernel-package source package in Zesty:
  Invalid
Status in linux source package in Zesty:
  Fix Released

Bug description:
  == Comment: #0 - SRIKANTH B. AITHAL  - 2016-10-26 
01:40:39 ==
  ---Problem Description---
  vfio_pci is not loaded by default on Ubuntu 16.10 host boot. All VFIO related 
tasks would fail without that module. For instance I was trying to boot guest 
with QEMU directly and it was failing complaining 
"/sys/bus/pci/drivers/vfio-pci/new_id" not present.

  root@c158f2u09os:~# lsmod | grep -i vfio
  root@c158f2u09os:~# modprobe vfio_pci <-- need to load explicitly
  root@c158f2u09os:~# lsmod | grep -i vfio
  vfio_pci   51735  0
  irqbypass   5567  1 vfio_pci
  vfio_iommu_spapr_tce14567  0
  vfio_virqfd 4859  1 vfio_pci
  vfio   31351  2 vfio_iommu_spapr_tce,vfio_pci
  vfio_spapr_eeh  3441  2 vfio_iommu_spapr_tce,vfio_pci

  Either 
  > we need to have these modules loaded by kernel by default 
  or 
  > we need to update https://wiki.ubuntu.com/ppc64el/CommonQuestions telling 
customers to load vfio_pci module explicitly before attempting any vfio tasks.
   
  Contact Information = Srikanth/bssrika...@in.ibm.com 
   
  ---uname output---
  Linux c158f2u09os 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:41:40 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. After booting into Ubuntu 16.10, see if vfio_pci modules are loaded:
  root@c158f2u09os:~# lsmod | grep -i vfio
  2. After that we need to manually load vfio_pci
  root@c158f2u09os:~# modprobe vfio_pci
  root@c158f2u09os:~#

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

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

[Kernel-packages] [Bug 1636733] Re: [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default

https://lists.ubuntu.com/archives/kernel-team/2016-October/080625.html

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

** Changed in: kernel-package (Ubuntu)
   Status: New => Invalid

** Also affects: kernel-package (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: kernel-package (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Invalid

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

** Also affects: kernel-package (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default

Status in linux package in Ubuntu:
  Fix Released
Status in kernel-package source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in kernel-package source package in Yakkety:
  New
Status in linux source package in Yakkety:
  In Progress
Status in kernel-package source package in Zesty:
  Invalid
Status in linux source package in Zesty:
  Fix Released

Bug description:
  == Comment: #0 - SRIKANTH B. AITHAL  - 2016-10-26 
01:40:39 ==
  ---Problem Description---
  vfio_pci is not loaded by default on Ubuntu 16.10 host boot. All VFIO related 
tasks would fail without that module. For instance I was trying to boot guest 
with QEMU directly and it was failing complaining 
"/sys/bus/pci/drivers/vfio-pci/new_id" not present.

  root@c158f2u09os:~# lsmod | grep -i vfio
  root@c158f2u09os:~# modprobe vfio_pci <-- need to load explicitly
  root@c158f2u09os:~# lsmod | grep -i vfio
  vfio_pci   51735  0
  irqbypass   5567  1 vfio_pci
  vfio_iommu_spapr_tce14567  0
  vfio_virqfd 4859  1 vfio_pci
  vfio   31351  2 vfio_iommu_spapr_tce,vfio_pci
  vfio_spapr_eeh  3441  2 vfio_iommu_spapr_tce,vfio_pci

  Either 
  > we need to have these modules loaded by kernel by default 
  or 
  > we need to update https://wiki.ubuntu.com/ppc64el/CommonQuestions telling 
customers to load vfio_pci module explicitly before attempting any vfio tasks.
   
  Contact Information = Srikanth/bssrika...@in.ibm.com 
   
  ---uname output---
  Linux c158f2u09os 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:41:40 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. After booting into Ubuntu 16.10, see if vfio_pci modules are loaded:
  root@c158f2u09os:~# lsmod | grep -i vfio
  2. After that we need to manually load vfio_pci
  root@c158f2u09os:~# modprobe vfio_pci
  root@c158f2u09os:~#

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

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

[Kernel-packages] [Bug 1635721] Re: Add a driver for Amazon Elastic Network Adapters (ENA)

2016-10-27 Thread Kamal Mostafa

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

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

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

Title:
  Add a driver for Amazon Elastic Network Adapters (ENA)

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Back-porting this driver to Ubuntu LTS generic kernels would be
  beneficial.

  commit 1738cd3ed342294360d6a74d4e5884bff854 linux-next
  "net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)"

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

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

[Kernel-packages] [Bug 1636941] Re: linux: 4.4.0-47.68 -proposed tracker

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Incomplete => 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/1636941

Title:
  linux: 4.4.0-47.68 -proposed tracker

Status in Kernel SRU Workflow:
  Incomplete
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:
  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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-47.68 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/1636941/+subscriptions

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

[Kernel-packages] [Bug 1626564] Re: 4.8 regression: SLAB is being used instead of SLUB

2016-10-27 Thread Doug Smythies

> Are you sure SLAB vs. SLUB fixed this?

No, it does not fix the issue. However, the issue is more difficult to
re-produce. It seems easy enough to reproduce on my test server, but
seems to not happen on my test LapTop.

There are 3 related upstream commits that fix the issue (at least in my
testing) for both SLAB and SLUB, and I think (but am not sure) they have
been flagged to eventually be backported to stable. I do not think any
of the patches have made it into the current release candidate kernel
(currently 4.9-rc2) yet.

References:
https://patchwork.kernel.org/patch/9359269/
https://patchwork.kernel.org/patch/9359271/
https://patchwork.kernel.org/patch/9363679/

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

Title:
  4.8 regression: SLAB is being used instead of SLUB

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  We're seeing hundreds of kernel worker threads being spawned with some
  actions, for example, after booting the desktop and hutting the
  brightness keys causes this.  On investigation, this occurs when
  CONFIG_SLAB is being used.

  1. Ubuntu traditionally uses CONFIG_SLUB, so we should use that instead of 
CONFIG_SLAB (why was it changed for Yakkety?)
  2. With CONFIG_SLUB I cannot reproduce the issue of the hundreds for worker 
threads
  3 CONFIG_SLUB seems more performant on the boot too over SLAB.

  Please re-enable the CONFIG_SLUB allocator as per the 4.4. Xenial
  configs.

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

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

[Kernel-packages] [Bug 1591618] Re: [Feature] KBL - New device ID for Kabypoint(KbP)

2016-10-27 Thread Robert Hooker

** Changed in: intel
 Assignee: Robert Hooker (sarvatt) => (unassigned)

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

Title:
  [Feature] KBL - New device ID for Kabypoint(KbP)

Status in intel:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released

Bug description:
  identify what new device IDs are required for Kabypoint (KBP): HS-
  UART,SPI, I2C, SMBUS,SPI-NOR,NPK,xHCI,usb device, SD

  Platform: Kabylake-S with Kabypoint PCH

  upstream schedule: 4.9

  X-HWE-Bug: Bug #1622469

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

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

[Kernel-packages] [Bug 1588479] Update Released

2016-10-27 Thread Brian Murray

The verification of the Stable Release Update for dkms has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  dkms_packages.py supported kernel check is not working

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released
Status in dkms source package in Yakkety:
  Fix Released

Bug description:
  Test Case
  -
  1) Look for some dkms package in /usr/src e.g. bbswitch-0.8
  2) Run python3 /usr/share/apport/package-hooks/dkms_packages.py -m bbswitch 
-v 0.8 -k 4.6.1-01234-lowlatency
  3) Observe a crash report dialog from apport for bbswitch

  With the version of apport from -proposed you will instead receive:

  ERROR (dkms apport): kernel package linux-
  headers-4.6.1-01234-lowlatency is not supported

  
  The apport package hook for dkms packages seems to have an error in its 
supported kernel check.  If the kernel is an unsupported one, the hook should 
exit with a return code of 1.  However, in the Ubuntu Error Tracker we can see 
some crashes with unsupported kernel versions e.g.:

  https://errors.ubuntu.com/oops/2733d742-284e-11e6-a745-fa163e839e11
  DKMSKernelVersion: 4.6.1-040601-lowlatency

  https://errors.ubuntu.com/oops/0a1afefc-253c-11e6-9082-fa163e192766
  DKMSKernelVersion: 4.6.0-040600-lowlatency

  If the intent really is to block creation of these reports, then let's
  do that.

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

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

[Kernel-packages] [Bug 1588479] Re: dkms_packages.py supported kernel check is not working

This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.3

---
dkms (2.2.0.3-2ubuntu11.3) xenial; urgency=medium

  * apport_name_in_valueerror.diff: (LP: #1588479)
- Check the ValueError from apport for the package name too, this prevents
  reporting of dkms crashes about unsupported kernels.

 -- Brian Murray   Thu, 15 Sep 2016 14:22:14 -0700

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

Title:
  dkms_packages.py supported kernel check is not working

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released
Status in dkms source package in Yakkety:
  Fix Released

Bug description:
  Test Case
  -
  1) Look for some dkms package in /usr/src e.g. bbswitch-0.8
  2) Run python3 /usr/share/apport/package-hooks/dkms_packages.py -m bbswitch 
-v 0.8 -k 4.6.1-01234-lowlatency
  3) Observe a crash report dialog from apport for bbswitch

  With the version of apport from -proposed you will instead receive:

  ERROR (dkms apport): kernel package linux-
  headers-4.6.1-01234-lowlatency is not supported

  
  The apport package hook for dkms packages seems to have an error in its 
supported kernel check.  If the kernel is an unsupported one, the hook should 
exit with a return code of 1.  However, in the Ubuntu Error Tracker we can see 
some crashes with unsupported kernel versions e.g.:

  https://errors.ubuntu.com/oops/2733d742-284e-11e6-a745-fa163e839e11
  DKMSKernelVersion: 4.6.1-040601-lowlatency

  https://errors.ubuntu.com/oops/0a1afefc-253c-11e6-9082-fa163e192766
  DKMSKernelVersion: 4.6.0-040600-lowlatency

  If the intent really is to block creation of these reports, then let's
  do that.

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

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

[Kernel-packages] [Bug 1588479] Re: dkms_packages.py supported kernel check is not working

This bug was fixed in the package dkms - 2.2.0.3-1.1ubuntu5.14.04.9

---
dkms (2.2.0.3-1.1ubuntu5.14.04.9) trusty; urgency=medium

  * apport_name_in_valueerror.diff: (LP: #1588479)
- Check the ValueError from apport for the package name too, this prevents
  reporting of dkms crashes about unsupported kernels.

 -- Brian Murray   Thu, 15 Sep 2016 14:25:09 -0700

** Changed in: dkms (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

** Changed in: dkms (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  dkms_packages.py supported kernel check is not working

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released
Status in dkms source package in Yakkety:
  Fix Released

Bug description:
  Test Case
  -
  1) Look for some dkms package in /usr/src e.g. bbswitch-0.8
  2) Run python3 /usr/share/apport/package-hooks/dkms_packages.py -m bbswitch 
-v 0.8 -k 4.6.1-01234-lowlatency
  3) Observe a crash report dialog from apport for bbswitch

  With the version of apport from -proposed you will instead receive:

  ERROR (dkms apport): kernel package linux-
  headers-4.6.1-01234-lowlatency is not supported

  
  The apport package hook for dkms packages seems to have an error in its 
supported kernel check.  If the kernel is an unsupported one, the hook should 
exit with a return code of 1.  However, in the Ubuntu Error Tracker we can see 
some crashes with unsupported kernel versions e.g.:

  https://errors.ubuntu.com/oops/2733d742-284e-11e6-a745-fa163e839e11
  DKMSKernelVersion: 4.6.1-040601-lowlatency

  https://errors.ubuntu.com/oops/0a1afefc-253c-11e6-9082-fa163e192766
  DKMSKernelVersion: 4.6.0-040600-lowlatency

  If the intent really is to block creation of these reports, then let's
  do that.

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

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

[Kernel-packages] [Bug 1630069] Update Released

2016-10-27 Thread Brian Murray

The verification of the Stable Release Update for apparmor has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Regression tests can not detect binfmt_elf mmpa semantic change

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  New
Status in apparmor source package in Yakkety:
  Won't Fix
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == apparmor SRU ==

  [Impact]

   * The exec_stack.sh regression test fails due to a behavior change in 4.8
     kernels from this patch:

     commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46
     Author: Linus Torvalds 
     Date: Mon Aug 22 16:41:46 2016 -0700

     binfmt_elf: switch to new creds when switching to new mm

   * The regression tests were fixed for this kernel change but they were fixed
     in a way that always assumed that kernel change is present. They should 
have
     been adjusted so that they act differently according to whether or not the
     kernel change is present (it is a change that could end up being backported
     through the stable trees).

  [Test Case]

   $ apt-get source apparmor # make sure this fetches the new apparmor source
   $ sudo apt-get install libapparmor-dev
   $ cd tests/regression/apparmor
   $ make USE_SYSTEM=1
   $ sudo bash exec_stack.sh

   The previous command should result in no output and return value of
  0.

  [Regression Potential]

   * This is an extremely low risk change since it only touches regression
     testing code that is not user-facing.

  [Other]

   * Fixed in upstream lp:apparmor tree:

     https://bazaar.launchpad.net/~apparmor-
  dev/apparmor/master/revision/3558

  == Original description ==

  The regression tests are currently hard coded to the semantics of mmap
  in binfmt_elf

  With the recent upstream commit
  9f834ec18defc369d73ccf9e87a2790bfa05bf46 the cred used for the mmap
  changed resulting in test failures. The tests have been patched for
  this change but it results in the test breaking for everyone using
  upstream releases against pre 4.8 kernels.

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

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

[Kernel-packages] [Bug 1630069] Re: Regression tests can not detect binfmt_elf mmpa semantic change

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.5

---
apparmor (2.10.95-0ubuntu2.5) xenial; urgency=medium

  * debian/lib/apparmor/functions, debian/apparmor.init,
debian/apparmor.service, debian/apparmor.upstart,
debian/lib/apparmor/profile-load: Adjust the checks that previously kept
AppArmor policy from being loaded while booting a container. Now we
attempt to load policy if we're in a LXD or LXC managed container that is
using profile stacking inside of a policy namespace. (LP: #1628285)
  * Fix regression tests for stacking so that the kernel SRU process is not
interrupted by failing tests whenever the AppArmor stacking features are
backported from the 16.10 kernel or when the 16.04 LTS Enablement Stack
receives a 4.8 or newer kernel
- debian/patches/r3509-tests-fix-exec_stack-errors-1.patch: Fix the
  exec_stack.sh test when running on 4.8 or newer kernels (LP: #1628745)
- debian/patches/r3558-tests-fix-exec_stack-errors-2.patch: Adjust the
  exec_stack.sh fix mentioned above to more accurately test kernels older
  than 4.8 (LP: #1630069)
- debian/patches/allow-stacking-tests-to-use-system.patch: Apply this
  patch earlier in the series, as to match when it was committed upstream,
  so that the above two patches can be cherry-picked from lp:apparmor

 -- Tyler Hicks   Fri, 07 Oct 2016 05:21:44 +

** Changed in: apparmor (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Regression tests can not detect binfmt_elf mmpa semantic change

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  New
Status in apparmor source package in Yakkety:
  Won't Fix
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == apparmor SRU ==

  [Impact]

   * The exec_stack.sh regression test fails due to a behavior change in 4.8
     kernels from this patch:

     commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46
     Author: Linus Torvalds 
     Date: Mon Aug 22 16:41:46 2016 -0700

     binfmt_elf: switch to new creds when switching to new mm

   * The regression tests were fixed for this kernel change but they were fixed
     in a way that always assumed that kernel change is present. They should 
have
     been adjusted so that they act differently according to whether or not the
     kernel change is present (it is a change that could end up being backported
     through the stable trees).

  [Test Case]

   $ apt-get source apparmor # make sure this fetches the new apparmor source
   $ sudo apt-get install libapparmor-dev
   $ cd tests/regression/apparmor
   $ make USE_SYSTEM=1
   $ sudo bash exec_stack.sh

   The previous command should result in no output and return value of
  0.

  [Regression Potential]

   * This is an extremely low risk change since it only touches regression
     testing code that is not user-facing.

  [Other]

   * Fixed in upstream lp:apparmor tree:

     https://bazaar.launchpad.net/~apparmor-
  dev/apparmor/master/revision/3558

  == Original description ==

  The regression tests are currently hard coded to the semantics of mmap
  in binfmt_elf

  With the recent upstream commit
  9f834ec18defc369d73ccf9e87a2790bfa05bf46 the cred used for the mmap
  changed resulting in test failures. The tests have been patched for
  this change but it results in the test breaking for everyone using
  upstream releases against pre 4.8 kernels.

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

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

[Kernel-packages] [Bug 1616949] Re: guest on bridge becomes inaccessible

2016-10-27 Thread Curtis Hovey

** Tags added: jujuqa

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

Title:
  guest on bridge becomes inaccessible

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have a "virtual maas" setup where we have a maas node on a linux
  bridge (created by libvirt) and some other number of nodes on that
  same bridge.

  the maas node then controls the other nodes turning them on and off
  and generally working maas-like magic.

  In this scenario on 16.04 with when deploying 3 or so nodes at a time,
  the maas node becomes inaccessible, and as it is the root device for
  iscsi storage of the installs, the nodes fail also.

  This occurred with xenial kernel (4.4).
  Reverting the kernel to 3.19 (linux-lts-vivid) kernel fixes the problem.
  https://launchpad.net/ubuntu/+source/linux-lts-vivid
  Specifically, the fixed kernel is
  $ dpkg-query --show | grep linux-.*3.19
  linux-image-3.19.0-66-generic   3.19.0-66.74~14.04.1
  linux-image-extra-3.19.0-66-generic 3.19.0-66.74~14.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-66-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 25 12:10 seq
   crw-rw 1 root audio 116, 33 Aug 25 12:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Aug 25 14:37:07 2016
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
  ProcLoadAvg: 0.40 0.28 0.46 1/1337 140794
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 3.19.0-66-generic (buildd@bos01-ppc64el-021) (gcc 
version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #74~14.04.1-Ubuntu SMP Tue Jul 
19 19:54:47 UTC 2016
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-66-generic N/A
   linux-backports-modules-3.19.0-66-generic  N/A
   linux-firmware 1.157.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.667 GHz (cpu 120)
   max: 3.691 GHz (cpu 0)
   avg: 3.689 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT is off

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

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

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

2016-10-27 Thread Joseph Salisbury

I built the another test kernel, up to the same commit:
4a5219edcdae52bfb5eea0dfc2a7bd575961dad7

This kernel also has the two patches.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1626436/4a5219edcdae52bfb5eea0dfc2a7bd575961dad7

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1630554] Re: QEMU throws failure msg while booting guest with SRIOV VF

https://lists.ubuntu.com/archives/kernel-team/2016-October/080620.html

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

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

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

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

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

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

Title:
  QEMU throws failure msg while booting guest with SRIOV VF

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released

Bug description:
  == Comment: #10 - VIPIN K. PARASHAR  - 2016-10-04 
02:39:30 ==
  (In reply to comment #9)
  > I took a quick look to this one and also noticed these 2 links:
  > https://bugzilla.redhat.com/show_bug.cgi?id=1237034
  > http://marc.info/?l=linux-kernel&m=143737274332400&w=2
  > and it looks like to avoid these message maybe just need to have this in
  > config file:
  > CONFIG_KVM_VFIO=y
  > I think we have that in powerkvm but not in Ubuntu KVM.

  On x86 running Ubuntu 16.04
  ==
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial
  $ head /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 61
  model name: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
  stepping  : 4
  microcode : 0x22
  cpu MHz   : 2300.179
  cache size: 3072 KB
  physical id   : 0
  $ uname -a
  Linux Workstation 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  $ grep CONFIG_KVM_VFIO /boot/config-4.4.0-38-generic 
  CONFIG_KVM_VFIO=y
  $

  On PowerPC
   
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety
  # head /proc/cpuinfo
  processor : 0
  cpu   : POWER8E (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.1 (pvr 004b 0201)

  processor : 1
  cpu   : POWER8E (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.1 (pvr 004b 0201)

  # uname -a
  Linux c158f2u09os 4.8.0-17-generic #19 SMP Thu Sep 29 12:03:21 CDT 2016 
ppc64le ppc64le ppc64le GNU/Linux
  # grep CONFIG_KVM_VFIO /boot/config-4.8.0-17-generic 
  #

  I see that CONFIG_KVM_VFIO is enabled on x86 running Ubuntu 16.04
  while ppc64 running 16.10 doesn't have it enabled.

  == Comment: #9 - Carol L. Soto  - 2016-09-30 16:25:32 ==
  I took a quick look to this one and also noticed these 2 links:
  https://bugzilla.redhat.com/show_bug.cgi?id=1237034
  http://marc.info/?l=linux-kernel&m=143737274332400&w=2
  and it looks like to avoid these message maybe just need to have this in 
config file:
  CONFIG_KVM_VFIO=y
  I think we have that in powerkvm but not in Ubuntu KVM.

  == Comment: #6 - VIPIN K. PARASHAR  - 2016-09-23 
06:50:22 ==
  $ git log 178a787502123b0 -1
  commit 178a787502123b01499c5a4617b94bb69ad49dd5
  Author: David Gibson 
  Date:   Mon Feb 1 11:14:15 2016 +1100

  vfio: Enable VFIO device for powerpc
  
  ec53500f "kvm: Add VFIO device" added a special KVM pseudo-device which is
  used to handle any necessary interactions between KVM and VFIO.
  
  Currently that device is built on x86 and ARM, but not powerpc, although
  powerpc does support both KVM and VFIO.  This makes things awkward in
  userspace
  
  Currently qemu prints an alarming error message if you attempt to use VFIO
  and it can't initialize the KVM VFIO device.  We don't want to remove the
  warning, because lack of the KVM VFIO device could mean coherency problems
  on x86.  On powerpc, however, the error is harmless but looks disturbing,
  and a test based on host architecture in qemu would be ugly, and break if
  we do need the KVM VFIO device for something important in future.
  
  There's nothing preventing the KVM VFIO device from being built for
  powerpc, so this patch turns it on.  It won't actually do anything, since
  we don't define any of the arch_*() hooks, but it will make qemu happy and
  we can extend it in future if we need to.
  
  Signed-off-by: David Gibson 
  Reviewed-by: Eric Auger 
  Signed-off-by: Paul Mackerras 
  $ 

  $ git describe --contains 178a787502123b
  v4.6-rc1~141^2~49^2~20
  $ 

  
  Commit (178a7875) seems to have enable

[Kernel-packages] [Bug 1630554] Re: QEMU throws failure msg while booting guest with SRIOV VF

https://lists.ubuntu.com/archives/kernel-team/2016-October/080621.html

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

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

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

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

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

Title:
  QEMU throws failure msg while booting guest with SRIOV VF

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released

Bug description:
  == Comment: #10 - VIPIN K. PARASHAR  - 2016-10-04 
02:39:30 ==
  (In reply to comment #9)
  > I took a quick look to this one and also noticed these 2 links:
  > https://bugzilla.redhat.com/show_bug.cgi?id=1237034
  > http://marc.info/?l=linux-kernel&m=143737274332400&w=2
  > and it looks like to avoid these message maybe just need to have this in
  > config file:
  > CONFIG_KVM_VFIO=y
  > I think we have that in powerkvm but not in Ubuntu KVM.

  On x86 running Ubuntu 16.04
  ==
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial
  $ head /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 61
  model name: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
  stepping  : 4
  microcode : 0x22
  cpu MHz   : 2300.179
  cache size: 3072 KB
  physical id   : 0
  $ uname -a
  Linux Workstation 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  $ grep CONFIG_KVM_VFIO /boot/config-4.4.0-38-generic 
  CONFIG_KVM_VFIO=y
  $

  On PowerPC
   
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety
  # head /proc/cpuinfo
  processor : 0
  cpu   : POWER8E (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.1 (pvr 004b 0201)

  processor : 1
  cpu   : POWER8E (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.1 (pvr 004b 0201)

  # uname -a
  Linux c158f2u09os 4.8.0-17-generic #19 SMP Thu Sep 29 12:03:21 CDT 2016 
ppc64le ppc64le ppc64le GNU/Linux
  # grep CONFIG_KVM_VFIO /boot/config-4.8.0-17-generic 
  #

  I see that CONFIG_KVM_VFIO is enabled on x86 running Ubuntu 16.04
  while ppc64 running 16.10 doesn't have it enabled.

  == Comment: #9 - Carol L. Soto  - 2016-09-30 16:25:32 ==
  I took a quick look to this one and also noticed these 2 links:
  https://bugzilla.redhat.com/show_bug.cgi?id=1237034
  http://marc.info/?l=linux-kernel&m=143737274332400&w=2
  and it looks like to avoid these message maybe just need to have this in 
config file:
  CONFIG_KVM_VFIO=y
  I think we have that in powerkvm but not in Ubuntu KVM.

  == Comment: #6 - VIPIN K. PARASHAR  - 2016-09-23 
06:50:22 ==
  $ git log 178a787502123b0 -1
  commit 178a787502123b01499c5a4617b94bb69ad49dd5
  Author: David Gibson 
  Date:   Mon Feb 1 11:14:15 2016 +1100

  vfio: Enable VFIO device for powerpc
  
  ec53500f "kvm: Add VFIO device" added a special KVM pseudo-device which is
  used to handle any necessary interactions between KVM and VFIO.
  
  Currently that device is built on x86 and ARM, but not powerpc, although
  powerpc does support both KVM and VFIO.  This makes things awkward in
  userspace
  
  Currently qemu prints an alarming error message if you attempt to use VFIO
  and it can't initialize the KVM VFIO device.  We don't want to remove the
  warning, because lack of the KVM VFIO device could mean coherency problems
  on x86.  On powerpc, however, the error is harmless but looks disturbing,
  and a test based on host architecture in qemu would be ugly, and break if
  we do need the KVM VFIO device for something important in future.
  
  There's nothing preventing the KVM VFIO device from being built for
  powerpc, so this patch turns it on.  It won't actually do anything, since
  we don't define any of the arch_*() hooks, but it will make qemu happy and
  we can extend it in future if we need to.
  
  Signed-off-by: David Gibson 
  Reviewed-by: Eric Auger 
  Signed-off-by: Paul Mackerras 
  $ 

  $ git describe --contains 178a787502123b
  v4.6-rc1~141^2~49^2~20
  $ 

  
  Commit (178a7875) seems to have enabled VFIO devices for powerpc.
  But this commit should already be available since 4.6 kernel and ubuntu is
  using 4.7 kernel h

[Kernel-packages] [Bug 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

An update on comment #30 - the security update has put
testing/verification behind schdule, so the release date for the
-proposed kernel has been pushed back a week to Nov 7. Apologies for the
inconvenience.

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

Title:
  Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  SRU Justification

  Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds"
  causes a regression in the requester uid and gid passed to userspace
  during automount, as the current credentials during automount are
  those of root and not the user who requested the mount.

  Fix: Use current->real_cred instead of current->cred for getting the
  requester's uid and gid.

  Regression Potential: Minimal. current->cred and current->real_cred
  are the same except when credentials are overridden, thus
  current->real_cred contains the same credentials that autofs had been
  using prior to the change which overrides the credentials during
  automount.

  ---

  Hello,

  I have run into a bug relating autofs's parameter substitution (e.g.
  UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40.
  Kernel version 4.4.0-28 does things correctly but testing intermediate
  kernel versions is hard due to earlier bugs related with fs's.
  Incorrect parameter substitution makes CIFS mounting with variable
  credentials impossible.

  Wat was expected:
  $UID in autofs map are substituted by the uid of the user that starts the 
auto-mounting process.

  What actually happens:
  Root's uid (0) is substituted instead.

  This ill parameter substitution likely caused by recent fixes
  resolving permissions problems for nfs/cifs mounts and dfs referrals
  (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount
  with the filesystems creds' but that is a wild guess.

  Furthermore; playing with the force_standard_program_map_env settings
  in autofs.conf and prefixing variables with 'AUTOFS_' does not solve
  anything.

  Yours kindly,

  Chris

   Additional info 

    lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  run1   3015 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214
  InstallationDate: Installed on 2016-09-19 (10 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp0s8no wireless extensions.

   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 
ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-40-generic N/A
   linux-backports-modules-4.4.0-40-generic  N/A
   linux-firmware1.157.3
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10

2016-10-27 Thread Bjorn Helgaas

>From the Linux kernel point of view, changing the BIOS option is not a
good fix, and "pci=realloc=off" is just a workaround and not a real fix
either.  Linux should be able to work even without that, or at least
give meaningful error messages.

The original problem appears to be that:

  - BIOS allocated space for the normal PCI BARs 0, 2 and 4, but not for the 
SR-IOV VF BARs,
  - Linux tried to allocate space for the SR-IOV BARs, but failed, and
  - Linux removed even the space allocated for the normal PCI BARs

Here's the initial state Linux found:

  pci :22:00.0: [8086:10fb] type 00 class 0x02
  pci :22:00.0: reg 0x10: [mem 0xe940-0xe947 64bit]  # BAR 0
  pci :22:00.0: reg 0x18: [io  0xdcc0-0xdcdf]# BAR 2
  pci :22:00.0: reg 0x20: [mem 0xe95f8000-0xe95fbfff 64bit]  # BAR 4
  pci :22:00.0: reg 0x30: [mem 0xe950-0xe957 pref]   # ROM BAR
  pci :22:00.0: reg 0x184: [mem 0x-0x3fff 64bit] # SR-IOV BAR
  pci :22:00.0: reg 0x190: [mem 0x-0x3fff 64bit] # SR-IOV BAR

After trying to move things around to provide space for the SR-IOV BARs:

  pci :22:00.0: BAR 0: can't assign mem (size 0x8)   # BAR 0
  pci :22:00.0: BAR 4: can't assign mem (size 0x4000)# BAR 4
  pci :22:00.0: BAR 7: can't assign mem (size 0x10)  # SR-IOV BAR
  pci :22:00.0: BAR 10: can't assign mem (size 0x10) # SR-IOV BAR

This may have been fixed by changes in the resource assignment code.  I
don't remember similar recent problem reports.

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

Title:
  Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Quantal:
  Won't Fix
Status in linux source package in Raring:
  Won't Fix
Status in linux source package in Saucy:
  Won't Fix
Status in linux source package in Trusty:
  Confirmed

Bug description:
  We have a server (Dell R715) with two Intel x520 NIC's. If we run
  Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel
  driver or with Intel compiled one), but if we upgrade release to
  12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel
  drivers fails with error:

  [  226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7
  [  226.395770] Copyright (c) 1999-2013 Intel Corporation.
  [  226.395980] ixgbe: probe of :22:00.0 failed with error -5
  [  226.396092] ixgbe: probe of :22:00.1 failed with error -5
  [  226.396203] ixgbe: probe of :23:00.0 failed with error -5
  [  226.396311] ixgbe: probe of :23:00.1 failed with error -5

  I contacted Intel developers and they responded:

  "Hey Fernando,
  We (ixgbe) only returns EIO (error 5) for a couple of reasons.
   1) When we fail to io map (ioremap)
   2) If the eeprom checksum is incorrect.
   3) If the MAC address from the checksum is invalid

  Reasons 2 and 3 are related to the NIC's eeprom so if they worked with 
another system they should still be fine now.  If you really wanted to verify 
you could try out the NIC's on a known good system again to see if the eeprom 
somehow got corrupted.
  That pretty much leaves us with ioremap returning an error.  I'm not at all 
sure why your Ubuntu release would not like the way we are calling ioremap, but 
it might give you a place to start looking in Ubuntu changes.
  Thanks,
  -Don"

  If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's
  works fine.

  Please let me know how can I help!

  Regards

  Fernando

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

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

[Kernel-packages] [Bug 1363313] Re: mpt2sas not loaded with LSISAS2008 card in trusty 14.04.1

2016-10-27 Thread Bjorn Helgaas

** Bug watch added: Linux Kernel Bug Tracker #92351
   http://bugzilla.kernel.org/show_bug.cgi?id=92351

** Also affects: linux via
   http://bugzilla.kernel.org/show_bug.cgi?id=92351
   Importance: Unknown
   Status: Unknown

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

Title:
  mpt2sas not loaded with LSISAS2008 card in trusty 14.04.1

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Won't Fix

Bug description:
  This card has worked without a problem in 12.04 up through the current
  kernel. After an upgrade to 14.04.1, mpt2sas tries to load during boot
  but fails. An apport file from this machine is attached; note the
  error messages during boot.

  WORKAROUND: pci=realloc=off

  ---
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  admsvr 3757 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7192beea-6a28-4c3f-b274-3332e6d007b7
  InstallationDate: Installed on 2010-09-14 (1445 days ago)
  InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 
(20100427)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P55-UD3L
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=46ac1ed7-062a-4ae3-b071-52ccee0cc346 ro splash nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-35-generic N/A
   linux-backports-modules-3.13.0-35-generic  N/A
   linux-firmware 1.127.5
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-35-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-08-23 (6 days ago)
  UserGroups: adm admin cdrom dialout lpadmin lpadmin mythtv plugdev sambashare 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/23/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: P55-UD3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd06/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55-UD3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

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

2016-10-27 Thread bugproxy

--- Comment From lagar...@br.ibm.com 2016-10-27 09:42 EDT---
This patch is currently upstream since 4.9-rc1.

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

Title:
  QEMU throws failure msg while booting guest with SRIOV VF

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #10 - VIPIN K. PARASHAR  - 2016-10-04 
02:39:30 ==
  (In reply to comment #9)
  > I took a quick look to this one and also noticed these 2 links:
  > https://bugzilla.redhat.com/show_bug.cgi?id=1237034
  > http://marc.info/?l=linux-kernel&m=143737274332400&w=2
  > and it looks like to avoid these message maybe just need to have this in
  > config file:
  > CONFIG_KVM_VFIO=y
  > I think we have that in powerkvm but not in Ubuntu KVM.

  On x86 running Ubuntu 16.04
  ==
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial
  $ head /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 61
  model name: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
  stepping  : 4
  microcode : 0x22
  cpu MHz   : 2300.179
  cache size: 3072 KB
  physical id   : 0
  $ uname -a
  Linux Workstation 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  $ grep CONFIG_KVM_VFIO /boot/config-4.4.0-38-generic 
  CONFIG_KVM_VFIO=y
  $

  On PowerPC
   
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety
  # head /proc/cpuinfo
  processor : 0
  cpu   : POWER8E (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.1 (pvr 004b 0201)

  processor : 1
  cpu   : POWER8E (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.1 (pvr 004b 0201)

  # uname -a
  Linux c158f2u09os 4.8.0-17-generic #19 SMP Thu Sep 29 12:03:21 CDT 2016 
ppc64le ppc64le ppc64le GNU/Linux
  # grep CONFIG_KVM_VFIO /boot/config-4.8.0-17-generic 
  #

  I see that CONFIG_KVM_VFIO is enabled on x86 running Ubuntu 16.04
  while ppc64 running 16.10 doesn't have it enabled.

  == Comment: #9 - Carol L. Soto  - 2016-09-30 16:25:32 ==
  I took a quick look to this one and also noticed these 2 links:
  https://bugzilla.redhat.com/show_bug.cgi?id=1237034
  http://marc.info/?l=linux-kernel&m=143737274332400&w=2
  and it looks like to avoid these message maybe just need to have this in 
config file:
  CONFIG_KVM_VFIO=y
  I think we have that in powerkvm but not in Ubuntu KVM.

  == Comment: #6 - VIPIN K. PARASHAR  - 2016-09-23 
06:50:22 ==
  $ git log 178a787502123b0 -1
  commit 178a787502123b01499c5a4617b94bb69ad49dd5
  Author: David Gibson 
  Date:   Mon Feb 1 11:14:15 2016 +1100

  vfio: Enable VFIO device for powerpc
  
  ec53500f "kvm: Add VFIO device" added a special KVM pseudo-device which is
  used to handle any necessary interactions between KVM and VFIO.
  
  Currently that device is built on x86 and ARM, but not powerpc, although
  powerpc does support both KVM and VFIO.  This makes things awkward in
  userspace
  
  Currently qemu prints an alarming error message if you attempt to use VFIO
  and it can't initialize the KVM VFIO device.  We don't want to remove the
  warning, because lack of the KVM VFIO device could mean coherency problems
  on x86.  On powerpc, however, the error is harmless but looks disturbing,
  and a test based on host architecture in qemu would be ugly, and break if
  we do need the KVM VFIO device for something important in future.
  
  There's nothing preventing the KVM VFIO device from being built for
  powerpc, so this patch turns it on.  It won't actually do anything, since
  we don't define any of the arch_*() hooks, but it will make qemu happy and
  we can extend it in future if we need to.
  
  Signed-off-by: David Gibson 
  Reviewed-by: Eric Auger 
  Signed-off-by: Paul Mackerras 
  $ 

  $ git describe --contains 178a787502123b
  v4.6-rc1~141^2~49^2~20
  $ 

  
  Commit (178a7875) seems to have enabled VFIO devices for powerpc.
  But this commit should already be available since 4.6 kernel and ubuntu is
  using 4.7 kernel here, so this should be already in.

  
  == Comment: #0 - SRIKANTH B. AITHAL  - 2016-09-15 
12:31:49 ==
  ---Problem Description---
  QEMU throwing false failure message while booting guest with SRIOV VF device

   
  ---uname output---
  Linux c158f2u09os 4.7.0unofficial #5 SMP Mon Sep 5 08:53:38 EDT 2016 ppc64le 
ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Mellanox CX4 

   
  Machine Type = 8247-22L 
   
  ---Debugger---
  A debugger is not confi

[Kernel-packages] [Bug 1633348] Re: iwlwifi brocken for Intel Corporation Wireless 7260 (rev bb) because of missing iwlwifi-7260-17.ucode

*** This bug is a duplicate of bug 1635091 ***
https://bugs.launchpad.net/bugs/1635091

** This bug has been marked a duplicate of bug 1635091
   New firmware is required for some iwlwifi modules

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

Title:
  iwlwifi brocken for Intel Corporation Wireless 7260 (rev bb) because
  of missing iwlwifi-7260-17.ucode

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  A few days ago, my wireless stopped working. Dmesg showed the
  following:

  [4.499602] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-7260-17.ucode failed with error -2
  [4.507101] iwlwifi :02:00.0: loaded firmware version 16.242414.0 
op_mode iwlmvm
  [4.579437] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 
7260, REV=0x144
  [4.581116] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
  [4.581429] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio.
  [4.581457] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
  [9.584554] iwlwifi :02:00.0: Failed to load firmware chunk!
  [9.584558] iwlwifi :02:00.0: Could not load the [0] uCode section
  [9.584567] iwlwifi :02:00.0: Failed to start INIT ucode: -110
  [9.584965] iwlwifi :02:00.0: Failed to run INIT ucode: -110
  [9.585041] iwlwifi :02:00.0: L1 Enabled - LTR Enabled

  Toggling the kill-switch did not enable the wifi.

  
  It seems that the problem is fixed by installing the latest version of the 
firmware by downloading 
  
https://raw.githubusercontent.com/OpenELEC/iwlwifi-firmware/master/firmware/iwlwifi-7260-17.ucode

  and placing it within /lib/firmware

  modprobe -r iwlwifi

  and

  modprobe iwlwifi

  resulted in the following dmesg-logs:
  [ 1135.124869] cfg80211: World regulatory domain updated:
  [ 1135.124872] cfg80211:  DFS Master region: unset
  [ 1135.124873] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
  [ 1135.124875] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 
2000 mBm), (N/A)
  [ 1135.124877] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 
2000 mBm), (N/A)
  [ 1135.124878] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 
2000 mBm), (N/A)
  [ 1135.124879] cfg80211:   (517 KHz - 525 KHz @ 8 KHz, 16 KHz 
AUTO), (N/A, 2000 mBm), (N/A)
  [ 1135.124881] cfg80211:   (525 KHz - 533 KHz @ 8 KHz, 16 KHz 
AUTO), (N/A, 2000 mBm), (0 s)
  [ 1135.124882] cfg80211:   (549 KHz - 573 KHz @ 16 KHz), (N/A, 
2000 mBm), (0 s)
  [ 1135.124883] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 
2000 mBm), (N/A)
  [ 1135.124884] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 
0 mBm), (N/A)
  [ 1135.126994] Intel(R) Wireless WiFi driver for Linux
  [ 1135.126996] Copyright(c) 2003- 2015 Intel Corporation
  [ 1135.128686] iwlwifi :02:00.0: loaded firmware version 17.352738.0 
op_mode iwlmvm
  [ 1135.149648] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 
7260, REV=0x144
  [ 1135.149804] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
  [ 1135.150127] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
  [ 1135.356449] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
  [ 1135.359048] iwlwifi :02:00.0 wlp2s0: renamed from wlan0
  [ 1135.382605] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
  [ 1135.382869] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
  [ 1135.383248] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
  [ 1135.584734] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
  [ 1135.585119] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
  [ 1135.603363] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
  [ 1135.652647] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.4
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Oct 14 08:48:10 2016
  Dependencies:
   
  InstallationDate: Installed on 2016-07-07 (98 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1635091] Re: New firmware is required for some iwlwifi modules

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  New firmware is required for some iwlwifi modules

Status in HWE Next:
  In Progress
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  Kernel complains about unable to load iwlwifi-7260-17.ucode.

  ubuntu@localhost:~$ dmesg | grep iwl
  [ 42.049462] iwlwifi :02:00.0: enabling device ( -> 0002)
  [ 42.074290] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-7260-17.ucode failed with error -2
  [ 42.376098] iwlwifi :02:00.0: loaded firmware version 16.242414.0 
op_mode iwlmvm
  [ 42.811854] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 
7260, REV=0x144
  [ 42.815269] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
  [ 42.815530] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
  [ 43.078312] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'

  This file can be found in commit
  f2cf4d67e8eced29c8a473d3a27057aa2df57c42.

  commit f2cf4d67e8eced29c8a473d3a27057aa2df57c42
  Author: Emmanuel Grumbach 
  Date:   Sun Jul 10 09:25:42 2016 +0300

  iwlwifi: add new -17 firmware for iwlmvm devices

  Revision number: 352738
  Build number: WFFW28817_L14LIN

  This is the last firmware that supports 3160 / 7260 / 7265.
  Newer firmware will support 7265D and up only.

  Signed-off-by: Emmanuel Grumbach 

  Xenial only. These files are already in yakkety.

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

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

[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

I think this is likely a kdump issue. It should rebuild the initrd with
appropriate modules when installed.

** Also affects: makedumpfile (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

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

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6
  [  132.643981] ---[ end trace eed6bbcd2c3bdfdf ]---
  [  132.646105]
  [  132.646176] Sending IPI to other CPUs
  [  132.647490] IPI complete
  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 104
   <- smp_release_cpus()
  [2.011346] alg: hash: Test 1 failed for crc32c-vpmsum
  [2.729254] sd 0:2:0:0: [sda] Assuming drive cache: write through
  [2.731554] sd 1:2:5:0: [sdn] Assuming drive cache: write through
  [2.739087] sd 1:2:4:0: [sdm] Assuming drive cache: write through
  [2.739089] sd 1:2:6:0: [sdo] Assuming drive cache: write through
  [2.739110] sd 1:2:7:0: [sdp] Assuming drive cache: write through
  [2.739115] sd 1:2:0:0: [sdi] Assuming drive cache: write through
  [2.739122] sd 1:2:3:0: [sdl] Assuming drive cache: write through
  [2.739123] sd 1:2:2:0: [sdk] Assuming drive cache: write through
  [2.739148] sd 1:2:1:0: [sdj] Assuming drive cache: write through
  [2.748938] sd 0:2:1:0: [sdb] Assuming drive cache: write through
  [2.748939] sd 0:2:7:0: [sdh] Assuming drive cache: write through
  [2.748940] sd 0:2:6:0: [sdg] Assuming drive cache:

[Kernel-packages] [Bug 1637165] Re: Module sha1-mb fails to load

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

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

Title:
  Module sha1-mb fails to load

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  The module sha1-mb always fails to load with "No such device":

  $ sudo modprobe sha1-mb
  modprobe: ERROR: could not insert 'sha1_mb': No such device

  This is a problem related to missing export/import functions and
  statesize in the algorithm definition. It's similar to the bug
  #1633058.

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

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

[Kernel-packages] [Bug 1635223] Re: please include mlx5_core modules in linux-image-generic package

https://lists.ubuntu.com/archives/kernel-team/2016-October/080618.html

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

** Also affects: linux (Ubuntu Zesty)
   Importance: Medium
   Status: Triaged

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

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

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: linux (Ubuntu Zesty)
   Status: Triaged => Fix Released

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

Title:
  please include mlx5_core modules in linux-image-generic package

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Because linux-image-generic pkg doesn't include mlx5_core,
  stock ubuntu cloud-images can't be used by VM guests using
  mellanox VFs, forcing the creation of an ad-hoc cloud image
  with added linux-image-extra-virtual

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1635223/+subscriptions

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

[Kernel-packages] [Bug 1637165] Re: Module sha1-mb fails to load

2016-10-27 Thread Marcelo Cerri

https://lists.ubuntu.com/archives/kernel-team/2016-October/080613.html
https://lists.ubuntu.com/archives/kernel-team/2016-October/080614.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/1637165

Title:
  Module sha1-mb fails to load

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The module sha1-mb always fails to load with "No such device":

  $ sudo modprobe sha1-mb
  modprobe: ERROR: could not insert 'sha1_mb': No such device

  This is a problem related to missing export/import functions and
  statesize in the algorithm definition. It's similar to the bug
  #1633058.

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

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

[Kernel-packages] [Bug 1626371] Re: cdc_ether fills kernel log

2016-10-27 Thread darthvader

The problem persists in mainline kernel 4.9-rc2

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

Title:
  cdc_ether fills kernel log

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo X1 4th gen with a dock attached:

  [ 1764.086306] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been 
dropped
  [ 1764.150317] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been 
dropped

  
  The USB Ethernet device would warn occasionally under the 4.4 kernel. Under 
the 4.8 kernel, it spams my kernel log so much that I don't get anything else.

  $ uname -a
  Linux aurora 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 20:00:03 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  joel@aurora ~ 
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

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

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

[Kernel-packages] [Bug 1635091] Re: New firmware is required for some iwlwifi modules

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

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-firmware (Ubuntu Xenial)
 Assignee: (unassigned) => Jesse Sung (wenchien)

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

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

Title:
  New firmware is required for some iwlwifi modules

Status in HWE Next:
  In Progress
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  In Progress

Bug description:
  Kernel complains about unable to load iwlwifi-7260-17.ucode.

  ubuntu@localhost:~$ dmesg | grep iwl
  [ 42.049462] iwlwifi :02:00.0: enabling device ( -> 0002)
  [ 42.074290] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-7260-17.ucode failed with error -2
  [ 42.376098] iwlwifi :02:00.0: loaded firmware version 16.242414.0 
op_mode iwlmvm
  [ 42.811854] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 
7260, REV=0x144
  [ 42.815269] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
  [ 42.815530] iwlwifi :02:00.0: L1 Enabled - LTR Enabled
  [ 43.078312] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'

  This file can be found in commit
  f2cf4d67e8eced29c8a473d3a27057aa2df57c42.

  commit f2cf4d67e8eced29c8a473d3a27057aa2df57c42
  Author: Emmanuel Grumbach 
  Date:   Sun Jul 10 09:25:42 2016 +0300

  iwlwifi: add new -17 firmware for iwlmvm devices

  Revision number: 352738
  Build number: WFFW28817_L14LIN

  This is the last firmware that supports 3160 / 7260 / 7265.
  Newer firmware will support 7265D and up only.

  Signed-off-by: Emmanuel Grumbach 

  Xenial only. These files are already in yakkety.

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

-- 
Mailing list: https://launchpad.net/~kernel-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-10-27 Thread Andreas John

This just happend to me when upgrading vom 4.7.8 to 4.8.4. Kernel is
self-compiled, but with the kernel config taken from Ubuntu Mainline
PPA.

I run a Macbook 11,3, so it's very similar to what at wvengen's setup
happens.

-- 
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: [   64.112245]  [] 
SyS_nanosleep

[Kernel-packages] [Bug 1637165] Re: Module sha1-mb fails to load

2016-10-27 Thread Marcelo Cerri

Yakkety already includes the fixes and Trusty does not include this
driver.

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

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

Title:
  Module sha1-mb fails to load

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The module sha1-mb always fails to load with "No such device":

  $ sudo modprobe sha1-mb
  modprobe: ERROR: could not insert 'sha1_mb': No such device

  This is a problem related to missing export/import functions and
  statesize in the algorithm definition. It's similar to the bug
  #1633058.

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

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

[Kernel-packages] [Bug 1637165] [NEW] Module sha1-mb fails to load

2016-10-27 Thread Marcelo Cerri

Public bug reported:

The module sha1-mb always fails to load with "No such device":

$ sudo modprobe sha1-mb
modprobe: ERROR: could not insert 'sha1_mb': No such device

This is a problem related to missing export/import functions and
statesize in the algorithm definition. It's similar to the bug #1633058.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

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

Title:
  Module sha1-mb fails to load

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The module sha1-mb always fails to load with "No such device":

  $ sudo modprobe sha1-mb
  modprobe: ERROR: could not insert 'sha1_mb': No such device

  This is a problem related to missing export/import functions and
  statesize in the algorithm definition. It's similar to the bug
  #1633058.

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

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

[Kernel-packages] [Bug 1574047] Re: Lenovo G50-30 laptop freezes randomly

lumiza, to clarify, if you can't boot into it at all, then it doesn't
fit the criteria of kernel-bug-exists-upstream.

Despite this, could you please provide the missing information following
https://wiki.ubuntu.com/DebuggingSystemCrash ?

** Tags removed: kernel-bug-exists-upstream-4.6-rc2 
kernel-bug-exists-upstream-4.8 kernel-bug-exists-upstream-4.8.4
** Tags added: kernel-bug-exists-upstream

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

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

Title:
  Lenovo G50-30 laptop freezes randomly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Keyboard or mouse do not work when the system freezes. Have to press
  power key to shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lumiza 1614 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 19:17:13 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=00509798-f59d-4d52-9500-f9a446e82c61
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 80G0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=44eeda32-7284-4e84-91ff-72fe3baefb7a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN47WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN47WW:bd04/16/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.name: 80G0
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1633681] Re: Lenovo G50-30 laptop does not start after rebooting

lumiza, could you please provide the missing information following
https://wiki.ubuntu.com/DebuggingKernelBoot ?

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

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

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

Title:
  Lenovo G50-30 laptop does not start after rebooting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It happens everytime when I reset my laptop:
  1. when I push "Reset" button in Ubuntu UI
  2. when I execute command via Terminal

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24 [modified: 
boot/vmlinuz-4.8.0-22-generic]
  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/pcmC0D0p:   lumiza 2276 F...m pulseaudio
   /dev/snd/controlC0:  lumiza 2276 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Oct 15 09:53:54 2016
  HibernationDevice: RESUME=UUID=98efa76d-932e-4955-9879-0d96cd54fa0d
  InstallationDate: Installed on 2016-10-15 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 80G0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=bc69e5fe-e021-4aa8-a6c4-9832aff639a0 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
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN48WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN48WW:bd08/03/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.name: 80G0
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1607571] Re: No network devices after suspend and resume

** Tags added: yakkety

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

Title:
  No network devices after suspend and resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on an Alienware 17R3 on Ubuntu 16.04.

  The wifi stops working after resume. The problem seems related to
  https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the
  solutions proposed there doesn't work. Other seems to have a problem
  related with the network-manager stop working (like
  http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-
  after-16-04-upgrade).

  However, in my case the network-manager restarts and stops after the
  resume. However, there is no device, and thus there is no list of
  available networks to join.

  For example, doing

  $ iwconfig
  lono wireless extensions.

  while in a normal reboot the wireless card information is printed

  $ iwconfig
  wlp60s0   IEEE 802.11abgn  ESSID:"Chapinlandia"  
Mode:Managed  Frequency:2.412 GHz  Access Point: 8C:04:FF:F6:90:9E  
 
Bit Rate=1 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr:off   Fragment thr:off
Power Management:on
Link Quality=51/70  Signal level=-59 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:36  Invalid misc:39   Missed beacon:0

  lono wireless extensions.

  enp59s0   no wireless extensions.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adin   3934 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 28 21:05:44 2016
  HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd
  InstallationDate: Installed on 2016-07-03 (25 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Alienware Alienware 17 R3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.3
  dmi.board.name: Alienware 17 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 17 R3
  dmi.product.version: 1.2.3
  dmi.sys.vendor: Alienware

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

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

[Kernel-packages] [Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04

Anthony Buckley, could you please advise to the results of 4.9-rc2? If
it is still reproducible in this, then this would be an upstream bug
also.

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

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

Title:
  Network scanner not detected by xsane after upgrade to 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hopefully I'm reporting this in the correct area/group. Sorry if not.
  After upgrading to 16.04, my scanner is no longer detected by xsane (and 
other scan apps.) The model is 'Epson WF-3520' multi-function and is connected 
wirelessly to the network.
  The problem occurs on all my computers: A Dell 64 bit desktop, An Asus 64 bit 
laptop, A Medion 32 bit laptop.
  I've upgraded to the latest software released by the manufacturer on 2 
computers, but it makes no difference.
  Printing works OK and also the scanner is detected if I connect using a USB 
cable (a second printer is installed though).
  The problem only occurs using the 'linux-image-4.4.0...' series of kernels. 
If I boot with any of the previous kernels available, 'linux-image-4.2.0...' or 
'linux-image-3.19.0...' everything works OK.
  I am able to ping the scanner.
  I've tried a number of suggested fixes from searching around various forums, 
although many of these relate to 'back-end' scanners connected to a host for 
network access which is not applicable as mine is connected directly to the 
network. In any case none have worked.
  I have tried the following:
  . Removing all manufacturer software and /usr/sane.d/epkowa.conf
  . Comment out all entries in the /usr/sane.d/dll (Back-end related)
  . Comment out all entries in the /usr/sane.d/dll.conf.conf except 'net' and 
adding 'epkowa' (Back-end related)
  . Disable the firewall (ufw)
  . Specifically adding a port to use (1865) (ie. net 192.1... 1865
  . Linking the libraries in /usr/lib/sane to /usr/lib/x86_64-linux-gnu/sane

  Other than that I'm at a loss and sticking with older kernels.

  Regards.

  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:  tony   4520 F pulseaudio
   /dev/snd/controlC1:  tony   4520 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Aug 14 16:37:16 2016
  HibernationDevice: RESUME=UUID=762f657a-d174-4173-b09d-52d580c09a91
  InstallationDate: Installed on 2013-10-01 (1047 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK Computer Inc. N71Jq
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=dea23950-d6b3-498c-abba-a94513b58579 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.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (14 days ago)
  dmi.bios.date: 12/24/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N71Jq.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N71Jq
  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.:bvrN71Jq.204:bd12/24/2009:svnASUSTeKComputerInc.:pnN71Jq:pvr1.0:rvnASUSTeKComputerInc.:rnN71Jq:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: N71Jq
  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/1613027/+subscriptions

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

[Kernel-packages] [Bug 1605433] Re: [Dell Alienware 17R3] enable/disable touchpad not working

** Tags added: yakkety

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

Title:
  [Dell Alienware 17R3] enable/disable touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad does not work as expected. It can't be enabled or
  disabled through FN+F11 combination.

  The light (in the pad) always turns on, regardless of its non
  functionality.

  The problem seems related to bug #1523738, and some say solution #24
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523738/comments/24)
  works, but it didn't for me.

  I'm not even sure if it is the same as the version of the hardware is
  different.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Jul 21 21:07:42 2016
  InstallationDate: Installed on 2016-07-03 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2016-07-16T11:29:07.694480
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adin   4247 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd
  InstallationDate: Installed on 2016-07-03 (24 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Alienware Alienware 17 R3
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.3
  dmi.board.name: Alienware 17 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 17 R3
  dmi.product.version: 1.2.3
  dmi.sys.vendor: Alienware

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

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

[Kernel-packages] [Bug 1532746] Re: SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

** Tags removed: kernel-bug-exists-upstream-4.7-rc5
** Tags added: kernel-bug-exists-upstream-4.8

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

Title:
  SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I've a problem with the keyboard of notebook HP Pavilion 15 ab062nl.
  the problem is with SHIFT ALT and CTRL buttons of the keyboard.

  for example when i use ALT-TAB shortcut, after few seconds, the ALT-TAB menu 
disappear as if i release ALT key, but isn't so.
  another example is when i navigate on web, when i scroll page with mouse 
wheel, sometimes the page start to resize, as if i'm pressing CTRL command 
while scroll, or if i'm writing a text, sometimes, borwser launch shortcut, as 
if i'm pressing CTRL while i type text, for exaple if i'm typing "b" letter, 
opens bookmarks...

  another example is while i'm typing text, if i press SHIFT key and
  start typing, begins to write uppercase letters and after a while,
  writes lowercase like I released shift, but i'm still pressing shift.

  for example if i press SHIFT+s, the result is this:
  SSs
  some letters are uppercase, but others are lowercase.

  WORKAROUND: Use kernel parameter:
  i8042.dumbkbd

  the only way to solve momentarily the problem, is pressing for some
  seconds the only SHIFT key, after that, the problems disappears
  indefinitely, or until the next restart.

  This problem occurs with all ubuntu version (x86 and x86_64), now i'm
  using Ubuntu 15.10, but i've also tried ubuntu 15.04, ubuntu 14.04,
  ubuntu 12.04, ubuntu 10.04.

  furthermore i've this problem also with other GNU/Linux Distributions (i've 
tried Fedora, OpenSuse, ArchLinux, Antergos, Debian, SteamOS).
  but isn't and hardware problem, because on Windows 8.1 and Windows 10 i 
haven't these problems.

  i've also tried to plug in an externa USB keyboard, and if i use
  external USB keybaord i haven't problems.

  i think is a problem of compatibility, with integrated keyboard of
  this notebook.

  i've tried to monitor these problems using XEV, and the results is
  that also if i'm not using notebook, sometimes XEV reads an INPUT of
  one of these 3 key (SHIFT, ALT, CTRL), and while i'm pressing one of
  these 3 key, XEV see also if i release and immedialty after press
  again the key.

  this is an example of the input while i press Left_ALT key for a while

  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 129987, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130147, (-142,152), root:(452,476),
  state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130391, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  whole log here http://pastebin.com/CPGz40aw

  and this is the output of xev, leaving the notebook on a few hours
  without using it http://pastebin.com/sYSHAbGy

  this is "xinput" output

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Laser Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ HP Truevision HDid=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=14   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=15   [slave  
keyboard (3)]

  i hope that this bug can be solved

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19

[Kernel-packages] [Bug 1519034] Re: Asus X302LA, Elantech touchpad dies off after pm-suspend or reprobe of 'psmouse' module

** Tags removed: kernel-bug-exists-upstream-4.4-rc5
** Tags added: kernel-bug-exists-upstream-4.8

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

Title:
  Asus X302LA, Elantech touchpad dies off after pm-suspend or reprobe of
  'psmouse' module

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have Asus X302LA notebook, and 'modprobe -r psmouse' followed by 'modprobe 
psmouse' makes its touchpad die off even without doing pm-suspend.
  Also I see in dmesg that ETPS/2 Elantech touchpad is initially created as 
/devices/platform/i8042/serio1/input/input5, and after module reload, it is 
recreated as .../input292 (but only after first module re-probe, next times 
nothing happens at all).
  The script in /etc/pm/sleep.d apparently does not do anything (probably need 
to re-test it after a fresh boot)

  i8042/serio/psmouse/elantech lines:
  i8042: PNP: PS/2 Controller [PNP030b:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
  serio: i8042 KBD port at 0x60,0x64 irq 1
  serio: i8042 AUX port at 0x60,0x64 irq 12
  input: AT Translated Set 2 keyboard as 
/devices/platform/i8042/serio0/input/input3
  psmouse serio1: elantech: assuming hardware version 4 (with firmware version 
0x381f00)
  psmouse serio1: elantech: Synaptics capabilities query result 0x10, 0x14, 
0x0e.
  psmouse serio1: elantech: Elan sample query result 00, 23, 64
  input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input5

  after manual mod-reprobe without pm-suspend :
  psmouse serio1: elantech: assuming hardware version 4 (with firmware version 
0x381f00)
  psmouse serio1: elantech: Synaptics capabilities query result 0x10, 0x14, 
0x0e.
  psmouse serio1: elantech: Elan sample query result 00, 23, 64
  input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio1/input/input292

  (then touchpad dies off)

  $ ls -l /etc/pm/sleep.d/05_elantech
  -rwxr-xr-x 1 root root 128 лис 22 20:33 /etc/pm/sleep.d/05_elantech

  $ cat /etc/pm/sleep.d/05_elantech
  #!/bin/sh
  case "$1" in
  suspend|hibernate)
   modprobe -r psmouse ;;
  resume|thaw)
  modprobe psmouse ;;
  esac

  after initial boot and pm-suspend : touchpad dies off, no records
  about its re-detection appear in dmesg

  now preparing to try a patch posted to linux-input mail list referred
  to at
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490130/comments/8

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mwg1482 F pulseaudio
   /dev/snd/controlC0:  mwg1482 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Nov 23 18:50:47 2015
  HibernationDevice: RESUME=UUID=6932e499-f0ad-4456-b93c-2b7f9bf763dc
  InstallationDate: Installed on 2009-11-01 (2213 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: ASUSTeK COMPUTER INC. X302LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=/dev/mapper/vg_c540scadaw-root64 ro rootflags=commit=3600 
transparent_hugepage=always init=/lib/systemd/systemd
  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
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X302LA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X302LA
  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.:bvrX302LA.203:bd04/20/2015:svnASUSTeKCOMPUTERINC.:pnX302LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X302LA
  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/1519034/+subscriptions

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

[Kernel-packages] [Bug 1453391] Re: Very slow Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0)

Ilari (ilarinews), 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.

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

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

Title:
  Very slow Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast
  Ethernet (rev b0)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading form Ubuntu 14.04 to Ubuntu 15.04, my gigabit ethernet
  controller is performing very very poorly.  I get < 10mb throughput.

  --

  lspic:

  02:00.0  controller: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or
  Fast Ethernet (rev b0)

  lshw:
  *-pci:4
   description: PCI bridge
   product: 82801JI (ICH10 Family) PCI Express Root Port 6
   vendor: Intel Corporation
   physical id: 1c.5
   bus info: pci@:00:1c.5
   version: 00
   width: 32 bits
   clock: 33MHz
   capabilities: pci normal_decode bus_master cap_list
   configuration: driver=pcieport
   resources: irq:28 ioport:c000(size=4096) 
memory:fe80-fe8f ioport:f080(size=2097152)
     *-network
  description: Ethernet interface
  product: AR8121/AR8113/AR8114 Gigabit or Fast Ethernet
  vendor: Qualcomm Atheros
  physical id: 0
  bus info: pci@:02:00.0
  logical name: eth0
  version: b0
  serial: XX:XX:XX:XX:XX:XX
  size: 1Gbit/s
  capacity: 1Gbit/s
  width: 64 bits
  clock: 33MHz
  capabilities: bus_master cap_list ethernet physical tp 10bt 
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
  configuration: autonegotiation=on broadcast=yes driver=ATL1E 
driverversion=1.0.0.7-NAPI duplex=full firmware=L1e ip=XX.XX.XX.XX latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
  resources: irq:17 memory:fe8c-fe8f 
ioport:cc00(size=128)
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test  23180 F pulseaudio
   /dev/snd/controlC1:  test  23180 F pulseaudio
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87da39cd-1a60-4c53-927d-87ae037d7a6b
  InstallationDate: Installed on 2015-04-29 (10 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  MachineType: System manufacturer P5QL-E
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=6107da8b-9d18-4922-a432-27a560213d1c ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 09/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1104
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QL-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 2.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1104:bd09/11/2009:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5QL-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1611831] Re: Can't boot from new kernel 4.4.0-34. Old kernel 4.4.0-31 is fine.

Ryan Budney, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611831/comments/25
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** No longer affects: linux (Ubuntu Xenial)

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

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

Title:
Can't boot from new kernel 4.4.0-34. Old kernel 4.4.0-31 is fine.

Status in linux package in Ubuntu:
Invalid

Bug description:
Greetings,

I recently upgraded from the 4.4.0-31 to 4.4.0-34 kernel in Ubuntu
16.04. If I try booting from 4.4.0-34, my system freezes just after I
enter my password to decrypt my hard-drive. If I ask it to boot from
4.4.0-31, everything is fine.

My boot.log file:

lvmetad is not active yet, using direct activation during sysinit
Volume group "ubuntu-vg" not found
Cannot process volume group ubuntu-vg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
Found volume group "ubuntu-vg" using metadata type lvm2
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
2 logical volume(s) in volume group "ubuntu-vg" now active
/dev/mapper/ubuntu--vg-root: recovering journal
/dev/mapper/ubuntu--vg-root: clean, 525872/28426240 files, 91143613/113674240
blocks

It's unclear to me what is going wrong. There appears to be no activity on
the computer. I let the boot sequence sit for 10 minutes (way longer than an
average boot time) my laptop's fan is running full-tilt. But there was no
hard-drive activity.

How can I find out what's going wrong?

I'm running Ubuntu 16.04 Linux on a Lenovo W530. I'm not certain what other
information would be helpful for a bug report. I would be happy to submit
whatever is deemed helpful.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: rybu 4449 F pulseaudio
/dev/snd/controlC0: rybu 4449 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=48cdbc4a-e07f-4aa4-bb23-e2904e1cd350
InstallationDate: Installed on 2016-04-26 (106 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: LENOVO 2436CTO
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
RelatedPackageVersions:
linux-restricted-modules-4.4.0-31-generic N/A
linux-backports-modules-4.4.0-31-generic N/A
linux-firmware1.157.2
Tags: xenial
Uname: Linux 4.4.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/18/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: G5ETA3WW (2.63 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2436CTO
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:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2436CTO
dmi.product.version: ThinkPad W530
dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1612895] Re: Display freezes on 2nd+subsequent logins

Nathan Dorfman, the next step is to fully reverse commit bisect from
kernel 4.8-rc2 to 4.9-rc1 in order to identify the last bad commit,
followed immediately by the first good one. Once this good commit has
been identified, it may be reviewed for backporting. Could you please do
this following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?

Please note, finding adjacent kernel versions is not fully commit
bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the fix commit (not kernel version) has
been identified, you then mark this report Status Confirmed.

Thank you for your help.

** Tags added: kernel-fixed-upstream-4.9-rc1 needs-reverse-bisect

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

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

Title:
  Display freezes on 2nd+subsequent logins

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  First boot after a fresh install of 16.04 from the 16.04.1 amd64
  desktop ISO, with 'download updates' enabled. This is alongside an
  existing 14.04 installation, which continues to work flawlessly. In
  particular, this issue cannot be reproduced there. (I've installed the
  -lts-xenial kernel package there, so it's version 4.4.0.34.24, but NOT
  the xorg ones.)

  The first login on the new system worked fine. After simply logging
  out and in again, the display freezes just after drawing my user's
  desktop. (This first time, everything was drawn, but on subsequent
  attempts the background was black and the top Unity panel was empty.)
  The mouse cursor is movable, but no button or key presses are
  recognized.

  Eventually, I press Ctrl+Alt+F1. The mouse cursor disappears
  immediately; the display stays frozen and otherwise unchanged. After
  another two minutes or so of waiting, I am finally dumped to the
  virtual tty, which works fine. At this point a couple of kernel stack
  traces appear in dmesg (see below), with timestamps corresponding to
  "just now," i.e. when the vty switch finally occurred.

  Switching back to the X vty via Alt+F7 brings me back to the still-
  frozen display, at which point all I can do is Ctrl+Alt+F1 and wait ~2
  minutes again. Stopping, then starting the lightdm service brings me
  back to a working login screen, but logging in just freezes right back
  again. Finally, rebooting the system allows me to login to a working
  desktop exactly once -- logging out and in again reproduces this
  problem reliably.

  The full dmesg is attached, but the short version is that stack traces
  appear in pairs, summarized by the following lines on the first
  occurrence:

  [  242.116429] WARNING: CPU: 2 PID: 2539 at 
/build/linux-dcxD3m/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1326 
drm_wait_one_vblank+0x1b5/0x1c0 [drm]()
  [  242.116498] CPU: 2 PID: 2539 Comm: Xorg Not tainted 4.4.0-31-generic 
#50-Ubuntu

  and by the following, slightly different ones, on the second and
  beyond:

  [  380.232443] WARNING: CPU: 1 PID: 4173 at 
/build/linux-dcxD3m/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:3963 
intel_crtc_wait_for_pending_flips+0x1e2/0x240 [i915]()
  [  380.232563] CPU: 1 PID: 4173 Comm: Xorg Tainted: GW   
4.4.0-31-generic #50-Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: 
boot/vmlinuz-4.4.0-31-generic]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  who3445 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Aug 12 19:51:28 2016
  HibernationDevice: RESUME=UUID=2065ee3e-d689-4432-a805-4a7822b06d0e
  InstallationDate: Installed on 2016-08-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 4236AR5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=093a7652-dfb2-4f9e-9ceb-23761b18c8ef ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET66WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4236AR5
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET66WW(1.36):bd10/31/2011:svnLENOVO:pn4

[Kernel-packages] [Bug 1615333] Re: S3/resume -> Memory corruption detected in low memory

jedie (launchpad-net-jensdiemer), 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/1615333

Title:
  S3/resume -> Memory corruption detected in low memory

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Every time, I resume from S3 I get a Memory corruption detected in low
  memory. it's supposed to be a BIOS issue (Bios has been updated to
  latest version)

  Dmesg :

   482.012031] Corrupted low memory at 880067f0 (67f0 phys) = 
2001
  [  482.012041] [ cut here ]
  [  482.012046] WARNING: CPU: 0 PID: 61 at 
/build/linux-5vkMGy/linux-4.4.0/arch/x86/kernel/check.c:141 
check_for_bios_corruption.part.1+0xaf/0x100()
  [  482.012047] Memory corruption detected in low memory
  [  482.012049] Modules linked in: drbg ansi_cprng ctr ccm pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nvidia_uvm(POE) 
nvidia(POE) binfmt_misc arc4 mxm_wmi kvm_amd ath9k kvm ath9k_common ath9k_hw 
joydev input_leds ath snd_hda_codec_realtek mac80211 snd_hda_codec_generic 
snd_hda_intel irqbypass snd_hda_codec cfg80211 crct10dif_pclmul crc32_pclmul 
snd_hda_core aesni_intel snd_hwdep aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd drm snd_pcm serio_raw snd_seq_midi snd_seq_midi_event 
fam15h_power snd_rawmidi snd_seq snd_seq_device snd_timer snd edac_mce_amd 
k10temp edac_core soundcore i2c_piix4 shpchp 8250_fintek tpm_infineon mac_hid 
wmi f71882fg adt7475 hwmon_vid parport_pc ppdev lp parport autofs4 raid10 raid1 
raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq
  [  482.012083]  async_xor async_tx xor raid6_pq libcrc32c hid_logitech_hidpp 
hid_logitech_dj usbhid hid psmouse r8169 mii ahci libahci fjes
  [  482.012091] CPU: 0 PID: 61 Comm: kworker/0:1 Tainted: P   OE   
4.4.0-34-generic #53-Ubuntu
  [  482.012092] Hardware name: MSI MS-7640/990FXA-GD65 (MS-7640), BIOS V20.5 
06/01/2015
  [  482.012095] Workqueue: events check_corruption
  [  482.012097]  0286 8eb30a27 88041bbefd20 
813f11b3
  [  482.012099]  88041bbefd68 81ca9938 88041bbefd58 
81081102
  [  482.012101]   8801 820fc730 
0001
  [  482.012103] Call Trace:
  [  482.012107]  [] dump_stack+0x63/0x90
  [  482.012110]  [] warn_slowpath_common+0x82/0xc0
  [  482.012112]  [] warn_slowpath_fmt+0x5c/0x80
  [  482.012115]  [] 
check_for_bios_corruption.part.1+0xaf/0x100
  [  482.012117]  [] check_corruption+0x18/0x50
  [  482.012119]  [] process_one_work+0x165/0x480
  [  482.012121]  [] worker_thread+0x4b/0x4c0
  [  482.012123]  [] ? process_one_work+0x480/0x480
  [  482.012125]  [] ? process_one_work+0x480/0x480
  [  482.012127]  [] kthread+0xd8/0xf0
  [  482.012129]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  482.012131]  [] ret_from_fork+0x3f/0x70
  [  482.012133]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  482.012134] ---[ end trace e749f67fe945b9d2 ]---

  ---

  System:Host: j-quadcore Kernel: 4.4.0-34-generic x86_64 (64 bit gcc: 
5.3.1)
     Desktop: Gnome 3.18.5 (Gtk 3.18.9-1ubuntu3.1) Distro: Ubuntu 16.04 
xenial
  Machine:   Mobo: MSI model: 990FXA-GD65 (MS-7640) v: 3.0 Bios: American 
Megatrends v: V20.5 date: 06/01/2015
  CPU:   Octa core AMD FX-8320E Eight-Core (-MCP-) cache: 16384 KB
     flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 
55049
     clock speeds: max: 3440 MHz 1: 3440 MHz 2: 3440 MHz 3: 3440 MHz 4: 
3440 MHz 5: 3440 MHz 6: 3440 MHz
     7: 3440 MHz 8: 3440 MHz
  Graphics:  Card: NVIDIA GT200 [GeForce GTX 260] bus-ID: 01:00.0
     Display Server: X.Org 1.18.3 drivers: nvidia (unloaded: 
fbdev,vesa,nouveau)
     Resolution: 1920x1080@60.00hz
     GLX Renderer: GeForce GTX 260/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 
340.96 Direct Rendering: Yes
  Info:  Processes: 329 Uptime: 1:06 Memory: 4118.7/15997.4MB Init: systemd 
runlevel: 5 Gcc sys: 5.4.0
     Client: Shell (bash 4.3.461) inxi: 2.2.35
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3689 F pulseaudio
jerome 4061 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3990cfcc-a32f-4626-8d03-7d7af5ad9412
  InstallationDate: Installed on 2014-12-27 (602 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  MachineType: MSI MS-7640
  NonfreeKernelModu

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

2016-10-27 Thread Yung Shen

Hardware Certification have begun testing this -proposed kernel.

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

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

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

Title:
  linux-lts-vivid: 3.19.0-74.82~14.04.1 -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-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-74.82~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: 1635424
  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/1635428/+subscriptions

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

[Kernel-packages] [Bug 1629714] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-1:1.0) is not active

2016-10-27 Thread David Knag

So THIS is what I get for doing a release upgrade to try and a somewhat
new version of libvirt

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

Title:
  scsi host6: runtime PM trying to activate child device host6 but
  parent (3-1:1.0) is not active

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [ 7434.858833] scsi host6: runtime PM trying to activate child device
  host6 but parent (3-1:1.0) is not active

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2140 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2140 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Oct  2 19:32:49 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (434 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1504445] Re: FocalTech touchpad stops working after suspend

** Tags added: cherry-pick

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

Title:
   FocalTech touchpad stops working after suspend

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have an Asus V502LX the persian version of the Asus K501LX.

  I have Ubuntu 14.04 installed and the kernel 4.1.6 installed. I had to
  install the kernel 4.1.6 to have the touchpad recognised. Under kernel
  3.19.30, as I am running now to file in this bug, the touchpad is
  recognised as a simple mouse (no two fingers scrolling...) and the
  problem I am describing below is also present...

  I noticed one problem. The Focaltech touchpad is not working after
  suspending the computer.

  Here is what I could find about the touchpad in
  /proc/bus/input/devices

  I: Bus=0011 Vendor=0002 Product=0012 Version=
  N: Name="FocalTechPS/2 FocalTech FocalTech Touchpad"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input5
  U: Uniq=
  H: Handlers=mouse0 event4
  B: PROP=5
  B: EV=b
  B: KEY=e520 1 0 0 0 0
  B: ABS=2608003

  Before suspending the computer, I can deactivate and activate again
  the touchpad with the hotkey of my keyboard without problem. However,
  once the computer suspended, nothing work to re-activate the touchpad.

  I tried a solution given on internet but it doesn't work properly.

  I created a file here /etc/pm/sleep.d/trackpad
  sudo gedit /etc/pm/sleep.d/trackpad

  and add the following
  #!/bin/sh
  case "$1" in
  suspend|hibernate)
  modprobe -r psmouse;
  resume|thaw)
  modprobe psmouse;
  esac

  With this file, the computer refuse to suspend. The touchpad keep
  working so it does something but I can't make my computer sleeping...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  9 12:05:16 2015
  InstallationDate: Installed on 2015-09-26 (12 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yogo   2073 F pulseaudio
   /dev/snd/controlC0:  yogo   2073 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=943b03af-c1bf-489e-8e42-485931fc619c
  InstallationDate: Installed on 2015-09-26 (12 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501LX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=37bd087e-a2f6-437e-8d20-b19536eb738a ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.127.15
  Tags:  trusty
  Uname: Linux 3.19.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True
  dmi.bios.date: 04/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501LX.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501LX
  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.:bvrK501LX.203:bd04/16/2015:svnASUSTeKCOMPUTERINC.:pnK501LX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501LX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K501LX
  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/1504445/+subscriptions

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

[Kernel-packages] [Bug 1566708] Re: Failed to boot when install ubuntu16.04 beta2 desktop64 with EFI boot in Vmware ESXi

Yuhua Zou, I am closing this report because the bug has been fixed in
the latest development version of Ubuntu.

This is a significant bug in Ubuntu. If you need a fix for the bug in
previous versions of Ubuntu, please perform as much as possible of the
SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

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

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

Title:
  Failed to boot when install ubuntu16.04 beta2 desktop64 with EFI boot
  in Vmware ESXi

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I insatlled Ubuntu16.04 beta2 desktop (64bit) with EFI boot on VMware
  ESXi 6.0.0 build 2494585, ESXi 5.5.0 build 3029944, and the on-going
  develop branch vsphere2016. When finish installation and reboot, I
  notice this on boot:

  /dev/sda2: recovering journal
  /dev/sda2: clean, 184027/950272 files, 1023281/3801088 blocks

  And then it hangs right there. It happens every time I reboot the VM.

  WORKAROUND: Change boot mode from EFI to BIOS.

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

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

[Kernel-packages] [Bug 1607153] Re: Mic mute key does not work for Ideapad laptops

2016-10-27 Thread Anthony Wong

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Mic mute key does not work for Ideapad laptops

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  When pressing mic mute key, there is no response and mic is not muted.

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

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

[Kernel-packages] [Bug 1635177] Re: mfd: intel-lpss: Add default I2C device properties for Apollo Lake

2016-10-27 Thread Anthony Wong

** Changed in: hwe-next
 Assignee: (unassigned) => Ying-Chun Liu (paulliu)

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

Title:
  mfd: intel-lpss: Add default I2C device properties for Apollo Lake

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  We need this patch for all Apollo Lake platforms for enabling the touchpad.
  This patch was cherry-picked from c50cdd62dda3f885c1e6ca8b3d5a0851c911ec54. 
And later backported to 4.4 kernel.
  It is because for Apollo Lake, the default freq/falling-time is incorrect. So 
it makes the i2c acts weird.

  Please consider SRU this commit.

  Impact:
All touchpad on Apollo Lake work unstable on i2c mode. Sometimes it will
  
fallback to PS/2 mode and lost some functionality.  
  
  Fix:
    touchpad works good on i2c mode.

  Tested:
    The patch is tested on many Dell ApolloLake laptops and works good.

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

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

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

2016-10-27 Thread Martin Pitt

> I built the another test kernel, up to the same commit:
a7fd20d1c476af4563e66865213474a2f9f473a4

This is GOOD.

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1637101] Re: On include/linux/acpi.h issue.

2016-10-27 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  On include/linux/acpi.h issue.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On include/linux/acpi.h functions is declared online for supress
  warning when compiling kernel.

  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/controlC0:  asu2326 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Oct 27 10:51:55 2016
  InstallationDate: Installed on 2016-04-29 (180 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  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: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

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

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

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