date:20160708

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Lenovo Y700-17ISK: Firmware Bug: No valid trip found

Status in linux package in Ubuntu:
  Expired

Bug description:
  After installing and updating Xenial, dmesg notes:
  [0.847894] [Firmware Bug]: No valid trip found
  [0.848310] [Firmware Bug]: No valid trip found
  [0.848351] GHES: HEST is not enabled!

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

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

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

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

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

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

Status in linux package in Ubuntu:
  Expired

Bug description:
  This happens while upgrading from Ubuntu 14.04.4 to Ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  7 03:33 seq
   crw-rw 1 root audio 116, 33 May  7 03:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sat May  7 03:34:30 2016
  Ec2AMI: ami-009c
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: az2
  Ec2InstanceType: SSD.30
  Ec2Kernel: aki-0002
  Ec2Ramdisk: ari-0002
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=cf46d380-0e4b-4826-88dc-d612eb447071 ro quiet
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  Title: package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (0 days ago)
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.4:cvnBochs:ct1:cvr:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 2013.2.4
  dmi.sys.vendor: OpenStack Foundation

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

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

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

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

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

Status in linux package in Ubuntu:
  Expired

Bug description:
  Just browsing in youtube.
  Non of the videos crashed or silenced.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  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/pcmC0D0p:   cemd   1809 F...m pulseaudio
   /dev/snd/controlC0:  cemd   1809 F pulseaudio
  Date: Mon May  9 01:26:37 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=ba064f6a-1f62-41aa-ad5e-cc388077ffd9
  InstallationDate: Installed on 2016-05-05 (3 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 004: ID 04f3:2085 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 5986:0670 Acer, Inc 
   Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80R5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=e2e9cb44-e381-432e-8b3a-80d981c5129e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D3CN32WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Yoga 500-14ISK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 500-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrD3CN32WW:bd04/13/2016:svnLENOVO:pn80R5:pvrLenovoYoga500-14ISK:rvnLENOVO:rnLenovoYoga500-14ISK:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14ISK:
  dmi.product.name: 80R5
  dmi.product.version: Lenovo Yoga 500-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1579349] Re: package linux-libc-dev:amd64 4.4.0-21.37 [modified: usr/share/doc/linux-libc-dev/changelog.Debian.gz] failed to install/upgrade: package linux-libc-dev:amd64 is not

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package linux-libc-dev:amd64 4.4.0-21.37 [modified: usr/share/doc
  /linux-libc-dev/changelog.Debian.gz] failed to install/upgrade:
  package linux-libc-dev:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in linux package in Ubuntu:
  Expired

Bug description:
  package linux-libc-dev:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

  Errors were encountered while processing:  linux-libc-dev:amd64 E:
  Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-libc-dev:amd64 4.4.0-21.37 [modified: 
usr/share/doc/linux-libc-dev/changelog.Debian.gz]
  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:  vinita 1392 F pulseaudio
  Date: Sat May  7 14:42:46 2016
  Dependencies:
   
  ErrorMessage: package linux-libc-dev:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  HibernationDevice: RESUME=UUID=0f7d210b-41f2-4093-a0e3-d9717d92c116
  InstallationDate: Installed on 2016-05-03 (3 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp3s0no wireless extensions.
   
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=83a24732-f113-4df1-b67a-a6fd115b687c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3
  RfKill:
   
  SourcePackage: linux
  Title: package linux-libc-dev:amd64 4.4.0-21.37 [modified: 
usr/share/doc/linux-libc-dev/changelog.Debian.gz] failed to install/upgrade: 
package linux-libc-dev:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-CS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd10/22/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-CS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1600413] Re: Unclaimed register detected after reading register 0x65f10

** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.7-rc6 latest-bios-01.02.10

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

