date:20160906

USN needed

** Changed in: kernel-sru-workflow/security-signoff
   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/1618083

Title:
  linux: 3.13.0-96.143 -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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1618083/+subscriptions

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

[Kernel-packages] [Bug 1618039] onibi (amd64) - tests ran: 136, failed: 0

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-110.151/onibi__3.2.0-110.151__2016-09-07_04-32-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/1618039

Title:
  linux: 3.2.0-110.151 -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-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1618039/+subscriptions

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

[Kernel-packages] [Bug 1618042] Re: linux-ti-omap4: 3.2.0-1488.115 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-ti-omap4: 3.2.0-1488.115 -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:
  Fix Released
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:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1618039
  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/1618042/+subscriptions

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

[Kernel-packages] [Bug 1612431] Re: CAPI: Update default setting for the psl_fir_cntl register

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

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

Title:
  CAPI: Update default setting for the psl_fir_cntl register

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:
  == Comment: #0 - Frederic Barrat - 2016-08-10 09:28:02 ==
  ---Problem Description---
  In the cxl driver, the psl_fir_cntl register is set to the recommended value 
for a lab environment. This should be converted to use the recommended setting 
for a production environment.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux freak 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:04:07 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  CAPI fpga card 

  Machine Type = any 
   
  ---Steps to Reproduce---
   setting of the psl_fir_cntl can be accessed through
  # cat /sys/kernel/debug/cxl/card0/fir_cntl
   

  == Comment: #2 - Frederic Barrat - 2016-08-10 10:13:22 ==
  Fix is in powerpc maintainer's tree and will find its way in 4.8-rc2;

  cxl: Set psl_fir_cntl to production environment value
  https://git.kernel.org/powerpc/c/c6d2ee09c2fffd3efdd31be2b2

  However, though simple, the upstream patch won't apply cleanly to the
  Xenial tree due to other patches merged in 4.8. So I'm attaching a
  version of the patch which applies on Xenial

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

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

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

--- Comment From praveen.pan...@in.ibm.com 2016-09-07 00:32 EDT---
(In reply to comment #19)
> This bug is awaiting verification that the kernel in -proposed solves the
> problem. Please test the kernel and update this bug with the results. If the
> problem is solved, change the tag 'verification-needed-xenial' to
> 'verification-done-xenial'.
>
> If verification is not done by 5 working days from today, this fix will be
> dropped from the source code, and this bug will be closed.
>
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> enable and use -proposed. Thank you!

Hi canonical,

Thanks for Fix !!
need one help , Facing this issue while installation can you please help me how 
i enable proposed repo while installation .

Regards
Praveen

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

Title:
  Ubuntu16.10:installation fails on Brazos system (31TB and 192 cores)
  No memory for flatten_device_tree (no room)

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

Bug description:
  == Comment: #0 - Praveen K. Pandey - 2016-07-16 10:00:52 ==
  Hi , 

I tried  ubuntu16.10 Installation in brazos (configuration 31TB memory and 
192 cores) system . installation failing during prom_init when trying to 
allocate flatten_dt memory) System F/w is 
  FW860.00 (TC860_020).

  Reproducible Step :

  1- Configure Power VM  system having profile with  31TB memory and 1 92 Core
  2- Start Ubuntu16.10  Installation 

  Actual Result :

  Installation drop in F/w Console as failing during prom_init

  Expected Result :

  Installation Should went through

  Log:

   Booting a command list

  OF stdout device is: /vdevice/v...@3000nitrd.gz  34.84MiB  100%  
3.01MiB/s ]
  Preparing to boot Linux version 4.4.0-30-generic (buildd@bos01-ppc64el-023) 
(gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #49-Ubuntu SMP Fri 
Jul 1 10:00:36 UTC 2016 (Ubuntu 4.4.0-30.49-generic 4.4.13)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/ubuntu-installer/ppc64el/yakkety/vmlinux 
tasks=standard pkgsel/language-pack-patterns= 
pkgsel/install-language-support=false DEBIAN_FRONTEND=text locale=en_US 
priority=low console-setup/ask_detect=false console-setup/layoutcode=us 
netcfg/disable_dhcp=true netcfg/confirm_static=true 
netcfg/choose_interface=6c:ae:8b:6a:81:98 netcfg/get_ipaddress=9.40.193.34/24 
netcfg/get_gateway=9.40.193.1 netcfg/get_nameservers=9.3.1.200 
netcfg/get_hostname=ltc-brazos1.aus.stglabs.ibm.com suite=yakkety 
scsi_mod.scan=sync sshd netcfg/get_domain=aus.stglabs.ibm.com unrestricted= 
url=tftp://9.3.80.16/tftpboot/ubuntu-installer/ppc64el/ubuntu-server.seed-01-6c-ae-8b-6a-81-98
 anna/choose_modules=network-console network-console/start=continue 
network-console/password=passw0rd network-console/password-again=passw0rd
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0e3e
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0e9e... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  No memory for flatten_device_tree (no room)
  EXIT called ok
  0 > 

  
  Regards
  Praveen

  == Comment: #8 - Sukadev Bhattiprolu  - 2016-08-05 02:27:07 ==
  Posted a couple of patches to the community for review: 

  http://marc.info/?l=linux-kernel=147037748624043=2
  http://marc.info/?l=linux-kernel=147037768124064=2 

  == Comment: #12 - Sukadev Bhattiprolu - 2016-08-17 19:23:22 ==

  Temporary fix to address the issue while the above patches are being
  reviewed.

  ==

  Canonical,

  Please add the attached temporary fix to 16.10 to address the
  following issue while the upstream changes are being considered.

 When booting a very large system with a large initrd we run out of space
 for the flattened device tree (FDT). To fix this we must increase the
 space allocated for the RMA region.

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

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

[Kernel-packages] [Bug 1618039] onibi (i386) - tests ran: 20, failed: 1

tests ran:  20, failed: 1;
  
http://kernel.ubuntu.com/testing/3.2.0-110.151/onibi__3.2.0-110.151__2016-09-07_02-57-00/results-index.html

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

Title:
  linux: 3.2.0-110.151 -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-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1618039/+subscriptions

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

[Kernel-packages] [Bug 1582075] Re: GPU HANG: ecode 6:0:0x85eefffc

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

Title:
  GPU HANG: ecode 6:0:0x85eefffc

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am using an i3 2100 system with an "Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)".

  I'm getting these errors after suspend, with the screen showing a
  little garbled (text appearing in the wrong color or disappearing).

  [27409.858424] [drm] GPU HANG: ecode 6:0:0x85eefffc, in chrome [9550], 
reason: Ring hung, action: reset
  [27409.858425] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [27409.858426] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [27409.858427] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [27409.858428] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [27409.858428] [drm] GPU crash dump saved to /sys/class/drm/card0/error
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  haggai 8000 F pulseaudio
   /dev/snd/controlC0:  haggai 8000 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ab5f4eed-4f9d-4097-8a15-cd7bc60070fa
  InstallationDate: Installed on 2013-01-31 (1200 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic 
root=UUID=35dc6554-8a90-49e3-852a-4ae844b92802 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-06 (10 days ago)
  UserGroups: adm cdrom debian-transmission dip docker libvirtd lpadmin lxd 
plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-207
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-207:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1552693] Re: Radeon driver only provides 1024x768 resolution

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

Title:
  Radeon driver only provides 1024x768 resolution

Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm using the latest development version of xenial. My graphics card
  is AMD HD7950 and I use an mini-DP to DP converter to connect it to an
  Acer XB240H monitor. The system works well in Windows 7.

  While using the open source radeon driver, the system was only able to
  detect resolution up to 1024x768:

  $ xrandr
  Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1024x768+0+0 (normal left inverted right x 
axis y axis) 0mm x 0mm
     1024x768  60.00*
     800x600   60.3256.25
     848x480   60.00
     640x480   59.94
  HDMI-0 disconnected (normal left inverted right x axis y axis)
  DVI-0 disconnected (normal left inverted right x axis y axis)

  $ dmesg | grep drm
  [0.615419] [drm] Initialized drm 1.1.0 20060810
  [0.630977] [drm] radeon kernel modesetting enabled.
  [0.633712] fb: switching to radeondrmfb from VESA VGA
  [0.633863] [drm] initializing kernel modesetting (TAHITI 0x1002:0x679A 
0x1682:0x3221).
  [0.633870] [drm] register mmio base: 0xF7E0
  [0.633870] [drm] register mmio size: 262144
  [0.633935] [drm] Changing default dispclk from 500Mhz to 600Mhz
  [0.633942] [drm] Detected VRAM RAM=3072M, BAR=256M
  [0.633943] [drm] RAM width 384bits DDR
  [0.633980] [drm] radeon: 3072M of VRAM memory ready
  [0.633980] [drm] radeon: 2048M of GTT memory ready.
  [0.633985] [drm] Loading tahiti Microcode
  [0.634037] [drm] Internal thermal controller with fan control
  [0.634064] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
  [0.638427] [drm] radeon: dpm initialized
  [0.639773] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
  [0.639776] [drm] GART: num cpu pages 524288, num gpu pages 524288
  [0.640486] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
  [0.640489] [drm] PCIE gen 3 link speeds already enabled
  [0.655393] [drm] PCIE GART of 2048M enabled (table at 0x002E8000).
  [0.675799] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [0.675800] [drm] Driver supports precise vblank timestamp query.
  [0.675874] [drm] radeon: irq initialized.
  [0.816685] [drm] ring test on 0 succeeded in 1 usecs
  [0.816689] [drm] ring test on 1 succeeded in 1 usecs
  [0.816692] [drm] ring test on 2 succeeded in 1 usecs
  [0.816697] [drm] ring test on 3 succeeded in 3 usecs
  [0.816701] [drm] ring test on 4 succeeded in 2 usecs
  [1.002289] [drm] ring test on 5 succeeded in 1 usecs
  [1.002294] [drm] UVD initialized successfully.
  [1.111494] [drm] ring test on 6 succeeded in 21 usecs
  [1.111505] [drm] ring test on 7 succeeded in 4 usecs
  [1.111505] [drm] VCE initialized successfully.
  [1.111627] [drm] ib test on ring 0 succeeded in 0 usecs
  [1.111648] [drm] ib test on ring 1 succeeded in 0 usecs
  [1.111673] [drm] ib test on ring 2 succeeded in 0 usecs
  [1.111688] [drm] ib test on ring 3 succeeded in 0 usecs
  [1.111702] [drm] ib test on ring 4 succeeded in 0 usecs
  [1.780603] [drm] ib test on ring 5 succeeded
  [2.280602] [drm] ib test on ring 6 succeeded
  [2.780592] [drm] ib test on ring 7 succeeded
  [2.781353] [drm] Radeon Display Connectors
  [2.781354] [drm] Connector 0:
  [2.781354] [drm]   DP-1
  [2.781355] [drm]   HPD5
  [2.781356] [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 
0x653c
  [2.781357] [drm]   Encoders:
  [2.781357] [drm] DFP1: INTERNAL_UNIPHY2
  [2.781358] [drm] Connector 1:
  [2.781358] [drm]   DP-2
  [2.781359] [drm]   HPD4
  [2.781360] [drm]   DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 
0x654c
  [2.781360] [drm]   Encoders:
  [2.781361] [drm] DFP2: INTERNAL_UNIPHY2
  [2.781361] [drm] Connector 2:
  [2.781362] [drm]   HDMI-A-1
  [2.781362] [drm]   HPD1
  [2.781363] [drm]   DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 
0x655c
  [2.781363] [drm]   Encoders:
  [2.781364] [drm] DFP3: INTERNAL_UNIPHY1
  [2.781364] [drm] Connector 3:
  [2.781365] [drm]   DVI-I-1
  [2.781365] [drm]   HPD3
  [2.781366] [drm]   DDC: 0x6580 0x6580 0x6584 0x6584 0x6588 0x6588 0x658c 
0x658c
  [2.781367] [drm]   Encoders:
  [2.781367] [drm] DFP4: INTERNAL_UNIPHY
  [2.781368] [drm] CRT1: INTERNAL_KLDSCP_DAC1
  [2.821395] [drm] fb mappable at 0xE06EA000
  [

[Kernel-packages] [Bug 1596281] Re: the target drive is not found when connected via USB 3 while installing Lubuntu alternate

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

Title:
  the target drive is not found when connected via USB 3 while
  installing Lubuntu alternate

Status in linux package in Ubuntu:
  Expired

Bug description:
  While trying to install from the Lubuntu 16.04 LTS alternate amd64
  daily iso file, the target drive is not found when connected via USB
  3.

  This happens with an SSD connected via USB 3. The corresponding
  desktop iso file works, and the released Lubuntu 16.04 LTS alternate
  amd64 worked.

  This problematic iso file can install into the same SSD, when
  connected internally (connected via SATA).

  I am writing this bug report booted from Lubuntu 16.04 desktop i364
  daily, and I will attach the output of some command lines to
  illustrate how the SSD is recognized (and should be recognized also
  but the alternate installer).

  I think the the bug is located in partman, or some related tool, that
  should identify connected drives.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-27-generic 4.4.0-27.46
  ProcVersionSignature: Ubuntu 4.4.0-27.46-generic 4.4.13
  Uname: Linux 4.4.0-27-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1700 F lxpanel
  CasperVersion: 1.376
  CurrentDesktop: LXDE
  Date: Sun Jun 26 09:38:09 2016
  LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160624)
  MachineType: TOSHIBA SATELLITE PRO C850-19W
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=sv 
keyboard-configuration/layoutcode?=se
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-27-generic N/A
   linux-backports-modules-4.4.0-27-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.10:bd09/24/2012:svnTOSHIBA:pnSATELLITEPROC850-19W:pvrPSCBXE-00C00VN5:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE PRO C850-19W
  dmi.product.version: PSCBXE-00C00VN5
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1620898] [NEW] 0.6.5.6 outdated. Latest version of ZoL on OpenZFS site is 0.6.5.7.

2016-09-06 Thread Ray Pating

Public bug reported:

If possible, please update zfs stack to 0.6.5.7, to include upstream bug
fixes.

** Affects: zfs-linux (Ubuntu)
 Importance: Undecided
 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/1620898

Title:
  0.6.5.6 outdated. Latest version of ZoL on OpenZFS site is 0.6.5.7.

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  If possible, please update zfs stack to 0.6.5.7, to include upstream
  bug fixes.

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

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

[Kernel-packages] [Bug 1166442] Re: Elantech clickpad/touchpad lacks multitouch features.

2016-09-06 Thread farhan

The same situation here as Arushi , I have an HP pavilion 14-ab042TX laptop.The 
touchpad supports basic functionalities like single click but no multitouch and 
two finger scroll.
I am using ubuntu 16.04 and kernel is 4.4.0-36-generic. The output of xinput is 
:

 Virtual core pointer   id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ PS/2 Elantech Touchpadid=12   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Video Bus id=8[slave  keyboard (3)]
↳ Power Button  id=9[slave  keyboard (3)]
↳ HP Truevision HD  id=10   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)]
↳ HP WMI hotkeysid=13   [slave  keyboard (3)]
↳ HP Wireless hotkeys   id=14   [slave  keyboard (3)]
When i do xinput list-props 12 , it shows:

Device 'PS/2 Elantech Touchpad':
Device Enabled (168):   1
Coordinate Transformation Matrix (170): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (289): 0
Device Accel Constant Deceleration (290):   1.00
Device Accel Adaptive Deceleration (291):   1.00
Device Accel Velocity Scaling (292):10.00
Device Product ID (285):2, 1
Device Node (286):  "/dev/input/event6"
Evdev Axis Inversion (293): 0, 0
Evdev Axes Swap (295):  0
Axis Labels (296):  "Rel X" (178), "Rel Y" (179)
Button Labels (297):"Button Left" (171), "Button Middle" (172), 
"Button Right" (173), "Button Wheel Up" (174), "Button Wheel Down" (175)
Evdev Scrolling Distance (298): 0, 0, 0
Evdev Middle Button Emulation (299):0
Evdev Middle Button Timeout (300):  50
Evdev Third Button Emulation (301): 0
Evdev Third Button Emulation Timeout (302): 1000
Evdev Third Button Emulation Button (303):  3
Evdev Third Button Emulation Threshold (304):   20
Evdev Wheel Emulation (305):0
Evdev Wheel Emulation Axes (306):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (307):10
Evdev Wheel Emulation Timeout (308):200
Evdev Wheel Emulation Button (309): 4
Evdev Drag Lock Buttons (310):  0
On doing dmesg | grep elantech gives:
[3.547709] psmouse serio1: elantech: unknown hardware version, aborting...
This message is also displayed every time I boot 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/1166442

