[Kernel-packages] [Bug 1491654] Re: Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04 installation

2017-01-08 Thread Leo-Chen
I have one question, How to install the v4.10.deb file on OS
installation ?

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

Title:
  Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04
  installation

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  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:
  Current Behavior
  ==
  1. Intel P3700 PCIe SSD string shows "Unknow" during Ubuntu 14.04 install.

  Reference Verification
  ==
  1. Which version of previous BIOS/BMC/HW passed/failed? 1st Test
  2. Which similar project/product passed/failed? NA

  Steps to reproduce the problem
  ==
  1. Install Intel P3700 PCIe SSD*2 and SAS 12G HDD*8 with LSI 3108 into SUT.
  2. Power on system and install Ubuntu 14.04.
  3. Intel P3700 PCIe SSD string shows "Unknown" during OS install.

  Expected Behavior
  ==
  1. Intel P3700 PCIe SSD string should not show "Unknown" during Ubuntu 14.04 
install.

  Pcie SSD config:HDD/SSD:Intel,SSDPE2MD016T4,PCI-e,1.6TB,Gen3

  
  Copied from private bug 1454945.

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

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


[Kernel-packages] [Bug 1382490] Re: Broadcom Bluetooth [413c:8143] does not work at all

2017-01-08 Thread Po-Hsu Lin
I found this thread on the Internet:
[PATCH 4/6] Bluetooth: Add support for Broadcom 413c:8143
http://www.spinics.net/lists/linux-bluetooth/msg56348.html

But just like Nish mentioned here, it looks like this was never got
merged.

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

Title:
  Broadcom Bluetooth [413c:8143] does not work at all

Status in HWE Next:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201307-13942 Dell Latitude E5540

  The Bluetooth can't find any devices.
  Error message could be found in dmesg:
  [   98.149145] Bluetooth: can't load firmware, may not work correctly

  Note that sometimes it works, but if you disable and re-enable it with
  the wifi slider (let it reload the firmware), it will stop working.

  Steps:
  1. Install 14.04.1 + update (3.13.0-37) + proprietary Broadcom driver
  2. Try to pair with any other Bluetooth device.

  Expected result:
  * Bluetooth works well as expected.

  Actual result:
  * Nothing can be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-37-generic 3.13.0-37.64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1542 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1542 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 17 04:14:55 2014
  HibernationDevice: RESUME=UUID=b150a530-b9dc-40f0-b867-a29dfbf5b499
  InstallationDate: Installed on 2014-10-17 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E5540
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=7a7e4c31-030c-4e00-af99-14797716597e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0V19JF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd09/19/2013:svnDellInc.:pnLatitudeE5540:pvr01:rvnDellInc.:rn0V19JF:rvrX02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5540
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1652018] Re: PowerNV: PCI Slot is invalid after fencedPHB Error injection

2017-01-08 Thread bugproxy
** Tags added: bugnameltc-150063 severity-high

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

Title:
  PowerNV: PCI Slot is invalid after fencedPHB Error injection

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

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2016-12-21 
01:16:41 ==
  ---Problem Description---
  PCI Slot is in invalid state after fencedPHB Error injection Test.
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux brigstrat1p1 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:46:13 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV CSE-829U 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot the system to runtime.
  2. Inject fencedPHB Error.
  echo 0x8000 > /sys/kernel/debug/powerpc/PCI0002/err_injct_outbound

  
  dmesg:
  [42725.641368] EEH: PHB#2 failure detected, location: N/A
  [42725.641450] CPU: 8 PID: 898 Comm: kworker/u320:1 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [42725.641461] Workqueue: i40e i40e_service_task [i40e]
  [42725.641464] Call Trace:
  [42725.641469] [c407f9e0] [c0b13b4c] dump_stack+0xb0/0xf0 
(unreliable)
  [42725.641474] [c407fa20] [c00376e0] 
eeh_dev_check_failure+0x200/0x580
  [42725.641477] [c407fac0] [c0037ae4] 
eeh_check_failure+0x84/0xd0
  [42725.641485] [c407fb00] [d00035845710] 
i40e_service_task+0x17b0/0x1a30 [i40e]
  [42725.641489] [c407fc50] [c00dde10] 
process_one_work+0x1e0/0x5a0
  [42725.641492] [c407fce0] [c00de364] worker_thread+0x194/0x680
  [42725.641496] [c407fd80] [c00e6e60] kthread+0x110/0x130
  [42725.641499] [c407fe30] [c0009538] 
ret_from_kernel_thread+0x5c/0xa4
  [42725.641509] EEH: Detected error on PHB#2
  [42725.641514] EEH: This PCI device has failed 1 times in the last hour
  [42725.641516] EEH: Notify device drivers to shutdown
  [42725.641523] i40e 0002:01:00.0: i40e_pci_error_detected: error 2
  [42725.641907] i40e 0002:01:00.0: VSI seid 396 Tx ring 0 disable timeout
  [42725.642144] i40e 0002:01:00.0: VSI seid 396 Rx ring 0 disable timeout
  [42725.666205] i40e 0002:01:00.1: i40e_pci_error_detected: error 2
  [42725.666499] i40e 0002:01:00.2: i40e_pci_error_detected: error 2
  [42725.666533] i40e 0002:01:00.0: ARQ event error -32
  [42725.01] i40e 0002:01:00.3: i40e_pci_error_detected: error 2
  [42725.666700] EEH: Collect temporary log
  [42725.666702] PHB3 PHB#2 Diag-data (Version: 1)
  [42725.666703] brdgCtl: 
  [42725.666704] UtlSts:  0010  
  [42725.666706] RootSts:     
  [42725.666707] RootErrSts:    
  [42725.666708] RootErrLog:     
  [42725.666709] RootErrLog1:   
  [42725.666711] nFir:8080 0030006e 8000
  [42725.666712] PhbSts:  0018 0018
  [42725.666713] Lem: 8280 42498e367f502eae 8000
  [42725.666715] OutErr:  8020 8000 
12080063fffe 402002a8
  [42725.666716] InBErr:  4000 4000 
0800 000c10c01001
  [42725.666718] EEH: Reset without hotplug activity
  [42730.052455] EEH: Notify device drivers the completion of reset
  [42730.053334] EEH: Notify device driver to resume
  [42730.184457] i40e 0002:01:00.0 enP2p1s0f0: NIC Link is Down
  [42731.568230] i40e 0002:01:00.0 enP2p1s0f0: NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: None

  
  OPAL LOG:
  [42990.475630456,7] PHB#0002: CRESET: Starts
  [42990.482717333,7] PHB#0002: CRESET: No pending transactions
  [42991.023963215,7] PHB#0002: CRESET: Reinitialization
  [42991.023964143,7] PHB#0002: Initializing PHB...
  [42991.075167078,7] PHB#0002: Core revision 0xa30005
  [42991.075171529,7] PHB#0002: Default system config: 0x421100fc3000
  [42991.075172655,7] PHB#0002: New system config: 0x421000fc3000
  [42991.075174000,7] PHB#0002: PHB_RESET is 0x2000
  [42991.075410938,7] PHB#0002: Waiting for DLP PG reset to complete...
  [42991.083713914,7] PHB#0002: Initialization complete
  [42991.136599535,7] PHB#0002: FRESET: Starts
  [42991.136600954,7] PHB#0002: FRESET: Prepare for link down
  [42991.136602933,7] PHB#0002: FRESET: Assert
  [42992.138625290,7] PHB#0002: FRESET: Deassert
  [42993.140657592,7] PHB#0002: LINK: Start polling
  [42993.193893558,7] PHB#0002: LINK: Electrical link detected
  [42993.247138072,7] PHB#0002: LINK: Link is up
  [42993.247174237,3] PCI-SLOT-0002 Invalid 

[Kernel-packages] [Bug 1654790] Re: Dell DW1550 - Ubuntu 16.10 WLAN works Bluetooth not

2017-01-08 Thread Po-Hsu Lin
*** This bug is a duplicate of bug 1382490 ***
https://bugs.launchpad.net/bugs/1382490

Marking this as duplicated for the following device:
Bus 003 Device 003: ID 413c:8143 Dell Computer Corp.

