date:20160607

[Kernel-packages] [Bug 1582756] Re: Bluetooth Option not found

2016-06-07 Thread Christopher M. Penalver

kaptme, in order to allow additional upstream developers to examine the issue, 
at your earliest convenience, could you please test the latest upstream kernel 
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please 
keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

Once testing of the latest upstream kernel is complete, please mark this
report Status Confirmed. Please let us know your results.

Thank you for your understanding.

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

Title:
  Bluetooth Option not found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel-bug-exists-upstream

  
  After installing Ubuntu16.04 i cannot find my bluetooth. When i type 
bluetooth and click on search tab, its all greyed out. Can someone help me?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  suresh 1644 F pulseaudio
   /dev/snd/controlC0:  suresh 1644 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 17 16:24:00 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=bf3cfb89-85e2-4c0f-aef8-673d9fec256c
  InstallationDate: Installed on 2016-05-17 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 350 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=71b1d57d-246d-47a1-9bd5-bc12ca92cde8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/12/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 21B8
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 46.0B
  dmi.chassis.asset.tag: 5CG4382PDH
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd06/12/2014:svnHewlett-Packard:pnHP350G1:pvr099810167:rvnHewlett-Packard:rn21B8:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 350 G1
  dmi.product.version: 099810167
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1425699] Re: kernel panic on IBM Power8 PPC MAAS ephemeral image

2016-06-07 Thread Stefan Bader

I will not change the status of this bug because I can not reliably rule out 
that the initial issue still exists. That was reported to happen not all the 
times and from the stack trace involved some locking issue in the pci scsi 
adapter's driver.
Since comment #9, however, the reported stack trace is showing a completely 
different issue. This happened to be a regression since 3.13.0-46 and in order 
to cleanly separate the problems I opened LP: #1589910 to track the fix for 
that. As soon as that is there should be no need to enforce a HWE kernel for 
commissioning and/or provisioning of ppc64el hosts.

Should the initially reported problem persist then, please report back
here so we can try to fix that, too. Note that the stack trace should
involve the IPR adapter in some way. Like:

[   14.995435] ipr: IBM Power RAID SCSI Device Driver version: 2.6.0 (November 
16, 2012)
[   14.995630] ipr 0001:04:00.0: Found IOA with IRQ: 0
[   14.995828] ipr 0001:04:00.0: Using 64-bit DMA iommu bypass
[   14.996992] pnv_pci_dump_phb_diag_data: Unrecognized ioType 33554432
[   14.997063] EEH: Frozen PE#5 detected on PHB#1
[   14.997124] CPU: 11 PID: 911 Comm: systemd-udevd Not tainted 
3.13.0-27-generic #50-Ubuntu
[   14.997207] Call Trace:
[   14.997242] [c00fe325af70] [c0016af0] .show_stack+0x170/0x290 
(unreliable)
[   14.997340] [c00fe325b060] [c0966fc0] .dump_stack+0x88/0xb4
[   14.997427] [c00fe325b0e0] [c00364b0] 
.eeh_dev_check_failure+0x430/0x480
[   14.997526] [c00fe325b190] [c0036584] 
.eeh_check_failure+0x84/0xe0
[   14.997630] [c00fe325b220] [def233e0] 
.ipr_mask_and_clear_interrupts+0x190/0x1d0 [ipr]
[   14.997747] [c00fe325b2d0] [def2a394] 
.ipr_probe_ioa+0xc24/0x1370 [ipr]
[   14.997857] [c00fe325b400] [def325c4] .ipr_probe+0x44/0x4c0 [ipr]

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

Title:
  kernel panic on IBM Power8 PPC MAAS ephemeral image

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

Bug description:
  The kernel running on the 14.04 ephemeral image for MAAS when
  commissioning an IBM Power8 PPC server causes a periodic kernel panic.

  This happens intermittently and cannot be forcefully reproduced.

  The kernel version on the image is 3.13.0-27.50-generic according to
  the boot process.

  Attached is the boot process log with the kernel panics.

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

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

[Kernel-packages] [Bug 1577516] Re: WiFi disconnects suddenly automatic with reason=4 locally_generated=1

2016-06-07 Thread Christopher M. Penalver

Ettore Atalan, could you please provide the full computer model (ex.
NP300E7A-A02UK) as noted on the sticker of the computer itself (not from
the Bug Description)?

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

Title:
  WiFi disconnects suddenly automatic with reason=4 locally_generated=1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm experiencing suddenly automatic WiFi disconnects after upgrading
  to Ubuntu 16.04. Syslog reports "reason=4 locally_generated=1". Ubuntu
  15.10 didn't show this problem.

  Regards,
  Atalanttore
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ben2016 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2e2e5512-9f35-4996-9c32-4ee11f0ed624
  InstallationDate: Installed on 2012-05-05 (1457 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4A/300E5A/300E7A/3430EA/3530EA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=484a35a0-ae5f-45d9-afa1-982bbb6ef909 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lp lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 09QA
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 300E4A/300E5A/300E7A/3430EA/3530EA
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr09QA:bd11/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4A/300E5A/300E7A/3430EA/3530EA:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300E4A/300E5A/300E7A/3430EA/3530EA:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 300E4A/300E5A/300E7A/3430EA/3530EA
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1588467] Re: Mount USB3 KEY of 64 Go

2016-06-07 Thread Christopher M. Penalver

Bougron, in order to allow additional upstream developers to examine the issue, 
at your earliest convenience, could you please test the latest upstream kernel 
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please 
keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

Once testing of the latest upstream kernel is complete, please mark this
report Status Confirmed. Please let us know your results.

Thank you for your understanding.

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

Title:
  Mount USB3 KEY of 64 Go

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  New question #293348 on Ubuntu:
  https://answers.launchpad.net/ubuntu/+question/293348

  Bonjour. / Hello.

  Je  peux utiliser ma clé USB3 sur un port USB3 avec windows mais pas avec 
ubuntu 16.04 sauf à y mettre un prolongateur usb2.
  I use my “USB3-key on a USB3 port with Windows but not with ubuntu 16.04 
except to put a USB2 extender.

  u1604btrfs@u1604btrfs:~$ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
  u1604btrfs@u1604btrfs:~$

  La clé USB3 de 64 GO connectée directement à un port USB3 n’a aucun problème 
avec windows10 avec un débit moyen de 42 MB/s.
  The USB3 64GB connected directly to a USB3 port was no problem with Windows 
10 with an average throughput of 42 MB / s.

  La clé USB3 de 64 GO connectée via un càble USB de prolongation  (20 cm)  à 
un port USB3 fonctionne avec un débit moyen de 26 MB/s avec ubuntu.
  The USB3 64GB connected via an extension USB cable (20 cm) to a USB3 port 
works with an average throughput of 26 MB / s with ubuntu.

  Un disque USB3 connecté à ce même port USB3 fonctionne avec un débit moyen de 
106 MB/s avec ubuntu,
  A USB3 drive connected to the same USB3 port works with an average throughput 
of 106 MB / s with ubuntu.

  La clé USB3 de 64 GO connectée directement à un port USB3 ne se monte pas  
avec ubuntu, Je pense à un problème logiciel. Merci de votre avis.
  The USB 3 64GB connected directly to a USB3 port does not go up with ubuntu. 
I think to a software problem, Thanks for your review,

  Trace DMESG du branchement direct.
  Trace DMESG direct connection.
  [15027.934173] usb 3-1: USB disconnect, device number 3
  [15113.908384] usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
  [15113.949359] usb 4-1: New USB device found, idVendor=0951, idProduct=1666
  [15113.949370] usb 4-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [15113.949377] usb 4-1: Product: DataTraveler 3.0
  [15113.949387] usb 4-1: Manufacturer: Kingston
  [15113.949395] usb 4-1: SerialNumber: 60A44C426697FE50C98100E8
  [15118.948235] usb 4-1: Set SEL for device-initiated U2 failed.
  [15118.951961] usb 4-1: Disable of device-initiated U1 failed.
  [15118.955466] usb 4-1: Disable of device-initiated U2 failed.
  [15118.955474] usb-storage 4-1:1.0: USB Mass Storage device detected
  [15118.955648] scsi host9: usb-storage 4-1:1.0
  [15118.959180] usb 4-1: Set SEL for device-initiated U1 failed.
  [15118.962661] usb 4-1: Set SEL for device-initiated U2 failed.
  [15118.962810] usb 4-1: USB disconnect, device number 3
  [15455.620301] perf interrupt took too long (2527 > 2500), lowering 
kernel.perf_event_max_sample_rate to 5

  Trace DMESG du branchement avec un

[Kernel-packages] [Bug 1587674] Re: Wifi cannot connect to router on Ubuntu 16.04 LTS - Ralink RT5390

2016-06-07 Thread Christopher M. Penalver

Johnnel, in order to allow additional upstream developers to examine the issue, 
at your earliest convenience, could you please test the latest upstream kernel 
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please 
keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

Once testing of the latest upstream kernel is complete, please mark this
report Status Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags added: latest-bios-f.13

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

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

Title:
  Wifi cannot connect to router on Ubuntu 16.04 LTS - Ralink RT5390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have researched all possible solutions. The correct driver rt2800pci
  is installed correctly out of the box. No hardware faults. Wifi works
  on Ubuntu 14.04 and Windows 10. Confirmed also driver is not blocked
  and hardware is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  johnnel1436 F pulseaudio
   /dev/snd/controlC0:  johnnel1436 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue May 31 18:35:18 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f7d6820f-3da5-44be-9899-a3286c944329
  InstallationDate: Installed on 2016-05-20 (11 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1611
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.3A
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd07/07/2011:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr058911252B0310100:rvnHewlett-Packard:rn1611:rvr96.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dm1 Notebook PC
  dmi.product.version: 058911252B0310100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1567417] Re: WARN_ON(!wm_changed) skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]

2016-06-07 Thread blabber

Would it only collect more data then? I don't use the default kernel as
it's completely unstable on this laptop.

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

Title:
  WARN_ON(!wm_changed) skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm using a new Skylake Thinkpad T460s with and external monitor
  connected via Displayport and Ubuntu 16.04 and the latest kernel as of
  today: Linux test 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:17:28
  UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  X will from time to time lock up when the computer is left idle for a
  long time and both displays (laptop and external) go to sleep and then
  woken up.

  Apr  7 08:00:49 test kernel: [9.950929] [ cut here 
]
  Apr  7 08:00:49 test kernel: [9.950950] WARNING: CPU: 0 PID: 214 at 
/build/linux-YiIlnA/linux-4.4.0/ubuntu/i915/intel_pm.c:3572 
skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]()
  Apr  7 08:00:49 test kernel: [9.950951] WARN_ON(!wm_changed)
  Apr  7 08:00:49 test kernel: [9.950972] Modules linked in: btusb btrtl 