Title:
  Elantech clickpad/touchpad lacks multitouch features.

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Fix Released
Status in linux source package in Saucy:
  Fix Released
Status in linux package in Arch Linux:
  New

Bug description:
  Newer versions of the Elantech multitouch trackpad are not fully
  supported in Linux.  These appear in many of the newer Samsung
  laptops, for example.  elantech.c in the kernel needs to be updated to
  support these models (up to v7 perhaps?)

  This bug is confirmed to affect a range of samsung laptops running
  Ubuntu 12.04 and newer, ArchLinux, Fedora and also affects the current
  (3.9) upstream kernel.

  A dkms package was produced in 2011 (see
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
  intel/+bug/681904/comments/64) which may fix certain older laptops
  affected by this issue, but doesn't fix newer models.

  == Original Report ==

  Hello,

  So far I've been having a problem with my Elantech multitouch trackpad in 
Linux. Basically all i get is right click, left click, and tap to click, along 
with basic  movement. The problem seems to be rooted in improper detection of 
the trackpad, likely b/c its a new revision or whatnot. Of note is that working 
elantech trackpads of the past in forums i scouted through show up as "ETPS/2 
Elantech Touchpad". Mine just shows up in xinput as "PS/2 Elantech Touchpad". I 
think this might be a simple fix in the end, just improper detection, I hope. 
For reference, I've tried kernel 3.5 on Ubuntu 12.10 and kernel 3.8.0-17 on 
Ubuntu 13.04 thus far, with all combinations of psmouse.

[Kernel-packages] [Bug 1619766] Re: Backport E3 Skylake Support in ie31200_edac to Xenial

2016-09-06 Thread Mark McCallister

Looks great!

# dmesg|grep -i edac
[9.551304] EDAC MC: Ver: 3.0.0
[9.605508] EDAC MC0: Giving out device to module ie31200_edac controller 
IE31200: DEV :00:00.0 (POLLED)

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

Title:
  Backport E3 Skylake Support in ie31200_edac to Xenial

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Skylake E3 Support was added to ie31200_edac with the following commit:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/edac/ie31200_edac.c?id=953dee9bbd245f5515173126b9cc8b1a2c340797

  Could we get this support backported to Xenial?

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

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

[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

2016-09-06 Thread Jason Gambrel

Followup to my last comment.  Checked which packages were installed,
they were all from oibaf ppa so removee xorg-edgers ppa for the time
being.  So far no further freezes, but will report back later.

Jay

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

Title:
  Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
  4.4.0-16

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm using ubuntu 16.04 on a XPS 15 9550.

  Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
  standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
  the system freezes when attempting a suspend. I get  no response from
  the system (nor keyboard, nor screen, nor touchpad), but it gets very
  hot, so that it must be running something.

  Booting with 4.4.0-15 makes the suspend to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  macias 1770 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr  5 14:56:17 2016
  HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
  InstallationDate: Installed on 2016-03-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1618039] onibi (amd64) - tests ran: 20, failed: 0

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-110.151/onibi__3.2.0-110.151__2016-09-07_01-16-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/1618039

Title:
  linux: 3.2.0-110.151 -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-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1618039/+subscriptions

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

[Kernel-packages] [Bug 1618678] Re: Disk Device Driver Reported Error: DID_ERROR ... DRIVER SENSE

2016-09-06 Thread Raymond

Joseph, we just verified that this bug manifests itself in the current
upstream kernel (4.4.19). I added the tag "kernel-bug-exists-upstream"
to the report. Thanks!

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

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

Title:
  Disk Device Driver Reported Error: DID_ERROR ... DRIVER SENSE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu 16.04.1 LTS upgrade from kernel 4.4.0-21 to 4.4.0-34
  introduced the following periodic error message sequence reported in
  dmesg/syslog:

  ...
  sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_SENSE
  sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor] 
  sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
  sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06 2c 00 da 00 
00 00 00 00 4f 00 c2 00 b0 00 
  sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_SENSE
  sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor] 
  sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
  sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 
00 00 00 00 00 00 00 00 e5 00 
  sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_SENSE
  sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor] 
  sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
  sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(12)/Blank a1 06 20 da 
00 00 4f c2 00 b0 00 00 
  ...

  These repeat at precisely five and ten minute intervals but appear to
  result in no data corruption, nor performance degradation on the
  external USB drive.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   rap3412 F...m pulseaudio
   /dev/snd/pcmC1D0p:   rap3412 F...m pulseaudio
   /dev/snd/controlC1:  rap3412 F pulseaudio
   /dev/snd/controlC0:  rap3412 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 30 19:48:43 2016
  HibernationDevice: RESUME=UUID=bb098361-baff-41e3-bf95-dad938b5d42c
  InstallationDate: Installed on 2016-08-10 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s9no wireless extensions.
  MachineType: ECS K8M890M-M
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=d38a2b9b-2da3-48e2-b5f8-a464f49a5dc5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080013
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: K8M890M-M
  dmi.board.vendor: ECS
  dmi.board.version: 1.X
  dmi.chassis.asset.tag: 0123ABC
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080013:bd12/29/2006:svnECS:pnK8M890M-M:pvr1.X:rvnECS:rnK8M890M-M:rvr1.X:cvnECS:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: K8M890M-M
  dmi.product.version: 1.X
  dmi.sys.vendor: ECS

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

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

[Kernel-packages] [Bug 1620658] Re: linux: 4.4.0-38.57 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

** Description changed:

  This bug is for tracking the 4.4.0-38.57 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-stable-phase:Packaging
- kernel-stable-phase-changed:Tuesday, 06. September 2016 15:02 UTC
- 
  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging
+ kernel-stable-phase-changed:Wednesday, 07. September 2016 02:04 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

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

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

Title:
  linux: 4.4.0-38.57 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

2016-09-06 Thread Jason Gambrel

Same problem here.  Lenovo G510 with I5 and integrated graphics.  Just
installed elementary OS Loki Beta.  Currently running 4.4.0-36-generic.
Randomly freezes on resuming from suspend.  Screen does not blank out,
windows are visible but everything is unresponsive including
mouse/touchpad.  Happens about 1 in 4 resumes.

Thinking this might be a video driver issue I just added the oibaf and
x-org/edgers ppas to update my graphics drivers to the latest by doing:

sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo add-apt-repository ppa:xorg-edgers/ppa
sudo apt-get update
sudo apt-get dist-upgrade

I'm not certain this will have any effect at all or even if it is a good
or bad idea to add both.  One is likely enough.  Did it this morning,
and so far no more freezing, but that might be luck.  I will report
later in the week.

Jay

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

Title:
  Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
  4.4.0-16

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm using ubuntu 16.04 on a XPS 15 9550.

  Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
  standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
  the system freezes when attempting a suspend. I get  no response from
  the system (nor keyboard, nor screen, nor touchpad), but it gets very
  hot, so that it must be running something.

  Booting with 4.4.0-15 makes the suspend to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  macias 1770 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr  5 14:56:17 2016
  HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
  InstallationDate: Installed on 2016-03-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1620422] Re: Macbook Pro Retina 12, 1 SD Card Reader Doesn't Work

2016-09-06 Thread graingert

How do I uninstall those modules? Does it need an apt-get uninstall or
can I disable them for just the mailine kernel?

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

Title:
   Macbook Pro Retina 12,1 SD Card Reader Doesn't Work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SD card reader doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graingert   2672 F pulseaudio
   /dev/snd/controlC1:  graingert   2672 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep  6 00:39:03 2016
  InstallationDate: Installed on 2016-01-05 (244 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic.efi.signed 
root=UUID=665d68d7-0c44-48e6-9e4c-9496a5c21d21 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9136-generic N/A
   linux-backports-modules-4.4.0-9136-generic  N/A
   linux-firmware  1.160
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-09-05 (0 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1620422] Re: Macbook Pro Retina 12, 1 SD Card Reader Doesn't Work

2016-09-06 Thread graingert

@penalvch I thought you said not the latest kernel before

Do you know which kernel version I should try, specifically?

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc5/ ?

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

Title:
   Macbook Pro Retina 12,1 SD Card Reader Doesn't Work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SD card reader doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graingert   2672 F pulseaudio
   /dev/snd/controlC1:  graingert   2672 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep  6 00:39:03 2016
  InstallationDate: Installed on 2016-01-05 (244 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic.efi.signed 
root=UUID=665d68d7-0c44-48e6-9e4c-9496a5c21d21 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9136-generic N/A
   linux-backports-modules-4.4.0-9136-generic  N/A
   linux-firmware  1.160
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-09-05 (0 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-110.151/onibi__3.2.0-110.151__2016-09-07_00-33-00/results-index.html

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

Title:
  linux: 3.2.0-110.151 -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-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1618039/+subscriptions

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

[Kernel-packages] [Bug 1618039] onibi (amd64) - tests ran: 2, failed: 0

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-110.151/onibi__3.2.0-110.151__2016-09-07_00-10-00/results-index.html

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

Title:
  linux: 3.2.0-110.151 -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-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1618039/+subscriptions

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

[Kernel-packages] [Bug 1618039] onibi (i386) - tests ran: 10, failed: 1

tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/3.2.0-110.151/onibi__3.2.0-110.151__2016-09-06_23-25-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/1618039

Title:
  linux: 3.2.0-110.151 -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-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1618039/+subscriptions

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

[Kernel-packages] [Bug 1618040] Re: linux: 4.4.0-37.56 -proposed tracker

USN needed

** Changed in: kernel-sru-workflow/security-signoff
   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/1618040

Title:
  linux: 4.4.0-37.56 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
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-37.56 upload package. This bug will
  contain status and testing results related to that upload.

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

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1618040/+subscriptions

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

[Kernel-packages] [Bug 1618039] onibi (amd64) - tests ran: 10, failed: 0

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-110.151/onibi__3.2.0-110.151__2016-09-06_22-41-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/1618039

Title:
  linux: 3.2.0-110.151 -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-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1618039/+subscriptions

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

[Kernel-packages] [Bug 1620811] Re: Focaltech touchpad detected as mouse on Asus K501UW laptop

2016-09-06 Thread David DIDIER

I have the same touchpad on my Asus Zenbook UX501 and I can confirm that it 
isn't recognized as such by the latest kernels installed from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7, 4.6.7 nor 4.7.2
And the function key to enable or disable the touchpad is not recognized as 
well (tested with xev).

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

Title:
  Focaltech touchpad detected as mouse on Asus K501UW laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following the bug reporting documentation here:
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

  The Focaltech touchpad on Asus K501UW laptop is detected as a mouse,
  so I can't access touchpad features such as two-finger scrolling or
  use two-finger tap as right mouse button. The touchpad is recognized
  in xinput-list as "FTE1001:00 0B05:0101".

  The bug appears in Ubuntu Mate 16.04.1 x64 and Linux Mint 18 Cinnamon
  x64, both with kernel 4.4.0-31. I've also tried Linux Mint 17.3 x64
  with kernel 3.19, and there the touchpad does not work at all (does
  not function even as a mouse).

  The bug is resemblant of #1372609.

  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:  e2 3605 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Sep  6 15:13:50 2016
  HibernationDevice: RESUME=UUID=8407ca60-029d-4be6-ab12-a2f1aee1d843
  InstallationDate: Installed on 2016-09-05 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=826cac6a-2d18-4d8d-a9ee-85299d3cac91 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.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UW.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UW
  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.:bvrK501UW.203:bd03/30/2016:svnASUSTeKCOMPUTERINC.:pnK501UW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K501UW
  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/1620811/+subscriptions

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

[Kernel-packages] [Bug 1587714] Re: MacBookPro11, 4 fails to poweroff or suspend

2016-09-06 Thread Joe Barnett

Verified this fixes the issue on xenial on kernel 4.4.0-37-generic.  Do
you still need further verification on other releases?

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

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

Title:
  MacBookPro11,4 fails to poweroff or suspend

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Since the release of the 2015 MacBookPro11,4 (15" retina), it has been
  unable to suspend or poweroff on linux.  Recently,
  https://bugzilla.kernel.org/show_bug.cgi?id=103211 has received a
  patch that works to fix these issues.  The patch is in comment #172,
  and is also attached to this bugreport, and reported to work very well
  by users of other distributions.  In addition, I can confirm that
  building the latest xenial 4.4.0-22-generic kernel with this patch
  applied fixes the issue.  Can this be added to the official xenial
  kernel?

  Thanks!

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

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

[Kernel-packages] [Bug 1618251] onibi (i386) - tests ran: 81, failed: 32

tests ran:  81, failed: 32;
  
http://kernel.ubuntu.com/testing/3.19.0-69.77~14.04.1/onibi__3.19.0-69.77~14.04.1__2016-09-06_17-09-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-69.77~14.04.1 -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:
  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-69.77~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

  -- swm properties --
  derivative-trackers-created: true
  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/1618251/+subscriptions

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

[Kernel-packages] [Bug 1620741] Re: Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown

HP Compaq nx6325
16.04 shutdown hangs ending with... (see more authoritative screenshot attached)
etc etc
systemd-shutdown[1]: All filesystems unmounted
systemd-shutdown[1]: Deactivating swaps.
systemd-shutdown[1]: All swaps deactivated.
systemd-shutdown[1]: Detaching loop devices.
systemd-shutdown[1]: All loop devices detached.
systemd-shutdown[1]: Detaching DM devices.
systemd-shutdown[1]: All DM devices detached.
systemd-shutdown[1]: Powering off.
tg3 :02:01.0 enp2s1: Link is up at 100 Mbps, full duplex
tg3 :02:01.0 enp2s1: Flow control is on for TX and on for ??
IPv6: ADDRCONF(NETDEV_CHANGE): enp2s1: link becomes ready
 

** Attachment added: "Screenshot of last moments of shutdown before hanging"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620741/+attachment/4735783/+files/20160906_200716p04NoShutdown.jpg

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

Title:
  Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown

Status in linux package in Ubuntu:
  Incomplete

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

  Have changed /etc/default/grub to attempt a fix without success...
  (grub.ref was original grub)

  :/etc/default$ grep CMDLINE grub*

  grub.ref:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  grub.ref:GRUB_CMDLINE_LINUX="forcepae"

  grub:GRUB_CMDLINE_LINUX_DEFAULT="acpi=noirq debug=y"
  grub:GRUB_CMDLINE_LINUX="forcepae"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  Uname: Linux 4.6.0-040600-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  6 18:16:30 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  NonfreeKernelModules: wl
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.6.0-040600-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1609475] Re: recovery mode completely broken by systemd

apport information

** Tags added: apport-collected

** Description changed:

  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).
  
  There is a problem running on this machine, but the problem report here
  is specifically about how systemd makes this impossible to debug.
  
  Symptoms:
  
  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"
  
  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"
  
  It appears to boot fine. From the Recovery Menu I select "root: Drop to
  root shell prompt", then "Press Enter for maintenance". All is good so
  far: I get a prompt.
  
  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:
  
  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.
  
  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of the
  lines has the ctrl-D for maintenance message.
  
  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts me
  back to the frozen recovery menu.
  
  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that the
  shell and the recovery menu are both fighting over the keyboard. By
  pressing cursor down repeatedly, it appears about 50% of them cause the
  recovery menu to move.
  
  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps; and
  when I get a shell, I want that shell to be mine on the console with no
  interference - and not taken away again.
  
- Lots of people say "systemd sucks", but I am submitting this in the hope
- that providing a *specific* way that it sucks might help get it fixed.
- (I have had a number of other cases of system recovery being frustrated
- by systemd, but this time I thought I would at least document the
- specifics)
+ Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
+ --- 
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ Card0.Amixer.info: Error: [Errno 2] No such file or directory
+ Card0.Amixer.values: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
+ InstallationDate: Installed on 2016-08-04 (33 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ IwConfig: Error:

[Kernel-packages] [Bug 1609475] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1609475/+attachment/4735768/+files/CRDA.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:

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

apport information

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

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64

[Kernel-packages] [Bug 1609475] PciMultimedia.txt

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735774/+files/PciMultimedia.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64

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

apport information

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

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1609475/+attachment/4735773/+files/Lspci.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)

[Kernel-packages] [Bug 1609475] Card0.Codecs.codec.2.txt

apport information

** Attachment added: "Card0.Codecs.codec.2.txt"

https://bugs.launchpad.net/bugs/1609475/+attachment/4735770/+files/Card0.Codecs.codec.2.txt

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

Title:
recovery mode completely broken by systemd

Status in linux package in Ubuntu:
Incomplete

Bug description:
Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
machines (with 8GB RAM and Crucial BX200 SSD).

There is a problem running on this machine, but the problem report
here is specifically about how systemd makes this impossible to debug.

Symptoms:

* Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB
/var, 202GB unused, 8GB swap
* On reboot strange things happen. The system doesn't come up fully;
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
[systemd-udevd:1148]"

So I try to boot again this time following "Advanced options for
Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

It appears to boot fine. From the Recovery Menu I select "root: Drop
to root shell prompt", then "Press Enter for maintenance". All is good
so far: I get a prompt.

However while I sit looking at this screen, after about two minutes a
bunch of systemd messages scroll up. I captured them as best as I can
with a camera:

[ OK ] Reached target Timers.
[ OK ] Reached target Login Prompts.
[ OK ] Started Stop ureadahead data collection 45s after completed startup
[ OK ] Reached target System Time Synchronized.
[ OK ] Reached target Sockets.
Starting Create Volatile Files and Directories...
[ OK ]Started Set console scheme.
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[FAILED] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
[FAILED] Failed to start LSB: AppArmor initialization.
See 'systemctl status apparmor.service' for details.
Starting Raise network interfaces...
[ OK ] Started Raise network interface.
[ OK ] Reached target Network.
[ OK ] Reached target Network is Online.
Starting iSCSI initiator daemon (iscsid)...
[ OK ] Started Set console font and keymap.
[ OK ] Started iSCSI initiator daemon (iscsid).
Starting Login to default iSCSI targets...
[ OK ] Created slice system-getty.slice.
[ OK ] Started Login to default iSCSI targets.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.

At this point it hangs for a few more seconds. Then a few more lines
flash up onto the screen - too fast to see, although I think one of
the lines has the ctrl-D for maintenance message.

Then I can see the Recovery Menu again, *but the keyboard apparently
does not work*. That is, I cannot move the selection up or down: it
appears completely dead at this point. Alt-F2 switches me to a screen
which is completely black apart from flashing cursor, and Alt-F1 puts
me back to the frozen recovery menu.

However, hitting Enter *does* give me a command line prompt again! But
then pressing up and down selects the recovery menu. It appears that
the shell and the recovery menu are both fighting over the keyboard.
By pressing cursor down repeatedly, it appears about 50% of them cause
the recovery menu to move.

This is completely pants: if I boot into recovery mode, I *don't* want
systemd nonsense, I want to see a sequential series of bootup steps;
and when I get a shell, I want that shell to be mine on the console
with no interference - and not taken away again.

Lots of people say "systemd sucks", but I am submitting this in the hope that
providing a *specific* way that it sucks might help get it fixed. (I have had a
number of other cases of system recovery being frustrated by systemd, but this
time I thought I would at least document the specifics)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.4.0-31-generic.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p',
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
InstallationDate: Installed on 2016-08-04 (33 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" -

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735777/+files/ProcModules.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64

[Kernel-packages] [Bug 1609475] Card0.Codecs.codec.0.txt

apport information

** Attachment added: "Card0.Codecs.codec.0.txt"

https://bugs.launchpad.net/bugs/1609475/+attachment/4735769/+files/Card0.Codecs.codec.0.txt

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

Title:
recovery mode completely broken by systemd

Status in linux package in Ubuntu:
Incomplete

Bug description:
Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
machines (with 8GB RAM and Crucial BX200 SSD).

There is a problem running on this machine, but the problem report
here is specifically about how systemd makes this impossible to debug.

Symptoms:

So I try to boot again this time following "Advanced options for
Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

It appears to boot fine. From the Recovery Menu I select "root: Drop
to root shell prompt", then "Press Enter for maintenance". All is good
so far: I get a prompt.

However while I sit looking at this screen, after about two minutes a
bunch of systemd messages scroll up. I captured them as best as I can
with a camera:

At this point it hangs for a few more seconds. Then a few more lines
flash up onto the screen - too fast to see, although I think one of
the lines has the ctrl-D for maintenance message.

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735775/+files/ProcCpuinfo.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64

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

apport information

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

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735776/+files/ProcInterrupts.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64

[Kernel-packages] [Bug 1609475] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735771/+files/CurrentDmesg.txt

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

Title:
  recovery mode completely broken by systemd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).

  There is a problem running on this machine, but the problem report
  here is specifically about how systemd makes this impossible to debug.

  Symptoms:

  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"

  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"

  It appears to boot fine. From the Recovery Menu I select "root: Drop
  to root shell prompt", then "Press Enter for maintenance". All is good
  so far: I get a prompt.

  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:

  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.

  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of
  the lines has the ctrl-D for maintenance message.

  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts
  me back to the frozen recovery menu.

  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that
  the shell and the recovery menu are both fighting over the keyboard.
  By pressing cursor down repeatedly, it appears about 50% of them cause
  the recovery menu to move.

  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps;
  and when I get a shell, I want that shell to be mine on the console
  with no interference - and not taken away again.

  Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
  InstallationDate: Installed on 2016-08-04 (33 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64

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

apport information

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

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

Title:
  Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown

Status in linux package in Ubuntu:
  Incomplete

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

  Have changed /etc/default/grub to attempt a fix without success...
  (grub.ref was original grub)

  :/etc/default$ grep CMDLINE grub*

  grub.ref:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  grub.ref:GRUB_CMDLINE_LINUX="forcepae"

  grub:GRUB_CMDLINE_LINUX_DEFAULT="acpi=noirq debug=y"
  grub:GRUB_CMDLINE_LINUX="forcepae"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  Uname: Linux 4.6.0-040600-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  6 18:16:30 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  NonfreeKernelModules: wl
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.6.0-040600-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  Xubuntu 16.04 on HP Compaq nx6325 freezes on Suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On suspend mouse movement stops.

  andymc@mvac21:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Suspend freezes in Kernel linux-headers-4.4.0-36 and linux-
  headers-4.6.0-040600

  Only way out is hold down power button for about 6 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  Uname: Linux 4.6.0-040600-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  6 17:55:49 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  NonfreeKernelModules: wl
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.6.0-040600-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1620733] Re: Xubuntu 16.04 on HP Compaq nx6325 freezes on Suspend

apport information

** Tags added: apport-collected

** Description changed:

  On suspend mouse movement stops.
  
  andymc@mvac21:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  
  Suspend freezes in Kernel linux-headers-4.4.0-36 and linux-
  headers-4.6.0-040600
  
  Only way out is hold down power button for about 6 seconds.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  Uname: Linux 4.6.0-040600-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  6 17:55:49 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: i386
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-08-16 (21 days ago)
+ InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
+ NonfreeKernelModules: wl
+ Package: linux (not installed)
+ Tags:  xenial
+ Uname: Linux 4.6.0-040600-generic i686
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Xubuntu 16.04 on HP Compaq nx6325 freezes on Suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On suspend mouse movement stops.

  andymc@mvac21:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Suspend freezes in Kernel linux-headers-4.4.0-36 and linux-
  headers-4.6.0-040600

  Only way out is hold down power button for about 6 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  Uname: Linux 4.6.0-040600-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  6 17:55:49 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  NonfreeKernelModules: wl
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.6.0-040600-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1620741] Re: Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown

apport information

** Tags added: apport-collected

** Description changed:

  $ lsb_release -rd
  Description: Ubuntu 16.04.1 LTS
  Release: 16.04
  
  Have changed /etc/default/grub to attempt a fix without success...
  (grub.ref was original grub)
  
  :/etc/default$ grep CMDLINE grub*
  
  grub.ref:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  grub.ref:GRUB_CMDLINE_LINUX="forcepae"
  
  grub:GRUB_CMDLINE_LINUX_DEFAULT="acpi=noirq debug=y"
  grub:GRUB_CMDLINE_LINUX="forcepae"
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  Uname: Linux 4.6.0-040600-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  6 18:16:30 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: i386
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-08-16 (21 days ago)
+ InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
+ NonfreeKernelModules: wl
+ Package: linux (not installed)
+ Tags:  xenial
+ Uname: Linux 4.6.0-040600-generic i686
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown

Status in linux package in Ubuntu:
  Incomplete

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

  Have changed /etc/default/grub to attempt a fix without success...
  (grub.ref was original grub)

  :/etc/default$ grep CMDLINE grub*

  grub.ref:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  grub.ref:GRUB_CMDLINE_LINUX="forcepae"

  grub:GRUB_CMDLINE_LINUX_DEFAULT="acpi=noirq debug=y"
  grub:GRUB_CMDLINE_LINUX="forcepae"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  Uname: Linux 4.6.0-040600-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  6 18:16:30 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  NonfreeKernelModules: wl
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.6.0-040600-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1620811] Re: Focaltech touchpad detected as mouse on Asus K501UW laptop