Title:
  Unclaimed register detected after reading register 0x65f10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Dell Precision 5510, the following appears in dmesg when booting on
  battery (no AC plugged in) and then plugging in the AC (TLP is used).
  This problem has been reported upstream
  (https://bugs.freedesktop.org/show_bug.cgi?id=96214), and even a patch
  has been suggested
  (https://bugs.freedesktop.org/show_bug.cgi?id=95646) which does not
  work however.

  There is a related launchpad bug against mainline kernel
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586046).

  This problem occurs on:
  - 4.4.0-28-generic
  - 4.6.3 (mainline PPA)
  - 4.7rc6 (compiled from Linus' tree) 

  [ +15.441606] [ cut here ]
  [  +0.32] WARNING: CPU: 3 PID: 1959 at 
/build/linux-BvkamA/linux-4.4.0/ubuntu/i915/intel_uncore.c:649 
__unclaimed_reg_debug+0x80/0x90 [i915_bpo]()
  [  +0.01] Unclaimed register detected after reading register 0x65f10
  [  +0.01] Modules linked in: drbg ansi_cprng ctr ccm nvram msr uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common 
videodev media vmw_vsock_vmci_transport vsock vmw_vmci uhid rfcomm btusb btrtl 
bnep arc4 binfmt_misc snd_hda_codec_hdmi dell_led snd_hda_codec_realtek iwlmvm 
snd_hda_codec_generic nls_iso8859_1 mac80211 dell_wmi sparse_keymap dell_rbtn 
dell_laptop dcdbas snd_hda_intel dell_smm_hwmon snd_hda_codec mxm_wmi iwlwifi 
intel_rapl snd_hda_core x86_pkg_temp_thermal intel_powerclamp snd_hwdep 
kvm_intel rtsx_pci_ms cfg80211 memstick kvm snd_pcm irqbypass snd_seq_midi 
crct10dif_pclmul crc32_pclmul snd_seq_midi_event aesni_intel aes_x86_64 lrw 
gf128mul snd_rawmidi glue_helper ablk_helper cryptd snd_seq snd_seq_device 
snd_timer joydev input_leds serio_raw snd soundcore
  [  +0.38]  idma64 mei_me virt_dma mei processor_thermal_device shpchp 
intel_lpss_pci intel_soc_dts_iosf hci_uart btbcm btqca btintel bluetooth 
int3403_thermal intel_lpss_acpi intel_lpss dell_smo8800 int3400_thermal wmi 
acpi_thermal_rel int3402_thermal acpi_pad int340x_thermal_zone acpi_als 
kfifo_buf mac_hid industrialio coretemp parport_pc ppdev lp parport autofs4 
rtsx_pci_sdmmc i915_bpo intel_ips i2c_algo_bit drm_kms_helper syscopyarea 
psmouse sysfillrect sysimgblt fb_sys_fops drm nvme ahci rtsx_pci libahci 
i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes
  [  +0.16] CPU: 3 PID: 1959 Comm: tlp Not tainted 4.4.0-28-generic 
#47-Ubuntu
  [  +0.01] Hardware name: Dell Inc. Precision 5510/08R8KJ, BIOS 01.02.10 
06/30/2016
  [  +0.01]  0086 c4023a8c 8800283b7aa0 
813eb1a3
  [  +0.01]  8800283b7ae8 c028b868 8800283b7ad8 
81081102
  [  +0.01]   0001 00065f10 
8808918b0080
  [  +0.01] Call Trace:
  [  +0.04]  [] dump_stack+0x63/0x90
  [  +0.02]  [] warn_slowpath_common+0x82/0xc0
  [  +0.01]  [] warn_slowpath_fmt+0x5c/0x80
  [  +0.03]  [] ? pci_conf1_write+0xb8/0xf0
  [  +0.11]  [] __unclaimed_reg_debug+0x80/0x90 [i915_bpo]
  [  +0.10]  [] gen9_read32+0x35e/0x390 [i915_bpo]
  [  +0.11]  [] 
i915_audio_component_codec_wake_override+0x39/0xb0 [i915_bpo]
  [  +0.04]  [] snd_hdac_set_codec_wakeup+0x3f/0xa0 
[snd_hda_core]
  [  +0.01]  [] azx_runtime_resume+0x187/0x1b0 
[snd_hda_intel]
  [  +0.02]  [] pci_pm_runtime_resume+0x7b/0xa0
  [  +0.02]  [] __rpm_callback+0x33/0x70
  [  +0.01]  [] ? pci_restore_standard_config+0x40/0x40
  [  +0.01]  [] rpm_callback+0x24/0x80
  [  +0.01]  [] ? pci_restore_standard_config+0x40/0x40
  [  +0.01]  [] rpm_resume+0x497/0x6a0
  [  +0.02]  [] ? mntput+0x24/0x40
  [  +0.02]  [] ? terminate_walk+0xbd/0xd0
  [  +0.01]  [] rpm_resume+0x2e1/0x6a0
  [  +0.01]  [] ? rpm_check_suspend_allowed+0x6e/0xb0
  [  +0.01]  [] ? rpm_idle+0x23/0x250
  [  +0.02]  [] pm_runtime_forbid+0x43/0x60
  [  +0.04]  [] snd_hda_set_power_save+0x54/0xc0 
[snd_hda_codec]
  [  +0.01]  [] param_set_xint+0x7f/0xa0 [snd_hda_intel]
  [  +0.02]  [] param_attr_store+0x61/0xc0
  [  +0.01]  [] module_attr_store+0x1e/0x30
  [  +0.02]  [] sysfs_kf_write+0x37/0x40
  [  +0.01]  [] kernfs_fop_write+0x11d/
  [  +0.02]  [] __vfs_write+0x18/0x40
  [  +0.01]  [] vfs_write+0xa9/0x1a0
  [  +0.01]  [] ? set_close_on_exec+0x35/0x70
  [  +0.02]  [] SyS_write+0x55/0xc0
  [  +0.01]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [  +0.01] ---[ end trace 1f4aae93fd1d0302 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature:

[Kernel-packages] [Bug 1578015] Re: does not power off

Lauren Weinstein, this bug report is being closed due to your last
comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578015/comments/10
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

Title:
  does not power off

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Yet another of the annoying "system hangs at shutdown" bug reports. A
  fresh complete install of 16.04. Just like the others, gets down to:

  Reached target shutdown

  then stops. I've tried all the workarounds discussed, including
  swapoff -a, before shutdown attempt, etc. No joy. Have to hold power
  switch for hard shutdown very time.

  One observation of possible value. I also very recently installed
  16.04 server on two other identical boxes. Neither of them exhibit
  this problem and both shut down cleanly. Only this system, which is a
  16.04 desktop version -- again on an identical box -- is having this
  problem.

  Frankly, it's stuff like this that makes my efforts to move ordinary
  consumers over to Linux very difficult!

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

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

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

This change was made by a bot.

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

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

Title:
  Unclaimed register detected after reading register 0x65f10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Dell Precision 5510, the following appears in dmesg when booting on
  battery (no AC plugged in) and then plugging in the AC (TLP is used).
  This problem has been reported upstream
  (https://bugs.freedesktop.org/show_bug.cgi?id=96214), and even a patch
  has been suggested
  (https://bugs.freedesktop.org/show_bug.cgi?id=95646) which does not
  work however.

  There is a related launchpad bug against mainline kernel
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586046).

  This problem occurs on:
  - 4.4.0-28-generic
  - 4.6.3 (mainline PPA)
  - 4.7rc6 (compiled from Linus' tree) 

  [ +15.441606] [ cut here ]
  [  +0.32] WARNING: CPU: 3 PID: 1959 at 
/build/linux-BvkamA/linux-4.4.0/ubuntu/i915/intel_uncore.c:649 
__unclaimed_reg_debug+0x80/0x90 [i915_bpo]()
  [  +0.01] Unclaimed register detected after reading register 0x65f10
  [  +0.01] Modules linked in: drbg ansi_cprng ctr ccm nvram msr uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common 
videodev media vmw_vsock_vmci_transport vsock vmw_vmci uhid rfcomm btusb btrtl 
bnep arc4 binfmt_misc snd_hda_codec_hdmi dell_led snd_hda_codec_realtek iwlmvm 
snd_hda_codec_generic nls_iso8859_1 mac80211 dell_wmi sparse_keymap dell_rbtn 
dell_laptop dcdbas snd_hda_intel dell_smm_hwmon snd_hda_codec mxm_wmi iwlwifi 
intel_rapl snd_hda_core x86_pkg_temp_thermal intel_powerclamp snd_hwdep 
kvm_intel rtsx_pci_ms cfg80211 memstick kvm snd_pcm irqbypass snd_seq_midi 
crct10dif_pclmul crc32_pclmul snd_seq_midi_event aesni_intel aes_x86_64 lrw 
gf128mul snd_rawmidi glue_helper ablk_helper cryptd snd_seq snd_seq_device 
snd_timer joydev input_leds serio_raw snd soundcore
  [  +0.38]  idma64 mei_me virt_dma mei processor_thermal_device shpchp 
intel_lpss_pci intel_soc_dts_iosf hci_uart btbcm btqca btintel bluetooth 
int3403_thermal intel_lpss_acpi intel_lpss dell_smo8800 int3400_thermal wmi 
acpi_thermal_rel int3402_thermal acpi_pad int340x_thermal_zone acpi_als 
kfifo_buf mac_hid industrialio coretemp parport_pc ppdev lp parport autofs4 
rtsx_pci_sdmmc i915_bpo intel_ips i2c_algo_bit drm_kms_helper syscopyarea 
psmouse sysfillrect sysimgblt fb_sys_fops drm nvme ahci rtsx_pci libahci 
i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes
  [  +0.16] CPU: 3 PID: 1959 Comm: tlp Not tainted 4.4.0-28-generic 
#47-Ubuntu
  [  +0.01] Hardware name: Dell Inc. Precision 5510/08R8KJ, BIOS 01.02.10 
06/30/2016
  [  +0.01]  0086 c4023a8c 8800283b7aa0 
813eb1a3
  [  +0.01]  8800283b7ae8 c028b868 8800283b7ad8 
81081102
  [  +0.01]   0001 00065f10 
8808918b0080
  [  +0.01] Call Trace:
  [  +0.04]  [] dump_stack+0x63/0x90
  [  +0.02]  [] warn_slowpath_common+0x82/0xc0
  [  +0.01]  [] warn_slowpath_fmt+0x5c/0x80
  [  +0.03]  [] ? pci_conf1_write+0xb8/0xf0
  [  +0.11]  [] __unclaimed_reg_debug+0x80/0x90 [i915_bpo]
  [  +0.10]  [] gen9_read32+0x35e/0x390 [i915_bpo]
  [  +0.11]  [] 
i915_audio_component_codec_wake_override+0x39/0xb0 [i915_bpo]
  [  +0.04]  [] snd_hdac_set_codec_wakeup+0x3f/0xa0 
[snd_hda_core]
  [  +0.01]  [] azx_runtime_resume+0x187/0x1b0 
[snd_hda_intel]
  [  +0.02]  [] pci_pm_runtime_resume+0x7b/0xa0
  [  +0.02]  [] __rpm_callback+0x33/0x70
  [  +0.01]  [] ? pci_restore_standard_config+0x40/0x40
  [  +0.01]  [] rpm_callback+0x24/0x80
  [  +0.01]  [] ? pci_restore_standard_config+0x40/0x40
  [  +0.01]  [] rpm_resume+0x497/0x6a0
  [  +0.02]  [] ? mntput+0x24/0x40
  [  +0.02]  [] ? terminate_walk+0xbd/0xd0
  [  +0.01]  [] rpm_resume+0x2e1/0x6a0
  [  +0.01]  [] ? rpm_check_suspend_allowed+0x6e/0xb0
  [  +0.01]  [] ? rpm_idle+0x23/0x250
  [  +0.02]  [] pm_runtime_forbid+0x43/0x60
  [  +0.04]  [] snd_hda_set_power_save+0x54/0xc0 
[snd_hda_codec]
  [  +0.01]  [] param_set_xint+0x7f/0xa0 [snd_hda_intel]
  [  +0.02]  [] param_attr_store+0x61/0xc0
  [  +0.01]  [] module_attr_store+0x1e/0x30
  [  +0.02]  [] sysfs_kf_write+0x37/0x40
  [  +0.01]  [] kernfs_fop_write+0x11d/
  [  +0.02]  [] __vfs_write+0x18/0x40
  [  +0.01]  [] vfs_write+0xa9/0x1a0
  [  +0.01]  [] ? set_close_on_exec+0x35/0x70
  [  +0.02]  [] SyS_write+0x55/0xc0
  [  +0.01]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [  +0.01] ---[ end trace 1f4aae93fd1d0302 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu

[Kernel-packages] [Bug 1586046] Re: Unclaimed register detected after reading register 0x65f10

Ok, here you go:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1600413

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

Title:
  Unclaimed register detected after reading register 0x65f10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After booting to newest kernel, I see following in dmesg:

  [   28.156951] WARNING: CPU: 3 PID: 2005 at 
/build/linux-FvcHlK/linux-4.4.0/ubuntu/i915/intel_uncore.c:649 
__unclaimed_reg_debug+0x80/0x90 [i915_bpo]()
  [   28.156953] Unclaimed register detected after reading register 0x65f10

  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/pcmC0D3p:   cromo  1941 F...m pulseaudio
   /dev/snd/controlC0:  cromo  1941 F pulseaudio
   /dev/snd/seq:timidity   1020 F timidity
  Date: Thu May 26 09:46:38 2016
  HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df
  InstallationDate: Installed on 2013-04-24 (1128 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0c45:670c Microdia 
   Bus 001 Device 004: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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-03-23 (64 days ago)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0VM5NC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1600413] [NEW] Unclaimed register detected after reading register 0x65f10

Public bug reported:

On Dell Precision 5510, the following appears in dmesg when booting on
battery (no AC plugged in) and then plugging in the AC (TLP is used).
This problem has been reported upstream
(https://bugs.freedesktop.org/show_bug.cgi?id=96214), and even a patch
has been suggested (https://bugs.freedesktop.org/show_bug.cgi?id=95646)
which does not work however.

There is a related launchpad bug against mainline kernel
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586046).

This problem occurs on:
- 4.4.0-28-generic
- 4.6.3 (mainline PPA)
- 4.7rc6 (compiled from Linus' tree) 

[ +15.441606] [ cut here ]
[  +0.32] WARNING: CPU: 3 PID: 1959 at 
/build/linux-BvkamA/linux-4.4.0/ubuntu/i915/intel_uncore.c:649 
__unclaimed_reg_debug+0x80/0x90 [i915_bpo]()
[  +0.01] Unclaimed register detected after reading register 0x65f10
[  +0.01] Modules linked in: drbg ansi_cprng ctr ccm nvram msr uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common 
videodev media vmw_vsock_vmci_transport vsock vmw_vmci uhid rfcomm btusb btrtl 
bnep arc4 binfmt_misc snd_hda_codec_hdmi dell_led snd_hda_codec_realtek iwlmvm 
snd_hda_codec_generic nls_iso8859_1 mac80211 dell_wmi sparse_keymap dell_rbtn 
dell_laptop dcdbas snd_hda_intel dell_smm_hwmon snd_hda_codec mxm_wmi iwlwifi 
intel_rapl snd_hda_core x86_pkg_temp_thermal intel_powerclamp snd_hwdep 
kvm_intel rtsx_pci_ms cfg80211 memstick kvm snd_pcm irqbypass snd_seq_midi 
crct10dif_pclmul crc32_pclmul snd_seq_midi_event aesni_intel aes_x86_64 lrw 
gf128mul snd_rawmidi glue_helper ablk_helper cryptd snd_seq snd_seq_device 
snd_timer joydev input_leds serio_raw snd soundcore
[  +0.38]  idma64 mei_me virt_dma mei processor_thermal_device shpchp 
intel_lpss_pci intel_soc_dts_iosf hci_uart btbcm btqca btintel bluetooth 
int3403_thermal intel_lpss_acpi intel_lpss dell_smo8800 int3400_thermal wmi 
acpi_thermal_rel int3402_thermal acpi_pad int340x_thermal_zone acpi_als 
kfifo_buf mac_hid industrialio coretemp parport_pc ppdev lp parport autofs4 
rtsx_pci_sdmmc i915_bpo intel_ips i2c_algo_bit drm_kms_helper syscopyarea 
psmouse sysfillrect sysimgblt fb_sys_fops drm nvme ahci rtsx_pci libahci 
i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes
[  +0.16] CPU: 3 PID: 1959 Comm: tlp Not tainted 4.4.0-28-generic #47-Ubuntu
[  +0.01] Hardware name: Dell Inc. Precision 5510/08R8KJ, BIOS 01.02.10 
06/30/2016
[  +0.01]  0086 c4023a8c 8800283b7aa0 
813eb1a3
[  +0.01]  8800283b7ae8 c028b868 8800283b7ad8 
81081102
[  +0.01]   0001 00065f10 
8808918b0080
[  +0.01] Call Trace:
[  +0.04]  [] dump_stack+0x63/0x90
[  +0.02]  [] warn_slowpath_common+0x82/0xc0
[  +0.01]  [] warn_slowpath_fmt+0x5c/0x80
[  +0.03]  [] ? pci_conf1_write+0xb8/0xf0
[  +0.11]  [] __unclaimed_reg_debug+0x80/0x90 [i915_bpo]
[  +0.10]  [] gen9_read32+0x35e/0x390 [i915_bpo]
[  +0.11]  [] 
i915_audio_component_codec_wake_override+0x39/0xb0 [i915_bpo]
[  +0.04]  [] snd_hdac_set_codec_wakeup+0x3f/0xa0 
[snd_hda_core]
[  +0.01]  [] azx_runtime_resume+0x187/0x1b0 
[snd_hda_intel]
[  +0.02]  [] pci_pm_runtime_resume+0x7b/0xa0
[  +0.02]  [] __rpm_callback+0x33/0x70
[  +0.01]  [] ? pci_restore_standard_config+0x40/0x40
[  +0.01]  [] rpm_callback+0x24/0x80
[  +0.01]  [] ? pci_restore_standard_config+0x40/0x40
[  +0.01]  [] rpm_resume+0x497/0x6a0
[  +0.02]  [] ? mntput+0x24/0x40
[  +0.02]  [] ? terminate_walk+0xbd/0xd0
[  +0.01]  [] rpm_resume+0x2e1/0x6a0
[  +0.01]  [] ? rpm_check_suspend_allowed+0x6e/0xb0
[  +0.01]  [] ? rpm_idle+0x23/0x250
[  +0.02]  [] pm_runtime_forbid+0x43/0x60
[  +0.04]  [] snd_hda_set_power_save+0x54/0xc0 
[snd_hda_codec]
[  +0.01]  [] param_set_xint+0x7f/0xa0 [snd_hda_intel]
[  +0.02]  [] param_attr_store+0x61/0xc0
[  +0.01]  [] module_attr_store+0x1e/0x30
[  +0.02]  [] sysfs_kf_write+0x37/0x40
[  +0.01]  [] kernfs_fop_write+0x11d/
[  +0.02]  [] __vfs_write+0x18/0x40
[  +0.01]  [] vfs_write+0xa9/0x1a0
[  +0.01]  [] ? set_close_on_exec+0x35/0x70
[  +0.02]  [] SyS_write+0x55/0xc0
[  +0.01]  [] entry_SYSCALL_64_fastpath+0x16/0x71
[  +0.01] ---[ end trace 1f4aae93fd1d0302 ]---

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  czikus 1586 F pulseaudio
CurrentDesktop: KDE
Date: Fri Jul  8 19:23:48 2016
InstallationDate: Installed on 2016-06-25 (13 days ago)
InstallationMedia: Kubuntu 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

[Kernel-packages] [Bug 1479322] Re: Acer Aspire M5 481T consuming power while turned off! Battery drains with system halted!

2016-07-08 Thread Dngrsone

I used this site to disable WOL before shutdown:
http://www.hecticgeek.com/2012/09/disabling-wake-on-lan-in-ubuntu-might-
save-a-tiny-bit-of-power-on-your-laptop/

This did not work.

I lose about 1% battery an hour when shutting the machine down from
Linux.  WOL is off in UEFI, and Windows shutdown works the way it
should.

My machine uses a Radeon R9 M265X graphics chip, so I'm not sure it's
only a video driver issue.

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

Title:
  Acer Aspire M5 481T consuming power while turned off! Battery drains
  with system halted!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Guys, I'm facing this problem just since I installed Ubuntu 15.04. The
  laptop came with Windows 8 installed and this problem didn't exists
  there. Everything seems to run just fine, but when I turn it off with
  50% of battery for instance there is no energy after some hours and I
  can feel that the laptop is a little hot, but there is no noise like
  anything was on.. What could be happening? I've searched for some
  solution, already tried to include some options in grub config like
  noapic, nolapic, irqpoll, acpi=off and others without solution. Also
  tried to check WOL but it's ok too. What could be happening? How to
  solve this problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-25-generic 3.19.0-25.26
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wsjunior   1946 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 29 08:37:36 2015
  HibernationDevice: RESUME=UUID=01156367-a677-486c-bf79-7d29dd6ca8a7
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 1bcf:2c32 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire M5-481T
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash intel_pstate=enable 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-25-generic N/A
   linux-backports-modules-3.19.0-25-generic  N/A
   linux-firmware 1.143.2
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Arquivo ou diretório não encontrado: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: MA40_HX
  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.:bvrV2.22:bd04/15/2013:svnAcer:pnAspireM5-481T:pvrV2.22:rvnAcer:rnMA40_HX:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire M5-481T
  dmi.product.version: V2.22
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1578015] Re: does not power off

2016-07-08 Thread Lauren Weinstein

This bug appears to now be fixed for me, at least in initial testing.

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

Title:
  does not power off

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Yet another of the annoying "system hangs at shutdown" bug reports. A
  fresh complete install of 16.04. Just like the others, gets down to:

  Reached target shutdown

  then stops. I've tried all the workarounds discussed, including
  swapoff -a, before shutdown attempt, etc. No joy. Have to hold power
  switch for hard shutdown very time.

  One observation of possible value. I also very recently installed
  16.04 server on two other identical boxes. Neither of them exhibit
  this problem and both shut down cleanly. Only this system, which is a
  16.04 desktop version -- again on an identical box -- is having this
  problem.

  Frankly, it's stuff like this that makes my efforts to move ordinary
  consumers over to Linux very difficult!

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

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

[Kernel-packages] [Bug 1586046] Re: Unclaimed register detected after reading register 0x65f10

Czikus, it will help immensely if you filed a new report with the Ubuntu 
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.

** Tags removed: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.6 kernel-bug-exists-upstream-4.7-rc6

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

Title:
  Unclaimed register detected after reading register 0x65f10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After booting to newest kernel, I see following in dmesg:

  [   28.156951] WARNING: CPU: 3 PID: 2005 at 
/build/linux-FvcHlK/linux-4.4.0/ubuntu/i915/intel_uncore.c:649 
__unclaimed_reg_debug+0x80/0x90 [i915_bpo]()
  [   28.156953] Unclaimed register detected after reading register 0x65f10

  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/pcmC0D3p:   cromo  1941 F...m pulseaudio
   /dev/snd/controlC0:  cromo  1941 F pulseaudio
   /dev/snd/seq:timidity   1020 F timidity
  Date: Thu May 26 09:46:38 2016
  HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df
  InstallationDate: Installed on 2013-04-24 (1128 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0c45:670c Microdia 
   Bus 001 Device 004: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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-03-23 (64 days ago)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0VM5NC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1573386] Re: Dell XPS 13 9350: Unclaimed register detected after reading register 0x65f10

*** This bug is a duplicate of bug 1586046 ***
https://bugs.launchpad.net/bugs/1586046

It has been reported upstream as well:
https://bugs.freedesktop.org/show_bug.cgi?id=96214
https://bugs.freedesktop.org/show_bug.cgi?id=95646

** Bug watch added: freedesktop.org Bugzilla #96214
   https://bugs.freedesktop.org/show_bug.cgi?id=96214

** Bug watch added: freedesktop.org Bugzilla #95646
   https://bugs.freedesktop.org/show_bug.cgi?id=95646

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

Title:
  Dell XPS 13 9350: Unclaimed register detected after reading register
  0x65f10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Connecting Dell XPS 13 9350 to power outlet causes kernel warn: 
  Unclaimed register detected after reading register 0x65f10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cromo  2664 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Apr 22 00:24:22 2016
  HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df
  InstallationDate: Installed on 2013-04-24 (1094 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-03-23 (30 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 0VM5NC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1584284] Re: Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Roger Merritt, could you please capture the full failed boot output via
https://wiki.ubuntu.com/DebuggingKernelBoot ?

** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.4.13

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

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

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:

[Kernel-packages] [Bug 1586046] Re: Unclaimed register detected after reading register 0x65f10

It has been reported upstream as well:
https://bugs.freedesktop.org/show_bug.cgi?id=96214
https://bugs.freedesktop.org/show_bug.cgi?id=95646

** Bug watch added: freedesktop.org Bugzilla #95646
   https://bugs.freedesktop.org/show_bug.cgi?id=95646

** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.6
kernel-bug-exists-upstream-4.7-rc6

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

Title:
  Unclaimed register detected after reading register 0x65f10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After booting to newest kernel, I see following in dmesg:

  [   28.156951] WARNING: CPU: 3 PID: 2005 at 
/build/linux-FvcHlK/linux-4.4.0/ubuntu/i915/intel_uncore.c:649 
__unclaimed_reg_debug+0x80/0x90 [i915_bpo]()
  [   28.156953] Unclaimed register detected after reading register 0x65f10

  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/pcmC0D3p:   cromo  1941 F...m pulseaudio
   /dev/snd/controlC0:  cromo  1941 F pulseaudio
   /dev/snd/seq:timidity   1020 F timidity
  Date: Thu May 26 09:46:38 2016
  HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df
  InstallationDate: Installed on 2013-04-24 (1128 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0c45:670c Microdia 
   Bus 001 Device 004: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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-03-23 (64 days ago)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0VM5NC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1584284] [NEW] Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

You have been subscribed to a public bug:

I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD A10-5800K 
AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no graphics card -- 
the Radeon HD 7660D graphics are done by the CPU. When I try to boot I get an 
error message, "ERROR: no UMS support in radeon module." When I edit the boot 
command line to add the parameter 'nomodeset' I first get an error message, "No 
UMS support on radeon module," then the familiar aubergine background with the 
ubuntu logo and the five dots below it changing from white to red and back 
again. After twenty or thirty seconds the background goes to black, I get the 
error message "No UMS support in radeon module," and the ubuntu logo disappears 
but the five dots continue. After another twenty or thirty seconds of that the 
screen clears, at the top is a line: "ubuntu 16.04 ubuntu LTS tty1," below that 
the line "ubuntu login:" and after a second or less the screen goes black and I 
can't do anything except reboot. I've tried old Live 
 CDs, from 10.10 to 15.10, and they all boot fine.
--- 
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DistUpgraded: Fresh install
DistroCodename: wily
DistroRelease: Ubuntu 15.10
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] 
[1002:9901]
InstallationDate: Installed on 2016-06-07 (27 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
Package: xorg 1:7.7+7ubuntu4
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
Tags:  wily ubuntu compiz-0.9
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.2.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
_MarkForUpload: True
dmi.bios.date: 03/18/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A75M-HD2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Tue Jul  5 00:55:16 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB Optical Wheel Mouse MOUSE, id 8
 inputLogitech USB Keyboard KEYBOARD, id 9
 inputLogitech USB Keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9.1
xserver.video_driver: radeon

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


** Tags: apport-collected bot-comment compiz-0.9 kernel-fixed-upstream 
kernel-fixed-upstream-4.4.13 latest-bios-f4 regression-release ubuntu wily 
xenial yakkety
-- 
Ubuntu 16.04 LiveCD does not boot on AMD A10 chip
https://bugs.launchpad.net/bugs/1584284
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1573386] Re: Dell XPS 13 9350: Unclaimed register detected after reading register 0x65f10

*** This bug is a duplicate of bug 1586046 ***
https://bugs.launchpad.net/bugs/1586046

I confirm that this problem exists on Dell Precision 5510 with kernels
4.6.3 and 4.7rc6. Also
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586046 looks like
a duplicate of this bug.

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

Title:
  Dell XPS 13 9350: Unclaimed register detected after reading register
  0x65f10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Connecting Dell XPS 13 9350 to power outlet causes kernel warn: 
  Unclaimed register detected after reading register 0x65f10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cromo  2664 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Apr 22 00:24:22 2016
  HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df
  InstallationDate: Installed on 2013-04-24 (1094 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-03-23 (30 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 0VM5NC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1586046] Re: Unclaimed register detected after reading register 0x65f10

I confirm that this problem exists on Dell Precision 5510 with kernels
4.6.3 and 4.7rc6. Also
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573386 looks like
a duplicate of this bug.

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

Title:
  Unclaimed register detected after reading register 0x65f10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After booting to newest kernel, I see following in dmesg:

  [   28.156951] WARNING: CPU: 3 PID: 2005 at 
/build/linux-FvcHlK/linux-4.4.0/ubuntu/i915/intel_uncore.c:649 
__unclaimed_reg_debug+0x80/0x90 [i915_bpo]()
  [   28.156953] Unclaimed register detected after reading register 0x65f10

  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/pcmC0D3p:   cromo  1941 F...m pulseaudio
   /dev/snd/controlC0:  cromo  1941 F pulseaudio
   /dev/snd/seq:timidity   1020 F timidity
  Date: Thu May 26 09:46:38 2016
  HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df
  InstallationDate: Installed on 2013-04-24 (1128 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0c45:670c Microdia 
   Bus 001 Device 004: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   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-03-23 (64 days ago)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0VM5NC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1600371] Re: Gnome freezes for some seconds on simultaneous touch and stylus input (palm rejection fails)

apport information

** Tags added: apport-collected xenial

** Description changed:

  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as an
  inductive screen for styluses. When I rest my palm on the screen and
  then hover my stylus above the screen so that the stylus is recognized
  and the mouse pointer follows it, and then move the stylus around Gnome
  seems to freeze for some seconds. The duration of the freeze is
  proportional to the time the notebook received simultaneous input from
  the two methods.
  
  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.
  
  I do not need to touch the screen with the stylus for the bug to occur.
  The bug occurs also when I actually touch the screen with the stylus.
  
  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.
  
  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.
  
  I attach a script as a workaround solution.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
+  /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 16.04
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
+ InstallationDate: Installed on 2016-03-19 (111 days ago)
+ InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
+ MachineType: LENOVO 20C0003SFR
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/usr/bin/zsh
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-28-generic N/A
+  linux-backports-modules-4.4.0-28-generic  N/A
+  linux-firmware1.157.1
+ Tags:  xenial
+ Uname: Linux 4.4.0-28-generic x86_64
+ UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 04/29/2016
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: B0ET33WW (1.20 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20C0003SFR
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0E50510 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Not Available
+ dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
+ dmi.product.name: 20C0003SFR
+ dmi.product.version: ThinkPad S1 Yoga
+ dmi.sys.vendor: LENOVO

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:

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

apport information

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1600371] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1600371/+attachment/4697693/+files/Lsusb.txt

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 759725] Re: The kernel is no longer readable by non-root users

** No longer affects: hobbit-plugins (Ubuntu)

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

Title:
  The kernel is no longer readable by non-root users

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  The mode of the latest kernel has changed so it is no longer readable
  by non-root users:

  -rw-r--r-- 1 root root 4336016 2010-10-17 01:37 
/boot/vmlinuz-2.6.35-22-generic
  -rw-r--r-- 1 root root 4336912 2010-11-24 12:46 
/boot/vmlinuz-2.6.35-23-generic
  -rw-r--r-- 1 root root 4523072 2011-03-08 18:47 /boot/vmlinuz-2.6.38-6-generic
  -rw--- 1 root root 4523936 2011-04-11 05:24 /boot/vmlinuz-2.6.38-8-generic

  This prevents people from using this kernel to boot qemu
  virtual machines as non-root.

  Please change the mode back to make the kernel readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: aplay: device_list:240: no soundcards found...
  Architecture: amd64
  ArecordDevices: arecord: device_list:240: no soundcards found...
  CRDA: Error: [Errno 2] No such file or directory
  Date: Wed Apr 13 13:05:01 2011
  HibernationDevice: RESUME=UUID=112bf9c4-620e-441f-abb3-aeac6aa15294
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  PciMultimedia:
   
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=1efa0b67-17df-484e-980c-8544fa2149fe ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-2.6.35-22-generic N/A
   linux-backports-modules-2.6.35-22-generic  N/A
   linux-firmware 1.50
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.0.0PC:cvnRedHat:ct1:cvr:
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.0.0 PC
  dmi.sys.vendor: Red Hat

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

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

[Kernel-packages] [Bug 752352] Re: /boot/vmlinuz-2.6.38-8-virtual has 600 perms

*** This bug is a duplicate of bug 759725 ***
https://bugs.launchpad.net/bugs/759725

** Branch unlinked: lp:~ubuntu-on-ec2/vmbuilder/automated-ec2-builds

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

Title:
  /boot/vmlinuz-2.6.38-8-virtual has 600 perms

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the latest kernel package installs file /boot/vmlinuz-2.6.38-8-virtual as 
  $ ls -l /boot/*-2.6.38-7-* /boot/*-2.6.38-8-*
  -rw-r--r-- 1 root root  739487 2011-03-26 02:09 /boot/abi-2.6.38-7-virtual
  -rw-r--r-- 1 root root  739487 2011-04-06 02:04 /boot/abi-2.6.38-8-virtual
  -rw-r--r-- 1 root root  137173 2011-03-26 02:09 /boot/config-2.6.38-7-virtual
  -rw-r--r-- 1 root root  137194 2011-04-06 02:04 /boot/config-2.6.38-8-virtual
  -rw-r--r-- 1 root root 4255956 2011-04-05 01:37 
/boot/initrd.img-2.6.38-7-virtual
  -rw-r--r-- 1 root root 4257226 2011-04-06 09:56 
/boot/initrd.img-2.6.38-8-virtual
  -rw--- 1 root root 2155387 2011-03-26 02:09 
/boot/System.map-2.6.38-7-virtual
  -rw--- 1 root root 2155052 2011-04-06 02:04 
/boot/System.map-2.6.38-8-virtual
  -rw--- 1 root root1216 2011-03-26 02:12 
/boot/vmcoreinfo-2.6.38-7-virtual
  -rw--- 1 root root1216 2011-04-06 02:07 
/boot/vmcoreinfo-2.6.38-8-virtual
  -rw-r--r-- 1 root root 4664784 2011-03-26 02:09 /boot/vmlinuz-2.6.38-7-virtual
  -rw--- 1 root root 4664784 2011-04-06 02:04 /boot/vmlinuz-2.6.38-8-virtual

  The only change of permissions in /boot from 2.6.38-7 -> 2.6.38-8 is
  perms on the vmlinuz

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-virtual 2.6.38-8.41
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: User Name 2.6.38-7.39-virtual 2.6.38
  Uname: Linux 2.6.38-7-virtual i686
  AlsaDevices:
   total 0
   crw--- 1 root root 116,  1 2011-04-06 09:51 seq
   crw--- 1 root root 116, 33 2011-04-06 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [  322.838676] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
   [  322.842660] SGI XFS Quota Management subsystem
   [  322.922050] Btrfs loaded
  Date: Wed Apr  6 09:59:24 2011
  Ec2AMI: ami-281fe241
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t1.micro
  Ec2Kernel: aki-407d9529
  Ec2Ramdisk: unavailable
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=LABEL=uec-rootfs ro console=hvc0
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2016-07-08 Thread bastien

Bug report created:
https://bugs.freedesktop.org/show_bug.cgi?id=96866

** Bug watch added: freedesktop.org Bugzilla #96866
   https://bugs.freedesktop.org/show_bug.cgi?id=96866

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

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 1179610] Re: poor performance of resize2fs on 12.04

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

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

Title:
  poor performance of resize2fs on 12.04

Status in e2fsprogs package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Precise:
  Won't Fix
Status in e2fsprogs source package in Quantal:
  Fix Released
Status in e2fsprogs package in Debian:
  Fix Released

Bug description:
  I just ran a simple single instance launch, and on raring i saw:
cc_resizefs.py[DEBUG]: Resizing took 0.450 seconds
  on precise:
cc_resizefs.py[DEBUG]: resize took 6.509745121 seconds

  Those are real time reports from /var/log/cloud-init.log for a resize
  up to 10G root from the ~1.4G that the images have built in.

  This is known-fixed in current versions (quantal and later).
  The changes were done to upstream e2fsprogs under debian bug 663237.

  Bug 978012 is a general request for a newer e2fsprogs, and this bug is
  a specific request for the performance improvements.

  Related bugs:
   * bug 978012: Please SRU micro bug fix release of e2fsprogs 1.42.4-3ubuntu1
 (main) from Quantal (main)
   * debian bug 663237: Make resize2fs shrinking use much less CPU

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

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

[Kernel-packages] [Bug 1571761] Re: zfs-import-cache.service slows boot by 60 seconds

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

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

Title:
  zfs-import-cache.service slows boot by 60 seconds

Status in cloud-init package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  In Progress
Status in zfs-linux source package in Xenial:
  New

Bug description:
  Fresh uvt-kvm guest, then
  $ sudo apt-get install zfsutils-linux
  $ sudo reboot

  The reboot will show on console waiting for tasks, then after ~ 60 seconds it 
continues boot.
  Logging in shows:

  $ sudo systemd-analyze critical-chain zfs-mount.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  zfs-mount.service +81ms
  └─zfs-import-cache.service @1min 786ms +272ms
└─systemd-udev-settle.service @494ms +1min 275ms
  └─systemd-udev-trigger.service @415ms +55ms
└─systemd-udevd-control.socket @260ms
  └─-.mount @124ms
└─system.slice @129ms
  └─-.slice @124ms

  Seems possibly related / or some discussion at
  https://github.com/zfsonlinux/zfs/issues/2368

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu8
  ProcVersionSignature: User Name 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Mon Apr 18 16:42:35 2016
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [deleted]

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

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

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

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

apport-collect 1600371

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

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

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

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.

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

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

[Kernel-packages] [Bug 1596643] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 136, failed: 0

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-64.72~14.04.1/ms10-35-mcdivittB0-kernel__3.19.0-64.72~14.04.1__2016-07-08_20-03-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1600371] [NEW] Gnome freezes for some seconds on simultaneous touch and stylus input (palm rejection fails)

Public bug reported:

My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as an
inductive screen for styluses. When I rest my palm on the screen and
then hover my stylus above the screen so that the stylus is recognized
and the mouse pointer follows it, and then move the stylus around Gnome
seems to freeze for some seconds. The duration of the freeze is
proportional to the time the notebook received simultaneous input from
the two methods.

"Freeze" means that the screen is not updated. Keyboard inputs that I
make during the freeze would be executed after the freezing stops.

I do not need to touch the screen with the stylus for the bug to occur.
The bug occurs also when I actually touch the screen with the stylus.

What I expect to happen (and what actually happens in all stylus-
supporting tablets, running with Android or Windows) is that the input
from the touch screen is rejected as long as the stylus is hovering
above the screen.

I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
problem was present in 15.10 as well.

I attach a script as a workaround solution.

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

** Attachment added: "workaround for the bug"
   
https://bugs.launchpad.net/bugs/1600371/+attachment/4697636/+files/palm-rejection.sh

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.

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

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

[Kernel-packages] [Bug 1598394] Re: intel_pstate has too aggressive frequency selection

The bug exists in the upstream kernel 4.7-rc6.


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

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

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

Title:
  intel_pstate has too aggressive frequency selection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was recently upgrading from Ubuntu Gnome 15.10 to 16.04 on my
  ThinkPad. Before the frequency-scaling chose the minimum possible
  frequency when the system was on low load. Now, when I allow the CPU
  to choose anything between the lowest and highest possible frequency,
  it sticks to the highest frequency for 90% of time and only
  occasionally drops to the low frequency.

  I can confirm (htop) that my system load is practically zero. Also the
  CPU Power Manager Applet from Gnome Shell works well, because I can
  force low frequency by reducing the maximum allowed frequency and can
  also switch off Turbo Boost.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.28.30
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timeshifter   1768 F pulseaudio
   /dev/snd/controlC1:  timeshifter   1768 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Jul  2 12:11:42 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (104 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (0 days ago)
  dmi.bios.date: 11/07/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET24WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET24WW(1.11):bd11/07/2014:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1600346] Re: On irq_work_run_list function issue.

2016-07-08 Thread Ubuntu Foundations Team Bug Bot

** Tags added: 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/1600346

Title:
  On irq_work_run_list function issue.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Below is result of perf report:

  irq_work_run_list  /proc/kcore
   
 │  
  ◆
 │  
  ▒
 │  
  ▒
 │Disassembly of section load0: 
  ▒
 │  
  ▒
 │811713a0 : 
  ▒
 │  pushfq  
  ▒
 │  pop%rax 
  ▒
 │  nop 
  ▒
 │  and$0x200,%eax  
  ▒
 │↓ jne69   
  ▒
 │  push   %rbp 
  ▒
 │  mov%rsp,%rbp
  ▒
 │  push   %r14 
  ▒
 │  push   %r13 
  ▒
 │  push   %r12 
  ▒
 │  push   %rbx 
  ▒
 │  mov%rax,%rbx
  ▒
 │  mov(%rdi),%rax  
  ▒
  100,00 │  test   %rax,%rax
  ▒
 │↓ je 60   
  ▒
 │  xchg   %rbx,(%rdi)  
  ▒
 │  test   %rbx,%rbx
  ..

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

To manage notifications

[Kernel-packages] [Bug 1599379] Re: Baytrail-I got black screen with HDMI output

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

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

Title:
  Baytrail-I got black screen with HDMI output

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  This issue happens with 4.0+ kernels. Bisecting shows following commit
  cause the issue:

  commit d2182a660808d9053a605e3ebc8c46a323ec6e5d
  Author: Ville Syrjälä 
  Date: Fri Jan 9 14:21:14 2015 +0200

  drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV

  The issue has been reported to upstream [1] and the fix has been
  merged.

  Although the commit fff7660 fixes the issue, it still misses to probe
  HDMI port in some circumstance, therefore there's another commit
  (already merged):

  commit a5aac5ab876ad95b7f5e8d862afb07248ee9cae2
  Author: Ville Syrjälä 
  CommitDate: Fri Jun 10 10:40:54 2016 +0300

  drm/i915: Check VBT for port presence in addition to the strap on
  VLV/CHV

  [1]: https://bugs.freedesktop.org/show_bug.cgi?id=96288

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

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

[Kernel-packages] [Bug 1597517] Re: linux-headers-3.2.0-105 not in precise-security

2016-07-08 Thread Alex King

This is affecting me as well, on a few servers.

# cat /etc/apt/sources.list
#deb http://aptproxy.sitehost.co.nz/ubuntu precise main multiverse universe
deb http://nz.archive.ubuntu.com/ubuntu precise main multiverse universe 
restricted
deb http://archive.ubuntu.com/ubuntu precise main multiverse universe restricted
deb http://archive.ubuntu.com/ubuntu precise-security main multiverse universe 
restricted

# apt-get upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages have been kept back:
  linux-headers-server linux-image-server linux-server
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

# apt-get install linux-headers-3.2.0-105-generic
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-headers-3.2.0-105-generic : Depends: linux-headers-3.2.0-105 but it is 
not installable
E: Unable to correct problems, you have held broken packages.

# dpkg --get-selections|grep -v install$
#

# apt-get install linux-headers-3.2.0-105
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package linux-headers-3.2.0-105 is not available, but is referred to by another 
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'linux-headers-3.2.0-105' has no installation candidate

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

Title:
  linux-headers-3.2.0-105 not in precise-security

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I noticed that linux-headers-3.2.0-105 is not in precise-security.

  > Package not available
  http://packages.ubuntu.com/precise/devel/linux-headers-3.2.0-105-generic

  Looks like it was published but then removed again:
  https://launchpad.net/ubuntu/precise/amd64/linux-
  headers-3.2.0-105-generic

  Are the headers not always in the security repo if the image is?
  http://packages.ubuntu.com/precise/linux-image-3.2.0-105-generic

  For previous generic kernels like 3.2.0-102 and 3.2.0-104 the headers
  are in precise-security as well instead of only in precise-update.

  See http://packages.ubuntu.com/precise/linux-headers-3.2.0-102-generic
  and http://packages.ubuntu.com/precise/linux-headers-3.2.0-104-generic

  I ran into this trying to install the virtualbox guest additions into
  a precise64 Vagrant with a 3.2.0-105 kernel. The guest plugin tries to
  install the latest headers like 'linux-headers-`uname -r`'

  see https://github.com/dotless-de/vagrant-
  vbguest/blob/d36ba2e4ae00577b4169bf1336a6a3264277c1e7/lib/vagrant-
  vbguest/installers/debian.rb#L31

  this fails because the box I am using has precise-security in the
  sources.list but not precise-update.

  I submitted a question about this and was suggested to create a
  bugreport:
  https://answers.launchpad.net/ubuntu/+source/linux/+question/295780

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

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

[Kernel-packages] [Bug 1599599] Re: System beep broken (again) in Xenial Xerus

I have rebooted several times using Advanced options for Ubuntu and
switching between 4.4.0-21-generic and 4.7.0-040700rc6-generic.

Sometimes the beep actually works for both kernal modules (yes 4.4.0-21
and 4.7) and sometimes it doesn't, but usually it doesn't. In all cases
it is very random and I can't isolate the cause.

I just restarted 3 times without touching anything during the boot
process and letting it go straight to 4.7 generic. The first time the
beep worked, even in Gedit. The 2nd and 3rd times the beep didn't work.

When I start with "upstart" option the beep always works, even with
4.4.0.28-generic as along as I get a command line. Sometimes the command
line doesn't load and the system hangs. (The GUI never loads with
"Upstart" option.)

Now, check out these results for:

$ sudo grep -ri "CONFIG_SND_HDA_INPUT_BEEP_MODE"

config-4.4.0-28-generic:CONFIG_SND_HDA_INPUT_BEEP_MODE=0
config-4.4.0-21-generic:CONFIG_SND_HDA_INPUT_BEEP_MODE=0
config-4.7.0-040700rc6-generic:CONFIG_SND_HDA_INPUT_BEEP_MODE=1

So it seems 4.7 mainline tried to fix this, but the problem must also be
located elsewhere, likely in something getting overridden immediately
after the login password is entered.

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

Title:
System beep broken (again) in Xenial Xerus

Status in linux package in Ubuntu:
Confirmed

Bug description:
This is my first ever bug report, so bear with me if I make mistakes.

System bell (aka PC speaker beep) is not working upon installing
Ubuntu 16.04 Xenial Xerus.

The "beep" command has been installed and works, also "echo foo |
wall" works. But "echo -e '\a'" and "printf '\a'" make no sound, nor
does pressing the rubout or other keys in terminal and Gedit like it
usually does.

lsmod shows pcspkr is loaded

Note
The symptoms are exactly the same as in bug #486154
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/486154

Just for the record, rmmod and reloading the pcspkr module,
unblacklisting it, trying in vain to turn up the volume, and all the
other usual steps are no longer relevant at this point. We are way
beyond that here. Something very, very elusive in this 16.04 distro is
blocking the bell. I suspect something new in 16.04 runs after you
login which nullifies the standard error beep. Pressing down at the
end in Gedit and the terminal also used to make the beep, but
something is telling it not to anymore. The PC speaker works of
course, as the alternative beep command and "echo foo | wall" prove.

Interestingly, Ubuntu can and does produce the system beep in two other
instances:
1) Edit the grub menu at /etc/default /grub and remove the # hash at
GRUB_INIT_TUNE="480 440 1" and you will get a beep when grub loads.
2) Press Backspace without entering your password at login, and you will get
the error beep.

Description: Ubuntu 16.04 LTS
Release: 16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: dv430uuyn 1784 F pulseaudio
/dev/snd/controlC0: dv430uuyn 1784 F pulseaudio
CurrentDesktop: Unity
Date: Wed Jul 6 14:00:50 2016
HibernationDevice: RESUME=UUID=e8206eff-651f-4207-b0a8-9c5a06959711
InstallationDate: Installed on 2016-06-24 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
IwConfig:
enp2s0no wireless extensions.

lono wireless extensions.
MachineType: Dell Inc. Vostro 430
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic
root=UUID=c3a8f971-548b-4666-b865-6bf917bef1c9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-28-generic N/A
linux-backports-modules-4.4.0-28-generic N/A
linux-firmware1.157.2
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/13/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 054KM3
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 430
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1596643] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 20, failed: 12

tests ran:  20, failed: 12;
  
http://kernel.ubuntu.com/testing/3.19.0-64.72~14.04.1/ms10-35-mcdivittB0-kernel__3.19.0-64.72~14.04.1__2016-07-08_19-03-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

This change was made by a bot.

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

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

Title:
  On irq_work_run_list function issue.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Below is result of perf report:

  irq_work_run_list  /proc/kcore
   
 │  
  ◆
 │  
  ▒
 │  
  ▒
 │Disassembly of section load0: 
  ▒
 │  
  ▒
 │811713a0 : 
  ▒
 │  pushfq  
  ▒
 │  pop%rax 
  ▒
 │  nop 
  ▒
 │  and$0x200,%eax  
  ▒
 │↓ jne69   
  ▒
 │  push   %rbp 
  ▒
 │  mov%rsp,%rbp
  ▒
 │  push   %r14 
  ▒
 │  push   %r13 
  ▒
 │  push   %r12 
  ▒
 │  push   %rbx 
  ▒
 │  mov%rax,%rbx
  ▒
 │  mov(%rdi),%rax  
  ▒
  100,00 │  test   %rax,%rax
  ▒
 │↓ je 60   
  ▒
 │  xchg   %rbx,(%rdi)  
  ▒
 │  test   %rbx,%rbx
  ..

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

[Kernel-packages] [Bug 1600346] [NEW] On irq_work_run_list function issue.

2016-07-08 Thread asu

Public bug reported:

Below is result of perf report:

irq_work_run_list  /proc/kcore  
 
   │
◆
   │
▒
   │
▒
   │Disassembly of section load0:   
▒
   │
▒
   │811713a0 :   
▒
   │  pushfq
▒
   │  pop%rax   
▒
   │  nop   
▒
   │  and$0x200,%eax
▒
   │↓ jne69 
▒
   │  push   %rbp   
▒
   │  mov%rsp,%rbp  
▒
   │  push   %r14   
▒
   │  push   %r13   
▒
   │  push   %r12   
▒
   │  push   %rbx   
▒
   │  mov%rax,%rbx  
▒
   │  mov(%rdi),%rax
▒
100,00 │  test   %rax,%rax  
▒
   │↓ je 60 
▒
   │  xchg   %rbx,(%rdi)
▒
   │  test   %rbx,%rbx
..

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

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


** Tags: amd64 apport-bug xenial

** Patch added: "Tested on linux-4.6.2"
   
https://bugs.launchpad.net/bugs/1600346/+attachment/4697563/+files/check_NULL_irq_work_run_list.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/1600346

Title:
  On

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

2016-07-08 Thread Tim Passingham

Sorry, I forgot that.

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

Title:
  Key 5 automatically pressed on some Logitech wireless keyboards

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1597971] Re: kernel: signal return with invalid floating-point control

2016-07-08 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  kernel: signal return with invalid floating-point control

Status in Linux:
  New
Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Please backport:
  commit bcf4dd5f9ee096bd1510f838dd4750c35df4e38b
  Author: Martin Schwidefsky 
  Date:   Mon Jun 27 17:06:45 2016 +0200

  s390: fix test_fp_ctl inline assembly contraints
  
  The test_fp_ctl function is used to test if a given value is a valid
  floating-point control. The inline assembly in test_fp_ctl uses an
  incorrect constraint for the 'orig_fpc' variable. If the compiler
  chooses the same register for 'fpc' and 'orig_fpc' the test_fp_ctl()
  function always returns true. This allows user space to trigger
  kernel oopses with invalid floating-point control values on the
  signal stack.
  
  This problem has been introduced with git commit 4725c86055f5bbdcdf
  "s390: fix save and restore of the floating-point-control register"
  
  Cc: sta...@vger.kernel.org # v3.13+
  Reviewed-by: Heiko Carstens 
  Signed-off-by: Martin Schwidefsky 

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

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

[Kernel-packages] [Bug 1596643] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 4, failed: 1

tests ran:   4, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-64.72~14.04.1/ms10-35-mcdivittB0-kernel__3.19.0-64.72~14.04.1__2016-07-08_18-48-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1596643] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 3, failed: 1

tests ran:   3, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-64.72~14.04.1/ms10-35-mcdivittB0-kernel__3.19.0-64.72~14.04.1__2016-07-08_17-33-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1291341] Re: tahr /var/log/syslog missing

2016-07-08 Thread James Qiang

I just installed a fresh 14.04 and had the same problem. After comparing
it with another working host, I found the difference in the /var/log
directory ownership and permission

on working host:

% ls -ld /var/log/
drwxrwxr-x 14 root syslog 4096 Jul  8 06:25 /var/log/

on the problem host:

% ls -ld /var/log/
drwxr-xr-x 7 root root 4096 Jul  9 01:40 /var/log/

/etc/rsyslog.conf writes file with syslog user and adm group but the
/var/log dir is not writable.

It's working ok after I have fix the ownership/permission problem.

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

Title:
  tahr /var/log/syslog missing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  jerry@Aspire1:~$ ubuntu-bug linux
  tail: cannot open ‘/var/log/syslog’ for reading: No such file or directory

  Took a look, there is no syslog.  In spite of all this on the screen
  ubuntu-bug does work:

  jerry@Aspire1:~$ jerry@Aspire1:~$ ubuntu-bug linux
  jerry@Aspire1:~$: command not found
  jerry@Aspire1:~$ tail: cannot open ‘/var/log/syslog’ for reading: No such 
file or directory
  No command 'tail:' found, did you mean:
   Command 'tailf' from package 'util-linux' (main)
   Command 'tail' from package 'coreutils' (main)
  tail:: command not found
  jerry@Aspire1:~$ jerry@Aspire1:~$ 
  jerry@Aspire1:~$: command not found
  jerry@Aspire1:~$ (process:3240): GLib-CRITICAL **: g_slice_set_config: 
assertion 'sys_page_size == 0' failed
  bash: syntax error near unexpected token `:'
  jerry@Aspire1:~$ NOTE: child process received `Goodbye', closing down

  Not much in /var/log:

  jerry@Aspire1:~$ ls /var/log
  boot.log  dmesggpu-manager.log  pm-powersave.log  udev
  cups  dmesg.0  lightdm  samba Xorg.0.log

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-17-generic 3.13.0-17.37
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jerry  1592 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar 12 08:22:29 2014
  HibernationDevice: RESUME=UUID=fb4f0b36-eec7-43a5-9265-4ecd90a404b5
  MachineType: Acer AOD255E
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic 
root=UUID=8e7eecfe-38ae-4bab-bd87-4bfe44a51904 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 12/16/2010
  dmi.bios.vendor: Acer
  dmi.bios.version: V3.12(DDR3)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE02_PT
  dmi.board.vendor: Acer
  dmi.board.version: V3.12(DDR3)
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V3.12(DDR3)
  dmi.modalias: 
dmi:bvnAcer:bvrV3.12(DDR3):bd12/16/2010:svnAcer:pnAOD255E:pvrV3.12(DDR3):rvnAcer:rnJE02_PT:rvrV3.12(DDR3):cvnAcer:ct10:cvrV3.12(DDR3):
  dmi.product.name: AOD255E
  dmi.product.version: V3.12(DDR3)
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

2016-07-08 Thread Mathieu Trudel-Lapierre

Verification done for XENIAL: grub2-signed, dkms, shim-signed all found
to be working as expected. Test cases pass. As previously discussed, the
grub2-signed update is not especially useful in itself and does need to
drop the calls to mokutil, but will need a further SRU to remove calling
update-secureboot-policy later.

** Tags added: verification-done-wily

** Tags added: verification-done-xenial

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

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  Invalid
Status in efivar source package in Precise:
  Fix Released
Status in grub2 source package in Precise:
  Invalid
Status in grub2-signed source package in Precise:
  Invalid
Status in mokutil source package in Precise:
  Fix Released
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  Fix Committed
Status in dkms source package in Trusty:
  Fix Committed
Status in efibootmgr source package in Trusty:
  Invalid
Status in efivar source package in Trusty:
  Fix Committed
Status in grub2 source package in Trusty:
  Invalid
Status in grub2-signed source package in Trusty:
  Invalid
Status in mokutil source package in Trusty:
  Fix Committed
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  Fix Committed
Status in dkms source package in Wily:
  Fix Committed
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  Invalid
Status in grub2-signed source package in Wily:
  Invalid
Status in mokutil source package in Wily:
  Fix Committed
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in grub2-signed source package in Xenial:
  In Progress
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  
https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0

  Test cases here are separated by the components that need to be
  changed:

  = mokutil =

  Adding a MOK key:
  1) Install system
  2) Run 'mokutil --import ' to import a signing certificate.
  3) On reboot; validate MOK prompts for new MOK key to add.

  Toggling Secure Boot state:
  1) Install system
  2) mokutil --enable-validationormokutil --disable-validation
  3) Validate that on reboot MOK prompts to change Secure Boot state.

  Listing keys:
  1) mokutil --list-enrolled
  -- should list keys previously enrolled, and Microsoft keys on systems that 
are configured with them for factory Secure Boot.

  
  = efivar =

  libefivar0 gets tested via the use of mokutil. Since it is a library
  with no directly usable binaries; we rely on mokutil / sbsigntool /
  efibootmgr to do testing.

  1) Run efibootmgr -v ; verify it lists BootEntries.
  2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that 
on reboot; you can get into a boot menu that will list 'ubuntu2', and that 
picking that boot entry boots into Ubuntu.

  
  = shim-signed =

  1) Install system; upgrade to new packages
  1b) Verify /proc/sys/kernel/secure_boot shows 1.
  1c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.
  2) Run 'sudo update-secureboot-policy'; validate that it prompts to disable 
Secure Boot if it's not already disabled.
  3) Run 'sudo update-secureboot-policy'; validate you are not prompted again 
to disable Secure Boot.
  4) Reboot; follow MOK steps to disable Secure Boot.
  4b) Verify /proc/sys/kernel/secure_boot shows 1.
  4c) Verify /proc/sys/kernel/moksbstate_disabled shows 1.
  5) Run 'sudo update-secureboot-policy --enable'; validate

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

2016-07-08 Thread Mathieu Trudel-Lapierre

Verification-done for TRUSTY: efivar, mokutil, dkms, shim-signed all
found to be working at expected. Test cases pass.

** Tags added: verification-done-trusty

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

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  Invalid
Status in efivar source package in Precise:
  Fix Released
Status in grub2 source package in Precise:
  Invalid
Status in grub2-signed source package in Precise:
  Invalid
Status in mokutil source package in Precise:
  Fix Released
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  Fix Committed
Status in dkms source package in Trusty:
  Fix Committed
Status in efibootmgr source package in Trusty:
  Invalid
Status in efivar source package in Trusty:
  Fix Committed
Status in grub2 source package in Trusty:
  Invalid
Status in grub2-signed source package in Trusty:
  Invalid
Status in mokutil source package in Trusty:
  Fix Committed
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  Fix Committed
Status in dkms source package in Wily:
  Fix Committed
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  Invalid
Status in grub2-signed source package in Wily:
  Invalid
Status in mokutil source package in Wily:
  Fix Committed
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in grub2-signed source package in Xenial:
  In Progress
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  
https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0

  Test cases here are separated by the components that need to be
  changed:

  = mokutil =

  Adding a MOK key:
  1) Install system
  2) Run 'mokutil --import ' to import a signing certificate.
  3) On reboot; validate MOK prompts for new MOK key to add.

  Toggling Secure Boot state:
  1) Install system
  2) mokutil --enable-validationormokutil --disable-validation
  3) Validate that on reboot MOK prompts to change Secure Boot state.

  Listing keys:
  1) mokutil --list-enrolled
  -- should list keys previously enrolled, and Microsoft keys on systems that 
are configured with them for factory Secure Boot.

  
  = efivar =

  libefivar0 gets tested via the use of mokutil. Since it is a library
  with no directly usable binaries; we rely on mokutil / sbsigntool /
  efibootmgr to do testing.

  1) Run efibootmgr -v ; verify it lists BootEntries.
  2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that 
on reboot; you can get into a boot menu that will list 'ubuntu2', and that 
picking that boot entry boots into Ubuntu.

  
  = shim-signed =

  1) Install system; upgrade to new packages
  1b) Verify /proc/sys/kernel/secure_boot shows 1.
  1c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.
  2) Run 'sudo update-secureboot-policy'; validate that it prompts to disable 
Secure Boot if it's not already disabled.
  3) Run 'sudo update-secureboot-policy'; validate you are not prompted again 
to disable Secure Boot.
  4) Reboot; follow MOK steps to disable Secure Boot.
  4b) Verify /proc/sys/kernel/secure_boot shows 1.
  4c) Verify /proc/sys/kernel/moksbstate_disabled shows 1.
  5) Run 'sudo update-secureboot-policy --enable'; validate you are prompted to 
enable Secure Boot.
  6) Reboot; follow MOK steps to re-enable Secure Boot.
  6b) Verify /proc/sys/kernel/secure_boot shows 1.
  6c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.

  
  = grub2 =

  Booting signed

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

2016-07-08 Thread Mathieu Trudel-Lapierre

Verification-done for WILY: mokutil, dkms, shim-signed all found to be
working as expected. Test cases pass.

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

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  Invalid
Status in efivar source package in Precise:
  Fix Released
Status in grub2 source package in Precise:
  Invalid
Status in grub2-signed source package in Precise:
  Invalid
Status in mokutil source package in Precise:
  Fix Released
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  Fix Committed
Status in dkms source package in Trusty:
  Fix Committed
Status in efibootmgr source package in Trusty:
  Invalid
Status in efivar source package in Trusty:
  Fix Committed
Status in grub2 source package in Trusty:
  Invalid
Status in grub2-signed source package in Trusty:
  Invalid
Status in mokutil source package in Trusty:
  Fix Committed
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  Fix Committed
Status in dkms source package in Wily:
  Fix Committed
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  Invalid
Status in grub2-signed source package in Wily:
  Invalid
Status in mokutil source package in Wily:
  Fix Committed
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in grub2-signed source package in Xenial:
  In Progress
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  
https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0

  Test cases here are separated by the components that need to be
  changed:

  = mokutil =

  Adding a MOK key:
  1) Install system
  2) Run 'mokutil --import ' to import a signing certificate.
  3) On reboot; validate MOK prompts for new MOK key to add.

  Toggling Secure Boot state:
  1) Install system
  2) mokutil --enable-validationormokutil --disable-validation
  3) Validate that on reboot MOK prompts to change Secure Boot state.

  Listing keys:
  1) mokutil --list-enrolled
  -- should list keys previously enrolled, and Microsoft keys on systems that 
are configured with them for factory Secure Boot.

  
  = efivar =

  libefivar0 gets tested via the use of mokutil. Since it is a library
  with no directly usable binaries; we rely on mokutil / sbsigntool /
  efibootmgr to do testing.

  1) Run efibootmgr -v ; verify it lists BootEntries.
  2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that 
on reboot; you can get into a boot menu that will list 'ubuntu2', and that 
picking that boot entry boots into Ubuntu.

  
  = shim-signed =

  1) Install system; upgrade to new packages
  1b) Verify /proc/sys/kernel/secure_boot shows 1.
  1c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.
  2) Run 'sudo update-secureboot-policy'; validate that it prompts to disable 
Secure Boot if it's not already disabled.
  3) Run 'sudo update-secureboot-policy'; validate you are not prompted again 
to disable Secure Boot.
  4) Reboot; follow MOK steps to disable Secure Boot.
  4b) Verify /proc/sys/kernel/secure_boot shows 1.
  4c) Verify /proc/sys/kernel/moksbstate_disabled shows 1.
  5) Run 'sudo update-secureboot-policy --enable'; validate you are prompted to 
enable Secure Boot.
  6) Reboot; follow MOK steps to re-enable Secure Boot.
  6b) Verify /proc/sys/kernel/secure_boot shows 1.
  6c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.

  
  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom kernel
  2)

[Kernel-packages] [Bug 1596643] modoc (ppc64el) - tests ran: 1, failed: 1

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/modoc__3.19.0-65.73~14.04.1__2016-07-08_17-19-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1596643] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 10, failed: 2

tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/ms10-35-mcdivittB0-kernel__3.19.0-65.73~14.04.1__2016-07-08_16-25-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1597053] Re: linux: 4.2.0-42.49 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-updates
   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/1597053

Title:
  linux: 4.2.0-42.49 -proposed tracker

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

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1596643] modoc (ppc64el) - tests ran: 20, failed: 18

tests ran:  20, failed: 18;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/modoc__3.19.0-65.73~14.04.1__2016-07-08_16-49-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1596631] Re: linux: 3.19.0-65.73 -proposed tracker

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-updates
   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/1596631

Title:
  linux: 3.19.0-65.73 -proposed tracker

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

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1590655] Re: [Hyper-V] storvsc messages for CD-ROM medium not present tray closed

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

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

Title:
  [Hyper-V] storvsc messages for CD-ROM medium not present tray closed

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

Bug description:
  The below can be seen with any distribution running on a Generation 2
  VM.

  There is a verified patch for this, however it has been scheduled only for 
the 4.8 scsi-queue.
  As it a small patch which has been verified by KY and also accepted in the 
patch queue, will you be able to include this as part of the 16.04 rebase to 
4.6, and as well for 14.04 and 15.10?

  Patch can be found at https://patchwork.kernel.org/patch/9131929/

  Description of problem:
  When starting and shutting down a Gen2 VM, at least 20-30 messages are 
recorded for storvsc with the below sample:
  [storvsc] Sense Key : Not Ready [current]
  [storvsc] Add. Sense: Medium not present - tray closed

  Steps to Reproduce:
  1. create a Generation2 VM
  2. start VM and observe the system logs
  3. multiple messages for the cd-rom are recorded from storvsc

  Actual results:
  even without a CD-ROM unit attached, the messages would appear.
  Having an ISO attached or not would still produce the same messages.

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

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

[Kernel-packages] [Bug 1596643] modoc (ppc64el) - tests ran: 2, failed: 2

tests ran:   2, failed: 2;
  
http://kernel.ubuntu.com/testing/3.19.0-65.73~14.04.1/modoc__3.19.0-65.73~14.04.1__2016-07-08_16-29-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

2016-07-08 Thread Pekka Hämäläinen

This bug affects also me. I just upgraded from 14.04 and 16.04
(4.4.0-28-generic #47-Ubuntu SMP kernel) radeon driver offers only 1024
x 768 resolution. Hw is adm redwood xt (hd 5670) which can do 1920 x
1080 at least.

I can run series of tests for you if needed.

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

Title:
  Radeon driver only provides 1024x768 resolution

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

[Kernel-packages] [Bug 1596631] Re: linux: 3.19.0-65.73 -proposed tracker

** Tags added: regression-testing-passed

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

Title:
  linux: 3.19.0-65.73 -proposed tracker

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

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1597047] Re: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker

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

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1597053] Re: linux: 4.2.0-42.49 -proposed tracker

** Tags added: regression-testing-passed

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

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

Title:
  linux: 4.2.0-42.49 -proposed tracker

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

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1597971] Re: kernel: signal return with invalid floating-point control

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

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

Title:
  kernel: signal return with invalid floating-point control

Status in Linux:
  New
Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Please backport:
  commit bcf4dd5f9ee096bd1510f838dd4750c35df4e38b
  Author: Martin Schwidefsky 
  Date:   Mon Jun 27 17:06:45 2016 +0200

  s390: fix test_fp_ctl inline assembly contraints
  
  The test_fp_ctl function is used to test if a given value is a valid
  floating-point control. The inline assembly in test_fp_ctl uses an
  incorrect constraint for the 'orig_fpc' variable. If the compiler
  chooses the same register for 'fpc' and 'orig_fpc' the test_fp_ctl()
  function always returns true. This allows user space to trigger
  kernel oopses with invalid floating-point control values on the
  signal stack.
  
  This problem has been introduced with git commit 4725c86055f5bbdcdf
  "s390: fix save and restore of the floating-point-control register"
  
  Cc: sta...@vger.kernel.org # v3.13+
  Reviewed-by: Heiko Carstens 
  Signed-off-by: Martin Schwidefsky 

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

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

[Kernel-packages] [Bug 1596643] Re: linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-lts-vivid: 3.19.0-65.73~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1596631
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1597060] Re: linux: 3.13.0-92.139 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-updates
   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/1597060

Title:
  linux: 3.13.0-92.139 -proposed tracker

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

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1599250] Re: Hotplug device addition issue - missing patches on Xenial kernel

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

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

Title:
  Hotplug device addition issue - missing patches on Xenial kernel

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

Bug description:
  == Comment: #0 - Guilherme Guaglianoni Piccoli - 2016-06-29 18:09:04 ==
  When performing hotplug device addition to LPAR/guest with Ubuntu 16.04 
(kernel 4.4.0-28) we can observe a kernel oops if device makes use of 64-bit 
DDW DMA. The following stack trace was observed with QLogic NIC (bnx2x driver):

  
  [  131.52] --- interrupt: 300 at enable_ddw+0x254/0x7c0
 LR = enable_ddw+0x238/0x7c0
  [  131.52] [c001fbc67480] [c0089b88] 
dma_set_mask_pSeriesLP+0x208/0x290
  [  131.52] [c001fbc67510] [c00246b8] dma_set_mask+0x58/0xf0
  [  131.52] [c001fbc67540] [d387a654] bnx2x_init_one+0x504/0x10f0 
[bnx2x]
  [  131.52] [c001fbc67620] [c05e4eac] local_pci_probe+0x6c/0x140
  [  131.52] [c001fbc676b0] [c05e5d58] pci_device_probe+0x168/0x200
  [  131.52] [c001fbc67710] [c06d2530] 
driver_probe_device+0x1f0/0x610
  [  131.52] [c001fbc677a0] [c06d2a6c] __driver_attach+0x11c/0x120
  [  131.52] [c001fbc677e0] [c06ceeac] bus_for_each_dev+0x9c/0x110
  [  131.52] [c001fbc67830] [c06d198c] driver_attach+0x3c/0x60
  [  131.52] [c001fbc67860] [c06d1278] bus_add_driver+0x2d8/0x390
  [  131.52] [c001fbc678f0] [c06d39dc] driver_register+0x9c/0x180
  [  131.52] [c001fbc67960] [c05e401c] 
__pci_register_driver+0x6c/0x90

  
  This issue is solved upstream, by the following 3 patches (SHA-1 from Linus 
tree):

  c2078d9ef60 ("Revert \"powerpc/eeh: Fix crash in eeh_add_device_early() on 
Cell\"")
  8445a87f709 ("powerpc/iommu: Remove the dependency on EEH struct in DDW 
mechanism")
  8a934efe943 ("powerpc/pseries: Fix PCI config address for DDW")

  
  So, we want to request the addition of these fixes in Ubuntu Xenial kernel.
  Besides, an old and obsolete non-upstream patch related to this issue can be 
removed (SHA-1 from Ubuntu xenial tree):

  623aabd5d68 ("UBUNTU: SAUCE: powerpc/eeh: Validate arch in
  eeh_add_device_early()")

  
  Thanks,

  Guilherme

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

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

[Kernel-packages] [Bug 1597047] Re: linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker

** Tags added: regression-testing-passed

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-lts-utopic: 3.16.0-77.99~14.04.1 -proposed tracker

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

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1597060] Re: linux: 3.13.0-92.139 -proposed tracker

** Tags added: regression-testing-passed

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

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

Title:
  linux: 3.13.0-92.139 -proposed tracker

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

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

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

2016-07-08 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1596281

** Tags added: iso-testing

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1600265] [NEW] package linux-image-extra-3.19.0-64-generic 3.19.0-64.72~14.04.1 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1

2016-07-08 Thread Rabbit the Black

Public bug reported:

don't know

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.19.0-64-generic 3.19.0-64.72~14.04.1
Uname: Linux 4.5.0-040500-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Jul  8 17:56:09 2016
ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код ошибки 1
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: linux-lts-vivid
Title: package linux-image-extra-3.19.0-64-generic 3.19.0-64.72~14.04.1 failed 
to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код 
ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package linux-image-extra-3.19.0-64-generic 3.19.0-64.72~14.04.1
  failed to install/upgrade: подпроцесс установлен сценарий post-removal
  возвратил код ошибки 1

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

Bug description:
  don't know

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.19.0-64-generic 3.19.0-64.72~14.04.1
  Uname: Linux 4.5.0-040500-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Jul  8 17:56:09 2016
  ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код 
ошибки 1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: linux-lts-vivid
  Title: package linux-image-extra-3.19.0-64-generic 3.19.0-64.72~14.04.1 
failed to install/upgrade: подпроцесс установлен сценарий post-removal 
возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1589889] Re: Bluetooth search gets nothing on Dell XPS 15 9550

2016-07-08 Thread Cruz Fernandez

Updated firmware with latest one (version 481).

Same as last one, decompress it, and ensure the permissions are correct
on:

-rw-r--r-- 1 root root 54734 may 19 21:22 /lib/firmware/brcm/BCM-
0a5c-6410.hcd

When loaded you should see something this on 'dmesg' like:

[ 6828.577574] Bluetooth: hci0: BCM (001.001.005) build 0481

After more digging on how this works, looks like several broadcom chips
have similar problems to load this type of files (bug #1129865, bug
#1065400). According to a question in askubuntu (also best place of how
the procedure to produce this .hcd files)
http://askubuntu.com/questions/632336/bluetooth-broadcom-43142-isnt-
working-on-ubuntu , there are some legal problems that don't allow this
firmware files to be added to the Ubuntu installation

Thanks a lot to @bertusrex on
http://ubuntuforums.org/showthread.php?t=2317843=13514092#post13514092
for getting into windows and getting us the firmware file.

** Attachment added: "version 481 of firmware bluetooth"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1589889/+attachment/4697483/+files/BCM-0a5c-6410_481.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/1589889

Title:
  Bluetooth search gets nothing on Dell XPS 15 9550

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Title: Bluetooth search gets nothing on Dell XPS 15 9550

  Summary:
  Bluetooth search gets nothing on Dell XPS 15 9550

  Steps:
  1. Open Bluetooth Setting
  2. Click "+" to search nearby bluetooth devices

  Expected results: BT search could get nearby BT devices

  Actual results: Nothing shows from BT search

  Additional information:
  BT device:
  Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
  Couldn't open device, some information will be missing
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.00
    bDeviceClass  255 Vendor Specific Class
    bDeviceSubClass 1
    bDeviceProtocol 1
    bMaxPacketSize064
    idVendor   0x0a5c Broadcom Corp.
    idProduct  0x6410

  CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8x)

  GPU: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics
  530 (rev 06)

  Manufacturer: Dell

  ProductName: XPS 15 9550

  BiosVersion: 01.02.00

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

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

[Kernel-packages] [Bug 1531768] Re: [arm64] lockups some time after booting

2016-07-08 Thread Martin Pitt

Thanks Colin, great work! I'll deploy this ASAP.

FYI, at least some of the VM hosts in scalingstack got updated to a 4.4
kernel. Not sure how much that changes your investigations.

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

Title:
  [arm64] lockups some time after booting

Status in Auto Package Testing:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
  want to use for armhf autopkgtesting in LXD). I started with wily as
  that has lxd available (it's not yet available in trusty nor the PPA
  for arm64).

  However, pretty much any LXD task that I do (I haven't tried much
  else) on this machine takes unbearably long. A simple "lxc profile set
  default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes.

  I see tons of

  [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0
  [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds.

  in dmesg (the attached apport info has the complete dmesg).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 09:18 seq
   crw-rw 1 root audio 116, 33 Jan  7 09:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Thu Jan  7 09:24:01 2016
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.

   lxcbr0no wireless extensions.
  Lspci:
   00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008]
    Subsystem: Red Hat, Inc Device [1af4:1100]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=LABEL=cloudimg-rootfs earlyprintk
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+subscriptions

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

[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)

2016-07-08 Thread Colan Schwartz

In my case there are no drives involved, just a hub with a camera.

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

Title:
  USB stops working after a while (xhci_hcd :00:14.0: Timeout while
  waiting for setup device command)

Status in System76:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On my laptop the kernel will sometimes drop the USB hub. After this,
  the laptop doesn't recognise any device plugged in to the USB ports -
  plugging and unplugging any device I've tried into any of the USB
  ports produces no response, not even dmesg entries.

  Strangely this also applies to bluetooth - it no longer works once USB
  has dropped (possibly the module is hung of the bus internally).

  Once this has happened only a reboot fixes it; I've not managed to
  find any combination of module unload/reload or suspend cycles to
  reinitialise things correctly.

  Relevant snippet of dmesg:
  [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe 
the host is dead
  [48838.079742] xhci_hcd :00:14.0: Abort command ring failed
  [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up
  [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079806] sched: RT throttling activated
  [48838.079981] usb 1-1: USB disconnect, device number 16
  [48838.079985] usb 1-1.2: USB disconnect, device number 18
  [48838.079987] usb 1-1.2.3: USB disconnect, device number 19
  [48838.080285] usb 1-1.2.4: USB disconnect, device number 20
  [48838.111892] usb 1-1.4: USB disconnect, device number 17
  [48838.191292] usb 1-4: USB disconnect, device number 6
  [48838.267550] usb 1-10: USB disconnect, device number 8
  [48838.282968] usb 2-1: device not accepting address 8, error -62
  [48838.282983] usb 2-1: USB disconnect, device number 8
  [48838.282986] usb 2-1.2: USB disconnect, device number 9

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  4255 F pulseaudio
   /dev/snd/controlC0:  chris  4255 F pulseaudio
  CRDA:
   country AU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (3, 23), (N/A)
(5250 - 5330 @ 40), (3, 23), (0 ms), DFS
(5735 - 5835 @ 40), (3, 30), (N/A)
  CurrentDesktop: Unity
  Date: Thu Jan 22 12:59:27 2015
  InstallationDate: Installed on 2013-08-06 (533 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Galago UltraPro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed 
root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd break=mount
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1531768] Re: [arm64] lockups some time after booting

2016-07-08 Thread Colin Ian King

Also, can we clarify something. Do the ARM hosts provide kvm? If not,
one should really run the VMs with just one CPU.

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

Title:
  [arm64] lockups some time after booting

Status in Auto Package Testing:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
  want to use for armhf autopkgtesting in LXD). I started with wily as
  that has lxd available (it's not yet available in trusty nor the PPA
  for arm64).

  However, pretty much any LXD task that I do (I haven't tried much
  else) on this machine takes unbearably long. A simple "lxc profile set
  default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes.

  I see tons of

  [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0
  [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds.

  in dmesg (the attached apport info has the complete dmesg).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 09:18 seq
   crw-rw 1 root audio 116, 33 Jan  7 09:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Thu Jan  7 09:24:01 2016
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.

   lxcbr0no wireless extensions.
  Lspci:
   00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008]
    Subsystem: Red Hat, Inc Device [1af4:1100]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=LABEL=cloudimg-rootfs earlyprintk
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+subscriptions

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

[Kernel-packages] [Bug 1531768] Re: [arm64] lockups some time after booting

2016-07-08 Thread Colin Ian King

This article throws some light onto things:

https://lwn.net/Articles/518953/

"Second, the greater the number of idle CPUs, the more work RCU must do
when forcing quiescent states. Yes, the busier the system, the less work
RCU needs to do! The reason for the extra work is that RCU is not
permitted to disturb idle CPUs for energy-efficiency reasons. RCU must
therefore probe a per-CPU data structure to read out idleness state
during each grace period, likely incurring a cache miss on each such
probe."

Just to add, I running the VM with say 4 CPUs, all are which are idle.

In my experiments on 3.19 and 4.2, kernels, kvm is not being used on the
host, so we have QEMU emulating N CPUs with just 1 host CPU.  Plus a
loaded host means that this single CPU is busy and we have potentially
large latencies serving the N virtual CPUs in the VM. I think that's
part of the issue; large latencies from the host with a N-to-1 virt to
host mapping meaning that we are tripping the RCU grace periods.

To try and help RCU kthreads from suffering from delays, I added the
following kernel parameters to the VM:

rcu_nocb_poll rcutree.kthread_prio=90 rcuperf.verbose=1

I was able to run an 8 CPU VM without any RCU issues with the host CPU
being hammered to death with stress-ng.  I also then cranked down the
RCU stall grace period to just 5 seconds to see how easy I can trip the
issue with this more extreme setting using:

echo 5 > /sys/module/rcupdate/parameters/rcu_cpu_stall_timeout

and again, no RCU issues.

@Martin,

can you try using the following kernel parameters on the VM and see if
this helps:

rcu_nocb_poll rcutree.kthread_prio=90 rcuperf.verbose=1

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

Title:
  [arm64] lockups some time after booting

Status in Auto Package Testing:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
  want to use for armhf autopkgtesting in LXD). I started with wily as
  that has lxd available (it's not yet available in trusty nor the PPA
  for arm64).

  However, pretty much any LXD task that I do (I haven't tried much
  else) on this machine takes unbearably long. A simple "lxc profile set
  default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes.

  I see tons of

  [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0
  [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds.

  in dmesg (the attached apport info has the complete dmesg).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 09:18 seq
   crw-rw 1 root audio 116, 33 Jan  7 09:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Thu Jan  7 09:24:01 2016
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.

   lxcbr0no wireless extensions.
  Lspci:
   00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008]
    Subsystem: Red Hat, Inc Device [1af4:1100]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=LABEL=cloudimg-rootfs earlyprintk
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+subscriptions

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

[Kernel-packages] [Bug 1490347] Re: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes

2016-07-08 Thread Konrad Zapałowicz

Hey, could you retest with silo 68 installed?

Thanks

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

Title:
  [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy
  LMP Link Management Protocol) PIN codes

Status in Bluez Utilities:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

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

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

[Kernel-packages] [Bug 1557298] Re: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly

2016-07-08 Thread Konrad Zapałowicz

Just have tested with silo 68 installed and I'm able to pair and connect
& use the MS Designer Keyboard quite smoothly. Could you retest with
silo 68 installed and let me know how it is on your end, thanks.

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

Title:
  [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly

Status in Unity Control Center:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  Failed to pair low energy(bluetooth smart, 4.0) keyboard correctly.

  Bluetooth smart keyboard is unable to use after bluetooth-wizard says
  "OK". Also the passcode input is also not acting interactively like
  when pairing with bluetooth 3.0(LegacyPairing) keyboard.

  Above scenario also being verified with bluetoothctl and blueman.

  Step to reproduce:

  1. open Bluetooth Settings
  2. click on Add New Device button
  3. select the bluetooth le keyboard
  4. input the passcode display on GUI

  Expected result:

  After bluetooth-wizard telling user is okay the keyboard should work

  
  Actual result:

  Pairing mode stop on keyboard, but still not work.

  
  -
  More details about versions:

  Environment:
  xenial daily (20160307)
  bluez 5.37-0ubuntu5
  gnome-bluetooth 3.18.2-1ubuntu2
  blueman  2.0.3-1ubuntu1
  bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1)

  Tested devices:
  Designer Mouse, bluetooth smart (pairable, work, re-pair work)
  Designer Keyboard, bluetooth smart (paired, not working)
  BT3.0 keyboard, bluetooth classic (pair and work)
  BT3.0 mouse, bluetooth classic (pair and work)

  -
  In control environment with the same hardware system and devices:
  trusty 14.04.1 + dist-upgrade (stay with 3.13 kernel)
  bluez5 5.35 (ppa: https://launchpad.net/~vidplace7/+archive/ubuntu/bluez5)

  It works with all above devices but can only be pairing through
  bluetoothctl manually, since the older bluetooth-wizard does not
  understand bluez 5.x.

  Everything seems works fine, although there are a lot more error
  messages, but since this bug is more about xenial, please let me know
  if we need more information about this, I'm able to reproduce this
  trusty scenario in anytime.

  -
  Additional note:
  A little clarification, since I'm not sure how far the Bluetooth SIG is going 
to use Bluetooth Smart(Low Energy, or even Smart-Ready) to cover the 
versioning, I decided to just use what ever I saw on the product box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 15 11:40:12 2016
  InstallationDate: Installed on 2016-03-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E5550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed 
root=UUID=1079eca4-4293-4e51-ba0e-84f7d681cb2c ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0141B2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5550
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 00:71:CC:39:BD:22  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:862538 acl:39687 sco:0 events:2668 errors:0
    TX bytes:26235 acl:904 sco:0 commands:1021 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-control-center/+bug/1557298/+subscriptions

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

[Kernel-packages] [Bug 1599561] Re: Ubuntu 16.04.01 kdump: IP prefix is missing in the directory name after first dump during kdump over ssh.

2016-07-08 Thread Louis Bouchard

Hello,

While I'm not able to reproduce the behavior I do think that the bug is
valid. It also bring up another issue with how the IP address is
collected. On system with multiple IP address in IPv4 & IPv6, hostname
-I would return :

192.168.88.240 10.0.4.1 192.168.30.1 192.168.10.1 192.168.122.1
192.168.11.1 10.0.3.1 10.172.64.118 fd39:6c94:2e21:a491::1
2001:67c:1562:8007::aac:4076

So while the race condition needs to be adressed, the definition method
also needs to be improved.

I'll do my best to look at it in a timely manner.

Kind regards,

...Louis

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

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

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

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** No longer affects: makedumpfile (Ubuntu Yakkety)

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

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

Title:
  Ubuntu 16.04.01 kdump: IP prefix is missing in the directory name
  after first dump during kdump over ssh.

Status in makedumpfile package in Ubuntu:
  Triaged
Status in makedumpfile source package in Xenial:
  Confirmed

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-06-30 07:12:40 ==
  ---Problem Description---

  During kdump over ssh IP prefix will be present only in first dump,
  subsequent dumps will not have IP in directory name.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show # should show "ready to dump"
  6) ssh-keygen -t rsa
  7) Edit below parameters in /etc/default/kdump-tools
  SSH="root@"
  SSH_KEY=/root/.ssh/id_rsa
  8)  kdump-config propagate
  9)  kdump-config show
  10) reboot
  11) echo "c" > /proc/sysrq-trigger
  12) verify dump is created in ssh server.
  13) trigger the crash again.

  Logs
  =
  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.4.0-26-generic #45-Ubuntu SMP Mon Jun 20 17:27:01 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  dumps on ssh server when 3 crashes are triggered
  
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523  -201606300524
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523  -201606300524  -201606300525
  [root@ltc-fire5 crash]# cd -201606300524
  -bash: cd: -2: invalid option
  cd: usage: cd [-L|[-P [-e]]] [dir]
  [root@ltc-fire5 crash]# cd -- -201606300524
  [root@ltc-fire5 -201606300524]# ls
  dmesg.201606300524  dump.201606300524

  
  == Comment: #8 - Kevin W. Rudd - 2016-07-05 18:23:01 ==

  Canonical,

  The behavior appears to be somewhat intermittent, and it looks as if
  define_stampdir() might be getting called before the network init has
  completed.  If delaying this function is not practical, it might be
  helpful to have define_stampdir() fall back to using just "hostname"
  if "hostname -I" doesn't return any useful information for setting
  THIS_HOST.

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

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

[Kernel-packages] [Bug 1599109] Re: [i915_bpo] Rebase driver to v4.7-rc6 + gen9 workarounds + KBP PCH support

Scratch that, dropped a late-addition WA for BXT from it that would've
required another commit to build.

+bpo5 will be good

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

Title:
  [i915_bpo] Rebase driver to v4.7-rc6 + gen9 workarounds + KBP PCH
  support

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

Bug description:
  i915_bpo driver should sync with v4.7-rc6 to better support
  SKL/KBL/BXT:

  - KBL enabled upstream, meaning v4.7 is first release they add fixes to
  - display power well support on BXT
  - fixes issues on certain machines not resuming properly from S3

  in addition to that, backport gen9 workarounds from drm-intel-next-
  queued:

  d1b4eefdea6d63a drm/i915/gen9: Add WaFbcHighMemBwCorruptionAvoidance
  031cd8c85aefad3 drm/i195/fbc: Add WaFbcNukeOnHostModify
  303d4ea522e8672 drm/i915/gen9: Add WaFbcWakeMemOn
  0f78dee6f06a939 drm/i915/gen9: Add WaFbcTurnOffFbcWatermark
  066d462888514af drm/i915/kbl: Add WaClearSlmSpaceAtContextSwitch
  71dce58c8e90872 drm/i915/skl: Extend WaDisableChickenBitTSGBarrierAckFor
  590e8ff04bc0182 drm/i915/gen9: Add WaEnableChickenDCPR
  954337aa96a31f6 drm/i915/kbl: Add WaDisableSbeCacheDispatchPortSharing
  4de5d7ccbccc88d drm/i915/kbl: Add WaDisableGafsUnitClkGating
  0b2d0934edceff9 drm/i915/kbl: Add WaForGAMHang
  44fff99ff25f1dd drm/i915/skl: Add WAC6entrylatency
  6fc29133eafb9eb drm/i915/gen9: Add WaDisableSkipCaching
  ad2bdb44b19529b drm/i915: Add WaInsertDummyPushConstP for bxt and kbl
  c0b730d572ea00d drm/i915/kbl: Add WaDisableDynamicCreditSharing
  8aeb7f624fbf8a6 drm/i915/kbl: Add WaDisableGamClockGating
  b033bb6d5d3a0e5 drm/i915/gen9: Enable must set chicken bits in config0 reg
  fe90581987cd5fa drm/i915/kbl: Add WaDisableLSQCROPERFforOCL
  17e0adf079a3bf2 drm/i915/edp: Add WaKVMNotificationOnConfigChange:bdw
  9498dba7b4ffe40 drm/i915/kbl: Add WaDisableSDEUnitClockGating
  8401d42fd5adf70 drm/i915/kbl: Add WaDisableFenceDestinationToSLM for A0
  e587f6cb0af140f drm/i915/kbl: Add WaEnableGapsTsvCreditFix
  bbaefe72a00c93c drm/i915: Mimic skl with WaForceEnableNonCoherent
  5b0e3659296cc4a drm/i915/gen9: Always apply WaForceContextSaveRestoreNonCohe
  6e4f10c33a8bd0d drm/i915/kbl: Add WaSkipStolenMemoryFirstPage for A0
  c033a37cd42c1b5 drm/i915/kbl: Add REVID macro
  e5f81d65ac5a040 drm/i915/kbl: Init gen9 workarounds
  eee8efb02a0f928 drm/i915/skl: Add WaDisableGafsUnitClkGating
  6bb6285582e0cf9 drm/i915/gen9: Add WaVFEStateAfterPipeControlwithMediaStateCl

  and another fix to support Kabypoint PCH (fixes blank screen issues on
  such hw):

  22dea0be50b2eb0 drm/i915: Introduce Kabypoint PCH for Kabylake H/DT.

  We should also revert a commit that causes flickering on at least one
  Skylake laptop model, until it's properly fixed:

  https://lists.freedesktop.org/archives/intel-gfx/2016-June/098826.html

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

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

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

The fix was already present in the Yakkety kernel (since the fix in
mainline Linux v4.6, upon which Yakkety is currently based).

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

Title:
  Key 5 automatically pressed on some Logitech wireless keyboards

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1599109] Re: [i915_bpo] Rebase driver to v4.7-rc6 + gen9 workarounds + KBP PCH support

** Description changed:

  i915_bpo driver should sync with v4.7-rc6 to better support SKL/KBL/BXT:
  
  - KBL enabled upstream, meaning v4.7 is first release they add fixes to
  - display power well support on BXT
  - fixes issues on certain machines not resuming properly from S3
  
  in addition to that, backport gen9 workarounds from drm-intel-next-
  queued:
  
- 3485d99e415fade drm/i915:gen9: implement WaMediaPoolStateCmdInWABB
  d1b4eefdea6d63a drm/i915/gen9: Add WaFbcHighMemBwCorruptionAvoidance
  031cd8c85aefad3 drm/i195/fbc: Add WaFbcNukeOnHostModify
  303d4ea522e8672 drm/i915/gen9: Add WaFbcWakeMemOn
  0f78dee6f06a939 drm/i915/gen9: Add WaFbcTurnOffFbcWatermark
  066d462888514af drm/i915/kbl: Add WaClearSlmSpaceAtContextSwitch
  71dce58c8e90872 drm/i915/skl: Extend WaDisableChickenBitTSGBarrierAckFor
  590e8ff04bc0182 drm/i915/gen9: Add WaEnableChickenDCPR
  954337aa96a31f6 drm/i915/kbl: Add WaDisableSbeCacheDispatchPortSharing
  4de5d7ccbccc88d drm/i915/kbl: Add WaDisableGafsUnitClkGating
  0b2d0934edceff9 drm/i915/kbl: Add WaForGAMHang
  44fff99ff25f1dd drm/i915/skl: Add WAC6entrylatency
  6fc29133eafb9eb drm/i915/gen9: Add WaDisableSkipCaching
  ad2bdb44b19529b drm/i915: Add WaInsertDummyPushConstP for bxt and kbl
  c0b730d572ea00d drm/i915/kbl: Add WaDisableDynamicCreditSharing
  8aeb7f624fbf8a6 drm/i915/kbl: Add WaDisableGamClockGating
  b033bb6d5d3a0e5 drm/i915/gen9: Enable must set chicken bits in config0 reg
  fe90581987cd5fa drm/i915/kbl: Add WaDisableLSQCROPERFforOCL
  17e0adf079a3bf2 drm/i915/edp: Add WaKVMNotificationOnConfigChange:bdw
  9498dba7b4ffe40 drm/i915/kbl: Add WaDisableSDEUnitClockGating
  8401d42fd5adf70 drm/i915/kbl: Add WaDisableFenceDestinationToSLM for A0
  e587f6cb0af140f drm/i915/kbl: Add WaEnableGapsTsvCreditFix
  bbaefe72a00c93c drm/i915: Mimic skl with WaForceEnableNonCoherent
  5b0e3659296cc4a drm/i915/gen9: Always apply WaForceContextSaveRestoreNonCohe
  6e4f10c33a8bd0d drm/i915/kbl: Add WaSkipStolenMemoryFirstPage for A0
  c033a37cd42c1b5 drm/i915/kbl: Add REVID macro
  e5f81d65ac5a040 drm/i915/kbl: Init gen9 workarounds
  eee8efb02a0f928 drm/i915/skl: Add WaDisableGafsUnitClkGating
  6bb6285582e0cf9 drm/i915/gen9: Add WaVFEStateAfterPipeControlwithMediaStateCl
  
  and another fix to support Kabypoint PCH (fixes blank screen issues on
  such hw):
  
  22dea0be50b2eb0 drm/i915: Introduce Kabypoint PCH for Kabylake H/DT.
  
  We should also revert a commit that causes flickering on at least one
  Skylake laptop model, until it's properly fixed:
  
  https://lists.freedesktop.org/archives/intel-gfx/2016-June/098826.html

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

Title:
  [i915_bpo] Rebase driver to v4.7-rc6 + gen9 workarounds + KBP PCH
  support

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

Bug description:
  i915_bpo driver should sync with v4.7-rc6 to better support
  SKL/KBL/BXT:

  - KBL enabled upstream, meaning v4.7 is first release they add fixes to
  - display power well support on BXT
  - fixes issues on certain machines not resuming properly from S3

  in addition to that, backport gen9 workarounds from drm-intel-next-
  queued:

  d1b4eefdea6d63a drm/i915/gen9: Add WaFbcHighMemBwCorruptionAvoidance
  031cd8c85aefad3 drm/i195/fbc: Add WaFbcNukeOnHostModify
  303d4ea522e8672 drm/i915/gen9: Add WaFbcWakeMemOn
  0f78dee6f06a939 drm/i915/gen9: Add WaFbcTurnOffFbcWatermark
  066d462888514af drm/i915/kbl: Add WaClearSlmSpaceAtContextSwitch
  71dce58c8e90872 drm/i915/skl: Extend WaDisableChickenBitTSGBarrierAckFor
  590e8ff04bc0182 drm/i915/gen9: Add WaEnableChickenDCPR
  954337aa96a31f6 drm/i915/kbl: Add WaDisableSbeCacheDispatchPortSharing
  4de5d7ccbccc88d drm/i915/kbl: Add WaDisableGafsUnitClkGating
  0b2d0934edceff9 drm/i915/kbl: Add WaForGAMHang
  44fff99ff25f1dd drm/i915/skl: Add WAC6entrylatency
  6fc29133eafb9eb drm/i915/gen9: Add WaDisableSkipCaching
  ad2bdb44b19529b drm/i915: Add WaInsertDummyPushConstP for bxt and kbl
  c0b730d572ea00d drm/i915/kbl: Add WaDisableDynamicCreditSharing
  8aeb7f624fbf8a6 drm/i915/kbl: Add WaDisableGamClockGating
  b033bb6d5d3a0e5 drm/i915/gen9: Enable must set chicken bits in config0 reg
  fe90581987cd5fa drm/i915/kbl: Add WaDisableLSQCROPERFforOCL
  17e0adf079a3bf2 drm/i915/edp: Add WaKVMNotificationOnConfigChange:bdw
  9498dba7b4ffe40 drm/i915/kbl: Add WaDisableSDEUnitClockGating
  8401d42fd5adf70 drm/i915/kbl: Add WaDisableFenceDestinationToSLM for A0
  e587f6cb0af140f drm/i915/kbl: Add WaEnableGapsTsvCreditFix
  bbaefe72a00c93c drm/i915: Mimic skl with WaForceEnableNonCoherent
  5b0e3659296cc4a drm/i915/gen9: Always apply WaForceContextSaveRestoreNonCohe
  6e4f10c33a8bd0d drm/i915/kbl: Add WaSkipStolenMemoryFirstPage for A0
  c033a37cd42c1b5 drm/i915/kbl: Add REVID macro
  e5f81d65ac5a040 drm/i915/kbl: Init gen9 workarounds

[Kernel-packages] [Bug 1588428] Re: PCI bus error on startup while booting into login screen (Kubuntu 16.04)

2016-07-08 Thread Abhishek Bhatia

URL to the mailing list post: http://www.spinics.net/lists/linux-
pci/msg52560.html

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

Title:
  PCI bus error on startup while booting into login screen (Kubuntu
  16.04)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With a HP Pavilion Notebook - 15-ab549tx, and Kubuntu 16.04, the problem is 
on startup error messages show up before the login screen as per attached 
screenshot:
  https://launchpadlibrarian.net/263296837/screenshot.jpg

  At times it is just stops at this screen and doesn't move to the login
  screen. Or while it shuts down it stops at this screen.

  WORKAROUND: Adding kernel boot parameters:
  pci=nomsi
  pci=noaer

  stop the messages from showing on startup, but it takes 2.5 minutes to
  boot.

  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
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abhishek   1332 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Jun  2 21:27:21 2016
  HibernationDevice: RESUME=UUID=bf42c497-2871-4fcb-9c6f-ea792ccf35ab
  InstallationDate: Installed on 2016-05-13 (19 days ago)
  InstallationMedia: Kubuntu 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 0bda:b006 Realtek Semiconductor Corp.
   Bus 001 Device 004: ID 04ca:0060 Lite-On Technology Corp.
   Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=85cd7db1-5379-4a11-84d8-0b7ed7989962 ro quiet splash pci=nomsi 
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: 03/07/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.78
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A4
  dmi.board.vendor: HP
  dmi.board.version: 91.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.78:bd03/07/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A4:rvr91.1D:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1599599] Re: System beep broken (again) in Xenial Xerus

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

Title:
System beep broken (again) in Xenial Xerus

Status in linux package in Ubuntu:
Confirmed

Bug description:
This is my first ever bug report, so bear with me if I make mistakes.

System bell (aka PC speaker beep) is not working upon installing
Ubuntu 16.04 Xenial Xerus.

lsmod shows pcspkr is loaded

Note
The symptoms are exactly the same as in bug #486154
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/486154

Description: Ubuntu 16.04 LTS
Release: 16.04

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

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

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

bastien, the issue you are reporting is an upstream one. Could you please 
report this problem via https://bugs.freedesktop.org/enter_bug.cgi?product=DRI :
Component: DRM/AMDgpu
Hardware: x86-64
OS: Linux (All)
CC: Alex Deucher

Please provide a direct URL to your bug report once you have made it so
that it may be tracked.

Thank you for your help.

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

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

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

Status in linux package in Ubuntu:
  Triaged

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 1599599] Re: System beep broken (again) in Xenial Xerus

First, Thomas, I apologize for sounding irritated above, but if you saw
the volume of comments I've seen addressing the wrong
(external/soundcard) speaker for this problem you would likely agree.

Joseph, I changed the tag to read 'kernel-bug-exists-upstream' as the
problem persists with v4.7-rc6 mainline.

Note the output for $ modeinfo pcspkr

filename:
/lib/modules/4.7.0-040700rc6-generic/kernel/drivers/input/misc/pcspkr.ko
alias: platform:pcspkr
license:GPL
description:PC Speaker beeper driver
author: Vojtech Pavlik
depends:
intree: Y
vermagic: 4.7.0-040700rc6-generic SMP mod_unload modversions

Also, as my previous comment pointed out in the changelog for 4.4.0-28,
I think this bug #582350 is the culprit.

** Tags added: amd64 apport-bug xenial

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

Title:
System beep broken (again) in Xenial Xerus

Status in linux package in Ubuntu:
Incomplete

Bug description:
This is my first ever bug report, so bear with me if I make mistakes.

System bell (aka PC speaker beep) is not working upon installing
Ubuntu 16.04 Xenial Xerus.

lsmod shows pcspkr is loaded

Note
The symptoms are exactly the same as in bug #486154
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/486154

Description: Ubuntu 16.04 LTS
Release: 16.04

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

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

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

-- 
You 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 1599599] Re: System beep broken (again) in Xenial Xerus

** Tags removed: amd64 apport-bug xenial
** Tags added: kernel-bug-exists-upstream

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

Title:
System beep broken (again) in Xenial Xerus

Status in linux package in Ubuntu:
Incomplete

Bug description:
This is my first ever bug report, so bear with me if I make mistakes.

System bell (aka PC speaker beep) is not working upon installing
Ubuntu 16.04 Xenial Xerus.

lsmod shows pcspkr is loaded

Note
The symptoms are exactly the same as in bug #486154
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/486154

Description: Ubuntu 16.04 LTS
Release: 16.04

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

[Kernel-packages] [Bug 1598571] Re: Audio-out on Asus X555 dont work

2016-07-08 Thread Alberto Salvia Novella

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

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

Title:
  Audio-out on Asus X555 dont work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Have problem with headphone/microphone port in my laptop. When plug-in 
headphones, sound resume play on speackers... In Win10 i dont have this 
problem. Physicaly port work good.
  Card: HDA Intel PCH
  Chip: Realtek ALC256

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-30-generic 4.4.0-30.49
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mnaz   1727 F pulseaudio
    mnaz   9456 F alsamixer
  CurrentDesktop: Unity
  Date: Sun Jul  3 15:17:26 2016
  HibernationDevice: RESUME=UUID=773628e6-2536-424b-9a24-4e8c8f0a1892
  InstallationDate: Installed on 2016-06-25 (8 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 004: ID 0bda:57de Realtek Semiconductor Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:0520 Microdia MaxTrack Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555UB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-30-generic.efi.signed 
root=UUID=f9ab2085-6070-4e16-969a-8769d6bd87e3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-30-generic N/A
   linux-backports-modules-4.4.0-30-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  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.:bvrX555UB.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 582350] Re: Please change CONFIG_SND_HDA_INPUT_BEEP_MODE to 0

So we circled back to #486154 again! The broken beep problem came back,
see # 1599599

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

Title:
  Please change CONFIG_SND_HDA_INPUT_BEEP_MODE to 0

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  As discussed in the kernel configuration review session at UDS-M, we
  should alter the default CONFIG_SND_HDA_INPUT_BEEP_MODE value to be 0
  (disabled by default) so that "annoying beeps go away". Note that this
  value is runtime configurable via sysfs, so there is negligible impact
  for a11y context (assuming that the a11y bits to toggle it are in
  place).

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

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

[Kernel-packages] [Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

2016-07-08 Thread Hubba

>>This appears to be fixed in Xenial (16.04) already. Can you confirm?

Yes, migration of Ubuntu 16.04 4.4.0-21-generic #37 works fine.

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

Title:
  Kernel panic after migration between XenServer 6.5 hosts

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

Bug description:
  Problem: after live migration from one XenServer 6.5 server to another
  XenServer 6.5 the Ubuntu VM crashes (see attached screenshot).

  Affected verions (at least):
  1. Ubuntu 14.04 (3.19.0-61-generic)
  2. Ubuntu 16.04 (4.4.0-24-generic)

  Not affected versions:
  1.Ubuntu 14.04 (3.19.0-49-generic)

  The issue is not dependent on installed XenServer updates.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 16 11:23 seq
   crw-rw 1 root audio 116, 33 Jun 16 11:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   69.046113] nf_conntrack version 0.5.0 (7868 buckets, 31472 
max)
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=250f9548-2a14-41c1-bc6e-63199d6e9236
  InstallationDate: Installed on 2016-02-02 (136 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=5a4cba3d-3be6-4a07-9c55-d5ea7b52585e ro ipv6.disable=1 net.ifnames=0 
biosdevname=0
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/11/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.4.1-xs125381
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.4.1-xs125381:bd05/11/2016:svnXen:pnHVMdomU:pvr4.4.1-xs125381:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.4.1-xs125381
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1599599] Re: System beep broken (again) in Xenial Xerus

The problem is definitely 100% in 4.4.0-28-generic.

I installed Ubuntu 16.04 on a different computer and the beep worked
properly. It initially had only 4.4.0-21-generic under /lib/modules/
then updated to 4.4.0-28 and the problem immediately started on that
machine.

I'm going to assume it was this package responsible:
linux-image-extra-4.4.0-28-generic
version 4.4.0-28.47
Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP.

Note in the package changelog attached at line 14362 that reads:

* [Config] Disable CONFIG_SND_HDA_INPUT_BEEP_MODE by default
- LP: #582350

** Attachment added: "changelog"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599599/+attachment/4697388/+files/linux-image-extra-4.4.0-28-generic_changelog.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/1599599

Title:
System beep broken (again) in Xenial Xerus

Status in linux package in Ubuntu:
Incomplete

Bug description:
This is my first ever bug report, so bear with me if I make mistakes.

System bell (aka PC speaker beep) is not working upon installing
Ubuntu 16.04 Xenial Xerus.

lsmod shows pcspkr is loaded

Note
The symptoms are exactly the same as in bug #486154
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/486154

Description: Ubuntu 16.04 LTS
Release: 16.04

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

[Kernel-packages] [Bug 1599109] Re: [i915_bpo] Rebase driver to v4.7-rc6 + gen9 workarounds + KBP PCH support

kernel build (without the revert) available at

https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/ppa

+bpo4 will have all

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

Title:
  [i915_bpo] Rebase driver to v4.7-rc6 + gen9 workarounds + KBP PCH
  support

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

Bug description:
  i915_bpo driver should sync with v4.7-rc6 to better support
  SKL/KBL/BXT:

  - KBL enabled upstream, meaning v4.7 is first release they add fixes to
  - display power well support on BXT
  - fixes issues on certain machines not resuming properly from S3

  in addition to that, backport gen9 workarounds from drm-intel-next-
  queued:

  3485d99e415fade drm/i915:gen9: implement WaMediaPoolStateCmdInWABB
  d1b4eefdea6d63a drm/i915/gen9: Add WaFbcHighMemBwCorruptionAvoidance
  031cd8c85aefad3 drm/i195/fbc: Add WaFbcNukeOnHostModify
  303d4ea522e8672 drm/i915/gen9: Add WaFbcWakeMemOn
  0f78dee6f06a939 drm/i915/gen9: Add WaFbcTurnOffFbcWatermark
  066d462888514af drm/i915/kbl: Add WaClearSlmSpaceAtContextSwitch
  71dce58c8e90872 drm/i915/skl: Extend WaDisableChickenBitTSGBarrierAckFor
  590e8ff04bc0182 drm/i915/gen9: Add WaEnableChickenDCPR
  954337aa96a31f6 drm/i915/kbl: Add WaDisableSbeCacheDispatchPortSharing
  4de5d7ccbccc88d drm/i915/kbl: Add WaDisableGafsUnitClkGating
  0b2d0934edceff9 drm/i915/kbl: Add WaForGAMHang
  44fff99ff25f1dd drm/i915/skl: Add WAC6entrylatency
  6fc29133eafb9eb drm/i915/gen9: Add WaDisableSkipCaching
  ad2bdb44b19529b drm/i915: Add WaInsertDummyPushConstP for bxt and kbl
  c0b730d572ea00d drm/i915/kbl: Add WaDisableDynamicCreditSharing
  8aeb7f624fbf8a6 drm/i915/kbl: Add WaDisableGamClockGating
  b033bb6d5d3a0e5 drm/i915/gen9: Enable must set chicken bits in config0 reg
  fe90581987cd5fa drm/i915/kbl: Add WaDisableLSQCROPERFforOCL
  17e0adf079a3bf2 drm/i915/edp: Add WaKVMNotificationOnConfigChange:bdw
  9498dba7b4ffe40 drm/i915/kbl: Add WaDisableSDEUnitClockGating
  8401d42fd5adf70 drm/i915/kbl: Add WaDisableFenceDestinationToSLM for A0
  e587f6cb0af140f drm/i915/kbl: Add WaEnableGapsTsvCreditFix
  bbaefe72a00c93c drm/i915: Mimic skl with WaForceEnableNonCoherent
  5b0e3659296cc4a drm/i915/gen9: Always apply WaForceContextSaveRestoreNonCohe
  6e4f10c33a8bd0d drm/i915/kbl: Add WaSkipStolenMemoryFirstPage for A0
  c033a37cd42c1b5 drm/i915/kbl: Add REVID macro
  e5f81d65ac5a040 drm/i915/kbl: Init gen9 workarounds
  eee8efb02a0f928 drm/i915/skl: Add WaDisableGafsUnitClkGating
  6bb6285582e0cf9 drm/i915/gen9: Add WaVFEStateAfterPipeControlwithMediaStateCl

  and another fix to support Kabypoint PCH (fixes blank screen issues on
  such hw):

  22dea0be50b2eb0 drm/i915: Introduce Kabypoint PCH for Kabylake H/DT.

  We should also revert a commit that causes flickering on at least one
  Skylake laptop model, until it's properly fixed:

  https://lists.freedesktop.org/archives/intel-gfx/2016-June/098826.html

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

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

[Kernel-packages] [Bug 1599379] Re: Baytrail-I got black screen with HDMI output

2016-07-08 Thread Phidias

** Description changed:

  This issue happens with 4.0+ kernels. Bisecting shows following commit
  cause the issue:
  
  commit d2182a660808d9053a605e3ebc8c46a323ec6e5d
  Author: Ville Syrjälä 
  Date: Fri Jan 9 14:21:14 2015 +0200
  
- drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV
+ drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV
  
  The issue has been reported to upstream [1] and the fix has been merged.
  
+ Although the commit fff7660 fixes the issue, it still misses to probe
+ HDMI port in some circumstance, therefore there's another commit
+ (already merged):
+ 
+ commit a5aac5ab876ad95b7f5e8d862afb07248ee9cae2
+ Author: Ville Syrjälä 
+ CommitDate: Fri Jun 10 10:40:54 2016 +0300
+ 
+ drm/i915: Check VBT for port presence in addition to the strap on
+ VLV/CHV
+ 
  [1]: https://bugs.freedesktop.org/show_bug.cgi?id=96288

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

Title:
  Baytrail-I got black screen with HDMI output

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

Bug description:
  This issue happens with 4.0+ kernels. Bisecting shows following commit
  cause the issue:

  commit d2182a660808d9053a605e3ebc8c46a323ec6e5d
  Author: Ville Syrjälä 
  Date: Fri Jan 9 14:21:14 2015 +0200

  drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV

  The issue has been reported to upstream [1] and the fix has been
  merged.

  Although the commit fff7660 fixes the issue, it still misses to probe
  HDMI port in some circumstance, therefore there's another commit
  (already merged):

  commit a5aac5ab876ad95b7f5e8d862afb07248ee9cae2
  Author: Ville Syrjälä 
  CommitDate: Fri Jun 10 10:40:54 2016 +0300

  drm/i915: Check VBT for port presence in addition to the strap on
  VLV/CHV

  [1]: https://bugs.freedesktop.org/show_bug.cgi?id=96288

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

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

[Kernel-packages] [Bug 1595765] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed to build

2016-07-08 Thread Vincent Gerris

I fixed the issue and submitted a pull request:
https://github.com/longsleep/bcmwl-ubuntu/pull/18
you can find my fork here:
https://github.com/vgerris/bcmwl-ubuntu/
Just follow the instructions and it should work.

Does anyone know where to fix this upstream?
Happy to patch.

Please find the 64 build deb attached for convenience.

Greetings
Vincent


** Attachment added: 
"bcmwl-kernel-source_6.30.223.271+bdcom-1longsleep0_amd64.deb"
   
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1595765/+attachment/4697351/+files/bcmwl-kernel-source_6.30.223.271+bdcom-1longsleep0_amd64.deb

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  error update for kernel 4.7 RC 3

  ProblemType: Package
  DistroRelease: elementary 0.4
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 [origin: Ubuntu]
  Uname: Linux 4.6.2-040602-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.7.0-040700rc3-generic
  Date: Thu Jun 23 22:03:59 2016
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:237:12:
 error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function)
  InstallationDate: Installed on 2016-06-14 (9 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Daily amd64 (20160613)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu8
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1599109] Re: [i915_bpo] Rebase driver to v4.7-rc6 + gen9 workarounds + KBP PCH support