btbcm btintel bluetooth binfmt_misc nls_iso8859_1 arc4 snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_skl snd_soc_skl_ipc 
snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core snd_compress 
ac97_bus snd_pcm_dmaengine dw_dmac_core snd_hda_intel snd_hda_codec 
snd_hda_core snd_hwdep snd_pcm thinkpad_acpi intel_rapl x86_pkg_temp_thermal 
nvram intel_powerclamp snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi 
iwlmvm snd_seq joydev snd_seq_device input_leds mac80211 snd_timer serio_raw 
snd rtsx_pci_ms memstick soundcore iwlwifi cfg80211 mei_me mei tpm_crb mac_hid 
shpchp kvm_intel kvm irqbypass parport_pc ppdev lp parport autofs4 drbg 
ansi_cprng algif_skcipher af_alg hid_microsoft dm_crypt hid_generic usbhid hid 
rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul i915_bpo aesni_intel aes_x86_64 
lrw gf128mul glue_helper ablk_helper cryptd intel_ips i2c_algo_bit 
drm_kms_helper e1000e syscop
 yarea sysfillrect psmouse sysimgblt ptp fb_sys_fops pps_core drm nvme rtsx_pci 
wmi video fjes
  Apr  7 08:00:49 test kernel: [9.950980] CPU: 0 PID: 214 Comm: plymouthd 
Not tainted 4.4.0-17-generic #33-Ubuntu
  Apr  7 08:00:49 test kernel: [9.950981] Hardware name: LENOVO 
20F9CTO1WW/20F9CTO1WW, BIOS N1CET40W (1.08 ) 03/09/2016
  Apr  7 08:00:49 test kernel: [9.950982]  0286 
39cb6999 880502bc3618 813e8123
  Apr  7 08:00:49 test kernel: [9.950983]  880502bc3660 
c0343c70 880502bc3650 8107fe12
  Apr  7 08:00:49 test kernel: [9.950984]  880502da8000 
880501f79d9c 880502dab000 880508186b78
  Apr  7 08:00:49 test kernel: [9.950984] Call Trace:
  Apr  7 08:00:49 test kernel: [9.950988]  [] 
dump_stack+0x63/0x90
  Apr  7 08:00:49 test kernel: [9.950990]  [] 
warn_slowpath_common+0x82/0xc0
  Apr  7 08:00:49 test kernel: [9.950991]  [] 
warn_slowpath_fmt+0x5c/0x80
  Apr  7 08:00:49 test kernel: [9.951002]  [] 
skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]
  Apr  7 08:00:49 test kernel: [9.951010]  [] 
skl_update_wm+0x186/0x5f0 [i915_bpo]
  Apr  7 08:00:49 test kernel: [9.951023]  [] ? 
intel_ddi_enable_transcoder_func+0x17f/0x260 [i915_bpo]
  Apr  7 08:00:49 test kernel: [9.951034]  [] 
intel_update_watermarks+0x1e/0x30 [i915_bpo]
  Apr  7 08:00:49 test kernel: [9.951048]  [] 
haswell_crtc_enable+0x321/0x8c0 [i915_bpo]
  Apr  7 08:00:49 test kernel: [9.951061]  [] ? 
intel_finish_crtc_commit+0xe/0x10 [i915_bpo]
  Apr  7 08:00:49 test kernel: [9.951072]  [] ? 
drm_atomic_helper_commit_planes_on_crtc+0x154/0x270 [drm_kms_helper]
  Apr  7 08:00:49 test kernel: [9.951085]  [] 
intel_atomic_commit+0x5dd/0xdb0 [i915_bpo]
  Apr  7 08:00:49 test kernel: [9.951101]  [] ? 
drm_atomic_check_only+0x18e/0x590 [drm]
  Apr  7 08:00:49 test kernel: [9.951109]  [] 
drm_atomic_commit+0x37/0x60 [drm]
  Apr  7 08:00:49 test kernel: [9.951113]  [] 
restore_fbdev_mode+0x22f/0x260 [drm_kms_helper]
  Apr  7 08:00:49 test kernel: [9.951121]  [] ? 
drm_modeset_lock_all_ctx+0x9a/0xb0 [drm]
  Apr  7 08:00:49 test kernel: [9.951125]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x33/0x80 [drm_kms_helper]
  Apr  7 08:00:49 test kernel: [9.951128]  [] 
drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper]
  Apr  7 08:00:49 test kernel: [9.951131]  [] 
drm_fb_helper_hotplug_event+0xd2/0x120 [drm_kms_helper]
  Apr  7 08:00:49 test kernel: [9.951134]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x56/0x80 [drm_kms_helper]
  Apr  7 08:00:49 test kernel: [9.951136]  [] 
drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper]
  Apr  7 08:00:49 test kernel: [9.951150]  [] 
intel_fbdev_set_par+0x1a/0x60 [i915_bpo]
  Apr  7

[Kernel-packages] [Bug 1311289] Re: 168c:0032 [TravelMate B113-E] Has issues with bluetooth

2016-06-07 Thread Christopher M. Penalver

Wildman, please post the results of the following terminal command:
sudo cat /sys/kernel/debug/usb/devices

** Description changed:

I have Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev
01) on Acer TM B113-E notebook.