2016-09-06 Thread Egor

** Attachment added: "xinput --list"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620811/+attachment/4735748/+files/xinput%20--list

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

Title:
  Focaltech touchpad detected as mouse on Asus K501UW laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following the bug reporting documentation here:
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

  The Focaltech touchpad on Asus K501UW laptop is detected as a mouse,
  so I can't access touchpad features such as two-finger scrolling or
  use two-finger tap as right mouse button. The touchpad is recognized
  in xinput-list as "FTE1001:00 0B05:0101".

  The bug appears in Ubuntu Mate 16.04.1 x64 and Linux Mint 18 Cinnamon
  x64, both with kernel 4.4.0-31. I've also tried Linux Mint 17.3 x64
  with kernel 3.19, and there the touchpad does not work at all (does
  not function even as a mouse).

  The bug is resemblant of #1372609.

  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:  e2 3605 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Sep  6 15:13:50 2016
  HibernationDevice: RESUME=UUID=8407ca60-029d-4be6-ab12-a2f1aee1d843
  InstallationDate: Installed on 2016-09-05 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=826cac6a-2d18-4d8d-a9ee-85299d3cac91 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.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UW.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UW
  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.:bvrK501UW.203:bd03/30/2016:svnASUSTeKCOMPUTERINC.:pnK501UW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K501UW
  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/1620811/+subscriptions

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

[Kernel-packages] [Bug 1620811] 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/1620811

Title:
  Focaltech touchpad detected as mouse on Asus K501UW laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following the bug reporting documentation here:
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

  The Focaltech touchpad on Asus K501UW laptop is detected as a mouse,
  so I can't access touchpad features such as two-finger scrolling or
  use two-finger tap as right mouse button. The touchpad is recognized
  in xinput-list as "FTE1001:00 0B05:0101".

  The bug appears in Ubuntu Mate 16.04.1 x64 and Linux Mint 18 Cinnamon
  x64, both with kernel 4.4.0-31. I've also tried Linux Mint 17.3 x64
  with kernel 3.19, and there the touchpad does not work at all (does
  not function even as a mouse).

  The bug is resemblant of #1372609.

  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:  e2 3605 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Sep  6 15:13:50 2016
  HibernationDevice: RESUME=UUID=8407ca60-029d-4be6-ab12-a2f1aee1d843
  InstallationDate: Installed on 2016-09-05 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=826cac6a-2d18-4d8d-a9ee-85299d3cac91 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.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UW.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UW
  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.:bvrK501UW.203:bd03/30/2016:svnASUSTeKCOMPUTERINC.:pnK501UW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K501UW
  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/1620811/+subscriptions

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

[Kernel-packages] [Bug 1620811] Re: Focaltech touchpad detected as mouse on Asus K501UW laptop

2016-09-06 Thread Egor

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620811/+attachment/4735749/+files/Xorg.0.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/1620811

Title:
  Focaltech touchpad detected as mouse on Asus K501UW laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following the bug reporting documentation here:
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

  The Focaltech touchpad on Asus K501UW laptop is detected as a mouse,
  so I can't access touchpad features such as two-finger scrolling or
  use two-finger tap as right mouse button. The touchpad is recognized
  in xinput-list as "FTE1001:00 0B05:0101".

  The bug appears in Ubuntu Mate 16.04.1 x64 and Linux Mint 18 Cinnamon
  x64, both with kernel 4.4.0-31. I've also tried Linux Mint 17.3 x64
  with kernel 3.19, and there the touchpad does not work at all (does
  not function even as a mouse).

  The bug is resemblant of #1372609.

  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:  e2 3605 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Sep  6 15:13:50 2016
  HibernationDevice: RESUME=UUID=8407ca60-029d-4be6-ab12-a2f1aee1d843
  InstallationDate: Installed on 2016-09-05 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=826cac6a-2d18-4d8d-a9ee-85299d3cac91 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.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UW.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UW
  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.:bvrK501UW.203:bd03/30/2016:svnASUSTeKCOMPUTERINC.:pnK501UW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K501UW
  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/1620811/+subscriptions

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

[Kernel-packages] [Bug 1620811] [NEW] Focaltech touchpad detected as mouse on Asus K501UW laptop

2016-09-06 Thread Egor

Public bug reported:

Following the bug reporting documentation here:
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

The Focaltech touchpad on Asus K501UW laptop is detected as a mouse, so
I can't access touchpad features such as two-finger scrolling or use
two-finger tap as right mouse button. The touchpad is recognized in
xinput-list as "FTE1001:00 0B05:0101".

The bug appears in Ubuntu Mate 16.04.1 x64 and Linux Mint 18 Cinnamon
x64, both with kernel 4.4.0-31. I've also tried Linux Mint 17.3 x64 with
kernel 3.19, and there the touchpad does not work at all (does not
function even as a mouse).

The bug is resemblant of #1372609.

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:  e2 3605 F pulseaudio
CurrentDesktop: MATE
Date: Tue Sep  6 15:13:50 2016
HibernationDevice: RESUME=UUID=8407ca60-029d-4be6-ab12-a2f1aee1d843
InstallationDate: Installed on 2016-09-05 (1 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 0bda:57ed Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. K501UW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=826cac6a-2d18-4d8d-a9ee-85299d3cac91 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.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/30/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K501UW.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K501UW
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.:bvrK501UW.203:bd03/30/2016:svnASUSTeKCOMPUTERINC.:pnK501UW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K501UW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug focaltech touchpad xenial

** Attachment added: "devices"
   https://bugs.launchpad.net/bugs/1620811/+attachment/4735732/+files/devices

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

Title:
  Focaltech touchpad detected as mouse on Asus K501UW laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following the bug reporting documentation here:
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

  The Focaltech touchpad on Asus K501UW laptop is detected as a mouse,
  so I can't access touchpad features such as two-finger scrolling or
  use two-finger tap as right mouse button. The touchpad is recognized
  in xinput-list as "FTE1001:00 0B05:0101".

  The bug appears in Ubuntu Mate 16.04.1 x64 and Linux Mint 18 Cinnamon
  x64, both with kernel 4.4.0-31. I've also tried Linux Mint 17.3 x64
  with kernel 3.19, and there the touchpad does not work at all (does
  not function even as a mouse).

  The bug is resemblant of #1372609.

  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:  e2 3605 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Sep  6 15:13:50 2016
  HibernationDevice: RESUME=UUID=8407ca60-029d-4be6-ab12-a2f1aee1d843
  InstallationDate: Installed on 2016-09-05 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux

[Kernel-packages] [Bug 1620317] Re: ISST-LTE:pNV: system ben is hung during ST (nvme)

Merged in v4.8

** Also affects: linux (Ubuntu Yakkety)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Triaged

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

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

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

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

Title:
  ISST-LTE:pNV: system ben is hung during ST (nvme)

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

Bug description:
  On when we are running I/O intensive tasks and CPU addition/removal,
  the block may hang stalling the entire machine.

  The backtrace below is one of the symptoms:

  [12747.49] ---[ end trace b4d8d720952460b5 ]---
  [12747.126885] Trying to free IRQ 357 from IRQ context!
  [12747.146930] [ cut here ]
  [12747.166674] WARNING: at 
/build/linux-iLHNl3/linux-4.4.0/kernel/irq/manage.c:1438
  [12747.184069] Modules linked in: minix nls_iso8859_1 rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) binfmt_misc xfs joydev input_leds mac_hid ofpart cmdlinepart 
powernv_flash ipmi_powernv mtd ipmi_msghandler at24 opal_prd powernv_rng 
ibmpowernv uio_pdrv_genirq uio sunrpc knem(OE) autofs4 btrfs xor raid6_pq 
hid_generic usbhid hid uas usb_storage nouveau ast bnx2x i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx5_core(OE) ahci 
drm mdio libcrc32c mlx_compat(OE) libahci vxlan nvme ip6_udp_tunnel udp_tunnel
  [12747.349013] CPU: 80 PID: 0 Comm: swapper/80 Tainted: GW  OEL  