Please feel free to open new bug reports against other two BT adapters if 
they're are not working
Bus 003 Device 005: ID 0b05:17cb ASUSTek Computer, Inc. Broadcom BCM20702A0 
Bluetooth
Bus 003 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth

** This bug has been marked a duplicate of bug 1382490
   Broadcom Bluetooth [413c:8143] does not work at all

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

Title:
  Dell DW1550 - Ubuntu 16.10 WLAN works Bluetooth not

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://askubuntu.com/questions/869008/dell-dw1550-ubuntu-16-10?

  usb-devices | awk '/8143/' RS=

  cat: '/sys/bus/usb/devices/usb3/3-2/3-*:?.*/bInterfaceNumber': Datei oder 
Verzeichnis nicht gefunden
  cat: '/sys/bus/usb/devices/usb3/3-2/3-*:?.*/bAlternateSetting': Datei oder 
Verzeichnis nicht gefunden
  cat: '/sys/bus/usb/devices/usb3/3-2/3-*:?.*/bNumEndpoints': Datei oder 
Verzeichnis nicht gefunden
  cat: '/sys/bus/usb/devices/usb3/3-2/3-*:?.*/bInterfaceClass': Datei oder 
Verzeichnis nicht gefunden
  cat: '/sys/bus/usb/devices/usb3/3-2/3-*:?.*/bInterfaceSubClass': Datei oder 
Verzeichnis nicht gefunden
  cat: '/sys/bus/usb/devices/usb3/3-2/3-*:?.*/bInterfaceProtocol': Datei oder 
Verzeichnis nicht gefunden
  /usr/bin/usb-devices: Zeile 79: printf: (none): Ungültige Zahl.
  T:  Bus=03 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=413c ProdID=8143 Rev=01.12
  S:  Manufacturer=Broadcom Corp
  S:  Product=BCM20702A0
  S:  SerialNumber=24FD52441F44
  C:  #Ifs= 0 Cfg#= 0 Atr= MxPwr=
  I:  If#= 0 Alt= 0 #EPs= 0 Cls=() Sub= Prot= Driver=

  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
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ps 1869 F pulseaudio
   /dev/snd/controlC1:  ps 1869 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jan  7 22:28:19 2017
  HibernationDevice: RESUME=UUID=721ba732-9cef-4ad6-b9b5-ddf3baf0e6c4
  InstallationDate: Installed on 2016-12-24 (14 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Alienware Alienware X51 R2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=9088b2c3-b7ec-413f-8696-e092752b1d73 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: A10
  dmi.board.name: 0PGRP5
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnAlienware:bvrA10:bd07/13/2015:svnAlienware:pnAlienwareX51R2:pvr00:rvnAlienware:rn0PGRP5:rvrA01:cvnAlienware:ct3:cvr00:
  dmi.product.name: Alienware X51 R2
  dmi.product.version: 00
  dmi.sys.vendor: Alienware

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

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


[Kernel-packages] [Bug 1600361] Re: NVME crashes Ubuntu 16.04

2017-01-08 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/1600361

Title:
  NVME crashes Ubuntu 16.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  Description:Ubuntu 16.04 LTS  


  Release:16.04 

  On a brand new Supermicro Chassis (SuperServer 1028R-WTNRT) we have
  installed Ubuntu 16.04 onto a pair of SAMSUNG SM863 SSDs in soft Raid
  1. We originally tried to install Ubuntu 16.04 to two NVMe drives
  (Intel® SSD DC P3700) but the Ubuntu install could not see both
  drives, Only one. Howerver Ubuntu Server 14.04 saw them and worked
  perfectly. After the install to the SSDs I plugged in the two NVMe
  drives and the server has had nothing but issues since.

  I attached the dmesg errors.

  The errors seen in the dmesg file attached just continue to repeat
  over and over again. The server locks up and no longer responds.

  Any ideas or fixes would be appreciated.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:32 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-06-30 (11 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro SYS-1028R-WTNRT
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=124ae1c9-44f6-44b3-a199-11c8d63289d7 ro
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 02/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRW-NT
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd02/03/2016:svnSupermicro:pnSYS-1028R-WTNRT:pvr0123456789:rvnSupermicro:rnX10DRW-NT:rvr1.01A:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: SYS-1028R-WTNRT
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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


[Kernel-packages] [Bug 1515087] Re: remote no longer works on wily

2017-01-08 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/1515087

Title:
  remote no longer works on wily

Status in linux package in Ubuntu:
  Expired

Bug description:
  since upgrading to wily, my tivo slide pro no longer has many of its
  keys recognized by the kernel. xev shows that many keys no longer
  register.

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

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


[Kernel-packages] [Bug 1639629] Re: can't change sensitivity on (new) Alps trackstick

2017-01-08 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/1639629

Title:
  can't change sensitivity on (new) Alps trackstick

Status in linux package in Ubuntu:
  Expired

Bug description:
  On a Toshiba z20t using Ubuntu 16.04, I can't change the sensitivity
  via

  echo 200 | sudo tee /sys/devices/platform/i8042/serio1/serio2/sensitivity
  echo 150 | sudo tee /sys/devices/platform/i8042/serio1/serio2/speed
  echo 1 | sudo tee /sys/devices/platform/i8042/serio1/serio2/press_to_select 

  as pointed out in https://wiki.ubuntuusers.de/Trackpoint/, because
  these virtual files are missing.

  dmesg:
  [4.517356] input: AlpsPS/2 ALPS DualPoint Stick as 
/devices/platform/i8042/serio1/input/input7
  [4.544238] input: AlpsPS/2 ALPS DualPoint TouchPad as 
/devices/platform/i8042/serio1/input/input5
  [ 2213.365432] input: AlpsPS/2 ALPS DualPoint Stick as 
/devices/platform/i8042/serio1/input/input22
  [ 2213.394015] input: AlpsPS/2 ALPS DualPoint TouchPad as 
/devices/platform/i8042/serio1/input/input21
  [ 2322.626764] input: AlpsPS/2 ALPS DualPoint Stick as 
/devices/platform/i8042/serio1/input/input25
  [ 2322.655136] input: AlpsPS/2 ALPS DualPoint TouchPad as 
/devices/platform/i8042/serio1/input/input24

  ls -lisa:
  ls -lisa /sys//devices/platform/i8042/serio1/input/input25/*
  27517 0 lrwxrwxrwx 1 root root0 Nov  6 22:23 
/sys//devices/platform/i8042/serio1/input/input25/device -> ../../../serio1
  27527 0 -r--r--r-- 1 root root 4096 Nov  6 22:23 
/sys//devices/platform/i8042/serio1/input/input25/modalias
  27519 0 -r--r--r-- 1 root root 4096 Nov  6 16:26 
/sys//devices/platform/i8042/serio1/input/input25/name
  27525 0 -r--r--r-- 1 root root 4096 Nov  6 22:23 
/sys//devices/platform/i8042/serio1/input/input25/phys
  27534 0 -r--r--r-- 1 root root 4096 Nov  6 16:26 
/sys//devices/platform/i8042/serio1/input/input25/properties
  27515 0 lrwxrwxrwx 1 root root0 Nov  6 16:26 
/sys//devices/platform/i8042/serio1/input/input25/subsystem -> 
../../../../../../class/input
  27509 0 -rw-r--r-- 1 root root 4096 Nov  6 16:26 
/sys//devices/platform/i8042/serio1/input/input25/uevent
  27526 0 -r--r--r-- 1 root root 4096 Nov  6 22:23 
/sys//devices/platform/i8042/serio1/input/input25/uniq

  Tries the mainline kernel - no change.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   michi 28816 F...m pulseaudio
   /dev/snd/pcmC0D0p:   michi 28816 F...m pulseaudio
   /dev/snd/controlC0:  michi 28816 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  Tags:  xenial
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1639211] Re: Driver

2017-01-08 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/1639211

Title:
  Driver

Status in linux package in Ubuntu:
  Expired

Bug description:
  my ubuntu 16.04 didnt recognize nvidia driver

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  faraz  1917 F pulseaudio
   /dev/snd/controlC1:  faraz  1917 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov  4 19:25:15 2016
  HibernationDevice: RESUME=UUID=cda5f7ba-35ac-451f-b2fa-e5084669a949
  InstallationDate: Installed on 2016-10-23 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X455LD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic 
root=UUID=aacdb7b3-44d8-40c4-a768-92cdc220a654 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X455LD.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X455LD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX455LD.202:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnX455LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X455LD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1639600] Re: Number of processes exceeds 1250

