[Kernel-packages] [Bug 1664622] Re: qemu: Missing transaction memory advertisement

2017-03-27 Thread ChristianEhrhardt 
Ok, thank you all for your help in clarifying that - given that Rafael
seems to be ok as initial reporter and that IBM stated there is nothing
to do for Qemu (we know newer qemu works, so there could be something,
yet unidentified yet) I'm setting that to Won't Fix for now.

** Changed in: qemu (Ubuntu Xenial)
   Status: Incomplete => Won't Fix

** Changed in: qemu (Ubuntu Yakkety)
   Status: Incomplete => Won't Fix

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

Title:
  qemu: Missing transaction memory advertisement

Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Won't Fix
Status in qemu source package in Yakkety:
  Won't Fix

Bug description:
  [Impact]

   * The non HW assisted virtualization (kvm-pr) on PowerPC announces 
 support for the Transactional memory feature but does not fully 
 support it. Due to that guests crash.

   * The fix essentially takes away the TM feature by default and only 
 enables it incertain cases where it is correct (right HW and recent 
 KVM-HV implementation)

  
  [Test Case]

   * Repro
 1. install uvtool-libvirt in Host
 2. uvt-simplestreams-libvirt sync --source 
http://cloud-images.ubuntu.com/daily arch=ppc64el label=daily release=xenial
 3. $ cat /home/ubuntu/ppc-template.xml
  

  hvm
  


  
  
  


  


  
  


  
  

  
  

  
 4. $ uvt-kvm create --memory 4096 --template /home/ubuntu/ppc-template.xml 
--password=ubuntu --ssh-public-key-file /home/ubuntu/.ssh/authorized_keys 
kvmguest-xenial-level1 release=xenial arch=ppc64el label=daily
 5. log into this guest (all following steps are in level1 guest to 
spawn a level2 guest)
 6. ensure kvm_pr is loaded correctly
This is in the extras package which is not installed by default 
(other bug). Get it with
$ apt-get install linux-image-extra-virtual
$ modprobe kvm_pr
$ lsmod | grep kvm_pr
 7. make sure libvirt default network can start in 2nd level
There likely is a network collision, use virsh net-edit to dix and 
then virsh net-start to start the network
 8. Get Original Xenial Ubuntu image
wget 
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-server-ppc64el.iso
 9. sudo apt install virtinst
  10. $ virt-install --virt-type=kvm --cpu=host --name=nested-xenial 
--controller type=scsi,model=virtio-scsi --graphics none --console 
pty,target_type=serial --disk 
path=/home/ubuntu/test-xenial-virt-inst.qcow2,size=4 --vcpus=4 --ram=2048 
--os-type=linux --os-variant ubuntu16.04 --network bridge=virbr0,model=virtio 
--cdrom=ubuntu-16.04-server-ppc64el.iso
 11. See crash on guest install/boot

   * Installing the fixed qemu in the 1st level (not on Bare Metal)
  before retrying step 11 should show the issue being fixed

  [Regression Potential]

   * It is changing features announced to the guest, but then it is only 
 taking it away in cases it won't work

   * The change is ppc64el "only" which restricts the audience to be hit  
 by regressions and even there kvm_pr (problem state virtualization) 
 is a rare case usually only for Testing/CI

   * Changes are upstream in qemu a while now without being revoked and 
 come from IBM themselves.

  
  --- 


  == Comment: #0 - Breno Henrique Leitao  - 2017-02-14 
10:03:03 ==
  We don't support transactional memory in PR KVM, so don't tell the OS that we 
do.

  These are the required patches:

  commit 2e68f28854f0120c9a938a61b64aaf1eaecb162b
  Author: Thomas Huth 
  Date:   Wed Sep 28 13:16:30 2016 +0200

  ppc: Check the availability of transactional memory

  KVM-PR currently does not support transactional memory, and the
  implementation in TCG is just a fake. We should not announce TM
  support in the ibm,pa-features property when running on such a
  system, so disable it by default and only enable it if the KVM
  implementation supports it (i.e. recent versions of KVM-HV).
  These changes are based on some earlier work from Anton Blanchard
  (thanks!).

  Signed-off-by: Thomas Huth 
  Reviewed-by: C?dric Le Goater 
  Signed-off-by: David Gibson 
  (cherry picked from commit bac3bf287ab60e264b636f5f00c116a19b655762)

  commit 45a4f18e2ec40b96893c780c28ab18c246906355
  Author: Thomas Huth 
  Date:   Wed Sep 28 13:16:29 2016 +0200

  hw/ppc/spapr: Fix the selection of the processor features

  The current code uses pa_features_206 for POWERPC_MMU_2_06, and
  for everything else, it uses pa_features_207. This is bad in some
  cases because there is also a "degraded" MMU version of ISA 2.06,
  called POWERPC_MMU_2_06a, which

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-27 Thread Cristiano Casella 
patched kernel works:

root@ID11600:~# uname -a
Linux ID11600.example.com 4.4.0-71-generic #92~lp1674635Patched SMP Mon Mar 27 
22:33:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1676078] Re: Touchpad is not recognized (ASUS X556U)

2017-03-27 Thread Enrique Palacios 
Thanks for the help.

Joseph: I test with 4.11 r4 kernel and now its working ok. 
I didnt have to try the parameters.

Thanks again.

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

Title:
  Touchpad is not recognized (ASUS X556U)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad doesnt work and it isnt recongnized.

  Xinput (USB optical mouse is another USB mouse connected)

  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ USB Optical Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Asus Wireless Radio Control id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Video Bus   id=9[slave  
keyboard (3)]
  ↳ Sleep Buttonid=10   [slave  
keyboard (3)]
  ↳ USB Camera  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]

  lspci
  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 08)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
  00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 08)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#5 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940M] (rev a2)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
  03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 30)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-41-generic 4.8.0-41.44
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brujo  2424 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Mar 25 12:45:42 2017
  HibernationDevice: RESUME=UUID=5a7d3492-03cf-436b-ab0c-7e85013a018d
  InstallationDate: Installed on 2017-01-30 (54 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X556UB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic.efi.signed 
root=UUID=67f6eec2-c5b9-4465-a985-87e85a5f86bf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-41-generic N/A
   linux-backports-modules-4.8.0-41-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UB.405
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UB
  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:bvnAmerican

[Kernel-packages] [Bug 1613472] Re: Ubuntu doesn't read SD cards

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]

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

Title:
  Ubuntu doesn't read SD cards

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

Bug description:
  Ubuntu doesn't read SD cards, I use internal card reader in my PC.

  I tried latest mainline kernel and it did not help.

  Before upgrade to this kernel, it worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tomas  3985 F pulseaudio
   /dev/snd/controlC2:  tomas  3985 F pulseaudio
   /dev/snd/controlC0:  tomas  3985 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Aug 16 00:58:27 2016
  HibernationDevice: RESUME=UUID=7b4a2bc3-8fd2-4684-b322-2c990980a5ac
  InstallationDate: Installed on 2016-07-26 (20 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  MachineType: MSI MS-7693
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=2aaf2167-aca2-41be-b11e-930925090f92 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970 GAMING (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV22.4:bd12/21/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0:
  dmi.product.name: MS-7693
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1619446] Re: mismatching headers between powerpc/ppc64el and other archs

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  mismatching headers between powerpc/ppc64el and other archs

Status in linux package in Ubuntu:
  Expired

Bug description:
  the header files from linux-libc-dev are causing repsnapper on
  -proposed to FTBFS on powerpc/ppc64el

  I tracked it to 2 include clauses:

  #include 
  #include 

  causing the following error on powerpc/ppc64el builds:

  following errors:

src/printer/custom_baud.cpp: In function 'bool set_custom_baudrate(int, 
int)':
src/printer/custom_baud.cpp:15:19: error: aggregate 
'set_custom_baudrate(int, int)::termios2 options' has incomplete type and 
cannot be defined
   struct termios2 options;
 ^
src/printer/custom_baud.cpp:17:26: error: 'TCGETS2' was not declared in 
this scope
   if ( ioctl( device_fd, TCGETS2, &options ) < 0 ) {
^
src/printer/custom_baud.cpp:27:26: error: 'TCSETS2' was not declared in 
this scope
   if ( ioctl( device_fd, TCSETS2, &options ) < 0 ) {

  Please see bug #1619100 for more info.

  Comparing the powerpc/ppc64el headers to amd64 I found that they seem
  to be missing includes to other headers under asm-generic/

  If I try to add the missing asm-generic headers:

  #include 
  #include 
  #include 
  #include 

  Then the build again fails on both powerpc/ppc64el and succeeds on all
  other archs, this time the error is:

  In file included from src/printer/custom_baud.cpp:11:0:
  /usr/include/asm-generic/termbits.h:11:8: error: redefinition of ‘struct 
termios’
   struct termios {
  ^~~
  In file included from src/printer/custom_baud.cpp:9:0:
  /usr/include/powerpc-linux-gnu/asm/termbits.h:22:8: error: previous 
definition of ‘struct termios’
   struct termios {
  ^~~
  In file included from src/printer/custom_baud.cpp:11:0:
  /usr/include/asm-generic/termbits.h:31:8: error: redefinition of ‘struct 
ktermios’
   struct ktermios {
  ^~~~
  In file included from src/printer/custom_baud.cpp:9:0:
  /usr/include/powerpc-linux-gnu/asm/termbits.h:35:8: error: previous 
definition of ‘struct ktermios’
   struct ktermios {
  ^~~~

  Finally, modifying the original includes to remove the asm/termbits.h:

  #include 
  #include 
  #include 

  Allows for the repsnapper build to succeed on all arches, including
  powerpc/ppc64el. Question is: why is this even needed?

  
  linux-libc-dev packages:
  Get:10 http://ftpmaster.internal/ubuntu yakkety/main powerpc linux-libc-dev 
powerpc 4.4.0-9136.55 [818 kB]
  Get:10 http://ftpmaster.internal/ubuntu yakkety/main ppc64el linux-libc-dev 
ppc64el 4.4.0-9136.55 [818 kB]
  Get:10 http://ftpmaster.internal/ubuntu yakkety/main amd64 linux-libc-dev 
amd64 4.4.0-9136.55 [828 kB]

  Checking the headers is seems that powerpc/ppc64el are missing
  includes for asm-generics:

  $ grep -r TCGETS2 linux-libc-dev_4.4.0-9136.55_*/
  linux-libc-dev_4.4.0-9136.55_amd64/usr/include/asm-generic/ioctls.h:#define 
TCGETS2   _IOR('T', 0x2A, struct termios2)
  linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/asm-generic/ioctls.h:#define 
TCGETS2 _IOR('T', 0x2A, struct termios2)

  $ grep -r ioctls.h linux-libc-dev_4.4.0-9136.55_*/
  
linux-libc-dev_4.4.0-9136.55_amd64/usr/include/x86_64-linux-gnu/asm/ioctls.h:#include
 
  linux-libc-dev_4.4.0-9136.55_amd64/usr/include/asm-generic/termios.h:#include 

  
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/asm-generic/termios.h:#include 

  
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/powerpc64le-linux-gnu/asm/termios.h:#include
 

  $ grep -r "termios2 {" linux-libc-dev_4.4.0-9136.55_*/ 
  linux-libc-dev_4.4.0-9136.55_amd64/usr/include/asm-generic/termbits.h:struct 
termios2 {
  
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/asm-generic/termbits.h:struct 
termios2 {

  $ grep -r termbits.h linux-libc-dev_4.4.0-9136.55_*/  
  
linux-libc-dev_4.4.0-9136.55_amd64/usr/include/x86_64-linux-gnu/asm/termbits.h:#include
 
  linux-libc-dev_4.4.0-9136.55_amd64/usr/include/asm-generic/termios.h:#include 

  
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/asm-generic/termios.h:#include 

  
linux-libc-dev_4.4.0-9136.55_ppc64el/usr/include/powerpc64le-linux-gnu/asm/termios.h:#include
 

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

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

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

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 1611901] Re: Backport Surface 3 touchscreen driver

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]

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

Title:
  Backport Surface 3 touchscreen driver

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

Bug description:
  The surface3_spi touchscreen driver finally hit Linus' kernel tree in
  v4.8rc1. It would be great if this could be backported to the kernels
  that Ubuntu ships.

  The relevant upstream commits should be:
  e399037e06beec6d190a302ff5e4fee4aae77c50 ACPI / scan: set status to 0 if _STA 
failed
  30f3a6ab44d8d06bb3d94f6320e4aa76df59d025 spi: pxa2xx: Add support for both 
chip selects on Intel Braswell
  4feacbc24eea0c5f36728017575cc0ad28d8758b Input: add new driver for the 
Surface 3
  427ee20610a7c252e99d08e08e70a4203c6059d0 Input: surface3_spi - Prepare to add 
support for Surface Pen
  72fb4765ac9eea56a94282f29cdc70706f21494e Input: surface3_spi - add surface 
pen support for Surface 3

  These should hopefully be enough to get the touchscreen working. 4.4
  is a really old kernel, so there might be some additional ACPI fixes
  needed. I'm not 100% certain. This is all that was needed on top of
  4.6.

  Config options needed on i386 and amd64:
  CONFIG_SPI_PXA2XX=m
  CONFIG_PINCTRL_CHERRYVIEW=m
  CONFIG_TOUCHSCREEN_SURFACE3_SPI=m

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.376
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1286:204c Marvell Semiconductor, Inc.
   Bus 001 Device 003: ID 045e:07de Microsoft Corp.
   Bus 001 Device 002: ID 03f0:b107 Hewlett-Packard v255w/c310w Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface 3
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash 
systemd.unit=rescue.target ---
  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: 03/09/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.51116.178
  dmi.board.asset.tag: 0
  dmi.board.name: Surface 3
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.51116.178:bd03/09/2015:svnMicrosoftCorporation:pnSurface3:pvrB16D1SW1C4G1X1:rvnMicrosoftCorporation:rnSurface3:rvr00:cvnMicrosoftCorporation:ct9:cvr1:
  dmi.product.name: Surface 3
  dmi.product.version: B16D1SW1C4G1X1
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1603810] Re: Ubuntu turns monitor permanently off during boot

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu turns monitor permanently off during boot

Status in linux package in Ubuntu:
  Expired

Bug description:
  This is a regression, at least trusty (and prior) worked fine on this
  hardware.

  Booting the Xenial installer image off USB also worked fine.

  The system boots fine, however the monitor is in DPMS power-off and
  does not ever turn back on. Switching VTs doesn't help, I have found
  no way to get it switch on.

  Removing '$vt_handoff' from grub resolves the problem and the system
  seems to work fine.

  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.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jgg2224 F pulseaudio
   /dev/snd/controlC0:  jgg2224 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jul 17 14:04:30 2016
  HibernationDevice: RESUME=UUID=b254872c-e84b-427c-bebe-343c031cbdcd
  InstallationDate: Installed on 2016-04-22 (86 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/main2-xenial64 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MEVO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1611901] Re: Backport Surface 3 touchscreen driver

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu Yakkety) because there has been no activity
for 60 days.]

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

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

Title:
  Backport Surface 3 touchscreen driver

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

Bug description:
  The surface3_spi touchscreen driver finally hit Linus' kernel tree in
  v4.8rc1. It would be great if this could be backported to the kernels
  that Ubuntu ships.

  The relevant upstream commits should be:
  e399037e06beec6d190a302ff5e4fee4aae77c50 ACPI / scan: set status to 0 if _STA 
failed
  30f3a6ab44d8d06bb3d94f6320e4aa76df59d025 spi: pxa2xx: Add support for both 
chip selects on Intel Braswell
  4feacbc24eea0c5f36728017575cc0ad28d8758b Input: add new driver for the 
Surface 3
  427ee20610a7c252e99d08e08e70a4203c6059d0 Input: surface3_spi - Prepare to add 
support for Surface Pen
  72fb4765ac9eea56a94282f29cdc70706f21494e Input: surface3_spi - add surface 
pen support for Surface 3

  These should hopefully be enough to get the touchscreen working. 4.4
  is a really old kernel, so there might be some additional ACPI fixes
  needed. I'm not 100% certain. This is all that was needed on top of
  4.6.

  Config options needed on i386 and amd64:
  CONFIG_SPI_PXA2XX=m
  CONFIG_PINCTRL_CHERRYVIEW=m
  CONFIG_TOUCHSCREEN_SURFACE3_SPI=m

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.376
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1286:204c Marvell Semiconductor, Inc.
   Bus 001 Device 003: ID 045e:07de Microsoft Corp.
   Bus 001 Device 002: ID 03f0:b107 Hewlett-Packard v255w/c310w Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface 3
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash 
systemd.unit=rescue.target ---
  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: 03/09/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.51116.178
  dmi.board.asset.tag: 0
  dmi.board.name: Surface 3
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.51116.178:bd03/09/2015:svnMicrosoftCorporation:pnSurface3:pvrB16D1SW1C4G1X1:rvnMicrosoftCorporation:rnSurface3:rvr00:cvnMicrosoftCorporation:ct9:cvr1:
  dmi.product.name: Surface 3
  dmi.product.version: B16D1SW1C4G1X1
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1613472] Re: Ubuntu doesn't read SD cards

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu doesn't read SD cards

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

Bug description:
  Ubuntu doesn't read SD cards, I use internal card reader in my PC.

  I tried latest mainline kernel and it did not help.

  Before upgrade to this kernel, it worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tomas  3985 F pulseaudio
   /dev/snd/controlC2:  tomas  3985 F pulseaudio
   /dev/snd/controlC0:  tomas  3985 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Aug 16 00:58:27 2016
  HibernationDevice: RESUME=UUID=7b4a2bc3-8fd2-4684-b322-2c990980a5ac
  InstallationDate: Installed on 2016-07-26 (20 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  MachineType: MSI MS-7693
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=2aaf2167-aca2-41be-b11e-930925090f92 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970 GAMING (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV22.4:bd12/21/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0:
  dmi.product.name: MS-7693
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]

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

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

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

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 1611901] Re: Backport Surface 3 touchscreen driver

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Backport Surface 3 touchscreen driver

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

Bug description:
  The surface3_spi touchscreen driver finally hit Linus' kernel tree in
  v4.8rc1. It would be great if this could be backported to the kernels
  that Ubuntu ships.

  The relevant upstream commits should be:
  e399037e06beec6d190a302ff5e4fee4aae77c50 ACPI / scan: set status to 0 if _STA 
failed
  30f3a6ab44d8d06bb3d94f6320e4aa76df59d025 spi: pxa2xx: Add support for both 
chip selects on Intel Braswell
  4feacbc24eea0c5f36728017575cc0ad28d8758b Input: add new driver for the 
Surface 3
  427ee20610a7c252e99d08e08e70a4203c6059d0 Input: surface3_spi - Prepare to add 
support for Surface Pen
  72fb4765ac9eea56a94282f29cdc70706f21494e Input: surface3_spi - add surface 
pen support for Surface 3

  These should hopefully be enough to get the touchscreen working. 4.4
  is a really old kernel, so there might be some additional ACPI fixes
  needed. I'm not 100% certain. This is all that was needed on top of
  4.6.

  Config options needed on i386 and amd64:
  CONFIG_SPI_PXA2XX=m
  CONFIG_PINCTRL_CHERRYVIEW=m
  CONFIG_TOUCHSCREEN_SURFACE3_SPI=m

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.376
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1286:204c Marvell Semiconductor, Inc.
   Bus 001 Device 003: ID 045e:07de Microsoft Corp.
   Bus 001 Device 002: ID 03f0:b107 Hewlett-Packard v255w/c310w Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface 3
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash 
systemd.unit=rescue.target ---
  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: 03/09/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.51116.178
  dmi.board.asset.tag: 0
  dmi.board.name: Surface 3
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.51116.178:bd03/09/2015:svnMicrosoftCorporation:pnSurface3:pvrB16D1SW1C4G1X1:rvnMicrosoftCorporation:rnSurface3:rvr00:cvnMicrosoftCorporation:ct9:cvr1:
  dmi.product.name: Surface 3
  dmi.product.version: B16D1SW1C4G1X1
  dmi.sys.vendor: Microsoft Corporation

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

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

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

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  guest on bridge becomes inaccessible

Status in linux package in Ubuntu:
  Expired

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1629784] Re: Ubuntu16.04 installation failed on IBM LE server

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu16.04 installation failed on IBM LE server

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu OS installation is getting failed on IBM LE server. Please let
  us know whether this is System/OS specific issue.,

  Also please include "christy.rajku...@broadcom.com" in bug_list for
  any further information regarding bug.

  We tried installation with the image("ubuntu-16.04-server-ppc64el") that is 
available 
  under link: http://cdimage.ubuntu.com/releases/16.04.1/release/

  
  Please find the error message below.
   
   
   
   GNU GRUB  version 2.02~beta2-36ubuntu3
   
   
++
   |*Install
|
   | Rescue mode
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   
++
   
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, `e' to edit the commands
before booting or `c' for a command-line.
  '
   
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) 
(gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon 
Apr 18 18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)
  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=/install/vmlinux tasks=standard 