4.4.0-21-generic #37-Ubuntu
  [12747.369046] task: c00f1fab89b0 ti: c00f1fb6c000 task.ti: 
c00f1fb6c000
  [12747.404848] NIP: c0131888 LR: c0131884 CTR: 
300303f0
  [12747.808333] REGS: c00f1fb6e550 TRAP: 0700   Tainted: GW  OEL   
(4.4.0-21-generic)
  [12747.867658] MSR: 900100029033   CR: 2802  
XER: 2000
  [12747.884783] CFAR: c0aea8f4 SOFTE: 1 
  GPR00: c0131884 c00f1fb6e7d0 c15b4200 0028 
  GPR04: c00f2a409c50 c00f2a41b4e0 000f2948 33da 
  GPR08: 0007 c0f8b27c 000f2948 90011003 
  GPR12: 2200 c7b6f800 c00f2a40a938 0100 
  GPR16: c00f1148 3a98   
  GPR20:  d9521008 d95146a0 f000 
  GPR24: c4a19ef0  0003 007d 
  GPR28: 0165 c00eefeb1800 c00eef830600 0165 
  [12748.243270] NIP [c0131888] __free_irq+0x238/0x370
  [12748.254089] LR [c0131884] __free_irq+0x234/0x370
  [12748.269738] Call Trace:
  [12748.286740] [c00f1fb6e7d0] [c0131884] __free_irq+0x234/0x370 
(unreliable)
  [12748.289687] [c00f1fb6e860] [c0131af8] free_irq+0x88/0xb0
  [12748.304594] [c00f1fb6e890] [d9514528] 
nvme_suspend_queue+0xc8/0x150 [nvme]
  [12748.333825] [c00f1fb6e8c0] [d951681c] 
nvme_dev_disable+0x3fc/0x400 [nvme]
  [12748.340913] [c00f1fb6e9a0] [d9516ae4] nvme_timeout+0xe4/0x260 
[nvme]
  [12748.357136] [c00f1fb6ea60] [c0548a34] 
blk_mq_rq_timed_out+0x64/0x110
  [12748.383939] [c00f1fb6ead0] [c054c540] bt_for_each+0x160/0x170
  [12748.399292] [c00f1fb6eb40] [c054d4e8] 
blk_mq_queue_tag_busy_iter+0x78/0x110
  [12748.402665] [c00f1fb6eb90] [c0547358] 
blk_mq_rq_timer+0x48/0x140
  [12748.438649] [c00f1fb6ebd0] [c014a13c] call_timer_fn+0x5c/0x1c0
  [12748.468126] [c00f1fb6ec60] [c014a5fc] 
run_timer_softirq+0x31c/0x3f0
  [12748.483367] [c00f1fb6ed30] [c00beb78] __do_softirq+0x188/0x3e0
  [12748.498378] [c00f1fb6ee20] [c00bf048] irq_exit+0xc8/0x100
  [12748.501048] [c00f1fb6ee40] [c001f954] timer_interrupt+0xa4/0xe0
  [12748.516377] [c00f1fb6ee70] [c0002714] 
decrementer_common+0x114/0x180
  [12748.547282] --- interrupt: 901 at arch_local_irq_restore+0x74/0x90
  [12748.547282] LR = arch_local_irq_restore+0x74/0x90
  [12748.574141] [c00f1fb6f160] [0001] 0x1 (unreliable)
  [12748.592405]

[Kernel-packages] [Bug 1620317] Re: ISST-LTE:pNV: system ben is hung during ST (nvme)

https://lists.ubuntu.com/archives/kernel-team/2016-September/079898.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/1620317

Title:
  ISST-LTE:pNV: system ben is hung during ST (nvme)

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

Bug description:
  On when we are running I/O intensive tasks and CPU addition/removal,
  the block may hang stalling the entire machine.

  The backtrace below is one of the symptoms:

  [12747.49] ---[ end trace b4d8d720952460b5 ]---
  [12747.126885] Trying to free IRQ 357 from IRQ context!
  [12747.146930] [ cut here ]
  [12747.166674] WARNING: at 
/build/linux-iLHNl3/linux-4.4.0/kernel/irq/manage.c:1438
  [12747.184069] Modules linked in: minix nls_iso8859_1 rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) binfmt_misc xfs joydev input_leds mac_hid ofpart cmdlinepart 
powernv_flash ipmi_powernv mtd ipmi_msghandler at24 opal_prd powernv_rng 
ibmpowernv uio_pdrv_genirq uio sunrpc knem(OE) autofs4 btrfs xor raid6_pq 
hid_generic usbhid hid uas usb_storage nouveau ast bnx2x i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx5_core(OE) ahci 
drm mdio libcrc32c mlx_compat(OE) libahci vxlan nvme ip6_udp_tunnel udp_tunnel
  [12747.349013] CPU: 80 PID: 0 Comm: swapper/80 Tainted: GW  OEL  
4.4.0-21-generic #37-Ubuntu
  [12747.369046] task: c00f1fab89b0 ti: c00f1fb6c000 task.ti: 
c00f1fb6c000
  [12747.404848] NIP: c0131888 LR: c0131884 CTR: 
300303f0
  [12747.808333] REGS: c00f1fb6e550 TRAP: 0700   Tainted: GW  OEL   
(4.4.0-21-generic)
  [12747.867658] MSR: 900100029033   CR: 2802  
XER: 2000
  [12747.884783] CFAR: c0aea8f4 SOFTE: 1 
  GPR00: c0131884 c00f1fb6e7d0 c15b4200 0028 
  GPR04: c00f2a409c50 c00f2a41b4e0 000f2948 33da 
  GPR08: 0007 c0f8b27c 000f2948 90011003 
  GPR12: 2200 c7b6f800 c00f2a40a938 0100 
  GPR16: c00f1148 3a98   
  GPR20:  d9521008 d95146a0 f000 
  GPR24: c4a19ef0  0003 007d 
  GPR28: 0165 c00eefeb1800 c00eef830600 0165 
  [12748.243270] NIP [c0131888] __free_irq+0x238/0x370
  [12748.254089] LR [c0131884] __free_irq+0x234/0x370
  [12748.269738] Call Trace:
  [12748.286740] [c00f1fb6e7d0] [c0131884] __free_irq+0x234/0x370 
(unreliable)
  [12748.289687] [c00f1fb6e860] [c0131af8] free_irq+0x88/0xb0
  [12748.304594] [c00f1fb6e890] [d9514528] 
nvme_suspend_queue+0xc8/0x150 [nvme]
  [12748.333825] [c00f1fb6e8c0] [d951681c] 
nvme_dev_disable+0x3fc/0x400 [nvme]
  [12748.340913] [c00f1fb6e9a0] [d9516ae4] nvme_timeout+0xe4/0x260 
[nvme]
  [12748.357136] [c00f1fb6ea60] [c0548a34] 
blk_mq_rq_timed_out+0x64/0x110
  [12748.383939] [c00f1fb6ead0] [c054c540] bt_for_each+0x160/0x170
  [12748.399292] [c00f1fb6eb40] [c054d4e8] 
blk_mq_queue_tag_busy_iter+0x78/0x110
  [12748.402665] [c00f1fb6eb90] [c0547358] 
blk_mq_rq_timer+0x48/0x140
  [12748.438649] [c00f1fb6ebd0] [c014a13c] call_timer_fn+0x5c/0x1c0
  [12748.468126] [c00f1fb6ec60] [c014a5fc] 
run_timer_softirq+0x31c/0x3f0
  [12748.483367] [c00f1fb6ed30] [c00beb78] __do_softirq+0x188/0x3e0
  [12748.498378] [c00f1fb6ee20] [c00bf048] irq_exit+0xc8/0x100
  [12748.501048] [c00f1fb6ee40] [c001f954] timer_interrupt+0xa4/0xe0
  [12748.516377] [c00f1fb6ee70] [c0002714] 
decrementer_common+0x114/0x180
  [12748.547282] --- interrupt: 901 at arch_local_irq_restore+0x74/0x90
  [12748.547282] LR = arch_local_irq_restore+0x74/0x90
  [12748.574141] [c00f1fb6f160] [0001] 0x1 (unreliable)
  [12748.592405] [c00f1fb6f180] [c0aedc3c] dump_stack+0xd0/0xf0
  [12748.596461] [c00f1fb6f1c0] [c01006fc] 
dequeue_task_idle+0x5c/0x90
  [12748.611532] [c00f1fb6f230] [c00f6080] 
deactivate_task+0xc0/0x130
  [12748.627685] [c00f1fb6f270] [c0adcb10] __schedule+0x440/0x990
  [12748.654416] [c00f1fb6f300] [c0add0a8] schedule+0x48/0xc0
  [12748.670558] [c00f1fb6f330] [c0ae1474] 
schedule_timeout+0x274/0x350
  [12748.673485] [c00f1fb6f420] [c0ade23c]

[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Test kernel at http://people.canonical.com/~rtg/lsattr-lp1619918/

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  In Progress
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  In Progress
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Kernel-packages] [Bug 1611081] Re: [HP Pavilion x2 - 12-b003nf (ENERGY STAR)] Synaptics touchpad not configured by HID RMI

2016-09-06 Thread GreenSkol

Hi,
Problem has been reported, I'm waiting for my email to appear on the mailing 
list archive.
As kernel 4.8.0rc5 is now available, I've tested & filed the bug against this 
kernel.

FYI, it seems that Andrew Duggan is not in the list of maintainers of the hid 
module (I couldn't find his address):
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/MAINTAINERS#n5511

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

Title:
  [HP Pavilion x2 - 12-b003nf (ENERGY STAR)] Synaptics touchpad not
  configured by HID RMI

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  The touchpad on the HP Pavilion X2 is not configured properly by
  hid_rmi and therefore is not detected at all later on by Xorg.

  The following can be seen in kern.log:

  Aug  8 20:11:45 X2 kernel: [4.201783] hid-rmi 0003:06CB:7D29.0001: 
Scanning PDT...
  Aug  8 20:11:45 X2 kernel: [4.203792] hid-rmi 0003:06CB:7D29.0001: Found 
F34 on page 0x00
  Aug  8 20:11:45 X2 kernel: [4.211498] hid-rmi 0003:06CB:7D29.0001: Found 
F01 on page 0x00
  Aug  8 20:11:45 X2 kernel: [4.213905] hid-rmi 0003:06CB:7D29.0001: Found 
F12 on page 0x00
  Aug  8 20:11:45 X2 kernel: [4.218779] hid-rmi 0003:06CB:7D29.0001: Found 
F54 on page 0x01
  Aug  8 20:11:45 X2 kernel: [4.224524] hid-rmi 0003:06CB:7D29.0001: Found 
F30 on page 0x02
  Aug  8 20:11:45 X2 kernel: [4.229785] hid-rmi 0003:06CB:7D29.0001: Found 
F55 on page 0x03
  Aug  8 20:11:45 X2 kernel: [4.235778] hid-rmi 0003:06CB:7D29.0001: Found 
F51 on page 0x04
  Aug  8 20:11:45 X2 kernel: [4.240853] hid-rmi 0003:06CB:7D29.0001: 
rmi_scan_pdt: Done with PDT scan.
  Aug  8 20:11:45 X2 kernel: [4.254044] hid-rmi 0003:06CB:7D29.0001: No 2D 
sensor found, giving up.
  Aug  8 20:11:45 X2 kernel: [4.254052] hid-rmi 0003:06CB:7D29.0001: Error 
while initializing F11 (-19).
  Aug  8 20:11:45 X2 kernel: [4.260475] hid-rmi 0003:06CB:7D29.0001: 
hiddev0,hidraw2: USB HID v1.11 Mouse [SYNAPTICS Synaptics HIDUSB TouchPad V03] 
on usb-:00:14.0-2.1/input0
  Aug  8 20:11:45 X2 kernel: [4.260482] hid-rmi 0003:06CB:7D29.0001: Device 
failed to be properly configured

  
  I'll attach dmesg, devices & xOrg log to this bug.

  Workaround: touchpad can be detected by hid_generic if blacklisting hid_rmi 
but is then lacking scrolling/multi-touch functionalities.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  greenskol   3454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=bd8f9fbe-28b6-433f-9543-894034b9586d
  InstallationDate: Installed on 2016-08-02 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion x2 Detachable
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=8455b162-d9c3-4f18-92b8-7b88707ecbba 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/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.04
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8181
  dmi.board.vendor: HP
  dmi.board.version: 42.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.04:bd11/27/2015:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1619766] Re: Backport E3 Skylake Support in ie31200_edac to Xenial

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  Backport E3 Skylake Support in ie31200_edac to Xenial

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Skylake E3 Support was added to ie31200_edac with the following commit:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/edac/ie31200_edac.c?id=953dee9bbd245f5515173126b9cc8b1a2c340797

  Could we get this support backported to Xenial?

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

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

[Kernel-packages] [Bug 1618572] Re: apt-key add fails in overlayfs

** Changed in: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1618572

Title:
  apt-key add fails in overlayfs

Status in cloud-init:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Sending a custom APT config to cloud-init fails to:
  1. add keys
  2. configure sources
  3. configura additional repository.

  The same config is being sent to curtin, and curtin doesn't seem to
  fail (curtin install log http://paste.ubuntu.com/23112826/ just in
  case).

  config sent by maas = http://pastebin.ubuntu.com/23112834/
  cloud-init.log = http://paste.ubuntu.com/23112820/
  cloud-init-output.log = http://paste.ubuntu.com/23112822/
  sources.list = http://paste.ubuntu.com/23112824/
  ubuntu@node03:/var/log$ ls -l /etc/apt/sources.list.d/
  total 0

  
  ubuntu@node03:/var/log$ sudo apt-get update
  Hit:2 http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease
  Get:3 http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease [92.2 
kB]
  Err:2 http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  Ign:3 http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease
  Hit:4 http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease
  Get:1 http://us.archive.ubuntu.com/ubuntu yakkety InRelease [247 kB]
  Err:4 http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  Err:1 http://us.archive.ubuntu.com/ubuntu yakkety InRelease
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  Fetched 339 kB in 0s (388 kB/s)
  Reading package lists... Error!
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: GPG error: http://us.archive.ubuntu.com/ubuntu yakkety-backports 
InRelease: The following signatures couldn't be verified because the public key 
is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: The repository 'http://us.archive.ubuntu.com/ubuntu yakkety-backports 
InRelease' is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://us.archive.ubuntu.com/ubuntu yakkety InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/dists/yakkety/InRelease  The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/dists/yakkety-updates/InRelease  The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/dists/yakkety-security/InRelease  The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.
  E: Problem renaming the file /var/cache/apt/srcpkgcache.bin.3HKvbX to 
/var/cache/apt/srcpkgcache.bin - rename (116: Stale file handle)
  E: Problem renaming the file /var/cache/apt/pkgcache.bin.d0JUHJ to 
/var/cache/apt/pkgcache.bin - rename (116: Stale file handle)
  W: You may want to run apt-get update to correct these problems
  E: The package cache file is corrupted

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

-- 
Mailing

[Kernel-packages] [Bug 1572025] Re: Regression for mmap writes through FUSE in 4.2+

commit 74d369443325063a5f0260e63971decb950fd8fa ('writeback: Fix
performance regression in wb_over_bg_thresh()') was released in
Ubuntu-4.4.0-23.41

** Changed in: linux (Ubuntu)
   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/1572025

Title:
  Regression for mmap writes through FUSE in 4.2+

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I apologize for being brief but all necessary details are behind the
  links below.

  Report:
  http://thread.gmane.org/gmane.linux.kernel/2132944

  Discussion:
  https://lkml.org/lkml/2016/3/16/260

  Patch:
  [writeback: Fix performance regression in wb_over_bg_thresh()]
  https://lkml.org/lkml/2016/3/10/21

  Patch was tested by Jakob Unterwurzacher and seems to have fixed the issue.
  Reverting to 3.13 or 3.19 works around the issue on 14.04.

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

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

[Kernel-packages] [Bug 1608854] Re: [arm64] nova instances can't boot with 3.13.0-92

2016-09-06 Thread dann frazier

** Attachment added: "dmesg-verified.out"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608854/+attachment/4735728/+files/dmesg-verified.out

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

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

Title:
  [arm64] nova instances can't boot with 3.13.0-92

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  New
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  Hi,

  It would appear that arm64 nova instances can't boot on 3.13.0-92.

  The serial console displays :

  error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB 
enabled.
  unaligned pointer 0xb90002e058000c57
  Aborted. Press any key to exit.

  I suspect this is due to LP#1566221, more specifically :
 * [Config] CONFIG_EFI=n for arm64

  This is pretty serious. I'm not 100% sure the above is the cause, but
  if so, it should be reverted asap.

  Thank you.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [   27.314355] random: nonblocking pool is initialized
   [   43.711734] init: jenkins-slave main process (1169) terminated with 
status 143
  DistroRelease: Ubuntu 14.04
  Ec2AMI: ami-08ce
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.medium
  Ec2Kernel: None
  Ec2Ramdisk: None
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty ec2-images
  Uname: Linux 3.13.0-85-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1618039] Re: linux: 3.2.0-110.151 -proposed tracker