2017-01-08 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/1639600

Title:
  Number of processes exceeds 1250

Status in linux package in Ubuntu:
  Expired

Bug description:
  At times when the linux-image-4.8.0-27 kernel is used it spawns more
  than 1250 processes and this can be seen using the top command. More
  amount of kworker processes are being spawned.

  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
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uday   5886 F pulseaudio
   /dev/snd/controlC1:  uday   5886 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Nov  6 22:51:39 2016
  HibernationDevice: RESUME=UUID=1aa7fbdf-3bda-4de7-8c34-5a6445ce6600
  InstallationDate: Installed on 2015-02-14 (631 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 3542
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=9ce2f167-b3df-4db5-bb27-44102031030d ro reboot=acpi
  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: Upgraded to yakkety on 2016-10-14 (22 days ago)
  dmi.bios.date: 08/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0926J6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0926J6:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1640440] Re: error message after upgrade

2017-01-08 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/1640440

Title:
  error message after upgrade

Status in linux package in Ubuntu:
  Expired

Bug description:
  error messages began to appear after a recent upgrade.

  ProblemType: KernelCrash
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-100-generic 3.13.0-100.147
  ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-100-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  calvin 2351 F pulseaudio
  Date: Fri Nov  4 22:52:13 2016
  HibernationDevice: RESUME=UUID=c5431ae8-fe70-4259-bc8b-ea1af1e36eb2
  InstallationDate: Installed on 2014-07-29 (833 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude D830
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-100-generic 
root=UUID=93bbc0bb-e609-4fb0-92c7-1f19ecab48b4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-100-generic N/A
   linux-backports-modules-3.13.0-100-generic  N/A
   linux-firmware  1.127.22
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HN341
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd11/05/2007:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0HN341:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D830
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1640590] Re: Issues on include/linux/moduleloader.h, kernel/module.c

2017-01-08 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/1640590

Title:
  Issues on  include/linux/moduleloader.h, kernel/module.c

Status in linux package in Ubuntu:
  Expired