When I use ath9k with 3.11 kernel then all works fine. WiFi and Bluetooth
works as well.
I have problem with bluetooth when install some later kernels(I'm test
3.15rc1 and (3.13 or 3.14)) from http://kernel.ubuntu.com/~kernel-ppa/mainline/
After this installation I have not bluetooth device! When I switch Wi-Fi by
acpi key, I can switch only Wi-Fi to on or off state(I saw status by "rfkill
list"). Bluetooth device will not reconize for me...
But if I will power off notebook and disconnect battery, then after power on
I'm get working Bluetooth.

I could not pay attention to this troubles but now we have Ubuntu 14.04(I
tested on Kubuntu 14.04).
After installed Kubuntu 14.04 I have working only Wi-Fi. Power off+disconnect
battery and other probes(such as I probe to install non-free firmware) do not
have results. System do not recognize BT device... I can not see this device in
rfkill list and in KDE's System Settings->Bluetooth...
In 3.11 kernel and later kernel I have problem with bluetooth after sleeping
too. Module do not start after resume. I wrote script with manual starting of
btusb module and get working BT after resume.

- cat version.log
- Ubuntu 3.11.0-19.13-lowlatency 3.11.10.5
+ WORKAROUND: In modprobe.conf blacklist acer_wmi and add:
+ options ath9k btcoex_enable=1

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image (not installed)
ProcVersionSignature: Ubuntu 3.11.0-19.13-lowlatency 3.11.10.5
Uname: Linux 3.11.0-19-lowlatency x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: asm3180 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: asm3180 F pulseaudio
Date: Tue Apr 22 22:07:32 2014
HibernationDevice: RESUME=UUID=e179b479-7a1f-4d86-919c-809b7e5d9e8e
InstallationDate: Installed on 2013-10-19 (184 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
MachineType: Acer TravelMate B113
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-19-lowlatency
root=UUID=94f29b75-e824-41b5-aa40-c5734a2d4804 ro pciehp.pciehp_force=1
pciehp.pciehp_poll=1 quiet splash pcie_aspm=force i915.i915_enable_fbc=1
drm.vblankoffdelay=1 i915.semaphores=1 i915.lvds_downclock=1 nmi_watchdog=0
acpi_backlight=vendor elevator=noop
RelatedPackageVersions:
- linux-restricted-modules-3.11.0-19-lowlatency N/A
- linux-backports-modules-3.11.0-19-lowlatency N/A
- linux-firmware1.116.2
+ linux-restricted-modules-3.11.0-19-lowlatency N/A
+ linux-backports-modules-3.11.0-19-lowlatency N/A
+ linux-firmware1.116.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2012
dmi.bios.vendor: Acer
dmi.bios.version: V1.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA10_HX
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.09
dmi.modalias:
dmi:bvnAcer:bvrV1.09:bd10/30/2012:svnAcer:pnTravelMateB113:pvrV1.09:rvnAcer:rnBA10_HX:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.09:
dmi.product.name: TravelMate B113
dmi.product.version: V1.09
dmi.sys.vendor: Acer

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

Title:
168c:0032 [TravelMate B113-E] Has issues with bluetooth

Status in linux package in Ubuntu:
Expired

Bug description:
I have Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032]
(rev 01) on Acer TM B113-E notebook.

[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04

2016-06-07 Thread Christopher M. Penalver

tobyS, could you please test the latest mainline kernel (4.7-rc2) and
advise to the results?

** Tags removed: bios-outdated-2.35
** Tags added: latest-bios-2.35

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

** Tags added: regression-release

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

Title:
  Middle mouse (wheel-click) button stopped working after upgrade to
  16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to 16.04 clicking the middle mouse button (scroll
  wheel) on my Logitech M185 stopped working.

  xev does not even show the event for clicking the wheel, while it
  shows other button clicks and scroll wheel up/down events.

  xinput list shows the USB receiver 2 times:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=9[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ HID 046a:0023   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=16   [slave  pointer 
 (2)]
  ⎜   ↳ TPPS/2 IBM TrackPoint   id=17   [slave  pointer 
 (2)]

  Listing the capabilities looks like this:

  $ xinput list 9
  Logitech USB Receiver id=9[slave  pointer  (2)]
   Reporting 7 classes:
    Class originated from: 9. Type: XIButtonClass
    Buttons supported: 24
    Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel 
Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" 
"Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" 
"Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button 
Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" 
"Button Unknown" "Button Unknown" "Button Unknown"
    Button state:
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 3:
  Label: Rel Vert Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIScrollClass
    Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0
    Class originated from: 9. Type: XIScrollClass
    Scroll info for Valuator 3
  type: 1 (vertical)
  increment: -1.00
  flags: 0x2 ( preferred )

  $ xinput list 10
  Logitech USB Receiver id=10   [slave  pointer  (2)]
   Reporting 6 classes:
    Class originated from: 10. Type: XIButtonClass
    Buttons supported: 7
    Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel 
Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right"
    Button state:
    Class originated from: 10. Type: XIKeyClass
    Keycodes supported: 248
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIScrollClass
    Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0

  Does anyone have an idea how I can attempt to further debug that issue? Or 
maybe even a solution? Should I consider this issue a bug? Can I provide more 
info?
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  toby  11625 F pulseaudio
   /dev/snd/controlC0:  toby  11625 F pulseaudio
   /dev/snd/pcmC1D0p:   toby  11625 F...m pulseaudio
   /dev/snd/controlC1:  toby  11625 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice:

[Kernel-packages] [Bug 1583288] Re: Realtek Wifi card rtl8723be [10ec:b723] WiFi not available

2016-06-07 Thread Christopher M. Penalver

Podsgrove, it will help immensely if you filed a new report with Ubuntu (not 
Mint) via the default repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Realtek Wifi card rtl8723be [10ec:b723] WiFi not available

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I am here on a HP Pavilion Laptop with beatsaudio. No Model Number -
  nothing.But I have this problem on other HP (455) Notebooks too.

  OS tried: OpenSuse / Kubuntu / Linux Mint Mate (card does not work out
  of the box / no scanning)

  The Wifi card is: (in Germany!)

  --

   lspci -nn | grep -iA2 net
  02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE 
PCIe Wireless Network Adapter [10ec:b723]

  --

  I am now under kernel:
  4.4.0-21-generic

  I installed the newest kernel because in some threads people said the card 
woule be available in the newest kernel. But this was not the case. I mean the 
card is there but does not scan nor see any wifi networks.
  -

  Before I tried everything I could find to get my wifi running but I do
  not even see one spot. So no connection at all. I even cloned git and
  compiled the driver - the compiling and installation worked fine. I
  tried the old and the new driver.

  By the way the BT seems to be fine - although I have not checked cause
  I do not need BT.

  -
  Here is what I tried:

  rfkill list all; hciconfig -a
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  hci0: Type: BR/EDR Bus: USB
   BD Address: 2C:33:7A:3F:E4:3E ACL MTU: 820:8 SCO MTU: 255:16
   UP RUNNING PSCAN
   RX bytes:1327 acl:0 sco:0 events:139 errors:0
   TX bytes:25058 acl:0 sco:0 commands:139 errors:0
   Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
   Link policy: RSWITCH HOLD SNIFF PARK
   Link mode: SLAVE ACCEPT
   Name: 'mint-0'
   Class: 0x740100
   Service Classes: Rendering, Object Transfer, Audio, Telephony
   Device Class: Computer, Uncategorized
   HCI Version: 4.0 (0x6) Revision: 0xe2f
   LMP Version: 4.0 (0x6) Subversion: 0x9f73
   Manufacturer: Realtek Semiconductor Corporation (93)

  -

  I added the options sugested in rtl8723be.conf

  options rtl8723be fwlps=0 swlps=0

  But this did not help either.

  --

  lsmod reports:

  rfcomm 69632 12
  rtl8723be 139264 0
  btcoexist 180224 1 rtl8723be
  rtl_pci 40960 1 rtl8723be
  rtlwifi 98304 3 btcoexist,rtl_pci,rtl8723be
  hp_wmi 16384 0
  mac80211 733184 3 rtl_pci,rtlwifi,rtl8723be
  sparse_keymap 16384 1 hp_wmi
  kvm 532480 0
  irqbypass 16384 1 kvm
  btusb 45056 0
  crct10dif_pclmul 16384 0
  btrtl 16384 1 btusb
  btbcm 16384 1 btusb
  ...

  ---

  dmesg | grep rtl reports:

  [ 8.982260] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b 
lmp_ver=06 lmp_subver=8723
  [ 8.982262] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_fw.bin
  [ 9.064265] rtlwifi: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 9.403770] Using firmware rtlwifi/rtl8723befw.bin
  [ 9.404023] rtlwifi: channel plan 0x20
  [ 9.404027] rtlwifi: country code 11
  [ 9.422483] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
  [ 9.423458] rtlwifi: wireless switch is on

  

  modinfo rtl8723be

  filename: 
/lib/modules/4.4.0-21-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723be/rtl8723be.ko
  firmware: rtlwifi/rtl8723befw.bin
  description: Realtek 8723BE 802.11n PCI wireless
  license: GPL
  author: Realtek WlanFAE 
  author: PageHe 
  srcversion: 00619764255210776FAB54D
  alias: pci:v10ECdB723sv*sd*bc*sc*i*
  depends: rtlwifi,rtl_pci,btcoexist,mac80211
  vermagic: 4.4.0-21-generic SMP mod_unload modversions
  parm: swlps:bool
  parm: swenc:using hardware crypto (default 0 [hardware])
   (bool)
  parm: ips:using no link power save (default 1 is open)
   (bool)
  parm: fwlps:using linked fw control power save (default 1 is open)
   (bool)
  parm: msi:Set to 1 to use MSI interrupts mode (default 0)
   (bool)
  parm: debug:Set debug level (0-5) (default 0) (int)
  parm: disable_watchdog:Set to 1 to disable the watchdog (default 0)
   (bool)
  parm: ant_sel:Set to 1 or 2 to force antenna number (default 0)
   (int)

[Kernel-packages] [Bug 1589910] Re: [regression trusty] oops/sig 4: power7_enter_nap_mode+0x0/0x18

2016-06-07 Thread Stefan Bader

** Patch added: "0001-powerpc-powernv-Fix-incomplete-backport-of-8117ac6.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589910/+attachment/4678891/+files/0001-powerpc-powernv-Fix-incomplete-backport-of-8117ac6.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/1589910

Title:
  [regression trusty] oops/sig 4: power7_enter_nap_mode+0x0/0x18

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

Bug description:
  Arch: ppc64el
  Release: Trusty/14.04

  [ 0.194023] Oops: Exception in kernel mode, sig: 4 [#3]
  [ 0.194128] SMP NR_CPUS=2048 NUMA PowerNV
  [ 0.194225] Modules linked in:
  [ 0.194316] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G D 3.13.0-48-generic 
#80-Ubuntu
  [ 0.194403] task: c007f26957c0 ti: c007f2728000 task.ti: 
c007f2728000
  [ 0.194477] NIP: c1598930 LR: c001897c CTR: c002abfc
  [ 0.194551] REGS: c007f272b800 TRAP: 0e40 Tainted: G D (3.13.0-48-generic)
  [ 0.194651] MSR: 90081001  CR: 22004088 XER: 
  [ 0.194788] CFAR: c002ace4 SOFTE: 0
  ...
  [ 0.195869] NIP [c1598930] power7_enter_nap_mode+0x0/0x18

  SRU Justification:

  = Impact =
  Since kernel 3.13.0-46 there was a incorrect backport of a stable patch which 
causes several oops messages and ends with an automatic reboot. Which renders 
all kernels since then to be unbootable on ppc64el. This happens because 
instead of the function address to power7_enter_nap_mode, the change 
accidentally loads the address of a related symbol table.

  = Fix =
  Pick up the alternate declaration of the function label as it is in the 
original upstream change (commmit 8117ac6 powerpc/powernv: Switch off MMU 
before entering nap/sleep/rvwinkle mode). In 3.13 this requires one more change 
because there is one call site that refers to a label name which would be 
implicitly generated by the macro that gets replaced. This was done upstream, 
too, in (b1576fe powerpc: No need to use dot symbols when branching to a 
function).

  = Testcase =
  Trying to boot current Trusty kernels on a Power8 host fails all the time. 
With the change applied the host comes up without errors.

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

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

[Kernel-packages] [Bug 1589910] [NEW] [regression trusty] oops/sig 4: power7_enter_nap_mode+0x0/0x18

2016-06-07 Thread Stefan Bader

Public bug reported:

Arch: ppc64el
Release: Trusty/14.04

[ 0.194023] Oops: Exception in kernel mode, sig: 4 [#3]
[ 0.194128] SMP NR_CPUS=2048 NUMA PowerNV
[ 0.194225] Modules linked in:
[ 0.194316] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G D 3.13.0-48-generic 
#80-Ubuntu
[ 0.194403] task: c007f26957c0 ti: c007f2728000 task.ti: 
c007f2728000
[ 0.194477] NIP: c1598930 LR: c001897c CTR: c002abfc
[ 0.194551] REGS: c007f272b800 TRAP: 0e40 Tainted: G D (3.13.0-48-generic)
[ 0.194651] MSR: 90081001  CR: 22004088 XER: 
[ 0.194788] CFAR: c002ace4 SOFTE: 0
...
[ 0.195869] NIP [c1598930] power7_enter_nap_mode+0x0/0x18

SRU Justification:

= Impact =
Since kernel 3.13.0-46 there was a incorrect backport of a stable patch which 
causes several oops messages and ends with an automatic reboot. Which renders 
all kernels since then to be unbootable on ppc64el. This happens because 
instead of the function address to power7_enter_nap_mode, the change 
accidentally loads the address of a related symbol table.

= Fix =
Pick up the alternate declaration of the function label as it is in the 
original upstream change (commmit 8117ac6 powerpc/powernv: Switch off MMU 
before entering nap/sleep/rvwinkle mode). In 3.13 this requires one more change 
because there is one call site that refers to a label name which would be 
implicitly generated by the macro that gets replaced. This was done upstream, 
too, in (b1576fe powerpc: No need to use dot symbols when branching to a 
function).

= Testcase =
Trying to boot current Trusty kernels on a Power8 host fails all the time. With 
the change applied the host comes up without errors.

** Affects: linux (Ubuntu)
 Importance: High
 Status: Fix Released

** Affects: linux (Ubuntu Trusty)
 Importance: High
 Assignee: Stefan Bader (smb)
 Status: In Progress


** Tags: trusty

** Tags added: trusty

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

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

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

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Stefan Bader (smb)

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

** Changed in: linux (Ubuntu)
 Assignee: Stefan Bader (smb) => (unassigned)

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

Title:
  [regression trusty] oops/sig 4: power7_enter_nap_mode+0x0/0x18

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

Bug description:
  Arch: ppc64el
  Release: Trusty/14.04

  [ 0.194023] Oops: Exception in kernel mode, sig: 4 [#3]
  [ 0.194128] SMP NR_CPUS=2048 NUMA PowerNV
  [ 0.194225] Modules linked in:
  [ 0.194316] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G D 3.13.0-48-generic 
#80-Ubuntu
  [ 0.194403] task: c007f26957c0 ti: c007f2728000 task.ti: 
c007f2728000
  [ 0.194477] NIP: c1598930 LR: c001897c CTR: c002abfc
  [ 0.194551] REGS: c007f272b800 TRAP: 0e40 Tainted: G D (3.13.0-48-generic)
  [ 0.194651] MSR: 90081001  CR: 22004088 XER: 
  [ 0.194788] CFAR: c002ace4 SOFTE: 0
  ...
  [ 0.195869] NIP [c1598930] power7_enter_nap_mode+0x0/0x18

  SRU Justification:

  = Impact =
  Since kernel 3.13.0-46 there was a incorrect backport of a stable patch which 
causes several oops messages and ends with an automatic reboot. Which renders 
all kernels since then to be unbootable on ppc64el. This happens because 
instead of the function address to power7_enter_nap_mode, the change 
accidentally loads the address of a related symbol table.

  = Fix =
  Pick up the alternate declaration of the function label as it is in the 
original upstream change (commmit 8117ac6 powerpc/powernv: Switch off MMU 
before entering nap/sleep/rvwinkle mode). In 3.13 this requires one more change 
because there is one call site that refers to a label name which would be 
implicitly generated by the macro that gets replaced. This was done upstream, 
too, in (b1576fe powerpc: No need to use dot symbols when branching to a 
function).

  = Testcase =
  Trying to boot current Trusty kernels on a Power8 host fails all the time. 
With the change applied the host comes up without errors.

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

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

[Kernel-packages] [Bug 1584479] Re: [MSI GP72 6QE Leopard Pro] Touchpad not detected on 16.04

2016-06-07 Thread Christopher M. Penalver

Sam, could you please test the latest mainline kernel (4.7-rc2) and
advise to the results?

** Tags removed: bios-outdated-114
** Tags added: latest-bios-114

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

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

Title:
  [MSI GP72 6QE Leopard Pro] Touchpad not detected on 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I just install Ubuntu 16.04 on my new MSI laptop G72 6QE.
  My touchpad doesn't work and recognize at all.

  I try :
  - Fn+F3 to activate my touchpad
  - xinput list and is not listed
  - xev and nothing append (no signal)
  - cat /proc/bus/input/devices ddoesn't display touchpad (only HDMI, mic, 
headphone, external mouse and keyboard)
  - I don't know if there is a link, but some buttons of my keyboard don't work 
(like Fn+arrows to manage sound and luminosity) :
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd event0 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=60070290 8380207af040d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  
  Thanks
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1305 F pulseaudio
moi1668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9649bbed-2d32-42cd-a446-43abaa9ab1f3
  InstallationDate: Installed on 2016-05-20 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Micro-Star International Co., Ltd. GP72 6QE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic 
root=UUID=80432220-0bdf-49f0-a145-0c015ad36c2a ro rootflags=subvol=@ acpi=off 
acpi_osi=! acpi_backlight=native i8042.nopnp quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  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-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1795IMS.10C
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1795
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1795IMS.10C:bd12/10/2015:svnMicro-StarInternationalCo.,Ltd.:pnGP726QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1795:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP72 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~kernel-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-06-07 Thread Anthony Wong

** Changed in: hwe-next
   Status: New => Triaged

-- 
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:
  Triaged
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.

  ---

  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) 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. 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

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

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

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

[Kernel-packages] [Bug 1589905] Re: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] is not supported

2016-06-07 Thread Phidias

** Package changed: linux (Ubuntu) => linux-firmware (Ubuntu)

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

Title:
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  is not supported

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

Bug description:
  Firmware for this card isn't in the current linux-firmware package.
  Latest upstream firmware is also tested but doesn't work either.

  The only working firmware is extracted from Windows driver. By
  comparing the md5sum, the only different file is
  ath10k/QCA6174/hw3.0/board.bin (upstream is cb37c6, and Windows is
  df5ba1), we need Qualcomm to upstream the file to fix this issue.

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

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

[Kernel-packages] [Bug 1589905] Re: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] is not supported

2016-06-07 Thread Anthony Wong

** Changed in: hwe-next
 Assignee: (unassigned) => Phidias (phidias-chiang)

** Changed in: hwe-next
   Importance: Undecided => High

** Description changed:

  Firmware for this card isn't in the current linux-firmware package.
  Latest upstream firmware is also tested but doesn't work either.
  
- The only work firmware is extracted from Windows driver. By comparing
+ The only working firmware is extracted from Windows driver. By comparing
  the md5sum, the only different file is ath10k/QCA6174/hw3.0/board.bin
  (upstream is cb37c6, and Windows is df5ba1), we need Qualcomm to
  upstream the file to fix this issue.

** Changed in: hwe-next
   Status: New => Triaged

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

Title:
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  is not supported

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

Bug description:
  Firmware for this card isn't in the current linux-firmware package.
  Latest upstream firmware is also tested but doesn't work either.

  The only working firmware is extracted from Windows driver. By
  comparing the md5sum, the only different file is
  ath10k/QCA6174/hw3.0/board.bin (upstream is cb37c6, and Windows is
  df5ba1), we need Qualcomm to upstream the file to fix this issue.

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

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

[Kernel-packages] [Bug 1578840] Re: System doesn't enter low power states on Skylake processors (Lenovo Thinkpad X260)

2016-06-07 Thread Christopher M. Penalver

Konstantin, the issue you are reporting is an upstream one. Could you
please report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO Daniel Vetter and Jani Nikula CC intel-gfx)?