USN needed

** Changed in: kernel-sru-workflow/security-signoff
   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/1618039

Title:
  linux: 3.2.0-110.151 -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-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1618039/+subscriptions

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

[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Commit 02da2d72174c61988eb4456b53f405e3ebdebce4 merged in v4.7

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

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

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

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

** Also affects: e2fsprogs (Ubuntu Yakkety)
   Importance: Undecided
   Status: Invalid

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  In Progress
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  In Progress
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Kernel-packages] [Bug 1585329] Re: Sometimes a black rectangle appears briefly under the mouse cursor

2016-09-06 Thread Bruno Nova

OK, I'll try, but I can't promise anything.

But I must say, after I removed and reinstalled the NVidia driver through 
software-properties-gtk, Ubuntu has shut down or completely frozen several 
times.
I'm going to "autoremove --purge" the driver and reinstall it to see if that 
stops this.

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

Title:
  Sometimes a black rectangle appears briefly under the mouse cursor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm on 16.04, using a laptop with Nvidia Optimus (Nvidia driver installed, 
Intel card selected).
  The problem also occurs in a guest session.
  It didn't occur in 14.04.

  Sometimes I see a black rectangle appear for a very brief moment (a flash).
  Horizontally, the rectangle occupies the whole screen.
  Vertically, the rectangle seems to start in the mouse cursor and ends in the 
bottom of the screen.

  The easiest way to reproduce the bug is to open a Gnome terminal, move
  the mouse cursor inside the window and press Alt+Backspace repeatedly.

  WORKAROUND: Switch to the nvidia card.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May 24 19:44:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics 
Controller [1025:0488]
   NVIDIA Corporation GF108M [GeForce GT 420M] [10de:0df1] (rev ff) (prog-if ff)
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'hsize' b'2'
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'compiztoolbox', 'imgpng', 'snap', 'titleinfo', 'grid', 'vpswitch', 'move', 
'regex', 'copytex', 'place', 'mousepoll', 'session', 'commands', 'wall', 
'resize', 'winrules', 'dbus', 'unitymtgrabhandles', 'animation', 'expo', 
'ezoom', 'fade', 'workarounds', 'scale', 'unityshell']"
   b'org.compiz.core' b'vsize' b'2'
   b'org.compiz.core' b'focus-prevention-level' b'0'
  InstallationDate: Installed on 2016-04-25 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines 
E730, Acer sub-brand)
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire 5742G
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=UUID=68a53fa4-4cfc-45bc-84de-762947ea37e1 ro locale=pt_PT quiet splash
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5742G
  dmi.board.vendor: Acer
  dmi.board.version: V1.30
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.30
  dmi.modalias: 
dmi:bvnAcer:bvrV1.30:bd08/13/2012:svnAcer:pnAspire5742G:pvrV1.30:rvnAcer:rnAspire5742G:rvrV1.30:cvnAcer:ct10:cvrV1.30:
  dmi.product.name: Aspire 5742G
  dmi.product.version: V1.30
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue May 24 19:18:29 2016
  xserver.configfile: default
  xserver.errors:

[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

https://lists.ubuntu.com/archives/kernel-team/2016-September/079897.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/1619918

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  In Progress
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  In Progress
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Kernel-packages] [Bug 1620317] Re: ISST-LTE:pNV: system ben is hung during ST (nvme)

2016-09-06 Thread Leann Ogasawara

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

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

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1620317

Title:
  ISST-LTE:pNV: system ben is hung during ST (nvme)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  On when we are running I/O intensive tasks and CPU addition/removal,
  the block may hang stalling the entire machine.

  The backtrace below is one of the symptoms:

  [12747.49] ---[ end trace b4d8d720952460b5 ]---
  [12747.126885] Trying to free IRQ 357 from IRQ context!
  [12747.146930] [ cut here ]
  [12747.166674] WARNING: at 
/build/linux-iLHNl3/linux-4.4.0/kernel/irq/manage.c:1438
  [12747.184069] Modules linked in: minix nls_iso8859_1 rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) binfmt_misc xfs joydev input_leds mac_hid ofpart cmdlinepart 
powernv_flash ipmi_powernv mtd ipmi_msghandler at24 opal_prd powernv_rng 
ibmpowernv uio_pdrv_genirq uio sunrpc knem(OE) autofs4 btrfs xor raid6_pq 
hid_generic usbhid hid uas usb_storage nouveau ast bnx2x i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx5_core(OE) ahci 
drm mdio libcrc32c mlx_compat(OE) libahci vxlan nvme ip6_udp_tunnel udp_tunnel
  [12747.349013] CPU: 80 PID: 0 Comm: swapper/80 Tainted: GW  OEL  
4.4.0-21-generic #37-Ubuntu
  [12747.369046] task: c00f1fab89b0 ti: c00f1fb6c000 task.ti: 
c00f1fb6c000
  [12747.404848] NIP: c0131888 LR: c0131884 CTR: 
300303f0
  [12747.808333] REGS: c00f1fb6e550 TRAP: 0700   Tainted: GW  OEL   
(4.4.0-21-generic)
  [12747.867658] MSR: 900100029033   CR: 2802  
XER: 2000
  [12747.884783] CFAR: c0aea8f4 SOFTE: 1 
  GPR00: c0131884 c00f1fb6e7d0 c15b4200 0028 
  GPR04: c00f2a409c50 c00f2a41b4e0 000f2948 33da 
  GPR08: 0007 c0f8b27c 000f2948 90011003 
  GPR12: 2200 c7b6f800 c00f2a40a938 0100 
  GPR16: c00f1148 3a98   
  GPR20:  d9521008 d95146a0 f000 
  GPR24: c4a19ef0  0003 007d 
  GPR28: 0165 c00eefeb1800 c00eef830600 0165 
  [12748.243270] NIP [c0131888] __free_irq+0x238/0x370
  [12748.254089] LR [c0131884] __free_irq+0x234/0x370
  [12748.269738] Call Trace:
  [12748.286740] [c00f1fb6e7d0] [c0131884] __free_irq+0x234/0x370 
(unreliable)
  [12748.289687] [c00f1fb6e860] [c0131af8] free_irq+0x88/0xb0
  [12748.304594] [c00f1fb6e890] [d9514528] 
nvme_suspend_queue+0xc8/0x150 [nvme]
  [12748.333825] [c00f1fb6e8c0] [d951681c] 
nvme_dev_disable+0x3fc/0x400 [nvme]
  [12748.340913] [c00f1fb6e9a0] [d9516ae4] nvme_timeout+0xe4/0x260 
[nvme]
  [12748.357136] [c00f1fb6ea60] [c0548a34] 
blk_mq_rq_timed_out+0x64/0x110
  [12748.383939] [c00f1fb6ead0] [c054c540] bt_for_each+0x160/0x170
  [12748.399292] [c00f1fb6eb40] [c054d4e8] 
blk_mq_queue_tag_busy_iter+0x78/0x110
  [12748.402665] [c00f1fb6eb90] [c0547358] 
blk_mq_rq_timer+0x48/0x140
  [12748.438649] [c00f1fb6ebd0] [c014a13c] call_timer_fn+0x5c/0x1c0
  [12748.468126] [c00f1fb6ec60] [c014a5fc] 
run_timer_softirq+0x31c/0x3f0
  [12748.483367] [c00f1fb6ed30] [c00beb78] __do_softirq+0x188/0x3e0
  [12748.498378] [c00f1fb6ee20] [c00bf048] irq_exit+0xc8/0x100
  [12748.501048] [c00f1fb6ee40] [c001f954] timer_interrupt+0xa4/0xe0
  [12748.516377] [c00f1fb6ee70] [c0002714] 
decrementer_common+0x114/0x180
  [12748.547282] --- interrupt: 901 at arch_local_irq_restore+0x74/0x90
  [12748.547282] LR = arch_local_irq_restore+0x74/0x90
  [12748.574141] [c00f1fb6f160] [0001] 0x1 (unreliable)
  [12748.592405] [c00f1fb6f180] [c0aedc3c] dump_stack+0xd0/0xf0
  [12748.596461] [c00f1fb6f1c0] [c01006fc] 
dequeue_task_idle+0x5c/0x90
  [12748.611532] [c00f1fb6f230] [c00f6080] 
deactivate_task+0xc0/0x130
  [12748.627685] [c00f1fb6f270] [c0adcb10] __schedule+0x440/0x990
  [12748.654416] [c00f1fb6f300] [c0add0a8] schedule+0x48/0xc0
  [12748.670558]

[Kernel-packages] [Bug 1620741] Re: Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc5


** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown

Status in linux package in Ubuntu:
  Incomplete

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

  Have changed /etc/default/grub to attempt a fix without success...
  (grub.ref was original grub)

  :/etc/default$ grep CMDLINE grub*

  grub.ref:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  grub.ref:GRUB_CMDLINE_LINUX="forcepae"

  grub:GRUB_CMDLINE_LINUX_DEFAULT="acpi=noirq debug=y"
  grub:GRUB_CMDLINE_LINUX="forcepae"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  Uname: Linux 4.6.0-040600-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  6 18:16:30 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1620733] Re: Xubuntu 16.04 on HP Compaq nx6325 freezes on Suspend

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc5


** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Xubuntu 16.04 on HP Compaq nx6325 freezes on Suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On suspend mouse movement stops.

  andymc@mvac21:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Suspend freezes in Kernel linux-headers-4.4.0-36 and linux-
  headers-4.6.0-040600

  Only way out is hold down power button for about 6 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  Uname: Linux 4.6.0-040600-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  6 17:55:49 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1619552] Re: Failed to acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or directory)

merged in 4.8-rc5

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

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

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

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

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

Title:
  Failed to acknowledge elog:
  /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or
  directory)

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

Bug description:
  == Comment: #0 - Mukesh K. Ojha  - 2016-09-02 02:10:14 ==
  ---Problem Description---
  Kernel is failed to free the kobject while acknowledging the error log which 
has been notified two times.
   
  Contact Information = Contact Information =  mukeo...@in.ibm.com 
   
  ---uname output---
  Ubuntu 16.04.01 LTS
   
  Machine Type = All power machine 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   
  Steps to reproduce:
  1.Boot the system to petitboot.
  2. Issue FSP Soft reset of Service Processor From ASMI page.
  3. After FSP comes up, boot the system to host OS.
  4. In the host OS seen the failure to acknowledge for one of elog.

  
  root@p8wookie ~]# service opal_errd status
  Redirecting to /bin/systemctl status  opal_errd.service
  opal_errd.service - opal_errd (PowerNV platform error handling) Service
 Loaded: loaded (/usr/lib/systemd/system/opal_errd.service; enabled)
 Active: active (running) since Wed 2016-08-03 07:55:03 CDT; 2min 4s ago
Process: 3452 ExecStart=/usr/libexec/ppc64-diag/opal_errd start 
(code=exited, status=0/SUCCESS)
   Main PID: 3497 (opal_errd)
 CGroup: /system.slice/opal_errd.service
 ??3497 /usr/sbin/opal_errd

  Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)


  
  [root@p8wookie ~]# cd /sys/firmware/opal/elog/
  [root@p8wookie elog]# ls
  0x5018d709
  [root@p8wookie elog]# 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Contact Information =  mukeo...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Mukesh K. Ojha  - 2016-09-02 02:12:45 ==
  Upstream commit :

  commit a9cbf0b2195b695cbcaa4e2770948c212e9a
  Author: Mukesh Ojha 
  Date:   Mon Aug 22 12:17:44 2016 +0530

  powerpc/powernv : Drop reference added by kset_find_obj()
  
  In a situation, where Linux kernel gets notified about duplicate error log
  from OPAL, it is been observed that kernel fails to remove sysfs entries
  (/sys/firmware/opal/elog/0x) of such error logs. This is because,
  we currently search the error log/dump kobject in the kset list via
  'kset_find_obj()' routine. Which eventually increment the

[Kernel-packages] [Bug 1619552] Re: Failed to acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or directory)

https://lists.ubuntu.com/archives/kernel-team/2016-September/079896.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/1619552

Title:
  Failed to acknowledge elog:
  /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or
  directory)

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

Bug description:
  == Comment: #0 - Mukesh K. Ojha  - 2016-09-02 02:10:14 ==
  ---Problem Description---
  Kernel is failed to free the kobject while acknowledging the error log which 
has been notified two times.
   
  Contact Information = Contact Information =  mukeo...@in.ibm.com 
   
  ---uname output---
  Ubuntu 16.04.01 LTS
   
  Machine Type = All power machine 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   
  Steps to reproduce:
  1.Boot the system to petitboot.
  2. Issue FSP Soft reset of Service Processor From ASMI page.
  3. After FSP comes up, boot the system to host OS.
  4. In the host OS seen the failure to acknowledge for one of elog.

  
  root@p8wookie ~]# service opal_errd status
  Redirecting to /bin/systemctl status  opal_errd.service
  opal_errd.service - opal_errd (PowerNV platform error handling) Service
 Loaded: loaded (/usr/lib/systemd/system/opal_errd.service; enabled)
 Active: active (running) since Wed 2016-08-03 07:55:03 CDT; 2min 4s ago
Process: 3452 ExecStart=/usr/libexec/ppc64-diag/opal_errd start 
(code=exited, status=0/SUCCESS)
   Main PID: 3497 (opal_errd)
 CGroup: /system.slice/opal_errd.service
 ??3497 /usr/sbin/opal_errd

  Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)


  
  [root@p8wookie ~]# cd /sys/firmware/opal/elog/
  [root@p8wookie elog]# ls
  0x5018d709
  [root@p8wookie elog]# 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Contact Information =  mukeo...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Mukesh K. Ojha  - 2016-09-02 02:12:45 ==
  Upstream commit :

  commit a9cbf0b2195b695cbcaa4e2770948c212e9a
  Author: Mukesh Ojha 
  Date:   Mon Aug 22 12:17:44 2016 +0530

  powerpc/powernv : Drop reference added by kset_find_obj()
  
  In a situation, where Linux kernel gets notified about duplicate error log
  from OPAL, it is been observed that kernel fails to remove sysfs entries
  (/sys/firmware/opal/elog/0x) of such error logs. This is because,
  we currently search the error log/dump kobject in the kset list via
  'kset_find_obj()' routine. Which eventually increment the reference count
  by one, once it founds the kobject.

  
  Above patch is the solution of this bugzilla.

  Kindly pull this patch in for both Ubuntu 16.04 LTS and Ubuntu 16.10.

  -Mukesh

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

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

[Kernel-packages] [Bug 1620648] Re: Pairing bluetooth 0a12:0001 with Bose SoundLink II headphones fails

2016-09-06 Thread Jarno Suni

No luck with v4.8-rc5

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

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

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

Title:
  Pairing bluetooth 0a12:0001 with Bose SoundLink II headphones fails