pkgsel/language-pack-patterns= pkgsel/install-language-support=false --- quiet
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0ad4
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0eb8... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0ad5 -> 0x0ad5197e
  Device tree struct  0x0ad6 -> 0x0adb
   -> smp_release_cpus()
  spinning_secondaries = 191
   <- smp_release_cpus()
   <- setup_system()
  [1.277480] pci 0005:50:00.0: of_irq_parse_pci() failed with rc=-22
  [1.490146] pci 0007:80:00.0: of_irq_parse_pci() failed with rc=-22
  [3.611923] genirq: Flags mismatch irq 16.  (hvc_console) vs. 
 (hvsi)
  [3.611954] hvc_open: request_irq failed with rc -16.
  [3.611981] Warning: unable to open an initial console.
  Starting system log daemon: syslogd, klogd.

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

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

[Kernel-packages] [Bug 1643533] Re: Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely)

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]

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

Title:
  Frequent kernel panic crashes in Linux KVM guest  (happens on
  different host hardware, so hardware fault unlikely)

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

Bug description:
  With Ubuntu 16.04, I get frequent kernel panic crashes in my Linux KVM
  guest. After notifying the hosting company the machine was migrated to
  a different physical host which didn't fix the problem. A complete
  reinstall of Ubuntu 16.04 also didn't fix anything. Therefore, I
  suspect some sort of bug in the kernel and not a hardware fault or a
  corrupted install.

  /proc/version_signature: Ubuntu 4.4.0-47.68-generic 4.4.24

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 21 12:51 seq
   crw-rw 1 root audio 116, 33 Nov 21 12:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Mon Nov 21 12:57:11 2016
  HibernationDevice: RESUME=UUID=704a373a-9754-4c59-bff2-001601f1c0bf
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hetzner vServer
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic 
root=UUID=fc92f1ac-ee98-4991-8a92-93451bd36d56 ro nomodeset elevator=noop 
net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.8.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.8.2:bd04/01/2014:svnHetzner:pnvServer:pvr2:cvnQEMU:ct1:cvrpc-i440fx-2.6:
  dmi.product.name: vServer
  dmi.product.version: 2
  dmi.sys.vendor: Hetzner

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

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

[Kernel-packages] [Bug 1632902] Re: kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]

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

Title:
  kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

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

Bug description:
  This occurred after rebooting after running Kubuntu's Update Manager
  5.6.2 on 2016-10-12. Unfortunately, I hadn't rebooted after the last
  update that required me to do so, and thus I don't know if the problem
  was from that update or this one.

  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/controlC1:  jacob  1494 F pulseaudio
   /dev/snd/controlC0:  jacob  1494 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Oct 12 19:54:03 2016
  HibernationDevice: RESUME=UUID=c5fdca37-edfe-4f31-928b-970bd6696164
  InstallationDate: Installed on 2016-05-25 (140 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=c70ba36b-21e9-48ae-bf12-79060d17dcfc ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/02/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1633391] Re: Ubuntu doesn't boot anymore {REGRESSION}

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu doesn't boot anymore {REGRESSION}

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

Bug description:
  After I upgraded to latest kernel, Ubuntu does not boot without messing with 
grub (I had to delete quiet splash options). 
  Before upgrade it was OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tomas  2090 F pulseaudio
   /dev/snd/controlC1:  tomas  2090 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 14 11:32:56 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ff267c2-ec30-4f81-975c-46640f436942
  InstallationDate: Installed on 2016-09-13 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 10104
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-42-generic 
root=UUID=fd50bb86-da1a-45bb-957b-ea19b330d7ff ro rootflags=subvol=@ 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT31AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10104
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1632902] Re: kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

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

Bug description:
  This occurred after rebooting after running Kubuntu's Update Manager
  5.6.2 on 2016-10-12. Unfortunately, I hadn't rebooted after the last
  update that required me to do so, and thus I don't know if the problem
  was from that update or this one.

  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/controlC1:  jacob  1494 F pulseaudio
   /dev/snd/controlC0:  jacob  1494 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Oct 12 19:54:03 2016
  HibernationDevice: RESUME=UUID=c5fdca37-edfe-4f31-928b-970bd6696164
  InstallationDate: Installed on 2016-05-25 (140 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=c70ba36b-21e9-48ae-bf12-79060d17dcfc ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/02/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1643533] Re: Frequent kernel panic crashes in Linux KVM guest (happens on different host hardware, so hardware fault unlikely)

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Frequent kernel panic crashes in Linux KVM guest  (happens on
  different host hardware, so hardware fault unlikely)

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

Bug description:
  With Ubuntu 16.04, I get frequent kernel panic crashes in my Linux KVM
  guest. After notifying the hosting company the machine was migrated to
  a different physical host which didn't fix the problem. A complete
  reinstall of Ubuntu 16.04 also didn't fix anything. Therefore, I
  suspect some sort of bug in the kernel and not a hardware fault or a
  corrupted install.

  /proc/version_signature: Ubuntu 4.4.0-47.68-generic 4.4.24

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 21 12:51 seq
   crw-rw 1 root audio 116, 33 Nov 21 12:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Mon Nov 21 12:57:11 2016
  HibernationDevice: RESUME=UUID=704a373a-9754-4c59-bff2-001601f1c0bf
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hetzner vServer
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic 
root=UUID=fc92f1ac-ee98-4991-8a92-93451bd36d56 ro nomodeset elevator=noop 
net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.8.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.8.2:bd04/01/2014:svnHetzner:pnvServer:pvr2:cvnQEMU:ct1:cvrpc-i440fx-2.6:
  dmi.product.name: vServer
  dmi.product.version: 2
  dmi.sys.vendor: Hetzner

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

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

[Kernel-packages] [Bug 1641127] Re: Network interface is not coming up

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]

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

Title:
  Network interface is not coming up

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

Bug description:
  Fresh installation of Ubuntu 16.04 and even after executing ifconfig
   up, the network interface is not coming up. Below are the
  kernel and driver details:

  lsb_release -rd
  Description:Ubuntu 16.04
  Release:16.04

  cat /proc/version_signature
  Ubuntu 4.4.0-47.68-generic 4.4.24

  sudo lspci -vnvn > lspci-vnvn.log
  Attached the .log file

  Basically bnxt_en driver needs to be updated with latest HWRM spec.

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

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

[Kernel-packages] [Bug 1633391] Re: Ubuntu doesn't boot anymore {REGRESSION}

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]

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

Title:
  Ubuntu doesn't boot anymore {REGRESSION}

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

Bug description:
  After I upgraded to latest kernel, Ubuntu does not boot without messing with 
grub (I had to delete quiet splash options). 
  Before upgrade it was OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tomas  2090 F pulseaudio
   /dev/snd/controlC1:  tomas  2090 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 14 11:32:56 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ff267c2-ec30-4f81-975c-46640f436942
  InstallationDate: Installed on 2016-09-13 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 10104
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-42-generic 
root=UUID=fd50bb86-da1a-45bb-957b-ea19b330d7ff ro rootflags=subvol=@ 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT31AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10104
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1641127] Re: Network interface is not coming up

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Network interface is not coming up

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

Bug description:
  Fresh installation of Ubuntu 16.04 and even after executing ifconfig
   up, the network interface is not coming up. Below are the
  kernel and driver details:

  lsb_release -rd
  Description:Ubuntu 16.04
  Release:16.04

  cat /proc/version_signature
  Ubuntu 4.4.0-47.68-generic 4.4.24

  sudo lspci -vnvn > lspci-vnvn.log
  Attached the .log file

  Basically bnxt_en driver needs to be updated with latest HWRM spec.

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

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

[Kernel-packages] [Bug 1643622] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu Yakkety) because there has been no activity
for 60 days.]

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

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

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

Bug description:
  Lenova x260 i7 laptop - screen blanks for < 1 second when this happens

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 21 16:49:37 2016
  HibernationDevice: RESUME=UUID=2a2aa818-8baa-4c43-9dad-51997def38f8
  InstallationDate: Installed on 2016-11-06 (15 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20F6CTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=a1b30635-761b-43ba-af92-7e41dcb3968c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET48W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F6CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET48W(1.21):bd06/01/2016:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20F6CTO1WW
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1643622] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

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

Bug description:
  Lenova x260 i7 laptop - screen blanks for < 1 second when this happens

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 21 16:49:37 2016
  HibernationDevice: RESUME=UUID=2a2aa818-8baa-4c43-9dad-51997def38f8
  InstallationDate: Installed on 2016-11-06 (15 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20F6CTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=a1b30635-761b-43ba-af92-7e41dcb3968c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET48W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F6CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET48W(1.21):bd06/01/2016:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20F6CTO1WW
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1658697] Re: package linux-image-3.13.0-107-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2017-03-27 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

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

Status in linux package in Ubuntu:
  Expired

Bug description:
  The software updater fails when used therefore I can't update the lubuntu 