Bug description:
  On these files inline  declaration is used to supress messages from
  compiler.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: sep3_15 pax
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu2800 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Nov  9 22:03:47 2016
  InstallationDate: Installed on 2016-04-29 (194 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

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

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


[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

2017-01-08 Thread Thinkren
Never mind.  Despite the dirty shutdown, a subsequent post-installation
update resolved the problem.

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

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

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


[Kernel-packages] [Bug 1644557] Re: crypto : tolerate new crypto hardware for z Systems

2017-01-08 Thread Po-Hsu Lin
Hello folks,
can anyone help us to verify this fix in -proposed?
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/1644557

Title:
  crypto : tolerate new crypto hardware for z Systems

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  crypto : tolerate new crypto hardware for z Systems

  cherrypick patches from v4.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644557/+subscriptions

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


[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

2017-01-08 Thread Leo-Chen
After update test the 4.8 was pass,it is work in tty1
Also update 4.4.40 same PASS

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  In Progress

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

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

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


[Kernel-packages] [Bug 1649584] Re: Kernel update 3.13.0-105 causes SATA errors that end up remounting partitions as read-only

2017-01-08 Thread Marcus Aurelius
I'm confirming that it's reproducible in 3.13.0-106-generic and
3.13.0-107-generic (although it seems to happen much less often).

I will run on 3.13.0-100-generic for a while to be sure it works well
and to (try to) rule out the possibility of a hardware fault.

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

Title:
  Kernel update 3.13.0-105 causes SATA errors that end up remounting
  partitions as read-only

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I started to notice SATA errors on my secondary hard disk (a Toshiba
  DT01ACA100 1TB, on an Intel DG45ID motherboard) after updating to
  3.13.0-105. A simple file copy operation fails after a few megabytes
  and the drive stops responding. Sometimes it remounts itself as read-
  only, and sometimes it disappears from the drive list. On next reboot
  the drive is sort-of OK, but without the new files.

  I thought it was a hard disk failure, but reverting to 3.13.0-100
  seems to fix the problem completely. SMART is OK and fsck checks
  passed.

  I'll try to post more details about my system later when I'm back to my home 
computer.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcuscf   2558 F pulseaudio
   /dev/snd/controlC0:  marcuscf   2558 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=6b4b37f4-4276-4541-8e40-36a0b8570265
  InstallationDate: Installed on 2012-05-12 (1676 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic 
root=UUID=15c44951-2c8d-4c57-b8ff-e46deebb7b4a ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-105-generic N/A
   linux-backports-modules-3.13.0-105-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-105-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2016-11-03 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/25/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: IDG4510H.86A.0135.2011.0225.1100
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DG45ID
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE27729-310
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrIDG4510H.86A.0135.2011.0225.1100:bd02/25/2011:svn:pn:pvr:rvnIntelCorporation:rnDG45ID:rvrAAE27729-310:cvn:ct3:cvr:

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

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


[Kernel-packages] [Bug 1654517] Re: ZFS I/O hangs for minutes

2017-01-08 Thread Karl-Philipp Richter
** Description changed:

  I/O for multiple programs, like `thunderbird`, `firefox`, etc., hangs
- for minutes, `dmesg` contains
+ for minutes and approx. 100 `z_rd_int_[n]` and `z_wr_int_[n]` kernel
+ threads are created, `dmesg` contains
  
- [ 9184.451606] INFO: task txg_sync:11471 blocked for more than 120 
seconds.
- [ 9184.451610]   Tainted: P   OE   4.8.0-32-generic #34-Ubuntu
- [ 9184.451611] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
- [ 9184.451612] txg_syncD a240ab3a7aa8 0 11471  2 
0x
- [ 9184.451616]  a240ab3a7aa8 00ffbb6ade1f a24095148000 
a240e5ca5580
- [ 9184.451618]  0046 a240ab3a8000 a240ff359200 
7fff
- [ 9184.451620]  a23d36cf9050 0001 a240ab3a7ac0 
bbe96b15
- [ 9184.451621] Call Trace:
- [ 9184.451627]  [] schedule+0x35/0x80
- [ 9184.451628]  [] schedule_timeout+0x22a/0x3f0
- [ 9184.451631]  [] ? __switch_to+0x2ce/0x6c0
- [ 9184.451633]  [] ? pick_next_task_fair+0x48c/0x4c0
- [ 9184.451635]  [] ? ktime_get+0x41/0xb0
- [ 9184.451636]  [] io_schedule_timeout+0xa4/0x110
- [ 9184.451644]  [] cv_wait_common+0xb2/0x130 [spl]
- [ 9184.451646]  [] ? wake_atomic_t_function+0x60/0x60
- [ 9184.451650]  [] __cv_wait_io+0x18/0x20 [spl]
- [ 9184.451689]  [] zio_wait+0xfd/0x1d0 [zfs]
- [ 9184.451716]  [] dsl_pool_sync+0xb8/0x480 [zfs]
- [ 9184.451745]  [] spa_sync+0x37f/0xb30 [zfs]
- [ 9184.451747]  [] ? default_wake_function+0x12/0x20
- [ 9184.451779]  [] txg_sync_thread+0x3a5/0x600 [zfs]
- [ 9184.451807]  [] ? txg_delay+0x160/0x160 [zfs]
- [ 9184.451811]  [] thread_generic_wrapper+0x71/0x80 
[spl]
- [ 9184.451815]  [] ? __thread_exit+0x20/0x20 [spl]
- [ 9184.451817]  [] kthread+0xd8/0xf0
- [ 9184.451819]  [] ret_from_fork+0x1f/0x40
- [ 9184.451821]  [] ? kthread_create_on_node+0x1e0/0x1e0
- [ 9184.451849] INFO: task mozStorage #2:21607 blocked for more than 120 
seconds.
- [ 9184.451851]   Tainted: P   OE   4.8.0-32-generic #34-Ubuntu
- [ 9184.451852] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
- [ 9184.451853] mozStorage #2   D a23fe8a5bd38 0 21607  19750 
0x0004
- [ 9184.451855]  a23fe8a5bd38 00ffa240ee8feb40 a240ecf72ac0 
a2403803b900
- [ 9184.451857]  bc2c02f7 a23fe8a5c000 a240aa940828 
a240aa940800
- [ 9184.451858]  a240aa940980  a23fe8a5bd50 
bbe96b15
- [ 9184.451860] Call Trace:
- [ 9184.451861]  [] schedule+0x35/0x80
- [ 9184.451866]  [] cv_wait_common+0x110/0x130 [spl]
- [ 9184.451868]  [] ? wake_atomic_t_function+0x60/0x60
- [ 9184.451872]  [] __cv_wait+0x15/0x20 [spl]
- [ 9184.451904]  [] zil_commit.part.11+0x79/0x7a0 [zfs]
- [ 9184.451909]  [] ? tsd_hash_search.isra.0+0x46/0xa0 
[spl]
- [ 9184.451913]  [] ? tsd_set+0x2b4/0x500 [spl]
- [ 9184.451914]  [] ? mutex_lock+0x12/0x30
- [ 9184.451945]  [] zil_commit+0x17/0x20 [zfs]
- [ 9184.451975]  [] zfs_fsync+0x7a/0xf0 [zfs]
- [ 9184.452005]  [] zpl_fsync+0x68/0xa0 [zfs]
- [ 9184.452008]  [] vfs_fsync_range+0x4b/0xb0
- [ 9184.452010]  [] do_fsync+0x3d/0x70
- [ 9184.452011]  [] SyS_fsync+0x10/0x20
- [ 9184.452013]  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
- [ 9184.452023] INFO: task bitcoin-msghand:663 blocked for more than 120 
seconds.
- [ 9184.452024]   Tainted: P   OE   4.8.0-32-generic #34-Ubuntu
- [ 9184.452025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
- [ 9184.452026] bitcoin-msghand D a23eeb23bd38 0   663  26994 
0x
- [ 9184.452028]  a23eeb23bd38 00ffa23eab434000 a240ecf7 
a24095148000
- [ 9184.452030]  a23eeb23bd20 a23eeb23c000 a240aa940828 
a240aa940800
- [ 9184.452031]  a240aa940980  a23eeb23bd50 
bbe96b15
- [ 9184.452033] Call Trace:
- [ 9184.452034]  [] schedule+0x35/0x80
- [ 9184.452039]  [] cv_wait_common+0x110/0x130 [spl]
- [ 9184.452041]  [] ? wake_atomic_t_function+0x60/0x60
- [ 9184.452044]  [] __cv_wait+0x15/0x20 [spl]
- [ 9184.452074]  [] zil_commit.part.11+0x79/0x7a0 [zfs]
- [ 9184.452079]  [] ? tsd_hash_search.isra.0+0x46/0xa0 
[spl]
- [ 9184.452083]  [] ? tsd_set+0x2b4/0x500 [spl]
- [ 9184.452084]  [] ? mutex_lock+0x12/0x30
- [ 9184.452113]  [] zil_commit+0x17/0x20 [zfs]
- [ 9184.452141]  [] zfs_fsync+0x7a/0xf0 [zfs]
- [ 9184.452168]  [] zpl_fsync+0x68/0xa0 [zfs]
- [ 9184.452170]  [] vfs_fsync_range+0x4b/0xb0
- [ 9184.452172]  [] do_fsync+0x3d/0x70
- [ 9184.452173]  [] SyS_fdatasync+0x13/0x20
- [ 9184.452174]  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
- [ 9305.221219] INFO: task txg_sync:11471 blocked for more than 120 
seconds.
- [ 

[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build

2017-01-08 Thread Mathew Hodson
** Changed in: crash (Ubuntu)
   Importance: Undecided => High

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

Title:
  Unable to analyse vmcore/dump via crash due to bad kernel debug info
  build

Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Trusty:
  Fix Committed

Bug description:
  [ Test case ]
  * trigger a kernel crash dump
  * use crash tool to analyse it
  * ... on ppc64el architecture

  
  == Comment: #0 - NAVEED A. UPPINANGADY SALIH  - 2016-07-01 02:41:07 ==
  ---Problem Description---
  Unable to analyse vmcore/kernel dumpfile generated by 4.4.0-29-generic kernel 
with ddeb kernel debuginfo available in 
http://ddebs.ubuntu.com/pool/main/l/linux/

  http://ddebs.ubuntu.com/pool/main/l/linux/linux-image-4.4.0-29
  -generic-dbgsym_4.4.0-29.48_ppc64el.ddeb

  ---uname output---
   4.4.0-29-generic #48~14.04.1-Ubuntu SMP Wed Jun 29 19:55:03 UTC 2016 ppc64le 
ppc64le ppc64le GNU/Linux

  Machine Type = model   : 8247-22L machine : PowerNV
  8247-22L

  ---Steps to Reproduce---
   # crash /usr/lib/debug/boot/vmlinux-4.4.0-29-generic 
/var/crash/201606300840/dump.201606300840
  crash 7.0.3
  ...
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  crash: invalid kernel virtual address: 61c2555c09c17994  type: "possible"
  WARNING: cannot read cpu_possible_map
  crash: invalid kernel virtual address: 8a0f6ddee20c4116  type: "present"
  WARNING: cannot read cpu_present_map
  crash: invalid kernel virtual address: 5a09344e320a1886  type: "online"
  WARNING: cannot read cpu_online_map
  WARNING: cannot read linux_banner string
  crash: /usr/lib/debug/boot/vmlinux-4.4.0-29-generic and 
/var/crash/201606300840/dump.201606300840 do not match!

  Userspace rpm: linux-image-4.4.0-29-generic-
  dbgsym_4.4.0-29.48_ppc64el.ddeb

  == Comment: #5 - Naresh Bannoth - 2016-07-27 04:12:09 ==

  The Latest kernel I am having is as follows

  root@ltcalpine-lp6:~# uname -a
  Linux ltcalpine-lp6 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 
01:03:56 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
  root@ltcalpine-lp6:~#

  >>> the issue same as posted originally.

  ...
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  crash: invalid kernel virtual address: 61c2555c09c17994  type: "possible"
  WARNING: cannot read cpu_possible_map
  crash: invalid kernel virtual address: 8a0f6ddee20c4116  type: "present"
  WARNING: cannot read cpu_present_map
  crash: invalid kernel virtual address: 5a09344e320a1886  type: "online"
  WARNING: cannot read cpu_online_map
  WARNING: cannot read linux_banner string
  crash: /usr/lib/debug/boot/vmlinux-4.4.0-31-generic and 
/var/crash/201607270248/dump.201607270248 do not match!

  == Comment: #6 - Hari Krishna Bathini - 2016-07-28 11:49:31 ==
  The kernel is compiled with gcc version 4.8.4 while the vmlinux pulled
  from http://ddebs.ubuntu.com/pool/main/l/linux/ is compiled with gcc
  version 5.3.1 which is the source of the issue.

   Resolved this by pulling the kernel debug symbols package from:

    deb http://ddebs.ubuntu.com/ -updates  main

  which indeed has the vmlinux compiled with gcc version 4.8.4.
  But I got this error:

    crash: invalid structure member offset: module_num_symtab
   FILE: kernel.c  LINE: 3049  FUNCTION: module_init()

  after the update owning to couple of missing patches listed below:

    commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
    Author: Dave Anderson 
    Date:   Wed Jan 20 09:56:36 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:

    commit 7523e4dc5057e157212b4741abd6256e03404cf1
    module: use a structure to encapsulate layout.

  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_init_text_size".
  (seb...@linux.vnet.ibm.com)

    commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
    Author: Dave Anderson 
    Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:

    commit 8244062ef1e54502ef55f54cced659913f244c3e
    modules: fix longstanding /proc/kallsyms vs module insertion race.

  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

  Applying the above patches on top of crash tool version 7.0.3-3ubuntu4.4,
  was able to analyze the dump. The patches apply cleanly..

  Thanks
  Hari

  == Comment: #8 - Naresh Bannoth - 2016-07-29 06:59:23 ==
  Verified with 4.4.0-31-generic kernel.
  on Applying the patches 

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools (saucy)

2017-01-08 Thread Dmitry Shachnev
Dear Tim or somebody from the kernel team — can you please reconsider my
patch, or reply to my proposal in comment #8?

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

Title:
  libcpupower.so is not installed from linux-tools (saucy)

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

Bug description:
  The patch for bug 1158668 installs cpupower_$(abi_version) command-
  line tool as well as libcpupower.so.$(abi_version).

  This isn't particularly suitable for projects that previously used
  libcpufreq and intend to migrate to libcpupower, because the
  libcpupower.so symlink is no longer installed. The command-line tools
  can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)).

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

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


[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers

2017-01-08 Thread Žygimantas Beručka
Well, I just did discovered something by accident. I *DID* manage to
start GDM3 just by executing 'gdm3' as *root* from a TTY. I am now able
to login just fine and GNOME works fine.

Launching GDM as a service (systemctl) does not work, though. Why is
this so? And what can I do to resolve the issue?

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

Title:
  Ubuntu GNOME boots to black screen when using proprietary Nvidia
  drivers

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in gdm3 source package in Xenial:
  Triaged
Status in linux source package in Xenial:
  Invalid

Bug description:
  Using latest Ubuntu Gnome x64 daily build with all updates installed. 
  Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure 
boot and other potentially problematic BIOS settings disabled.

  Can only see a black screen instead of a log-in screen after boot completes 
when proprietary Nvidia drivers are installed.
  Regular Ubuntu works absolutely fine on the same machine with the same driver 
version. Attempting to use older drivers on Ubuntu Gnome made no difference.

  Bug is affecting more than just me. We were talking about workarounds
  in ubuntuforums. User fthx claims that switching to lightdm fixes the
  issue
  http://ubuntuforums.org/showthread.php?t=2317628=13457703#post13457703

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-14-generic 4.4.0-14.30
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 19 23:19:21 2016
  HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6
  InstallationDate: Installed on 2016-03-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
  MachineType: LENOVO 80FG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed 
root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-14-generic N/A
   linux-backports-modules-4.4.0-14-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ABCN96WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo Z70-80
  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 Z70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80:
  dmi.product.name: 80FG
  dmi.product.version: Lenovo Z70-80
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers

2017-01-08 Thread Žygimantas Beručka
Similarly to comment #74, I have exactly the same symptoms on a Samsung
laptop with Intel HD4000 graphics (i.e. *no* nVidia or any other video
card is/was present). Moreover, it's a fresh install of Ubuntu 16.10. It
is also of note that I've never had this issue before on the same
machine with any of previous versions of Ubuntu Gnome, including 16.04
LTS with gnome3 ppa enabled.

On 16.10, I just cannot properly start GDM3 at all. It shows the same
black/dark grey background as has been mentioned and nothing else is
going on. Also, going to TTY1 does not work -- one is unable to do
anything on it; even CTRL-C does not work. Switching to TTY2, however,
works fine. I've looked at various log files, but to be honest, I don't
see any clues indicating what's the problem and where the process gets
stuck.

It works just fine with LightDM, though.

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

Title:
  Ubuntu GNOME boots to black screen when using proprietary Nvidia
  drivers

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in gdm3 source package in Xenial:
  Triaged
Status in linux source package in Xenial:
  Invalid

Bug description:
  Using latest Ubuntu Gnome x64 daily build with all updates installed. 
  Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure 
boot and other potentially problematic BIOS settings disabled.

  Can only see a black screen instead of a log-in screen after boot completes 
when proprietary Nvidia drivers are installed.
  Regular Ubuntu works absolutely fine on the same machine with the same driver 
version. Attempting to use older drivers on Ubuntu Gnome made no difference.

  Bug is affecting more than just me. We were talking about workarounds
  in ubuntuforums. User fthx claims that switching to lightdm fixes the
  issue
  http://ubuntuforums.org/showthread.php?t=2317628=13457703#post13457703

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-14-generic 4.4.0-14.30
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 19 23:19:21 2016
  HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6
  InstallationDate: Installed on 2016-03-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
  MachineType: LENOVO 80FG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed 
root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-14-generic N/A
   linux-backports-modules-4.4.0-14-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ABCN96WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo Z70-80
  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 Z70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80:
  dmi.product.name: 80FG
  dmi.product.version: Lenovo Z70-80
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1643341] Re: Unexpected shutdown

2017-01-08 Thread Sam_
Still the same with 4.4.0-59.80 - after 1½ minutes the fan starts, temperature 
moves from 42 to 24° then appears shutdown dialog and computer turns off.
I need to run mainline kernel otherwise I wouldn't be able to proceed updates. 
Mainline kernels make no trouble at all.
>From kern.log
4.9.0-040900rc6 ACPI: Thermal Zone [TZ0] (35 C)
4.4.0-59.80 ACPI: Thermal Zone [TZ0] (40 C)
4.9.0-040900 ACPI: Thermal Zone [TZ0] (11 C)

** Attachment added: "16:40:02-4.4.0-59.80"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643341/+attachment/4801634/+files/16%3A40%3A02-4.4.0-59.80

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

Title:
  Unexpected shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens twice in between a short time, 2-5 minutes, after the computer 
was turned on and Ubuntu desktop has started.
  It never happens a third time.
  From Ubuntu desktop, the cooler starts to run, a shutdown dialog with four 
options appears and computer turns off.
  I turn it on again and watch the same procedure happen again.
  I turn it on the third time, all is fine.

  4.4.0-47.68
  ACPI: Thermal Zone [TZ0] (11 C)

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68 and 4.4.0-49.70
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zootie 1897 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Nov 20 17:19:01 2016
  HibernationDevice: RESUME=UUID=6a848b08-24f4-499b-8281-8ba10097226d
  InstallationDate: Installed on 2016-11-02 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20160823)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 5986:055c Acer, Inc
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W65_W67RB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=31f6cc2f-d9df-473c-be2d-fd1abf719500 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_W67RB
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/16/2015:svnNotebook:pnW65_W67RB:pvrNotApplicable:rvnNotebook:rnW65_W67RB:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65_W67RB
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Kernel-packages] [Bug 1560473] Re: Fan doesn't work

2017-01-08 Thread Ming-Hung Tsai
Aspire ES1-331, bios 1.16, Ubuntu 16.04.1

After upgrading kernel to 4.4.0-57-generic via apt dist-upgrade, the fan seems 
work.
The fan starts working when the CPU temperature goes above 45'C, and stops when 
the CPU cool down.

Does anyone still having issues?

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

Title:
  Fan doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There is no fan support for this hardware. Fan speed changing only on
  reboot and stay the same until reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-34-generic 4.2.0-34.39
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob3618 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar 22 18:25:27 2016
  HibernationDevice: RESUME=UUID=0d193a72-b3ef-44a7-92c8-ed9df2de9807
  InstallationDate: Installed on 2015-12-01 (111 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e095 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed 
root=UUID=82b73f79-8d4f-453e-b9ad-fc07955aaa21 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-34-generic N/A
   linux-backports-modules-4.2.0-34-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire ES1-331
  dmi.board.vendor: Acer
  dmi.board.version: V1.13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.13
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.13:bd12/07/2015:svnAcer:pnAspireES1-331:pvrV1.13:rvnAcer:rnAspireES1-331:rvrV1.13:cvnAcer:ct10:cvrV1.13:
  dmi.product.name: Aspire ES1-331
  dmi.product.version: V1.13
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

2017-01-08 Thread Uranicus
Will someone pick this issue up? Or are you dropping this bug because
there will be a re-write of the bluetooth framework for the snappy image
later on?

Please let us know a bit of what is going on.

Thanks!

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

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

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

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


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

2017-01-08 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  ethernet interface connection crashes due to "NETDEV WATCHDOG:
  enx00e07cc862a1 (r8152): transmit queue 0 timed out"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  `dmesg` reveals

  [124280.117155] [ cut here ]
  [124280.117170] WARNING: CPU: 0 PID: 0 at 
/build/linux-_qw1uB/linux-4.8.0/net/sched/sch_generic.c:316 
dev_watchdog+0x22c/0x230
  [124280.117172] NETDEV WATCHDOG: enx00e07cc862a1 (r8152): transmit queue 
0 timed out
  [124280.117173] Modules linked in: openafs(POE) xfs libcrc32c uas 
usb_storage snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd 
soundcore iptable_filter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) bbswitch(OE) binfmt_misc zfs(PO) zunicode(PO) 
zcommon(PO) znvpair(PO) spl(O) zavl(PO) rtsx_usb_ms memstick usblp 
nls_iso8859_1 cdc_ether usbnet r8152 intel_rapl x86_pkg_temp_thermal coretemp 
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
aesni_intel uvcvideo aes_x86_64 videobuf2_vmalloc lrw videobuf2_memops 
glue_helper ablk_helper cryptd videobuf2_v4l2 intel_cstate videobuf2_core 
intel_rapl_perf hid_multitouch videodev media arc4 joydev input_leds iwldvm 
mac80211
  [124280.117232]  iwlwifi cfg80211 serio_raw lpc_ich ideapad_laptop 
sparse_keymap wmi mac_hid mei_me mei shpchp parport_pc ppdev lp sunrpc parport 
coda ip_tables x_tables autofs4 btrfs xor raid6_pq rtsx_usb_sdmmc rtsx_usb 
hid_generic usbhid hid psmouse ahci libahci i915 r8169 mii video i2c_algo_bit 
drm_kms_helper fjes syscopyarea sysfillrect sysimgblt fb_sys_fops drm
  [124280.117262] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P   OE   
4.8.0-32-generic #34-Ubuntu
  [124280.117263] Hardware name: LENOVO 20221/INVALID, BIOS 71CN51WW(V1.21) 
07/12/2013
  [124280.117266]  0286 83418944731d8c97 a240ff203d60 
bba2fc82
  [124280.117268]  a240ff203db0  a240ff203da0 
bb6830fb
  [124280.117270]  013cff2d9200  0001 

  [124280.117272] Call Trace:
  [124280.117273][] dump_stack+0x63/0x81
  [124280.117283]  [] __warn+0xcb/0xf0
  [124280.117285]  [] warn_slowpath_fmt+0x5f/0x80
  [124280.117289]  [] ? cpu_load_update+0xdd/0x150
  [124280.117291]  [] dev_watchdog+0x22c/0x230
  [124280.117292]  [] ? qdisc_rcu_free+0x40/0x40
  [124280.117298]  [] call_timer_fn+0x35/0x120
  [124280.117299]  [] run_timer_softirq+0x215/0x4b0
  [124280.117303]  [] ? ktime_get+0x41/0xb0
  [124280.117307]  [] ? lapic_next_deadline+0x26/0x30
  [124280.117310]  [] __do_softirq+0x10d/0x298
  [124280.117315]  [] irq_exit+0xa3/0xb0
  [124280.117316]  [] smp_apic_timer_interrupt+0x42/0x50
  [124280.117317]  [] apic_timer_interrupt+0x82/0x90
  [124280.117317][] ? 
cpuidle_enter_state+0x122/0x2c0
  [124280.117326]  [] cpuidle_enter+0x17/0x20
  [124280.117330]  [] call_cpuidle+0x2a/0x50
  [124280.117331]  [] cpu_startup_entry+0x2a0/0x350
  [124280.117338]  [] rest_init+0x77/0x80
  [124280.117341]  [] start_kernel+0x448/0x469
  [124280.117343]  [] ? 
early_idt_handler_array+0x120/0x120
  [124280.117344]  [] x86_64_start_reservations+0x24/0x26
  [124280.117346]  [] x86_64_start_kernel+0x14d/0x170
  [124280.117347] ---[ end trace a17e9d5abd1ea1de ]---

  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
  NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.8.0-32-generic.
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  ArecordDevices:
    Liste der Hardware-Geräte (CAPTURE) 
   Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC269VC Analog [ALC269VC Analog]
 Sub-Geräte: 1/1
 Sub-Gerät #0: subdevice #0
  AudioDevicesInUse:
   BEN.PID ZUGR.  BEFEHL
   /dev/snd/pcmC0D0p:   richter   20519 F...m pulseaudio
   /dev/snd/controlC0:  richter   20519 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xd361 irq 31'
 Mixer name : 'Realtek ALC269VC'
 Components : 'HDA:10ec0269,17aac034,00100202 
HDA:80862806,80860101,0010'
 Controls  : 30
 Simple ctrls  : 12
  CurrentDesktop: Unity
  Date: Sun Jan  8 15:03:36 2017
  HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
  InstallationDate: Installed on 2015-12-12 (393 days ago)
  InstallationMedia: Ubuntu 

[Kernel-packages] [Bug 1654849] [NEW] ethernet interface connection crashes due to "NETDEV WATCHDOG: enx00e07cc862a1 (r8152): transmit queue 0 timed out"

2017-01-08 Thread Karl-Philipp Richter
Public bug reported:

`dmesg` reveals

[124280.117155] [ cut here ]
[124280.117170] WARNING: CPU: 0 PID: 0 at 
/build/linux-_qw1uB/linux-4.8.0/net/sched/sch_generic.c:316 
dev_watchdog+0x22c/0x230
[124280.117172] NETDEV WATCHDOG: enx00e07cc862a1 (r8152): transmit queue 0 
timed out
[124280.117173] Modules linked in: openafs(POE) xfs libcrc32c uas 
usb_storage snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd 
soundcore iptable_filter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) bbswitch(OE) binfmt_misc zfs(PO) zunicode(PO) 
zcommon(PO) znvpair(PO) spl(O) zavl(PO) rtsx_usb_ms memstick usblp 
nls_iso8859_1 cdc_ether usbnet r8152 intel_rapl x86_pkg_temp_thermal coretemp 
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
aesni_intel uvcvideo aes_x86_64 videobuf2_vmalloc lrw videobuf2_memops 
glue_helper ablk_helper cryptd videobuf2_v4l2 intel_cstate videobuf2_core 
intel_rapl_perf hid_multitouch videodev media arc4 joydev input_leds iwldvm 
mac80211
[124280.117232]  iwlwifi cfg80211 serio_raw lpc_ich ideapad_laptop 
sparse_keymap wmi mac_hid mei_me mei shpchp parport_pc ppdev lp sunrpc parport 
coda ip_tables x_tables autofs4 btrfs xor raid6_pq rtsx_usb_sdmmc rtsx_usb 
hid_generic usbhid hid psmouse ahci libahci i915 r8169 mii video i2c_algo_bit 
drm_kms_helper fjes syscopyarea sysfillrect sysimgblt fb_sys_fops drm
[124280.117262] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P   OE   
4.8.0-32-generic #34-Ubuntu
[124280.117263] Hardware name: LENOVO 20221/INVALID, BIOS 71CN51WW(V1.21) 
07/12/2013
[124280.117266]  0286 83418944731d8c97 a240ff203d60 
bba2fc82
[124280.117268]  a240ff203db0  a240ff203da0 
bb6830fb
[124280.117270]  013cff2d9200  0001 

[124280.117272] Call Trace:
[124280.117273][] dump_stack+0x63/0x81
[124280.117283]  [] __warn+0xcb/0xf0
[124280.117285]  [] warn_slowpath_fmt+0x5f/0x80
[124280.117289]  [] ? cpu_load_update+0xdd/0x150
[124280.117291]  [] dev_watchdog+0x22c/0x230
[124280.117292]  [] ? qdisc_rcu_free+0x40/0x40
[124280.117298]  [] call_timer_fn+0x35/0x120
[124280.117299]  [] run_timer_softirq+0x215/0x4b0
[124280.117303]  [] ? ktime_get+0x41/0xb0
[124280.117307]  [] ? lapic_next_deadline+0x26/0x30
[124280.117310]  [] __do_softirq+0x10d/0x298
[124280.117315]  [] irq_exit+0xa3/0xb0
[124280.117316]  [] smp_apic_timer_interrupt+0x42/0x50
[124280.117317]  [] apic_timer_interrupt+0x82/0x90
[124280.117317][] ? 
cpuidle_enter_state+0x122/0x2c0
[124280.117326]  [] cpuidle_enter+0x17/0x20
[124280.117330]  [] call_cpuidle+0x2a/0x50
[124280.117331]  [] cpu_startup_entry+0x2a0/0x350
[124280.117338]  [] rest_init+0x77/0x80
[124280.117341]  [] start_kernel+0x448/0x469
[124280.117343]  [] ? early_idt_handler_array+0x120/0x120
[124280.117344]  [] x86_64_start_reservations+0x24/0x26
[124280.117346]  [] x86_64_start_kernel+0x14d/0x170
[124280.117347] ---[ end trace a17e9d5abd1ea1de ]---

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
NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-32-generic.
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
ArecordDevices:
  Liste der Hardware-Geräte (CAPTURE) 
 Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC269VC Analog [ALC269VC Analog]
   Sub-Geräte: 1/1
   Sub-Gerät #0: subdevice #0
AudioDevicesInUse:
 BEN.PID ZUGR.  BEFEHL
 /dev/snd/pcmC0D0p:   richter   20519 F...m pulseaudio
 /dev/snd/controlC0:  richter   20519 F pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xd361 irq 31'
   Mixer name   : 'Realtek ALC269VC'
   Components   : 'HDA:10ec0269,17aac034,00100202 
HDA:80862806,80860101,0010'
   Controls  : 30
   Simple ctrls  : 12
CurrentDesktop: Unity
Date: Sun Jan  8 15:03:36 2017
HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
InstallationDate: Installed on 2015-12-12 (393 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20221
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-32-generic N/A
 linux-backports-modules-4.8.0-32-generic  N/A
 linux-firmware1.161.1
SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (83 days ago)
dmi.bios.date: 07/12/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 

[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D

2017-01-08 Thread Aakash Roy
Mike - checking if you have found a workaround or any temporary fix for
this issue ? I have faced the same problem on an R410 with iDRAC running
trusty kernel.

Following are the logs from my server:

[3903494.645100] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
[3903499.760216] usb 5-2: device descriptor read/64, error -110
[3903499.984358] usb 5-2: device descriptor read/64, error -71
[3903500.200497] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
[3903500.320567] usb 5-2: device descriptor read/64, error -71
[3903500.544709] usb 5-2: device descriptor read/64, error -71
[3903500.760848] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
[3903501.169123] usb 5-2: device not accepting address 2, error -71
[3903501.281153] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
[3903501.689411] usb 5-2: device not accepting address 2, error -71
[3903501.689842] usb 5-2: USB disconnect, device number 2
[3903717.219659] INFO: task khubd:119 blocked for more than 120 seconds.
[3903717.220045]   Not tainted 3.13.0-100-generic #147-Ubuntu
[3903717.220441] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[3903717.220975] khubd   D 88012b293180 0   119  2 
0x
[3903717.220980]  880128f85c80 0046 880128ece000 
00013180
[3903717.220984]  880128f85fd8 00013180 880128ece000 
8801253da0e8
[3903717.220988]  8801253da0ec 880128ece000  
8801253da0f0
[3903717.220992] Call Trace:
[3903717.221002]  [] schedule_preempt_disabled+0x29/0x70
[3903717.221006]  [] __mutex_lock_slowpath+0x135/0x1b0
[3903717.221010]  [] mutex_lock+0x1f/0x2f
[3903717.221016]  [] usb_disconnect+0x64/0x200
[3903717.221019]  [] hub_port_connect_change+0xd3/0xb30
[3903717.221023]  [] ? hub_port_status+0xdd/0x120
[3903717.221026]  [] hub_events+0x4d4/0xa20
[3903717.221030]  [] hub_thread+0x35/0x150
[3903717.221034]  [] ? prepare_to_wait_event+0x100/0x100
[3903717.221037]  [] ? hub_events+0xa20/0xa20
[3903717.221041]  [] kthread+0xc9/0xe0
[3903717.221045]  [] ? kthread_create_on_node+0x1c0/0x1c0
[3903717.221050]  [] ret_from_fork+0x58/0x90
[3903717.221053]  [] ? kthread_create_on_node+0x1c0/0x1c0
[3903717.221064] INFO: task kworker/2:1:12543 blocked for more than 120 seconds.
[3903717.221495]   Not tainted 3.13.0-100-generic #147-Ubuntu
[3903717.221828] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[3903717.85] kworker/2:1 D 88012b253180 0 12543  2 
0x
[3903717.99] Workqueue: events hid_reset [usbhid]
[3903717.222301]  880036091850 0046 8800c4c4 
00013180
[3903717.222304]  880036091fd8 00013180 8800c4c4 
880036091998
[3903717.222308]  8800360919a0 7fff 8800c4c4 
8800c4c4
[3903717.222312] Call Trace:
[3903717.222315]  [] schedule+0x29/0x70
[3903717.222318]  [] schedule_timeout+0x279/0x310
[3903717.222323]  [] ? __enqueue_entity+0x78/0x80
[3903717.222327]  [] ? enqueue_entity+0x2ad/0xc00
[3903717.222331]  [] wait_for_completion+0xa6/0x150
[3903717.222336]  [] ? wake_up_state+0x20/0x20
...
...

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

Title:
  khubd/usbhid deadlock(?) creates processes in state D

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (Note that the attached logs are not a machine exhibiting the issue)

  I've observed this issue specifically on Dell's PowerEdge R410 with
  its DRAC. I manage quite a few other machines with DRACs and haven't
  seen this issue so it may be limited to the R410. I've seen cases of
  this both with the precise and trusty kernel.

  Basically, what happens is that things that read any info about the
  DRAC's usbhid device will block in an uninterruptible state. A quick
  way to do this is with "cat
  /sys/devices/pci:00/:00:1d.0/usb5/5-2/manufacturer". This
  means that commands like lspci will block as well. The thing is that
  it doesn't happen every time, but once it happens the first time all
  future reads on the device will block in state D too.

  This is also associated with the following from the kernel (first from a 
precise machine):
  [197852.595820] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197857.716899] usb 5-2: device descriptor read/64, error -71
  [197857.944966] usb 5-2: device descriptor read/64, error -71
  [197858.165020] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197858.285090] usb 5-2: device descriptor read/64, error -71
  [197858.513108] usb 5-2: device descriptor read/64, error -71
  [197858.733154] usb 5-2: reset full-speed USB device number 2 using uhci_hcd
  [197859.145214] usb 5-2: device not accepting address 2, error -71
  [197859.261234] usb 5-2: reset full-speed USB 

[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards

2017-01-08 Thread Tim Passingham
Earlier posts say this bug was fixed in linux 4.4.0-30.49.  My system
has been fine since then.

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

Title:
  Key 5 automatically pressed on some Logitech wireless keyboards

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  I have a K520 Logitech keyboard and sometimes something starts to keep 
pressing key 5.
  It mostly happens when I leave the computer alone for some time, but 
sometimes also just during regular usage.

  It seems that this is a Linux specific issue as no one is complaining
  about this issue under Windows, but a couple of people are complaining
  for different versions of Ubuntu.

  It is always 5 and WladyXX3740 claims on the Logitech forum that:
  "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably 
kernel related."

  Here is where most of the people are complaining:
  
https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639

  I discovered that this is related to my Logitech keyboard by running this 
command:
  xinput test-xi2 --root

  Here is the device list:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech K520   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Logitech M310/M310t id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=15   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]

  And some extract from the output when this happens:
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags:
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 12 (PropertyEvent)
   property: 308 'Synaptics Off'
   changed: modified
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: 

[Kernel-packages] [Bug 1512848] Re: Radeon VCE Init Error

2017-01-08 Thread Jean-Pierre van Riel
It's still happening to me on 16.04 (Xenial), fully up to date.

@madbiologist, thanks, good to know where the cause might be.

Still, having to rebuild a kernel with one commit reverted is a fairly
cumbersome work-around and painful given fairly frequent kernel
updates...

As far as I can see, no fixes have been worked on? 0 commits to
vce_v1_0.c (my graphics card is only VCE 1 capable) `CHIP_PITCAIRN`

https://github.com/torvalds/linux/commits/master/drivers/gpu/drm/radeon/vce_v1_0.c

https://github.com/torvalds/linux/commits/master/drivers/gpu/drm/radeon/radeon_vce.c

However, there might be a way to disable VCE (I need to look into it
more)

https://github.com/torvalds/linux/commit/fabb5935871db1f31fcd2684fd154e24de04d917
#diff-9bc1b4aaf15dd521a1991717e4e2a2e0

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

Title:
  Radeon VCE Init Error

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  Since upgrading to Ubuntu 15.10, I have encountered graphics
  performance issues, and have occasionally experienced lockups during
  boot.

   dmesg | grep -E 'drm|radeon'
  [2.164605] [drm] Initialized drm 1.1.0 20060810
  [2.192852] [drm] radeon kernel modesetting enabled.
  [2.201268] [drm] Memory usable by graphics device = 2048M
  [2.201274] fb: switching to inteldrmfb from EFI VGA
  [2.201394] [drm] Replacing VGA console driver
  [2.204234] radeon :01:00.0: enabling device ( -> 0003)
  [2.207919] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [2.207921] [drm] Driver supports precise vblank timestamp query.
  [2.242929] fbcon: inteldrmfb (fb0) is primary device
  [3.529125] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
has_drrs (expected 1, found 0)
  [3.529141] WARNING: CPU: 1 PID: 195 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:12700 
intel_modeset_check_state+0x5aa/0x870 [i915]()
  [3.529150] Modules linked in: hid_logitech_hidpp hid_logitech_dj usbhid 
hid rtsx_usb_sdmmc rtsx_usb amdkfd amd_iommu_v2 i915(+) radeon(+) i2c_algo_bit 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse r8169 
ahci drm libahci mii fjes wmi video
  [3.529201]  [] drm_atomic_commit+0x37/0x60 [drm]
  [3.529206]  [] drm_atomic_helper_set_config+0x1bf/0x420 
[drm_kms_helper]
  [3.529212]  [] drm_mode_set_config_internal+0x62/0x100 
[drm]
  [3.529215]  [] restore_fbdev_mode+0xb3/0x110 
[drm_kms_helper]
  [3.529219]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70 [drm_kms_helper]
  [3.529221]  [] drm_fb_helper_set_par+0x2d/0x50 
[drm_kms_helper]
  [3.529253]  [] drm_fb_helper_initial_config+0x250/0x3e0 
[drm_kms_helper]
  [3.535608] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.546293] [drm] Initialized i915 1.6.0 20150731 for :00:02.0 on 
minor 0
  [3.546469] [drm] initializing kernel modesetting (OLAND 0x1002:0x6600 
0x144D:0xC0E6).
  [3.546483] [drm] register mmio base: 0xF7E0
  [3.546484] [drm] register mmio size: 262144
  [3.574408] [drm] GPU not posted. posting now...
  [3.587216] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [3.587218] radeon :01:00.0: GTT: 2048M 0x4000 - 
0xBFFF
  [3.587220] [drm] Detected VRAM RAM=1024M, BAR=256M
  [3.587220] [drm] RAM width 128bits DDR
  [3.587314] [drm] radeon: 1024M of VRAM memory ready
  [3.587315] [drm] radeon: 2048M of GTT memory ready.
  [3.587322] [drm] Loading oland Microcode
  [3.587398] [drm] Internal thermal controller without fan control
  [3.587450] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e
  [3.593155] [drm] radeon: dpm initialized
  [3.594806] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
  [3.594811] [drm] GART: num cpu pages 524288, num gpu pages 524288
  [3.595617] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e
  [3.595620] [drm] enabling PCIE gen 3 link speeds, disable with 
radeon.pcie_gen2=0
  [4.815819] [drm] PCIE GART of 2048M enabled (table at 0x002E8000).
  [4.815912] radeon :01:00.0: WB enabled
  [4.815914] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x880416408c00
  [4.815916] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x4c04 and cpu addr 0x880416408c04
  [4.815917] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x4c08 and cpu addr 0x880416408c08
  [4.815918] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x880416408c0c
  [4.815919] radeon :01:00.0: fence driver on 

[Kernel-packages] [Bug 1580732] Re: wireless keyboard - repeating characters unattended

2017-01-08 Thread Bjørn Næss
*** This bug is a duplicate of bug 1579190 ***
https://bugs.launchpad.net/bugs/1579190

Very strange - the problem with "[[C^" disappeared over the night. Today it 
seems works fine. I didn't do any changes. 
I will update if the problem appears later.

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

Title:
  wireless keyboard - repeating characters unattended

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When doing nothing at all, the screen (eg an editor, mail message,
  terminal etc) will start displaying '5' rapidly across the screen.

  I am a recent ubuntu 16.04 user - a fresh install "Linux TimPassingham
  4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 x86_64
  x86_64 x86_64 GNU/Linux"

  I was previously on 14.04 and had no such issues.

  My keyboard is a Logitech wireless MK700/710.  There is nothing wrong
  with it in normal running, nor when using windows (dual-booted).

  I am not alone, and it is the same key (5) for others seeing this
  issue.  See https://askubuntu.com/questions/761522/ubuntu-16-04
  -repeats-keys-without-holding-down-any-key

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crusty 1927 F pulseaudio
   /dev/snd/controlC1:  crusty 1927 F pulseaudio
   /dev/snd/pcmC2D0c:   crusty 1927 F...m pulseaudio
   /dev/snd/controlC2:  crusty 1927 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May 11 19:41:39 2016
  HibernationDevice: RESUME=UUID=79194a4a-c084-466c-8b41-b5988820be2e
  InstallationDate: Installed on 2016-05-08 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ZOTAC ZBOX-ID92/ZBOX-IQ01
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=fcd7b99b-d3fb-4a80-b928-e0378d881a8a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B220P007
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID92/ZBOX-IQ01
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB220P007:bd05/21/2014:svnZOTAC:pnZBOX-ID92/ZBOX-IQ01:pvrXX:rvnZOTAC:rnZBOX-ID92/ZBOX-IQ01:rvrXX:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ZBOX-ID92/ZBOX-IQ01
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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


[Kernel-packages] [Bug 1653012] Re: RTL8821AE doesn't work after some minutes.

2017-01-08 Thread hotellina
You can see the difference between Windows and Linux while uploading the
same file.

Windows 10 on ASUS X555L https://www.youtube.com/watch?v=1KcRefy3yho  
Linux on  ASUS X555L https://www.youtube.com/watch?v=jFJh_qwc3qg  

While on Windows the upload is very fast on Linux takes ages. This time
on Linux didn't disconnect me from the server but I was just lucky.

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

Title:
  RTL8821AE doesn't work after some minutes.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop is an ASUS X555L and I have a wireless card RTL8821AE.
  After a few minutes it hangs and doesn't let me surf internet although it 
shows connected. I have a dual boot Windows 10 / Ubuntu and on Windows works 
seamlessly.

  ---
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1630 F pulseaudio
   /dev/snd/controlC0:  john   1630 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=30b021e6-b5af-4de8-af81-71108e2d8381
  InstallationDate: Installed on 2016-12-28 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IE:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=aa44a294-fde3-45eb-b84f-98b998f29eef ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.6
  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  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.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2017-01-08 Thread Josep Pujadas-Jubany
Please, copy/paste the output of the command:

uname -a

Like this others (than Mint flavor) can know which kernel version you're
using.

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

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

Status in linux package in Ubuntu:
  Won't Fix

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

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

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

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

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

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


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

2017-01-08 Thread Andrew
Hello.

I've tried Linix Mint 18, Ubuntu Mate 16.04 - the problem appeared right
after booting live image from USB stick. Ubuntu Mate 16.10 does not have
the issue. So I've installed 16.10.

The kernel from 16.10 does not fix Mint 18 and Ubuntu 16.04, so I think
it is not a kernel code regression.

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

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

Status in linux package in Ubuntu:
  Won't Fix

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

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

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

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

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

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