Status in blueman package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I see the device in blueman-manager, but pairing fails. I could pair
  the dongle with another device. And I could pair the Bose device with
  another bluetooth device in Xubuntu 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jarnos 3069 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jarnos 3069 F...m pulseaudio
   /dev/snd/controlC0:  jarnos 3069 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Sep  6 17:01:49 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (131 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-36-generic 
root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  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/blueman/+bug/1620648/+subscriptions

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

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

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

apport-collect 1620741

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

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

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

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

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

Title:
  Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown

Status in linux package in Ubuntu:
  Incomplete

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

  Have changed /etc/default/grub to attempt a fix without success...
  (grub.ref was original grub)

  :/etc/default$ grep CMDLINE grub*

  grub.ref:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  grub.ref:GRUB_CMDLINE_LINUX="forcepae"

  grub:GRUB_CMDLINE_LINUX_DEFAULT="acpi=noirq debug=y"
  grub:GRUB_CMDLINE_LINUX="forcepae"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  Uname: Linux 4.6.0-040600-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  6 18:16:30 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

apport-collect 1620733

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

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

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

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

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

Title:
  Xubuntu 16.04 on HP Compaq nx6325 freezes on Suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On suspend mouse movement stops.

  andymc@mvac21:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Suspend freezes in Kernel linux-headers-4.4.0-36 and linux-
  headers-4.6.0-040600

  Only way out is hold down power button for about 6 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  Uname: Linux 4.6.0-040600-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  6 17:55:49 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-09-06 Thread harry

Same as before with this one:

>This one was broken but not in the same way. With this one, right
>after the PC booted it gets stuck in a console (only a blinking >cursor
in the upper left corner) right before plymouth is supposed to >load.

>The keyboard and everything else is unresponsive. I had to physically
>restart the computer.

I will say, maybe it's evident to everyone, but I keep seeing similar
messages in all broken kernels while installing:

>W: Possible missing firmware >/lib/firmware/i915/skl_dmc_ver4.bin for
module i915

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

Title:
  Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

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

Bug description:
  When I install Ubuntu 16.04 on my computer the screen goes blank at
  login. I can blindly login and it boots but I cannot use the display
  (external monitor through HDMI).

  I've looked online for an answer to this issue but could not find a
  solution.  However, many people report this issue in forums with the
  4.4x kernel.

  On my main computer, I upgraded from 14.04 to 16.04.1. On this
  computer I was able to switch back to the 3.13 kernel which *does
  work*.

  On the same computer, if I use a 16.04 live CD, it does the same
  thing.  The screen goes blank.

  UEFI may be part of the issue as well.  I have it disabled in bios
  (set to legacy mode) but when I first boot, it seems to go into UEFI
  mode first and then, after rebooting with  it shows
  me the list of kernels. I can select the kernel from there but if I
  use a 4.4x kernel, it blanks out at encryption passphrase screen.

  There are also people with similar issues on AskUbuntu.

  Here's some basic HW info.  If you require more, please ask.

  sudo lshw | head
  zbox
  description: Notebook
  product: ZBOX-ID18 (NA)
  vendor: ZOTAC
  version: XX
  serial: G211X
  width: 64 bits
  capabilities: smbios-2.7 dmi-2.7 vsyscall32
  configuration: boot=normal chassis=notebook family=NA sku=NA 
uuid=00020003-0004-0005-0006-000700080009
    *-core

  sudo lshw -C display
    *-display
     description: VGA compatible controller
     product: 3rd Gen Core processor Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 09
     width: 64 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:45 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

  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:  user5536 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38
  InstallationDate: Installed on 2014-07-23 (743 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  MachineType: ZOTAC ZBOX-ID18
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.157.2
  RfKill:

  StagingDrivers: rts5139
  Tags:  xenial staging
  Uname: Linux 3.13.0-92-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B211P011
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID18
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 10
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA:
  dmi.product.name: ZBOX-ID18
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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

[Kernel-packages] [Bug 1618299] Re: IPv6 with LVS Performance issue in latest 3.13LTS kernels

2016-09-06 Thread Marc Hasson

Thanks so much Joseph!  My apologies on not seeing this earlier that you
had a test kernel ready, I was offsite almost all of last week and
swamped.  Will download it now and test it later this evening or
tomorrow morning in my test rig.  By any chance, so as to aid my
systemtap monitoring, do you have a matching dbgsyms package for your
test kernel available?

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

Title:
  IPv6 with LVS Performance issue in latest 3.13LTS kernels

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

Bug description:
  We experienced a major performance regression between 12.04's 3.2 kernels
  and 14.04's 3.13 kernels when using IPv6 with the LVS load-balancing
  facility.  Through analysis of perf events and a workaround we've
  determined that an upstream fix is available which addresses the issue.
  Ubuntu has picked up the "IPv6: remove rt6i_genid" fix that appears to
  address our issue in their 3.16 and later kernels.  This was checked
  into the upstream 3.16 kernel back in late 2014.  This fix addressed an
  issue introduced by the (late 2012) "ipv6: use net->rt_genid to check dst
  validity", which is the source of our issue due to the mismatch between
  a dst/route instantiation's rt6i_genid and the IPv6 rt_genid field.

  Since we have drivers and other software tied to the 3.13 kernels in
  the field this report is requesting that the backport of that upstream
  fix be done to the 3.13 LTS kernels as well since we were planning on
  several more years for those deployed systems.  It seems relatively
  straight-forward.

  In our 3.13 kernel we used the "systemtap" facility in a test system
  to temporarily address the "obsolete" determination mistakenly made by
  the ip6_dst_check() function to check dst validity on behalf of the LVS
  (ip_vs) code.  By updating rt6i_genid to the current global value we were
  able to restore our test systems to the previous performance obtained
  with the 3.2 kernels.  But clearly we want the official upstream fix
  incorporated, which pulls the troublesome rt6i_genid field out altogether
  since its mishandling affected more than IPv6/LVS support based on the
  upstream mail threads.  Those were made in mid-2014 to the upstream
  kernel folks, such as a per-socket route caching issue.

  Note that the apport-bug collected info from a 3.13.0-87 system but we see the
  issue on all 3.13.0-xxx kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-87-generic 3.13.0-87.133
  ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-87-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marc   2433 F pulseaudio
  Date: Mon Aug 29 20:05:57 2016
  HibernationDevice: RESUME=UUID=c4187d86-ea40-4f53-af39-1b7e83964502
  InstallationDate: Installed on 2014-04-30 (852 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 001 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 001 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic 
root=UUID=92211e82-1c0b-42e6-bb12-0003b7f6db54 ro quiet splash 
crashkernel=384M-:128M
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-87-generic N/A
   linux-backports-modules-3.13.0-87-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  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:bd05/20/2014: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/1618299/+subscriptions

-- 
Mailing

[Kernel-packages] [Bug 1620733] Re: Xubuntu 16.04 on HP Compaq nx6325 freezes on Suspend

** Package changed: xfce4-panel (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/1620733

Title:
  Xubuntu 16.04 on HP Compaq nx6325 freezes on Suspend

Status in linux package in Ubuntu:
  New

Bug description:
  On suspend mouse movement stops.

  andymc@mvac21:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Suspend freezes in Kernel linux-headers-4.4.0-36 and linux-
  headers-4.6.0-040600

  Only way out is hold down power button for about 6 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  Uname: Linux 4.6.0-040600-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  6 17:55:49 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1620741] Re: Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown

Affects  shutdown from the main logout menu

** Package changed: xfce4-panel (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/1620741

Title:
  Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown

Status in linux package in Ubuntu:
  New

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

  Have changed /etc/default/grub to attempt a fix without success...
  (grub.ref was original grub)

  :/etc/default$ grep CMDLINE grub*

  grub.ref:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  grub.ref:GRUB_CMDLINE_LINUX="forcepae"

  grub:GRUB_CMDLINE_LINUX_DEFAULT="acpi=noirq debug=y"
  grub:GRUB_CMDLINE_LINUX="forcepae"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xfce4-panel 4.12.0-3ubuntu2
  Uname: Linux 4.6.0-040600-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  6 18:16:30 2016
  ExecutablePath: /usr/bin/xfce4-panel
  InstallationDate: Installed on 2016-08-16 (21 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1608652] Re: [Ubuntu 16.04] FCoE Lun not visible in OS with inbox driver - Issue with ioremap() call on 32bit kernel

2016-09-06 Thread Dick Kennedy

Are you waiting for me to verify this?

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

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

Title:
  [Ubuntu 16.04] FCoE Lun not visible in OS with inbox driver - Issue
  with ioremap() call on 32bit kernel

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:
  Broadcom has a fix for this issue that it will be sending upstream
  on/by  8/15/16


  BUG REPRODUCTION DETAILS  
  Test Case Instance- 
  Reproducibility of Bug- Always
  Last Known Working Build  - NA
  Time to Reproduce Bug - 5 Minutes
  Steps To Reproduce Bug- 
  ==
  1. Map a LUN and make sure the FCoE Lun is visible in the UEFI/ as well as
  Legacy BIOS
  2. Boot to OS, and check "fdisk -l" the Lun is not listed.

  Logs
  

  ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ modinfo lpfc|grep -i version
  version:0:11.0.0.10.
  srcversion: 77EBC3EEDF32DABDDF14B7F
  vermagic:   4.4.0-22-generic SMP mod_unload modversions 686

  
  ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ lsmod|grep lpfc
  lpfc  614400  0
  scsi_transport_fc  57344  1 lpfc

  ubuntu_sl@dhcp-10-227-71-12:~$ cd /sys/class/fc_host
  ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ ls
  ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$

  
  dmesg logs
  ==

  ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ dmesg|grep lpfc
  [   12.521665] Modules linked in: hid_generic ahci crc32_pclmul lpfc(+) igb
  be2net aesni_intel ptp aes_i586 vxlan xts pps_core libahci usbhid lrw
  scsi_transport_fc gf128mul megaraid_sas ablk_helper wmi ip6_udp_tunnel cryptd
  hid i2c_algo_bit udp_tunnel fjes
  [   13.532543]  [] ? lpfc_pci_probe_one_s4.isra.38+0x207/0x970 
[lpfc]
  [   13.581554]  [] ? lpfc_pci_probe_one_s4.isra.38+0x207/0x970 
[lpfc]
  [   13.675661]  [] ? lpfc_pci_probe_one_s4.isra.38+0x207/0x970 
[lpfc]
  [   13.723254]  [] lpfc_pci_probe_one_s4.isra.38+0x207/0x970 [lpfc]
  [   13.770876]  [] lpfc_pci_probe_one+0xa2/0xe40 [lpfc]
  [   14.551773]  [] lpfc_init+0xe4/0x1000 [lpfc]
  [   15.046636] lpfc :1b:00.2: ioremap failed for SLI4 PCI config 
registers.
  [   15.082558] lpfc :1b:00.2: 0:1410 Failed to set up pci memory space.
  [   15.118685] lpfc :1b:00.3: ioremap failed for SLI4 PCI config 
registers.
  [   15.155054] lpfc :1b:00.3: 0:1410 Failed to set up pci memory space.
  [  592.495893] lpfc :1b:00.2: ioremap failed for SLI4 PCI config 
registers.
  [  592.495900] lpfc :1b:00.2: 0:1410 Failed to set up pci memory space.
  [  592.496028] lpfc :1b:00.3: ioremap failed for SLI4 PCI config 
registers.
  [  592.496030] lpfc :1b:00.3: 0:1410 Failed to set up pci memory space.

  
  Setup Details
  =
  SUT: 10.227.65.215(IMM IP) (USERID/PASSW0RD)
  OS IP: 10.227.73.172(ubuntu_sl/Swamiji001)
  Switch: 10.227.65.35(admin/Pass1234, Port no: 6,17)
  IBM Target: 10.227.65.50(emulex/passw0rd)

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

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

[Kernel-packages] [Bug 1620762] Re: Support AverMedia DVD EZMaker 7 USB video capture dongle

2016-09-06 Thread Eldar Khayrullin

No it is bug applies to all releases of Ubuntu. 
I say that I tested the patch on Ubuntu 16.04 and it works fine.

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

Title:
  Support AverMedia DVD EZMaker 7 USB video capture dongle

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux doesn't support this capture.
  Link to patch 
https://www.linuxtv.org/wiki/index.php/AVerMedia_DVD_EZMaker_7_(C039). 
  I tested it on Ubuntu 16.04 - OK.
  It will be great if this patch is built-in to kernel.

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

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

[Kernel-packages] [Bug 1620741] [NEW] Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown

You have been subscribed to a public bug:

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

Have changed /etc/default/grub to attempt a fix without success...
(grub.ref was original grub)

:/etc/default$ grep CMDLINE grub*

grub.ref:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
grub.ref:GRUB_CMDLINE_LINUX="forcepae"

grub:GRUB_CMDLINE_LINUX_DEFAULT="acpi=noirq debug=y"
grub:GRUB_CMDLINE_LINUX="forcepae"

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xfce4-panel 4.12.0-3ubuntu2
Uname: Linux 4.6.0-040600-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CurrentDesktop: XFCE
Date: Tue Sep  6 18:16:30 2016
ExecutablePath: /usr/bin/xfce4-panel
InstallationDate: Installed on 2016-08-16 (21 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: xfce4-panel
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 xenial
-- 
Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown
https://bugs.launchpad.net/bugs/1620741
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 1620733] [NEW] Xubuntu 16.04 on HP Compaq nx6325 freezes on Suspend

You have been subscribed to a public bug:

On suspend mouse movement stops.

andymc@mvac21:~$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

Suspend freezes in Kernel linux-headers-4.4.0-36 and linux-
headers-4.6.0-040600

Only way out is hold down power button for about 6 seconds.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xfce4-panel 4.12.0-3ubuntu2
Uname: Linux 4.6.0-040600-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CurrentDesktop: XFCE
Date: Tue Sep  6 17:55:49 2016
ExecutablePath: /usr/bin/xfce4-panel
InstallationDate: Installed on 2016-08-16 (21 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: xfce4-panel
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 xenial
-- 
Xubuntu 16.04 on HP Compaq nx6325 freezes on Suspend
https://bugs.launchpad.net/bugs/1620733
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 1620762] Re: Support AverMedia DVD EZMaker 7 USB video capture dongle

Does this bug not exist in 16.04 and newer?  Are you requesting this
patch in releases prior to 16.04?

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Tags added: kernel-da-key

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

Title:
  Support AverMedia DVD EZMaker 7 USB video capture dongle

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Linux doesn't support this capture.
  Link to patch 
https://www.linuxtv.org/wiki/index.php/AVerMedia_DVD_EZMaker_7_(C039). 
  I tested it on Ubuntu 16.04 - OK.
  It will be great if this patch is built-in to kernel.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

I started a kernel bisect between 4.4.0-22 and 4.4.0-23. The kernel
bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
986aed37359b5c7dc72e0cc7217cbd48fc8efe7a

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1608236

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/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 1559194] linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

--- Comment on attachment From geral...@de.ibm.com 2016-09-06 10:25 
EDT---


Debian kernel package with genwqe-bad-page.patch applied.

** Attachment added: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb"
   
https://bugs.launchpad.net/bugs/1559194/+attachment/4735664/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

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

Title:
  Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device
  driver

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  == Comment: #0 - Dmitry Gorbachev  - 2016-03-17 
08:52:41 ==
  An error occurs when running zEDC compression/decompression and hotplugging 
PCI devices.
  There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled.

  Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in 
process genwqe_gunzip  pfn:3c275
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 
count:-1 mapcount:0 mapping:  (null) index:0x0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0()
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero 
_count
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: 
xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) 
iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) 
nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) 
ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) 
ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) 
ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) 
scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) 
async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) 
xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) 
prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) 
sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) 
dasd_eckd_mod(E) dasd_mod(E)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: 
genwqe_gunzip Tainted: GW   E   4.4.0-8-generic #23-Ubuntu
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 
20917788 0002 
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 
209177a0 209177a0 00114182
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 
0092345a 03d1000a 000a
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 
20917788  20914000
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 
00114182 20917788 209177e8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace:
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] 
show_trace+0xf6/0x148)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486929]  [<00114136>] 
show_stack+0x76/0xe8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486934]  [<00518c26>] 
dump_stack+0x6e/0x90
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486937]  [<0027c376>] 
bad_page+0xe6/0x148
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486938]  [<00280516>] 
get_page_from_freelist+0x49e/0xba8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486940]  [<00280ede>] 
__alloc_pages_nodemask+0x166/0xb00
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486941]  [<0015635a>] 
s390_dma_alloc+0x82/0x1a0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486944]  [<03ff805ea142>] 
__genwqe_alloc_consistent+0x7a/0x90 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486947]  [<03ff805ea344>] 
genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486950]  [<03ff805e52da>] 
do_execute_ddcb+0x1da/0x348 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486952]  [<03ff805e5964>] 
genwqe_ioctl+0x51c/0xc20 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486953]  [<003145ee>] 
do_vfs_ioctl+0x3b6/0x518
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486955]  [<003147f4>] 
SyS_ioctl+0xa4/0xb8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486956]  [<007ad1be>] 
system_call+0xd6/0x264
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486957]  [<03ffa9df2492>] 
0x3ffa9df2492

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+subscriptions