system.
  Hope this can sorted as ubuntu is a very stable OS.
  Thanks.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-107-generic (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mike   1385 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Mon Jan 23 14:09:24 2017
  DpkgHistoryLog:
   Start-Date: 2017-01-23  14:09:18
   Commandline: apt-get -f install
   Install: linux-headers-3.13.0-107:i386 (3.13.0-107.154, automatic), 
linux-image-extra-3.13.0-107-generic:i386 (3.13.0-107.154, automatic), 
linux-headers-3.13.0-107-generic:i386 (3.13.0-107.154, automatic), 
linux-image-3.13.0-107-generic:i386 (3.13.0-107.154, automatic), 
linux-image-3.13.0-105-generic:i386 (3.13.0-105.152, automatic)
   Upgrade: linux-generic:i386 (3.13.0.105.113, 3.13.0.107.115), 
linux-image-generic:i386 (3.13.0.105.113, 3.13.0.107.115), 
linux-headers-generic:i386 (3.13.0.105.113, 3.13.0.107.115)
  DpkgTerminalLog:
   Preparing to unpack 
.../linux-image-3.13.0-107-generic_3.13.0-107.154_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-3.13.0-107-generic_3.13.0-107.154_i386.deb 
(--unpack):
subprocess new pre-installation script returned error exit status 1
  DuplicateSignature: package:linux-image-3.13.0-107-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=8ea04b59-9c47-4d88-b7c2-9e999ce1435b
  InstallationDate: Installed on 2016-11-16 (68 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Samsung Electronics Aquila Slim Platform
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=7a8e48cc-a123-4e05-85b6-4187292d7699 ro rootflags=sync quiet splash 
vt.handoff=7
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-3.13.0-107-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 09/17/2003
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 02VE
  dmi.board.name: Aquila Slim Platform
  dmi.board.vendor: Samsung Electronics
  dmi.board.version: Revision 01
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Samsung Electronics
  dmi.chassis.version: revision 1.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr02VE:bd09/17/2003:svnSamsungElectronics:pnAquilaSlimPlatform:pvrRevision01:rvnSamsungElectronics:rnAquilaSlimPlatform:rvrRevision01:cvnSamsungElectronics:ct10:cvrrevision1.0:
  dmi.product.name: Aquila Slim Platform
  dmi.product.version: Revision 01
  dmi.sys.vendor: Samsung Electronics

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

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

[Kernel-packages] [Bug 1676209] Re: VM crashes after saving and restoring with latest kernel

2017-03-27 Thread Blake Cottington 
** Attachment added: "Linux4.4.0-71jsalisburyNoCrash.gif"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676209/+attachment/4848321/+files/Linux4.4.0-71jsalisburyNoCrash.gif

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

Title:
  VM crashes after saving and restoring with latest kernel

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

Bug description:
  After upgrading my Ubuntu Hyper-V VM to the latest kernel
  (4.4.0-67-generic, Ubuntu 16.04.2 LTS), it started crashing after
  saving and restoring it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-67-generic 4.4.0-67.88
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Mar 26 20:49 seq
   crw-rw+ 1 root audio 116, 33 Mar 26 20:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sun Mar 26 20:51:29 2017
  HibernationDevice: RESUME=/dev/mapper/HUGVWEB01--vg-swap_1
  InstallationDate: Installed on 2015-10-29 (514 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro elevator=noop
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-67-generic N/A
   linux-backports-modules-4.4.0-67-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-02-23 (31 days ago)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0559-3398-3600-3623-3585-8903-93
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Mar 26 21:13 seq
   crw-rw+ 1 root audio 116, 33 Mar 26 21:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/HUGVWEB01--vg-swap_1
  InstallationDate: Installed on 2015-10-29 (514 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro elevator=noop
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-67-generic N/A
   linux-backports-modules-4.4.0-67-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-67-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-02-23 (31 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-adressverwaltung
  _MarkForUpload: False
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corpor

[Kernel-packages] [Bug 1676209] Re: VM crashes after saving and restoring with latest kernel

2017-03-27 Thread Blake Cottington 
More info: Host is Server 2016. Guest is Generation 2 type. Dynamic
memory is not enabled.

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

Title:
  VM crashes after saving and restoring with latest kernel

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

Bug description:
  After upgrading my Ubuntu Hyper-V VM to the latest kernel
  (4.4.0-67-generic, Ubuntu 16.04.2 LTS), it started crashing after
  saving and restoring it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-67-generic 4.4.0-67.88
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Mar 26 20:49 seq
   crw-rw+ 1 root audio 116, 33 Mar 26 20:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sun Mar 26 20:51:29 2017
  HibernationDevice: RESUME=/dev/mapper/HUGVWEB01--vg-swap_1
  InstallationDate: Installed on 2015-10-29 (514 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro elevator=noop
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-67-generic N/A
   linux-backports-modules-4.4.0-67-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-02-23 (31 days ago)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0559-3398-3600-3623-3585-8903-93
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Mar 26 21:13 seq
   crw-rw+ 1 root audio 116, 33 Mar 26 21:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/HUGVWEB01--vg-swap_1
  InstallationDate: Installed on 2015-10-29 (514 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro elevator=noop
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-67-generic N/A
   linux-backports-modules-4.4.0-67-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-67-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-02-23 (31 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-adressverwaltung
  _MarkForUpload: False
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0559-3398-3600-3

[Kernel-packages] [Bug 1676209] Re: VM crashes after saving and restoring with latest kernel

2017-03-27 Thread Blake Cottington 
Hi, I know this isn't my thread but I'm trying to help. I am seeing the
crash of the VM during a Windows Server Backup with the latest kernel
4.4.0-67. I installed the kernel from comment 42 referenced in the other
thread. It did make a difference. I will post screenshots of the
results.

Side note - I am a noob to installing patches like this. I tried using the 3rd 
technique here:
https://wiki.ubuntu.com/Kernel/Dev/KernelTesting

and pointed to: http://kernel.ubuntu.com/~jsalisbury/lp1674635/revert/

then did apt-get update, but I got a message similar to this:
W: The repository '...' does not have a Release file.
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.
E: Failed to fetch ...  404  Not Found
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

So... I did wget and dpkg -i for each of the 12 files in the directory.

** Attachment added: "Linux4.4.0-67Crash.gif"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676209/+attachment/4848320/+files/Linux4.4.0-67Crash.gif

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

Title:
  VM crashes after saving and restoring with latest kernel

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

Bug description:
  After upgrading my Ubuntu Hyper-V VM to the latest kernel
  (4.4.0-67-generic, Ubuntu 16.04.2 LTS), it started crashing after
  saving and restoring it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-67-generic 4.4.0-67.88
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Mar 26 20:49 seq
   crw-rw+ 1 root audio 116, 33 Mar 26 20:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sun Mar 26 20:51:29 2017
  HibernationDevice: RESUME=/dev/mapper/HUGVWEB01--vg-swap_1
  InstallationDate: Installed on 2015-10-29 (514 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro elevator=noop
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-67-generic N/A
   linux-backports-modules-4.4.0-67-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-02-23 (31 days ago)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0559-3398-3600-3623-3585-8903-93
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Mar 26 21:13 seq
   crw-rw+ 1 root audio 116, 33 Mar 26 21:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/HUGVWEB01--vg-swap_1
  InstallationDate: Installed on 2015-10-29 (514 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linu

[Kernel-packages] [Bug 1676078] Re: Touchpad is not recognized (ASUS X556U)

2017-03-27 Thread Kai-Heng Feng 
Can you try adding 'i8042.noloop=1' or 'i8042.nomux=1' or
'i8042.nopnp=1' to kernel parameter?

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

Title:
  Touchpad is not recognized (ASUS X556U)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad doesnt work and it isnt recongnized.

  Xinput (USB optical mouse is another USB mouse connected)

  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ USB Optical Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Asus Wireless Radio Control id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Video Bus   id=9[slave  
keyboard (3)]
  ↳ Sleep Buttonid=10   [slave  
keyboard (3)]
  ↳ USB Camera  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]

  lspci
  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 08)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
  00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 08)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#5 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940M] (rev a2)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
  03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 30)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-41-generic 4.8.0-41.44
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brujo  2424 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Mar 25 12:45:42 2017
  HibernationDevice: RESUME=UUID=5a7d3492-03cf-436b-ab0c-7e85013a018d
  InstallationDate: Installed on 2017-01-30 (54 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X556UB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic.efi.signed 
root=UUID=67f6eec2-c5b9-4465-a985-87e85a5f86bf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-41-generic N/A
   linux-backports-modules-4.8.0-41-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UB.405
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UB
  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.:bvrX556UB.405:bd06/28/2

[Kernel-packages] [Bug 1645951] Re: [Feature] GLK:New device IDs

2017-03-27 Thread quanxian 
NPK: 0x318e v4.11-rc4 340837f985

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

Title:
  [Feature] GLK:New device IDs

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Placeholder for GLK(Gemini Lake) IDs that should be published.
  USB device/xDCI: 0x31aa
  LPC: 0x31e8
  SPI-NOR: 0x3196
  PWM: 0x31c8
  SMBus: 0x31d4
  I2C: 0x31ac 0x31ae 0x31b0 0x31b2 0x31b4 0x31b6 0x31b8 0x31ba
  HS-UART: 0x31bc 0x31be 0x31c0 0x31ee
  SPI: 0x31c2 0x31c4 0x31c6
  GPIO: INT3453
  SD Card: 0x31ca
  eMMC: 0x31cc
  SDIO: 0x31d0
  UFS: 0x31ce
  NPK: 0x318e

  HW:
  Gemini Lake

  Upstream Schedule:
  kernel: TBD

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

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

[Kernel-packages] [Bug 1673350] Re: dm-queue-length module is not included in installer/initramfs

2017-03-27 Thread Mathieu Trudel-Lapierre 
The hw-detect change is uploaded, so once it's in the archive, installs
on hardware requiring dm-queue-length should work without issues.

We're still blocked on having the kernel include dm-queue-length and dm-
service-time for the installer for the hw-detect side of this SRU to
yakkety and xenial.

As for the multipath-tools part of the SRUs, I'll upload them in the
morning.

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in hw-detect source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in multipath-tools source package in Xenial:
  New
Status in hw-detect source package in Yakkety:
  New
Status in initramfs-tools source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  New
Status in multipath-tools source package in Yakkety:
  New

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+subscriptions

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

[Kernel-packages] [Bug 1673350] Re: dm-queue-length module is not included in installer/initramfs

2017-03-27 Thread Mathieu Trudel-Lapierre 
** Changed in: hw-detect (Ubuntu)
   Status: Triaged => 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/1673350

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in hw-detect source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in multipath-tools source package in Xenial:
  New
Status in hw-detect source package in Yakkety:
  New
Status in initramfs-tools source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  New
Status in multipath-tools source package in Yakkety:
  New

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+subscriptions

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

[Kernel-packages] [Bug 1676678] libvirt guest xml for dotg6

2017-03-27 Thread bugproxy 
Default Comment by Bridge

** Attachment added: "libvirt guest xml for dotg6"
   
https://bugs.launchpad.net/bugs/1676678/+attachment/4848267/+files/file_152796.txt

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

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

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

Title:
  ISST-LTE:dotg6:Kernel access of bad area, sig: 11 - during stress
  tests

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  After running stress tests (IO, TCP, BASE) for a few hours, Ubuntu 17.04 KVM 
guest dotg6 crashed, produced a kdump, and rebooted.
   
  ---uname output---
  Linux dotg6 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = KVM guest on a 8247-22L (host also running Ubuntu 17.04) 
   
   Stack trace output:
   [ 1909.621800] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 1909.621870] SMP NR_CPUS=2048
  [ 1909.621871] NUMA
  [ 1909.621925] pSeries
  [ 1909.622016] Modules linked in: minix nls_iso8859_1 rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache binfmt_misc xfs libcrc32c vmx_crypto 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq dm_service_time 
crc32c_vpmsum virtio_scsi virtio_net scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [ 1909.622401] CPU: 2 PID: 27704 Comm: ppc64_cpu Not tainted 
4.10.0-13-generic #15-Ubuntu
  [ 1909.622536] task: c00042a64200 task.stack: c0003423c000
  [ 1909.622627] NIP: d16a14f4 LR: d16a14a0 CTR: 
c0609d00
  [ 1909.622737] REGS: c0003423f7f0 TRAP: 0380   Not tainted  
(4.10.0-13-generic)
  [ 1909.622850] MSR: 8280b033 
  [ 1909.622860]   CR: 24002428  XER: 2000
  [ 1909.623016] CFAR: c061a238 SOFTE: 1
  [ 1909.623016] GPR00: d16a14a0 c0003423fa70 d16ab8cc 
c00170fd5000
  [ 1909.623016] GPR04:    
7530
  [ 1909.623016] GPR08: c146c700 757465736d642f6e c146dbe0 
d16a2ef8
  [ 1909.623016] GPR12: c0609d00 c1b81200 0008 
0001
  [ 1909.623016] GPR16:    
46f05f80
  [ 1909.623016] GPR20: 46f061f8  46f05f58 
c0017fd4a808
  [ 1909.623016] GPR24: 0001 c00170fc7a30 c1326eb0 
d16a1648
  [ 1909.623016] GPR28: c1471c28 c00170fc7860 71ae4a20 
0058
  [ 1909.623990] NIP [d16a14f4] __virtscsi_set_affinity+0xac/0x200 
[virtio_scsi]
  [ 1909.624114] LR [d16a14a0] __virtscsi_set_affinity+0x58/0x200 
[virtio_scsi]
  [ 1909.624235] Call Trace:
  [ 1909.624278] [c0003423fa70] [d16a14a0] 
__virtscsi_set_affinity+0x58/0x200 [virtio_scsi] (unreliable)
  [ 1909.624445] [c0003423fac0] [d16a1678] 
virtscsi_cpu_online+0x30/0x70 [virtio_scsi]
  [ 1909.624746] [c0003423fae0] [c00db73c] 
cpuhp_invoke_callback+0x3ec/0x5a0
  [ 1909.624887] [c0003423fb50] [c00dba88] 
cpuhp_down_callbacks+0x78/0xf0
  [ 1909.625037] [c0003423fba0] [c0268bb0] _cpu_down+0x150/0x1b0
  [ 1909.625174] [c0003423fc00] [c00de1b4] do_cpu_down+0x64/0xb0
  [ 1909.625330] [c0003423fc40] [c074b834] 
cpu_subsys_offline+0x24/0x40
  [ 1909.625485] [c0003423fc60] [c0743284] device_offline+0xf4/0x130
  [ 1909.625610] [c0003423fca0] [c0743434] online_store+0x64/0xb0
  [ 1909.625736] [c0003423fce0] [c073e37c] dev_attr_store+0x3c/0x60
  [ 1909.625862] [c0003423fd00] [c03faa18] sysfs_kf_write+0x68/0xa0
  [ 1909.625984] [c0003423fd20] [c03f98bc] 
kernfs_fop_write+0x17c/0x250
  [ 1909.626132] [c0003423fd70] [c033c98c] __vfs_write+0x3c/0x70
  [ 1909.626253] [c0003423fd90] [c033e414] vfs_write+0xd4/0x240
  [ 1909.626374] [c0003423fde0] [c033ffc8] SyS_write+0x68/0x110
  [ 1909.626501] [c0003423fe30] [c000b184] system_call+0x38/0xe0
  [ 1909.626624] Instruction dump:
  [ 1909.626691] 2f89 419e0064 3be0 393f0021 3880 792926e4 7d3d4a14 
e9290010
  [ 1909.626835] 2fa9 7d234b78 419e002c e9290020  e9290058 
2fa9 7d2c4b78
  [ 1909.627003] ---[ end trace ecc8a323beb021a2 ]---

   
  crash>  bt
  PID: 27704  TASK: c00042a64200  CPU: 2   COMMAND: "ppc64_cpu"
   #0 [c0003423f630] crash_kexec at c01a04c4
   #1 [c0003423f670] oops_end at c0024da8
   #2 [c0003423f6f0] bad_page_fault at c00627b0
   #3 [c0003423f760] slb_miss_bad_addr at c0026828
   #4 [c0003423f780] bad_addr_slb at c0008acc
   Data SLB Access [380] exception frame:
   R0:  d16a14a0R1:  c0003423fa70R2:  d16ab8cc   
   R3:

[Kernel-packages] [Bug 1676678] [NEW] ISST-LTE:dotg6:Kernel access of bad area, sig: 11 - during stress tests

2017-03-27 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

---Problem Description---
After running stress tests (IO, TCP, BASE) for a few hours, Ubuntu 17.04 KVM 
guest dotg6 crashed, produced a kdump, and rebooted.
 
---uname output---
Linux dotg6 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = KVM guest on a 8247-22L (host also running Ubuntu 17.04) 
 
 Stack trace output:
 [ 1909.621800] Oops: Kernel access of bad area, sig: 11 [#1]
[ 1909.621870] SMP NR_CPUS=2048
[ 1909.621871] NUMA
[ 1909.621925] pSeries
[ 1909.622016] Modules linked in: minix nls_iso8859_1 rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache binfmt_misc xfs libcrc32c vmx_crypto 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq dm_service_time 
crc32c_vpmsum virtio_scsi virtio_net scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
[ 1909.622401] CPU: 2 PID: 27704 Comm: ppc64_cpu Not tainted 4.10.0-13-generic 
#15-Ubuntu
[ 1909.622536] task: c00042a64200 task.stack: c0003423c000
[ 1909.622627] NIP: d16a14f4 LR: d16a14a0 CTR: c0609d00
[ 1909.622737] REGS: c0003423f7f0 TRAP: 0380   Not tainted  
(4.10.0-13-generic)
[ 1909.622850] MSR: 8280b033 
[ 1909.622860]   CR: 24002428  XER: 2000
[ 1909.623016] CFAR: c061a238 SOFTE: 1
[ 1909.623016] GPR00: d16a14a0 c0003423fa70 d16ab8cc 
c00170fd5000
[ 1909.623016] GPR04:    
7530
[ 1909.623016] GPR08: c146c700 757465736d642f6e c146dbe0 
d16a2ef8
[ 1909.623016] GPR12: c0609d00 c1b81200 0008 
0001
[ 1909.623016] GPR16:    
46f05f80
[ 1909.623016] GPR20: 46f061f8  46f05f58 
c0017fd4a808
[ 1909.623016] GPR24: 0001 c00170fc7a30 c1326eb0 
d16a1648
[ 1909.623016] GPR28: c1471c28 c00170fc7860 71ae4a20 
0058
[ 1909.623990] NIP [d16a14f4] __virtscsi_set_affinity+0xac/0x200 
[virtio_scsi]
[ 1909.624114] LR [d16a14a0] __virtscsi_set_affinity+0x58/0x200 
[virtio_scsi]
[ 1909.624235] Call Trace:
[ 1909.624278] [c0003423fa70] [d16a14a0] 
__virtscsi_set_affinity+0x58/0x200 [virtio_scsi] (unreliable)
[ 1909.624445] [c0003423fac0] [d16a1678] 
virtscsi_cpu_online+0x30/0x70 [virtio_scsi]
[ 1909.624746] [c0003423fae0] [c00db73c] 
cpuhp_invoke_callback+0x3ec/0x5a0
[ 1909.624887] [c0003423fb50] [c00dba88] 
cpuhp_down_callbacks+0x78/0xf0
[ 1909.625037] [c0003423fba0] [c0268bb0] _cpu_down+0x150/0x1b0
[ 1909.625174] [c0003423fc00] [c00de1b4] do_cpu_down+0x64/0xb0
[ 1909.625330] [c0003423fc40] [c074b834] 
cpu_subsys_offline+0x24/0x40
[ 1909.625485] [c0003423fc60] [c0743284] device_offline+0xf4/0x130
[ 1909.625610] [c0003423fca0] [c0743434] online_store+0x64/0xb0
[ 1909.625736] [c0003423fce0] [c073e37c] dev_attr_store+0x3c/0x60
[ 1909.625862] [c0003423fd00] [c03faa18] sysfs_kf_write+0x68/0xa0
[ 1909.625984] [c0003423fd20] [c03f98bc] 
kernfs_fop_write+0x17c/0x250
[ 1909.626132] [c0003423fd70] [c033c98c] __vfs_write+0x3c/0x70
[ 1909.626253] [c0003423fd90] [c033e414] vfs_write+0xd4/0x240
[ 1909.626374] [c0003423fde0] [c033ffc8] SyS_write+0x68/0x110
[ 1909.626501] [c0003423fe30] [c000b184] system_call+0x38/0xe0
[ 1909.626624] Instruction dump:
[ 1909.626691] 2f89 419e0064 3be0 393f0021 3880 792926e4 7d3d4a14 
e9290010
[ 1909.626835] 2fa9 7d234b78 419e002c e9290020  e9290058 2fa9 
7d2c4b78
[ 1909.627003] ---[ end trace ecc8a323beb021a2 ]---

 
crash>  bt
PID: 27704  TASK: c00042a64200  CPU: 2   COMMAND: "ppc64_cpu"
 #0 [c0003423f630] crash_kexec at c01a04c4
 #1 [c0003423f670] oops_end at c0024da8
 #2 [c0003423f6f0] bad_page_fault at c00627b0
 #3 [c0003423f760] slb_miss_bad_addr at c0026828
 #4 [c0003423f780] bad_addr_slb at c0008acc
 Data SLB Access [380] exception frame:
 R0:  d16a14a0R1:  c0003423fa70R2:  d16ab8cc   
 R3:  c00170fd5000R4:  R5:     
 R6:  R7:  7530R8:  c146c700   
 R9:  757465736d642f6eR10: c146dbe0R11: d16a2ef8   
 R12: c0609d00R13: c1b81200R14: 0008   
 R15: 0001R16: R17:    
 R18: R19: 46f05f80R20: 46f061f8   
 R21: R22: 46f05f58R23: c0017fd4a808   
 R24: 0001R25: c00170fc7a30R26: c1326eb0   
 R27: d16a1648R28: c1471c28R29: c00170fc7860   
 R30: 7

[Kernel-packages] [Bug 1676635] Re: [Hyper-V] Implement Hyper-V PTP Source

2017-03-27 Thread Joshua R. Poulson 
This patch needs the CONFIG_PTP_1588_CLOCK flag set in the kernel
config.

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

Title:
  [Hyper-V] Implement Hyper-V PTP Source

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

Bug description:
  Please include the following upstream commit into lts-xenial, 16.04
  HWE, Yakkity, and Zesty. This will improve the behavior of timesync on
  Hyper-V hosts while simultaneously using network time sync protocols
  like NTP.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/hv_util.c?id=3716a49a81ba19dda7202633a68b28564ba95eb5

  commit 3716a49a81ba19dda7202633a68b28564ba95eb5
  Author: Vitaly Kuznetsov 
  Date:   Sat Feb 4 09:57:14 2017 -0700

  hv_utils: implement Hyper-V PTP source

  With TimeSync version 4 protocol support we started updating system time
  continuously through the whole lifetime of Hyper-V guests. Every 5 seconds
  there is a time sample from the host which triggers do_settimeofday[64]().
  While the time from the host is very accurate such adjustments may cause
  issues:
  - Time is jumping forward and backward, some applications may misbehave.
  - In case an NTP server runs in parallel and uses something else for time
    sync (network, PTP,...) system time will never converge.
  - Systemd starts annoying you by printing "Time has been changed" every 5
    seconds to the system log.

  Instead of doing in-kernel time adjustments offload the work to an
  NTP client by exposing TimeSync messages as a PTP device. Users may now
  decide what they want to use as a source.

  I tested the solution with chrony, the config was:

   refclock PHC /dev/ptp0 poll 3 dpoll -2 offset 0

  The result I'm seeing is accurate enough, the time delta between the guest
  and the host is almost always within [-10us, +10us], the in-kernel 
solution
  was giving us comparable results.

  I also tried implementing PPS device instead of PTP by using not currently
  used Hyper-V synthetic timers (we use only one of four for clockevent) but
  with PPS source only chrony wasn't able to give me the required accuracy,
  the delta often more that 100us.

  Signed-off-by: Vitaly Kuznetsov 
  Signed-off-by: K. Y. Srinivasan 
  Signed-off-by: Greg Kroah-Hartman 

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

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

[Kernel-packages] [Bug 1654319] Re: kernel BUG at /build/linux-_qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413

2017-03-27 Thread Shrikrishna Khare 
My VMs are running hwversion 13 on 6.5 (for several days now), but
haven't hit this issue yet.

Thanks for the vmss, cryptz.

To analyze this, also need access to ex.vmem, could you please provide
that? It should have been created in the same directory as vmss when you
suspended the VM.

Do you how I can get vmlinux (debug symbols) corresponding to which
distro version (16.10?) and kernel you were running?

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

Title:
  kernel BUG at /build/linux-
  _qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello everyone,

  I have jenkins installed with an apache frontend. Sometimes, after
  making few GET requests whole system crashes and restarts.

  ESXi host version 6.5, virtual hardware version 13.

  I've found similar bug report here
  https://bugzilla.kernel.org/show_bug.cgi?id=191201

  
  [ 6544.559660] [ cut here ]
  [ 6544.559694] kernel BUG at 
/build/linux-_qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413!
  [ 6544.559728] invalid opcode:  [#1] SMP
  [ 6544.559745] Modules linked in: xt_multiport vmw_vsock_vmci_transport vsock 
ppdev vmw_balloon joydev coretemp input_leds serio_raw nfit shpchp i2c_piix4 
vmw_vmci parport_pc parport mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables 
nf_conntrack_netbios_ns ib_iser rdma_cm nf_conntrack_broadcast iw_cm nf_nat_ftp 
ib_cm nf_nat ib_core nf_conntrack_ftp nf_conntrack iptable_filter configfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic
  [ 6544.560172]  usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
vmwgfx ttm aesni_intel aes_x86_64 lrw glue_helper ablk_helper cryptd 
drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops vmxnet3 
ahci libahci mptspi drm mptscsih mptbase scsi_transport_spi pata_acpi fjes
  [ 6544.560332] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.8.0-32-generic 
#34-Ubuntu
  [ 6544.560360] Hardware name: VMware, Inc. VMware Virtual Platform/440BX 
Desktop Reference Platform, BIOS 6.00 04/05/2016
  [ 6544.560399] task: a172f62a0d00 task.stack: a172f62ac000
  [ 6544.560422] RIP: 0010:[]  [] 
vmxnet3_rq_rx_complete+0x8d1/0xeb0 [vmxnet3]
  [ 6544.560465] RSP: 0018:a172ffc83dc8  EFLAGS: 00010297
  [ 6544.560487] RAX:  RBX:  RCX: 
a172efb8a000
  [ 6544.560513] RDX: 0040 RSI: 0001 RDI: 
0040
  [ 6544.560540] RBP: a172ffc83e40 R08: 0002 R09: 
0030
  [ 6544.560566] R10:  R11: a172ec950880 R12: 
a172f35cc280
  [ 6544.560593] R13: a172ec951400 R14: a172f1c83000 R15: 
a172f2b1c000
  [ 6544.560621] FS:  () GS:a172ffc8() 
knlGS:
  [ 6544.560650] CS:  0010 DS:  ES:  CR0: 80050033
  [ 6544.560671] CR2: 7f742a78da30 CR3: 00022f962000 CR4: 
06e0
  [ 6544.560752] Stack:
  [ 6544.560766]  a172ec950880 a172ec950880  
a172ec950880
  [ 6544.560803]  002d a172ec951420 0002 
00010040
  [ 6544.560837]  a172ec9514e8  a172ec950880 
a172ec951420
  [ 6544.560872] Call Trace:
  [ 6544.561677]  
  [ 6544.561689]  [] vmxnet3_poll_rx_only+0x3a/0xb0 [vmxnet3]
  [ 6544.563233]  [] net_rx_action+0x238/0x380
  [ 6544.564004]  [] __do_softirq+0x10d/0x298
  [ 6544.564757]  [] irq_exit+0xa3/0xb0
  [ 6544.565499]  [] do_IRQ+0x54/0xd0
  [ 6544.566224]  [] common_interrupt+0x82/0x82
  [ 6544.566928]  
  [ 6544.566940]  [] ? native_safe_halt+0x6/0x10
  [ 6544.568313]  [] default_idle+0x20/0xd0
  [ 6544.568978]  [] arch_cpu_idle+0xf/0x20
  [ 6544.569625]  [] default_idle_call+0x2a/0x40
  [ 6544.570255]  [] cpu_startup_entry+0x2ec/0x350
  [ 6544.570871]  [] start_secondary+0x151/0x190
  [ 6544.571475] Code: 90 88 45 98 4c 89 55 a0 e8 4d 70 e9 d8 0f b6 45 98 4c 8b 
5d 90 4c 8b 55 a0 49 c7 85 60 01 00 00 00 00 00 00 89 c6 e9 91 f8 ff ff <0f> 0b 
0f 0b 49 83 85 b8 01 00 00 01 49 c7 85 60 01 00 00 00 00
  [ 6544.573327] RIP  [] vmxnet3_rq_rx_complete+0x8d1/0xeb0 
[vmxnet3]
  [ 6544.573926]  RSP 

  
  BR, 
  Mikolaj Kowalski

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 r

[Kernel-packages] [Bug 1673627] Re: dmcrypt-get-device does not check the return values of setuid() or setgid()

2017-03-27 Thread Launchpad Bug Tracker 
This bug was fixed in the package eject -
2.1.5+deb1+cvs20081104-13.1ubuntu1

---
eject (2.1.5+deb1+cvs20081104-13.1ubuntu1) zesty; urgency=medium

  * SECURITY UPDATE: Improper check for dropped privileges (LP: #1673627)
- dmcrypt-get-device.c: Ensure that setgid() and setuid() were successful
  before continuing
- CVE-2017-6964

 -- Tyler Hicks   Mon, 27 Mar 2017 21:21:46 +

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

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

Title:
  dmcrypt-get-device does not check the return values of setuid() or
  setgid()

Status in eject package in Ubuntu:
  Fix Released

Bug description:
  Ilja Van Sprundel discovered that dmcrypt-get-device does not properly
  handle errors returned from setuid()/setgid() despite being a setuid-
  root binary. Although it looks to be handling trustworthy input from
  the kernel after the setuid()/setgid() calls, the intent is to be
  parsing the data as a non-root user.

  Here's the original report:

  I noticed that dmcrypt-get-device is suid root. it's source code is 
apparently written at ubuntu (according to the comments)
  The code for which I found at 
http://archive.ubuntu.com/ubuntu/pool/main/e/eject/eject_2.1.5+deb1+cvs20081104-13.1.diff.gz

  which has the following comments: 
  * Opening /dev/mapper/control requires root privileges, therefore this
  * program needs to be installed setuid root. Root privileges are dropped
  * immediately after querying the information from the device mapper. The
  * parsing is done with normal user privileges afterwards.

  The priv dropping happens in dmcrypt-get-device.c and looks as
  follows:

  /* Drop all privileges */
  setgid(getgid());
  setuid(getuid());

  This unfortunately doesn't account for a failed call to setuid(), which would 
then perform the parsing as root. 
  You'll probably want to fix both the call to setgid() and setuid() with 
proper return value checks.

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

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

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-27 Thread Joseph Salisbury 
Upstream thinks the following commit may resolve this bug:

commit f1c635b439a5c01776fe3a25b1e2dc546ea82e6f
Author: Stephen Hemminger 
Date:   Tue Mar 7 09:15:53 2017 -0800

scsi: storvsc: Workaround for virtual DVD SCSI version


I built a test kernel with a pick of this commit.  The test kernel can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1674635/patched

Can you test that kernel and report back if it has the bug or not?

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1645187] Re: 4.4.0-47-generic dm_snapshot random deadlock

2017-03-27 Thread john 
patched upstream in 4.4.55, please upgrade / backport :

https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.55

commit cd8ad4d9eb6d9ee04e77b42c6a7a15eabada85ac
Author: Mikulas Patocka 
Date:   Wed Feb 15 11:26:10 2017 -0500

dm: flush queued bios when process blocks to avoid deadlock

commit d67a5f4b5947aba4bfe9a80a2b86079c215ca755 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/1645187

Title:
  4.4.0-47-generic dm_snapshot random deadlock

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

Bug description:
  Server's load become high with tasks in D state, no choice but to reboot the 
system.
  Could be related to the following ? :

  https://bugzilla.kernel.org/show_bug.cgi?id=119841
  https://www.redhat.com/archives/dm-devel/2016-June/msg00399.html
  https://patchwork.kernel.org/patch/9223697/
  https://xen.crc.id.au/bugs/view.php?id=75

  ii  xen-hypervisor-4.4-amd64 4.4.2-0ubuntu0.14.04.7
amd64Xen Hypervisor on AMD64
  ii  linux-image-extra-4.4.0-47-generic   4.4.0-47.68~14.04.1   
amd64Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
  ii  linux-image-4.4.0-47-generic 4.4.0-47.68~14.04.1   
amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP

  kernel messages:
  
  [890070.994700] INFO: task blkback.3.xvda2:5756 blocked for more than 120 
seconds.
  [890070.994758]   Not tainted 4.4.0-47-generic #68~14.04.1-Ubuntu 
  [890070.994806] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [890070.994884] blkback.3.xvda2 D 8800b7ff3928 0  5756  2 
0x
  [890070.994890]  8800b7ff3928 81e13500 8800b6a4be80 
8800b7ff4000
  [890070.994895]  88013a83cc18 88013a83cc00  
fffe0001
  [890070.994898]  8800b7ff3940 817fafc5 8800b6a4be80 
8800b7ff39c0
  [890070.994902] Call Trace:
  [890070.994912]  [] schedule+0x35/0x80
  [890070.994917]  [] rwsem_down_write_failed+0x1da/0x320
  [890070.994923]  [] ? push+0x47/0x50
  [890070.994927]  [] ? dm_kcopyd_copy+0x147/0x1f0
  [890070.994931]  [] call_rwsem_down_write_failed+0x13/0x20
  [890070.994933]  [] ? down_write+0x2d/0x40
  [890070.994939]  [] __origin_write+0x6e/0x210 [dm_snapshot]
  [890070.994944]  [] ? mempool_alloc_slab+0x15/0x20
  [890070.994946]  [] ? mempool_alloc+0x5f/0x150
  [890070.994949]  [] do_origin.isra.14+0x67/0x90 
[dm_snapshot]
  [890070.994952]  [] origin_map+0x62/0x80 [dm_snapshot]
  [890070.994955]  [] __map_bio+0x3a/0x110
  [890070.994957]  [] __split_and_process_bio+0x240/0x3c0
  [890070.994960]  [] dm_make_request+0x6a/0xd0
  [890070.994964]  [] generic_make_request+0xe1/0x1a0 
  [890070.994968]  [] submit_bio+0x77/0x150
  [890070.994971]  [] ? bio_alloc_bioset+0x181/0x2a0
  [890070.994977]  [] dispatch_rw_block_io+0x4fd/0x9b0 
[xen_blkback]
  [890070.994981]  [] ? xen_load_sp0+0x84/0x180
  [890070.994985]  [] __do_block_io_op+0x1f5/0x650 
[xen_blkback]
  [890070.994990]  [] ? del_timer_sync+0x48/0x50
  [890070.994993]  [] ? schedule_timeout+0x16b/0x2d0
  [890070.994997]  [] xen_blkif_schedule+0xd0/0x820 
[xen_blkback]
  [890070.995002]  [] ? finish_task_switch+0x7a/0x290
  [890070.995004]  [] ? __schedule+0x359/0x980
  [890070.995010]  [] ? prepare_to_wait_event+0xf0/0xf0
  [890070.995014]  [] ? xen_blkif_be_int+0x30/0x30 
[xen_blkback]
  [890070.995018]  [] kthread+0xc9/0xe0
  [890070.995021]  [] ? kthread_park+0x60/0x60
  [890070.995025]  [] ret_from_fork+0x3f/0x70
  [890070.995027]  [] ? kthread_park+0x60/0x60

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

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

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: Invalid argument

2017-03-27 Thread Mike Rushton 
** Summary changed:

- Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: 
Invalid argument
+ Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: 
Invalid argument

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

Title:
  Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  Incomplete

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC 
(8335-GTB) 

   * This is a toleration change (no exploitation) for those HW releases 
 following the SRU policy of "For Long Term Support releases we 
 regularly want to enable new hardware. Such changes are appropriate 
 provided that we can ensure not to affect upgrades on existing 
 hardware."

   * Without the Fix that hardware won't run Xenial guests under current 
 Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07 
 compatibility mode (plus a few no-op changes as backport 
 dependencies)

  
  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being 
 affected.

  [Regression Potential]

   * Changes are PPC only, so fallout should be contained to that
   * Patches were created by IBM and in Upstream qemu since 2.7
   * The effective change is rather small, only allow different compat 
 level on this other cpu class
   * There are a few refactoring changes needed to get the backport done, 
 while they should be a no-op that is a regression potential (still 
 limited to ppc64el)

  [Other Info]
   
   * Needed for certifying this Hardware for Ubuntu


  
  Upon running the virtualization test from the certification test suite, the 
kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UU

[Kernel-packages] [Bug 1675868] Re: linux: 4.10.0-15.17 -proposed tracker

2017-03-27 Thread Brad Figg 
** Changed in: kernel-development-workflow/automated-testing
   Status: New => Confirmed

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

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

** Changed in: kernel-development-workflow/automated-testing
   Status: Confirmed => Incomplete

** Description changed:

  This bug is for tracking the 4.10.0-15.17 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-phase-changed:Monday, 27. March 2017 22:31 UTC
+ kernel-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 4.10.0-15.17 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-phase-changed:Monday, 27. March 2017 22:31 UTC
- kernel-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.10.0-15.17 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1673627] Re: dmcrypt-get-device does not check the return values of setuid() or setgid()

2017-03-27 Thread Tyler Hicks 
Stable Ubuntu releases have been fixed:

  https://www.ubuntu.com/usn/usn-3246-1/

This bug will get auto-closed when my upload to Zesty lands.

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

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

Title:
  dmcrypt-get-device does not check the return values of setuid() or
  setgid()

Status in eject package in Ubuntu:
  Fix Committed

Bug description:
  Ilja Van Sprundel discovered that dmcrypt-get-device does not properly
  handle errors returned from setuid()/setgid() despite being a setuid-
  root binary. Although it looks to be handling trustworthy input from
  the kernel after the setuid()/setgid() calls, the intent is to be
  parsing the data as a non-root user.

  Here's the original report:

  I noticed that dmcrypt-get-device is suid root. it's source code is 
apparently written at ubuntu (according to the comments)
  The code for which I found at 
http://archive.ubuntu.com/ubuntu/pool/main/e/eject/eject_2.1.5+deb1+cvs20081104-13.1.diff.gz

  which has the following comments: 
  * Opening /dev/mapper/control requires root privileges, therefore this
  * program needs to be installed setuid root. Root privileges are dropped
  * immediately after querying the information from the device mapper. The
  * parsing is done with normal user privileges afterwards.

  The priv dropping happens in dmcrypt-get-device.c and looks as
  follows:

  /* Drop all privileges */
  setgid(getgid());
  setuid(getuid());

  This unfortunately doesn't account for a failed call to setuid(), which would 
then perform the parsing as root. 
  You'll probably want to fix both the call to setgid() and setuid() with 
proper return value checks.

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

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

[Kernel-packages] [Bug 1676635] Re: [Hyper-V] Implement Hyper-V PTP Source

2017-03-27 Thread Joseph Salisbury 
** Tags added: kernel-da-key kernel-hyper-v xenial yakkety zesty

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

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

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

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

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

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

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

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

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

Title:
  [Hyper-V] Implement Hyper-V PTP Source

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

Bug description:
  Please include the following upstream commit into lts-xenial, 16.04
  HWE, Yakkity, and Zesty. This will improve the behavior of timesync on
  Hyper-V hosts while simultaneously using network time sync protocols
  like NTP.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/hv_util.c?id=3716a49a81ba19dda7202633a68b28564ba95eb5

  commit 3716a49a81ba19dda7202633a68b28564ba95eb5
  Author: Vitaly Kuznetsov 
  Date:   Sat Feb 4 09:57:14 2017 -0700

  hv_utils: implement Hyper-V PTP source

  With TimeSync version 4 protocol support we started updating system time
  continuously through the whole lifetime of Hyper-V guests. Every 5 seconds
  there is a time sample from the host which triggers do_settimeofday[64]().
  While the time from the host is very accurate such adjustments may cause
  issues:
  - Time is jumping forward and backward, some applications may misbehave.
  - In case an NTP server runs in parallel and uses something else for time
    sync (network, PTP,...) system time will never converge.
  - Systemd starts annoying you by printing "Time has been changed" every 5
    seconds to the system log.

  Instead of doing in-kernel time adjustments offload the work to an
  NTP client by exposing TimeSync messages as a PTP device. Users may now
  decide what they want to use as a source.

  I tested the solution with chrony, the config was:

   refclock PHC /dev/ptp0 poll 3 dpoll -2 offset 0

  The result I'm seeing is accurate enough, the time delta between the guest
  and the host is almost always within [-10us, +10us], the in-kernel 
solution
  was giving us comparable results.

  I also tried implementing PPS device instead of PTP by using not currently
  used Hyper-V synthetic timers (we use only one of four for clockevent) but
  with PPS source only chrony wasn't able to give me the required accuracy,
  the delta often more that 100us.

  Signed-off-by: Vitaly Kuznetsov 
  Signed-off-by: K. Y. Srinivasan 
  Signed-off-by: Greg Kroah-Hartman 

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

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

[Kernel-packages] [Bug 624510] Re: Copying To USB Is Very Slow

2017-03-27 Thread David Hume 
This bug has been consistent in all Ubuntu releases 14, 15, 16 and the
relevant Mint releases upto and including 18. It never goes away and
always it stops around half-way copied. It is soo annoying!!

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

Title:
  Copying To USB Is Very Slow

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

Bug description:
  Copying files from hard disk to Usb or Usb to Hard Disk is very slow
  in Ubuntu 10.04..

  Is there a way to speed up the process of copying with the
  installation of additional softwares...

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: nautilus 1:2.30.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic i686
  Architecture: i386
  Date: Thu Aug 26 14:03:27 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_IN.utf8
   SHELL=/bin/bash
  SourcePackage: nautilus

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

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

[Kernel-packages] [Bug 1676635] Re: [Hyper-V] Implement Hyper-V PTP Source

2017-03-27 Thread Joshua R. Poulson 
** Description changed:

  Please include the following upstream commit into lts-xenial, 16.04 HWE,
  Yakkity, and Zesty. This will improve the behavior of timesync on
  Hyper-V hosts while simultaneously using network time sync protocols
  like NTP.
  
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/hv_util.c?id=3716a49a81ba19dda7202633a68b28564ba95eb5
+ 
  commit 3716a49a81ba19dda7202633a68b28564ba95eb5
  Author: Vitaly Kuznetsov 
  Date:   Sat Feb 4 09:57:14 2017 -0700
  
- hv_utils: implement Hyper-V PTP source
+ hv_utils: implement Hyper-V PTP source
  
- With TimeSync version 4 protocol support we started updating system time
- continuously through the whole lifetime of Hyper-V guests. Every 5 seconds
- there is a time sample from the host which triggers do_settimeofday[64]().
- While the time from the host is very accurate such adjustments may cause
- issues:
- - Time is jumping forward and backward, some applications may misbehave.
- - In case an NTP server runs in parallel and uses something else for time
-   sync (network, PTP,...) system time will never converge.
- - Systemd starts annoying you by printing "Time has been changed" every 5
-   seconds to the system log.
+ With TimeSync version 4 protocol support we started updating system time
+ continuously through the whole lifetime of Hyper-V guests. Every 5 seconds
+ there is a time sample from the host which triggers do_settimeofday[64]().
+ While the time from the host is very accurate such adjustments may cause
+ issues:
+ - Time is jumping forward and backward, some applications may misbehave.
+ - In case an NTP server runs in parallel and uses something else for time
+   sync (network, PTP,...) system time will never converge.
+ - Systemd starts annoying you by printing "Time has been changed" every 5
+   seconds to the system log.
  
- Instead of doing in-kernel time adjustments offload the work to an
- NTP client by exposing TimeSync messages as a PTP device. Users may now
- decide what they want to use as a source.
+ Instead of doing in-kernel time adjustments offload the work to an
+ NTP client by exposing TimeSync messages as a PTP device. Users may now
+ decide what they want to use as a source.
  
- I tested the solution with chrony, the config was:
+ I tested the solution with chrony, the config was:
  
-  refclock PHC /dev/ptp0 poll 3 dpoll -2 offset 0
+  refclock PHC /dev/ptp0 poll 3 dpoll -2 offset 0
  
- The result I'm seeing is accurate enough, the time delta between the guest
- and the host is almost always within [-10us, +10us], the in-kernel 
solution
- was giving us comparable results.
+ The result I'm seeing is accurate enough, the time delta between the guest
+ and the host is almost always within [-10us, +10us], the in-kernel 
solution
+ was giving us comparable results.
  
- I also tried implementing PPS device instead of PTP by using not currently
- used Hyper-V synthetic timers (we use only one of four for clockevent) but
- with PPS source only chrony wasn't able to give me the required accuracy,
- the delta often more that 100us.
+ I also tried implementing PPS device instead of PTP by using not currently
+ used Hyper-V synthetic timers (we use only one of four for clockevent) but
+ with PPS source only chrony wasn't able to give me the required accuracy,
+ the delta often more that 100us.
  
- Signed-off-by: Vitaly Kuznetsov 
- Signed-off-by: K. Y. Srinivasan 
- Signed-off-by: Greg Kroah-Hartman 
+ Signed-off-by: Vitaly Kuznetsov 
+ Signed-off-by: K. Y. Srinivasan 
+ Signed-off-by: Greg Kroah-Hartman 

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

Title:
  [Hyper-V] Implement Hyper-V PTP Source

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Confirmed

Bug description:
  Please include the following upstream commit into lts-xenial, 16.04
  HWE, Yakkity, and Zesty. This will improve the behavior of timesync on
  Hyper-V hosts while simultaneously using network time sync protocols
  like NTP.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/hv_util.c?id=3716a49a81ba19dda7202633a68b28564ba95eb5

  commit 3716a49a81ba19dda7202633a68b28564ba95eb5
  Author: Vitaly Kuznetsov 
  Date:   Sat Feb 4 09:57:14 2017 -0700

  hv_utils: implement Hyper-V PTP source

  With TimeSync version 4 protocol support we started updating system time
  continuously through the whole lifetime of Hyper-V guests. Every 5 seconds
  there is a time sample from the host which triggers d

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-27 Thread Joseph Salisbury 
@cristiano, yes you should have.  The commit has not been reverted yet
and a patch to fix the bug has not been added.  The commit that
introduced this bug was also cc'd to stable, so other releases will now
have this bug as well, until it is fixed.

** Also affects: linux (Ubuntu Zesty)
   Importance: Critical
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

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

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

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

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

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

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

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

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1676635] [NEW] [Hyper-V] Implement Hyper-V PTP Source

2017-03-27 Thread Joshua R. Poulson 
Public bug reported:

Please include the following upstream commit into lts-xenial, 16.04 HWE,
Yakkity, and Zesty. This will improve the behavior of timesync on
Hyper-V hosts while simultaneously using network time sync protocols
like NTP.

commit 3716a49a81ba19dda7202633a68b28564ba95eb5
Author: Vitaly Kuznetsov 
Date:   Sat Feb 4 09:57:14 2017 -0700

hv_utils: implement Hyper-V PTP source

With TimeSync version 4 protocol support we started updating system time
continuously through the whole lifetime of Hyper-V guests. Every 5 seconds
there is a time sample from the host which triggers do_settimeofday[64]().
While the time from the host is very accurate such adjustments may cause
issues:
- Time is jumping forward and backward, some applications may misbehave.
- In case an NTP server runs in parallel and uses something else for time
  sync (network, PTP,...) system time will never converge.
- Systemd starts annoying you by printing "Time has been changed" every 5
  seconds to the system log.

Instead of doing in-kernel time adjustments offload the work to an
NTP client by exposing TimeSync messages as a PTP device. Users may now
decide what they want to use as a source.

I tested the solution with chrony, the config was:

 refclock PHC /dev/ptp0 poll 3 dpoll -2 offset 0

The result I'm seeing is accurate enough, the time delta between the guest
and the host is almost always within [-10us, +10us], the in-kernel solution
was giving us comparable results.

I also tried implementing PPS device instead of PTP by using not currently
used Hyper-V synthetic timers (we use only one of four for clockevent) but
with PPS source only chrony wasn't able to give me the required accuracy,
the delta often more that 100us.

Signed-off-by: Vitaly Kuznetsov 
Signed-off-by: K. Y. Srinivasan 
Signed-off-by: Greg Kroah-Hartman 

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

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

Title:
  [Hyper-V] Implement Hyper-V PTP Source

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please include the following upstream commit into lts-xenial, 16.04
  HWE, Yakkity, and Zesty. This will improve the behavior of timesync on
  Hyper-V hosts while simultaneously using network time sync protocols
  like NTP.

  commit 3716a49a81ba19dda7202633a68b28564ba95eb5
  Author: Vitaly Kuznetsov 
  Date:   Sat Feb 4 09:57:14 2017 -0700

  hv_utils: implement Hyper-V PTP source

  With TimeSync version 4 protocol support we started updating system time
  continuously through the whole lifetime of Hyper-V guests. Every 5 seconds
  there is a time sample from the host which triggers do_settimeofday[64]().
  While the time from the host is very accurate such adjustments may cause
  issues:
  - Time is jumping forward and backward, some applications may misbehave.
  - In case an NTP server runs in parallel and uses something else for time
sync (network, PTP,...) system time will never converge.
  - Systemd starts annoying you by printing "Time has been changed" every 5
seconds to the system log.

  Instead of doing in-kernel time adjustments offload the work to an
  NTP client by exposing TimeSync messages as a PTP device. Users may now
  decide what they want to use as a source.

  I tested the solution with chrony, the config was:

   refclock PHC /dev/ptp0 poll 3 dpoll -2 offset 0

  The result I'm seeing is accurate enough, the time delta between the guest
  and the host is almost always within [-10us, +10us], the in-kernel 
solution
  was giving us comparable results.

  I also tried implementing PPS device instead of PTP by using not currently
  used Hyper-V synthetic timers (we use only one of four for clockevent) but
  with PPS source only chrony wasn't able to give me the required accuracy,
  the delta often more that 100us.

  Signed-off-by: Vitaly Kuznetsov 
  Signed-off-by: K. Y. Srinivasan 
  Signed-off-by: Greg Kroah-Hartman 

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

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

Re: [Kernel-packages] [Bug 1675996] Re: Default nouveau video driver creates garbled display (White 24" iMac w/ NVIDIA GeForce 7600 GT)

2017-03-27 Thread Graham Leach 
Hello Joseph,

*A) Current configuration:*

This is happening with the Precise Pangolin (12.04.5 LTS) and Trusty Tahir
(14.04.5 LTS) I*nstall Discs* on a White 24" iMac A1200.
I am using the following Install Disc image: http://cdimage.ubuntu.
com/releases/14.04/release/ubuntu-14.04.5-server-amd64+mac.iso
The video card in question is an *NVIDIA GeForce 7600GT* graphics
processor with
256 MB of GDDR3 SDRAM using PCI Express.

It is also happening with:

- Ubuntu (Trusty Tahir) - standard, alternative, net install
- Ubuntu (Xenial Xerus) - standard, alternative, net install
- Ubuntu (Mitaka) - standard, alternative, net install

The incident is fully documented at:
http://mymanthemaker.blogspot.hk/2017/03/getting-white-24-
core-2-duo-imac-to.html

The steps I have taken so far to obtain a working system is docmented at:
http://mymanthemaker.blogspot.hk/2017/03/imac-ubuntu-install-gone-wrong-install.html
http://mymanthemaker.blogspot.hk/2017/03/imac-ubuntu-install-gone-wrong-install_22.html

The nouveau driver family in question is:

NV40GeForce 6, *GeForce 7*Curie
NV4B(G73)   GeForce 7300 GT, *7600* (GS, GT, Go, Go GT), 7700 Go Quadro FX
(550M, 560, 560M)

The error(s) I am seeing are:

[   34.295856] nouveau :01:00.0: fifo: CACHE_ERROR - ch 0 [DRM] subc 3
mthd 0df8 data 
[   34.297536] nouveau :01:00.0: fifo: CACHE_ERROR - ch 0 [DRM] subc 3
mthd 0dfc data 

[   33.691722] nouveau :01:00.0: fifo: DMA_PUSHER - ch 0 [DRM] get
808c put 7d88 state 80006e00 (err: INVALID_CMD) push 0001

[   33.620013] nouveau :01:00.0: DRM: GPU lockup - switching to
software fbcon

[19993.568062] nouveau :01:00.0: DRM: Calling LVDS script 6:
[19993.568067] nouveau :01:00.0: DRM: 0xC165: Parsing digital output
script table


*B) Test new kernel:*

I can test the latest kernel, sure.


Best Regards,

Graham Leach

www.graham-leach.com | +852 6977 9076 <6977%209076> | SKYPE: graham_leach |
  @graham_leach | hk.linkedin.com/in/grahamrleach | about.me/GrahamLeach

On Tue, Mar 28, 2017 at 4:46 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> 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.11 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.11-rc4
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1675996
>
> Title:
>   Default nouveau video driver creates garbled display (White 24" iMac
>   w/ NVIDIA GeForce 7600 GT)
>
> Status in linux-lts-trusty package in Ubuntu:
>   New
>
> Bug description:
>   My White iMac 24" is unable to start an X-Windows session with the
>   Ubuntu Install DVD.
>
>   I am running Ubuntu 14.04.5 LTS (Trusty Tahir)
>
>   It looks like the kernel/initrd is loading the nouveau_304 driver, but
>   this results in a garbled screen (see attachment).  For even more
>   information, please see:
>
>   http://mymanthemaker.blogspot.hk/2017/03/getting-white-24-co
> re-2-duo-imac-to.html
>   http://mymanthemaker.blogspot.hk/2017/03/imac-ubuntu-install
> -gone-wrong-install.html
>
>   For exhaustive detail and many screen shots.
>
>   The error messages I see in dmesg (thousands of them) are:
>
>   nouveau :01:00.0: fifo: DMA_PUSHER - ch 1 [Xorg[2121]] get
>   00018000 put 000180a0 state 8000 (err: INVALID_CMD) push 
>
>   and
>
>   nouveau :01:00.0: Xorg[2121]: failed to idle channel 1
>   [Xorg[2121]]
>
>   and
>
>   EQ overflowing. Additional events will be discarded until existing
>   events are processed.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-4.4.0-31-generic 4.4.0-31.50~14.04.1
>   ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
>   Uname: Linux 4.4.0-31-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3.21
>   Architecture: amd64
>   Date: Sat Mar 25 06:39:17 2017
>   ProcEnviron:
>TERM=xterm
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: linux-lts-xenial
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+
> bug/1675996/+subscriptions
>

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

[Kernel-packages] [Bug 1673627] Re: dmcrypt-get-device does not check the return values of setuid() or setgid()

2017-03-27 Thread Tyler Hicks 
Debian wasn't interested in an embargo. I'm now making this bug public
and will be releasing security updates shortly.

** Information type changed from Private Security to Public Security

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

Title:
  dmcrypt-get-device does not check the return values of setuid() or
  setgid()

Status in eject package in Ubuntu:
  In Progress

Bug description:
  Ilja Van Sprundel discovered that dmcrypt-get-device does not properly
  handle errors returned from setuid()/setgid() despite being a setuid-
  root binary. Although it looks to be handling trustworthy input from
  the kernel after the setuid()/setgid() calls, the intent is to be
  parsing the data as a non-root user.

  Here's the original report:

  I noticed that dmcrypt-get-device is suid root. it's source code is 
apparently written at ubuntu (according to the comments)
  The code for which I found at 
http://archive.ubuntu.com/ubuntu/pool/main/e/eject/eject_2.1.5+deb1+cvs20081104-13.1.diff.gz

  which has the following comments: 
  * Opening /dev/mapper/control requires root privileges, therefore this
  * program needs to be installed setuid root. Root privileges are dropped
  * immediately after querying the information from the device mapper. The
  * parsing is done with normal user privileges afterwards.

  The priv dropping happens in dmcrypt-get-device.c and looks as
  follows:

  /* Drop all privileges */
  setgid(getgid());
  setuid(getuid());

  This unfortunately doesn't account for a failed call to setuid(), which would 
then perform the parsing as root. 
  You'll probably want to fix both the call to setgid() and setuid() with 
proper return value checks.

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

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

[Kernel-packages] [Bug 1676070] Re: Wrong button's map for Logitech M560

2017-03-27 Thread Joseph Salisbury 
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.11 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.11-rc4

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

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

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

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1675949] Re: perf report can't annotate kernel and dbgsym package has wrong addresses

2017-03-27 Thread Joseph Salisbury 
** 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/1675949

Title:
  perf report can't annotate kernel and dbgsym package has wrong
  addresses

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running zesty 4.10.0-13-generic kernel and running:
  $ perf record 

  followed by

  $ perf report

  results in output that can't be annotated (even when run as root). The 
following message appears:
  Couldn't annotate do_io_submit:
  No vmlinux file with build id 81ba79d482fa9e3ea58486de8f119b27fe6db55e
  was found in the path.

  Note that annotation using /proc/kcore requires CAP_SYS_RAWIO
  capability.

  Please use:

  perf buildid-cache -vu vmlinux

  Note this is being run as root and /proc/kcore is accessible with dd from the 
same shell:
  $ dd if=/proc/kcore bs=8 count=16 | hexdump
  000 457f 464c 0102 0001    
  010 0004 00b7 0001     
  020 0040       
  030   0040 0038 0003   
  040 0004    00e8   

  Additionally, installing the linux-image-4.10.0-13-generic-dbgsym
  actually hurts the situation because the symbol addresses in the
  dbgsym don't match the kernel addresses.

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

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

[Kernel-packages] [Bug 1675996] Re: Default nouveau video driver creates garbled display (White 24" iMac w/ NVIDIA GeForce 7600 GT)

2017-03-27 Thread Joseph Salisbury 
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.11 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.11-rc4

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

Title:
  Default nouveau video driver creates garbled display (White 24" iMac
  w/ NVIDIA GeForce 7600 GT)

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

Bug description:
  My White iMac 24" is unable to start an X-Windows session with the
  Ubuntu Install DVD.

  I am running Ubuntu 14.04.5 LTS (Trusty Tahir)

  It looks like the kernel/initrd is loading the nouveau_304 driver, but
  this results in a garbled screen (see attachment).  For even more
  information, please see:

  
http://mymanthemaker.blogspot.hk/2017/03/getting-white-24-core-2-duo-imac-to.html
  
http://mymanthemaker.blogspot.hk/2017/03/imac-ubuntu-install-gone-wrong-install.html

  For exhaustive detail and many screen shots.

  The error messages I see in dmesg (thousands of them) are:

  nouveau :01:00.0: fifo: DMA_PUSHER - ch 1 [Xorg[2121]] get
  00018000 put 000180a0 state 8000 (err: INVALID_CMD) push 

  and

  nouveau :01:00.0: Xorg[2121]: failed to idle channel 1
  [Xorg[2121]]

  and

  EQ overflowing. Additional events will be discarded until existing
  events are processed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50~14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Sat Mar 25 06:39:17 2017
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1675983] Re: package linux-image-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-03-27 Thread Joseph Salisbury 
You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

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

Title:
  package linux-image-4.4.0-66-generic 4.4.0-66.87 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  system displayed unexpected error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  karthikeyan   1706 F pulseaudio
  Date: Sat Mar 25 09:17:35 2017
  Df:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=/dev/sda1
  InstallationDate: Installed on 2017-03-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   ens34 no wireless extensions.
   
   lono wireless extensions.
   
   enp0s29f7u7  no wireless extensions.
  MachineType: Intel DL-G41MX3-LT
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=a23a1244-f351-40a6-9c7b-27f2d56416f8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.8
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-66-generic 4.4.0-66.87 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L1.01
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: DL-G41MX3-LT
  dmi.board.vendor: Intel
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL1.01:bd10/24/2011:svnIntel:pnDL-G41MX3-LT:pvr1.0:rvnIntel:rnDL-G41MX3-LT:rvr1.0:cvnIntel:ct3:cvr1.0:
  dmi.product.name: DL-G41MX3-LT
  dmi.product.version: 1.0
  dmi.sys.vendor: Intel

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

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

[Kernel-packages] [Bug 1669758] Re: Centrino Wireless-N 1000 not working on 16.10

2017-03-27 Thread Joseph Salisbury 
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.11 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.11-rc4

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

Title:
  Centrino Wireless-N 1000 not working on 16.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Summary
  Wifi is not working on Centrino Wireless-N 1000 not working on 16.10, but 
does work on windows.

  Please see following

  http://paste.ubuntu.com/24101344/
  
http://askubuntu.com/questions/887257/device-not-ready-wifi-not-working-on-ubuntu-16-10
  https://ubuntuforums.org/showthread.php?t=2354116&p=13615105#post13615105
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  anton  2691 F pulseaudio
   /dev/snd/controlC0:  anton  2691 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=4f9bb031-cd71-4106-8408-bc6b09dc34aa
  InstallationDate: Installed on 2017-02-25 (29 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 4384WHB
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-41-generic N/A
   linux-backports-modules-4.8.0-41-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET55WW (1.18 )
  dmi.board.name: 4384WHB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6MET55WW(1.18):bd04/21/2010:svnLENOVO:pn4384WHB:pvrThinkPadT510:rvnLENOVO:rn4384WHB:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4384WHB
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-27 Thread Cristiano Casella 
got same troubles also on version 4.4.0-70 (just released:
https://launchpad.net/ubuntu/+source/linux/4.4.0-70.91)

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1675533] Re: Black screen on Kernel 4.4.0-64 and 4.4.0-66

2017-03-27 Thread Joseph Salisbury 
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable 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'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-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.4.57

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

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

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

Title:
  Black screen on Kernel 4.4.0-64 and 4.4.0-66

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
   It was suggested on askubuntu that I try here. I can load up on Kernel 
4.4.0-62 but not 4.4.0-64 or 4.4.0-66. I currently have to press escape on 
load-up and select 4.4.0-62 on the GRUB screen. I assume new Kernels come out 
every few weeks and therefore 4.4.0-62 will eventually be redundant? 
Coincidentally kernel 4.4.0-64 & 4.4.0-66 stopped working after I installed the 
GIMP image program.

  I also have an additional problem of the wifi stopping/dropping every
  few minutes but hope I can fix that later on askubuntu. I haven't
  worked out if it stops regularly or when I briefly stop typing and
  read a webpage. I thought I would mention it in case it is related.

  My knowledge of ubuntu/computers is limited. What are the best
  commands to try and diagnose the problem?

  CPU: AMD phenom 11x4 970 Processor x4 (32-bit)
  RAM: 15.8 GiB
  Graphics: Gallium 0.4 on AMD CAICOS (DRM 2.43.0/4.4.0-62-generic, LLVM 
3.8.0)
  Disk: 475.2GB

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-generic 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lalalala   1648 F pulseaudio
   /dev/snd/controlC1:  lalalala   1648 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 23 19:14:39 2017
  HibernationDevice: RESUME=UUID=d99064f6-aa39-4d52-95df-27762169c27e
  InstallationDate: Installed on 2017-01-02 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=5b90d169-62a7-498f-92d2-673ed94400aa ro rootflags=sync quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78LT-M
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd08/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78LT-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1676078] Re: Touchpad is not recognized (ASUS X556U)

2017-03-27 Thread Joseph Salisbury 
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.11 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.11-rc4

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

Title:
  Touchpad is not recognized (ASUS X556U)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad doesnt work and it isnt recongnized.

  Xinput (USB optical mouse is another USB mouse connected)

  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ USB Optical Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Asus Wireless Radio Control id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Video Bus   id=9[slave  
keyboard (3)]
  ↳ Sleep Buttonid=10   [slave  
keyboard (3)]
  ↳ USB Camera  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]

  lspci
  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 08)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
  00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 08)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#5 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940M] (rev a2)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
  03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 30)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-41-generic 4.8.0-41.44
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brujo  2424 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Mar 25 12:45:42 2017
  HibernationDevice: RESUME=UUID=5a7d3492-03cf-436b-ab0c-7e85013a018d
  InstallationDate: Installed on 2017-01-30 (54 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X556UB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic.efi.signed 
root=UUID=67f6eec2-c5b9-4465-a985-87e85a5f86bf ro quiet splash vt.handoff=7
  Re

[Kernel-packages] [Bug 1675540] Re: i2c i2c-1: sendbytes: NAK bailout.

2017-03-27 Thread Joseph Salisbury 
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.11 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.11-rc4

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

Title:
  i2c i2c-1: sendbytes: NAK bailout.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This bug still exists and looks like it was identified as part of the
  Nouveau video driver, experienced now with Ubuntu 16.10.

  Timed out (original?) bug thread:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1015165

  Trackback on forums with no clear resolution:
  https://ubuntuforums.org/showthread.php?t=2074280

  
  Details:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.10
  Release:16.10
  Codename:   yakkety

  $ lsmod | grep 'i2c'
  i2c_piix4  24576  0
  i2c_algo_bit   16384  1 nouveau
  support@apollo:~$ lsmod | grep 'nouveau'
  nouveau  1572864  1
  mxm_wmi16384  1 nouveau
  video  40960  1 nouveau
  i2c_algo_bit   16384  1 nouveau
  ttm   102400  1 nouveau
  drm_kms_helper167936  1 nouveau
  drm   368640  4 nouveau,ttm,drm_kms_helper
  wmi16384  2 mxm_wmi,nouveau

  $ uname -a
  Linux apollo 4.8.0-40-generic #43-Ubuntu SMP Thu Feb 23 16:01:19 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  
  $ lspci | grep -i 'nvidia'
  01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] 