Please provide a direct URL to your post to the mailing list when it
becomes available so that it may be tracked.

Thank you for your understanding.


** Tags removed: bios-updated-1.19
** Tags added: bios-outdated-1.19

** Tags removed: bios-outdated-1.19
** Tags added: latest-bios-1.19

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

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

Title:
  System doesn't enter low power states on Skylake processors (Lenovo
  Thinkpad X260)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Powertop shows, that the system does not enter the low power idle
  states of the CPU (beyond PC2) despite the individual cores all
  reaching their lowest power idle states (C10). See attached screen
  shot for a typical example of powertop's output.

  A result of this is a vastly reduced battery live.

  Furthermore, Intel suggests that not enabling low power idle states may have 
a negative impact on the life time of the CPU. See
  https://mjg59.dreamwidth.org/41713.html

  The laptop is a Lenovo ThinkPad x260 which is is a Ubuntu certified
  system (http://www.ubuntu.com/certification/hardware/201511-20298/).

  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:  kaymes 1572 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  6 07:53:35 2016
  HibernationDevice: RESUME=UUID=7b2bf86b-4ad7-48d5-ba12-ed741ffcefea
  InstallationDate: Installed on 2016-05-04 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:0706 Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20F6CTO1WW
  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: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET44W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F6CTO1WW
  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:bvrR02ET44W(1.17):bd01/25/2016:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20F6CTO1WW
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1589905] Re: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] is not supported

2016-06-07 Thread Anthony Wong

** Tags added: dw1820b

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

Title:
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  is not supported

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

Bug description:
  Firmware for this card isn't in the current linux-firmware package.
  Latest upstream firmware is also tested but doesn't work either.

  The only working firmware is extracted from Windows driver. By
  comparing the md5sum, the only different file is
  ath10k/QCA6174/hw3.0/board.bin (upstream is cb37c6, and Windows is
  df5ba1), we need Qualcomm to upstream the file to fix this issue.

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

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

[Kernel-packages] [Bug 1589905] [NEW] Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] is not supported

2016-06-07 Thread Phidias

Public bug reported:

Firmware for this card isn't in the current linux-firmware package.
Latest upstream firmware is also tested but doesn't work either.

The only working firmware is extracted from Windows driver. By comparing
the md5sum, the only different file is ath10k/QCA6174/hw3.0/board.bin
(upstream is cb37c6, and Windows is df5ba1), we need Qualcomm to
upstream the file to fix this issue.

** Affects: hwe-next
 Importance: High
 Assignee: Phidias (phidias-chiang)
 Status: Triaged

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: dw1820b originate-from-1577657 somerville wily xenial

** Tags added: originate-from-1577657 somerville

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

Title:
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  is not supported

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

Bug description:
  Firmware for this card isn't in the current linux-firmware package.
  Latest upstream firmware is also tested but doesn't work either.

  The only working firmware is extracted from Windows driver. By
  comparing the md5sum, the only different file is
  ath10k/QCA6174/hw3.0/board.bin (upstream is cb37c6, and Windows is
  df5ba1), we need Qualcomm to upstream the file to fix this issue.

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

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

[Kernel-packages] [Bug 1549613] Re: Enable Sunix Serial/Parallel cards [1FD4:1999]

2016-06-07 Thread Anthony Wong

** Changed in: hwe-next
   Importance: Undecided => Medium

** Changed in: hwe-next
 Assignee: (unassigned) => Jesse Sung (wenchien)

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

Title:
  Enable Sunix Serial/Parallel cards [1FD4:1999]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  This card often shows up in our projects. We got the attached driver
  from vendor for inclusion into Ubuntu.

  This bug is for tracking purpose, please don't triage.

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

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

[Kernel-packages] [Bug 1578305] Re: Stoney powerplay support

2016-06-07 Thread Anthony Wong

** Changed in: hwe-next
   Status: New => 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/1578305

Title:
  Stoney powerplay support

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

Bug description:
  I'd love to submit a patch right now but I can't since the clone is
  taking way too long...

  The bug is in drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c on line 83
  you need to insert

  case CHIP_STONEY:

  before CHIP_CARRIZO to get ST to successfully init with the amdgpu
  module.

  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/controlC1:  amd1533 F pulseaudio
   /dev/snd/controlC0:  amd1533 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 12:35:10 2016
  HibernationDevice: RESUME=UUID=39b1897f-c3d9-4222-9b73-94e0f6527917
  InstallationDate: Installed on 2016-05-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enx54b80aefee18  no wireless extensions.
   
   enx1a1b9c20  no wireless extensions.
   
   lono wireless extensions.
  MachineType: AMD Gardenia-ST
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=f4bc1961-0964-4010-a6e5-401bbfe28352 ro quiet splash vt.handoff=7 
amdgpu.powerplay=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: WGY5930N_Weekly_15_09_3
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Gardenia-ST
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrWGY5930N_Weekly_15_09_3:bd09/30/2015:svnAMD:pnGardenia-ST:pvr1:rvnAMD:rnGardenia-ST:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Gardenia-ST
  dmi.product.version: 1
  dmi.sys.vendor: AMD

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

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

[Kernel-packages] [Bug 1549660] Re: Fix speaker volume on a Dell machine

2016-06-07 Thread Anthony Wong

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Fix speaker volume on a Dell machine

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  On one of the machines we enable, we found that the actual speaker
  volume did not always correspond to the volume set in alsamixer.

  This bug is for tracking purposes; please do not triage.

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

-- 
Mailing list: https://launchpad.net/~kernel-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-06-07 Thread Anthony Wong

** Tags added: dw1810

** Changed in: hwe-next
   Importance: Undecided => Medium

** Changed in: hwe-next
   Importance: Medium => High

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

  ---

  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) 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. 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

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

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

-- 
Mailing list: https://launchpad.net/~kernel-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-06-07 Thread Frederik Bosch

@emsi I had that problem too, you should ignore the binutils upgrade. I
had a look at the CHANGELOG of binutils and there is no significant
change. So the installation should continue although there is a
dependency mismatch. I cannot recall exactly what I fix the mismatch.

-- 
You 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
Status in linux source package in Yakkety:
  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-06-07 Thread Emsi

I'm having difficulties installing those packages on trusty.
I run into:
 linux-tools-3.13.0-86 : Depends: binutils (>= 2.24) but it is not going to be 
installed.
 Depends: binutils (< 2.25) but it is not going to be 
installed.
 Depends: libdw1 (>= 0.143) but it is not going to be 
installed.
 Depends: libunwind8 but it is not going to be 
installed.
 Depends: linux-tools-common but it is not going to be 
installed.


BTW: by default in cloud image there are following packages installed:
# dpkg -l  | grep 3.19.0
ii  linux-image-3.19.0-59-generic  3.19.0-59.66~14.04.1 amd64   
 Linux kernel image for version 3.19.0 on 64 bit x86 SMP
ii  linux-image-virtual-lts-vivid  3.19.0.59.42 amd64   
 This package will always depend on the latest minimal generic kernel image.
ii  linux-lts-vivid-cloud-tools-common 3.19.0-18.18~14.04.1 all 
 Linux kernel version specific cloud tools for version 3.19.0

I'm wondering about linux-lts-vivid-cloud-tools-common... Do you provide
the same version of cloud tools in your packages? (Note it's a vivid
backport).

-- 
You 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
Status in linux source package in Yakkety:
  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 1588467] Re: Mount USB3 KEY of 64 Go

2016-06-07 Thread Bougron

Hello.
Today some measures:

On the USB3 Key, i put a very big file of 61 801 717 760 octets. It is
100% of the only ntfs partition.

Copying on a internal disk file this KEY  mounted on USB2 is 36'38" with
windows and 36'21" with ubuntu. The rate is  28 MB/s.