-- 
Mailing list:

[Kernel-packages] [Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

I built the next test kernel, up to the following commit:
623e01e53927b05e96781532bdb40536e833e276

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1609242

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.

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

Title:
  Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

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

Bug description:
  When I install Ubuntu 16.04 on my computer the screen goes blank at
  login. I can blindly login and it boots but I cannot use the display
  (external monitor through HDMI).

  I've looked online for an answer to this issue but could not find a
  solution.  However, many people report this issue in forums with the
  4.4x kernel.

  On my main computer, I upgraded from 14.04 to 16.04.1. On this
  computer I was able to switch back to the 3.13 kernel which *does
  work*.

  On the same computer, if I use a 16.04 live CD, it does the same
  thing.  The screen goes blank.

  UEFI may be part of the issue as well.  I have it disabled in bios
  (set to legacy mode) but when I first boot, it seems to go into UEFI
  mode first and then, after rebooting with  it shows
  me the list of kernels. I can select the kernel from there but if I
  use a 4.4x kernel, it blanks out at encryption passphrase screen.

  There are also people with similar issues on AskUbuntu.

  Here's some basic HW info.  If you require more, please ask.

  sudo lshw | head
  zbox
  description: Notebook
  product: ZBOX-ID18 (NA)
  vendor: ZOTAC
  version: XX
  serial: G211X
  width: 64 bits
  capabilities: smbios-2.7 dmi-2.7 vsyscall32
  configuration: boot=normal chassis=notebook family=NA sku=NA 
uuid=00020003-0004-0005-0006-000700080009
    *-core

  sudo lshw -C display
    *-display
     description: VGA compatible controller
     product: 3rd Gen Core processor Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 09
     width: 64 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:45 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

  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:  user5536 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38
  InstallationDate: Installed on 2014-07-23 (743 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  MachineType: ZOTAC ZBOX-ID18
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.157.2
  RfKill:

  StagingDrivers: rts5139
  Tags:  xenial staging
  Uname: Linux 3.13.0-92-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B211P011
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID18
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 10
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA:
  dmi.product.name: ZBOX-ID18
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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

[Kernel-packages] [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler()

2016-09-06 Thread Radha Mohan Chintakuntla

@Dann, my bad. the installer kernel is from older 16.04 release, that
was before this commit. I don't see this issue with latest installer
kernel.

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

Title:
  ThunderX: soft lockup in cursor_timer_handler()

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

Bug description:
  I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via 
virtual media:

http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso

  During boot I observed the following lockup on the serial console:

  [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! 
[swapper/14:0]
  [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) 
usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) 
drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) 
ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
  [ 84.922749]
  [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic 
#37-Ubuntu
  [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
  [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: 
801f6c9e8000
  [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
  [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
  [ 84.922778] pc : [] lr : [] pstate: 
00400145
  [ 84.922781] sp : 801f6c9ebc20
  [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
  [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
  [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
  [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
  [ 84.922802] x21: 0100 x20: 8000f94398d8
  [ 84.922807] x19: 8000f9439800 x18: c76a5358
  [ 84.922811] x17: 97bbd2a8 x16: 802a5040
  [ 84.922816] x15: 3e4cf1e0 x14: 0008
  [ 84.922820] x13:  x12: 003d0900
  [ 84.922824] x11: 003d0900 x10: 8090f200
  [ 84.922829] x9 : 3d09 x8 : 000e
  [ 84.922833] x7 : 801f7b3c5008 x6 : 
  [ 84.922837] x5 :  x4 : 0001
  [ 84.922842] x3 :  x2 : 801f6c899e05
  [ 84.922846] x1 : 801f667d99e0 x0 : 
  [ 84.922850]
  [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.342677] random: nonblocking pool is initialized

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

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

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

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

apport-collect 1620762

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

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

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

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

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

Title:
  Support AverMedia DVD EZMaker 7 USB video capture dongle

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Linux doesn't support this capture.
  Link to patch 
https://www.linuxtv.org/wiki/index.php/AVerMedia_DVD_EZMaker_7_(C039). 
  I tested it on Ubuntu 16.04 - OK.
  It will be great if this patch is built-in to kernel.

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

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

[Kernel-packages] [Bug 1559194] Re: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver

** This bug is no longer a duplicate of bug 1572291
   s390/pci: add extra padding to function measurement block

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

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => 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/1559194

Title:
  Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device
  driver

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  == Comment: #0 - Dmitry Gorbachev  - 2016-03-17 
08:52:41 ==
  An error occurs when running zEDC compression/decompression and hotplugging 
PCI devices.
  There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled.

  Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in 
process genwqe_gunzip  pfn:3c275
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 
count:-1 mapcount:0 mapping:  (null) index:0x0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0()
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero 
_count
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: 
xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) 
iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) 
nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) 
ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) 
ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) 
ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) 
scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) 
async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) 
xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) 
prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) 
sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) 
dasd_eckd_mod(E) dasd_mod(E)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: 
genwqe_gunzip Tainted: GW   E   4.4.0-8-generic #23-Ubuntu
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 
20917788 0002 
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 
209177a0 209177a0 00114182
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 
0092345a 03d1000a 000a
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 
20917788  20914000
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 
00114182 20917788 209177e8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace:
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] 
show_trace+0xf6/0x148)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486929]  [<00114136>] 
show_stack+0x76/0xe8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486934]  [<00518c26>] 
dump_stack+0x6e/0x90
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486937]  [<0027c376>] 
bad_page+0xe6/0x148
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486938]  [<00280516>] 
get_page_from_freelist+0x49e/0xba8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486940]  [<00280ede>] 
__alloc_pages_nodemask+0x166/0xb00
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486941]  [<0015635a>] 
s390_dma_alloc+0x82/0x1a0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486944]  [<03ff805ea142>] 
__genwqe_alloc_consistent+0x7a/0x90 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486947]  [<03ff805ea344>] 
genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486950]  [<03ff805e52da>] 
do_execute_ddcb+0x1da/0x348 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486952]  [<03ff805e5964>] 
genwqe_ioctl+0x51c/0xc20 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486953]  [<003145ee>] 
do_vfs_ioctl+0x3b6/0x518
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486955]  [<003147f4>] 
SyS_ioctl+0xa4/0xb8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486956]  [<007ad1be>] 
system_call+0xd6/0x264
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486957]  [<03ffa9df2492>] 
0x3ffa9df2492

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+subscriptions

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

[Kernel-packages] [Bug 1620648] Re: Pairing bluetooth 0a12:0001 with Bose SoundLink II headphones fails

2016-09-06 Thread Jarno Suni

Both devices are new to me and I recently bought them new. The same
happened with 4.4.0-22 at least. I have not been able to pair by any
kernel that I have tried with.

I hope the "blueman-manager output" attachment is useful.

Bluetooth dongle with same id seems to have worked at some point: 
https://wiki.ubuntu.com/HardwareSupportComponentsBluetoothUsbAdapters
It is found under brand Bluetake there (mine is Konig) and there is:

"Works out-of-the-box in Ubuntu v10.04 ~ 11.04 Stopped working reliably in 
11.10, frequent kernel panics and other general not good stuff, [Bug: 901770]
...
Might need same fix as Belkin : add "blacklist hci_usb" to 
/etc/modprobe.d/blacklist.conf, and add "hci_usb reset=1" to /etc/modules"

I tried the module trick and rebooted, but no help.

Maybe I'll experiment with the mainline kernel next.

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

Title:
  Pairing bluetooth 0a12:0001 with Bose SoundLink II headphones fails