(rev a2)

  dmesg spam :

  [74243.701317] Raw EDID:
  [74243.702234]  78 ee c1 25 a3 56 4b 99 27 11 50 54 bf ef 80 95
  [74243.703153]  00 71 4f 81 80 95 0f 01 01 01 01 01 01 01 01 9a
  [74243.704050]  29 a0 d0 51 84 22 30 50 98 36 00 98 ff 10 00 00
  [74243.704925]  1c 00 00 00 fd 00 38 4b 1e 53 0e 00 0a 20 20 20
  [74243.705816]  20 20 20 00 00 00 ff 00 37 33 37 33 31 38 33 49
  [74243.706732]  32 38 57 53 01 00 00 00 fc 00 44 45 4c 4c 20 45
  [74243.707617]  31 39 38 57 46 50 0a 00 3a ff ff ff ff ff ff ff
  [74243.708508]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [74243.65] i2c i2c-1: sendbytes: NAK bailout.
  [74246.557345] i2c i2c-1: sendbytes: NAK bailout.
  [74246.843767] i2c i2c-1: sendbytes: NAK bailout.
  [74247.128195] i2c i2c-1: sendbytes: NAK bailout.
  [74249.366638] i2c i2c-1: sendbytes: NAK bailout.
  [74250.883810] i2c i2c-1: sendbytes: NAK bailout.
  [74251.295261] i2c i2c-1: sendbytes: NAK bailout.
  [74252.939101] i2c i2c-1: sendbytes: NAK bailout.
  [74254.200165] i2c i2c-1: sendbytes: NAK bailout.
  [74254.885717] i2c i2c-1: readbytes: ack/nak timeout
  [74255.169703] i2c i2c-1: readbytes: ack/nak timeout
  [74255.737676] i2c i2c-1: readbytes: ack/nak timeout
  [74257.450821] i2c i2c-1: sendbytes: NAK bailout.

  No packages :
  $ dpkg --list | grep  -i 'nvidia'
  $ dpkg --list | grep  -i 'nouveau'
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.8.0-41-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', 
'/dev/snd/midiC1D0', '/dev/snd/pcmC1D3c', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/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
  Card1.Amixer.info: Error: [Errno 2] No such file or directory
  Card1.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=/dev/mapper/mike--ubuntu--vg-swap_1
  InstallationDate: Installed on 2017-03-01 (24 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  IwConfig: Error: [Er

[Kernel-packages] [Bug 1675395] Re: ubuntu_bpf test fail to build on aarch64 system

2017-03-27 Thread Joseph Salisbury 
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Tags added: kernel-da-key

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

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

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

Title:
  ubuntu_bpf test fail to build on aarch64 system

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

Bug description:
  # make
  for TARGET in bpf; do \
make -C $TARGET; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest-client-tests/ubuntu_bpf/linux/tools/testing/selftests/bpf'
  gcc -Wall -O2 -I../../../../usr/includetest_verifier.c   -o test_verifier
  In file included from test_verifier.c:23:0:
  /usr/include/linux/bpf_perf_event.h:13:17: error: field ‘regs’ has incomplete 
type
struct pt_regs regs;
   ^~~~
  : recipe for target 'test_verifier' failed
  make[1]: *** [test_verifier] Error 1
  make[1]: Leaving directory 
'/home/ubuntu/autotest-client-tests/ubuntu_bpf/linux/tools/testing/selftests/bpf'
  Makefile:18: recipe for target 'all' failed
  make: *** [all] Error 2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-13-generic 4.10.0-13.15
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 23 04:39 seq
   crw-rw 1 root audio 116, 33 Mar 23 04:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Mar 23 12:23:15 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1675204] Re: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP)