Copying on a internal disk file this KEY  mounted on USB3 with an extended usb2 
cable of 10 inches is 31'40" with windows and 29'36" with ubuntu. The rate is  
35 MB/s with ubuntu and 33 MB/s with windows.
But another test with ubuntu and working a little on internet give a laps of 
copy 34"37". Rate is 30 Mb/s. So i say that it is the same result between 
windows and ubuntu.

Copying on a internal disk file this KEY  mounted directly on USB3  is 21'27" 
with windows. The rate is 48 Mb/s.
Copying on a 'nul' file this KEY  mounted directly on USB3 with windows is also 
a rate of 48 Mb/s.
( copy   fic1   /B > nul)

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

Title:
  Mount USB3 KEY of 64 Go

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  New question #293348 on Ubuntu:
  https://answers.launchpad.net/ubuntu/+question/293348

  Bonjour. / Hello.

  Je  peux utiliser ma clé USB3 sur un port USB3 avec windows mais pas avec 
ubuntu 16.04 sauf à y mettre un prolongateur usb2.
  I use my “USB3-key on a USB3 port with Windows but not with ubuntu 16.04 
except to put a USB2 extender.

  u1604btrfs@u1604btrfs:~$ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
  u1604btrfs@u1604btrfs:~$

  La clé USB3 de 64 GO connectée directement à un port USB3 n’a aucun problème 
avec windows10 avec un débit moyen de 42 MB/s.
  The USB3 64GB connected directly to a USB3 port was no problem with Windows 
10 with an average throughput of 42 MB / s.

  La clé USB3 de 64 GO connectée via un càble USB de prolongation  (20 cm)  à 
un port USB3 fonctionne avec un débit moyen de 26 MB/s avec ubuntu.
  The USB3 64GB connected via an extension USB cable (20 cm) to a USB3 port 
works with an average throughput of 26 MB / s with ubuntu.

  Un disque USB3 connecté à ce même port USB3 fonctionne avec un débit moyen de 
106 MB/s avec ubuntu,
  A USB3 drive connected to the same USB3 port works with an average throughput 
of 106 MB / s with ubuntu.

  La clé USB3 de 64 GO connectée directement à un port USB3 ne se monte pas  
avec ubuntu, Je pense à un problème logiciel. Merci de votre avis.
  The USB 3 64GB connected directly to a USB3 port does not go up with ubuntu. 
I think to a software problem, Thanks for your review,

  Trace DMESG du branchement direct.
  Trace DMESG direct connection.
  [15027.934173] usb 3-1: USB disconnect, device number 3
  [15113.908384] usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
  [15113.949359] usb 4-1: New USB device found, idVendor=0951, idProduct=1666
  [15113.949370] usb 4-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [15113.949377] usb 4-1: Product: DataTraveler 3.0
  [15113.949387] usb 4-1: Manufacturer: Kingston
  [15113.949395] usb 4-1: SerialNumber: 60A44C426697FE50C98100E8
  [15118.948235] usb 4-1: Set SEL for device-initiated U2 failed.
  [15118.951961] usb 4-1: Disable of device-initiated U1 failed.
  [15118.955466] usb 4-1: Disable of device-initiated U2 failed.
  [15118.955474] usb-storage 4-1:1.0: USB Mass Storage device detected
  [15118.955648] scsi host9: usb-storage 4-1:1.0
  [15118.959180] usb 4-1: Set SEL for device-initiated U1 failed.
  [15118.962661] usb 4-1: Set SEL for device-initiated U2 failed.
  [15118.962810] usb 4-1: USB disconnect, device number 3
  [15455.620301] perf interrupt took too long (2527 > 2500), lowering 
kernel.perf_event_max_sample_rate to 5

  Trace DMESG du branchement avec un câble prolongateur.
  Trace DMESG connecting with an extension cable.
  [15455.620301] perf interrupt took too long (2527 > 2500), lowering 
kernel.perf_event_max_sample_rate to 5
  [15930.041889] usb 3-1: new high-speed USB device number 4 using xhci_hcd
  [15930.248230] usb 3-1: New USB device found, idVendor=0951, idProduct=1666
  [15930.248237] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [15930.248241] usb 3-1: Product: DataTraveler 3.0
  [15930.248244] usb 3-1: Manufacturer: Kingston
  [15930.248246] usb 3-1: SerialNumber: 60A44C426697FE50C98100E8
  [15930.248591] usb 3-1: ep 0x81 - rounding interval to 128 microframes, ep 
desc says 255 microframes
  [15930.248610] usb 3-1: ep 0x2 - rounding interval to 128 microframes, ep 
desc says 255 microframes
  [15930.249352] usb-storage 3-1:1.0: USB Mass Storage device detected
  [15930.251542] scsi host10: usb-storage 3-1:1.0
  [15932.447123] scsi 10:0:0:0: Direct-Access Kingston DataTraveler 3.0 
1.00 PQ: 0 ANSI: 6
  [15932.447953] sd 10:0:0:0: Attached scsi generic sg2 type 0
  [15932.449447] sd

[Kernel-packages] [Bug 1544254] Re: connected bt mouse/kybd get disconnected/not in "connect when active" list

2016-06-07 Thread Victor gonzalez

Hope this is useful for you, test performe with Rii BT keyboard that
cannot connect automatically when it comes from idle:

Time stamp:

9:57 - Start
9:57 - Forget BT keyboard RII
9:58 - Paired
9:58-10:00 - Use some apps with RII keybard
10:07 - Frieza locked(both tablet BT and keyboard still on)
10:59 - Unlock Frieza --> BT keyboard is on and Frieza BT appears not 
connected. It is not able to autoconnect in this scenario where tablet entered 
deep sleep and awakes again.

11:01 - Tapped in connect button from BT settings and it is not able to connect
11:01 - Press button combo in BT keyboard to disable and enable BT again to see 
if it pairs automatically
11:03 - It connects automatically

** Attachment added: "Rii_BT_keyboard_test_logs.zip"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544254/+attachment/4678807/+files/Rii_BT_keyboard_test_logs.zip

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

Title:
  connected bt mouse/kybd get disconnected/not in "connect when active"
  list

Status in Canonical System Image:
  Incomplete
Status in Canonical Pocket Desktop:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  So I've been running ubuntu-pd on Nexus4 over a few days and began
  noticing this.

  1. connect bt mouse and keyboard
  2. connect to external monitor
  3. use device for extended period of time

  sometimes the devices will appear to disconnect, as well as be forgotten.
  I can't tell if this is in conjunction with the screen blanking or not

  I've even run into the kybd being forgotten, while the mouse was
  remembered.

  here's my devices info
  [bluetooth]# paired-devices
  Device 34:88:5D:24:05:61 Logitech Keyboard K480
  Device F0:65:DD:AA:04:8B HP Bluetooth Mouse X4000b
  [bluetooth]# info 34:88:5D:24:05:61
  Device 34:88:5D:24:05:61
   Name: Logitech Keyboard K480
   Alias: Logitech Keyboard K480
   Class: 0x002540
   Icon: input-keyboard
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: yes
   LegacyPairing: yes
   UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
   UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
   UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
   Modalias: usb:v046DpB330d2800
  [bluetooth]# info F0:65:DD:AA:04:8B
  Device F0:65:DD:AA:04:8B
   Name: HP Bluetooth Mouse X4000b
   Alias: HP Bluetooth Mouse X4000b
   Class: 0x002580
   Icon: input-mouse
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: yes
   LegacyPairing: no
   UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
   UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
   UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
   Modalias: usb:v03F0p024Cd0103
  [bluetooth]#

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

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

[Kernel-packages] [Bug 1543179] Re: Audio does not get routed to BT headset/speaker

2016-06-07 Thread Victor gonzalez

Hope this is useful for you, I performed some test with a BT
headset(blueaudio I5):

Time stamp:

10:23 - Paired 
10:24 -/27 Two success calls(last one BT is disconnected before ending the 
call, phone call properly routed to the phone)

10:44 - disconnect and connect Krillin BT again
10:45 - BT headset autoconnects properly(audio routed to headset saying 
"connected")
10:46 - Receive a phone call("Incoming call" voice sounds through earpiece)
10:47 - Phone call ends properly

10:48 - Play some music and use volume controls properly
10:50 - Disconnect BT and music stops

Additional info: logs = dbus+syslog+application-legacy-ubuntu-system-
settings-.log

** Attachment added: "Blueaudio_I5_headset_tests.zip"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+attachment/4678798/+files/Blueaudio_I5_headset_tests.zip

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

Title:
  Audio does not get routed to BT headset/speaker

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Flash the latest daily rc-proposed image to a phone
  2. Connect a bluetooth headset to the phone
  3. Connect a speaker to the phone.

  EXPECTED:
  I expect the devices to connect and play audio

  ACTUAL:
  Speakers just connect and instantly disconnect

  Headsets don't get trusted and disconnect instantly, Once you trust it
  and then turn the headset off and back on again it connect can accept
  calls but the audio from both the mic and earpiece don't function.

  Image: 242

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

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

Re: [Kernel-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2016-06-07 Thread Ștefănescu Cristian

Hello,

The touchpad is working fine with 4.4.0-23-generic, but the sound problem
persists.

On Mon, Jun 6, 2016 at 4:16 PM, Barry  wrote:

> Any update on this? I'd love the get the touchpad working properly.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1563110
>
> Title:
>   No sound on Asus e200ha, intel sst with cx2072x codec
>
> Status in ALSA driver:
>   Unknown
> Status in alsa-driver package in Ubuntu:
>   Confirmed
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I've recently bought an Asus e200ha.
>   Sound in this laptop doesn't work.
>   The sound card is an intel sst with codec conexant cx2072x
>
>   aplay -l:
>   aplay: device_list:268: no soundcard found...
>   in the sound setting there is a "Dummy output"
>   ---
>   ApportVersion: 2.14.1-0ubuntu3.19
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: XFCE
>   DistroRelease: Ubuntu 14.04
>   HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
>   InstallationDate: Installed on 2016-03-28 (0 days ago)
>   InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
>   Lsusb:
>Bus 002 Device 002: ID 0781:5583 SanDisk Corp.
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 13d3:3496 IMC Networks
>Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: ASUSTeK COMPUTER INC. E200HA
>   Package: linux (not installed)
>   ProcEnviron:
>TERM=xterm
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=it_IT.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic
> root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
>   RelatedPackageVersions:
>linux-restricted-modules-3.19.0-32-generic N/A
>linux-backports-modules-3.19.0-32-generic  N/A
>linux-firmware 1.127.16
>   Tags:  rosa
>   Uname: Linux 3.19.0-32-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 11/26/2015
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: E200HA.203
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: E200HA
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: 1.0
>   dmi.chassis.asset.tag: ATN12345678901234567
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK COMPUTER INC.
>   dmi.chassis.version: 1.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
>   dmi.product.name: E200HA
>   dmi.product.version: 1.0
>   dmi.sys.vendor: ASUSTeK COMPUTER INC.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions
>


-- 
Multumesc,
Cristian Stefanescu
Google+ 
Facebook 
GitHub 

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)