Status in blueman package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I see the device in blueman-manager, but pairing fails. I could pair
  the dongle with another device. And I could pair the Bose device with
  another bluetooth device in Xubuntu 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jarnos 3069 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jarnos 3069 F...m pulseaudio
   /dev/snd/controlC0:  jarnos 3069 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Sep  6 17:01:49 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (131 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-36-generic 
root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  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/blueman/+bug/1620648/+subscriptions

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

[Kernel-packages] [Bug 1620762] [NEW] Support AverMedia DVD EZMaker 7 USB video capture dongle

2016-09-06 Thread Eldar Khayrullin

Public bug reported:

Linux doesn't support this capture.
Link to patch 
https://www.linuxtv.org/wiki/index.php/AVerMedia_DVD_EZMaker_7_(C039). 
I tested it on Ubuntu 16.04 - OK.
It will be great if this patch is built-in to kernel.

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


** Tags: device

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

Title:
  Support AverMedia DVD EZMaker 7 USB video capture dongle

Status in linux package in Ubuntu:
  New

Bug description:
  Linux doesn't support this capture.
  Link to patch 
https://www.linuxtv.org/wiki/index.php/AVerMedia_DVD_EZMaker_7_(C039). 
  I tested it on Ubuntu 16.04 - OK.
  It will be great if this patch is built-in to kernel.

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

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

[Kernel-packages] [Bug 1619766] Re: Backport E3 Skylake Support in ie31200_edac to Xenial

I built a test kernel with a pick of commit 953dee9.  The test kernel can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1619766/

Can you test this kernel and see if it resolves this bug?

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

Title:
  Backport E3 Skylake Support in ie31200_edac to Xenial

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Skylake E3 Support was added to ie31200_edac with the following commit:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/edac/ie31200_edac.c?id=953dee9bbd245f5515173126b9cc8b1a2c340797

  Could we get this support backported to Xenial?

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

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

[Kernel-packages] [Bug 1573848] Re: KASLR should be enabled by default (x86)

2016-09-06 Thread Simon Déziel

** Attachment removed: "13882350_308252829517622_547356934184648507_n.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573848/+attachment/4719653/+files/13882350_308252829517622_547356934184648507_n.jpg

** Patch removed: "13882350_308252829517622_547356934184648507_n.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573848/+attachment/4719654/+files/13882350_308252829517622_547356934184648507_n.jpg

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

Title:
  KASLR should be enabled by default (x86)

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

Bug description:
  Kernel Address Space Layout Randomization (KASLR) can make it harder
  to accomplish kernel security vulnerability exploits, especially
  during remote attacks or attacks from containers. On x86, KASLR has a
  run-time conflict with Hibernation, and currently the kernel selects
  Hibernation instead of KASLR unless the "kaslr" kernel command line
  option is given at boot time. Since the Unity desktop disabled access
  to Hibernation by default and cloud images don't use Hibernation, it
  would make sense to make KASLR enabled by default on Ubuntu. Those
  wishing to use Hibernation could just provide the "nokaslr" kernel
  command line option to flip the preference back.

  A patch to implement this already exists:
  https://lkml.org/lkml/2016/4/6/637

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

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

[Kernel-packages] [Bug 1618251] onibi (amd64) - tests ran: 81, failed: 31

tests ran:  81, failed: 31;
  
http://kernel.ubuntu.com/testing/3.19.0-69.77~14.04.1/onibi__3.19.0-69.77~14.04.1__2016-09-06_12-28-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-69.77~14.04.1 -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:
  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-69.77~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

  -- swm properties --
  derivative-trackers-created: true
  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/1618251/+subscriptions

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

[Kernel-packages] [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler()

2016-09-06 Thread dann frazier

@Radha If you are still seeing this bug, can you attach a console log?

Here's the commit that was added in xenial to address this:

commit 51b7d7350e526bde77f458fb23481e7c5d312d91
Author: David Daney 
Date:   Tue May 24 12:55:54 2016 +0800

UBUNTU: SAUCE: tty: vt: Fix soft lockup in fbcon cursor blink timer.

BugLink: http://bugs.launchpad.net/bugs/1574814

We are getting somewhat random soft lockups with this signature:

[   86.992215] [] el1_irq+0xa0/0x10c
[   86.997082] [] cursor_timer_handler+0x30/0x54
[   87.002991] [] call_timer_fn+0x54/0x1a8
[   87.008378] [] run_timer_softirq+0x1c4/0x2bc
[   87.014200] [] __do_softirq+0x114/0x344
[   87.019590] [] irq_exit+0x74/0x98
[   87.024458] [] __handle_domain_irq+0x98/0xfc
[   87.030278] [] gic_handle_irq+0x94/0x190

This is caused by the vt visual_init() function calling into
fbcon_init() with a vc_cur_blink_ms value of zero.  This is a
transient condition, as it is later set to a non-zero value.  But, if
the timer happens to expire while the blink rate is zero, it goes into
an endless loop, and we get soft lockup.

The fix is to initialize vc_cur_blink_ms before calling the con_init()
function.

Tested-by: Ming Lei 
Acked-by: Pavel Machek 
Acked-by: Scot Doyle 
Signed-off-by: David Daney 
Cc: sta...@vger.kernel.org
Reference: https://lkml.org/lkml/2016/5/17/455
Cc: Ming Lei 
Acked-by: Tim Gardner 
Signed-off-by: Kamal Mostafa 

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

Title:
  ThunderX: soft lockup in cursor_timer_handler()

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

Bug description:
  I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via 
virtual media:

http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso

  During boot I observed the following lockup on the serial console:

  [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! 
[swapper/14:0]
  [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) 
usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) 
drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) 
ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
  [ 84.922749]
  [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic 
#37-Ubuntu
  [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
  [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: 
801f6c9e8000
  [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
  [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
  [ 84.922778] pc : [] lr : [] pstate: 
00400145
  [ 84.922781] sp : 801f6c9ebc20
  [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
  [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
  [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
  [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
  [ 84.922802] x21: 0100 x20: 8000f94398d8
  [ 84.922807] x19: 8000f9439800 x18: c76a5358
  [ 84.922811] x17: 97bbd2a8 x16: 802a5040
  [ 84.922816] x15: 3e4cf1e0 x14: 0008
  [ 84.922820] x13:  x12: 003d0900
  [ 84.922824] x11: 003d0900 x10: 8090f200
  [ 84.922829] x9 : 3d09 x8 : 000e
  [ 84.922833] x7 : 801f7b3c5008 x6 : 
  [ 84.922837] x5 :  x4 : 0001
  [ 84.922842] x3 :  x2 : 801f6c899e05
  [ 84.922846] x1 : 801f667d99e0 x0 : 
  [ 84.922850]
  [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.342677] random: nonblocking pool is initialized

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

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

[Kernel-packages] [Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-09-06 Thread harry

Hi All,

Until this issue is resolved, is there anything I could do to protect
myself (esp., since I'm not getting any security updates using the
mainline 4.2.8 kernel)?

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

Title:
  Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

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

Bug description:
  When I install Ubuntu 16.04 on my computer the screen goes blank at
  login. I can blindly login and it boots but I cannot use the display
  (external monitor through HDMI).

  I've looked online for an answer to this issue but could not find a
  solution.  However, many people report this issue in forums with the
  4.4x kernel.

  On my main computer, I upgraded from 14.04 to 16.04.1. On this
  computer I was able to switch back to the 3.13 kernel which *does
  work*.

  On the same computer, if I use a 16.04 live CD, it does the same
  thing.  The screen goes blank.

  UEFI may be part of the issue as well.  I have it disabled in bios
  (set to legacy mode) but when I first boot, it seems to go into UEFI
  mode first and then, after rebooting with  it shows
  me the list of kernels. I can select the kernel from there but if I
  use a 4.4x kernel, it blanks out at encryption passphrase screen.

  There are also people with similar issues on AskUbuntu.

  Here's some basic HW info.  If you require more, please ask.

  sudo lshw | head
  zbox
  description: Notebook
  product: ZBOX-ID18 (NA)
  vendor: ZOTAC
  version: XX
  serial: G211X
  width: 64 bits
  capabilities: smbios-2.7 dmi-2.7 vsyscall32
  configuration: boot=normal chassis=notebook family=NA sku=NA 
uuid=00020003-0004-0005-0006-000700080009
    *-core

  sudo lshw -C display
    *-display
     description: VGA compatible controller
     product: 3rd Gen Core processor Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 09
     width: 64 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:45 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

  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:  user5536 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38
  InstallationDate: Installed on 2014-07-23 (743 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  MachineType: ZOTAC ZBOX-ID18
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.157.2
  RfKill:

  StagingDrivers: rts5139
  Tags:  xenial staging
  Uname: Linux 3.13.0-92-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B211P011
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID18
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 10
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA:
  dmi.product.name: ZBOX-ID18
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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

[Kernel-packages] [Bug 1620089] Re: REGRESSION: Laptop hangs during second time it suspends

2016-09-06 Thread Jan van de Wijdeven

Thanks Joseph. 
In the meantime, I finished the bisect. It tells me the following commit is to 
blame:

87bd13c6f9776e18ab9a5192325c54621db8a2af is the first bad commit
commit 87bd13c6f9776e18ab9a5192325c54621db8a2af
Author: Jarkko Sakkinen 
Date:   Mon Jun 27 07:10:51 2016 -0600

tpm_crb: fix mapping of the buffers

BugLink: http://bugs.launchpad.net/bugs/1596469

On my Lenovo x250 the following situation occurs:

[18697.813871] tpm_crb MSFT0101:00: can't request region for resource
[mem 0xacdff080-0xacdf]

The mapping of the control area overlaps the mapping of the command
buffer. The control area is mapped over page, which is not right. It
should mapped over sizeof(struct crb_control_area).

Fixing this issue unmasks another issue. Command and response buffers
can overlap and they do interleave on this machine. According to the PTP
specification the overlapping means that they are mapped to the same
buffer.

The commit has been also on a Haswell NUC where things worked before
applying this fix so that the both code paths for response buffer
initialization are tested.

Cc: sta...@vger.kernel.org
Fixes: 1bd047be37d9 ("tpm_crb: Use devm_ioremap_resource")
Signed-off-by: Jarkko Sakkinen 
Reviewed-by: Jason Gunthorpe 
(cherry picked from linux-next commit 
0af6e0a2da2e4fedaa274da438d3b879192b)
Signed-off-by: Tim Gardner 
Acked-by: Stefan Bader 
Acked-by: Brad Figg 
Signed-off-by: Kamal Mostafa   
 

 
:04 04 84dfc36e75e151c51541109acdf6dc2a7a620398 
a236ec06194abc467c852316b1b50f3b3a9ae7f0 M  drivers

That also leads me to try a workaround. When I blacklist the tpm_crb
module, I can suspend to my hearts delight. Or at least, more than two
times in a row ;)

** Tags added: bisect-done tpm workaround

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

Title:
  REGRESSION: Laptop hangs during second time it suspends

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Kubuntu 15.10 I had a problem with the suspend functionality on my
  laptop. The second time it suspends it would hang, and a hard reset
  was necessary to resolve the problem. After the update to 16.04, the
  problem was resolved (see
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552216)

  I updated my laptop using the xenial-updates repository. After the
  upgrade to linux 4.4.0-31, the suspend issue returned. I have also
  tried later updates (4.4.0-34 and 4.4.0-36), but the issue is also
  present in those versions. I therefore still use 4.4.0-28.

  I tried bisecting, but after a few iterations it messed up my boot
  partition, and after repairing that, I no longer took the time to
  finish the bisection. (see
  https://launchpad.net/ubuntu/+source/linux/4.4.0-31.50 for changelog)

  I have a short bit (but not complete work) of the git bisect log:

  $ git bisect log
  # bad: [2a1e175b928aefed1fd3c90c98e845f764fa8684] UBUNTU: Ubuntu-4.4.0-31.50
  # good: [a6409cad137621e2b43d9f49c757fbc996539e85] UBUNTU: Ubuntu-4.4.0-28.47
  git bisect start 'Ubuntu-4.4.0-31.50' 'Ubuntu-4.4.0-28.47'
  # bad: [44d66d94ed3e6e2434b06af7180a441cbf2b9f83] UBUNTU: Ubuntu-4.4.0-29.48
  git bisect bad 44d66d94ed3e6e2434b06af7180a441cbf2b9f83


  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jan9230 F pulseaudio
  Date: Sun Sep  4 19:42:54 2016
  HibernationDevice: RESUME=UUID=321acbbf-9a6a-4825-8f47-a89d56536272
  InstallationDate: Installed on 2016-02-03 (214 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:57eb Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed

[Kernel-packages] [Bug 1604314] Re: [Xenial] iommu/amd: Fix unity mapping initialization race

2016-09-06 Thread Ganesh Lakshminarayana

Verified with daily build of Ubuntu 16.10(Yakkety) and the issue is not
seen. Kernel panic issue is not seen and OS boots as expected with IOMMU
enabled. Please find the details below:

Server : BL465c Gen8
ROM : A26 03/07/2016
iLO : 2.40
OS : Ubuntu 16.10  (Ubuntu Yakkety Yak (development branch))
Kernel version : 4.4.0-9136-generic

Thanks
Ganesh

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

Title:
  [Xenial] iommu/amd: Fix unity mapping initialization race

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

Bug description:
  == Xenial SRU Justification ==
  HP Gen8 servers were having kernel panics with the 4.2 and 4.4 kernel which 
is apparently resolved with the following commits.  HP would like to see these 
SRU'd for Xenial.

  commit 0caa7616a6aca449dd68b58cb29bd491d296c2d5
  Author: Aaron Campbell 
  Date:   Sat Jul 2 21:23:24 2016 -0300

  iommu/vt-d: Fix infinite loop in free_all_cpu_cached_iovas

  commit 522e5cb76d0663c88f96b6a8301451c8efa37207
  Author: Joerg Roedel 
  Date:   Fri Jul 1 16:42:55 2016 +0200

  iommu/amd: Fix unity mapping initialization race

  == Testing ==
  HP confirms their testing shows these patches resolves the issue on several 
test machines.

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

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

[Kernel-packages] [Bug 1615665] Re: Enable virtual scsi server driver for Power

--- Comment on attachment From b...@us.ibm.com 2016-09-01 10:01 EDT---


This is a dependency, where the driver might cause a kernel crash on 
de-registration of target session.

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

** Attachment added: "Ibmvscsis: Fix to properly de-register target session"
   
https://bugs.launchpad.net/bugs/1615665/+attachment/4735602/+files/0001-Ibmvscsis-Properly-deregister-target-sessions.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/1615665

Title:
  Enable virtual scsi server driver for Power

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:
  Once Canonical updates to the 4.8 kernel, the following kernel options
  need to be enabled for this feature:

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

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

[Kernel-packages] [Bug 1592547] Re: vmalloc failure leads to null ptr dereference in aa_dfa_next

2016-09-06 Thread Colin Ian King

Pounded this for a while, cannot reproduce with the fix, marking it as
verified

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

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

Title:
  vmalloc failure leads to null ptr dereference in aa_dfa_next

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  running stress-ng apparmor stressor with a vmalloc NULL return trips a
  null ptr dereference in aa_dfa_next:

  $ uname -a
  Linux ubuntu 4.4.0-24-generic #43

  [   46.271517] BUG: unable to handle kernel NULL pointer dereference at 
0020
  [   46.271641] IP: [] aa_dfa_next+0x6/0x70
  [   46.271743] PGD 39ebd067 PUD 39ebe067 PMD 0
  [   46.271833] Oops:  [#1] SMP
  [   46.271926] Modules linked in: jitterentropy_rng algif_rng salsa20_generic 
salsa20_x86_64 camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 
cast6_avx_x86_64 cast6_generic cast_common serpent_avx_x86_64 
serpent_sse2_x86_64 serpent_generic twofish_generic twofish_avx_x86_64 
twofish_x86_64_3way twofish_x86_64 twofish_common xts algif_skcipher tgr192 
wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg ppdev 
snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm input_leds joydev snd_timer serio_raw snd soundcore i2c_piix4 mac_hid 
8250_fintek parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq
  [   46.273290]  libcrc32c raid1 raid0 multipath linear 8139too 
crct10dif_pclmul crc32_pclmul qxl aesni_intel aes_x86_64 lrw gf128mul ttm 
drm_kms_helper glue_helper ablk_helper cryptd syscopyarea sysfillrect sysimgblt 
fb_sys_fops psmouse drm floppy 8139cp mii pata_acpi
  [   46.274250] CPU: 0 PID: 1349 Comm: stress-ng-appar Not tainted 
4.4.0-24-generic #43
  [   46.274436] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   46.274632] task: 8800374be040 ti: 88003746c000 task.ti: 
88003746c000
  [   46.274854] RIP: 0010:[]  [] 
aa_dfa_next+0x6/0x70
  [   46.275072] RSP: 0018:88003746fca8  EFLAGS: 00010282
  [   46.275450] RAX:  RBX: 0003 RCX: 
4a46
  [   46.275934] RDX: 0002 RSI: 0001 RDI: 

  [   46.276348] RBP: 88003746fd28 R08: 88003fc19f40 R09: 
88003e001d00
  [   46.276757] R10: 88003da8e600 R11: 88003e001500 R12: 
88003746fd48
  [   46.276979] R13: 88003acc4800 R14: 88003acc4894 R15: 
0029
  [   46.277202] FS:  7f7198a0f700() GS:88003fc0() 
knlGS:
  [   46.277500] CS:  0010 DS:  ES:  CR0: 80050033
  [   46.278006] CR2: 0020 CR3: 39ebc000 CR4: 
001406f0
  [   46.278592] Stack:
  [   46.278846]  88003746fd28 81383585  

  [   46.279271]  3746fd00  c9000268e400 

  [   46.279860]  88003746fd40  5833b243 
88003746fe28
  [   46.280311] Call Trace:
  [   46.280606]  [] ? unpack_profile+0x5c5/0x970
  [   46.280854]  [] aa_unpack+0xe9/0x450
  [   46.281091]  [] aa_replace_profiles+0x77/0xb70
  [   46.281341]  [] ? vmalloc+0x6b/0x70
  [   46.281610]  [] policy_update+0x9f/0x1f0
  [   46.281887]  [] profile_replace+0x13/0x20
  [   46.282169]  [] __vfs_write+0x18/0x40
  [   46.282444]  [] vfs_write+0xa9/0x1a0
  [   46.282728]  [] ? do_sys_open+0x1bf/0x2a0
  [   46.283418]  [] SyS_write+0x55/0xc0
  [   46.284188]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [   46.284753] Code: 0c 42 39 ce 74 d9 0f b6 02 41 0f b7 34 7b 84 c0 75 d9 eb 
c3 41 0f b7 34 44 eb 89 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 <48> 8b 
47 20 4c 8b 5f 28 4c 8b 57 40 48 89 e5 4c 8b 4f 18 48 8d 
  [   46.285401] RIP  [] aa_dfa_next+0x6/0x70

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

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

[Kernel-packages] [Bug 1613787] Re: xfrm: ipsec crash when updating spd thresholds

2016-09-06 Thread Nicolas Dichtel

Test done on ubuntu-16.04 (Linux ubuntu1604 4.4.0-37-generic #56-Ubuntu)
and ubuntu-14.04 (Linux ubuntu1404 3.19.0-69-generic
#77~14.04.1-Ubuntu).

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

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

Title:
  xfrm: ipsec crash when updating spd thresholds

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Fixed upstream by this commit (only in IPsec tree for now):

  
https://git.kernel.org/cgit/linux/kernel/git/klassert/ipsec.git/commit/?id=6916fb3b10b3cbe3b1f9f5b680675f53e4e299eb
  http://patchwork.ozlabs.org/patch/654026/

  To update the thresholds: 'ip xfrm policy set hthresh4 24 32'

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

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

[Kernel-packages] [Bug 1620027] Re: sound doesn't work - ubnt 16.04.1, asus laptop, snd-hda-intel

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc5


** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  sound doesn't work - ubnt 16.04.1, asus laptop, snd-hda-intel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi guys,

  sound doesn't work on my asus V1J laptop. I tried change
  /etc/modprobe.d/alsa.conf and set:

  options snd-hda-intel position_fix=1 model=3stack

  then i tried: options snd-hda-intel power_save=10
  power_save_controller=N position_fix=1 model=3stack

  as described there (find V1J keyword):
  https://doc.ubuntu-fr.org/audio_intel_hda

  after that i tried these models:
  model=laptop
  model=laptop-imic
  model=epad
  model=auto

  In year 2007, model=3stack works for me (I was running gentoo).

  my sound card chipset: AD1986A

  lspci:

  00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High
  Definition Audio Controller (rev 02)

  I think, that there is problem in acpi, because model 3stack works for
  me some years before.

  I tried config grub and boot options:
  acpi=off -> doesn't help
  acpi=on -> doesn't help
  acpi=noirq -> doesn't help

  In year 2007, there was an article - How to install debian on ASUS
  V1J: http://sgxris.blogspot.cz/2007/03/install-debian-unstable-on-
  asus.html

  There is written, that sound will work, after I will install 
http://acpi4asus.sourceforge.net/.
  But these drivers are included in kernel since 2.6.19 - so I does not need 
compile acpi4asus. But in 2007 it helped for me.

  
  user@asus-v1j:~$ aplay -l
   Seznam PLAYBACK Hardwarových zařízení 
  karta 0: Intel [HDA Intel], zařízení 0: AD1986A Analog [AD1986A Analog]
Podzařízení: 1/1
Podzařízení #0: subdevice #0
  karta 0: Intel [HDA Intel], zařízení 1: AD1986A Digital [AD1986A Digital]
Podzařízení: 1/1
Podzařízení #0: subdevice #0
  karta 0: Intel [HDA Intel], zařízení 6: Si3054 Modem [Si3054 Modem]
Podzařízení: 1/1
Podzařízení #0: subdevice #0


  I have no idea, how to repair my sound in Ubuntu.

  Do you have any idea?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosek  2688 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ab7b83f2-1270-41d0-bfb5-d1d74b9da089
  InstallationDate: Installed on 2015-11-05 (304 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release i386 
(20151021)
  MachineType: ASUSTeK Computer Inc. V1J
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=e45c4c00-42ea-44e9-a797-d21584d694ae ro quiet splash acpi=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-09-03 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: V1J
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr305:bd04/10/2007:svnASUSTeKComputerInc.:pnV1J:pvr1.0:rvnASUSTeKComputerInc.:rnV1J:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
  dmi.product.name: V1J
  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/1620027/+subscriptions

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

[Kernel-packages] [Bug 1619766] Re: Backport E3 Skylake Support in ie31200_edac to Xenial

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

** Tags added: kernel-da-key xenial

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

Title:
  Backport E3 Skylake Support in ie31200_edac to Xenial

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Skylake E3 Support was added to ie31200_edac with the following commit:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/edac/ie31200_edac.c?id=953dee9bbd245f5515173126b9cc8b1a2c340797

  Could we get this support backported to Xenial?

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

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

[Kernel-packages] [Bug 1620089] Re: REGRESSION: Laptop hangs during second time it suspends

Are you continuing with the bisect?  If you are, I can build a test
kernel with the first bad commit reverted.

I could also pick up the bisect where you left off and build test
kernels for you to test.

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  REGRESSION: Laptop hangs during second time it suspends

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Kubuntu 15.10 I had a problem with the suspend functionality on my
  laptop. The second time it suspends it would hang, and a hard reset
  was necessary to resolve the problem. After the update to 16.04, the
  problem was resolved (see
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552216)

  I updated my laptop using the xenial-updates repository. After the
  upgrade to linux 4.4.0-31, the suspend issue returned. I have also
  tried later updates (4.4.0-34 and 4.4.0-36), but the issue is also
  present in those versions. I therefore still use 4.4.0-28.

  I tried bisecting, but after a few iterations it messed up my boot
  partition, and after repairing that, I no longer took the time to
  finish the bisection. (see
  https://launchpad.net/ubuntu/+source/linux/4.4.0-31.50 for changelog)

  I have a short bit (but not complete work) of the git bisect log:

  $ git bisect log
  # bad: [2a1e175b928aefed1fd3c90c98e845f764fa8684] UBUNTU: Ubuntu-4.4.0-31.50
  # good: [a6409cad137621e2b43d9f49c757fbc996539e85] UBUNTU: Ubuntu-4.4.0-28.47
  git bisect start 'Ubuntu-4.4.0-31.50' 'Ubuntu-4.4.0-28.47'
  # bad: [44d66d94ed3e6e2434b06af7180a441cbf2b9f83] UBUNTU: Ubuntu-4.4.0-29.48
  git bisect bad 44d66d94ed3e6e2434b06af7180a441cbf2b9f83


  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jan9230 F pulseaudio
  Date: Sun Sep  4 19:42:54 2016
  HibernationDevice: RESUME=UUID=321acbbf-9a6a-4825-8f47-a89d56536272
  InstallationDate: Installed on 2016-02-03 (214 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:57eb Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=43cbb8c2-c0ce-40e2-a795-3a506e63d450 ro nogpumanager quiet splash 
pci=noaer
  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-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.160
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.77
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A4
  dmi.board.vendor: HP
  dmi.board.version: 91.1C
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.77:bd12/18/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A4:rvr91.1C:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1620525] Re: sbuild with overlayfs fails in yakkety