2017-03-27 Thread Joseph Salisbury 
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.11 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.11-rc4

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

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

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

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

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

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

Title:
  Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP)

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

Bug description:
  I have a very strange issue related to Intel graphics drivers (i915)
  with 3 connected on-board displays.

  I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop
  computer running on a i7-6700K processor and on-board graphics (Mobo:
  AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG
  display (via onboard DP port), a 1920x1200 Dell display (via on-board
  HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter).

  If I just connect my desktop to the first two displays (not the TV),
  everything works fine (except some minor issues). However, if I
  connect the 4k TV, even the TV is not on, my graphics starts to
  flicker every 5 min-ish (window theme turns off and then turns quickly
  back on); after a few flickering, the window theme will disappear, and
  the screen becomes weird - my chrome window will not fresh, or show
  blank boxes etc.

  If I disconnect the DVI connector to the TV (just use the LG+Dell
  dual-display), flickering and crash will not appear.

  I want to mention that, when I connect the computer to all 3 displays,
  I was actually able to get video output to all displays (I used arandr
  to configure them). I can even get 4k output to the 4k TV at 30Hz.

  I can't find a useful log entry when the flicking or graphics crash
  happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F
  (log attached at the end), but I can see many similar errors in my log
  and the appearance is not correlated to the flickering/crash. The
  "pipe A FIFO underrun" issue was previously reported in Bug#1550779.

  I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my
  Xorg.0.log file constantly, I also do not see an consistent mapping
  between the log entry and the flickering.

  Can anyone tell me how to properly debug this? what can I do to get a
  log for what was wrong?

  ---

  [  145.033055] WARNING: CPU: 2 PID: 1804 at 
/build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675
 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]()
  [  145.033058] WARN_ON(!wm_changed)
  [  145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev 
input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main 
v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) 
uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi 
coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) 
nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw 
gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi 
cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo 
auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc 
intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel 
btintel intel_lpss_ac
 pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops 
syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi 
kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp 
pps_core ahci nvme libahci fjes
  [  145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW  OE   
4.4.0-66-generic #87~14.04.1-Ubuntu
  [  145.033287] Hardware name: To Be Filled By O.E.M. To B

[Kernel-packages] [Bug 1675564] Re: After hibernation screen becomes completely pixellated.

2017-03-27 Thread Joseph Salisbury 
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.11 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.11-rc4

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

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

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

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

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

Title:
  After hibernation screen becomes completely pixellated.

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

Bug description:
  This started happening just this morning. After resuming from
  hibernation, the screen becomes pixellated, and the screen around GUI
  apps, such as File Explorer or Terminal, also becomes pixellated when
  opened in a minimized window. Any help is appreciated. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-41-generic 4.8.0-41.44
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexander   2553 F pulseaudio
   /dev/snd/controlC0:  alexander   2553 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 23 17:17:57 2017
  HibernationDevice: RESUME=UUID=331f3735-3e6d-4a8e-b06c-64f51b2c9d36
  InstallationDate: Installed on 2017-01-22 (60 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP ENVY m7 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic.efi.signed 
root=UUID=6d932bfc-8d72-4c9c-b619-902eb6e1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-41-generic N/A
   linux-backports-modules-4.8.0-41-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVYm7NotebookPC:pvr096F120022405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY m7 Notebook PC
  dmi.product.version: 096F120022405F1620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1676183] Re: Could not update the system to use proposed kernel

2017-03-27 Thread Joseph Salisbury 
** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Tags added: kernel-da-key

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

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

Title:
  Could not update the system to use proposed kernel

Status in linux package in Ubuntu:
  Triaged

Bug description:
  [Description]

  When -proposed pocket is enabled in the apt source list, the -proposed
  kernel 3.13.0-114.161 [1] could not be fetched by "apt-get dist-
  upgrade"

  [Steps to Reproduce]
  1. Install trusty.
  2. Enable the -proposed in the source list  /etc/apt/sources.list
  3. Issue the command, "sudo apt-get update; sudo apt-get dist-grade" to 
update the system
  4. Reboot.

  [Expected Result]
  The system is now having the proposed kernel 3.13.0-114.161 installed and 
using it. Check this by "uname -a" for example.

  [Actual Result]
  1. The system is still use the original kernel.
  2. "dpkg -l" does not show that linux-image-3.13.0-114-generic is installed.

  [1]
  -proposed tracker  
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673207

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

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

[Kernel-packages] [Bug 1676148] Re: psmouse FingerSensingPad lost synchronization, throwing bytes away

2017-03-27 Thread Joseph Salisbury 
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.11 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.11-rc4

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

Title:
  psmouse FingerSensingPad lost synchronization, throwing bytes away

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  (This is my first bug report, sorry if I miss important information)

  Following https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-
  input-synaptics/+bug/1568224

  I randomly loose my trackpad. It just stop working. I can recover it
  by rebooting or going in/out sleep mode, or using a real mouse.

  Here is my dmesg :
  [   53.061907] xhci_hcd :00:14.0: WARN Event TRB for slot 3 ep 4 with no 
TDs queued?
  [   74.581715] usb 2-6: USB disconnect, device number 4
  [   74.862156] usb 2-6: new full-speed USB device number 6 using xhci_hcd
  [   74.995872] usb 2-6: New USB device found, idVendor=138a, idProduct=0017
  [   74.995877] usb 2-6: New USB device strings: Mfr=0, Product=0, 
SerialNumber=1
  [   74.995879] usb 2-6: SerialNumber: 5e9c23e2536c
  [   95.478843] systemd[1]: apt-daily.timer: Adding 5h 56min 35.524032s random 
time.
  [   97.678577] systemd[1]: apt-daily.timer: Adding 10h 43min 17.662649s 
random time.
  [   97.772519] systemd[1]: apt-daily.timer: Adding 4h 21min 42.522475s random 
time.
  [   98.473794] systemd[1]: apt-daily.timer: Adding 4h 18min 56.902835s random 
time.
  [   98.555859] systemd[1]: apt-daily.timer: Adding 11h 48min 39.748131s 
random time.
  [  250.996796] psmouse serio1: bad data from KBC - timeout
  [  251.024804] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 4
  [  251.025998] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 1
  [  251.027168] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 1
  [  251.039245] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 4
  [  251.040419] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 1
  [  251.040424] psmouse serio1: issuing reconnect request
  [  251.434273] psmouse serio1: synaptics: queried max coordinates: x 
[..5112], y [..3834]
  [  251.466430] psmouse serio1: synaptics: queried min coordinates: x 
[1024..], y [1024..]
  [  251.466438] psmouse serio1: synaptics: quirked min/max coordinates: x 
[1024..5112], y [2024..4832]
  [  253.568814] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 1
  [  253.569944] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 1
  [  253.571072] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 1
  [  253.572229] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 1
  [  253.586347] psmouse serio1: TouchPad at isa0060/serio1/input0 - driver 
resynced.
  [ 1397.604492] usb 2-6: reset full-speed USB device number 6 using xhci_hcd
  [ 1398.572300] usb 2-6: reset full-speed USB device number 6 using xhci_hcd
  [ 1399.244611] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 4 with no 
TDs queued?
  [ 1399.819750] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 4 with no 
TDs queued?
  [ 1399.882079] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 4 with no 
TDs queued?
  [ 1401.072220] usb 2-6: reset full-speed USB device number 6 using xhci_hcd
  [ 1401.763121] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 4 with no 
TDs queued?
  [ 1402.164429] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 4 with no 
TDs queued?
  [ 1402.241696] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 4 with no 
TDs queued?
  [ 1545.494485] usb 2-6: USB disconnect, device number 6
  [ 1545.764854] usb 2-6: new full-speed USB device number 7 using xhci_hcd
  [ 1545.950344] usb 2-6: New USB device found, idVendor=138a, idProduct=0017
  [ 1545.950351] usb 2-6: New USB device strings: Mfr=0, Product=0, 
SerialNumber=1
  [ 1545.950355] usb 2-6: SerialNumber: 5e9c23e2536c
  [ 1602.481988] psmouse serio1: bad data from KBC - timeout bad parity

  I'm using a Thinkpad T440s with ubuntu 16.04.

  I have been facing this issue for several months. Still going...

  Thanks for your help !

  ProblemType: Bug
  DistroR

[Kernel-packages] [Bug 1676209] Re: VM crashes after saving and restoring with latest kernel

2017-03-27 Thread Joseph Salisbury 
This could be related to bug 1674635.  Can you try the test kernel
posted in comment #42?

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

** Tags added: kernel-da-key kernel-hyper-v

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

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

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

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

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

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

Title:
  VM crashes after saving and restoring with latest kernel

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

Bug description:
  After upgrading my Ubuntu Hyper-V VM to the latest kernel
  (4.4.0-67-generic, Ubuntu 16.04.2 LTS), it started crashing after
  saving and restoring it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-67-generic 4.4.0-67.88
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Mar 26 20:49 seq
   crw-rw+ 1 root audio 116, 33 Mar 26 20:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sun Mar 26 20:51:29 2017
  HibernationDevice: RESUME=/dev/mapper/HUGVWEB01--vg-swap_1
  InstallationDate: Installed on 2015-10-29 (514 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro elevator=noop
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-67-generic N/A
   linux-backports-modules-4.4.0-67-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-02-23 (31 days ago)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0559-3398-3600-3623-3585-8903-93
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Mar 26 21:13 seq
   crw-rw+ 1 root audio 116, 33 Mar 26 21:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/HUGVWEB01--vg-swap_1
  InstallationDate: Installed on 2015-10-29 (514 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro elevator=noop
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-67-generic N/A
   linux-backports-modules-4.4.0-67-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  U

[Kernel-packages] [Bug 1675674] Re: package linux-image-4.8.0-44-generic 4.8.0-44.47 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

2017-03-27 Thread Joseph Salisbury 
You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

Title:
  package linux-image-4.8.0-44-generic 4.8.0-44.47 failed to
  install/upgrade: subprocess installed post-installation script was
  killed by signal (Terminated)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installation of this package using apt hangs at 'run-parts: executing 
/etc/kernel/postinst.d/dkms 4.8.0-44-generic /boot/vmlinuz-4.8.0-44-generic' 
with no process activity observable by htop or others.
  killing the process and running 'dpkg --configure -a' hangs at the same 
position, 'apt purge *4.8.0-44*' hangs at the same position.

  I remember this happening before for a different kernel but can't
  remember which.

  Please tell me if and which information is needed additionally to the
  automatic collected data.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-44-generic 4.8.0-44.47
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2192 F pulseaudio
dirk   2537 F pulseaudio
   /dev/snd/controlC1:  gdm2192 F pulseaudio
dirk   2537 F pulseaudio
  Date: Fri Mar 24 09:11:44 2017
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
  HibernationDevice: RESUME=UUID=016cefa8-4e13-45c6-a877-ddbc86b78741
  InstallationDate: Installed on 2017-01-15 (67 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: LENOVO 80NV
  ProcFB:
   0 inteldrmfb
   1 evdidrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=7ebecb7d-79da-41a5-84bd-68400bda8190 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
  SourcePackage: linux
  Title: package linux-image-4.8.0-44-generic 4.8.0-44.47 failed to 
install/upgrade: subprocess installed post-installation script was killed by 
signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN27WW:bd11/12/2015:svnLENOVO:pn80NV:pvrLenovoideapadY700-15ISK:rvnLENOVO:rnAllsparks5A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-15ISK:
  dmi.product.name: 80NV
  dmi.product.version: Lenovo ideapad Y700-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-27 Thread Cristiano Casella 
thanks for your support

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1675390] Re: touchpad stops responding erratically

2017-03-27 Thread Joseph Salisbury 
** 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/1675390

Title:
  touchpad stops responding erratically

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware: Dell XPW 13 2016 model no. 9360
  Touchpad  DLL075B:01 06CB:76AF Touchpad  
  OS KUBUNTU 

  Description:

  - The tochpad works ok for a while, then after some time it stops responding 
to finger input. 
  - There seems to be a correlation bwetween the touchpad failure and a running 
a heavy program, like LIBREOFFICE. 
  - Plugging in an extenral mouse is a solution (of sorts). 
  - After a while the touchapd resumea normal activity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xinput 1.6.2-1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Mar 23 14:28:24 2017
  InstallationDate: Installed on 2016-12-09 (104 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: xinput
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-27 Thread Joseph Salisbury 
Thanks for all the help testing Cristiano and Marcin.  I pinged the
patch author and upstream to get some feedback.  I'll post when we know
the next steps.

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-27 Thread Cristiano Casella 
Reverted kernel works fine on 2 server:

root@ID11600:~# uname -a
Linux ID11600.example.com 4.4.0-71-generic #92~lp1674635Revert SMP Mon Mar 27 
18:33:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1633769] Re: Bug with kernel 4.8

2017-03-27 Thread Никитушкин Андрей 
Hello, Brad Figg!

I send apport-collect files for my bug, please see.


Thanks.


27.03.2017 21:00, Brad Figg пишет:
> This bug is missing log files that will aid in diagnosing the problem.
> >From a terminal window please run:
>
> apport-collect 1633769
>
> 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
>


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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

[Kernel-packages] [Bug 1633769] Re: Bug with kernel 4.8

2017-03-27 Thread Никитушкин Андрей 
Please send this information about this bug to Debian bug report for
Debian developers.

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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

[Kernel-packages] [Bug 1633769] Re: Bug with kernel 4.8

2017-03-27 Thread Никитушкин Андрей 
This apport information for 4.4 linux kernel (Ubuntu 16.04), linux
kernel and i915 after 4.7 linux kernel version not work with my
hardware.

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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-27 Thread Cristiano Casella 
b4e22b8a3d9d5746380e8d400cd9134567ffe675 works fine.

Testing the reverted...

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-27 Thread Marcin Banaszek 
4.4.0-71.92~lp1674635Revert works fine.

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

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

2017-03-27 Thread Никитушкин Андрей 
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1633769/+attachment/4847990/+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/1633769

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

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

2017-03-27 Thread Никитушкин Андрей 
apport information

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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

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

2017-03-27 Thread Никитушкин Андрей 
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1633769/+attachment/4847982/+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/1633769

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

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

2017-03-27 Thread Никитушкин Андрей 
apport information

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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

[Kernel-packages] [Bug 1633769] RfKill.txt

2017-03-27 Thread Никитушкин Андрей 
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1633769/+attachment/4847988/+files/RfKill.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/1633769

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

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

2017-03-27 Thread Никитушкин Андрей 
apport information

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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

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

2017-03-27 Thread Никитушкин Андрей 
apport information

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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

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

2017-03-27 Thread Никитушкин Андрей 
apport information

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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

[Kernel-packages] [Bug 1633769] Lsusb.txt

2017-03-27 Thread Никитушкин Андрей 
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1633769/+attachment/4847984/+files/Lsusb.txt

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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

[Kernel-packages] [Bug 1633769] Dependencies.txt

2017-03-27 Thread Никитушкин Андрей 
apport information

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

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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

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

2017-03-27 Thread Никитушкин Андрей 
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1633769/+attachment/4847978/+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/1633769

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

[Kernel-packages] [Bug 1633769] IwConfig.txt

2017-03-27 Thread Никитушкин Андрей 
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1633769/+attachment/4847981/+files/IwConfig.txt

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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

[Kernel-packages] [Bug 1633769] Re: Bug with kernel 4.8

2017-03-27 Thread Никитушкин Андрей 
apport information

** Tags added: apport-collected xenial

** Description changed:

  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.
  
  Please correct your mistakes.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  redarmy3360 F pulseaudio
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
+ MachineType: Acer Extensa 5220
+ NonfreeKernelModules: wl
+ Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
+ PackageArchitecture: amd64
+ PccardctlIdent:
+  Socket 0:
+no product info available
+ PccardctlStatus:
+  Socket 0:
+no card
+ ProcEnviron:
+  LANGUAGE=en_US
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=ru_RU.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-70-generic N/A
+  linux-backports-modules-4.4.0-70-generic  N/A
+  linux-firmware1.157.8
+ Tags:  xenial xenial
+ Uname: Linux 4.4.0-70-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 07/03/2008
+ dmi.bios.vendor: Phoenix Technologies LTD
+ dmi.bios.version: V1.35
+ dmi.board.name: Columbia
+ dmi.board.vendor: Acer
+ dmi.board.version: Rev
+ dmi.chassis.asset.tag: None
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Acer
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
+ dmi.product.name: Extensa 5220
+ dmi.product.version: 0100
+ dmi.sys.vendor: Acer

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1633769/+attachment/4847977/+files/AlsaInfo.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/1633769

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.

[Kernel-packages] [Bug 1664602] Re: Using an NVMe drive causes huge power drain

2017-03-27 Thread Francois Thirioux 
After some reasonable big time of use, I get (as far I noticed in user
interface or system journals) no errors and not any hang. I did not
notice any slowdown either.

Thanks a lot, my battery is smiling again.

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

Title:
  Using an NVMe drive causes huge power drain

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

Bug description:
  PCIe NVMe drives are very common in new laptops. The Zesty's kernels 
(including latest 4.10 rc8 from CKT PPA) does not support APST (autonomous 
power state transitions). A patch does exist :
  http://lists.infradead.org/pipermail/linux-nvme/2017-February/008051.html
  https://github.com/damige/linux-nvme

  It seems that we cannot expect this before kernel 4.11.

  Additionally my laptop CPU does never go under PC3 power saving state, 
powertop says. I don't know if it's related.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ft 1900 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=a04b55bf-b1b6-464c-88ce-44b6adbbbc10
  InstallationDate: Installed on 2016-12-12 (63 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=0d1f213e-73a9-4097-ae64-9cd963cfba23 ro quiet
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-8-generic N/A
   linux-backports-modules-4.10.0-8-generic  N/A
   linux-firmware1.163
  Tags:  zesty
  Uname: Linux 4.10.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.5
  dmi.board.name: 0YH43H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.5:bd12/22/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0YH43H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

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

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

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

2017-03-27 Thread Никитушкин Андрей 
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1633769/+attachment/4847979/+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/1633769

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  redarmy3360 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/sys_v01-swap
  MachineType: Acer Extensa 5220
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-70-generic 
root=/dev/mapper/sys_v01-sys ro splash quiet ipv6.disable=1 intel_pstate=enable 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-70-generic N/A
   linux-backports-modules-4.4.0-70-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial xenial
  Uname: Linux 4.4.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5220
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

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

2017-03-27 Thread bugproxy 
--- Comment From jos...@br.ibm.com 2017-03-27 15:08 EDT---
Based on #comment 26 we're ok now, but only to let it registered anyway:

Yes, today I don't see anything we can do in QEMU. The reason is that
kernel (arch/powerpc/include/asm/cputable.h) defines a basic feature set
for Power8:

#define CPU_FTRS_POWER8 (CPU_FTR_USE_TB | CPU_FTR_LWSYNC | \
CPU_FTR_PPCAS_ARCH_V2 | CPU_FTR_CTRL | CPU_FTR_ARCH_206 |\
CPU_FTR_MMCRA | CPU_FTR_SMT | \
CPU_FTR_COHERENT_ICACHE | \
CPU_FTR_PURR | CPU_FTR_SPURR | CPU_FTR_REAL_LE | \
CPU_FTR_DSCR | CPU_FTR_SAO  | \
CPU_FTR_STCX_CHECKS_ADDRESS | CPU_FTR_POPCNTB | CPU_FTR_POPCNTD | \
CPU_FTR_ICSWX | CPU_FTR_CFAR | CPU_FTR_HVMODE | CPU_FTR_VMX_COPY | \
CPU_FTR_DBELL | CPU_FTR_HAS_PPR | CPU_FTR_DAWR | \
CPU_FTR_ARCH_207S | CPU_FTR_TM_COMP | CPU_FTR_SUBCORE)

and CPU_FTR_TM_COMP (0x0080) is among them.

Then, in arch/powerpc/kernel/prom.c, a function initializes the device
tree and scans the CPUs in the current system. During the scan
(early_init_dt_scan_cpus), the architecture is identified
(arch/powerpc/kernel/cputable.c - identify_cpu) and the feature set
above is assigned to the processor.

So, in a nutshell, when the kernel loads, the CPU arch is identified and
its basic feature set is loaded.

Based on it, I could work around it by setting a Power7 arch: qemu-
system-ppc64 -machine pseries -cpu POWER7 -vga none -nographic ...

Thanks

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

Title:
  qemu: Missing transaction memory advertisement

Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Incomplete
Status in qemu source package in Yakkety:
  Incomplete

Bug description:
  [Impact]

   * The non HW assisted virtualization (kvm-pr) on PowerPC announces 
 support for the Transactional memory feature but does not fully 
 support it. Due to that guests crash.

   * The fix essentially takes away the TM feature by default and only 
 enables it incertain cases where it is correct (right HW and recent 
 KVM-HV implementation)

  
  [Test Case]

   * Repro
 1. install uvtool-libvirt in Host
 2. uvt-simplestreams-libvirt sync --source 
http://cloud-images.ubuntu.com/daily arch=ppc64el label=daily release=xenial
 3. $ cat /home/ubuntu/ppc-template.xml
  

  hvm
  


  
  
  


  


  
  


  
  

  
  

  
 4. $ uvt-kvm create --memory 4096 --template /home/ubuntu/ppc-template.xml 
--password=ubuntu --ssh-public-key-file /home/ubuntu/.ssh/authorized_keys 
kvmguest-xenial-level1 release=xenial arch=ppc64el label=daily
 5. log into this guest (all following steps are in level1 guest to 
spawn a level2 guest)
 6. ensure kvm_pr is loaded correctly
This is in the extras package which is not installed by default 
(other bug). Get it with
$ apt-get install linux-image-extra-virtual
$ modprobe kvm_pr
$ lsmod | grep kvm_pr
 7. make sure libvirt default network can start in 2nd level
There likely is a network collision, use virsh net-edit to dix and 
then virsh net-start to start the network
 8. Get Original Xenial Ubuntu image
wget 
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-server-ppc64el.iso
 9. sudo apt install virtinst
  10. $ virt-install --virt-type=kvm --cpu=host --name=nested-xenial 
--controller type=scsi,model=virtio-scsi --graphics none --console 
pty,target_type=serial --disk 
path=/home/ubuntu/test-xenial-virt-inst.qcow2,size=4 --vcpus=4 --ram=2048 
--os-type=linux --os-variant ubuntu16.04 --network bridge=virbr0,model=virtio 
--cdrom=ubuntu-16.04-server-ppc64el.iso
 11. See crash on guest install/boot

   * Installing the fixed qemu in the 1st level (not on Bare Metal)
  before retrying step 11 should show the issue being fixed

  [Regression Potential]

   * It is changing features announced to the guest, but then it is only 
 taking it away in cases it won't work

   * The change is ppc64el "only" which restricts the audience to be hit  
 by regressions and even there kvm_pr (problem state virtualization) 
 is a rare case usually only for Testing/CI

   * Changes are upstream in qemu a while now without being revoked and 
 come from IBM themselves.

  
  --- 


  == Comment: #0 - Breno Henrique Leitao  - 2017-02-14 
10:03:03 ==
  We don't support transactional memory in PR KVM, so don't tell the OS that we 
do.

  These are the required patches:

  commit 2e68f28854f0120c9a938a61b64aaf1eaecb162b
  Author: Thomas Huth 
  Date:   Wed Sep 28 13:16:30 2016 +0200

  ppc: Check the availability of transactional memory

  KVM-PR currently does not support transactional memory, and

[Kernel-packages] [Bug 1672785] Re: [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device shutdown

2017-03-27 Thread Joseph Salisbury 
Were you able to test for this specific bug using the combined test
kernel posted in comment #4?  A SRU request will be submitted once
testing is verified.

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

Title:
  [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver
  device shutdown

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

Bug description:
  Mellanox has submitted the following patch upstream that's important
  for SR-IOV in Azure.

  Please integrate it into the Mellanox mlx4 drivers for lts-xenial,
  HWE, Zesty, and Azure custom.

  https://patchwork.ozlabs.org/patch/738305/

  From: Jack Morgenstein 

  Some Hypervisors detach VFs from VMs by instantly causing an FLR event
  to be generated for a VF.

  In the mlx4 case, this will cause that VF's comm channel to be disabled
  before the VM has an opportunity to invoke the VF device's "shutdown"
  method.

  For such Hypervisors, there is a race condition between the VF's
  shutdown method and its internal-error detection/reset thread.

  The internal-error detection/reset thread (which runs every 5 seconds) also
  detects a disabled comm channel. If the internal-error detection/reset
  flow wins the race, we still get delays (while that flow tries repeatedly
  to detect comm-channel recovery).

  The cited commit fixed the command timeout problem when the
  internal-error detection/reset flow loses the race.

  This commit avoids the unneeded delays when the internal-error
  detection/reset flow wins.

  Fixes: d585df1c5ccf ("net/mlx4_core: Avoid command timeouts during VF driver 
device shutdown")
  Signed-off-by: Jack Morgenstein 
  Reported-by: Simon Xiao 
  Signed-off-by: Tariq Toukan 
  ---
   drivers/net/ethernet/mellanox/mlx4/cmd.c  | 11 +++
   drivers/net/ethernet/mellanox/mlx4/main.c | 11 +++
   include/linux/mlx4/device.h   |  1 +
   3 files changed, 23 insertions(+)

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

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

[Kernel-packages] [Bug 1675949] Re: perf report can't annotate kernel and dbgsym package has wrong addresses

2017-03-27 Thread Seth Forshee 
Everything continues to work fine for me, but I see now that you are on
aarch64.

I don't have any 64-bit ARM platforms in my posession, but I should be
able to get access to something. I'll see what I can find out.

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

Title:
  perf report can't annotate kernel and dbgsym package has wrong
  addresses

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running zesty 4.10.0-13-generic kernel and running:
  $ perf record 

  followed by

  $ perf report

  results in output that can't be annotated (even when run as root). The 
following message appears:
  Couldn't annotate do_io_submit:
  No vmlinux file with build id 81ba79d482fa9e3ea58486de8f119b27fe6db55e
  was found in the path.

  Note that annotation using /proc/kcore requires CAP_SYS_RAWIO
  capability.

  Please use:

  perf buildid-cache -vu vmlinux

  Note this is being run as root and /proc/kcore is accessible with dd from the 
same shell:
  $ dd if=/proc/kcore bs=8 count=16 | hexdump
  000 457f 464c 0102 0001    
  010 0004 00b7 0001     
  020 0040       
  030   0040 0038 0003   
  040 0004    00e8   

  Additionally, installing the linux-image-4.10.0-13-generic-dbgsym
  actually hurts the situation because the symbol addresses in the
  dbgsym don't match the kernel addresses.

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

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

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-27 Thread Joseph Salisbury 
The bisect reported the following commit as the first bad commit:

commit 8df3e3271ae0bd4d85aff701abc88d6b5526f7fe
Author: Long Li 
Date:   Mon Feb 13 06:05:20 2017 -0700

scsi: storvsc: properly set residual data length on errors


I built a test kernel with that commit reverted.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1674635/revert

Can you test that kernel and report back if it has the bug or not?

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1664622] Re: qemu: Missing transaction memory advertisement

2017-03-27 Thread Rafael Folco 
Yep, makes sense. 
If 16.04.2 works as stated above, the job is done here.
Thanks.

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

Title:
  qemu: Missing transaction memory advertisement

Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Incomplete
Status in qemu source package in Yakkety:
  Incomplete

Bug description:
  [Impact]

   * The non HW assisted virtualization (kvm-pr) on PowerPC announces 
 support for the Transactional memory feature but does not fully 
 support it. Due to that guests crash.

   * The fix essentially takes away the TM feature by default and only 
 enables it incertain cases where it is correct (right HW and recent 
 KVM-HV implementation)

  
  [Test Case]

   * Repro
 1. install uvtool-libvirt in Host
 2. uvt-simplestreams-libvirt sync --source 
http://cloud-images.ubuntu.com/daily arch=ppc64el label=daily release=xenial
 3. $ cat /home/ubuntu/ppc-template.xml
  

  hvm
  


  
  
  


  


  
  


  
  

  
  

  
 4. $ uvt-kvm create --memory 4096 --template /home/ubuntu/ppc-template.xml 
--password=ubuntu --ssh-public-key-file /home/ubuntu/.ssh/authorized_keys 
kvmguest-xenial-level1 release=xenial arch=ppc64el label=daily
 5. log into this guest (all following steps are in level1 guest to 
spawn a level2 guest)
 6. ensure kvm_pr is loaded correctly
This is in the extras package which is not installed by default 
(other bug). Get it with
$ apt-get install linux-image-extra-virtual
$ modprobe kvm_pr
$ lsmod | grep kvm_pr
 7. make sure libvirt default network can start in 2nd level
There likely is a network collision, use virsh net-edit to dix and 
then virsh net-start to start the network
 8. Get Original Xenial Ubuntu image
wget 
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-server-ppc64el.iso
 9. sudo apt install virtinst
  10. $ virt-install --virt-type=kvm --cpu=host --name=nested-xenial 
--controller type=scsi,model=virtio-scsi --graphics none --console 
pty,target_type=serial --disk 
path=/home/ubuntu/test-xenial-virt-inst.qcow2,size=4 --vcpus=4 --ram=2048 
--os-type=linux --os-variant ubuntu16.04 --network bridge=virbr0,model=virtio 
--cdrom=ubuntu-16.04-server-ppc64el.iso
 11. See crash on guest install/boot

   * Installing the fixed qemu in the 1st level (not on Bare Metal)
  before retrying step 11 should show the issue being fixed

  [Regression Potential]

   * It is changing features announced to the guest, but then it is only 
 taking it away in cases it won't work

   * The change is ppc64el "only" which restricts the audience to be hit  
 by regressions and even there kvm_pr (problem state virtualization) 
 is a rare case usually only for Testing/CI

   * Changes are upstream in qemu a while now without being revoked and 
 come from IBM themselves.

  
  --- 


  == Comment: #0 - Breno Henrique Leitao  - 2017-02-14 
10:03:03 ==
  We don't support transactional memory in PR KVM, so don't tell the OS that we 
do.

  These are the required patches:

  commit 2e68f28854f0120c9a938a61b64aaf1eaecb162b
  Author: Thomas Huth 
  Date:   Wed Sep 28 13:16:30 2016 +0200

  ppc: Check the availability of transactional memory

  KVM-PR currently does not support transactional memory, and the
  implementation in TCG is just a fake. We should not announce TM
  support in the ibm,pa-features property when running on such a
  system, so disable it by default and only enable it if the KVM
  implementation supports it (i.e. recent versions of KVM-HV).
  These changes are based on some earlier work from Anton Blanchard
  (thanks!).

  Signed-off-by: Thomas Huth 
  Reviewed-by: C?dric Le Goater 
  Signed-off-by: David Gibson 
  (cherry picked from commit bac3bf287ab60e264b636f5f00c116a19b655762)

  commit 45a4f18e2ec40b96893c780c28ab18c246906355
  Author: Thomas Huth 
  Date:   Wed Sep 28 13:16:29 2016 +0200

  hw/ppc/spapr: Fix the selection of the processor features

  The current code uses pa_features_206 for POWERPC_MMU_2_06, and
  for everything else, it uses pa_features_207. This is bad in some
  cases because there is also a "degraded" MMU version of ISA 2.06,
  called POWERPC_MMU_2_06a, which should of course use the flags for
  2.06 instead. And there is also the possibility that the user runs
  the pseries machine with a POWER5+ or even 970 processor. In that
  case we certainly do not want to set the flags for 2.07, and rather
  simply skip the setting of the pa-features property instead.

  Signed-off-by:

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-27 Thread Marcin Banaszek 
b4e22b8a3d9d5746380e8d400cd9134567ffe675 works fine.

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-27 Thread Joseph Salisbury 
I built the next test kernel, up to the following commit:
b4e22b8a3d9d5746380e8d400cd9134567ffe675

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1674635/b4e22b8a3d9d5746380e8d400cd9134567ffe675

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 4898-1213-1192-4801-7611-1594-99
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

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

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

2017-03-27 Thread bugproxy 
--- Comment From lagar...@br.ibm.com 2017-03-27 13:44 EDT---
Thanks, Christian. I agree that, in this case, there isn't much we can do in 
QEMU.

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

Title:
  qemu: Missing transaction memory advertisement

Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Incomplete
Status in qemu source package in Yakkety:
  Incomplete

Bug description:
  [Impact]

   * The non HW assisted virtualization (kvm-pr) on PowerPC announces 
 support for the Transactional memory feature but does not fully 
 support it. Due to that guests crash.

   * The fix essentially takes away the TM feature by default and only 
 enables it incertain cases where it is correct (right HW and recent 
 KVM-HV implementation)

  
  [Test Case]

   * Repro
 1. install uvtool-libvirt in Host
 2. uvt-simplestreams-libvirt sync --source 
http://cloud-images.ubuntu.com/daily arch=ppc64el label=daily release=xenial
 3. $ cat /home/ubuntu/ppc-template.xml
  

  hvm
  


  
  
  


  


  
  


  
  

  
  

  
 4. $ uvt-kvm create --memory 4096 --template /home/ubuntu/ppc-template.xml 
--password=ubuntu --ssh-public-key-file /home/ubuntu/.ssh/authorized_keys 
kvmguest-xenial-level1 release=xenial arch=ppc64el label=daily
 5. log into this guest (all following steps are in level1 guest to 
spawn a level2 guest)
 6. ensure kvm_pr is loaded correctly
This is in the extras package which is not installed by default 
(other bug). Get it with
$ apt-get install linux-image-extra-virtual
$ modprobe kvm_pr
$ lsmod | grep kvm_pr
 7. make sure libvirt default network can start in 2nd level
There likely is a network collision, use virsh net-edit to dix and 
then virsh net-start to start the network
 8. Get Original Xenial Ubuntu image
wget 
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-server-ppc64el.iso
 9. sudo apt install virtinst
  10. $ virt-install --virt-type=kvm --cpu=host --name=nested-xenial 
--controller type=scsi,model=virtio-scsi --graphics none --console 
pty,target_type=serial --disk 
path=/home/ubuntu/test-xenial-virt-inst.qcow2,size=4 --vcpus=4 --ram=2048 
--os-type=linux --os-variant ubuntu16.04 --network bridge=virbr0,model=virtio 
--cdrom=ubuntu-16.04-server-ppc64el.iso
 11. See crash on guest install/boot

   * Installing the fixed qemu in the 1st level (not on Bare Metal)
  before retrying step 11 should show the issue being fixed

  [Regression Potential]

   * It is changing features announced to the guest, but then it is only 
 taking it away in cases it won't work

   * The change is ppc64el "only" which restricts the audience to be hit  
 by regressions and even there kvm_pr (problem state virtualization) 
 is a rare case usually only for Testing/CI

   * Changes are upstream in qemu a while now without being revoked and 
 come from IBM themselves.

  
  --- 


  == Comment: #0 - Breno Henrique Leitao  - 2017-02-14 
10:03:03 ==
  We don't support transactional memory in PR KVM, so don't tell the OS that we 
do.

  These are the required patches:

  commit 2e68f28854f0120c9a938a61b64aaf1eaecb162b
  Author: Thomas Huth 
  Date:   Wed Sep 28 13:16:30 2016 +0200

  ppc: Check the availability of transactional memory

  KVM-PR currently does not support transactional memory, and the
  implementation in TCG is just a fake. We should not announce TM
  support in the ibm,pa-features property when running on such a
  system, so disable it by default and only enable it if the KVM
  implementation supports it (i.e. recent versions of KVM-HV).
  These changes are based on some earlier work from Anton Blanchard
  (thanks!).

  Signed-off-by: Thomas Huth 
  Reviewed-by: C?dric Le Goater 
  Signed-off-by: David Gibson 
  (cherry picked from commit bac3bf287ab60e264b636f5f00c116a19b655762)

  commit 45a4f18e2ec40b96893c780c28ab18c246906355
  Author: Thomas Huth 
  Date:   Wed Sep 28 13:16:29 2016 +0200

  hw/ppc/spapr: Fix the selection of the processor features

  The current code uses pa_features_206 for POWERPC_MMU_2_06, and
  for everything else, it uses pa_features_207. This is bad in some
  cases because there is also a "degraded" MMU version of ISA 2.06,
  called POWERPC_MMU_2_06a, which should of course use the flags for
  2.06 instead. And there is also the possibility that the user runs
  the pseries machine with a POWER5+ or even 970 processor. In that
  case we certainly do not want to set the flags for 2.07, and rather
  simply skip

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

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

apport-collect 1633769

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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

[Kernel-packages] [Bug 1633769] Re: Bug with kernel 4.8

2017-03-27 Thread Никитушкин Андрей 
Почему никто не хочет обратить внимание на данный баг, который проявился
после версии ядра 4.7 в последующих ядрах 4.8, 4.9, 4.10?

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

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

Title:
  Bug with kernel 4.8

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have a problem after upgrading from Kubuntu 16.04 to Kubuntu 16.10 with 
kernel 4.8:
  1. For a long time to wait start window to enter a password encrypted 
parasitic system partition at boot.
  2. Self loading process began last very long, 2 times longer than the 
previous kernel 4.4.0.
  3. Fails to boot Plasma KDE 4.8.0 with the kernel, the old kernel 4.4.0 works 
fine.
  4. Kernel logs file attachment in this message.
  5. My hardware is Acer Extensa 5220, i960M chipset, Intel GMA 3100.

  Please correct your mistakes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1633769/+subscriptions

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

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

2017-03-27 Thread l3iggs 
I've attached a trace for the 4.11 kernel.

First
echo xhci-hcd >> /sys/kernel/debug/tracing/set_event

Then initiate network transport to create the bug.

/sys/kernel/debug/tracing/trace (as 4.11.trace.txt)
and
dmesg (as 4.11.dmesg.txt) are attached.

** Attachment added: "4.11.trace.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750/+attachment/4847786/+files/4.11.trace.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/1667750

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New
Status in linux package in Fedora:
  New

Bug description:
  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx timeout
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:09 ubuntu kerne

  1   2   >