[Kernel-packages] [Bug 1584479] Re: [MSI GP72 6QE Leopard Pro] Touchpad not detected on 16.04

2016-06-07 Thread Sam

Hi,

I just update my BIOS and nothing apparently change (cat
/proc/bus/input/devices return the same result).

dmidecode -s bios-version : E1795IMS.114
dmidecode -s bios-release-date : 04/29/2016


Thanks

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

Title:
  [MSI GP72 6QE Leopard Pro] Touchpad not detected on 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  I just install Ubuntu 16.04 on my new MSI laptop G72 6QE.
  My touchpad doesn't work and recognize at all.

  I try :
  - Fn+F3 to activate my touchpad
  - xinput list and is not listed
  - xev and nothing append (no signal)
  - cat /proc/bus/input/devices ddoesn't display touchpad (only HDMI, mic, 
headphone, external mouse and keyboard)
  - I don't know if there is a link, but some buttons of my keyboard don't work 
(like Fn+arrows to manage sound and luminosity) :
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd event0 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=60070290 8380207af040d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  
  Thanks
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1305 F pulseaudio
moi1668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9649bbed-2d32-42cd-a446-43abaa9ab1f3
  InstallationDate: Installed on 2016-05-20 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Micro-Star International Co., Ltd. GP72 6QE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic 
root=UUID=80432220-0bdf-49f0-a145-0c015ad36c2a ro rootflags=subvol=@ acpi=off 
acpi_osi=! acpi_backlight=native i8042.nopnp quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  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-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1795IMS.10C
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1795
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1795IMS.10C:bd12/10/2015:svnMicro-StarInternationalCo.,Ltd.:pnGP726QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1795:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP72 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1568703] Re: [Alienware Alienware 13 R2] hibernate/resume failure [non-free: nvidia_uvm nvidia_modeset nvidia]

2016-06-07 Thread Jan Stutzki

Dell released another BIOS update (1.2.14) which I installed. Using
4.4.0-22 the error message unfortunately remains the same.

Using Mainline Kernele 4.7-rc2 the system does not suspend anymore. The
HD activity indicator is permanently on and judging by the sound of the
ac adapter the CPU is under load.

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

Title:
  [Alienware Alienware 13 R2] hibernate/resume failure [non-free:
  nvidia_uvm nvidia_modeset nvidia]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As standby is not working I tried it with hibernate. Unfortunately the
  same error occurs (EXT4-fs error) after the message that nvme0n1 is
  not available.

  ProblemType: KernelOops
  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
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1306 F pulseaudio
stutzki2131 F pulseaudio
  Date: Mon Apr 11 08:34:00 2016
  DuplicateSignature: hibernate/resume:Alienware Alienware 13 R2:1.2.12
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=45b1ef11-e9d4-4daf-9cb1-f253e996f6b4
  InstallationDate: Installed on 2016-04-01 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
  InterpreterPath: /usr/bin/python3.5
  MachineType: Alienware Alienware 13 R2
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=9bc7e2b8-0f93-4332-b217-19fdb84e9e0d ro
  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
  Title: [Alienware Alienware 13 R2] hibernate/resume failure [non-free: 
nvidia_uvm nvidia_modeset nvidia]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/22/2016
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.12
  dmi.board.name: Alienware 13 R2
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.12:bd03/22/2016:svnAlienware:pnAlienware13R2:pvr1.2.12:rvnAlienware:rnAlienware13R2:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 13 R2
  dmi.product.version: 1.2.12
  dmi.sys.vendor: Alienware

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

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

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

2016-06-07 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/1589837

Title:
  Kernel oops - BUG: unable to handle kernel NULL pointer dereference at
  00e4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Regarding the dmesg from the crashdump:

  [ 2210.842592] BUG: unable to handle kernel NULL pointer dereference at 
00e4
  [ 2210.842631] IP: [] sock_poll+0x26/0x120
  [ 2210.842659] PGD 0 
  [ 2210.842670] Oops:  [#1] SMP 
  [ 2210.842687] Modules linked in: drbg ansi_cprng cdc_ether usbnet r8152 mii 
nvram rfcomm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) xt_tcpudp bridge stp llc 
vboxdrv(OE) iptable_filter ip_tables x_tables msr bnep btusb btrtl btbcm 
btintel bluetooth input_leds joydev bcm5974 nls_iso8859_1 applesmc 
input_polldev brcmfmac snd_hda_codec_hdmi snd_hda_codec_cirrus 
snd_hda_codec_generic brcmutil cfg80211 thunderbolt bdc_pci intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd intel_pch_thermal lpc_ich snd_hda_intel snd_hda_codec 
snd_hda_core
  [ 2210.843039]  snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer mei_me snd mei shpchp soundcore sbs sbshc 
acpi_als kfifo_buf apple_bl industrialio mac_hid spi_pxa2xx_platform 
facetimehd(OE) videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videobuf2_core 
v4l2_common videodev media parport_pc ppdev lp parport autofs4 hid_generic 
hid_apple usbhid hid uas usb_storage i915 i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops ahci libahci drm fjes video
  [ 2210.843180] CPU: 3 PID: 3991 Comm: Chrome_IOThread Tainted: G   OE 
  4.4.0-22-generic #40-Ubuntu
  [ 2210.843202] Hardware name: Apple Inc. MacBookPro12,1/Mac-E43C1C25D4880AD6, 
BIOS MBP121.88Z.0167.B14.1509281135 09/28/2015
  [ 2210.843226] task: 8802611de040 ti: 880263a44000 task.ti: 
880263a44000
  [ 2210.843243] RIP: 0010:[]  [] 
sock_poll+0x26/0x120
  [ 2210.843264] RSP: 0018:880263a47d68  EFLAGS: 00010246
  [ 2210.843276] RAX: 81abcbe0 RBX: 88022dedf480 RCX: 
88022c576918
  [ 2210.843292] RDX:  RSI: 880263a47db8 RDI: 
880263c1cf00
  [ 2210.843308] RBP: 880263a47d90 R08:  R09: 
880242c88c18
  [ 2210.843324] R10: 880244293038 R11: 88025f54d8c0 R12: 
880263a47db8
  [ 2210.843340] R13: 880263c1cf00 R14:  R15: 

  [ 2210.843356] FS:  7f4015e73700() GS:88026ecc() 
knlGS:
  [ 2210.843374] CS:  0010 DS:  ES:  CR0: 80050033
  [ 2210.843388] CR2: 00e4 CR3: 821fe000 CR4: 
003406e0
  [ 2210.843404] Stack:
  [ 2210.843409]  880263a47e18  1ed61c429c00 
880263a47ea0
  [ 2210.843429]  880124d99d98 880263a47df8 81254a50 
8800821d98a0
  [ 2210.843448]  880263a47f18 8800821d9840  
0019
  [ 2210.843467] Call Trace:
  [ 2210.843476]  [] ep_send_events_proc+0xb0/0x1c0
  [ 2210.843490]  [] ? ep_ptable_queue_proc+0xa0/0xa0
  [ 2210.843505]  [] ep_scan_ready_list+0x99/0x1f0
  [ 2210.843519]  [] ep_poll+0x1d8/0x3d0
  [ 2210.843532]  [] ? vfs_write+0x149/0x1a0
  [ 2210.843545]  [] SyS_epoll_wait+0xb8/0xd0
  [ 2210.843560]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [ 2210.843574] Code: 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 
55 41 54 45 31 ff 53 48 8b 9f d0 00 00 00 49 89 fd 49 89 f4 4c 8b 73 20 <41> 8b 
96 e4 00 00 00 85 d2 0f 84 c2 00 00 00 41 8b 86 e0 00 00 
  [ 2210.843662] RIP  [] sock_poll+0x26/0x120
  [ 2210.843679]  RSP 
  [ 2210.843687] CR2: 00e4

  
  the problem occurs since yesterday. 
  probably related to 
