[Kernel-packages] [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit

2016-05-03 Thread Radha Mohan Chintakuntla
I think AMI UEFI has the aspeed vga driver but Cavium UEFI doesn't. so
this might be causing 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/1574814

Title:
  ThunderX: soft lockup in cursor_timer_handler() Edit

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via 
virtual media:

http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso

  During boot I observed the following lockup on the serial console:

  [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! 
[swapper/14:0]
  [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) 
usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) 
drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) 
ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
  [ 84.922749]
  [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic 
#37-Ubuntu
  [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
  [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: 
801f6c9e8000
  [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
  [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
  [ 84.922778] pc : [] lr : [] pstate: 
00400145
  [ 84.922781] sp : 801f6c9ebc20
  [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
  [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
  [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
  [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
  [ 84.922802] x21: 0100 x20: 8000f94398d8
  [ 84.922807] x19: 8000f9439800 x18: c76a5358
  [ 84.922811] x17: 97bbd2a8 x16: 802a5040
  [ 84.922816] x15: 3e4cf1e0 x14: 0008
  [ 84.922820] x13:  x12: 003d0900
  [ 84.922824] x11: 003d0900 x10: 8090f200
  [ 84.922829] x9 : 3d09 x8 : 000e
  [ 84.922833] x7 : 801f7b3c5008 x6 : 
  [ 84.922837] x5 :  x4 : 0001
  [ 84.922842] x3 :  x2 : 801f6c899e05
  [ 84.922846] x1 : 801f667d99e0 x0 : 
  [ 84.922850]
  [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.342677] random: nonblocking pool is initialized

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

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


[Kernel-packages] [Bug 1536841] Re: xenial can't access network printer 14.04.3 no problem

2016-05-03 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/1536841

Title:
  xenial can't access network printer 14.04.3 no problem

Status in linux package in Ubuntu:
  Expired

Bug description:
  There was an error during the CUPS operation: 'client-error-not-
  possible'.

  14.04.3 on another partition accesses network printer on XP just fine.

  With identical smb.conf xenial cannot access the printer.

  Xenial can access XP jpg images etc. so network connection to XP
  working fine.

  See attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-6-generic 4.3.0-6.17
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  Date: Thu Jan 21 18:41:32 2016
  InstallationDate: Installed on 2015-12-26 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-6-generic 
root=UUID=c8c33dea-5f04-4670-84f3-daf1d956e6b8 ro quiet splash vt.handoff=7
  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: 01/10/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT69AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.name: 6234A1U
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1543254] Re: Wifi disconnects and my wifi is missing from list so I cannot connect to it

2016-05-03 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/1543254

Title:
  Wifi disconnects and my wifi is missing from list so I cannot connect
  to it

Status in linux package in Ubuntu:
  Expired

Bug description:
  For a few times a day, my wifi disconnects when using 802.11n. If I
  try to connect to it manually, I cannot do that as it is missing from
  the list with nearby connections. I have discovered a way to connect
  by going to  Connect to hidden Wifi Connection, select the dropdown
  and chose from that list my home wifi network. It works. But of
  course, a few hours later, it will disconnect and I have to do this
  again. I should mention that my wifi is not a hidden one, never has
  been. See the attached screen recording.

  Router: TP-Link TL-WR842ND v1; firmware: DD-WRT v24-sp2 (12/22/14) std
  (SVN revision 25697), Linux 3.5.7.33 #17743 Mon Dec 22 04:32:38 CET
  2014 mips.

  WORKAROUND: Use 802.11g.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  florin 1578 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  8 21:04:27 2016
  HibernationDevice: RESUME=UUID=e6dd3a64-131e-4aee-8ed4-84e81029859e
  InstallationDate: Installed on 2016-01-30 (8 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 002: ID 13d3:5652 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic 
root=UUID=99542f8d-67cc-4ee6-bd91-596c9a4709ee ro persistent quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-27-generic N/A
   linux-backports-modules-4.2.0-27-generic  N/A
   linux-firmware1.149.3
  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: 10/08/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.20
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit

2016-05-03 Thread dann frazier
fyi, I've found that removing the ast kernel module from the di initrd
seems to avoid 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/1574814

Title:
  ThunderX: soft lockup in cursor_timer_handler() Edit

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via 
virtual media:

http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso

  During boot I observed the following lockup on the serial console:

  [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! 
[swapper/14:0]
  [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) 
usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) 
drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) 
ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
  [ 84.922749]
  [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic 
#37-Ubuntu
  [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
  [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: 
801f6c9e8000
  [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
  [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
  [ 84.922778] pc : [] lr : [] pstate: 
00400145
  [ 84.922781] sp : 801f6c9ebc20
  [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
  [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
  [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
  [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
  [ 84.922802] x21: 0100 x20: 8000f94398d8
  [ 84.922807] x19: 8000f9439800 x18: c76a5358
  [ 84.922811] x17: 97bbd2a8 x16: 802a5040
  [ 84.922816] x15: 3e4cf1e0 x14: 0008
  [ 84.922820] x13:  x12: 003d0900
  [ 84.922824] x11: 003d0900 x10: 8090f200
  [ 84.922829] x9 : 3d09 x8 : 000e
  [ 84.922833] x7 : 801f7b3c5008 x6 : 
  [ 84.922837] x5 :  x4 : 0001
  [ 84.922842] x3 :  x2 : 801f6c899e05
  [ 84.922846] x1 : 801f667d99e0 x0 : 
  [ 84.922850]
  [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.342677] random: nonblocking pool is initialized

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

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


[Kernel-packages] [Bug 1578022] [NEW] dmidecode fails to output smibios 3.0 info

2016-05-03 Thread Samantha Jian-Pielak
Public bug reported:

Ubuntu 16.04, dmidecode 3.0-2 can display smibios 2.8 but not smibios
3.0. Rhel 7.2 can display smibios 3.0 on the same system without a
problem.

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

** Attachment added: "dmi.png"
   https://bugs.launchpad.net/bugs/1578022/+attachment/4654941/+files/dmi.png

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

Title:
  dmidecode fails to output smibios 3.0 info

Status in dmidecode package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04, dmidecode 3.0-2 can display smibios 2.8 but not smibios
  3.0. Rhel 7.2 can display smibios 3.0 on the same system without a
  problem.

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

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


[Kernel-packages] [Bug 1577364] Re: Screen flickers after upgrade to 16.04 from 15.10 on Dell XPS13 9350

2016-05-03 Thread Brewster Malevich
May be duplicate of Bug #1554613 ?

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

Title:
  Screen flickers after upgrade to 16.04 from 15.10 on Dell XPS13  9350

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Screen flickers after upgrade to 16.04 from 15.10 on Dell XPS13  9350.

  Flickers frequently on mid-range brightness, better on high and low
  range brightness.

  Tried to turn off tlp but doesn't help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seanl  1895 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May  2 21:27:58 2016
  HibernationDevice: RESUME=UUID=8c16e7e0-1b67-4bf7-b502-25e5d6de6d81
  InstallationDate: Installed on 2015-12-16 (138 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 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=0d974029-002f-443f-b682-4209064663d0 ro acpi_sleep=nonvs quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (9 days ago)
  dmi.bios.date: 11/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.7
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.7:bd11/27/2015:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit

2016-05-03 Thread Radha Mohan Chintakuntla
I tried PXE based install (just booting till the installer does network
init) multiple times with Cavium UEFI and did not see this issue, but as
soon as I tried AMI UEFI first time the "NMI softlockup ..." appeared
after sometime while still in opening screen of "debian-installer".

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

Title:
  ThunderX: soft lockup in cursor_timer_handler() Edit

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via 
virtual media:

http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso

  During boot I observed the following lockup on the serial console:

  [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! 
[swapper/14:0]
  [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) 
usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) 
drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) 
ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
  [ 84.922749]
  [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic 
#37-Ubuntu
  [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
  [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: 
801f6c9e8000
  [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
  [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
  [ 84.922778] pc : [] lr : [] pstate: 
00400145
  [ 84.922781] sp : 801f6c9ebc20
  [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
  [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
  [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
  [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
  [ 84.922802] x21: 0100 x20: 8000f94398d8
  [ 84.922807] x19: 8000f9439800 x18: c76a5358
  [ 84.922811] x17: 97bbd2a8 x16: 802a5040
  [ 84.922816] x15: 3e4cf1e0 x14: 0008
  [ 84.922820] x13:  x12: 003d0900
  [ 84.922824] x11: 003d0900 x10: 8090f200
  [ 84.922829] x9 : 3d09 x8 : 000e
  [ 84.922833] x7 : 801f7b3c5008 x6 : 
  [ 84.922837] x5 :  x4 : 0001
  [ 84.922842] x3 :  x2 : 801f6c899e05
  [ 84.922846] x1 : 801f667d99e0 x0 : 
  [ 84.922850]
  [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.342677] random: nonblocking pool is initialized

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

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


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

2016-05-03 Thread Daniel
I have the same problem with an intel i7-6500U on the 4.4.0 from Apr
18th. The Kernel does not freeze when i plug the external display in
before booting.

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

Title:
  i915 Skylake - Ultra Dock external displays not detected after
  suspend/resume cycle

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1577957] Re: Intel 7265D wifi firmware crashes on a Lenovo x1 carbon (3rd generation)

2016-05-03 Thread mich...@hinespot.com
** Summary changed:

- Intel 7265D wifi firmware crashes on a Lenovo x1 carbon (3rd genearation)
+ Intel 7265D wifi firmware crashes on a Lenovo x1 carbon (3rd generation)

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

Title:
  Intel 7265D wifi firmware crashes on a Lenovo x1 carbon (3rd
  generation)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The stock firmware for this device /lib/firmware/iwlwifi-
  7265D-16.ucode is crashing.

  Downloading the latest firmware (/lib/firmware/iwlwifi-7265D-21.ucode)
  isn't supported by the existing iwlwifi driver, and so the driver
  likely needs to be upgraded (or downgraded as well
  (https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/backport-
  iwlwifi.git/?h=release/LinuxCore18).

  I can also confirm that wifi *did* work successfully on 15.10 before
  upgrading to 16.04, although the kernel module required frequent
  restarts due to this bug:
  https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1570595

  
  A detailed message about the firmware crash is located in the attachment from 
dmesg output.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   mrhines2419 F...m pulseaudio
   /dev/snd/controlC1:  mrhines2419 F pulseaudio
   /dev/snd/controlC0:  mrhines2419 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  3 16:50:50 2016
  HibernationDevice: RESUME=UUID=1ac1f16c-161d-45c7-83b9-cecbbfdeee42
  InstallationDate: Installed on 2016-01-05 (119 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20BSCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (12 days ago)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1570595] Re: Intel 7265 wifi drops and won't reconnect

2016-05-03 Thread mich...@hinespot.com
I had exactly the same problem too on 15.10. Restarting the iwlwifi
kernel module fixed it, but that's not ideal.

My machine is a thinkpad x1 carbon (3rd generation) and device is a
Intel 7265D wifi device.

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

Title:
  Intel 7265 wifi drops and won't reconnect

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

Bug description:
  My my T450 has Intel 7265 wifi. Sometimes it just seems to disappear
  from network manager. I end up having to rmmod the iwlwifi module and
  re-add it to make it see wireless access points again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alan   2224 F pulseaudio
   /dev/snd/controlC0:  alan   2224 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Apr 14 21:43:35 2016
  HibernationDevice: RESUME=UUID=f39f9990-20e6-4bbf-b8bf-46316b7b6d42
  InstallationDate: Installed on 2016-04-08 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160407)
  MachineType: LENOVO 20BV001BUK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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


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

2016-05-03 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/1577957

Title:
  Intel 7265D wifi firmware crashes on a Lenovo x1 carbon (3rd
  generation)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The stock firmware for this device /lib/firmware/iwlwifi-
  7265D-16.ucode is crashing.

  Downloading the latest firmware (/lib/firmware/iwlwifi-7265D-21.ucode)
  isn't supported by the existing iwlwifi driver, and so the driver
  likely needs to be upgraded (or downgraded as well
  (https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/backport-
  iwlwifi.git/?h=release/LinuxCore18).

  I can also confirm that wifi *did* work successfully on 15.10 before
  upgrading to 16.04, although the kernel module required frequent
  restarts due to this bug:
  https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1570595

  
  A detailed message about the firmware crash is located in the attachment from 
dmesg output.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   mrhines2419 F...m pulseaudio
   /dev/snd/controlC1:  mrhines2419 F pulseaudio
   /dev/snd/controlC0:  mrhines2419 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  3 16:50:50 2016
  HibernationDevice: RESUME=UUID=1ac1f16c-161d-45c7-83b9-cecbbfdeee42
  InstallationDate: Installed on 2016-01-05 (119 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20BSCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (12 days ago)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1577792] Re: video not working after resume

2016-05-03 Thread Joseph Salisbury
Do you have some time to test some kernels?  We can bisect down to the
commit that introduced this once we know the last good 4.4 kernel and
the first bad one.

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

** Tags added: kernel-da-key

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

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

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

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

Title:
  video not working after resume

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

Bug description:
  I suspended my x250.  Then plugged it in (overnight).  Then unplugged
  it.  Then opened it.  It resumed, but video did not work.  I closed
  the lid and opened it, a few times.  No dice.  Then, I pressed the
  power button, and the video came back on.  I was sitting next to
  Leann, Chris, and Brad here at the CDO Sprint.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kirkland   4510 F pulseaudio
   /dev/snd/pcmC1D0p:   kirkland   4510 F...m pulseaudio
   /dev/snd/controlC1:  kirkland   4510 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May  3 08:18:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-15 (354 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CMCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=a4d6a56a-7b1b-4a7c-8420-f2b8e6d15c37 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  UpgradeStatus: Upgraded to xenial on 2016-01-04 (119 days ago)
  dmi.bios.date: 03/05/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET30W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkpadX250:rvnLENOVO:rn20CMCTO1WW:rvr0B98417PRO:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CMCTO1WW
  dmi.product.version: Thinkpad X250
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1577957] [NEW] Intel 7265D wifi firmware crashes on a Lenovo x1 carbon (3rd generation)

2016-05-03 Thread mich...@hinespot.com
Public bug reported:

The stock firmware for this device /lib/firmware/iwlwifi-7265D-16.ucode
is crashing.

Downloading the latest firmware (/lib/firmware/iwlwifi-7265D-21.ucode)
isn't supported by the existing iwlwifi driver, and so the driver likely
needs to be upgraded (or downgraded as well
(https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/backport-
iwlwifi.git/?h=release/LinuxCore18).

I can also confirm that wifi *did* work successfully on 15.10 before
upgrading to 16.04, although the kernel module required frequent
restarts due to this bug:
https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1570595


A detailed message about the firmware crash is located in the attachment from 
dmesg output.

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   mrhines2419 F...m pulseaudio
 /dev/snd/controlC1:  mrhines2419 F pulseaudio
 /dev/snd/controlC0:  mrhines2419 F pulseaudio
CurrentDesktop: KDE
Date: Tue May  3 16:50:50 2016
HibernationDevice: RESUME=UUID=1ac1f16c-161d-45c7-83b9-cecbbfdeee42
InstallationDate: Installed on 2016-01-05 (119 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20BSCTO1WW
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic  N/A
 linux-firmware1.157
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-21 (12 days ago)
dmi.bios.date: 08/13/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N14ET32W (1.10 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BSCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BSCTO1WW
dmi.product.version: ThinkPad X1 Carbon 3rd
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug xenial

** Attachment added: "Dmesg showing firmware crash."
   https://bugs.launchpad.net/bugs/1577957/+attachment/4654826/+files/dmesg.txt

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

Title:
  Intel 7265D wifi firmware crashes on a Lenovo x1 carbon (3rd
  generation)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The stock firmware for this device /lib/firmware/iwlwifi-
  7265D-16.ucode is crashing.

  Downloading the latest firmware (/lib/firmware/iwlwifi-7265D-21.ucode)
  isn't supported by the existing iwlwifi driver, and so the driver
  likely needs to be upgraded (or downgraded as well
  (https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/backport-
  iwlwifi.git/?h=release/LinuxCore18).

  I can also confirm that wifi *did* work successfully on 15.10 before
  upgrading to 16.04, although the kernel module required frequent
  restarts due to this bug:
  https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1570595

  
  A detailed message about the firmware crash is located in the attachment from 
dmesg output.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   mrhines2419 F...m pulseaudio
   /dev/snd/controlC1:  mrhines2419 F pulseaudio
   /dev/snd/controlC0:  mrhines2419 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  3 16:50:50 2016
  HibernationDevice: RESUME=UUID=1ac1f16c-161d-45c7-83b9-cecbbfdeee42
  InstallationDate: Installed on 2016-01-05 (119 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20BSCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports

[Kernel-packages] [Bug 1575334] Re: Docking thinkpad laptop causes a complete system freeze

2016-05-03 Thread Joseph Salisbury
Since this bug does not exist with any of the upstream kernels, it may
be due to a SAUCE patch.  Can you test the following Ubuntu kernels:

4.3.0-0.9:  https://launchpad.net/ubuntu/+source/linux/4.3.0-0.9/+build/8360668
4.4.0-1.15: https://launchpad.net/ubuntu/+source/linux/4.4.0-1.15/+build/8880824

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

Title:
  Docking thinkpad laptop causes a complete system freeze

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Since upgrading to Xenial, about 80% of the time when I dock my
  thinkpad laptop I get a complete system freeze. The symptoms of the
  freeze are:

   * The two external monitors connected to the dock seem to be in a
  half-configured state - they're powered on, and display some graphics
  from my desktop, but do not yet show the correct contents.

   * I can't get to a console with Ctrl+Alt+F1.

   * I can't kill X with Ctrl+Alt+Backspace

   * I can't get the mouse cursor to appear or move, either with the
  trackpad or the external mouse.

   * Undocking the laptop doesn't help.

  The only thing I *can* do at this point is to hold down the power
  button.

  I seem to recall similar issues in the past (perhaps in Vivid?), where
  the fix ended up being in the graphics driver.

  The laptop is a T540p. The docking station is an "ultra dock pro" -
  not a USB dock, but rather one of those ones where the laoptop clicks
  into a base.

  This bug makes the docking station rather useless, and makes me sad :(

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  thomi  3196 F pulseaudio
   /dev/snd/controlC0:  thomi  3196 F pulseaudio
   /dev/snd/controlC1:  thomi  3196 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 27 07:35:58 2016
  HibernationDevice: RESUME=UUID=d27c9b15-955a-4bff-b4a7-e6116a8b30bb
  InstallationDate: Installed on 2015-10-12 (197 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20BECTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (5 days ago)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET72WW (2.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMET72WW(2.20):bd09/01/2015:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20BECTO1WW
  dmi.product.version: ThinkPad T540p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1574072] Re: Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after 4.4.0.10

2016-05-03 Thread Trueman
It is impossible to create log right after problem reproducing so as
laptop is totally freezing. So attached logs are got after system start
with kernel 4.4.0-21.

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

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


[Kernel-packages] [Bug 1574072] PulseList.txt

2016-05-03 Thread Trueman
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1574072/+attachment/4654777/+files/PulseList.txt

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


[Kernel-packages] [Bug 1484159] Re: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] is not supported

2016-05-03 Thread Miles Krell
** Description changed:

  This card remains unsupported out-of-the-box by the ath10k_pci kernel
  module. At this point, it looks like kvalo's ath10k-firmware repo just
  needs to be pulled in.
  
  ---
  
  HOW TO GET THIS CARD TO WORK:
  
  I don't actually have this card, but AndyP was able to get this card to
  work by following my instructions, so I've written them here in a
  clearer format.
  
- 1) Support for this card is not present in kernel 4.2.  However, it was
- added at some point between then and kernel 4.4.  See
+ 1) Use a kernel that supports this card
+ 
+ Support for this card is not present in kernel 4.2.  However, it was
+ added at some point between then and kernel 4.4.  If you're running
+ Ubuntu 16.04 LTS or above, your kernel is fine; skip to the next step.
+ If you're running Ubuntu 15.10 or below, see
  https://wiki.ubuntu.com/Kernel/MainlineBuilds for info on installing a
- newer kernel.  Kernel 4.5 is suggested.
+ newer kernel. Alternatively, you can use backports. This is a lot more
+ work, but if you really need to keep using an older kernel for some
+ reason, there are some guides to installing backports in the comments
+ below.
  
  2) Get the latest firmware from https://github.com/kvalo/ath10k-
  firmware/archive/master.zip
  
- 3) Unzip this file, and copy the contents of ath10k-firmware-master to
- /lib/firmware/ath10k.
+  wget https://github.com/kvalo/ath10k-firmware/archive/master.zip
+ 
+ 3) Unzip the downloaded file. Inside the ath10k-firmware-master folder
+ is a folder named QCA9377. Copy the QCA9377 folder to
+ /lib/firmware/ath10k:
+ 
+ unzip master.zip
+ sudo cp -r ath10k-firmware-master/QCA9377/ /lib/firmware/ath10k/
  
  4) Run the following commands to rename the necessary firmware file:
+ 
  cd /lib/firmware/ath10k/QCA9377/hw1.0/
  sudo mv firmware-5.bin_WLAN.TF.1.0-00267-1 firmware-5.bin
  
  5) Reboot your computer. Run "lshw -C network" to see if your card is
- recognized.
+ recognized. You can delete the files you downloaded earlier:
+ 
+ cd ~
+ rm master.zip
+ rm -r ath10k-firmware-master/
  
  Please tell me if these instructions are working for you.
  
  The original bug description follows.
  ---
  
  Hi,
  Qualcomm Atheros Device [168c:0042] (rev 30) is not supported by linux 
kernal. Please add support.
  
  Thanks
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-61-generic 3.13.0-61.100
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic i686
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu14   1658 F pulseaudio
   /dev/snd/controlC1:  ubuntu14   1658 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Aug 12 20:31:24 2015
  HibernationDevice: RESUME=UUID=0483444a-0d9a-4215-b36b-4aee75fd9ec0
  InstallationDate: Installed on 2015-08-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  IwConfig:
   lono wireless extensions.
  
   eth0  no wireless extensions.
  MachineType: Acer Aspire E5-573
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic 
root=UUID=72a8a100-d5ec-4e9d-8bc5-45695001a29c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-61-generic N/A
   linux-backports-modules-3.13.0-61-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd04/20/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

Title:
  Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042]
  is not supported

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  This card remains unsupported out-of-the-box by the ath10k_pci kernel
  module. At this point, it looks like kvalo's ath10k-firmware repo just
  needs to be pulled in.

  -

[Kernel-packages] [Bug 1574072] RfKill.txt

2016-05-03 Thread Trueman
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1574072/+attachment/4654778/+files/RfKill.txt

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


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

2016-05-03 Thread Trueman
apport information

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

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


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

2016-05-03 Thread Trueman
apport information

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

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


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

2016-05-03 Thread Trueman
apport information

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

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


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

2016-05-03 Thread Trueman
apport information

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

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


[Kernel-packages] [Bug 1574072] IwConfig.txt

2016-05-03 Thread Trueman
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1574072/+attachment/4654770/+files/IwConfig.txt

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


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

2016-05-03 Thread Trueman
apport information

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

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


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

2016-05-03 Thread Trueman
apport information

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

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


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

2016-05-03 Thread Trueman
apport information

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

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


[Kernel-packages] [Bug 1574072] Dependencies.txt

2016-05-03 Thread Trueman
apport information

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

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


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

2016-05-03 Thread Trueman
apport information

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

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


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

2016-05-03 Thread Trueman
apport information

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

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/06/2015
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.20
  dmi.board.name: FJNBB3D
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555/G
  dmi.sys.vendor: FUJITSU

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

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


[Kernel-packages] [Bug 1574072] Re: Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after 4.4.0.10

2016-05-03 Thread Trueman
apport information

** Tags added: apport-collected xenial

** Description changed:

  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  trueman1829 F pulseaudio
+  /dev/snd/controlC0:  trueman1829 F pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 16.04
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
+ InstallationDate: Installed on 2016-03-03 (61 days ago)
+ InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
+  Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
+  Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: FUJITSU LIFEBOOK A555/G
+ Package: xserver-xorg-video-amdgpu 1.1.0-1
+ PackageArchitecture: amd64
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-21-generic N/A
+  linux-backports-modules-4.4.0-21-generic  N/A
+  linux-firmware1.157
+ Tags:  xenial xenial
+ Uname: Linux 4.4.0-21-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
+ _MarkForUpload: True
+ dmi.bios.date: 10/06/2015
+ dmi.bios.vendor: FUJITSU // Insyde Software Corp.
+ dmi.bios.version: 1.20
+ dmi.board.name: FJNBB3D
+ dmi.board.vendor: FUJITSU
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: FUJITSU
+ dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.20:bd10/06/2015:svnFUJITSU:pnLIFEBOOKA555/G:pvr:rvnFUJITSU:rnFJNBB3D:rvr:cvnFUJITSU:ct10:cvr:
+ dmi.product.name: LIFEBOOK A555/G
+ dmi.sys.vendor: FUJITSU

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1574072/+attachment/4654766/+files/AlsaInfo.txt

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

Title:
  Ubuntu Mate 16.04 freezes on resume after sleep with any kernel after
  4.4.0.10

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've installed 16.04 beta several monthes ago on Fujitsu A555 laptop (the one 
with AMD Radeon R7 M260 graphic).
  Everything goes fine till kernel updated to 4.4.0.11. Since 4.4.0.11 kernel - 
if put laptop into sleep and then resume - laptop either freezes or will sure 
freeze on next resume after sleep. This happens with any kernel in range 
4.4.0.11 - 4.4.0.21. I'm forced to stay on kernel 4.4.0.10 to use ubuntu.
  Note: the issue started after force removing FGLRX by upcomming update.
  Please let me know if any of logs or outputs will be helpful - I'll attache 
them.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trueman1829 F pulseaudio
   /dev/snd/controlC0:  trueman1829 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cb8dafc9-72a7-47b1-ba4d-cf27ddc33fe2
  InstallationDate: Installed on 2016-03-03 (61 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c526 Logitech, Inc. Nano Receiver
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b3b4 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555/G
  Package: xserver-xorg-video-amdgpu 1.1.0-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d6211aca-675e-4ba4-b8e6-4b094a73b60a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-

[Kernel-packages] [Bug 1549354] Re: After upgrading to 4.2.0.30 Elantech touchpad not detected

2016-05-03 Thread Thomas Zell
I tested the new kernel 4.2.0-35 and it works.

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

Title:
  After upgrading to 4.2.0.30 Elantech touchpad not detected

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

Bug description:
  Elan Touchpad not listed as "Elan Touchpad" after "xinput list" or "cat 
/proc/bus/input/devices"
   . Not detected properly? For sure it does not work.
  External mouse working well. 
  Downgrading to 4.2.0-27-generic kernel solves problem(touchpad works). 
  My computer model is Toshiba Chromebook 2 with Gnome ubuntu 15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-30-generic 4.2.0-30.35
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  siulkilulki909 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Feb 24 16:55:47 2016
  InstallationDate: Installed on 2015-12-06 (80 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 04f2:b48b Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 1ea7:0011  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Swanky
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=20463b36-edda-428c-a236-f715f1d7bb85 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/22/2014:svnGOOGLE:pnSwanky:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Swanky
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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


[Kernel-packages] [Bug 1577898] Re: thunderbolt hotplug is broken

2016-05-03 Thread Mario Limonciello
There aren't logs for this.  it's  a request to backport a patch.

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

Title:
  thunderbolt hotplug is broken

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  Thunderbolt hotplug is broken on type-c ports.  Redhat already
  submitted a patch for this that was accepted into upstream ACPICA, but
  it needs to be backported into Ubuntu's kernel.

  I've verified that the patch works properly using a type-C USB
  Ethernet dongle as well as hot-plugging a Dell TB15 dock.

  http://www.spinics.net/lists/linux-acpi/msg65578.html

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

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


[Kernel-packages] [Bug 1577905] Re: Dell TB15 audio is distorted

2016-05-03 Thread Mario Limonciello
There aren't logs for this.  it's  a request to backport a patch.

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

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

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

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

Title:
  Dell  TB15 audio is distorted

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  On the Dell TB15 and Dell WD15 docks, analogue audio output is
  distorted.  This is because of a missing driver quirk on docks.

  It has been fixed upstream here.
  
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

  Please backport it into Ubuntu.

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

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


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

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

apport-collect 1577905

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

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

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

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

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

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

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

Title:
  Dell  TB15 audio is distorted

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

Bug description:
  On the Dell TB15 and Dell WD15 docks, analogue audio output is
  distorted.  This is because of a missing driver quirk on docks.

  It has been fixed upstream here.
  
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

  Please backport it into Ubuntu.

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

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


[Kernel-packages] [Bug 1574362] Re: autoreconstruct: need to also generate extend-diff-ignore options for links

2016-05-03 Thread Kamal Mostafa
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  autoreconstruct: need to also generate extend-diff-ignore options for
  links

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  When autoreconstruct detects links and adds them to the reconstruction
  list, it also needs to add them to the debian/source/options list as
  extend-diff-ignore options.

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

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


[Kernel-packages] [Bug 1577898] Re: thunderbolt hotplug is broken

2016-05-03 Thread Mario Limonciello
** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => Confirmed

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

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

** Changed in: linux (Ubuntu)
   Status: Won't Fix => 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/1577898

Title:
  thunderbolt hotplug is broken

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  Thunderbolt hotplug is broken on type-c ports.  Redhat already
  submitted a patch for this that was accepted into upstream ACPICA, but
  it needs to be backported into Ubuntu's kernel.

  I've verified that the patch works properly using a type-C USB
  Ethernet dongle as well as hot-plugging a Dell TB15 dock.

  http://www.spinics.net/lists/linux-acpi/msg65578.html

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

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


[Kernel-packages] [Bug 1577905] [NEW] Dell TB15 audio is distorted

2016-05-03 Thread Mario Limonciello
Public bug reported:

On the Dell TB15 and Dell WD15 docks, analogue audio output is
distorted.  This is because of a missing driver quirk on docks.

It has been fixed upstream here.
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

Please backport it into Ubuntu.

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

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

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


** Tags: bot-stop-nagging

** Tags added: bot-stop-nagging

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

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

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

Title:
  Dell  TB15 audio is distorted

Status in linux package in Ubuntu:
  New
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New

Bug description:
  On the Dell TB15 and Dell WD15 docks, analogue audio output is
  distorted.  This is because of a missing driver quirk on docks.

  It has been fixed upstream here.
  
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

  Please backport it into Ubuntu.

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

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


[Kernel-packages] [Bug 1448566] Re: Ubuntu 15.04 - Macbook Pro Early 2015 (12, 1) Bluetooth disabled

2016-05-03 Thread Jean-Frédéric
Posting this in case it would help someone else: I had the same issue
with 15.10 (with kernel 4.2). I upgraded today to 16.04 (with kernel
4.4.0) and the buletooth is working like a charm.

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

Title:
  Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) Bluetooth disabled

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of 15.04 on a Macbook Pro 12,1.

  I get no Bluetooth icon in the status bar, and in System Settings >
  Bluetooth, everything is greyed out (i.e., can't turn it on).

  
  $lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; rfkill list all; 
lsmod | grep bluetooth; hciconfig -a; uname -a

  Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
  Bus 001 Device 004: ID 05ac:8290 Apple, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [ 32.369395] usb 1-3: Product: Bluetooth USB Host Controller
  [ 32.435743] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:05AC:8290.0006/input/input7
  [ 32.490662] hid-generic 0003:05AC:8290.0006: input,hidraw5: USB HID v1.11 
Keyboard [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input0
  [ 32.490750] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:05AC:8290.0007/input/input8
  [ 32.490995] hid-generic 0003:05AC:8290.0007: input,hidraw6: USB HID v1.11 
Mouse [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input1
  [ 34.866186] Bluetooth: Core ver 2.20
  [ 34.866205] Bluetooth: HCI device and connection manager initialized
  [ 34.866751] Bluetooth: HCI socket layer initialized
  [ 34.866754] Bluetooth: L2CAP socket layer initialized
  [ 34.866759] Bluetooth: SCO socket layer initialized
  [ 0.158493] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
  [ 0.168342] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain  [bus 
00-9b] only partially covers this bridge
  [ 35.003383] brcmfmac :03:00.0: Direct firmware load for 
brcm/brcmfmac43602-pcie.txt failed with error -2
  [ 35.290656] brcmf_c_preinit_dcmds: Firmware version = wl0: Mar 13 2015 
08:11:08 version 7.35.177.36 (r540934) FWID 01-e4dc15b
  0: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  bluetooth 491520 1 btusb
  Linux hxn-laptop-linux 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

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

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


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

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

apport-collect 1577898

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

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

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

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

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

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

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

Title:
  thunderbolt hotplug is broken

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

Bug description:
  Thunderbolt hotplug is broken on type-c ports.  Redhat already
  submitted a patch for this that was accepted into upstream ACPICA, but
  it needs to be backported into Ubuntu's kernel.

  I've verified that the patch works properly using a type-C USB
  Ethernet dongle as well as hot-plugging a Dell TB15 dock.

  http://www.spinics.net/lists/linux-acpi/msg65578.html

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

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


[Kernel-packages] [Bug 1577898] [NEW] thunderbolt hotplug is broken

2016-05-03 Thread Mario Limonciello
Public bug reported:

Thunderbolt hotplug is broken on type-c ports.  Redhat already submitted
a patch for this that was accepted into upstream ACPICA, but it needs to
be backported into Ubuntu's kernel.

I've verified that the patch works properly using a type-C USB Ethernet
dongle as well as hot-plugging a Dell TB15 dock.

http://www.spinics.net/lists/linux-acpi/msg65578.html

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

** Affects: linux (Ubuntu Trusty)
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: Incomplete


** Tags: bot-stop-nagging

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

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

** Tags added: bot-stop-nagging

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

Title:
  thunderbolt hotplug is broken

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

Bug description:
  Thunderbolt hotplug is broken on type-c ports.  Redhat already
  submitted a patch for this that was accepted into upstream ACPICA, but
  it needs to be backported into Ubuntu's kernel.

  I've verified that the patch works properly using a type-C USB
  Ethernet dongle as well as hot-plugging a Dell TB15 dock.

  http://www.spinics.net/lists/linux-acpi/msg65578.html

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

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


[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

2016-05-03 Thread faulpeltz
I did not explicitly test for that, but on our production server the issue went 
away completely
But we can definitely try that, 48 hours of I/O torture should rule out any 
non-VSS related 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/1470250

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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


[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

2016-05-03 Thread Frederik Bosch
@alexng-v I only had this while doing backups. Also, in the initial post
on MS Technet refers to it as a backup problem:
https://social.technet.microsoft.com/Forums/windowsserver/en-US
/8807f61c-565e-45bc-abc4-af09abf59de2/ubuntu-14042-lts-generation-2
-scsi-errors-on-vss-based-backups. We are now running HyperV with linux
VMs for over a year (in production) and we only see it during backups.

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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


[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

2016-05-03 Thread Alex Ng
Don't think this has been asked before, but has anyone had a repro when
backups were turned off? Or does this only happen when backups are
enabled?

I'm verifying this on my own as well, but if this happens regardless of
whether backup is enabled/disabled; then it'll help us narrow down the
cause further to either a storage issue (more likely) or a VSS backup
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/1470250

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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


[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash

2016-05-03 Thread Grzegorz Bartman
I have some workaround (distable/enable wl module when suspend)

- check this 
http://askubuntu.com/questions/620494/ubuntu-15-04-suspend-doesnt-run-pm-suspend
 (needed for 15.04 or higher)
- in /etc/pm/sleep.d create file with some name (for example 01_wifi_wl) with 
content:

=
#!/bin/bash

case "$1" in
suspend)
modprobe -r wl
;;
resume) 
modprobe wl
;;
*)
;;
esac
=

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

Title:
  14e4:4365 bcmwl-kernel source: fix for null pointer crash

Status in Dell Sputnik:
  Confirmed
Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Precise:
  Fix Committed
Status in bcmwl source package in Trusty:
  Fix Committed
Status in bcmwl source package in Vivid:
  Fix Committed
Status in bcmwl source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * bcmwl does not compile on new kernels (or HWE kernels)
   * bcmwl suffers from null reference bug 

  [Test Case]

   * public PPA provided to community and feedback
   * based on patch available to other distros
   * comment #42

  [Regression Potential]

   * for changes on kernel support it may not compile (tested with 3.2, 3.13, 
3.18 and 4.2)
   * for the null reference change -> proved to fix problem for community based 
on feedback

  [Other Info]

  Original bug description:

  The bcmwl package as of now misses one patch for a bug that occurs
  with BCM43142 and possibly other broadcom chipsets that will look like
  random disconnects, poor wifi signal and kernel warnings, See also
  #1379524.

  Adding the patch is a fairly simple process:

  * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches
  * add the following line to  /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf
  PATCH[7]="0014-null-pointer-crash.patch"
  * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom 
/usr/share/bcmwl x86_64 $(uname -r)

  This has fixed the issue for me. Edit: I just wanted to add that I did
  not write the patch; I merely downloaded it from a paste that was
  linked from the respective AUR package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: 
usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf]
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Jan 29 13:15:17 2015
  InstallationDate: Installed on 2015-01-26 (3 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions

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


[Kernel-packages] [Bug 1553694] Re: Lenovo Y700-17ISK: Bluetooth issues

2016-05-03 Thread Nathan Grennan
I am experiencing the same issue my Lenovo P50. It doesn't work most of
the time at boot.

workaround:
rmmod btusb ; modprobe btusb

kernel messages when it fails:
[8.523061] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[8.525271] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[8.532355] Bluetooth: hci0: Failed to send firmware data (-38)
[   10.608812] Bluetooth: hci0: Reading Intel version information failed (-110)
[   10.612778] Bluetooth: hci0 command tx timeout

kernel messages post reload of the btusb module:
[  712.576916] Bluetooth: hci0: Firmware revision 0.0 build 90 week 25 2015
[  767.110199] Bluetooth: hci0 urb 88073c4c0540 failed to resubmit (2)

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

Title:
  Lenovo Y700-17ISK: Bluetooth issues

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing and updating Xenial, dmesg notes:
  [2.253211] Bluetooth: hci0: Failed to send firmware data (-38)
  [4.250058] Bluetooth: hci0 command 0xfc05 tx timeout
  [9.135505] Bluetooth: hci0: Reading Intel version information failed (-19)
  [   10.926411] Bluetooth: hci0: Setting Intel event mask failed (-16)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:31:12 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1568039] Re: Kernel crashes consistently when using Eclipse references search

2016-05-03 Thread Peter Rimshnick
I no longer actively use the machine where I was seeing this issue, but
I can continue to investigate if there'd be a public benefit. Otherwise,
this can be closed.

Thanks,
Pete

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

Title:
  Kernel crashes consistently when using Eclipse references search

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since downloading new updates and restarting my computer this morning,
  my system crashes consistently when I do a Search->References
  operation in Eclipse. I'm using Eclipse Luna (4.4.2), buildid:
  20150219-0600 if anyone wants to try to reproduce.

  I've attached a file with a screenshot of the error information.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  primshnick   2527 F pulseaudio
   /dev/snd/controlC1:  primshnick   2527 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=80be1e16-0c37-4cef-9730-18ceec4e1d5b
  InstallationDate: Installed on 2015-04-16 (358 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. XPS 8700
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-69-generic 
root=UUID=d587ed3c-8be4-4d41-9838-c68252482637 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-69.89~14.04.1-generic 3.16.7-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-69-generic N/A
   linux-backports-modules-3.16.0-69-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.16.0-69-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0KWVT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd03/25/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8700
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

2016-05-03 Thread Tim Gardner
Mike - Wily was the first release to support ppc64el -
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-wily/linux-
image-4.2.0-040200-generic_4.2.0-040200.201510260713_ppc64el.deb

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

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

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


[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell

2016-05-03 Thread Kamal Mostafa
** Changed in: linux (Ubuntu)
   Status: Confirmed => In Progress

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

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

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

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

Title:
  OOPS on wily+ for Haswell-ULT and Broadwell

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  New
Status in linux source package in Wily:
  New
Status in linux source package in Xenial:
  New

Bug description:
  After upgrading to the wily 4.2 kernel, we see early OOPSes similar to
  the following on Haswell-ULT and Broadwell processors:

  [ cut here ]
  WARNING: CPU: 1 PID: 1 at 
/build/linux-lts-wily-MVxxD8/linux-lts-wily-4.2.0/arch/x86/mm/ioremap.c:198 
__ioremap_caller+0x2a2/0x360()
  Info: mapping multiple BARs. Your kernel is fine.
  Modules linked in:
  CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.2.0-34-generic #39~14.04.1-Ubuntu
  Hardware name: Hewlett-Packard HP EliteBook Folio 1040 G1/213E, BIOS L83 Ver. 
01.07 03/28/2014
   81a91c80 88023522bad8 817b5fed 0001
   88023522bb28 88023522bb18 8107799a c9cbe000
   c9cb8000 c9cb8000 6000 880230297040
  Call Trace:
   [] dump_stack+0x45/0x57
   [] warn_slowpath_common+0x8a/0xc0
   [] warn_slowpath_fmt+0x46/0x50
   [] __ioremap_caller+0x2a2/0x360
   [] ioremap_nocache+0x17/0x20
   [] snb_uncore_imc_init_box+0x65/0x90
   [] uncore_pci_probe+0xd5/0x1c0
   [] local_pci_probe+0x45/0xa0
   [] ? pci_match_device+0xf4/0x120
   [] pci_device_probe+0xca/0x110
   [] driver_probe_device+0x213/0x460
   [] __driver_attach+0x90/0xa0
   [] ? driver_probe_device+0x460/0x460
   [] bus_for_each_dev+0x5d/0x90
   [] driver_attach+0x1e/0x20
   [] bus_add_driver+0x1d0/0x290
   [] ? uncore_cpu_setup+0x12/0x12
   [] driver_register+0x60/0xe0
   [] __pci_register_driver+0x4c/0x50
   [] intel_uncore_init+0xe6/0x2fc
   [] ? uncore_cpu_setup+0x12/0x12
   [] do_one_initcall+0xcd/0x1f0
   [] ? parse_args+0x120/0x470
   [] ? __wake_up+0x48/0x60
   [] kernel_init_freeable+0x199/0x226
   [] ? initcall_blacklist+0xc0/0xc0
   [] ? rest_init+0x80/0x80
   [] kernel_init+0xe/0xe0
   [] ret_from_fork+0x3f/0x70
   [] ? rest_init+0x80/0x80
  ---[ end trace 5f5beae5b9d2dc45 ]---

  the issue is fixed in upstream kernels, via two patches:

  https://lkml.org/lkml/2015/12/11/165
  http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html

  each is a one-liner against the mch_quirk_devices[] structure.

  [nlb-glaptop](0) $ cat /proc/version_signature 
  Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  [nlb-glaptop](0) $ 

  [nlb-glaptop](0) $ lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  [nlb-glaptop](0) $ 

  [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily
  linux-generic-lts-wily:
Installed: 4.2.0.35.28
Candidate: 4.2.0.35.28
Version table:
   *** 4.2.0.35.28 0
  600 https://rapture-prod.corp.google.com/ 
goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 
Packages
  100 /var/lib/dpkg/status
  [nlb-glaptop](0) $

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

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


[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

2016-05-03 Thread Stunts
@Konrad
Great idea.
Ok, so I went here[1] to get info on running "bluetoothctl" and pairing a 
device via this interface.
Here's the result:
Pairing works via "bluetoothctl". I did not have to enter a PIN code as before 
and as mentioned in the car's instructions.
After pairing was working, I was able to:
1. Browse the phone's address book;
2. Set "speed dials" using the phone's address book
3. Activate "Bluetooth" as a "source" for audio in the car, open the "Music" 
app and the music played through the car's speakers (albeit with a very low 
volume, and car controls don't work (next track, previous track, etc). This is 
an improvement as I had never been able to play the phone's audio via the car's 
speakers.
Unfortunately, the good news stop here.
1. Placing a call using the car's phone interface results in the phone placing 
the call, but no audio can be heard. Not even the "ring". The person on the 
other side had long hung up the call, but the phone's interface remained frozen 
and silent as if it were still trying to make the outgoing call.
2. Once somebody called me,  I expected the car to display the name of the 
person calling me. Instead I get "Unknown". Not even the phone number of the 
person calling is displayed.
3. Trying to answer the call results only in silence. I can't hear what the 
other person is saying, and they can't hear me. I was, however able to "answer" 
and "disconnect" the call using the car's interface.
4. Turning off bluetooth on the phone made it usable just as normal again. 

So all in all, what is currently happening is the same set of symptoms I had 
when I first got OTA9 and the pairing was already configured.
Should a separate issue be opened? We are looking at 2 distinct things here 
(maybe three) - one is the pairing problem. The other is the silence during the 
calls, and the other is the missing name of the caller.
That being said, what would you like me to log first and attempt to tackle?



[1] https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

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

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


[Kernel-packages] [Bug 1575467] Re: Ubuntu 16.04 consistently freezes up / hangs

2016-05-03 Thread kebabfish
Same freeze-bug on akoya p2212t with a n2920 cpu with ubuntu 14.10 - 16.04.
Ubuntu 14.04 with 3.13 works fine.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1575467

Title:
  Ubuntu 16.04 consistently freezes up / hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from stock Ubuntu 14.04 to 16.04 my laptop
  consistently freezes up and is unresponsive to keyboard or mouse. The
  only way is to do a hard shutdown. I'm usually in a browser when this
  happens, and often watching a video or two. It seems to happen more
  often in Google Chrome than Firefox, but it happens with both. It has
  happened at least once with no videos loaded. I haven’t observed it
  freeze / hang when I’m not in a browser, but that's mainly what i use
  my laptop for, so that's where most of my time is spent.

  Call trace:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 1949 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020
  InstallationDate: Installed on 2015-08-08 (263 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 3451
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  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-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0H4MK6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3451
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1571691] Re: linux: MokSBState is ignored

2016-05-03 Thread Tim Gardner
Yes, that message indicates that your kernel is _not_ in secure boot
mode, i.e., it _will_ load any (appropriately compiled) module.

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

Title:
  linux: MokSBState is ignored

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

Bug description:
  Ubuntu-4.4.0-20.36 was released with signed module enforcement
  enabled, but contained no way of disabling secure boot for DKMS.
  Without these kernel patches it is possible to get your machine in an
  unbootable state, especially if you don't have a fallback kernel.

  This patch set implements the ability to disable secure boot on demand
  from user space (with some password shennaigans). If one boots in
  secure boot mode and then installs a third party module (such as
  DKMS), then a dialog is displayed giving the user an option to disable
  secure boot, thereby also disabling module signature verification.
  Patch 1/2 is a scaffold patch of which only the GUID macros are
  actually used. The rest of the code is fenced by
  CONFIG_MODULE_SIG_UEFI which will not be enabled until a later series.
  Patch 2/2 is where MOKSBState is read and implemented. Patch 3/3
  simply prints a bit more informative state information.

  Information regarding secure boot and signed module enforcement will
  appear in the kernel log thusly:

  'Secure boot enabled' - normal secure boot operation with signed module 
enforcement.
  'Secure boot MOKSBState disabled' - UEFI Secure boot state has been 
over-ridden by MOKSBState. No signed module enforcement.

  In the absense of a 'Secure boot' string assume that secure boot is
  disabled or does not exist.

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

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


[Kernel-packages] [Bug 1566221] Re: linux: Enforce signed module loading when UEFI secure boot

2016-05-03 Thread Tim Gardner
lts-utopic and trusty tested in QEMU/OVMF with signed kernel, with and
without MokSBState enabled.

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

Title:
  linux: Enforce signed module loading when UEFI secure boot

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

Bug description:
  This work is authorized by an approved UOS spec and blueprint at
  https://wiki.ubuntu.com/Spec/InstallingUnsignedSecureBoot

  Add code to implement secure boot checks. Unsigned or incorrectly
  signed modules will continue to install while tainting the kernel
  _until_ EFI_SECURE_BOOT_SIG_ENFORCE is enabled.

  When EFI_SECURE_BOOT_SIG_ENFORCE is enabled, then the only recourse
  for platforms booting in secure boot mode with a DKMS dependency is to
  disable secure boot using mokutil:

  sudo mokutil --disable-validation
  sudo reboot

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

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


[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

2016-05-03 Thread Mike Rushton
Are there ppc64le versions of those kernels?

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

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

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


[Kernel-packages] [Bug 1577800] Re: Frequent disconnects with Intel 8260 wireless NIC

2016-05-03 Thread Craig G
Please see the upstream bug report for all of the necessary debugging
logs.  However, the bug has already been identified and the issue here
is really just deciding how to package the fix.

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

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

Title:
  Frequent disconnects with Intel 8260 wireless NIC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This issue has been resolved upstream and is described in
  https://bugzilla.kernel.org/show_bug.cgi?id=117391

  The current Ubuntu Xenial Xerus kernel (4.4.0-21.37) is built with a
  version of the iwlwifi driver which supports firmware version up to
  iwlwifi-8000C-19.ucode.  However, the matching linux-firmware package
  ships with the -16.ucode version of the firmware, which contains this
  bug.

  The next stable version of the firmware after -16.ucode is -21.ucode,
  but is not supported by the version of the iwlwifi driver in the 4.4.0
  kernel.  In order to fix this issue, either the minor version of the
  firmware (-19.ucode) needs to be included in the linux-firmware
  package or the iwlwifi driver in the kernel package needs to be
  upgraded with a backport of the iwlwifi driver new enough to support
  the -21.ucode firmware.

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

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


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

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

apport-collect 1577800

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

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

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

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

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

Title:
  Frequent disconnects with Intel 8260 wireless NIC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This issue has been resolved upstream and is described in
  https://bugzilla.kernel.org/show_bug.cgi?id=117391

  The current Ubuntu Xenial Xerus kernel (4.4.0-21.37) is built with a
  version of the iwlwifi driver which supports firmware version up to
  iwlwifi-8000C-19.ucode.  However, the matching linux-firmware package
  ships with the -16.ucode version of the firmware, which contains this
  bug.

  The next stable version of the firmware after -16.ucode is -21.ucode,
  but is not supported by the version of the iwlwifi driver in the 4.4.0
  kernel.  In order to fix this issue, either the minor version of the
  firmware (-19.ucode) needs to be included in the linux-firmware
  package or the iwlwifi driver in the kernel package needs to be
  upgraded with a backport of the iwlwifi driver new enough to support
  the -21.ucode firmware.

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

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


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

2016-05-03 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/1577792

Title:
  video not working after resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I suspended my x250.  Then plugged it in (overnight).  Then unplugged
  it.  Then opened it.  It resumed, but video did not work.  I closed
  the lid and opened it, a few times.  No dice.  Then, I pressed the
  power button, and the video came back on.  I was sitting next to
  Leann, Chris, and Brad here at the CDO Sprint.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kirkland   4510 F pulseaudio
   /dev/snd/pcmC1D0p:   kirkland   4510 F...m pulseaudio
   /dev/snd/controlC1:  kirkland   4510 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May  3 08:18:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-15 (354 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CMCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=a4d6a56a-7b1b-4a7c-8420-f2b8e6d15c37 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  UpgradeStatus: Upgraded to xenial on 2016-01-04 (119 days ago)
  dmi.bios.date: 03/05/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET30W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkpadX250:rvnLENOVO:rn20CMCTO1WW:rvr0B98417PRO:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CMCTO1WW
  dmi.product.version: Thinkpad X250
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1577802] [NEW] bluetooth keyboard layout

2016-05-03 Thread Gerd Hammer
Public bug reported:

Bq Aquarius M10 Ubuntu Edition  Ota-10.1, System language German. When I
connect an external keyboard (Logittech  K480) with german layout it
works fine, but Libreoffice and Firefox do not accept the keyboard
layout and continue with qwerty instead of qwertz. What can I do?

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

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

Title:
  bluetooth keyboard layout

Status in bluez package in Ubuntu:
  New

Bug description:
  Bq Aquarius M10 Ubuntu Edition  Ota-10.1, System language German. When
  I connect an external keyboard (Logittech  K480) with german layout it
  works fine, but Libreoffice and Firefox do not accept the keyboard
  layout and continue with qwerty instead of qwertz. What can I do?

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

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


[Kernel-packages] [Bug 1577800] [NEW] Frequent disconnects with Intel 8260 wireless NIC

2016-05-03 Thread Craig G
Public bug reported:

This issue has been resolved upstream and is described in
https://bugzilla.kernel.org/show_bug.cgi?id=117391

The current Ubuntu Xenial Xerus kernel (4.4.0-21.37) is built with a
version of the iwlwifi driver which supports firmware version up to
iwlwifi-8000C-19.ucode.  However, the matching linux-firmware package
ships with the -16.ucode version of the firmware, which contains this
bug.

The next stable version of the firmware after -16.ucode is -21.ucode,
but is not supported by the version of the iwlwifi driver in the 4.4.0
kernel.  In order to fix this issue, either the minor version of the
firmware (-19.ucode) needs to be included in the linux-firmware package
or the iwlwifi driver in the kernel package needs to be upgraded with a
backport of the iwlwifi driver new enough to support the -21.ucode
firmware.

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

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

Title:
  Frequent disconnects with Intel 8260 wireless NIC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue has been resolved upstream and is described in
  https://bugzilla.kernel.org/show_bug.cgi?id=117391

  The current Ubuntu Xenial Xerus kernel (4.4.0-21.37) is built with a
  version of the iwlwifi driver which supports firmware version up to
  iwlwifi-8000C-19.ucode.  However, the matching linux-firmware package
  ships with the -16.ucode version of the firmware, which contains this
  bug.

  The next stable version of the firmware after -16.ucode is -21.ucode,
  but is not supported by the version of the iwlwifi driver in the 4.4.0
  kernel.  In order to fix this issue, either the minor version of the
  firmware (-19.ucode) needs to be included in the linux-firmware
  package or the iwlwifi driver in the kernel package needs to be
  upgraded with a backport of the iwlwifi driver new enough to support
  the -21.ucode firmware.

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

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


[Kernel-packages] [Bug 1564949] Re: Severe latency/skew on AMD Opetron processor

2016-05-03 Thread Jeff Lane
Per Narinder:
Also on DL385p Gen8  is reported the kernel hang and storage controller in soft 
lock up mode with 14.4.4 and 16.04 images. And i believe it is hpsa driver 
error which is soft locking. I told HP team to look into it as HP owns the hpsa 
driver.

So there's more than just the CPU timer issue going on with these
systems.

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

Title:
  Severe latency/skew on AMD Opetron processor

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Discovered this while doing pre-release certification testing for
  16.04 on an HP ProLiant DL385p Gen8 with an AMD Opteron 6320 8-core
  CPU.

  I have some code that essentially does this:  And note, I am NOT a C
  programmer, I know enough C to read it and do some minor things, and I
  once knew C++ fairly well, about 10 years ago...

  gettimeofday(&tval_start, NULL);
  sleep(sleeptime);
  gettimeofday(&tval_stop, NULL);

  where tval_start and tval_stop are timeval structs and sleeptime is
  60.

  Once it gets the start and stop it finds the delta minus the sleep
  time.

  In a perfect world, for example, start time would be 123456.123 and
  end time would be 123516.123 and the delta between them minus the 60
  seconds of sleep would be 0.

  Of course, that isn't how it works in reality so the delta may be a
  few microseconds here and there depending on what else the kernel is
  doing at any given moment.  The following, however, are on essentially
  idle Xenial systems (only processes running are whatever Ubuntu Server
  runs by default, nothing really taxing going on).

  On my Skylake i7 with Xenial, the time differences are never more than
  a few 10,000ths of a second: (kernel 4.4.0-15.31)
  Testing clock direction for 5 minutes...
  PASSED: Iteration 0 delta: 0.000109
  PASSED: Iteration 1 delta: 0.68
  PASSED: Iteration 2 delta: 0.000107
  PASSED: Iteration 3 delta: 0.000216
  PASSED: Iteration 4 delta: 0.89

  On a zVM instance (kernel 4.4.0-16.32) it's even better:
  PASSED: Iteration 0 delta: 0.58
  PASSED: Iteration 1 delta: 0.58
  PASSED: Iteration 2 delta: 0.74
  PASSED: Iteration 3 delta: 0.52
  PASSED: Iteration 4 delta: 0.62

  But on an AMD cpu with Xenial (the only AMD CPU I have access to), the
  difference is always in the 10ths of a second, sometimes even several
  seconds... in other words, I've seen up to a 7.9 second delta with
  this code.  Here's one run that shows 3 seconds in one iteration:
  (kernel 4.4.0-15.31)
  FAILED: Iteration 0 delta: 3.057980
  FAILED: Iteration 1 delta: 0.225712
  FAILED: Iteration 2 delta: 0.241468
  FAILED: Iteration 3 delta: 0.229084
  FAILED: Iteration 4 delta: 0.223933

  I ran a second run on the AMD cpu and the latency was all over the place:
  FAILED: Iteration 0 delta: 9.302149
  FAILED: Iteration 1 delta: 0.624466
  FAILED: Iteration 2 delta: 1.644834
  FAILED: Iteration 3 delta: 1.011474
  FAILED: Iteration 4 delta: 0.923033

  After a discussion with cking and apw, deviations of as seen on the
  Intel and s390 CPUs are about what we should expect to see depending
  on what the system is doing at the moment gettimeofday() is executed.
  However, on the AMD CPU, differences of up to 9 seconds or more are
  NOT expected and highly irregular.

  Colin said he tested this on an AMD C60 CPU and got numbers inline
  with the Skylake and s390 chips and could not reproduce the times I am
  seeing on the Opteron.

  $ cat /proc/version_signature 
  Ubuntu 4.4.0-15.31-generic 4.4.6
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 31 17:21 seq
   crw-rw 1 root audio 116, 33 Mar 31 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b6a44b05-ebe0-4d1c-a525-69d4748960f8
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL385p Gen8
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=70808172-98ba-4129-a185-20a112bdc4fe ro rootdelay=60
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sam

[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

2016-05-03 Thread Konrad Zapałowicz
@Stunts:

There is one thing, however, that you could try on your phone. In order
to make sure that the flaw is still in the Ubuntu System Settings you
could try to pair and connect with the car using the bluetoothctl
commandline interface w/o even opening the Bluetooth settings scope.

In order to achieve this you will have to connect to the phone either
using the ssh or use any kid of terminal emulator on it. Let me know if
you need further instructions in order to accomplish this and I will
walk you through.

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

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

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


[Kernel-packages] [Bug 1577795] [NEW] Ubuntu touch Frieza ota-10.1 dropping connection to logitech k810

2016-05-03 Thread Paul Spain
Public bug reported:

I can successfully pair the k810 to my BQ Aquaris M10 FHD tablet.
The connection state flips every few seconds between connected and disconected 
and the signal strength between excellent and none.
I have tried forgetting the connection and repairing, and power-cycling then 
repeating the process, to no avail.
Both the tablet and keyboard have a full charge.
I have successfully paired and am using a Logitech Ultrathin mouse with the 
tablet.
I have succesfully paired and use the k810 keyboard with several Android 
devices across multiple versions of Android.
I have also paired and use the keyboard with Ubuntu 14.04 LTS.

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

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

Title:
  Ubuntu touch Frieza ota-10.1 dropping connection to logitech k810

Status in bluez package in Ubuntu:
  New

Bug description:
  I can successfully pair the k810 to my BQ Aquaris M10 FHD tablet.
  The connection state flips every few seconds between connected and 
disconected and the signal strength between excellent and none.
  I have tried forgetting the connection and repairing, and power-cycling then 
repeating the process, to no avail.
  Both the tablet and keyboard have a full charge.
  I have successfully paired and am using a Logitech Ultrathin mouse with the 
tablet.
  I have succesfully paired and use the k810 keyboard with several Android 
devices across multiple versions of Android.
  I have also paired and use the keyboard with Ubuntu 14.04 LTS.

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

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


[Kernel-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang

2016-05-03 Thread Michael G.
@tjaalton: Could you please elaborate what that means? Does that mean
that a fix will be available via the ubuntu updater soon? Or do we have
to wait till 16.10? 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/1559308

Title:
  Plugging HDMI screen in causes system hang

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  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 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  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.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

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

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


[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell

2016-05-03 Thread Kamal Mostafa
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  OOPS on wily+ for Haswell-ULT and Broadwell

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the wily 4.2 kernel, we see early OOPSes similar to
  the following on Haswell-ULT and Broadwell processors:

  [ cut here ]
  WARNING: CPU: 1 PID: 1 at 
/build/linux-lts-wily-MVxxD8/linux-lts-wily-4.2.0/arch/x86/mm/ioremap.c:198 
__ioremap_caller+0x2a2/0x360()
  Info: mapping multiple BARs. Your kernel is fine.
  Modules linked in:
  CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.2.0-34-generic #39~14.04.1-Ubuntu
  Hardware name: Hewlett-Packard HP EliteBook Folio 1040 G1/213E, BIOS L83 Ver. 
01.07 03/28/2014
   81a91c80 88023522bad8 817b5fed 0001
   88023522bb28 88023522bb18 8107799a c9cbe000
   c9cb8000 c9cb8000 6000 880230297040
  Call Trace:
   [] dump_stack+0x45/0x57
   [] warn_slowpath_common+0x8a/0xc0
   [] warn_slowpath_fmt+0x46/0x50
   [] __ioremap_caller+0x2a2/0x360
   [] ioremap_nocache+0x17/0x20
   [] snb_uncore_imc_init_box+0x65/0x90
   [] uncore_pci_probe+0xd5/0x1c0
   [] local_pci_probe+0x45/0xa0
   [] ? pci_match_device+0xf4/0x120
   [] pci_device_probe+0xca/0x110
   [] driver_probe_device+0x213/0x460
   [] __driver_attach+0x90/0xa0
   [] ? driver_probe_device+0x460/0x460
   [] bus_for_each_dev+0x5d/0x90
   [] driver_attach+0x1e/0x20
   [] bus_add_driver+0x1d0/0x290
   [] ? uncore_cpu_setup+0x12/0x12
   [] driver_register+0x60/0xe0
   [] __pci_register_driver+0x4c/0x50
   [] intel_uncore_init+0xe6/0x2fc
   [] ? uncore_cpu_setup+0x12/0x12
   [] do_one_initcall+0xcd/0x1f0
   [] ? parse_args+0x120/0x470
   [] ? __wake_up+0x48/0x60
   [] kernel_init_freeable+0x199/0x226
   [] ? initcall_blacklist+0xc0/0xc0
   [] ? rest_init+0x80/0x80
   [] kernel_init+0xe/0xe0
   [] ret_from_fork+0x3f/0x70
   [] ? rest_init+0x80/0x80
  ---[ end trace 5f5beae5b9d2dc45 ]---

  the issue is fixed in upstream kernels, via two patches:

  https://lkml.org/lkml/2015/12/11/165
  http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html

  each is a one-liner against the mch_quirk_devices[] structure.

  [nlb-glaptop](0) $ cat /proc/version_signature 
  Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  [nlb-glaptop](0) $ 

  [nlb-glaptop](0) $ lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  [nlb-glaptop](0) $ 

  [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily
  linux-generic-lts-wily:
Installed: 4.2.0.35.28
Candidate: 4.2.0.35.28
Version table:
   *** 4.2.0.35.28 0
  600 https://rapture-prod.corp.google.com/ 
goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 
Packages
  100 /var/lib/dpkg/status
  [nlb-glaptop](0) $

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

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


[Kernel-packages] [Bug 1577792] [NEW] video not working after resume

2016-05-03 Thread Dustin Kirkland 
Public bug reported:

I suspended my x250.  Then plugged it in (overnight).  Then unplugged
it.  Then opened it.  It resumed, but video did not work.  I closed the
lid and opened it, a few times.  No dice.  Then, I pressed the power
button, and the video came back on.  I was sitting next to Leann, Chris,
and Brad here at the CDO Sprint.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kirkland   4510 F pulseaudio
 /dev/snd/pcmC1D0p:   kirkland   4510 F...m pulseaudio
 /dev/snd/controlC1:  kirkland   4510 F pulseaudio
CurrentDesktop: Unity
Date: Tue May  3 08:18:10 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-15 (354 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 20CMCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=a4d6a56a-7b1b-4a7c-8420-f2b8e6d15c37 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic  N/A
 linux-firmware1.157
SourcePackage: linux
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
UpgradeStatus: Upgraded to xenial on 2016-01-04 (119 days ago)
dmi.bios.date: 03/05/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N10ET30W (1.07 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CMCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98417 PRO
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkpadX250:rvnLENOVO:rn20CMCTO1WW:rvr0B98417PRO:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20CMCTO1WW
dmi.product.version: Thinkpad X250
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug xenial

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

Title:
  video not working after resume

Status in linux package in Ubuntu:
  New

Bug description:
  I suspended my x250.  Then plugged it in (overnight).  Then unplugged
  it.  Then opened it.  It resumed, but video did not work.  I closed
  the lid and opened it, a few times.  No dice.  Then, I pressed the
  power button, and the video came back on.  I was sitting next to
  Leann, Chris, and Brad here at the CDO Sprint.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kirkland   4510 F pulseaudio
   /dev/snd/pcmC1D0p:   kirkland   4510 F...m pulseaudio
   /dev/snd/controlC1:  kirkland   4510 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May  3 08:18:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-15 (354 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CMCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=a4d6a56a-7b1b-4a7c-8420-f2b8e6d15c37 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  UpgradeStatus: Upgraded to xenial on 2016-01-04 (119 days ago)
  dmi.bios.date: 03/05/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET30W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkpadX250:rvnLENOVO:rn20CMCTO1WW:rvr0B98417PRO:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CMCTO1WW
  dmi.product.version: Thinkpad X250
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

2016-05-03 Thread Konrad Zapałowicz
Hey, the Bluetooth bugs with cars are our top priority at the moment and
we are putting the effort into fixing them as soon as we can.

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

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

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


[Kernel-packages] [Bug 1559469] Re: [Dell Inc. XPS 13 9350] suspend/resume failure

2016-05-03 Thread Shunning Jiang
For me, when I close the lid to suspend, sometimes it automatically
wakes up without my opening the lid, and the screen freezes. The light
is on but all I see is the black screen.

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

Title:
  [Dell Inc. XPS 13 9350] suspend/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  suspend failure, my system halt

  ProblemType: KernelOops
  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
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1348 F pulseaudio
simon  1822 F pulseaudio
  Date: Sat Mar 19 15:24:50 2016
  DuplicateSignature: suspend/resume:Dell Inc. XPS 13 9350:1.2.3
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=975f7887-2e07-4f75-a523-7625eb0515b0
  InstallationDate: Installed on 2016-03-11 (7 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  InterpreterPath: /usr/bin/python3.5
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-14-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   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
  Title: [Dell Inc. XPS 13 9350] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 0PWNCR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0PWNCR:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1576564] Re: Xen 32bit dom0 on 64bit hypervisor: bad page flags

2016-05-03 Thread Stefan Bader
While not restricting the maximum dom0 memory maybe is not the optimal
case, it still would be a valid config. So I tested more kernel
versions. The bad page bug messages started to appear with kernel 4.2
and the panic is starting with 4.4.

Using sync_console and minicom capture mode, I finally got a complete
log of the boot messages using a 4.6-rc6 kernel.

** Attachment added: "Xen and dom0 console log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576564/+attachment/4654438/+files/console.txt

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

Title:
  Xen 32bit dom0 on 64bit hypervisor: bad page flags

Status in linux package in Ubuntu:
  Triaged
Status in xen package in Ubuntu:
  Triaged

Bug description:
  This problem is a mix between running certain versions of 32bit Linux
  kernel dom0 on certain versions of 64bit Xen hypervisor, combined with
  certain memory clamping settings (dom0_mem=xM, without setting the max
  limit).

  Xen 4.4.2 + Linux 3.13.x
  Xen 4.5.0 + linux 3.19.x
  Xen 4.6.0 + linux 4.0.x
  Xen 4.6.0 + linux 4.1.x
   -> all boot without messages
  Xen 4.5.1 + Linux 4.2.x
  Xen 4.6.0 + Linux 4.2.x
  Xen 4.6.0 + Linux 4.3.x
   * dom0_mem 512M, 4096M, or unlimited
     -> boot without messages
   * dom0_mem between 1024M and 3072M (inclusive)
     -> bad page messages (but finishes boot)
  Xen 4.6.0 + Linux 4.4.x
  Xen 4.6.0 + Linux 4.5.x
  Xen 4.6.0 + Linux 4.6-rc6
   The boot for 512M,4096M, and unlimited looks good as well. Though trying to
   start a domU without dom0_mem set caused a crash when ballooning (but I
   think this should be a seperate bug)
   Using a dom0_mem range between 1G and 3G it looks like still producing the
   bad page flags bug message and additionally panicking + reboot.

  The bad page bug generally looks like this (the pfn numbers seem to be
  towards the end of the allocated range.

  [8.980150] BUG: Bad page state in process swapper/0  pfn:7fc22
  [8.980238] page:f4566550 count:0 mapcount:0 mapping:  (null) index:0x0
  [8.980328] flags: 0x7000400(reserved)
  [8.980486] page dumped because: PAGE_FLAGS_CHECK_AT_PREP flag set
  [8.980575] bad because of flags:
  [8.980688] flags: 0x400(reserved)
  [8.980844] Modules linked in:
  [8.980960] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GB   
4.2.0-19-
  generic #23-Ubuntu
  [8.981084] Hardware name: Supermicro H8SGL/H8SGL, BIOS 3.0
08/31/2012
  [8.981177]  c1a649a7 23e07668  e9cafce4 c175e501 f4566550 
e9cafd08 c
  1166897
  [8.981608]  c19750a4 e9d183ec 0007fc22 007f c1975630 c1978e86 
0001 e
  9cafd74
  [8.982074]  c1169f83 0002 0141 0004a872 c1af3644  
ee44bce4 e
  e44bce4
  [8.982506] Call Trace:
  [8.982582]  [] dump_stack+0x41/0x52
  [8.982666]  [] bad_page+0xb7/0x110
  [8.982749]  [] get_page_from_freelist+0x2d3/0x610
  [8.982838]  [] __alloc_pages_nodemask+0x153/0x910
  [8.982926]  [] ? find_entry.isra.13+0x52/0x90
  [8.983013]  [] ? kmem_cache_alloc_trace+0x175/0x1e0
  [8.983102]  [] ? 
__raw_callee_save___pv_queued_spin_unlock+0x6/0x10
  [8.983223]  [] ? __kmalloc+0x21d/0x240
  [8.983308]  [] __vmalloc_node_range+0x10e/0x210
  [8.983433]  [] ? bpf_prog_alloc+0x37/0xa0
  [8.983518]  [] __vmalloc_node+0x66/0x70
  [8.983604]  [] ? bpf_prog_alloc+0x37/0xa0
  [8.983689]  [] __vmalloc+0x34/0x40
  [8.983773]  [] ? bpf_prog_alloc+0x37/0xa0
  [8.983859]  [] bpf_prog_alloc+0x37/0xa0
  [8.983944]  [] bpf_prog_create+0x2c/0x90
  [8.984034]  [] ? bsp_pm_check_init+0x11/0x11
  [8.984121]  [] ptp_classifier_init+0x2b/0x44
  [8.984207]  [] sock_init+0x7c/0x83
  [8.984291]  [] do_one_initcall+0xaa/0x200
  [8.984376]  [] ? bsp_pm_check_init+0x11/0x11
  [8.984463]  [] ? repair_env_string+0x12/0x54
  [8.984551]  [] ? kernel_init_freeable+0x126/0x1d9
  [8.984726]  [] kernel_init+0x10/0xe0
  [8.984846]  [] ? schedule_tail+0x11/0x50
  [8.984932]  [] ret_from_kernel_thread+0x21/0x30
  [8.985019]  [] ? rest_init+0x70/0x70

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

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


[Kernel-packages] [Bug 1546603] Re: Bluetooth mouse connects but doesn't work

2016-05-03 Thread Felix Delattre
GATT is part of bluez experimental feature: bluetoothd -E.

After I enabled it by setting the NOPLUGIN_OPTION="-E" into the
/etc/default/bluetooth file. I just had to pair and trust the mouse
manually using the "bluetoothctl" console and it worked fine.

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

Title:
  Bluetooth mouse connects but doesn't work

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth mouse that I can get to connect via the gnome
  bluetooth settings panel, but even after it's connected it doesn't
  move the pointer or register any clicks.

  the following shows up in the journal :

  $ $ journalctl -b 0 |grep bluetooth
  Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth daemon 5.36
  Feb 17 07:18:22 spiny bluetoothd[1009]: Starting SDP server
  Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth management interface 1.10 
initialized
  Feb 17 07:18:22 spiny bluetoothd[1009]: Failed to obtain handles for "Service 
Changed" characteristic
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Error adding Link Loss service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Current Time Service could not be 
registered
  Feb 17 07:18:22 spiny bluetoothd[1009]: gatt-time-server: Input/output error 
(5)
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Sap driver initialization failed.
  Feb 17 07:18:22 spiny bluetoothd[1009]: sap-server: Operation not permitted 
(1)
  Feb 17 07:18:22 spiny NetworkManager[1062]:   Loaded device plugin: 
NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
  Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSource
  Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSink
  Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSource
  Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSink
  Feb 17 07:18:42 spiny bluetoothd[1009]: RFCOMM server failed for Headset 
Voice gateway: rfcomm_bind: Address already in use (98)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher gufw (missing 
desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  Feb 17 07:19:00 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 
'str != NULL' failed
  Feb 17 07:19:01 spiny bluetoothd[1009]: No cache for F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x000c for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x001b for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x003f for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Report Map read failed: Attribute 
requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Protocol Mode characteristic read 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: HID Information read failed: 
Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:08 sp

[Kernel-packages] [Bug 1576564] Re: Xen 32bit dom0 on 64bit hypervisor: bad page flags

2016-05-03 Thread Stefan Bader
** Description changed:

  This problem is a mix between running certain versions of 32bit Linux
  kernel dom0 on certain versions of 64bit Xen hypervisor, combined with
- certain memory clamping settings.
+ certain memory clamping settings (dom0_mem=xM, without setting the max
+ limit).
  
  Xen 4.4.2 + Linux 3.13.x
-  -> at least boots without messages
  Xen 4.5.0 + linux 3.19.x
-  -> at least boots without messages
+ Xen 4.6.0 + linux 4.0.x
+ Xen 4.6.0 + linux 4.1.x
+  -> all boot without messages
  Xen 4.5.1 + Linux 4.2.x
+ Xen 4.6.0 + Linux 4.2.x
+ Xen 4.6.0 + Linux 4.3.x
   * dom0_mem 512M, 4096M, or unlimited
     -> boot without messages
   * dom0_mem between 1024M and 3072M (inclusive)
     -> bad page messages (but finishes boot)
- Xen 4.6 + Linux 4.2.x
-  -> all cases as with Xen 4.5.1
- Xen 4.6 + Linux 4.4.x..4.6-rc5
+ Xen 4.6.0 + Linux 4.4.x
+ Xen 4.6.0 + Linux 4.5.x
+ Xen 4.6.0 + Linux 4.6-rc6
   The boot for 512M,4096M, and unlimited looks good as well. Though trying to
   start a domU without dom0_mem set caused a crash when ballooning (but I
   think this should be a seperate bug)
   Using a dom0_mem range between 1G and 3G it looks like still producing the
   bad page flags bug message and additionally panicking + reboot.
-  Unfortunately there is no clear panic message, the serial console
-  seems to be overwhelmed.
  
  The bad page bug generally looks like this (the pfn numbers seem to be
  towards the end of the allocated range.
  
  [8.980150] BUG: Bad page state in process swapper/0  pfn:7fc22
  [8.980238] page:f4566550 count:0 mapcount:0 mapping:  (null) index:0x0
  [8.980328] flags: 0x7000400(reserved)
  [8.980486] page dumped because: PAGE_FLAGS_CHECK_AT_PREP flag set
  [8.980575] bad because of flags:
  [8.980688] flags: 0x400(reserved)
  [8.980844] Modules linked in:
  [8.980960] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GB   
4.2.0-19-
  generic #23-Ubuntu
  [8.981084] Hardware name: Supermicro H8SGL/H8SGL, BIOS 3.0
08/31/2012
  [8.981177]  c1a649a7 23e07668  e9cafce4 c175e501 f4566550 
e9cafd08 c
  1166897
  [8.981608]  c19750a4 e9d183ec 0007fc22 007f c1975630 c1978e86 
0001 e
  9cafd74
  [8.982074]  c1169f83 0002 0141 0004a872 c1af3644  
ee44bce4 e
  e44bce4
  [8.982506] Call Trace:
  [8.982582]  [] dump_stack+0x41/0x52
  [8.982666]  [] bad_page+0xb7/0x110
  [8.982749]  [] get_page_from_freelist+0x2d3/0x610
  [8.982838]  [] __alloc_pages_nodemask+0x153/0x910
  [8.982926]  [] ? find_entry.isra.13+0x52/0x90
  [8.983013]  [] ? kmem_cache_alloc_trace+0x175/0x1e0
  [8.983102]  [] ? 
__raw_callee_save___pv_queued_spin_unlock+0x6/0x10
  [8.983223]  [] ? __kmalloc+0x21d/0x240
  [8.983308]  [] __vmalloc_node_range+0x10e/0x210
  [8.983433]  [] ? bpf_prog_alloc+0x37/0xa0
  [8.983518]  [] __vmalloc_node+0x66/0x70
  [8.983604]  [] ? bpf_prog_alloc+0x37/0xa0
  [8.983689]  [] __vmalloc+0x34/0x40
  [8.983773]  [] ? bpf_prog_alloc+0x37/0xa0
  [8.983859]  [] bpf_prog_alloc+0x37/0xa0
  [8.983944]  [] bpf_prog_create+0x2c/0x90
  [8.984034]  [] ? bsp_pm_check_init+0x11/0x11
  [8.984121]  [] ptp_classifier_init+0x2b/0x44
  [8.984207]  [] sock_init+0x7c/0x83
  [8.984291]  [] do_one_initcall+0xaa/0x200
  [8.984376]  [] ? bsp_pm_check_init+0x11/0x11
  [8.984463]  [] ? repair_env_string+0x12/0x54
  [8.984551]  [] ? kernel_init_freeable+0x126/0x1d9
  [8.984726]  [] kernel_init+0x10/0xe0
  [8.984846]  [] ? schedule_tail+0x11/0x50
  [8.984932]  [] ret_from_kernel_thread+0x21/0x30
  [8.985019]  [] ? rest_init+0x70/0x70

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

Title:
  Xen 32bit dom0 on 64bit hypervisor: bad page flags

Status in linux package in Ubuntu:
  Triaged
Status in xen package in Ubuntu:
  Triaged

Bug description:
  This problem is a mix between running certain versions of 32bit Linux
  kernel dom0 on certain versions of 64bit Xen hypervisor, combined with
  certain memory clamping settings (dom0_mem=xM, without setting the max
  limit).

  Xen 4.4.2 + Linux 3.13.x
  Xen 4.5.0 + linux 3.19.x
  Xen 4.6.0 + linux 4.0.x
  Xen 4.6.0 + linux 4.1.x
   -> all boot without messages
  Xen 4.5.1 + Linux 4.2.x
  Xen 4.6.0 + Linux 4.2.x
  Xen 4.6.0 + Linux 4.3.x
   * dom0_mem 512M, 4096M, or unlimited
     -> boot without messages
   * dom0_mem between 1024M and 3072M (inclusive)
     -> bad page messages (but finishes boot)
  Xen 4.6.0 + Linux 4.4.x
  Xen 4.6.0 + Linux 4.5.x
  Xen 4.6.0 + Linux 4.6-rc6
   The boot for 512M,4096M, and unlimited looks good as well. Though trying to
   start a domU without dom0_mem set caused a crash when ballooning (but I
   think this should be a seperate bug)
   Using a dom0_mem range between 1G and 3G it looks like still producing the
   bad pa

[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell

2016-05-03 Thread nick black
apport-collect crashes:

[nlb-glaptop](0) $ apport-collect 1577748
Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 594, in 
app.run_argv()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 653, in run_argv
return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 525, in 
run_update_report
pkgs = self.crashdb.get_affected_packages(self.options.update_report)
  File "/usr/lib/python2.7/dist-packages/apport/crashdb_impl/memory.py", line 
79, in get_affected_packages
return [self.reports[id]['report']['SourcePackage']]
IndexError: list index out of range
[nlb-glaptop](1) $

Manually Confirming

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

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

Title:
  OOPS on wily+ for Haswell-ULT and Broadwell

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the wily 4.2 kernel, we see early OOPSes similar to
  the following on Haswell-ULT and Broadwell processors:

  [ cut here ]
  WARNING: CPU: 1 PID: 1 at 
/build/linux-lts-wily-MVxxD8/linux-lts-wily-4.2.0/arch/x86/mm/ioremap.c:198 
__ioremap_caller+0x2a2/0x360()
  Info: mapping multiple BARs. Your kernel is fine.
  Modules linked in:
  CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.2.0-34-generic #39~14.04.1-Ubuntu
  Hardware name: Hewlett-Packard HP EliteBook Folio 1040 G1/213E, BIOS L83 Ver. 
01.07 03/28/2014
   81a91c80 88023522bad8 817b5fed 0001
   88023522bb28 88023522bb18 8107799a c9cbe000
   c9cb8000 c9cb8000 6000 880230297040
  Call Trace:
   [] dump_stack+0x45/0x57
   [] warn_slowpath_common+0x8a/0xc0
   [] warn_slowpath_fmt+0x46/0x50
   [] __ioremap_caller+0x2a2/0x360
   [] ioremap_nocache+0x17/0x20
   [] snb_uncore_imc_init_box+0x65/0x90
   [] uncore_pci_probe+0xd5/0x1c0
   [] local_pci_probe+0x45/0xa0
   [] ? pci_match_device+0xf4/0x120
   [] pci_device_probe+0xca/0x110
   [] driver_probe_device+0x213/0x460
   [] __driver_attach+0x90/0xa0
   [] ? driver_probe_device+0x460/0x460
   [] bus_for_each_dev+0x5d/0x90
   [] driver_attach+0x1e/0x20
   [] bus_add_driver+0x1d0/0x290
   [] ? uncore_cpu_setup+0x12/0x12
   [] driver_register+0x60/0xe0
   [] __pci_register_driver+0x4c/0x50
   [] intel_uncore_init+0xe6/0x2fc
   [] ? uncore_cpu_setup+0x12/0x12
   [] do_one_initcall+0xcd/0x1f0
   [] ? parse_args+0x120/0x470
   [] ? __wake_up+0x48/0x60
   [] kernel_init_freeable+0x199/0x226
   [] ? initcall_blacklist+0xc0/0xc0
   [] ? rest_init+0x80/0x80
   [] kernel_init+0xe/0xe0
   [] ret_from_fork+0x3f/0x70
   [] ? rest_init+0x80/0x80
  ---[ end trace 5f5beae5b9d2dc45 ]---

  the issue is fixed in upstream kernels, via two patches:

  https://lkml.org/lkml/2015/12/11/165
  http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html

  each is a one-liner against the mch_quirk_devices[] structure.

  [nlb-glaptop](0) $ cat /proc/version_signature 
  Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  [nlb-glaptop](0) $ 

  [nlb-glaptop](0) $ lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  [nlb-glaptop](0) $ 

  [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily
  linux-generic-lts-wily:
Installed: 4.2.0.35.28
Candidate: 4.2.0.35.28
Version table:
   *** 4.2.0.35.28 0
  600 https://rapture-prod.corp.google.com/ 
goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 
Packages
  100 /var/lib/dpkg/status
  [nlb-glaptop](0) $

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

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


[Kernel-packages] [Bug 1570503] Re: Computer freezes on hibernate

2016-05-03 Thread Michael Kaiser
Update: I found that I can reliably reproduce the failure by running

stress --vm-bytes $(awk '/MemFree/{printf "%d\n", $2 * 0.9;}' <
/proc/meminfo)k --vm-keep -m 1

and then trying to hibernate. So I did a git bisect between
Ubuntu-4.2.0-34.39 and Ubuntu-4.2.0-35.40 and identified this commit[0]
as the one that introduced the problem.

[0] http://kernel.ubuntu.com/git/ubuntu/ubuntu-
wily.git/commit/?id=292d352640b677d473fbd9e13c63a0826fafa2a8

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

Title:
  Computer freezes on hibernate

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since version 4.2.0-35 hibernation fails when there's significant RAM
  usage, like running google chrome with tens of open tabs. The screen
  will turn dark, display goes to sleep mode, but the computer just
  hangs and doesn't power off. (I am still able to ping the machine, but
  can't ssh in for example). When I reset the machine, it will just boot
  normally instead of resuming. The problem doesn't show when there's
  low RAM usage (like, just hibernating from an empty desktop) and it
  doesn't show when running 4.2.0-34.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-35-generic 4.2.0-35.40
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 14 19:25:09 2016
  HibernationDevice: RESUME=/dev/mapper/swap
  InstallationDate: Installed on 2015-05-11 (339 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   docker0   no wireless extensions.
   
   lono wireless extensions.
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-35-generic 
root=UUID=7612132b-8a66-4416-89e1-ac334e9dee91 ro rootflags=subvol=@
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-35-generic N/A
   linux-backports-modules-4.2.0-35-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-05 (161 days ago)
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0128.2011.0823.1224
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-207
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0128.2011.0823.1224:bd08/23/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-207:cvn:ct3:cvr:

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

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


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

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

apport-collect 1577748

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

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

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

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

** Tags added: trusty

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

Title:
  OOPS on wily+ for Haswell-ULT and Broadwell

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the wily 4.2 kernel, we see early OOPSes similar to
  the following on Haswell-ULT and Broadwell processors:

  [ cut here ]
  WARNING: CPU: 1 PID: 1 at 
/build/linux-lts-wily-MVxxD8/linux-lts-wily-4.2.0/arch/x86/mm/ioremap.c:198 
__ioremap_caller+0x2a2/0x360()
  Info: mapping multiple BARs. Your kernel is fine.
  Modules linked in:
  CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.2.0-34-generic #39~14.04.1-Ubuntu
  Hardware name: Hewlett-Packard HP EliteBook Folio 1040 G1/213E, BIOS L83 Ver. 
01.07 03/28/2014
   81a91c80 88023522bad8 817b5fed 0001
   88023522bb28 88023522bb18 8107799a c9cbe000
   c9cb8000 c9cb8000 6000 880230297040
  Call Trace:
   [] dump_stack+0x45/0x57
   [] warn_slowpath_common+0x8a/0xc0
   [] warn_slowpath_fmt+0x46/0x50
   [] __ioremap_caller+0x2a2/0x360
   [] ioremap_nocache+0x17/0x20
   [] snb_uncore_imc_init_box+0x65/0x90
   [] uncore_pci_probe+0xd5/0x1c0
   [] local_pci_probe+0x45/0xa0
   [] ? pci_match_device+0xf4/0x120
   [] pci_device_probe+0xca/0x110
   [] driver_probe_device+0x213/0x460
   [] __driver_attach+0x90/0xa0
   [] ? driver_probe_device+0x460/0x460
   [] bus_for_each_dev+0x5d/0x90
   [] driver_attach+0x1e/0x20
   [] bus_add_driver+0x1d0/0x290
   [] ? uncore_cpu_setup+0x12/0x12
   [] driver_register+0x60/0xe0
   [] __pci_register_driver+0x4c/0x50
   [] intel_uncore_init+0xe6/0x2fc
   [] ? uncore_cpu_setup+0x12/0x12
   [] do_one_initcall+0xcd/0x1f0
   [] ? parse_args+0x120/0x470
   [] ? __wake_up+0x48/0x60
   [] kernel_init_freeable+0x199/0x226
   [] ? initcall_blacklist+0xc0/0xc0
   [] ? rest_init+0x80/0x80
   [] kernel_init+0xe/0xe0
   [] ret_from_fork+0x3f/0x70
   [] ? rest_init+0x80/0x80
  ---[ end trace 5f5beae5b9d2dc45 ]---

  the issue is fixed in upstream kernels, via two patches:

  https://lkml.org/lkml/2015/12/11/165
  http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html

  each is a one-liner against the mch_quirk_devices[] structure.

  [nlb-glaptop](0) $ cat /proc/version_signature 
  Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  [nlb-glaptop](0) $ 

  [nlb-glaptop](0) $ lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  [nlb-glaptop](0) $ 

  [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily
  linux-generic-lts-wily:
Installed: 4.2.0.35.28
Candidate: 4.2.0.35.28
Version table:
   *** 4.2.0.35.28 0
  600 https://rapture-prod.corp.google.com/ 
goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 
Packages
  100 /var/lib/dpkg/status
  [nlb-glaptop](0) $

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

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


[Kernel-packages] [Bug 1577748] [NEW] OOPS on wily+ for Haswell-ULT and Broadwell

2016-05-03 Thread nick black
Public bug reported:

After upgrading to the wily 4.2 kernel, we see early OOPSes similar to
the following on Haswell-ULT and Broadwell processors:

[ cut here ]
WARNING: CPU: 1 PID: 1 at 
/build/linux-lts-wily-MVxxD8/linux-lts-wily-4.2.0/arch/x86/mm/ioremap.c:198 
__ioremap_caller+0x2a2/0x360()
Info: mapping multiple BARs. Your kernel is fine.
Modules linked in:
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.2.0-34-generic #39~14.04.1-Ubuntu
Hardware name: Hewlett-Packard HP EliteBook Folio 1040 G1/213E, BIOS L83 Ver. 
01.07 03/28/2014
 81a91c80 88023522bad8 817b5fed 0001
 88023522bb28 88023522bb18 8107799a c9cbe000
 c9cb8000 c9cb8000 6000 880230297040
Call Trace:
 [] dump_stack+0x45/0x57
 [] warn_slowpath_common+0x8a/0xc0
 [] warn_slowpath_fmt+0x46/0x50
 [] __ioremap_caller+0x2a2/0x360
 [] ioremap_nocache+0x17/0x20
 [] snb_uncore_imc_init_box+0x65/0x90
 [] uncore_pci_probe+0xd5/0x1c0
 [] local_pci_probe+0x45/0xa0
 [] ? pci_match_device+0xf4/0x120
 [] pci_device_probe+0xca/0x110
 [] driver_probe_device+0x213/0x460
 [] __driver_attach+0x90/0xa0
 [] ? driver_probe_device+0x460/0x460
 [] bus_for_each_dev+0x5d/0x90
 [] driver_attach+0x1e/0x20
 [] bus_add_driver+0x1d0/0x290
 [] ? uncore_cpu_setup+0x12/0x12
 [] driver_register+0x60/0xe0
 [] __pci_register_driver+0x4c/0x50
 [] intel_uncore_init+0xe6/0x2fc
 [] ? uncore_cpu_setup+0x12/0x12
 [] do_one_initcall+0xcd/0x1f0
 [] ? parse_args+0x120/0x470
 [] ? __wake_up+0x48/0x60
 [] kernel_init_freeable+0x199/0x226
 [] ? initcall_blacklist+0xc0/0xc0
 [] ? rest_init+0x80/0x80
 [] kernel_init+0xe/0xe0
 [] ret_from_fork+0x3f/0x70
 [] ? rest_init+0x80/0x80
---[ end trace 5f5beae5b9d2dc45 ]---

the issue is fixed in upstream kernels, via two patches:

https://lkml.org/lkml/2015/12/11/165
http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html

each is a one-liner against the mch_quirk_devices[] structure.

[nlb-glaptop](0) $ cat /proc/version_signature 
Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
[nlb-glaptop](0) $ 

[nlb-glaptop](0) $ lsb_release -rd
Description:Ubuntu 14.04 LTS
Release:14.04
[nlb-glaptop](0) $ 

[nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily
linux-generic-lts-wily:
  Installed: 4.2.0.35.28
  Candidate: 4.2.0.35.28
  Version table:
 *** 4.2.0.35.28 0
600 https://rapture-prod.corp.google.com/ 
goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 
Packages
100 /var/lib/dpkg/status
[nlb-glaptop](0) $

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


** Tags: trusty

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

Title:
  OOPS on wily+ for Haswell-ULT and Broadwell

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the wily 4.2 kernel, we see early OOPSes similar to
  the following on Haswell-ULT and Broadwell processors:

  [ cut here ]
  WARNING: CPU: 1 PID: 1 at 
/build/linux-lts-wily-MVxxD8/linux-lts-wily-4.2.0/arch/x86/mm/ioremap.c:198 
__ioremap_caller+0x2a2/0x360()
  Info: mapping multiple BARs. Your kernel is fine.
  Modules linked in:
  CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.2.0-34-generic #39~14.04.1-Ubuntu
  Hardware name: Hewlett-Packard HP EliteBook Folio 1040 G1/213E, BIOS L83 Ver. 
01.07 03/28/2014
   81a91c80 88023522bad8 817b5fed 0001
   88023522bb28 88023522bb18 8107799a c9cbe000
   c9cb8000 c9cb8000 6000 880230297040
  Call Trace:
   [] dump_stack+0x45/0x57
   [] warn_slowpath_common+0x8a/0xc0
   [] warn_slowpath_fmt+0x46/0x50
   [] __ioremap_caller+0x2a2/0x360
   [] ioremap_nocache+0x17/0x20
   [] snb_uncore_imc_init_box+0x65/0x90
   [] uncore_pci_probe+0xd5/0x1c0
   [] local_pci_probe+0x45/0xa0
   [] ? pci_match_device+0xf4/0x120
   [] pci_device_probe+0xca/0x110
   [] driver_probe_device+0x213/0x460
   [] __driver_attach+0x90/0xa0
   [] ? driver_probe_device+0x460/0x460
   [] bus_for_each_dev+0x5d/0x90
   [] driver_attach+0x1e/0x20
   [] bus_add_driver+0x1d0/0x290
   [] ? uncore_cpu_setup+0x12/0x12
   [] driver_register+0x60/0xe0
   [] __pci_register_driver+0x4c/0x50
   [] intel_uncore_init+0xe6/0x2fc
   [] ? uncore_cpu_setup+0x12/0x12
   [] do_one_initcall+0xcd/0x1f0
   [] ? parse_args+0x120/0x470
   [] ? __wake_up+0x48/0x60
   [] kernel_init_freeable+0x199/0x226
   [] ? initcall_blacklist+0xc0/0xc0
   [] ? rest_init+0x80/0x80
   [] kernel_init+0xe/0xe0
   [] ret_from_fork+0x3f/0x70
   [] ? rest_init+0x80/0x80
  ---[ end trace 5f5beae5b9d2dc45 ]---

  the issue is fixed in upstream kernels, via two patches:

  https://lkml.org/lkml/2015/12/11/165
  http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html

  each is a one-liner against the mch_quirk_devices[] s

[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

2016-05-03 Thread Stunts
Sorry about the noise, but is there any further info I can provide, or patches 
I can try?
This is a critical functionality for me.

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

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

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


[Kernel-packages] [Bug 1523088]

2016-05-03 Thread Prasad H L Bhat
Created attachment 123355
attachment-32584-0.html

Could someone please let me know how to apply this patchwork to mainstream
kernel source?

I tried on the latest 4.6-rc5 and it failed. It did work on
drm-intel-nightly though which is a not mainstream branch.

On 26 April 2016 at 07:45,  wrote:

> *Comment # 52  on
> bug 89055  from
> dwk...@gmail.com  *
>
> I can confirm that this works for me on SKL, i5-6200U dell xps 13 9350. There
> used to be a crash at every boot and two on suspend, with external HDMI 
> plugged
> in. I patched the drm-nightly kernel and compiled it manually.
>
> --
> You are receiving this mail because:
>
>- You are on the CC list for the bug.
>
>

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

Title:
  WARN_ON(!wm_changed) warning and stacktrace in kernel log

Status in X.Org X server:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I always get an warning and stacktrace (and it seems to hang a little
  bit). This occurs after reboot as well as when I move with the cursor
  between my hdmi monitor and my laptop. (This only occurs when HDMI is
  connected)

  Default Kubuntu install version 15.10 with kernel 4.2.0-19-generic
  Processor: i5 6300hq
  Graphics: gtx950m

  WARNING: CPU: 1 PID: 827 at 
/build/linux-26_gwp/linux-4.2.0/drivers/gpu/drm/i915/intel_pm.c:3404 
skl_update_other_pipe_wm+0x1de/0x1f0 [i915]()
  [Sam Dez  5 12:34:46 2015] WARN_ON(!wm_changed)
  [Sam Dez  5 12:34:46 2015] Modules linked in:
  [Sam Dez  5 12:34:46 2015]  nls_iso8859_1 pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) drbg ansi_cprng ctr ccm rfcomm bnep arc4 rtsx_usb_ms 
memstick i2c_designware_platform i2c_designware_core acer_wmi sparse_keymap 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core intel_rapl snd_hwdep iosf_mbi x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm snd_pcm snd_seq_midi snd_seq_midi_event 
snd_rawmidi snd_seq crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul snd_seq_device glue_helper snd_timer ablk_helper cryptd ath10k_pci 
ath10k_core snd ath mac80211 serio_raw soundcore idma64 virt_dma cfg80211 
joydev input_leds uvcvideo mei_me videobuf2_vmalloc videobuf2_memops mei 
videobuf2_core v4l2_common intel_lpss_pci videodev media
  [Sam Dez  5 12:34:46 2015]  btusb btrtl btbcm btintel bluetooth shpchp 
dell_smo8800 intel_lpss_acpi intel_lpss tpm_crb acpi_pad mac_hid parport_pc 
ppdev lp parport autofs4 hid_generic hid_logitech_hidpp hid_logitech_dj usbhid 
rtsx_usb_sdmmc rtsx_usb uas usb_storage nouveau i915 mxm_wmi ttm i2c_algo_bit 
drm_kms_helper r8169 mii drm ahci libahci i2c_hid hid wmi pinctrl_sunrisepoint 
video pinctrl_intel
  [Sam Dez  5 12:34:46 2015] CPU: 1 PID: 827 Comm: Xorg Tainted: GW  OE 
  4.2.0-19-generic #23-Ubuntu
  [Sam Dez  5 12:34:46 2015] Hardware name: Acer Aspire V5-591G/Usopp_SLS, BIOS 
V1.03 10/23/2015
  [Sam Dez  5 12:34:46 2015]   a287b8f0 
880071b03518 817e93f9
  [Sam Dez  5 12:34:46 2015]   880071b03570 
880071b03558 8107b3d6
  [Sam Dez  5 12:34:46 2015]  880071b03620 880071b036c4 
880279bf2000 880279bf7000
  [Sam Dez  5 12:34:46 2015] Call Trace:
  [Sam Dez  5 12:34:46 2015]  [] dump_stack+0x45/0x57
  [Sam Dez  5 12:34:46 2015]  [] 
warn_slowpath_common+0x86/0xc0
  [Sam Dez  5 12:34:46 2015]  [] warn_slowpath_fmt+0x55/0x70
  [Sam Dez  5 12:34:46 2015]  [] 
skl_update_other_pipe_wm+0x1de/0x1f0 [i915]
  [Sam Dez  5 12:34:46 2015]  [] skl_update_wm+0x1bb/0x740 
[i915]
  [Sam Dez  5 12:34:46 2015]  [] ? gen9_read32+0xf7/0x2d0 
[i915]
  [Sam Dez  5 12:34:46 2015]  [] ? 
i915_get_vblank_timestamp+0x62/0xa0 [i915]
  [Sam Dez  5 12:34:46 2015]  [] 
intel_update_watermarks+0x1e/0x30 [i915]
  [Sam Dez  5 12:34:46 2015]  [] 
intel_finish_crtc_commit+0x169/0x190 [i915]
  [Sam Dez  5 12:34:46 2015]  [] 
drm_atomic_helper_commit_planes_on_crtc+0x143/0x260 [drm_kms_helper]
  [Sam Dez  5 12:34:46 2015]  [] 
intel_atomic_commit+0x6b/0x100 [i915]
  [Sam Dez  5 12:34:46 2015]  [] drm_atomic_commit+0x37/0x60 
[drm]
  [Sam Dez  5 12:34:46 2015]  [] 
drm_atomic_helper_disable_plane+0xef/0x130 [drm_kms_helper]
  [Sam Dez  5 12:34:46 2015]  [] 
__setplane_internal+0x23a/0x2f0 [drm]
  [Sam Dez  5 12:34:46 2015]  [] 
drm_mode_cursor_universal+0x12b/0x210 [drm]
  [Sam Dez  5 12:34:46 2015]  [] ? __ww_mutex_lock+0x5f/0xa0
  [Sam Dez  5 12:34:46 2015]  [] 
drm_mode_cursor_common+0x81/0x180 [drm]
  [Sam Dez  5 12:34:46 2015]  [] 
drm_mode_cursor_ioctl+0x50/0x70 [drm]
  [Sam Dez  5 12:34:46 2015]  [] drm_ioctl+0x125/0x610 [drm]
  [Sam Dez  5 12:34:46 2015]  [] ? 
drm_mode_setcrtc+0x500/0x500 [drm]
  [Sam D

[Kernel-packages] [Bug 1523088]

2016-05-03 Thread Dwk128
Unfortunately, while this patch (against drm-nightly 4.6.0-rc5) did
eliminate the stack traces from my dmesg logs, it seems to have
*introduced* a freezing bug. Every six to twelve hours or so the system
freezes completely, audio stops, caps lock stops working (though it
doesn't blink as in a panic). I assume this is a deadlock of some sort
because there is no indication in any system logs that a freeze has
occurred.

I have been having many issues related to suspend, so I thought at first
this freeze was another manifestation of the same bug. But after
happening four or five times, it just happened last night after several
hours of being on without ever having been suspended. I can try the same
kernel unpatched but I have tried a similar version before and I suspect
the freeze is new.

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

Title:
  WARN_ON(!wm_changed) warning and stacktrace in kernel log

Status in X.Org X server:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I always get an warning and stacktrace (and it seems to hang a little
  bit). This occurs after reboot as well as when I move with the cursor
  between my hdmi monitor and my laptop. (This only occurs when HDMI is
  connected)

  Default Kubuntu install version 15.10 with kernel 4.2.0-19-generic
  Processor: i5 6300hq
  Graphics: gtx950m

  WARNING: CPU: 1 PID: 827 at 
/build/linux-26_gwp/linux-4.2.0/drivers/gpu/drm/i915/intel_pm.c:3404 
skl_update_other_pipe_wm+0x1de/0x1f0 [i915]()
  [Sam Dez  5 12:34:46 2015] WARN_ON(!wm_changed)
  [Sam Dez  5 12:34:46 2015] Modules linked in:
  [Sam Dez  5 12:34:46 2015]  nls_iso8859_1 pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) drbg ansi_cprng ctr ccm rfcomm bnep arc4 rtsx_usb_ms 
memstick i2c_designware_platform i2c_designware_core acer_wmi sparse_keymap 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core intel_rapl snd_hwdep iosf_mbi x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm snd_pcm snd_seq_midi snd_seq_midi_event 
snd_rawmidi snd_seq crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul snd_seq_device glue_helper snd_timer ablk_helper cryptd ath10k_pci 
ath10k_core snd ath mac80211 serio_raw soundcore idma64 virt_dma cfg80211 
joydev input_leds uvcvideo mei_me videobuf2_vmalloc videobuf2_memops mei 
videobuf2_core v4l2_common intel_lpss_pci videodev media
  [Sam Dez  5 12:34:46 2015]  btusb btrtl btbcm btintel bluetooth shpchp 
dell_smo8800 intel_lpss_acpi intel_lpss tpm_crb acpi_pad mac_hid parport_pc 
ppdev lp parport autofs4 hid_generic hid_logitech_hidpp hid_logitech_dj usbhid 
rtsx_usb_sdmmc rtsx_usb uas usb_storage nouveau i915 mxm_wmi ttm i2c_algo_bit 
drm_kms_helper r8169 mii drm ahci libahci i2c_hid hid wmi pinctrl_sunrisepoint 
video pinctrl_intel
  [Sam Dez  5 12:34:46 2015] CPU: 1 PID: 827 Comm: Xorg Tainted: GW  OE 
  4.2.0-19-generic #23-Ubuntu
  [Sam Dez  5 12:34:46 2015] Hardware name: Acer Aspire V5-591G/Usopp_SLS, BIOS 
V1.03 10/23/2015
  [Sam Dez  5 12:34:46 2015]   a287b8f0 
880071b03518 817e93f9
  [Sam Dez  5 12:34:46 2015]   880071b03570 
880071b03558 8107b3d6
  [Sam Dez  5 12:34:46 2015]  880071b03620 880071b036c4 
880279bf2000 880279bf7000
  [Sam Dez  5 12:34:46 2015] Call Trace:
  [Sam Dez  5 12:34:46 2015]  [] dump_stack+0x45/0x57
  [Sam Dez  5 12:34:46 2015]  [] 
warn_slowpath_common+0x86/0xc0
  [Sam Dez  5 12:34:46 2015]  [] warn_slowpath_fmt+0x55/0x70
  [Sam Dez  5 12:34:46 2015]  [] 
skl_update_other_pipe_wm+0x1de/0x1f0 [i915]
  [Sam Dez  5 12:34:46 2015]  [] skl_update_wm+0x1bb/0x740 
[i915]
  [Sam Dez  5 12:34:46 2015]  [] ? gen9_read32+0xf7/0x2d0 
[i915]
  [Sam Dez  5 12:34:46 2015]  [] ? 
i915_get_vblank_timestamp+0x62/0xa0 [i915]
  [Sam Dez  5 12:34:46 2015]  [] 
intel_update_watermarks+0x1e/0x30 [i915]
  [Sam Dez  5 12:34:46 2015]  [] 
intel_finish_crtc_commit+0x169/0x190 [i915]
  [Sam Dez  5 12:34:46 2015]  [] 
drm_atomic_helper_commit_planes_on_crtc+0x143/0x260 [drm_kms_helper]
  [Sam Dez  5 12:34:46 2015]  [] 
intel_atomic_commit+0x6b/0x100 [i915]
  [Sam Dez  5 12:34:46 2015]  [] drm_atomic_commit+0x37/0x60 
[drm]
  [Sam Dez  5 12:34:46 2015]  [] 
drm_atomic_helper_disable_plane+0xef/0x130 [drm_kms_helper]
  [Sam Dez  5 12:34:46 2015]  [] 
__setplane_internal+0x23a/0x2f0 [drm]
  [Sam Dez  5 12:34:46 2015]  [] 
drm_mode_cursor_universal+0x12b/0x210 [drm]
  [Sam Dez  5 12:34:46 2015]  [] ? __ww_mutex_lock+0x5f/0xa0
  [Sam Dez  5 12:34:46 2015]  [] 
drm_mode_cursor_common+0x81/0x180 [drm]
  [Sam Dez  5 12:34:46 2015]  [] 
drm_mode_cursor_ioctl+0x50/0x70 [drm]
  [Sam Dez  5 12:34:46 2015]  [] drm_ioctl+0x125/0x610 [drm]
  [Sam Dez  5 12:34:46 2015]  [] ? 
drm_mode_setcrtc+0x500/0x500 [drm]
  [Sam Dez  5 12:34:46 2015]  []

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

2016-05-03 Thread bugproxy
--- Comment From thorsten.di...@de.ibm.com 2016-05-03 07:28 EDT---
On an LPAR with 8458 (!!) ccw devices (only 11 of them in use) I set 
crashkernel with various values:
256M : no dump created
288M : oom killer killed some processes, dump was created, but system did not 
come up
320M : no oom killer, dump properly created
Then I invoked cio_ignore -u -k and added these values to KDUMP_CMD_APPEND in 
/etc/default/kdump_tools. Kdump worked fine, even with crashkernel=128M

IMO the best thing is to set this dynamically in /etc/default/kdump_tools by 
the following suggested patch:
--- /etc/default/kdump-tools.orig   2016-04-21 15:11:57.0 +0200
+++ /etc/default/kdump-tools2016-05-03 13:17:38.862816261 +0200
@@ -63,7 +63,8 @@
# for the kdump kernel.  If unset, it defaults to "irqpoll maxcpus=1 nousb"
#KDUMP_KEXEC_ARGS=""
#KDUMP_CMDLINE=""
-#KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"
+APPEND=
+KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
$APPEND"

# ---
# Architecture specific Overrides:

The cmdline during kdump is set properly, the values from cio_ignore are
reflected.

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

Title:
  makekdump should re-exec with cio_ignore on s390x

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Confirmed

Bug description:
  As per
  
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/comments/19

  We should re-exec with cio_ignore lines. As per report there, it
  should result in lowered required crashdump setting.

  Hypothetically, one should be able to test this imperially by lowering
  crashdump memory settings until kdump does not succeed anymore. And
  then generated and append `cio_ignore -k -u` to the
  KDUMP_CMDLINE_APPEND= and see that kdump starts working again with a
  lower memory usage.

  Once this is developed / verified / tested, we should probably SRU
  this back to xenial.

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

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


[Kernel-packages] [Bug 1574690] Re: linux: 4.4.0-22.38 -proposed tracker

2016-05-03 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

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

Title:
  linux: 4.4.0-22.38 -proposed tracker

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

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

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1571853] Re: linux: 3.2.0-102.142 -proposed tracker

2016-05-03 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

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

Title:
  linux: 3.2.0-102.142 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 18. April 2016 21:40 UTC
  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1574690] Re: linux: 4.4.0-22.38 -proposed tracker

2016-05-03 Thread Luis Henriques
All tests seem to be passing now.

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

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

Title:
  linux: 4.4.0-22.38 -proposed tracker

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

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

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1557924] Re: Machine fails to resume from suspend

2016-05-03 Thread Torsten Bronger
How can one install Linux 4.4.5 on Xenial?  It is not on
  Or can I use
?

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

Title:
  Machine fails to resume from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My machine (HP zbook 14 G2, http://store.hp.com/us/en/pdp/business-
  solutions/hp-zbook-14-g2-mobile-workstation-%28energy-star%29) fails
  to resume from suspend since kernel version 4.4.0-12. Version 4.4.0-10
  still works fine (I don't know about *-11).

  Below are the last log messages before machine suspended:

  Mär 14 20:54:23 moebius wpa_supplicant[888]: p2p-dev-wlo1: 
CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
  Mär 14 20:54:23 moebius dbus[699]: [system] Rejected send message, 10 matched 
rules; type="method_return", sender=":1.92" (uid=0 pid=1533 
comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") i
  Mär 14 20:54:23 moebius NetworkManager[623]:  NetworkManager state is 
now ASLEEP
  Mär 14 20:54:23 moebius whoopsie[649]: [20:54:23] Cannot reach: 
https://daisy.ubuntu.com
  Mär 14 20:54:23 moebius wpa_supplicant[888]: nl80211: deinit 
ifname=p2p-dev-wlo1 disabled_11b_rates=0
  Mär 14 20:54:23 moebius NetworkManager[623]:  Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Mär 14 20:54:23 moebius dbus[699]: [system] Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service'
  Mär 14 20:54:23 moebius systemd[1]: Reached target Sleep.
  Mär 14 20:54:23 moebius systemd[1]: Starting Suspend...
  Mär 14 20:54:23 moebius systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Mär 14 20:54:23 moebius dbus[699]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
  Mär 14 20:54:23 moebius systemd[1]: Started Network Manager Script Dispatcher 
Service.
  Mär 14 20:54:23 moebius nm-dispatcher[1910]: Dispatching action 'down' for 
wlo1
  Mär 14 20:54:23 moebius wpa_supplicant[888]: nl80211: deinit ifname=wlo1 
disabled_11b_rates=0
  Mär 14 20:54:25 moebius bluetoothd[655]: Endpoint unregistered: sender=:1.56 
path=/MediaEndpoint/A2DPSource
  Mär 14 20:54:25 moebius bluetoothd[655]: Endpoint unregistered: sender=:1.56 
path=/MediaEndpoint/A2DPSink
  Mär 14 20:54:27 moebius org.gnome.zeitgeist.Engine[1243]: ** 
(zeitgeist-datahub:1958): WARNING **: zeitgeist-datahub.vala:229: Unable to get 
name "org.gnome.zeitgeist.datahub" on the bus!
  Mär 14 20:54:27 moebius gnome-session[1359]: ** (zeitgeist-datahub:1936): 
WARNING **: kde-recent-document-provider.vala:174: Couldn't find actor for 
'okular'.
  Mär 14 20:54:33 moebius systemd-sleep[1908]: Selected interface 'wlo1'
  Mär 14 20:54:33 moebius systemd-sleep[1908]: 'SUSPEND' command timed out.
  Mär 14 20:54:33 moebius systemd-sleep[1912]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Mär 14 20:54:33 moebius systemd-sleep[1908]: Suspending system...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johnny 1401 F pulseaudio
   /dev/snd/controlC1:  johnny 1401 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar 16 08:27:16 2016
  HibernationDevice: RESUME=UUID=d987a311-b37d-44cf-9888-57b93b40cf51
  InstallationDate: Installed on 2016-03-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: Hewlett-Packard HP ZBook 14 G2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic.efi.signed 
root=UUID=2b4e0fd5-152d-4456-8fce-fa2e8b77cebb ro quiet splash net.ifnames=0 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-12-generic N/A
   linux-backports-modules-4.4.0-12-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M71 Ver. 01.13
  dmi.board.name: 2216
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.58
  dmi.chassis.asset.tag: 5CG54335T5
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM71Ver.01.13:bd01/18/2016:svnHewlett-Packard:pnHPZBook14G2:pvrA3008C510003:rvnHewlett-Packard:rn2216:rvrKBCVersion96.58:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 14 G2
  dmi.product.version: A3008C510003
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about th

[Kernel-packages] [Bug 1479136] Re: [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards

2016-05-03 Thread Mrerexx
thom,  VGA output is better. There is some flickering (no white lines,
though) but my D-Sub cable is cheap.

AFAIK, HP has disabled ATI PowerPlay in models with Athlon or Sempron
CPUs. Maybe that's the culprit.

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

Title:
  [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu-Mate 14.04.2

  This is what I get if I run a kernel newer than 3.13: 
https://www.youtube.com/watch?v=nx2-Fvihzxg
  sorry for the link, I just don't know how to describe these artefacts 
verbally.
  (a storm of small horizontal moving blips from right to left ??)

  Those artefacts appear as soon as new kernel is selected in GRUB, and
  remain during the whole session.

  The lastest kernel (from the main repository that is) working without
  artifacts is v3.13.0.59. All later kernels have artifacts. All later
  kernels also are either "-utopic" or "-vivid" instead of "-trusty",
  but I do not know if it is related.

  
  GPU: Mobility Radeon HD 3200 (RS780M)
  System: Ubuntu Mate 14.04.2  32-bit

  Kernels tested: 3.13.0.59 (and earlier) , 3.16.0.45 , 3.19.0.25 
  Only  3.13.0.59 (and earlier) are without problems.

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

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


[Kernel-packages] [Bug 1571853] Re: linux: 3.2.0-102.142 -proposed tracker

2016-05-03 Thread Luis Henriques
There was a networking issue while running i386 dahdi dmks.  Re-run and
it passed.

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

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

Title:
  linux: 3.2.0-102.142 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 18. April 2016 21:40 UTC
  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang

2016-05-03 Thread Timo Aaltonen
sounds like kernel 4.4.0-22.38 will fix this on 16.04, as it has merged
4.4.8

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

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

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

Title:
  Plugging HDMI screen in causes system hang

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  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 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  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.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

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

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


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

2016-05-03 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/1577702

Title:
  Lenovo Y510p Backlight control not changing backlight

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Potentially the same bug as #1258058 however it was closed due to
  inactivity

  the backlight controls worked fine under Kubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aj 2104 F pulseaudio
   /dev/snd/controlC0:  aj 2104 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May  3 02:41:42 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5a28597e-d4c1-4c0f-aae4-1c674f67e436
  InstallationDate: Installed on 2016-05-03 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: LENOVO 20217
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: \vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=f78854ef-3876-45cd-90c6-d67a77af7a32 ro rootflags=subvol=@ quiet 
splash vt.handoff=7 initrd=\initrd.img-4.4.0-21-generic
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 1/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN47WW(V3.08)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN47WW(V3.08):bd1/30/2015:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1559308] [NEW] Plugging HDMI screen in causes system hang

2016-05-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
using 4.4.0-13-generic and the Nouveau drivers.

If I plug in an external HDMI monitor (FHD) either into either HDMI port
(there's one on the machine and there's one available via a usb 3.1
extra adaptor) then the whole system hangs, completely unresponsive and
needing a hard reboot. Before hanging the 2nd display gets an image as
expected, but the laptop's screen flashes randomly, sometimes you see
weird artifacts. Then the hang comes.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Mar 18 20:43:42 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 
[VGA controller])
   Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
   Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
InstallationDate: Installed on 2016-03-15 (3 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
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 0c45:6713 Microdia 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9550
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
SourcePackage: xorg
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.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Mar 18 17:28:07 2016
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 Unknown chipset: NV117
 SynPS/2 Synaptics TouchPad: Read error 19
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5182 
 vendor SHP
xserver.version: 2:1.18.1-1ubuntu4

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Committed


** Tags: amd64 apport-bug ubuntu xenial
-- 
Plugging HDMI screen in causes system hang
https://bugs.launchpad.net/bugs/1559308
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash

2016-05-03 Thread Grzegorz Bartman
Just checked with Ubuntu 16.04 and Dell XPS 15 9530  - still same
problem.

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

Title:
  14e4:4365 bcmwl-kernel source: fix for null pointer crash

Status in Dell Sputnik:
  Confirmed
Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Precise:
  Fix Committed
Status in bcmwl source package in Trusty:
  Fix Committed
Status in bcmwl source package in Vivid:
  Fix Committed
Status in bcmwl source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * bcmwl does not compile on new kernels (or HWE kernels)
   * bcmwl suffers from null reference bug 

  [Test Case]

   * public PPA provided to community and feedback
   * based on patch available to other distros
   * comment #42

  [Regression Potential]

   * for changes on kernel support it may not compile (tested with 3.2, 3.13, 
3.18 and 4.2)
   * for the null reference change -> proved to fix problem for community based 
on feedback

  [Other Info]

  Original bug description:

  The bcmwl package as of now misses one patch for a bug that occurs
  with BCM43142 and possibly other broadcom chipsets that will look like
  random disconnects, poor wifi signal and kernel warnings, See also
  #1379524.

  Adding the patch is a fairly simple process:

  * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches
  * add the following line to  /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf
  PATCH[7]="0014-null-pointer-crash.patch"
  * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom 
/usr/share/bcmwl x86_64 $(uname -r)

  This has fixed the issue for me. Edit: I just wanted to add that I did
  not write the patch; I merely downloaded it from a paste that was
  linked from the respective AUR package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: 
usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf]
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Jan 29 13:15:17 2015
  InstallationDate: Installed on 2015-01-26 (3 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions

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


[Kernel-packages] [Bug 1577702] [NEW] Lenovo Y510p Backlight control not changing backlight

2016-05-03 Thread AJ Fite
Public bug reported:

Potentially the same bug as #1258058 however it was closed due to
inactivity

the backlight controls worked fine under Kubuntu

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  aj 2104 F pulseaudio
 /dev/snd/controlC0:  aj 2104 F pulseaudio
CurrentDesktop: GNOME
Date: Tue May  3 02:41:42 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=5a28597e-d4c1-4c0f-aae4-1c674f67e436
InstallationDate: Installed on 2016-05-03 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
MachineType: LENOVO 20217
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: \vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=f78854ef-3876-45cd-90c6-d67a77af7a32 ro rootflags=subvol=@ quiet 
splash vt.handoff=7 initrd=\initrd.img-4.4.0-21-generic
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic  N/A
 linux-firmware1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 1/30/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN47WW(V3.08)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias: 
dmi:bvnLENOVO:bvr74CN47WW(V3.08):bd1/30/2015:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.name: 20217
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug xenial

** Description changed:

- Potentially the same bug as 1258058
+ Potentially the same bug as #1258058 however it was closed due to
+ inactivity
  
  the backlight controls worked fine under Kubuntu
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  aj 2104 F pulseaudio
-  /dev/snd/controlC0:  aj 2104 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  aj 2104 F pulseaudio
+  /dev/snd/controlC0:  aj 2104 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May  3 02:41:42 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5a28597e-d4c1-4c0f-aae4-1c674f67e436
  InstallationDate: Installed on 2016-05-03 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: LENOVO 20217
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: \vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=f78854ef-3876-45cd-90c6-d67a77af7a32 ro rootflags=subvol=@ quiet 
splash vt.handoff=7 initrd=\initrd.img-4.4.0-21-generic
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-21-generic N/A
-  linux-backports-modules-4.4.0-21-generic  N/A
-  linux-firmware1.157
+  linux-restricted-modules-4.4.0-21-generic N/A
+  linux-backports-modules-4.4.0-21-generic  N/A
+  linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 1/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN47WW(V3.08)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN47WW(V3.08):bd1/30/2015:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun

[Kernel-packages] [Bug 1571416] Re: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC)

2016-05-03 Thread Bug Watch Updater
Launchpad has imported 12 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=95017.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-04-19T11:28:15+00:00 Mathieu Malaterre wrote:

I am installing a Debian Jessie on a Mac Mini PowerPC G4 system.

After a couple of seconds of using the system, it generally freeze,
looking at dmesg from another ssh connection I can see:

[   21.314765] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   21.459715] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[   21.531076] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   23.719199] gem 0002:20:0f.0 eth0: Link is up at 100 Mbps, full-duplex
[   23.719318] gem 0002:20:0f.0 eth0: Pause is disabled
[   23.719357] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  180.631048] radeon :00:10.0: ring 0 stalled for more than 16096msec
[  180.631062] radeon :00:10.0: GPU lockup (waiting for
0x031b last fence id 0x0301 on ring 0)
[  180.768184] radeon: wait for empty RBBM fifo failed ! Bad things
might happen.
[  180.905284] Failed to wait GUI idle while programming pipes. Bad
things might happen.
[  180.908156] radeon :00:10.0: Saved 827 dwords of commands on ring 0.
[  180.908176] radeon :00:10.0: (r100_asic_reset:2551)
RBBM_STATUS=0x8002C139
[  181.405690] radeon :00:10.0: (r100_asic_reset:2572)
RBBM_STATUS=0x8002C139
[  181.899237] radeon :00:10.0: (r100_asic_reset:2580)
RBBM_STATUS=0x8002C139
[  181.899264] radeon :00:10.0: GPU reset succeed
[  181.899269] radeon :00:10.0: GPU reset succeeded, trying to resume
[  181.899281] radeon :00:10.0: (r100_asic_reset:2551)
RBBM_STATUS=0x8002C139
[  182.396784] radeon :00:10.0: (r100_asic_reset:2572)
RBBM_STATUS=0x8002C139
[  182.890328] radeon :00:10.0: (r100_asic_reset:2580)
RBBM_STATUS=0x8002C139
[  182.890351] radeon :00:10.0: GPU reset succeed
[  182.890376] radeon :00:10.0: WB disabled
[  182.890384] radeon :00:10.0: fence driver on ring 0 use gpu
addr 0x and cpu addr 0xe2819000
[  183.027494] radeon: wait for empty RBBM fifo failed ! Bad things
might happen.
[  183.164599] Failed to wait GUI idle while programming pipes. Bad
things might happen.
[  183.164643] [drm] radeon: ring at 0x1000
[  183.171448] [drm] ring test succeeded in 0 usecs
[  193.171046] radeon :00:10.0: ring 0 stalled for more than 1msec
[  193.171061] radeon :00:10.0: GPU lockup (waiting for
0x031c last fence id 0x0301 on ring 0)
[  193.171068] [drm:r100_ib_test] *ERROR* radeon: fence wait failed (-35).
[  193.171079] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed
testing IB on GFX ring (-35).
[  193.171084] radeon :00:10.0: ib ring test failed (-35).
[  193.308210] radeon: wait for empty RBBM fifo failed ! Bad things
might happen.
[  193.445310] Failed to wait GUI idle while programming pipes. Bad
things might happen.
[  193.446307] radeon :00:10.0: (r100_asic_reset:2551)
RBBM_STATUS=0x8002C136
[  193.943817] radeon :00:10.0: (r100_asic_reset:2572)
RBBM_STATUS=0x8002C136
[  194.437363] radeon :00:10.0: (r100_asic_reset:2580)
RBBM_STATUS=0x8002C136
[  194.437390] radeon :00:10.0: GPU reset succeed
[  194.437395] radeon :00:10.0: GPU reset succeeded, trying to resume
[  194.437407] radeon :00:10.0: (r100_asic_reset:2551)
RBBM_STATUS=0x8002C136
[  194.934911] radeon :00:10.0: (r100_asic_reset:2572)
RBBM_STATUS=0x8002C136
[  195.428455] radeon :00:10.0: (r100_asic_reset:2580)
RBBM_STATUS=0x8002C136
[  195.428476] radeon :00:10.0: GPU reset succeed
[  195.428501] radeon :00:10.0: WB disabled
[  195.428509] radeon :00:10.0: fence driver on ring 0 use gpu
addr 0x and cpu addr 0xe2819000
[  195.565605] radeon: wait for empty RBBM fifo failed ! Bad things
might happen.
[  195.702705] Failed to wait GUI idle while programming pipes. Bad
things might happen.
[  195.702749] [drm] radeon: ring at 0x1000
[  195.710956] [drm] ring test succeeded in 0 usecs
[  205.707048] radeon :00:10.0: ring 0 stalled for more than 1msec
[  205.707063] radeon :00:10.0: GPU lockup (waiting for
0x031d last fence id 0x0301 on ring 0)
[  205.707070] [drm:r100_ib_test] *ERROR* radeon: fence wait failed (-35).
[  205.707081] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed
testing IB on GFX ring (-35).
[  205.707086] radeon :00:10.0: ib ring test failed (-35).
[  205.758647] radeon :00:10.0: GPU reset failed

Using

# apt-cache policy xserver-xorg-video-r128
xserver-xorg-video-r128:
  Installé : 6.9.2-1+b2
  Candidat : 6.9.2-1+b2
 Table de version :
 *** 6.9.2-1+b2 0
5

[Kernel-packages] [Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

2016-05-03 Thread Rasmus Larsen
I get the same issue with the build, which seemed weird so I retested and it 
looks like I must have mislabeled one of my builds, because now when I build 
31c2013e4ea2e594522980acc3d20e88664b19f1, I still get the issue, but if I go 
back to a6ebb4464659d35e0516900a8493f9720dd77d67 it works.
Somehow I must have swapped some builds...

a6ebb4464659d35e0516900a8493f9720dd77d67 Good
31c2013e4ea2e594522980acc3d20e88664b19f1   Bad
8ae10f463b7ae3455e9d0507176349c76580995f   Bad

Really sorry about the detour Joseph.

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

Bug description:
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 
5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 
UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8ea401db-b84b-4cd6-a628-d72f30bbf1e5 ro console=tty1 console=ttyS0
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Centaur CentaurHauls
  [0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
  [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point 
registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
  [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 
bytes, using 'standard' format.
  [0.00] x86/fpu: Using 'eager' FPU context switches.
  [0.00] e820: BIOS-provided physical RAM map:
  [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
  [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved
  [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
  [0.00] BIOS-e820: [mem 0x0010-0xefff] usable
  [0.00] BIOS-e820: [mem 0xfc00-0x] reserved
  [0.00] BIOS-e820: [mem 0x0001-0x0001efff] usable
  [0.00] NX (Execute Disable) protection: active
  [0.00] SMBIOS 2.4 present.
  [0.00] Hypervisor detected: Xen
  [0.00] Xen version 4.2.
  [0.00] Netfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated NICs.
  [0.00] Blkfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated disks.
  [0.00] You might have to change the root device
  [0.00] from /dev/hd[a-d] to /dev/xvd[a-d]
  [0.00] in your root= kernel command line option
  [0.00] e820: last_pfn = 0x1f max_arch_pfn = 0x4
  [0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
  [0.00] e820: last_pfn = 0xf max_arch_pfn = 0x4
  [0.00] found SMP MP-table at [mem 0x000fbba0-0x000fbbaf] mapped at 
[880fbba0]
  [0.00] Scanning 1 areas for low memory corruption
  [0.00] RAMDISK: [mem 0x3407e000-0x36036fff]
  [0.00] ACPI: Early table checksum verification disabled
  [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen   )
  [0.00] ACPI: XSDT 0xFC00F5A0 54 (v01 XenHVM  
 HVML )
  [0.00] ACPI: FACP 0xFC00F260 F4 (v04 XenHVM  
 HVML )
  [0.00] ACPI: DSDT 0xFC0035E0 00BBF6 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: FACS 0xFC0035A0 40
  [0.00] ACPI: FACS 0xFC0035A0 40
  [0.00] ACPI: APIC 0xFC00F360 D8 (v02 XenHVM  
 HVML )
  [0.00] ACPI: HPET 0xFC00F4B0 38 (v01 XenHVM  
 HVML )
  [0.00] ACPI: WAET 0xFC00F4F0 28 (v01 XenHVM  
 HVML )
  [0.00] ACPI: SSDT 0xFC00F520 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: SSDT 0xFC00F560 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] No NUMA configuration found
  [0.00] Faking a node at [mem 0x-0x0001efff]
  [0.00] NODE_DATA(0) allocated [mem 0x1efff7000-0x1efffbfff]
  [0.00] Zone ranges:
  [0.00]   DMA  [mem 0x1000-0x00ff]
  [0.00]   DMA32[mem 0x0100-0x]
  [0.00]  

[Kernel-packages] [Bug 1574622] Re: RTL8723AU No WiFi after reboot

2016-05-03 Thread Leonard Broman
I'm having similar problems. In 15.10 wifi worked just fine, but after
upgrade to 16.04 it does not work at all. I have the same messages in
dmesg.

[3.487325] usb 2-1.7: Vendor: Realtek
[3.487330] usb 2-1.7: Product: 802.11n WLAN Adapter
[3.487335] usb 2-1.7: RTL8723AU rev B (TSMC) 1T1R, TX queues 2, WiFi=1, 
BT=1, GPS=0, HI PA=0
[3.487338] usb 2-1.7: RTL8723AU MAC: 24:fd:52:8f:1a:52
[3.487341] usb 2-1.7: rtl8xxxu: Loading firmware 
rtlwifi/rtl8723aufw_B_NoBT.bin
[3.491456] usb 2-1.7: Firmware revision 31.0 (signature 0x2302)
[3.826305] usb 2-1.7: Firmware failed to start
[3.832910] usbcore: registered new interface driver rtl8xxxu
[3.845035] r8723au: module is from the staging directory, the quality is 
unknown, you have been warned.
[3.846925] usbcore: registered new interface driver rtl8723au

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

Title:
  RTL8723AU No WiFi after reboot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting the system, the wifi is not initialized correctly.
  dmesg lists [   14.132275] usb 2-5: Firmware failed to start

  However, after complete shutdown and startup the chip works just fine.

  I was using 14.04 before and this chip has always been kind of dodgy,
  requiring a kernel module from github for some time.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  enbewe 1685 F pulseaudio
   /dev/snd/controlC1:  enbewe 1685 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 25 14:34:09 2016
  HibernationDevice: RESUME=UUID=ca32a7cb-a574-4faf-9376-ab44bae3ac42
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20246
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=dbed3725-2e1c-4a74-8594-6fd4cdb20e21 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  StagingDrivers: r8723au
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8FCN36WW(V1.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Yoga 11S
  dmi.modalias: 
dmi:bvnLENOVO:bvr8FCN36WW(V1.03):bd10/08/2013:svnLENOVO:pn20246:pvrLenovoIdeaPadYoga11S:rvnLENOVO:rnYoga2:rvr3193STD:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga11S:
  dmi.product.name: 20246
  dmi.product.version: Lenovo IdeaPad Yoga 11S
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1571416] Re: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC)

2016-05-03 Thread ernsteiswuerfel
** Bug watch added: freedesktop.org Bugzilla #95017
   https://bugs.freedesktop.org/show_bug.cgi?id=95017

** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=95017
   Importance: Unknown
   Status: Unknown

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

Title:
  System freezes shortly after reaching the desktop (Ubuntu MATE 16.04,
  PowerPC)

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

Bug description:
  The freeze happens every time unless I use "radeon.agpmode=-1" as a
  kernel parameter.

  Affected machines:
  PowerBook G4 5,6 + PowerMac G5 7,3 (w. "ATI Radeon 9600 AP (AGP)".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-powerpc-smp 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-powerpc-smp 4.4.6
  Uname: Linux 4.4.0-18-powerpc-smp ppc
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.373
  CurrentDesktop: MATE
  Date: Sun Apr 17 21:08:40 2016
  IwConfig:
   lono wireless extensions.

   enP2p36s15f0  no wireless extensions.
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160417.1)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: ro ramdisk_size=1048576 file=/cdrom/preseed/username.seed 
boot=casper quiet --- radeon.agpmode=-1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-powerpc-smp N/A
   linux-backports-modules-4.4.0-18-powerpc-smp  N/A
   linux-firmware1.157
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1577288] Re: HDMI audio playback noise observed on AMD Polaris 10/11 GPU

2016-05-03 Thread maruthi
changed the status to 'Confirmed'

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

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

Title:
  HDMI audio playback noise  observed on AMD Polaris 10/11 GPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce :

  1. Install Ubuntu 16.04 and make sure AMDGPU driver is loaded for Polaris 
10/11 GPUs.
  1.Connect  the audio capable monitor via HDMI or DP.
  2.Install vlc player
  3.Select HDMI as default audio endpoint
  4.Play any audio file using vlc

   Expected:
  Audio should be played smoothly

  Actually:
  Along with audio play-back noise output was observed

  FIX:  The fix is submitted to upstream. The  commit hash 
#8eb22214b7cb0c0a28be6caf3b81201629d8ea7c is in torvalds master branch tree :
  https://github.com/torvalds/linux/commits/master/sound/pci/hda/hda_intel.c

  Please pick this commit. The commit was also sent to stable kernel
  release.

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

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