http://googlechromereleases.blogspot.ch/2016/06/stable-channel-update_6.html

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin  2371 F pulseaudio
   /dev/snd/controlC1:  kevin  2371 F pulseaudio
  Date: Tue Jun  7 09:38:44 2016
  InstallationDate: Installed on 2016-03-01 (97 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed

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

2016-06-07 Thread Victor gonzalez

Please find attached logs from a BT success pairing and functioning with
Renault Clio. Hope it is useful.

Time stamp:

9:32 - Start test
9:35 - Successfully paired
9:35-36 - Phone call done properly

** Attachment added: "logs_Renaul_Clio_success_BT_connection.zip"

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+attachment/4678728/+files/logs_Renaul_Clio_success_BT_connection.zip

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

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

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

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

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

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

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

ACTUAL:
No connection to the blue tooth device

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

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

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

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

[Kernel-packages] [Bug 1589837] [NEW] Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 00000000000000e4

2016-06-07 Thread Kevin

Public bug reported:

Regarding the dmesg from the crashdump:

[ 2210.842592] BUG: unable to handle kernel NULL pointer dereference at 
00e4
[ 2210.842631] IP: [] sock_poll+0x26/0x120
[ 2210.842659] PGD 0 
[ 2210.842670] Oops:  [#1] SMP 
[ 2210.842687] Modules linked in: drbg ansi_cprng cdc_ether usbnet r8152 mii 
nvram rfcomm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) xt_tcpudp bridge stp llc 
vboxdrv(OE) iptable_filter ip_tables x_tables msr bnep btusb btrtl btbcm 
btintel bluetooth input_leds joydev bcm5974 nls_iso8859_1 applesmc 
input_polldev brcmfmac snd_hda_codec_hdmi snd_hda_codec_cirrus 
snd_hda_codec_generic brcmutil cfg80211 thunderbolt bdc_pci intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd intel_pch_thermal lpc_ich snd_hda_intel snd_hda_codec 
snd_hda_core
[ 2210.843039]  snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer mei_me snd mei shpchp soundcore sbs sbshc 
acpi_als kfifo_buf apple_bl industrialio mac_hid spi_pxa2xx_platform 
facetimehd(OE) videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videobuf2_core 
v4l2_common videodev media parport_pc ppdev lp parport autofs4 hid_generic 
hid_apple usbhid hid uas usb_storage i915 i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops ahci libahci drm fjes video
[ 2210.843180] CPU: 3 PID: 3991 Comm: Chrome_IOThread Tainted: G   OE   
4.4.0-22-generic #40-Ubuntu
[ 2210.843202] Hardware name: Apple Inc. MacBookPro12,1/Mac-E43C1C25D4880AD6, 
BIOS MBP121.88Z.0167.B14.1509281135 09/28/2015
[ 2210.843226] task: 8802611de040 ti: 880263a44000 task.ti: 
880263a44000
[ 2210.843243] RIP: 0010:[]  [] 
sock_poll+0x26/0x120
[ 2210.843264] RSP: 0018:880263a47d68  EFLAGS: 00010246
[ 2210.843276] RAX: 81abcbe0 RBX: 88022dedf480 RCX: 88022c576918
[ 2210.843292] RDX:  RSI: 880263a47db8 RDI: 880263c1cf00
[ 2210.843308] RBP: 880263a47d90 R08:  R09: 880242c88c18
[ 2210.843324] R10: 880244293038 R11: 88025f54d8c0 R12: 880263a47db8
[ 2210.843340] R13: 880263c1cf00 R14:  R15: 
[ 2210.843356] FS:  7f4015e73700() GS:88026ecc() 
knlGS:
[ 2210.843374] CS:  0010 DS:  ES:  CR0: 80050033
[ 2210.843388] CR2: 00e4 CR3: 821fe000 CR4: 003406e0
[ 2210.843404] Stack:
[ 2210.843409]  880263a47e18  1ed61c429c00 
880263a47ea0
[ 2210.843429]  880124d99d98 880263a47df8 81254a50 
8800821d98a0
[ 2210.843448]  880263a47f18 8800821d9840  
0019
[ 2210.843467] Call Trace:
[ 2210.843476]  [] ep_send_events_proc+0xb0/0x1c0
[ 2210.843490]  [] ? ep_ptable_queue_proc+0xa0/0xa0
[ 2210.843505]  [] ep_scan_ready_list+0x99/0x1f0
[ 2210.843519]  [] ep_poll+0x1d8/0x3d0
[ 2210.843532]  [] ? vfs_write+0x149/0x1a0
[ 2210.843545]  [] SyS_epoll_wait+0xb8/0xd0
[ 2210.843560]  [] entry_SYSCALL_64_fastpath+0x16/0x71
[ 2210.843574] Code: 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 
55 41 54 45 31 ff 53 48 8b 9f d0 00 00 00 49 89 fd 49 89 f4 4c 8b 73 20 <41> 8b 
96 e4 00 00 00 85 d2 0f 84 c2 00 00 00 41 8b 86 e0 00 00 
[ 2210.843662] RIP  [] sock_poll+0x26/0x120
[ 2210.843679]  RSP 
[ 2210.843687] CR2: 00e4


the problem occurs since yesterday. 
probably related to 
http://googlechromereleases.blogspot.ch/2016/06/stable-channel-update_6.html

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.40
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kevin  2371 F pulseaudio
 /dev/snd/controlC1:  kevin  2371 F pulseaudio
Date: Tue Jun  7 09:38:44 2016
InstallationDate: Installed on 2016-03-01 (97 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Apple Inc. MacBookPro12,1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=18e90ec4-bbea-4061-aa6a-a7a46445929d ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic  N/A
 linux-firmware1.157
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-06 (61 days ago)
dmi.bios.date: 09/28/2015

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

2016-06-07 Thread Ryan

I wasn't able to boot 4.6.1, but I was able to boot 4.6.0-040600-generic
#201606030904. It does not seem to have the screen detection or freezing
issues experienced in 4.4.0 when docking/un-docking (yet).

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

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

Status in linux package in Ubuntu:
  Incomplete

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 1589418] Re: udisksd high CPU usage

2016-06-07 Thread Bones

APPORT

ProblemType: Hang
Architecture: amd64
Date: Tue Jun  7 08:14:43 2016
Dependencies:
 adduser 3.113+nmu3ubuntu4 [origin: unknown]
 apt 1.0.10.2ubuntu3 [origin: unknown]
 apt-utils 1.0.10.2ubuntu3 [origin: unknown]
 coreutils 8.23-4ubuntu2 [origin: unknown]
 dbus 1.10.0-1ubuntu1 [origin: unknown]
 debconf 1.5.57ubuntu1 [origin: unknown]
 debconf-i18n 1.5.57ubuntu1 [origin: unknown]
 debianutils 4.5.1 [origin: unknown]
 dmsetup 2:1.02.99-1ubuntu1 [origin: unknown]
 dosfstools 3.0.28-1ubuntu0.1 [origin: unknown]
 dpkg 1.18.2ubuntu5.1 [origin: unknown]
 e2fslibs 1.42.12-1ubuntu2 [origin: unknown]
 e2fsprogs 1.42.12-1ubuntu2 [origin: unknown]
 eject 2.1.5+deb1+cvs20081104-13.1 [origin: unknown]
 fuse 2.9.4-1ubuntu1 [origin: unknown]
 gcc-5-base 5.2.1-22ubuntu2 [origin: unknown]
 gdisk 1.0.0-3 [origin: unknown]
 gnupg 1.4.18-7ubuntu1 [modified: usr/lib/gnupg/gpgkeys_curl 
usr/lib/gnupg/gpgkeys_hkp] [origin: unknown]
 gpgv 1.4.18-7ubuntu1 [origin: unknown]
 groff-base 1.22.3-1 [origin: unknown]
 init-system-helpers 1.23ubuntu4 [origin: unknown]
 initscripts 2.88dsf-59.2ubuntu2.1 [origin: unknown]
 insserv 1.14.0-5ubuntu3 [origin: unknown]
 libacl1 2.2.52-2 [origin: unknown]
 libapparmor1 2.10-0ubuntu6 [origin: unknown]
 libapt-inst1.7 1.0.10.2ubuntu3 [origin: unknown]
 libapt-pkg4.16 1.0.10.2ubuntu3 [origin: unknown]
 libatasmart4 0.19-3 [origin: unknown]
 libattr1 1:2.4.47-2 [origin: unknown]
 libaudit-common 1:2.4.2-1ubuntu1 [origin: unknown]
 libaudit1 1:2.4.2-1ubuntu1 [origin: unknown]
 libblkid1 2.26.2-6ubuntu3 [origin: unknown]
 libbz2-1.0 1.0.6-8 [origin: unknown]
 libc6 2.21-0ubuntu4.3 [origin: unknown]
 libcap-ng0 0.7.6-1 [origin: unknown]
 libcap2 1:2.24-9 [origin: unknown]
 libcap2-bin 1:2.24-9 [origin: unknown]
 libcomerr2 1.42.12-1ubuntu2 [origin: unknown]
 libcryptsetup4 2:1.6.6-5ubuntu2 [origin: unknown]
 libdb5.3 5.3.28-11 [origin: unknown]
 libdbus-1-3 1.10.0-1ubuntu1 [origin: unknown]
 libdevmapper1.02.1 2:1.02.99-1ubuntu1 [origin: unknown]
 libexpat1 2.1.0-7ubuntu0.15.10.1 [origin: unknown]
 libfdisk1 2.26.2-6ubuntu3 [origin: unknown]
 libffi6 3.2.1-3 [origin: unknown]
 libfuse2 2.9.4-1ubuntu1 [origin: unknown]
 libgcc1 1:5.2.1-22ubuntu2 [origin: unknown]
 libgcrypt20 1.6.3-2ubuntu1.1 [origin: unknown]
 libglib2.0-0 2.46.2-1ubuntu2 [origin: unknown]
 libglib2.0-data 2.46.2-1ubuntu2 [origin: unknown]
 libgmp10 2:6.0.0+dfsg-7 [origin: unknown]
 libgnutls-deb0-28 3.3.15-5ubuntu2 [origin: unknown]
 libgpg-error0 1.19-2 [origin: unknown]
 libgpm2 1.20.4-6.1 [origin: unknown]
 libgudev-1.0-0 1:230-2 [origin: unknown]
 libhogweed4 3.1.1-4ubuntu0.1 [origin: unknown]
 libicu55 55.1-4ubuntu1 [origin: unknown]
 libkmod2 21-1ubuntu1 [origin: unknown]
 liblocale-gettext-perl 1.05-9 [origin: unknown]
 liblzma5 5.1.1alpha+20120614-2ubuntu2 [origin: unknown]
 libmount1 2.26.2-6ubuntu3 [origin: unknown]
 libncurses5 5.9+20150516-2ubuntu1 [origin: unknown]
 libncursesw5 5.9+20150516-2ubuntu1 [origin: unknown]
 libnettle6 3.1.1-4ubuntu0.1 [origin: unknown]
 libp11-kit0 0.23.1-3 [origin: unknown]
 libpam-modules 1.1.8-3.1ubuntu3.2 [origin: unknown]
 libpam-modules-bin 1.1.8-3.1ubuntu3.2 [origin: unknown]
 libpam-runtime 1.1.8-3.1ubuntu3.2 [origin: unknown]
 libpam-systemd 225-1ubuntu9.1 [origin: unknown]
 libpam0g 1.1.8-3.1ubuntu3.2 [origin: unknown]
 libparted2 3.2-7ubuntu1 [origin: unknown]
 libpcre3 2:8.35-7.1ubuntu1.4 [origin: unknown]
 libpng12-0 1.2.51-0ubuntu3.15.10.2 [origin: unknown]
 libpolkit-agent-1-0 0.105-11ubuntu3 [origin: unknown]
 libpolkit-backend-1-0 0.105-11ubuntu3 [origin: unknown]
 libpolkit-gobject-1-0 0.105-11ubuntu3 [origin: unknown]
 libpopt0 1.16-10 [origin: unknown]
 libprocps3 1:3.3.9-1ubuntu8 [origin: unknown]
 libreadline6 6.3-8ubuntu1 [origin: unknown]
 libseccomp2 2.2.3-2ubuntu1 [origin: unknown]
 libselinux1 2.3-2build1 [origin: unknown]
 libsemanage-common 2.3-1build2 [origin: unknown]
 libsemanage1 2.3-1build2 [origin: unknown]
 libsepol1 2.3-2 [origin: unknown]
 libslang2 2.3.0-2ubuntu1 [origin: unknown]
 libsmartcols1 2.26.2-6ubuntu3 [origin: unknown]
 libss2 1.42.12-1ubuntu2 [origin: unknown]
 libstdc++6 5.2.1-22ubuntu2 [origin: unknown]
 libsystemd0 225-1ubuntu9.1 [origin: unknown]
 libtasn1-6 4.5-2ubuntu0.1 [origin: unknown]
 libtext-charwidth-perl 0.04-7build4 [origin: unknown]
 libtext-iconv-perl 1.7-5build3 [origin: unknown]
 libtext-wrapi18n-perl 0.06-7 [origin: unknown]
 libtinfo5 5.9+20150516-2ubuntu1 [origin: unknown]
 libudev1 225-1ubuntu9.1 [origin: unknown]
 libudisks2-0 2.1.6-2ubuntu1 [origin: unknown]
 libusb-0.1-4 2:0.1.12-27 [origin: unknown]
 libustr-1.0-1 1.0.4-5 [origin: unknown]
 libuuid1 2.26.2-6ubuntu3 [origin: unknown]
 libxml2 2.9.2+zdfsg1-4ubuntu0.3 [origin: unknown]
 lsb-base 4.1+Debian11ubuntu8 [origin: unknown]
 mount 2.26.2-6ubuntu3 [origin: unknown]
 multiarch-support 2.21-0ubuntu4.3 [origin: unknown]
 ntfs-3g 1:2014.2.15AR.3-3 [origin: unknown]
 parted 3.2-7ubuntu1 [origin: unknown]
 passwd 1:4.1.5.1-1.1ubuntu7 [origin: unknown]

[Kernel-packages] [Bug 1589379] Re: System frozen after resume, on Ubuntu 16.04 kernel 4.4.0-22

2016-06-07 Thread bastien

I just tried on the latest upstream kernel, 4.7-rc2, and the bug is
reproduced.

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

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

Title:
  System frozen after resume, on Ubuntu 16.04 kernel 4.4.0-22

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem on HP probook 450, with Radeon R7 M260/M265.
  The last kernel on which resume works is 4.4.3-040403-generic.
  I have the problem on all kernels above, including v4.6-rc7-wily.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bastien2164 F pulseaudio
  Date: Mon Jun  6 07:50:40 2016
  DuplicateSignature: suspend/resume:HP HP ProBook 450 G3:N78 Ver. 01.06
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=1888eb9c-89d7-4478-b4bc-1ce90d714377
  InstallationDate: Installed on 2016-05-05 (31 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterpreterPath: /usr/bin/python3.5
  MachineType: HP HP ProBook 450 G3
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=b919e8bc-92b0-4fcc-b9d3-0d8f38803a2b 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-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  Title: [HP HP ProBook 450 G3] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/18/2015
  dmi.bios.vendor: HP
  dmi.bios.version: N78 Ver. 01.06
  dmi.board.name: 8101
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.20
  dmi.chassis.asset.tag: 5CD6080WDD
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.06:bd12/18/2015:svnHP:pnHPProBook450G3:pvr:rvnHP:rn8101:rvrKBCVersion16.20:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 450 G3
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1589814] Re: zfs-dkms 0.6.5.6-0ubuntu9: zfs kernel module failed to build

2016-06-07 Thread Abram Daniel

upgrade continued on.

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu9: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  this summary was reported towards the end of upgrading ver. 15.10 to
  16.04lts.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-22-generic (x86_64)
   Tue Jun  7 02:13:31 EDT 2016
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-22-generic
  Date: Tue Jun  7 02:14:10 2016
  InstallationDate: Installed on 2015-12-20 (169 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageVersion: 0.6.5.6-0ubuntu9
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu9: zfs kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-06-07 (0 days ago)

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

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

[Kernel-packages] [Bug 1589814] [NEW] zfs-dkms 0.6.5.6-0ubuntu9: zfs kernel module failed to build

2016-06-07 Thread Abram Daniel

Public bug reported:

this summary was reported towards the end of upgrading ver. 15.10 to
16.04lts.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: zfs-dkms 0.6.5.6-0ubuntu9
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
Uname: Linux 4.2.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
DKMSBuildLog:
 DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-22-generic (x86_64)
 Tue Jun  7 02:13:31 EDT 2016
 make: *** No targets specified and no makefile found.  Stop.
DKMSKernelVersion: 4.4.0-22-generic
Date: Tue Jun  7 02:14:10 2016
InstallationDate: Installed on 2015-12-20 (169 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageVersion: 0.6.5.6-0ubuntu9
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: zfs-linux
Title: zfs-dkms 0.6.5.6-0ubuntu9: zfs kernel module failed to build
UpgradeStatus: Upgraded to xenial on 2016-06-07 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu9: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  this summary was reported towards the end of upgrading ver. 15.10 to
  16.04lts.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-22-generic (x86_64)
   Tue Jun  7 02:13:31 EDT 2016
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-22-generic
  Date: Tue Jun  7 02:14:10 2016
  InstallationDate: Installed on 2015-12-20 (169 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageVersion: 0.6.5.6-0ubuntu9
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu9: zfs kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-06-07 (0 days ago)

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

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

[Kernel-packages] [Bug 1589776] Re: Radeon R7 not work in ubuntu xenial

2016-06-07 Thread andy cao

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

** Description changed:

- lspci:Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz
- XT [Radeon R7 M260/M265 / M340/M360] (rev ff)
+ lspci:
+ VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)
+ Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon 
R7 M260/M265 / M340/M360] (rev ff)
  
  kernel:4.4.12-040412-generic #201606011712
  ubuntu xenial.
  
  [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 1 test failed 
(scratch(0xC040)=0xCAFEDEAD)
  [   18.514980] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 2 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   18.719097] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 3 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   18.923323] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 4 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   19.127705] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 5 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   19.331781] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 6 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   19.535642] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 7 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   19.739668] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 8 
test failed (scratch(0xC040)=0xCAFEDEAD)
  
- 
-  [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock 
ring 0 (-2).
+  [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock 
ring 0 (-2).
  [   26.229070] [drm:amdgpu_resume_kms [amdgpu]] *ERROR* amdgpu_resume failed 
(-2).
  [   26.229823] amdgpu :05:00.0: couldn't schedule ib
  [   26.230498] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   26.231173] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
- 
  
  amdgpu :05:00.0: couldn't schedule ib
  [   27.260411] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   27.260425] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   27.260428] amdgpu :05:00.0: couldn't schedule ib
  [   27.260438] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   27.260447] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   27.260572] amdgpu :05:00.0: couldn't schedule ib
  [   27.260583] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   27.260592] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550867] amdgpu :05:00.0: couldn't schedule ib
  [   28.550891] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.550908] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550912] amdgpu :05:00.0: couldn't schedule ib
  [   28.550926] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.550939] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550942] amdgpu :05:00.0: couldn't schedule ib
  [   28.550954] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.550967] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550969] amdgpu :05:00.0: couldn't schedule ib
  [   28.550980] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.550992] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550995] amdgpu :05:00.0: couldn't schedule ib
  [   28.551006] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551018] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.551021] amdgpu :05:00.0: couldn't schedule ib
  [   28.551032] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551044] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.551046] amdgpu :05:00.0: couldn't schedule ib
  [   28.551057] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551069] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.551072] amdgpu :05:00.0: couldn't schedule ib
  [   28.551083] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551095] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.551122] amdgpu :05:00.0: couldn't schedule ib
  [   28.551136] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551148] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.713622] amdgpu :05:00.0: couldn't schedule ib
  [   28.713646] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.713663] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.713667] amdgpu :05:00.0: couldn't schedule ib
  [   28.713681] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.713695] [drm:amd_sched_main [amdgpu]]

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

2016-06-07 Thread andy cao

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1589776/+attachment/4678624/+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/1589776

Title:
  Radeon R7 not work in ubuntu xenial

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  lspci:Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz
  XT [Radeon R7 M260/M265 / M340/M360] (rev ff)

  kernel:4.4.12-040412-generic #201606011712
  ubuntu xenial.

  [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 1 test failed 
(scratch(0xC040)=0xCAFEDEAD)
  [   18.514980] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 2 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   18.719097] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 3 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   18.923323] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 4 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   19.127705] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 5 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   19.331781] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 6 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   19.535642] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 7 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   19.739668] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 8 
test failed (scratch(0xC040)=0xCAFEDEAD)


   [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock 
ring 0 (-2).
  [   26.229070] [drm:amdgpu_resume_kms [amdgpu]] *ERROR* amdgpu_resume failed 
(-2).
  [   26.229823] amdgpu :05:00.0: couldn't schedule ib
  [   26.230498] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   26.231173] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!

  
  amdgpu :05:00.0: couldn't schedule ib
  [   27.260411] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   27.260425] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   27.260428] amdgpu :05:00.0: couldn't schedule ib
  [   27.260438] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   27.260447] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   27.260572] amdgpu :05:00.0: couldn't schedule ib
  [   27.260583] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   27.260592] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550867] amdgpu :05:00.0: couldn't schedule ib
  [   28.550891] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.550908] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550912] amdgpu :05:00.0: couldn't schedule ib
  [   28.550926] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.550939] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550942] amdgpu :05:00.0: couldn't schedule ib
  [   28.550954] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.550967] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550969] amdgpu :05:00.0: couldn't schedule ib
  [   28.550980] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.550992] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550995] amdgpu :05:00.0: couldn't schedule ib
  [   28.551006] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551018] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.551021] amdgpu :05:00.0: couldn't schedule ib
  [   28.551032] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551044] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.551046] amdgpu :05:00.0: couldn't schedule ib
  [   28.551057] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551069] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.551072] amdgpu :05:00.0: couldn't schedule ib
  [   28.551083] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551095] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.551122] amdgpu :05:00.0: couldn't schedule ib
  [   28.551136] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551148] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.713622] amdgpu :05:00.0: couldn't schedule ib
  [   28.713646] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.713663] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.713667] amdgpu :05:00.0: couldn't schedule ib
  [   28.713681] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [

[Kernel-packages] [Bug 1589776] Re: Radeon R7 not work in ubuntu xenial

2016-06-07 Thread andy cao

apport information

** Tags added: apport-collected

** Description changed:

  lspci:Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz
  XT [Radeon R7 M260/M265 / M340/M360] (rev ff)
  
  kernel:4.4.12-040412-generic #201606011712
  ubuntu xenial.
  
  [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 1 test failed 
(scratch(0xC040)=0xCAFEDEAD)
  [   18.514980] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 2 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   18.719097] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 3 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   18.923323] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 4 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   19.127705] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 5 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   19.331781] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 6 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   19.535642] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 7 
test failed (scratch(0xC040)=0xCAFEDEAD)
  [   19.739668] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 8 
test failed (scratch(0xC040)=0xCAFEDEAD)
  
  
   [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock 
ring 0 (-2).
  [   26.229070] [drm:amdgpu_resume_kms [amdgpu]] *ERROR* amdgpu_resume failed 
(-2).
  [   26.229823] amdgpu :05:00.0: couldn't schedule ib
  [   26.230498] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   26.231173] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  
  
  amdgpu :05:00.0: couldn't schedule ib
  [   27.260411] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   27.260425] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   27.260428] amdgpu :05:00.0: couldn't schedule ib
  [   27.260438] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   27.260447] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   27.260572] amdgpu :05:00.0: couldn't schedule ib
  [   27.260583] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   27.260592] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550867] amdgpu :05:00.0: couldn't schedule ib
  [   28.550891] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.550908] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550912] amdgpu :05:00.0: couldn't schedule ib
  [   28.550926] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.550939] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550942] amdgpu :05:00.0: couldn't schedule ib
  [   28.550954] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.550967] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550969] amdgpu :05:00.0: couldn't schedule ib
  [   28.550980] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.550992] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.550995] amdgpu :05:00.0: couldn't schedule ib
  [   28.551006] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551018] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.551021] amdgpu :05:00.0: couldn't schedule ib
  [   28.551032] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551044] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.551046] amdgpu :05:00.0: couldn't schedule ib
  [   28.551057] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551069] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.551072] amdgpu :05:00.0: couldn't schedule ib
  [   28.551083] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551095] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.551122] amdgpu :05:00.0: couldn't schedule ib
  [   28.551136] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.551148] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.713622] amdgpu :05:00.0: couldn't schedule ib
  [   28.713646] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.713663] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.713667] amdgpu :05:00.0: couldn't schedule ib
  [   28.713681] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.713695] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.713698] amdgpu :05:00.0: couldn't schedule ib
  [   28.713710] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [   28.713722] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [   28.713725] amdgpu :05:00.0: couldn't

< 1 2 3

201 - 241 of 241 matches

Mail list logo