[Kernel-packages] [Bug 1713448] Re: Adobe Reader doesn't print on OKI C911

[Kai-Heng Feng]

I guess it's more CUPS related...

** Also affects: cups (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Adobe Reader doesn't print on OKI C911

Status in cups package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Out and over.
  I tried whatever I could think of, but whatever I send there, anything will 
make the printer blink, 'processing', forever, until I cancel the job. 
  The printer, however, prints the same files from okular, and from all other 
applications that I have tried so far. This would clearly point to acroread. 
  However, acroread prints to all other printers that we have standing about 
without any problem. 

  Logically, from what I could state so far, we have an AND-combination:
  everything works, except I print a file from acroread through OKI
  C911.

  Since I have other printers and other PDF-software, it is minor. And yet, I 
wouldn't mind helping to debug this thing.
  I'm using the OKI-provided ppd with cups. 

  adobereader-enu:i386 9.5.5
  cups 2.1.3-4

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1713016

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

Title:
  XPS 13 9360 touchpad stops working

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just got my XPS 13 9360 developer editions, I updated the BIOS to 2.1.0  
and I installed ubuntu-gnome-16.04.3-desktop-amd64 on it.
  I'm having issues with the trackpad, it behaves erratic and, sometimes, just 
stop working for few seconds, sometimes it stops completely.
  The issues has been reported to DELL already.[1]
  Following the indications in this blog post [2] reduces the problem but does 
not make it disappear. 

  
  [1] 
http://en.community.dell.com/techcenter/os-applications/f/4613/t/19997691?pi9=1
  [2] 
https://medium.com/@patrickmmartin/dell-xps-13-9360-journey-to-linux-trackpad-fix-a2d9b551d291

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

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

[Kernel-packages] [Bug 1688716] Re: screen turns black after reopening lid (laptop)

[Kai-Heng Feng]

Yes. Please run `apport-collect 1688716`.

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

Title:
  screen turns black after reopening lid (laptop)

Status in ubuntu-mate:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I close the laptop lid, the laptop hibernates/(suspends?). When I
  reopen the lid, the fans starts again but the screen is completely
  black.

  I'm running Ubuntu MATE 16.04.2 LTS (installed yesterday) on a ASUS
  TP301U.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1688716/+subscriptions

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

[Kernel-packages] [Bug 1713016] Re: XPS 13 9360 touchpad stops working

[Kai-Heng Feng]

First, try the latest mainline kernel [1] to see if the fix is already
in upstream kernel.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc7/linux-
image-4.13.0-041300rc7-generic_4.13.0-041300rc7.201708272131_amd64.deb


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

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

Title:
  XPS 13 9360 touchpad stops working

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  I just got my XPS 13 9360 developer editions, I updated the BIOS to 2.1.0  
and I installed ubuntu-gnome-16.04.3-desktop-amd64 on it.
  I'm having issues with the trackpad, it behaves erratic and, sometimes, just 
stop working for few seconds, sometimes it stops completely.
  The issues has been reported to DELL already.[1]
  Following the indications in this blog post [2] reduces the problem but does 
not make it disappear. 

  
  [1] 
http://en.community.dell.com/techcenter/os-applications/f/4613/t/19997691?pi9=1
  [2] 
https://medium.com/@patrickmmartin/dell-xps-13-9360-journey-to-linux-trackpad-fix-a2d9b551d291

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

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

[Kernel-packages] [Bug 1712508] Re: Disappearing screen and flickering after upgrade to 16.04

[Kai-Heng Feng]

You don't need to touch those DKMS to install mainline kernel.

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

Title:
  Disappearing screen and flickering after upgrade to 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have two Lenovo T410s that I upgraded from 14.04 to 16.04.
  Since then, one is working fine while the other shows mainly an ever 
disappearing screen and flickering.

  I have asked here: 
https://askubuntu.com/questions/947233/i-upgraded-from-kubuntu-14-04-lts-to-16-04-lts-and-now-my-screen-shows-up-and-di?noredirect=1#comment1506995_947233
  I also found I am not the only one: 
https://askubuntu.com/questions/927407/flickering-screen-with-intel-graphics-on-ubuntu-17-04?noredirect=1#comment1507937_927407
  The latter has tried pretty much that could be tried already, to no avail.

  I think that I can help with this problem, since my two T410s are
  identical in hard- and software, including BIOS, except that one is a
  type 2924 (with NVIDIA-card, though disabled in the BIOS), and the
  other one is a 2904 (without NVIDIA card).

  I have checked for differences at boot time and found DMAR as major 
difference:
  T410s, 2924: [ 0.335616] DMAR: Disabling batched IOTLB flush on Ironlake
  T410s, 2904: [ 0.355681] DMAR: BIOS has allocated no shadow GTT; disabling 
IOMMU for graphics 

  Should this be initially at the root of the problem, I'd consider the
  kernel package as responsible, therefore I marked it as above.

  The outputs of lspci -k | grep -EA3 'VGA|3D|Display' are identical to
  the point.

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

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

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

[NancyHsu]

Download file:
linux-image-4.4.0-20-generic_4.4.0-20.36_amd64.deb
linux-image-extra-4.4.0-20-generic_4.4.0-20.36_amd64.deb

This issue can be reproduced on 4.4.0-20 kernel.
OS installer via PXE and then update to 4.4.0-20 kernel, that still would stop 
at tty7 and it doesn't switch straight to a tty1.

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1709257] Re: [Bug] Harrisonville: pnd2_edac always fail to load on B1 stepping Harrisonville SDP

[quanxian]

>From comment#2, patch bfd4473b850c was not pushed into upstream.
Currently it has been in upstream now.

Comment from upstream
"
The patch "bfd4473b850c i2c: i801: Restore the presence state of P2SB PCI 
device after reading BAR" has been pushed on the 'for-next' branch of I2C 
maintainer Wolfram Sang.
'

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

Title:
  [Bug] Harrisonville: pnd2_edac always fail to load on B1 stepping
  Harrisonville SDP

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

Bug description:
  Description:
  During our EDAC validation on Wind River Linux 9, we found pnd2_edac manually 
load always fails on B1 stepping Harrisonville SDP.
  Error info as below:
  root@intel-x86-64:~# uname -r
  4.8.20-WR9.0.0.5_standard
  root@intel-x86-64:~# dmesg |grep -i edac
  [   11.949838] EDAC MC: Ver: 3.0.0
  [   11.954312] EDAC DEBUG: edac_mc_sysfs_init: device mc created
  [   12.060157] EDAC DEBUG: pnd2_init:
  [   12.060160] EDAC DEBUG: pnd2_probe:
  [   12.060167] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000
  [   12.060169] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_lo_pci=_8000
  [   12.060172] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_hi_pci=_0004
  [   12.060228] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region0_mchbar=_
  [   12.060239] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region1_mchbar=_
  [   12.060247] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_base_mchbar=_
  [   12.060255] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_mask_mchbar=_
  [   12.078301] Modules linked in: pnd2_edac(+) edac_core x86_pkg_temp_thermal 
i2c_i801 intel_powerclamp matroxfb_base matroxfb_g450 matroxfb_accel 
matroxfb_DAC1064 g450_pll matroxfb_misc i2c_ismt i2c_smbus coretemp 
crct10dif_pclmul crct10dif_common aesni_intel aes_x86_64 glue_helper lrw 
gf128mul ablk_helper cryptd efi_pstore efivars acpi_cpufreq tpm_tis 
tpm_tis_core softdog efivarfs
  [   12.143390]  [] ? dnv_rd_reg+0x128/0x220 [pnd2_edac]
  [   12.148890]  [] dnv_rd_reg+0x128/0x220 [pnd2_edac]
  [   12.148896]  [] pnd2_init+0x22b/0x809 [pnd2_edac]
  [   12.148961] EDAC pnd2: Failed to register device with error -19.
  [   12.180813] EDAC DEBUG: pnd2_init:
  [   12.180814] EDAC DEBUG: pnd2_probe:
  [   12.180841] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000
  [   12.180937] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_lo_pci=_8000
  [   12.180969] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_hi_pci=_0004
  [   12.181129] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region0_mchbar=_
  [   12.181299] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region1_mchbar=_
  [   12.181425] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_base_mchbar=_
  [   12.181671] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_mask_mchbar=_
  [   12.181810] EDAC pnd2: Failed to register device with error -19.
  root@intel-x86-64:~# dmesg -c > dmesg.clear_14.D91.log
  root@intel-x86-64:~# modprobe edac_core
  root@intel-x86-64:~# modprobe pnd2_edac
  modprobe: ERROR: could not insert 'pnd2_edac': No such device
  root@intel-x86-64:~# dmesg
  [  194.524122] EDAC DEBUG: pnd2_init:
  [  194.524126] EDAC DEBUG: pnd2_probe:
  [  194.524135] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000
  [  194.524139] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_lo_pci=_8000
  [  194.524143] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_hi_pci=_0004
  [  194.524211] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region0_mchbar=_
  [  194.524226] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region1_mchbar=_
  [  194.524239] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_base_mchbar=_
  [  194.524252] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_mask_mchbar=_
  [  194.524264] EDAC pnd2: Failed to register device with error -19.
  root@intel-x86-64:~# dmidecode -t bios | grep Version
  Version: HAVLCRB1.X64.0014.D91.1704200405

  Target Kernel: 4.14
  Target Release: 18.04
  if 17.10, it will need back porting

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

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

[Kernel-packages] [Bug 1713470] Re: linux: 4.10.0-34.38 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-zesty

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  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
  
  backports: 1713471,1713472
  derivatives: 1713473
  kernel-stable-phase-changed:Monday, 28. August 2017 19:32 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.10.0-34.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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:
  Confirmed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  New

Bug description:
  This bug is for tracking the  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

  backports: 1713471,1713472
  derivatives: 1713473
  kernel-stable-phase-changed:Monday, 28. August 2017 19:32 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1713017] Re: Enable MIDI support

[wvengen]

For those seeking a workaround, see instructions here:
https://gist.github.com/wvengen/7ebd29da38c08540832fb228c4628171#bluez-546

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

Title:
  Enable MIDI support

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  Now that bluez has landed with 5.46-0ubuntu2, it would be nice to
  enable Bluetooth MIDI support. This did not seem to be enabled by
  default in the build from
  https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE
  MIDI devices, gatttool could talk to them, but no MIDI device was
  made; also ldd showed no linkage to libasound.so.2).

  After recompiling it with libasound2-dev installed and --enable-midi
  in debian/rules, it worked.

  Suggestion: add libasound2-dev to bluez dependencies, add --enable-
  midi to rules.

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

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

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

[Samantha Jian-Pielak]

@nancy-hsu
Scroll down on 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9583414 
you can find download link for 
linux-image-4.4.0-20-generic_4.4.0-20.36_amd64.deb and 
linux-image-extra-4.4.0-20-generic_4.4.0-20.36_amd64.deb
Here are the links for your quick reference:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9583414/+files/linux-image-4.4.0-20-generic_4.4.0-20.36_amd64.deb
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9583414/+files/linux-image-extra-4.4.0-20-generic_4.4.0-20.36_amd64.deb

Thanks for your testing so far. All the upstream kernel (mainline) you
have tested (4.9, 4.8, 4.4.40, 4.4.35 and 4.4.44) are fine, the two
Ubuntu kernels 4.4.0-59 (based on upstream 4.4.35) and 4.4.0-64 (based
on upstream 4.4.44) the bug can be reproduced. As #37, we need to find a
working Ubuntu kernel to identify where the bug is first introduced,
hence the request to test 4.4.0-20.

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

[dann frazier]

Here's a backport for zesty's QEMU, tested with the 4.13.0-7.8 kernel
from ppa:canonical-kernel-team/unstable w/ the patch from Comment #10
applied.

** Changed in: qemu (Ubuntu)
   Status: In Progress => 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/1710019

Title:
  support GICv3 ITS save/restore & migration

Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in qemu source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in qemu source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Virtual machines on GICv3-based ARM systems cannot be saved/restored or 
migrated.
  This feature was added in QEMU 2.10.

  [Test Case]
  ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav

  Domain 7936-0 saved to 7936-0.sav

  ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav
  error: Failed to restore domain from 7396-0.sav
  error: operation failed: job: unexpectedly failed

  ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log 
  2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by 
non-migratable device 'arm_gicv3_its'
  2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: 
Invalid argument
  2017-08-10 21:26:38.217+: shutting down, reason=failed

  [Regression Risk]

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

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

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

[dann frazier]

@Vijaya: Yes, that patch does resolve the issue for me, thanks! Do you
plan to submit this upstream?

@Christian: Yep - I'll open one.

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

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

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

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

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

** Changed in: qemu (Ubuntu)
 Assignee: dann frazier (dannf) => (unassigned)

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

Title:
  support GICv3 ITS save/restore & migration

Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in qemu source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in qemu source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Virtual machines on GICv3-based ARM systems cannot be saved/restored or 
migrated.
  This feature was added in QEMU 2.10.

  [Test Case]
  ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav

  Domain 7936-0 saved to 7936-0.sav

  ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav
  error: Failed to restore domain from 7396-0.sav
  error: operation failed: job: unexpectedly failed

  ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log 
  2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by 
non-migratable device 'arm_gicv3_its'
  2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: 
Invalid argument
  2017-08-10 21:26:38.217+: shutting down, reason=failed

  [Regression Risk]

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

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

[Kernel-packages] [Bug 1713576] sched/fair: Prefer sibiling only if local group is under-utilized

[bugproxy]

Default Comment by Bridge

** Attachment added: "sched/fair: Prefer sibiling only if local group is 
under-utilized"
   
https://bugs.launchpad.net/bugs/1713576/+attachment/4940432/+files/05b40e0577.patch

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

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

Title:
  More migrations with constant load

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PUVICHAKRAVARTHY RAMACHANDRAN  - 2017-08-06 13:44:45 ==
  ---Problem Description---
  Significantly higher number of task migrations when the load is fixed but not 
balanced across cores.
   
  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Power9 dd2.0 

  Machine Type = Power9 
   
  ---Steps to Reproduce---
   Benchmark : Multithreaded - cpu intensive. The system had 2 socket/ 32 
cores/ SMT4 mode.

  When 64 threads was run - the migrations were less over 10s interval.
  when 80 threads were run - the migrations were very high.

  Ideally, it should have been very minimal, as the over all load was constant
   
  == Comment: #3 - SRIKAR DRONAMRAJU - 2017-08-11 06:56:47 ==
  As suspected (commit :  05b40e0577 : "sched/fair: Prefer sibiling only if 
local group is under-utilized")
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05b40e0577
  should fix the problem

  Ran ' perf stat -a -r 5 -e sched:sched_migrate_task 
/home/srikar/work/ebizzy-0.3/ebizzy -t 35 -S 100'
  to detect the problem and verify the fix

  Here is perf stat without fix.

  Performance counter stats for 'system wide' (5 runs):

   7,758  sched:sched_migrate_task
  ( +-  1.28% )

   100.015658079 seconds time elapsed
  ( +-  0.00% )

  perf stat with fix.

  Performance counter stats for 'system wide' (5 runs):

 415  sched:sched_migrate_task
  ( +- 11.74% )

   100.016021787 seconds time elapsed
  ( +-  0.00% )

  
  git describe on upstream kernel says v4.11-rc2
  # git describe 05b40e0577
  v4.11-rc2-227-g05b40e0

  == Comment: #4 - SRIKAR DRONAMRAJU - 2017-08-11 07:05:37 ==
  Attaching the patch that needs to be applied to fix this bug.
  Verified that patch fixes the problem.

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

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

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

[bugproxy]

--- Comment From ha...@us.ibm.com 2017-08-28 17:22 EDT---
Problem still occurs on current 16.04, at least with the 4.4-series kernel: 
cpupower still suggests installation of "cloud" packages and they still don't 
exist (at least for for ppc64le):

$ dpkg -l | egrep 'linux-(tools|cloud-tools)'
ii  linux-tools-common   4.4.0-93.116   all   Linux kernel version specific 
tools for version 4.4.0

$ cpupower
WARNING: cpupower not found for kernel 4.4.0-92

You may need to install the following packages for this specific kernel:
linux-tools-4.4.0-92-generic
linux-cloud-tools-4.4.0-92-generic

You may also want to install one of the following packages to keep up to date:
linux-tools-generic
linux-cloud-tools-generic

$ apt-cache policy linux-cloud-tools-generic linux-cloud-tools-4.4.0-92-generic 
linux-cloud-tools-4.4.0-93-generic
N: Unable to locate package linux-cloud-tools-generic
N: Unable to locate package linux-cloud-tools-4.4.0-92-generic
N: Couldn't find any package by glob 'linux-cloud-tools-4.4.0-92-generic'
N: Couldn't find any package by regex 'linux-cloud-tools-4.4.0-92-generic'
N: Unable to locate package linux-cloud-tools-4.4.0-93-generic
N: Couldn't find any package by glob 'linux-cloud-tools-4.4.0-93-generic'
N: Couldn't find any package by regex 'linux-cloud-tools-4.4.0-93-generic'

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

Title:
  cpupower suggests installation of non-existent linux-cloud-tools-
  generic package

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem Description
  ===
  cpupower suggests installation of non-existent linux-cloud-tools-generic 
package

  Problem occurs on an IBM POWER 16.04 LTS system. Unknown whether it
  occurs on other architectures or later releases.

  When run _without package "linux-tools-$(uname -r)" installed_,
  cpupower will issue a complaint, suggesting to install (among others),
  some linux-cloud-tools-*-generic packages:

  $ cpupower
  WARNING: cpupower not found for kernel 4.4.0-75

You may need to install the following packages for this specific kernel:
  linux-tools-4.4.0-75-generic
  linux-cloud-tools-4.4.0-75-generic

You may also want to install one of the following packages to keep up to 
date:
  linux-tools-generic
  linux-cloud-tools-generic

  However, those linux-cloud-tools-*-generic package appear not to exist
  --at least not in the default repos.

  Package linux-cloud-tools-common exists, but none of the *-generic
  packages are available:

  $ apt-cache policy "linux-cloud-*"
  $ cat xxx
  linux-cloud-tools-common:
Installed: (none)
Candidate: 4.4.0-78.99
Version table:
   4.4.0-78.99 500
  500 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el 
Packages
   4.4.0-77.98 500
  500 http://us.ports.ubuntu.com/ubuntu-ports xenial-updates/main 
ppc64el Packages
   4.4.0-75.96 500
  500 http://us.ports.ubuntu.com/ubuntu-ports xenial-updates/main 
ppc64el Packages
  500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main ppc64el 
Packages
  [...]
   4.4.0-21.37 500
  500 http://us.ports.ubuntu.com/ubuntu-ports xenial/main ppc64el 
Packages

  
  The cpupower command works (at least doesn't give this complaint) if the 
appropriate linux-tools-$(uname -r) (perhaps via linux-tools-generic) is 
installed, so the cloud package is maybe not needed (as least for some 
functionality).

  I think the fix is to either: 
  a) supply the cloud packages for POWER, or 
  b) remove the non-existent packages from cpupower's complaint message.
   
  ---uname output---
  Linux fs3 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:55:30 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Firestone 
   
  ---Steps to Reproduce---
   Install linux-tools-common but NOT linux-tools-*-generic on a POWER 16.04 
LTS system, then run cpupower.

  Userspace rpm: linux-tools-common

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

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

[Kernel-packages] [Bug 1713576] [NEW] More migrations with constant load

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - PUVICHAKRAVARTHY RAMACHANDRAN  - 2017-08-06 13:44:45 ==
---Problem Description---
Significantly higher number of task migrations when the load is fixed but not 
balanced across cores.
 
---uname output---
Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
 
---Additional Hardware Info---
Power9 dd2.0 

Machine Type = Power9 
 
---Steps to Reproduce---
 Benchmark : Multithreaded - cpu intensive. The system had 2 socket/ 32 cores/ 
SMT4 mode.

When 64 threads was run - the migrations were less over 10s interval.
when 80 threads were run - the migrations were very high.

Ideally, it should have been very minimal, as the over all load was constant
 
== Comment: #3 - SRIKAR DRONAMRAJU - 2017-08-11 06:56:47 ==
As suspected (commit :  05b40e0577 : "sched/fair: Prefer sibiling only if local 
group is under-utilized")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05b40e0577
should fix the problem

Ran ' perf stat -a -r 5 -e sched:sched_migrate_task 
/home/srikar/work/ebizzy-0.3/ebizzy -t 35 -S 100'
to detect the problem and verify the fix

Here is perf stat without fix.

Performance counter stats for 'system wide' (5 runs):

 7,758  sched:sched_migrate_task
( +-  1.28% )

 100.015658079 seconds time elapsed
( +-  0.00% )

perf stat with fix.

Performance counter stats for 'system wide' (5 runs):

   415  sched:sched_migrate_task
( +- 11.74% )

 100.016021787 seconds time elapsed
( +-  0.00% )


git describe on upstream kernel says v4.11-rc2
# git describe 05b40e0577
v4.11-rc2-227-g05b40e0

== Comment: #4 - SRIKAR DRONAMRAJU - 2017-08-11 07:05:37 ==
Attaching the patch that needs to be applied to fix this bug.
Verified that patch fixes the problem.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-157336 severity-high 
targetmilestone-inin16043
-- 
More migrations with constant load
https://bugs.launchpad.net/bugs/1713576
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1701137] Re: enable ARCH_SUNXI (and friends) in arm64 kernel .config

[Andre Przywara]

> There are numerous drivers disabled...

The 64-bit Allwinner SoCs share a lot of devices with their 32-bit
predecessors (or siblings), so we also share some config symbols, most
prominently ARCH_SUNXI. However some of those supported devices are only
in older SoCs (Sun4i generation, for instance), and will never be needed
for an *arm64* kernel (take Sun4i sound drivers, for example). In the
wake of avoiding to bloat the kernel (or the number of modules)
needlessly, we can safely disable drivers for which there is no AArch64
capable SoC using those devices. I marked those as "not in 64-bit
Allwinner SoCs" in the list above.

> The way we normally handle boot-critical modules ...

I understand that, and can see the reasons why. It's just for my work (hacking 
and testing kernels, and not being on Ubuntu) it's very inconvenient to always 
build a matching initrd, and it's just those two symbols needed to boot into an 
SD card based rootfs without one.
If this is of no concern for you, then it's fine to leave them as =m.

Thanks!

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

Title:
  enable ARCH_SUNXI (and friends) in arm64 kernel .config

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

Bug description:
  The mainline support for the ARM64 Allwinner SoCs (featured on the Pine64 
boards and the Pinebook notebook, for instance, as well as other development 
boards like the BananaPi-M64) has come a long way by now, since 4.11 we have 
MMC and USB support working.
  Now can we just enable the proper .config bits to make the official Ubuntu 
kernel support those boards? The latest mainline U-Boot can load an EFI grub 
from some UEFI ESP partition, so any standard EFI installer should work.
  Apart from some minor hiccup (a missing MBR bootable flag/MBR at all) this 
works already with the Debian-testing netinst installer.
  The config symbols needed for decent support are (all enabled by the latest 
Debian kernel and the official mainline defconfig):
  ARCH_SUNXI=y
  CONFIG_USB_MUSB_SUNXI=m
  CONFIG_MMC_SUNXI=m
  CONFIG_RTC_DRV_SUN6I=y
  CONFIG_PHY_SUN4I_USB=y

  Those enable MMC and USB (the mandatory clocks, pinctrl and UART are enabled 
by default) and make those boards quite usable already. The on-SoC Ethernet 
driver will probably be merged into 4.13-rc1.
  Optionally:
  CONFIG_I2C_MV64XXX=m
  CONFIG_SPI_SUN6I=m
  give us I2C and SPI support as well.

  So can we add those symbols to the Ubuntu kernel .config to give users
  an out-of-the-box experience?

  Cheers,
  Andre.

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

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

[Kernel-packages] [Bug 1713575] [NEW] Vlun resize request could fail with cxlflash driver

[bugproxy]

Public bug reported:

== Comment: #0 - UMA KRISHNAN  - 2017-08-28 12:14:12 ==
---Problem Description---
Recently a regression in cxlflash driver was identified and a fix has been 
upstreamed to  kernel.org. We would like to get that included in Xenial 16.04.3 
SRU (HWE v4.10 kernel). Even though regression patch is the very last one, I 
have also listed the missing patches in-between, that are minor and will be 
easier for further cxlflash updates to Xenial.

eeac8cda2c957e156093933b860eec09e488fe15 scsi: cxlflash: return -EFAULT if 
copy_from_user() fails
9ff870417e56b1fb7b15b2cda74de639d3cd8559 scsi: cxlflash: Fix an error handling 
path in 'cxlflash_disk_attach()'
48a17ad5931c3832eec68411620bc3527021c193 scsi: cxlflash: Remove unnecessary 
existence check
1a9e394154e34728f58c1f697b993aaaf89a4db2 scsi: cxlflash: Avoid double mutex 
unlock
07a191f762a7b8d0db13c38036380927116e29bb scsi: cxlflash: Fix vlun resize 
failure in the shrink path
 
---Steps to Reproduce---
 Vlun resize request could fail after updating to a kernel that includes Commit 
565180723294 ("scsi: cxlflash: SISlite updates to support 4 ports")

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-158076 severity-high 
targetmilestone-inin---

** Tags added: architecture-ppc64le bugnameltc-158076 severity-high
targetmilestone-inin---

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

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

Title:
  Vlun resize request could fail with cxlflash driver

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - UMA KRISHNAN  - 2017-08-28 12:14:12 ==
  ---Problem Description---
  Recently a regression in cxlflash driver was identified and a fix has been 
upstreamed to  kernel.org. We would like to get that included in Xenial 16.04.3 
SRU (HWE v4.10 kernel). Even though regression patch is the very last one, I 
have also listed the missing patches in-between, that are minor and will be 
easier for further cxlflash updates to Xenial.

  eeac8cda2c957e156093933b860eec09e488fe15 scsi: cxlflash: return -EFAULT if 
copy_from_user() fails
  9ff870417e56b1fb7b15b2cda74de639d3cd8559 scsi: cxlflash: Fix an error 
handling path in 'cxlflash_disk_attach()'
  48a17ad5931c3832eec68411620bc3527021c193 scsi: cxlflash: Remove unnecessary 
existence check
  1a9e394154e34728f58c1f697b993aaaf89a4db2 scsi: cxlflash: Avoid double mutex 
unlock
  07a191f762a7b8d0db13c38036380927116e29bb scsi: cxlflash: Fix vlun resize 
failure in the shrink path
   
  ---Steps to Reproduce---
   Vlun resize request could fail after updating to a kernel that includes 
Commit 565180723294 ("scsi: cxlflash: SISlite updates to support 4 ports")

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

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

[Kernel-packages] [Bug 1689365] Re: ibmvscsis: Do not send aborted task response

[bugproxy]

** Tags removed: bugnameltc-154092 severity-high triage-g ubuntu-17.04
verification-done-zesty

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

Title:
  ibmvscsis: Do not send aborted task response

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  ibmvscsis: Do not send aborted task response

  The driver is sending a response to the actual scsi op that was
  aborted by an abort task TM, while LIO is sending a response to
  the abort task TM.

  ibmvscsis_tgt does not send the response to the client until
  release_cmd time. The reason for this was because if we did it
  at queue_status time, then the client would be free to reuse the
  tag for that command, but we're still using the tag until the
  command is released at release_cmd time, so we chose to delay
  sending the response until then. That then caused this issue, because
  release_cmd is always called, even if queue_status is not.

  SCSI spec says that the initiator that sends the abort task
  TM NEVER gets a response to the aborted op and with the current
  code it will send a response. Thus this fix will remove that response
  if the CMD_T_ABORTED && !CMD_T_TAS.

  Another case with a small timing window is the case where if LIO sends a
  TMR_DOES_NOT_EXIST, and the release_cmd callback is called for the TMR Abort
  cmd before the release_cmd for the (attemped) aborted cmd, then we need to
  ensure that we send the response for the (attempted) abort cmd to the client
  before we send the response for the TMR Abort cmd.

  [Test Case]
  As per comment #11, this requires sending manual abort signals to trigger the 
bug.

  [Fix]
  ibmvscsis: Fix the incorrect req_lim_delta
  ibmvscsis: Clear left-over abort_cmd pointers
  ibmvscsis: Do not send aborted task response
  target: Fix unknown fabric callback queue-full errors

  [Regression Potential]
  Patches are confined to ibmvscsi driver and target driver.

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

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

[Kernel-packages] [Bug 1713575] [NEW] Vlun resize request could fail with cxlflash driver

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - UMA KRISHNAN  - 2017-08-28 12:14:12 ==
---Problem Description---
Recently a regression in cxlflash driver was identified and a fix has been 
upstreamed to  kernel.org. We would like to get that included in Xenial 16.04.3 
SRU (HWE v4.10 kernel). Even though regression patch is the very last one, I 
have also listed the missing patches in-between, that are minor and will be 
easier for further cxlflash updates to Xenial.

eeac8cda2c957e156093933b860eec09e488fe15 scsi: cxlflash: return -EFAULT if 
copy_from_user() fails
9ff870417e56b1fb7b15b2cda74de639d3cd8559 scsi: cxlflash: Fix an error handling 
path in 'cxlflash_disk_attach()'
48a17ad5931c3832eec68411620bc3527021c193 scsi: cxlflash: Remove unnecessary 
existence check
1a9e394154e34728f58c1f697b993aaaf89a4db2 scsi: cxlflash: Avoid double mutex 
unlock
07a191f762a7b8d0db13c38036380927116e29bb scsi: cxlflash: Fix vlun resize 
failure in the shrink path
 
---Steps to Reproduce---
 Vlun resize request could fail after updating to a kernel that includes Commit 
565180723294 ("scsi: cxlflash: SISlite updates to support 4 ports")

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-158076 severity-high 
targetmilestone-inin---
-- 
Vlun resize request could fail with cxlflash driver
https://bugs.launchpad.net/bugs/1713575
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
501faf881377dc38998fe8603ee1767d61883cfb

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1701222

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

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

Bug description:
  Issue description: Hyper-V daemons fail to start after disable/re-
  enable VM integration services.

  Platform: host independent
  Affected daemons - KVP, FCOPY and VSS.

  Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
  Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 
4.10.0-19-generic (for Ubuntu 17.04)

  Repro rate: 100%

  Steps to reproduce:
  1.Start VM with Guest Services enabled (FCopy daemon starts automatically)
  2.Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
  3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
  This is the issue. systemd monitors for the service and if we have the hook 
for the Guest Service, it tries to start the daemon again.
  systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

  Additional Info:
  - the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
  - Manually starting hv_fcopy_daemon works fine.
  - other distros (RHEL) does not have this behavior, the LIS daemons are 
started automatically by systemd once we re-enable the integration service.

  On the upstream kernel and the upstream hv daemons, these messages are 
recorded in syslog, once we re-enable the Guest service:
  HV_FCOPY: pread failed: Bad file descriptor
  systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
  systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

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

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

[Kernel-packages] [Bug 1701137] Re: enable ARCH_SUNXI (and friends) in arm64 kernel .config

[Seth Forshee]

There are numerous drivers disabled in the supplied diff which can be
configured as modules. What's the reason for not including these?

The way we normally handle boot-critical modules is to include them in
the installer, and then they will automatically be included in the
initrd built for each new kernel as it is installed. Is there any
special reason that we need to make the drivers you mentioned built-in
instead of doing this?

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

Title:
  enable ARCH_SUNXI (and friends) in arm64 kernel .config

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

Bug description:
  The mainline support for the ARM64 Allwinner SoCs (featured on the Pine64 
boards and the Pinebook notebook, for instance, as well as other development 
boards like the BananaPi-M64) has come a long way by now, since 4.11 we have 
MMC and USB support working.
  Now can we just enable the proper .config bits to make the official Ubuntu 
kernel support those boards? The latest mainline U-Boot can load an EFI grub 
from some UEFI ESP partition, so any standard EFI installer should work.
  Apart from some minor hiccup (a missing MBR bootable flag/MBR at all) this 
works already with the Debian-testing netinst installer.
  The config symbols needed for decent support are (all enabled by the latest 
Debian kernel and the official mainline defconfig):
  ARCH_SUNXI=y
  CONFIG_USB_MUSB_SUNXI=m
  CONFIG_MMC_SUNXI=m
  CONFIG_RTC_DRV_SUN6I=y
  CONFIG_PHY_SUN4I_USB=y

  Those enable MMC and USB (the mandatory clocks, pinctrl and UART are enabled 
by default) and make those boards quite usable already. The on-SoC Ethernet 
driver will probably be merged into 4.13-rc1.
  Optionally:
  CONFIG_I2C_MV64XXX=m
  CONFIG_SPI_SUN6I=m
  give us I2C and SPI support as well.

  So can we add those symbols to the Ubuntu kernel .config to give users
  an out-of-the-box experience?

  Cheers,
  Andre.

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

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

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

[Ubuntu Kernel Bot]

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

Title:
  package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to
  install/upgrade: подпроцесс установлен сценарий post-removal возвратил
  код ошибки 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  W: Целевые пакеты (partner / binary-amd64 / Packages): Целевые пакеты
  (partner / binary-amd64 / Packages) настраиваются несколько раз в
  /etc/apt/sources.list:41 и /etc/apt/sources.list.d/xenial-
  partner.list:4, W: Целевые пакеты (partner / binary-i386 / Packages)
  настроены несколько раз в /etc/apt/sources.list:41 и
  /etc/apt/sources.list.d/xenial-partner.list:4, W: целевые пакеты
  (partner / binary-all / Packages) настраивается несколько раз в
  /etc/apt/sources.list:41 и /etc/apt/sources.list.d/xenial-
  partner.list:4, W: Целевые переводы (партнер / i18n / Translation-en)
  настраивается несколько раз в /etc/apt/sources.list:41 и
  /etc/apt/sources.list.d/xenial-partner.list:4, W: Целевые переводы
  (партнер / i18n / Translation-en_GB) настроен несколько раз в
  /etc/apt/sources.list:41 и /etc/apt/sources.list.d/xenial-
  partner.list:4, W: Целевые переводы (партнер / i18n / Перевод -ru)
  настраивается несколько раз в /etc/apt/sources.list:41 и
  /etc/apt/sources.list.d/xenial-partner.list:4, W: Target DEP-11
  (partner / dep11 / Components -amd6 4.yml) настраивается несколько раз
  в /etc/apt/sources.list:41 и /etc/apt/sources.list.d/xenial-
  partner.list:4, W: целевые DEP-11-значки (партнер / dep11 / icons-
  64x64.tar) настраивается несколько раз в /etc/apt/sources.list:41 и
  /etc/apt/sources.list.d/xenial-partner.list:4, W: репозиторий 'cdrom:
  // Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) xenial
  Release 'не имеет файла Release. W: данные из такого репозитория не
  могут быть аутентифицированы и поэтому потенциально опасны для
  использования. W: см. Apt- secure (8) manpage для создания репозитория
  и сведений о конфигурации пользователя. W: репозиторий
  «http://ppa.launchpad.net/aap/xbmc-release-fernetmenta/ubuntu xenial
  Release» не имеет файла деблокировки., W : Данные из такого
  репозитория не могут быть аутентифицированы и поэтому потенциально
  опасны для использования. W: см. Man-страницу apt-secure (8) для
  создания репозитория и сведений о конфигурации пользователя. W:
  Репозиторий 'http: // ppa. launchpad.net/stedy6/stedy-minidna/ubuntu
  xenial Release 'делает не имеет файла Release., W: данные из такого
  репозитория не могут быть аутентифицированы и поэтому потенциально
  опасны для использования. W: см. man-страницу apt-secure (8) для
  создания репозитория и сведений о конфигурации пользователя. W:
  репозиторий 'http://ppa.launchpad.net/tualatrix/ppa/ubuntu xenial
  Release' не имеет файла Release. W: данные из такого репозитория не
  могут быть аутентифицированы и поэтому потенциально опасны для
  использования., W : См. Man-страницу apt-secure (8) для создания
  репозитория и сведений о конфигурации пользователя. W: в репозитории
  «http://ppa.launchpad.net/upubuntu-com/gtk3themes/ubuntu xenial
  Release» нет файла Release. , W: данные из такого репозитория не могут
  быть аутентифицированы и поэтому потенциально опасны для
  использования. W: см. Справочную страницу apt-secure (8) для создания
  репозитория и сведений о конфигурации пользователя. W: репозиторий
  'http: // ppa.launchpad.net/venerix/pkg/ubuntu xenial Release 'не
  имеет файла Release., W: данные из такого репозитория не могут быть
  аутентифицированы и, следовательно, опасно для использования., W: см.
  man-страницу apt-secure (8) для создания репозитория и подробные
  сведения о конфигурации пользователя. W: репозиторий
  «http://ppa.launchpad.net/voria/ppa/ubuntu xenial Release» не имеют
  файл Release., W: данные из такого репозитория не могут быть
  аутентифицированы и поэтому потенциально опасны для использования. W:
  см. man-страницу apt-secure (8) для создания репозитория и сведений о
  конфигурации пользователя., W: https:
  //linuxdesktopcloud.mail.ru/deb/dists/appind/InRelease: Подпись по
  ключу 8A99BA500079839DF7DE4833196205AF7396FF77 использует слабый
  алгоритм дайджеста (SHA1), E: Не удалось получить cdrom: // Ubuntu
  16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) / dists / xenial
  / main / binary-amd64 / Пакеты Пожалуйста, используйте apt-cdrom,
  чтобы этот CD-ROM был распознан APT. Обновление apt-get не может
  использоваться для добавления новых CD-ROM, E: Не удалось получить
  http://ppa.launchpad.net/aap/xbmc-release-
  fernetmenta/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Не
  найдено, E: Не удалось получить http://ppa.launchpad.net/stedy6/stedy-
  minidna/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Not Found,
  E: Не удалось получить http: /
  

[Kernel-packages] [Bug 1713572] [NEW] package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1

[ddimaa]

Public bug reported:

W: Целевые пакеты (partner / binary-amd64 / Packages): Целевые пакеты
(partner / binary-amd64 / Packages) настраиваются несколько раз в
/etc/apt/sources.list:41 и /etc/apt/sources.list.d/xenial-
partner.list:4, W: Целевые пакеты (partner / binary-i386 / Packages)
настроены несколько раз в /etc/apt/sources.list:41 и
/etc/apt/sources.list.d/xenial-partner.list:4, W: целевые пакеты
(partner / binary-all / Packages) настраивается несколько раз в
/etc/apt/sources.list:41 и /etc/apt/sources.list.d/xenial-
partner.list:4, W: Целевые переводы (партнер / i18n / Translation-en)
настраивается несколько раз в /etc/apt/sources.list:41 и
/etc/apt/sources.list.d/xenial-partner.list:4, W: Целевые переводы
(партнер / i18n / Translation-en_GB) настроен несколько раз в
/etc/apt/sources.list:41 и /etc/apt/sources.list.d/xenial-
partner.list:4, W: Целевые переводы (партнер / i18n / Перевод -ru)
настраивается несколько раз в /etc/apt/sources.list:41 и
/etc/apt/sources.list.d/xenial-partner.list:4, W: Target DEP-11 (partner
/ dep11 / Components -amd6 4.yml) настраивается несколько раз в
/etc/apt/sources.list:41 и /etc/apt/sources.list.d/xenial-
partner.list:4, W: целевые DEP-11-значки (партнер / dep11 / icons-
64x64.tar) настраивается несколько раз в /etc/apt/sources.list:41 и
/etc/apt/sources.list.d/xenial-partner.list:4, W: репозиторий 'cdrom: //
Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) xenial
Release 'не имеет файла Release. W: данные из такого репозитория не
могут быть аутентифицированы и поэтому потенциально опасны для
использования. W: см. Apt- secure (8) manpage для создания репозитория и
сведений о конфигурации пользователя. W: репозиторий
«http://ppa.launchpad.net/aap/xbmc-release-fernetmenta/ubuntu xenial
Release» не имеет файла деблокировки., W : Данные из такого репозитория
не могут быть аутентифицированы и поэтому потенциально опасны для
использования. W: см. Man-страницу apt-secure (8) для создания
репозитория и сведений о конфигурации пользователя. W: Репозиторий
'http: // ppa. launchpad.net/stedy6/stedy-minidna/ubuntu xenial Release
'делает не имеет файла Release., W: данные из такого репозитория не
могут быть аутентифицированы и поэтому потенциально опасны для
использования. W: см. man-страницу apt-secure (8) для создания
репозитория и сведений о конфигурации пользователя. W: репозиторий
'http://ppa.launchpad.net/tualatrix/ppa/ubuntu xenial Release' не имеет
файла Release. W: данные из такого репозитория не могут быть
аутентифицированы и поэтому потенциально опасны для использования., W :
См. Man-страницу apt-secure (8) для создания репозитория и сведений о
конфигурации пользователя. W: в репозитории «http://ppa.launchpad.net
/upubuntu-com/gtk3themes/ubuntu xenial Release» нет файла Release. , W:
данные из такого репозитория не могут быть аутентифицированы и поэтому
потенциально опасны для использования. W: см. Справочную страницу apt-
secure (8) для создания репозитория и сведений о конфигурации
пользователя. W: репозиторий 'http: //
ppa.launchpad.net/venerix/pkg/ubuntu xenial Release 'не имеет файла
Release., W: данные из такого репозитория не могут быть
аутентифицированы и, следовательно, опасно для использования., W: см.
man-страницу apt-secure (8) для создания репозитория и подробные
сведения о конфигурации пользователя. W: репозиторий
«http://ppa.launchpad.net/voria/ppa/ubuntu xenial Release» не имеют файл
Release., W: данные из такого репозитория не могут быть
аутентифицированы и поэтому потенциально опасны для использования. W:
см. man-страницу apt-secure (8) для создания репозитория и сведений о
конфигурации пользователя., W: https:
//linuxdesktopcloud.mail.ru/deb/dists/appind/InRelease: Подпись по ключу
8A99BA500079839DF7DE4833196205AF7396FF77 использует слабый алгоритм
дайджеста (SHA1), E: Не удалось получить cdrom: // Ubuntu 16.04 LTS
_Xenial Xerus_ - Release amd64 (20160420.1) / dists / xenial / main /
binary-amd64 / Пакеты Пожалуйста, используйте apt-cdrom, чтобы этот CD-
ROM был распознан APT. Обновление apt-get не может использоваться для
добавления новых CD-ROM, E: Не удалось получить
http://ppa.launchpad.net/aap/xbmc-release-
fernetmenta/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Не
найдено, E: Не удалось получить http://ppa.launchpad.net/stedy6/stedy-
minidna/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Not Found, E:
Не удалось получить http: /
/ppa.launchpad.net/tualatrix/ppa/ubuntu/dists/xenial/main/binary-
amd64/Packages 404 Not Found, E: Не удалось получить
http://ppa.launchpad.net/upubuntu-com/gtk3themes/ubuntu / dists / xenial
/ main / binary-amd64 / Пакеты 404 Не найдено, E: Не удалось получить
http://ppa.launchpad.net/venerix/pkg/ubuntu/dists/xenial/main/binary-
amd64/Packages 404 Not Найдено, E: Не удалось получить
http://ppa.launchpad.net/voria/ppa/ubuntu/dists/xenial/main/binary-
amd64/Packages 404 Not Found, E: Некоторым индексным файлам не удалось
загрузить. Они были проигнорированы или использовались старые.

ProblemType: 

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

[quadra]

I think we should focus on the the essential.
This bug has nothing to do with broken hardware. It's a regression. And as 
such, I think it should have HIGH importance, not medium.

xev shows the left and right buttons, but no event for middle/scroll
wheel button.

I've used the middle button for many years, in many (X)Ubuntu releases,
with many mouses. Now it's broken.

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

  xinput list shows the USB receiver 2 times:

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

  Listing the capabilities looks like this:

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

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

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

[Kernel-packages] [Bug 1712626] Re: Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => 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/1712626

Title:
  Cannot launch virtual instance on nova host after upgrading to kernel
  4.4.0.92- works with 4.4.0.83

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

Bug description:
  Host -- IBM Power 8  822L
  OS- Ubuntu 14.04 ppc64el
  previous kernel 3.19.0.68
  Nova Compute host using kvm - Openstack Liberty

  HWE was out of date so needed to update

  Steps:

  sudo apt-get install linux-generic-lts-xenial linux-image-generic-lts-xenial
  sudo init 6
  sudo apt update
  sudo apt upgrade
  sudo init 6

  afterwards - system seemed ok - kernel 4.4.0.92 installed

  However, launching a Ubuntu VM failed

  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246360] Facility 'TM' unavailable, 
exception at 0xd000189f85a0, MSR=90009033
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246374] Oops: Unexpected facility 
unavailable exception, sig: 6 [#1]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246379] SMP NR_CPUS=2048 NUMA PowerNV
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246385] Modules linked in: vhost_net 
vhost macvtap macvlan xt_REDIRECT nf_nat_redirect xt_mark xt_nat ip6table_raw 
nf_conntrack_ipv6
   xt_CT xt_mac xt_comment xt_physdev br_netfilter iptable_raw veth xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrac
  k_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables 
x_tables vport_gre ip_gre 
  ip_tunnel gre nbd kvm_hv kvm ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi openvswitch 
nf_defrag_ipv6 nf_conn
  track dm_crypt bridge stp llc dm_multipath uio_pdrv_genirq ipmi_powernv 
ipmi_msghandler uio ibmpowernv powernv_rng vmx_crypto leds_powernv ses 
enclosure bnx2x vxlan ip6_udp_
  tunnel udp_tunnel mdio libcrc32c ipr
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246500] CPU: 96 PID: 52779 Comm: 
qemu-system-ppc Not tainted 4.4.0-92-generic #115~14.04.1-Ubuntu
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246506] task: c01e228dcf60 ti: 
c01e229f4000 task.ti: c01e229f4000
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246511] NIP: d000189f85a0 LR: 
d000188a2584 CTR: d000189f84f0
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246516] REGS: c01e229f7840 TRAP: 
0f60   Not tainted  (4.4.0-92-generic)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246519] MSR: 90009033 
  CR: 28022448  XER: 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] CFAR: d000189f8534 
SOFTE: 1 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR00: d000188a2584 
c01e229f7ac0 d00018a0c7f8 c01c4c68 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR04: c01c5308 
c01e229f7bc0  0004 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR08: 0001 
c01e228dcf60  d000188a7518 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR12: d000189f84f0 
cfb79000 3fff7d74ed40 3fff7d74f3d0 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR16: 3fff7cf5 
 0003 3fff7d750010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR20: 100c0570 
01000f6ebba0 0080 3fff85644330 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR24:  
3fff7cf30028 d4f6d401 0010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR28:  
c01c4c68 c01c4c68 c01c5308 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246594] NIP [d000189f85a0] 
kvmppc_vcpu_run_hv+0xb0/0x610 [kvm_hv]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246606] LR [d000188a2584] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246610] Call Trace:
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246617] [c01e229f7ac0] 
[c00ca294] recalc_sigpending+0x24/0x90 (unreliable)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246630] [c01e229f7b70] 
[d000188a2584] kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246642] [c01e229f7ba0] 
[d0001889f274] kvm_arch_vcpu_ioctl_run+0x64/0x180 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246653] [c01e229f7be0] 
[d00018893898] kvm_vcpu_ioctl+0x5e8/0x7c0 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246661] [c01e229f7d40] 
[c02ef7d0] do_vfs_ioctl+0x4d0/0x7e0
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246667] [c01e229f7de0] 
[c02efbb4] SyS_ioctl+0xd4/0xf0
  

[Kernel-packages] [Bug 1676884] Re: kdump-tools uses the wrong crashkernel command line parameter in ppc64le

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: New => Fix Released

** Tags removed: triage-a
** Tags added: triage-g

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

Title:
  kdump-tools uses the wrong crashkernel command line parameter in
  ppc64le

Status in The Ubuntu-power-systems project:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  == Comment: #0 - Thiago Jung Bauermann  - 2017-03-24 
11:44:39 ==
  ---Problem Description---
  kdump-tools uses the wrong crashkernel command line parameter in ppc64le:

  u1704le?? grep crashkernel /boot/grub/grub.cfg
  linux   /boot/vmlinux-4.10.0-13-generic 
root=UUID=2d6f73c7-b463-4f02-9ec4-8d4afed0635d ro   crashkernel=384M-:128M

  128M of reserved memory is too small for ppc64le.

  That happens because /etc/default/grub.d/kdump-tools.cfg links to the
  wrong file:

  u1704le??  ls -l /etc/default/grub.d/
  total 8.0K
  lrwxrwxrwx 1 root root  39 Mar 24 13:34 kdump-tools.cfg -> 
/etc/default/grub.d/kdump-tools.default
  -rw-r--r-- 1 root root  80 Jan  5 08:07 kdump-tools.default
  -rw-r--r-- 1 root root 137 Jan  5 08:07 kdump-tools..ppc64el
  u1704le?? 

  As can be seen, it should be pointing to kdump-tools..ppc64el but
  isn't.

  Also, kdump-tools..ppc64el has two dots in it. That doesn't seem right.
  Possibly just a cosmetic issue, but it would be nice if that was fixed.
   
  Contact Information = thiag...@br.ibm.com 
   
  ---uname output---
  Linux u1704le 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Any ppc64le machine. In this case, a KVM guest hosted on an 
8286-42A. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   sudo apt intall kdump-tools
  Select 'Yes' when asked whether kdump should be enabled.
   
  Userspace tool common name: kdump 
   
  The userspace tool has the following bit modes: 64 bit 

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for thiag...@br.ibm.com:
  -Attach ltrace and strace of userspace application.

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

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

[Kernel-packages] [Bug 1712626] Re: Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

[Blake Henderson]

I noticed that the repo now has kernel 4.4.0-93 available- i tried that
but it did not work either - it also seemed to set SMT to 8 which caused
me a few problems until i realized what it did.

I rebooted with kernel 4.4.0.94 and all is well again (after I set SMT
to off)

Hopefully the new kernel will be available in the repo soon.
Also wondering if x86 is experiencing same issue, since I have 6 x86 nova hosts 
to update too.

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

Title:
  Cannot launch virtual instance on nova host after upgrading to kernel
  4.4.0.92- works with 4.4.0.83

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

Bug description:
  Host -- IBM Power 8  822L
  OS- Ubuntu 14.04 ppc64el
  previous kernel 3.19.0.68
  Nova Compute host using kvm - Openstack Liberty

  HWE was out of date so needed to update

  Steps:

  sudo apt-get install linux-generic-lts-xenial linux-image-generic-lts-xenial
  sudo init 6
  sudo apt update
  sudo apt upgrade
  sudo init 6

  afterwards - system seemed ok - kernel 4.4.0.92 installed

  However, launching a Ubuntu VM failed

  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246360] Facility 'TM' unavailable, 
exception at 0xd000189f85a0, MSR=90009033
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246374] Oops: Unexpected facility 
unavailable exception, sig: 6 [#1]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246379] SMP NR_CPUS=2048 NUMA PowerNV
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246385] Modules linked in: vhost_net 
vhost macvtap macvlan xt_REDIRECT nf_nat_redirect xt_mark xt_nat ip6table_raw 
nf_conntrack_ipv6
   xt_CT xt_mac xt_comment xt_physdev br_netfilter iptable_raw veth xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrac
  k_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables 
x_tables vport_gre ip_gre 
  ip_tunnel gre nbd kvm_hv kvm ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi openvswitch 
nf_defrag_ipv6 nf_conn
  track dm_crypt bridge stp llc dm_multipath uio_pdrv_genirq ipmi_powernv 
ipmi_msghandler uio ibmpowernv powernv_rng vmx_crypto leds_powernv ses 
enclosure bnx2x vxlan ip6_udp_
  tunnel udp_tunnel mdio libcrc32c ipr
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246500] CPU: 96 PID: 52779 Comm: 
qemu-system-ppc Not tainted 4.4.0-92-generic #115~14.04.1-Ubuntu
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246506] task: c01e228dcf60 ti: 
c01e229f4000 task.ti: c01e229f4000
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246511] NIP: d000189f85a0 LR: 
d000188a2584 CTR: d000189f84f0
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246516] REGS: c01e229f7840 TRAP: 
0f60   Not tainted  (4.4.0-92-generic)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246519] MSR: 90009033 
  CR: 28022448  XER: 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] CFAR: d000189f8534 
SOFTE: 1 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR00: d000188a2584 
c01e229f7ac0 d00018a0c7f8 c01c4c68 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR04: c01c5308 
c01e229f7bc0  0004 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR08: 0001 
c01e228dcf60  d000188a7518 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR12: d000189f84f0 
cfb79000 3fff7d74ed40 3fff7d74f3d0 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR16: 3fff7cf5 
 0003 3fff7d750010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR20: 100c0570 
01000f6ebba0 0080 3fff85644330 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR24:  
3fff7cf30028 d4f6d401 0010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR28:  
c01c4c68 c01c4c68 c01c5308 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246594] NIP [d000189f85a0] 
kvmppc_vcpu_run_hv+0xb0/0x610 [kvm_hv]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246606] LR [d000188a2584] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246610] Call Trace:
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246617] [c01e229f7ac0] 
[c00ca294] recalc_sigpending+0x24/0x90 (unreliable)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246630] [c01e229f7b70] 
[d000188a2584] kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246642] [c01e229f7ba0] 
[d0001889f274] kvm_arch_vcpu_ioctl_run+0x64/0x180 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246653] [c01e229f7be0] 

[Kernel-packages] [Bug 1713470] Re: linux: 4.10.0-34.38 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  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
  
  backports: 1713471,1713472
  derivatives: 1713473
+ kernel-stable-phase-changed:Monday, 28. August 2017 19:32 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  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
  
  backports: 1713471,1713472
  derivatives: 1713473
  kernel-stable-phase-changed:Monday, 28. August 2017 19:32 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.10.0-34.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  New

Bug description:
  This bug is for tracking the  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

  backports: 1713471,1713472
  derivatives: 1713473
  kernel-stable-phase-changed:Monday, 28. August 2017 19:32 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Manoj Iyer]

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: ubuntu-power-systems
   Status: Triaged => In Progress

** Tags removed: triage-r
** Tags added: triage-g

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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

[Kernel-packages] [Bug 1702998] Re: Ubuntu 17.04: Guest crashed @writeback_sb_inodes+0x310/0x590

[Manoj Iyer]

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

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

Title:
  Ubuntu 17.04: Guest crashed @writeback_sb_inodes+0x310/0x590

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Lata Kuntal  - 2017-03-03 00:50:54 ==
  Ubuntu 17.04 guest dropped at xmon after crashing at 
writeback_sb_inodes+0x310/0x590. 
  The guest is having XFS rootfs and NPIV disk. It crashed after 30+ hrs of 
BASE and NFS stress test .

  Crash logs
  ===
  root@guskvm:~# virsh console gusg1 --force
  Connected to domain gusg1
  Escape character is ^]

  0:mon>
  0:mon> t
  [c000a4bc7940] c036f790 writeback_sb_inodes+0x310/0x590
  [c000a4bc7a50] c036faf4 __writeback_inodes_wb+0xe4/0x150
  [c000a4bc7ab0] c036ff1c wb_writeback+0x2cc/0x440
  [c000a4bc7b80] c0370c30 wb_workfn+0x150/0x560
  [c000a4bc7c90] c00ed8c0 process_one_work+0x2b0/0x5a0
  [c000a4bc7d20] c00edc58 worker_thread+0xa8/0x650
  [c000a4bc7dc0] c00f67b4 kthread+0x154/0x1a0
  [c000a4bc7e30] c000b4e8 ret_from_kernel_thread+0x5c/0x74
  0:mon> r
  R00 = c036f790   R16 = c000eca70300
  R01 = c000a4bc78e0   R17 = c000f7035240
  R02 = c143c900   R18 = 
  R03 = c000f7035150   R19 = 
  R04 = 0019   R20 = c000a4bc4000
  R05 = 0100   R21 = ff7f
  R06 =    R22 = c433d758
  R07 =    R23 = c433d738
  R08 = 00034995   R24 = 
  R09 =    R25 = 
  R10 = 8000   R26 = c000f70351d8
  R11 = c000a4bc7a40   R27 = 
  R12 = 2200   R28 = 0001
  R13 = cfb8   R29 = c433d728
  R14 =    R30 = c000f7035150
  R15 = c000f70351d8   R31 = 
  pc  = c036c120 locked_inode_to_wb_and_lock_list+0x50/0x290
  cfar= c00b2a14 kvmppc_save_tm+0x168/0x16c
  lr  = c036f790 writeback_sb_inodes+0x310/0x590
  msr = 80009033   cr  = 24002482
  ctr = c0381e30   xer =    trap =  300
  dar =    dsisr = 4000
  0:mon> e
  cpu 0x0: Vector: 300 (Data Access) at [c000a4bc7660]
  pc: c036c120: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c036f790: writeback_sb_inodes+0x310/0x590
  sp: c000a4bc78e0
 msr: 80009033
 dar: 0
   dsisr: 4000
current = 0xc000fbe96000
paca= 0xcfb8   softe: 0irq_happened: 0x01
  pid   = 17305, comm = kworker/u16:0
  Linux version 4.10.0-8-generic (buildd@bos01-ppc64el-001) (gcc version 6.3.0 
20161229 (Ubuntu 6.3.0-2ubuntu1) ) #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 
(Ubuntu 4.10.0-8.10-generic 4.10.0-rc8)
  0:mon> d
      ||
  0:mon>

  
  Host and guest kernel build
  =
  4.10.0-8-generic

  
  OPAL firmware version
  
T side: FW860.20 (SV860_078)
Boot side : FW860.20 (SV860_078)

  
  == Comment: #4 - VIPIN K. PARASHAR  - 2017-03-03 
02:55:20 ==
  [140071.761707] Adding 153536k swap on /dev/loop0.  Priority:-2 extents:1 
across:153536k FS
  [140072.153143] Adding 153472k swap on /dev/loop0.  Priority:-2 extents:1 
across:153472k FS
  [140072.441833] Unable to handle kernel paging request for data at address 
0x
  [140072.442064] Faulting instruction address: 0xc036c120
  0:mon>

  0:mon> e
  cpu 0x0: Vector: 300 (Data Access) at [c000a4bc7660]
  pc: c036c120: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c036f790: writeback_sb_inodes+0x310/0x590
  sp: c000a4bc78e0
 msr: 80009033
 dar: 0
   dsisr: 4000
current = 0xc000fbe96000
paca= 0xcfb8 softe: 0irq_happened: 0x01
  pid   = 17305, comm = kworker/u16:0
  Linux version 4.10.0-8-generic (buildd@bos01-ppc64el-001) (gcc version 6.3.0 
20161229 (Ubuntu 6.3.0-2ubuntu1) ) #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 
(Ubuntu 4.10.0-8.10-generic 4.10.0-rc8)
  0:mon> t
  [c000a4bc7940] c036f790 writeback_sb_inodes+0x310/0x590
  [c000a4bc7a50] c036faf4 __writeback_inodes_wb+0xe4/0x150
  [c000a4bc7ab0] c036ff1c wb_writeback+0x2cc/0x440
  [c000a4bc7b80] c0370c30 wb_workfn+0x150/0x560
  [c000a4bc7c90] c00ed8c0 process_one_work+0x2b0/0x5a0
  [c000a4bc7d20] c00edc58 

[Kernel-packages] [Bug 1709257] Re: [Bug] Harrisonville: pnd2_edac always fail to load on B1 stepping Harrisonville SDP

[Seth Forshee]

Applied the indicated patches to 4.13. With 4.12 there were still
problems cherry picking, but there were just a few small patches in 4.13
so I just went ahead and pulled in all of these as well:

ee514c7a2379 EDAC, pnd2: Return proper error value from apl_rd_reg()
77641dacead2 EDAC, pnd2: Make function sbi_send() static
164c29244d4b EDAC, pnd2: Fix Apollo Lake DIMM detection

** Changed in: linux (Ubuntu Artful)
   Status: Incomplete => 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/1709257

Title:
  [Bug] Harrisonville: pnd2_edac always fail to load on B1 stepping
  Harrisonville SDP

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

Bug description:
  Description:
  During our EDAC validation on Wind River Linux 9, we found pnd2_edac manually 
load always fails on B1 stepping Harrisonville SDP.
  Error info as below:
  root@intel-x86-64:~# uname -r
  4.8.20-WR9.0.0.5_standard
  root@intel-x86-64:~# dmesg |grep -i edac
  [   11.949838] EDAC MC: Ver: 3.0.0
  [   11.954312] EDAC DEBUG: edac_mc_sysfs_init: device mc created
  [   12.060157] EDAC DEBUG: pnd2_init:
  [   12.060160] EDAC DEBUG: pnd2_probe:
  [   12.060167] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000
  [   12.060169] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_lo_pci=_8000
  [   12.060172] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_hi_pci=_0004
  [   12.060228] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region0_mchbar=_
  [   12.060239] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region1_mchbar=_
  [   12.060247] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_base_mchbar=_
  [   12.060255] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_mask_mchbar=_
  [   12.078301] Modules linked in: pnd2_edac(+) edac_core x86_pkg_temp_thermal 
i2c_i801 intel_powerclamp matroxfb_base matroxfb_g450 matroxfb_accel 
matroxfb_DAC1064 g450_pll matroxfb_misc i2c_ismt i2c_smbus coretemp 
crct10dif_pclmul crct10dif_common aesni_intel aes_x86_64 glue_helper lrw 
gf128mul ablk_helper cryptd efi_pstore efivars acpi_cpufreq tpm_tis 
tpm_tis_core softdog efivarfs
  [   12.143390]  [] ? dnv_rd_reg+0x128/0x220 [pnd2_edac]
  [   12.148890]  [] dnv_rd_reg+0x128/0x220 [pnd2_edac]
  [   12.148896]  [] pnd2_init+0x22b/0x809 [pnd2_edac]
  [   12.148961] EDAC pnd2: Failed to register device with error -19.
  [   12.180813] EDAC DEBUG: pnd2_init:
  [   12.180814] EDAC DEBUG: pnd2_probe:
  [   12.180841] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000
  [   12.180937] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_lo_pci=_8000
  [   12.180969] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_hi_pci=_0004
  [   12.181129] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region0_mchbar=_
  [   12.181299] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region1_mchbar=_
  [   12.181425] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_base_mchbar=_
  [   12.181671] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_mask_mchbar=_
  [   12.181810] EDAC pnd2: Failed to register device with error -19.
  root@intel-x86-64:~# dmesg -c > dmesg.clear_14.D91.log
  root@intel-x86-64:~# modprobe edac_core
  root@intel-x86-64:~# modprobe pnd2_edac
  modprobe: ERROR: could not insert 'pnd2_edac': No such device
  root@intel-x86-64:~# dmesg
  [  194.524122] EDAC DEBUG: pnd2_init:
  [  194.524126] EDAC DEBUG: pnd2_probe:
  [  194.524135] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000
  [  194.524139] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_lo_pci=_8000
  [  194.524143] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_hi_pci=_0004
  [  194.524211] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region0_mchbar=_
  [  194.524226] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region1_mchbar=_
  [  194.524239] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_base_mchbar=_
  [  194.524252] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_mask_mchbar=_
  [  194.524264] EDAC pnd2: Failed to register device with error -19.
  root@intel-x86-64:~# dmidecode -t bios | grep Version
  Version: HAVLCRB1.X64.0014.D91.1704200405

  Target Kernel: 4.14
  Target Release: 18.04
  if 17.10, it will need back porting

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

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

[Kernel-packages] [Bug 1702998] Re: Ubuntu 17.04: Guest crashed @writeback_sb_inodes+0x310/0x590

[Manoj Iyer]

** Tags removed: triage-g
** Tags added: triage-r

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

Title:
  Ubuntu 17.04: Guest crashed @writeback_sb_inodes+0x310/0x590

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Lata Kuntal  - 2017-03-03 00:50:54 ==
  Ubuntu 17.04 guest dropped at xmon after crashing at 
writeback_sb_inodes+0x310/0x590. 
  The guest is having XFS rootfs and NPIV disk. It crashed after 30+ hrs of 
BASE and NFS stress test .

  Crash logs
  ===
  root@guskvm:~# virsh console gusg1 --force
  Connected to domain gusg1
  Escape character is ^]

  0:mon>
  0:mon> t
  [c000a4bc7940] c036f790 writeback_sb_inodes+0x310/0x590
  [c000a4bc7a50] c036faf4 __writeback_inodes_wb+0xe4/0x150
  [c000a4bc7ab0] c036ff1c wb_writeback+0x2cc/0x440
  [c000a4bc7b80] c0370c30 wb_workfn+0x150/0x560
  [c000a4bc7c90] c00ed8c0 process_one_work+0x2b0/0x5a0
  [c000a4bc7d20] c00edc58 worker_thread+0xa8/0x650
  [c000a4bc7dc0] c00f67b4 kthread+0x154/0x1a0
  [c000a4bc7e30] c000b4e8 ret_from_kernel_thread+0x5c/0x74
  0:mon> r
  R00 = c036f790   R16 = c000eca70300
  R01 = c000a4bc78e0   R17 = c000f7035240
  R02 = c143c900   R18 = 
  R03 = c000f7035150   R19 = 
  R04 = 0019   R20 = c000a4bc4000
  R05 = 0100   R21 = ff7f
  R06 =    R22 = c433d758
  R07 =    R23 = c433d738
  R08 = 00034995   R24 = 
  R09 =    R25 = 
  R10 = 8000   R26 = c000f70351d8
  R11 = c000a4bc7a40   R27 = 
  R12 = 2200   R28 = 0001
  R13 = cfb8   R29 = c433d728
  R14 =    R30 = c000f7035150
  R15 = c000f70351d8   R31 = 
  pc  = c036c120 locked_inode_to_wb_and_lock_list+0x50/0x290
  cfar= c00b2a14 kvmppc_save_tm+0x168/0x16c
  lr  = c036f790 writeback_sb_inodes+0x310/0x590
  msr = 80009033   cr  = 24002482
  ctr = c0381e30   xer =    trap =  300
  dar =    dsisr = 4000
  0:mon> e
  cpu 0x0: Vector: 300 (Data Access) at [c000a4bc7660]
  pc: c036c120: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c036f790: writeback_sb_inodes+0x310/0x590
  sp: c000a4bc78e0
 msr: 80009033
 dar: 0
   dsisr: 4000
current = 0xc000fbe96000
paca= 0xcfb8   softe: 0irq_happened: 0x01
  pid   = 17305, comm = kworker/u16:0
  Linux version 4.10.0-8-generic (buildd@bos01-ppc64el-001) (gcc version 6.3.0 
20161229 (Ubuntu 6.3.0-2ubuntu1) ) #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 
(Ubuntu 4.10.0-8.10-generic 4.10.0-rc8)
  0:mon> d
      ||
  0:mon>

  
  Host and guest kernel build
  =
  4.10.0-8-generic

  
  OPAL firmware version
  
T side: FW860.20 (SV860_078)
Boot side : FW860.20 (SV860_078)

  
  == Comment: #4 - VIPIN K. PARASHAR  - 2017-03-03 
02:55:20 ==
  [140071.761707] Adding 153536k swap on /dev/loop0.  Priority:-2 extents:1 
across:153536k FS
  [140072.153143] Adding 153472k swap on /dev/loop0.  Priority:-2 extents:1 
across:153472k FS
  [140072.441833] Unable to handle kernel paging request for data at address 
0x
  [140072.442064] Faulting instruction address: 0xc036c120
  0:mon>

  0:mon> e
  cpu 0x0: Vector: 300 (Data Access) at [c000a4bc7660]
  pc: c036c120: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c036f790: writeback_sb_inodes+0x310/0x590
  sp: c000a4bc78e0
 msr: 80009033
 dar: 0
   dsisr: 4000
current = 0xc000fbe96000
paca= 0xcfb8 softe: 0irq_happened: 0x01
  pid   = 17305, comm = kworker/u16:0
  Linux version 4.10.0-8-generic (buildd@bos01-ppc64el-001) (gcc version 6.3.0 
20161229 (Ubuntu 6.3.0-2ubuntu1) ) #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 
(Ubuntu 4.10.0-8.10-generic 4.10.0-rc8)
  0:mon> t
  [c000a4bc7940] c036f790 writeback_sb_inodes+0x310/0x590
  [c000a4bc7a50] c036faf4 __writeback_inodes_wb+0xe4/0x150
  [c000a4bc7ab0] c036ff1c wb_writeback+0x2cc/0x440
  [c000a4bc7b80] c0370c30 wb_workfn+0x150/0x560
  [c000a4bc7c90] c00ed8c0 process_one_work+0x2b0/0x5a0
  [c000a4bc7d20] c00edc58 worker_thread+0xa8/0x650
  [c000a4bc7dc0] c00f67b4 kthread+0x154/0x1a0
  [c000a4bc7e30] 

[Kernel-packages] [Bug 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.

[Manoj Iyer]

** Tags removed: triage-r
** Tags added: triage-g

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

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in Linux:
  Unknown
Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 or
  aacraid driver.

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have a filesystem or OS installed,
  so there must be at least two disks made available to HTX by clearing
  any previous data. A partition table is optional, in my testing I have
  none.

  Also, it may be desirable to run HTX somewhere other than the console,
  leaving the console free to watch for messages.

  To run:

  A. su - htx (this may take some time)
  B. htx
  C. Select 

[Kernel-packages] [Bug 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.

[Manoj Iyer]

** Tags added: triage-r

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

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in Linux:
  Unknown
Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 or
  aacraid driver.

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have a filesystem or OS installed,
  so there must be at least two disks made available to HTX by clearing
  any previous data. A partition table is optional, in my testing I have
  none.

  Also, it may be desirable to run HTX somewhere other than the console,
  leaving the console free to watch for messages.

  To run:

  A. su - htx (this may take some time)
  B. htx
  C. Select the test file "mdt.io"
  D. 

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

[bugproxy]

--- Comment From jhop...@us.ibm.com 2017-08-28 14:42 EDT---
(In reply to comment #7)
> IBM, How does this bug affect package perforate ? These patches seem to be
> kernel patches.

Looks like that was a mistake in the mirror request. These are all
kernel/perf changes.  I am not sure how to fix the mirrored package from
our bugzilla side.. can this please be corrected from the launchpad
side? Thanks!

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

Title:
  [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New
Status in perforate package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2017-08-16 
04:07:45 ==
  Please integrate the following PMU fixes for P9.

  93fc5ca9a0048c ('powerpc/perf: Cleanup of PM_BR_CMPL vs. PM_BRU_CMPL in 
Power9 event list')
  91e0bd1e62519b ('powerpc/perf: Add PM_LD_MISS_L1 and PM_BR_2PATH to power9 
event list')
  70a7e720998d5b ('powerpc/perf: Factor out PPMU_ONLY_COUNT_RUN check code from 
power8')
  7aa345d84245a7 ('powerpc/perf: Update default sdar_mode value for power9')
  101dd590a7fa37 ('powerpc/perf: Avoid spurious PMU interrupts after idle')
  bdd21ddb919d28 ('powerpc/perf: Avoid spurious PMU interrupts after idle on 
Power9')
  3f0bd8dad0db73 ('powerpc/perf: Add POWER9 alternate PM_RUN_CYC and 
PM_RUN_INST_CMPL events')
  20dd4c624d2515 ('powerpc/perf: Fix SDAR_MODE value for continous sampling on 
Power9')
  24bedcb7c81137 ('powerpc/perf: Fix branch event code for power9')
  8c218578fcbbbd ('powerpc/perf: Fix Power9 test_adder fields')

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

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

[Kernel-packages] [Bug 1713553] Re: Intel i40e PF reset due to incorrect MDD detection

[Dan Streetman]

Note there is one additional upstream commit that improves performance
by allowing up to 12k per tx descriptor, instead of 8k per descriptor
(the current code in Xenial 4.4 kernel), and its changes are related to
the fixes for this issue.  However, from my reading of the code, I don't
think that commit is actually required to fix this problem, so I am not
including it in this bug (yet).

commit 5c4654daf2e2f25dfbd7fa572c59937ea6d4198b
Author: Alexander Duyck 
Date:   Fri Feb 19 12:17:08 2016 -0800

i40e/i40evf: Allow up to 12K bytes of data per Tx descriptor instead
of 8K

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

Title:
  Intel i40e PF reset due to incorrect MDD detection

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  Using an Intel i40e network device, under heavy traffic load with
  TSO enabled, the device will spontaneously reset itself and issue errors
  similar to the following:

  Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:53 hostname kernel: [4253915.476283] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:54 hostname kernel: [4253917.411264] i40e :05:00.1: TX 
driver issue detected, PF reset issued

   This causes a full reset of the PF, which causes an interruption
  in traffic flow.

  This was partially fixed by Xenial commit
  12f8cc59d5886b86372f45290166deca57a60d7a, however there is one
  additional upstream commit required to fully fix the issue:

  commit 841493a3f64395b60554afbcaa17f4350f90e764
  Author: Alexander Duyck 
  Date:   Tue Sep 6 18:05:04 2016 -0700

  i40e: Limit TX descriptor count in cases where frag size is
  greater than 16K

   This fix was never backported into the Xenial 4.4 kernel series, but
  is already present in the Xenial HWE (and Zesty) 4.10 kernel.

  [Testcase]

   In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled. Under heavy load, the card will
  reset itself as described.

  [Regression Potential]

  As with any change to a network card driver, this may cause
  regressions with network I/O through i40e card(s).  However, this
  specific change only increases the likelyhood that any specific large
  TSO tx will need to be linearized, which will avoid the PF reset.
  Linearizing a TSO tx that did not need to be linearized will not cause
  any failures, it may only decrease performance slightly.  However this
  patch should only cause linearization when required to avoid the MDD
  detection and PF reset.

  [Other Info]

  The previous bug for this issue is bug 1700834.

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

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

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

[Dexuan Cui]

@fastlanejb are you on Windows Server 2012 R2 or 2016? Is your VM
running some I/O intensive workload when the live backup happens? It
looks you get the OOM issue every time you do the live backup? I'm
digging into the issue, and trying to reproduce it first.

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  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
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 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.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  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
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  

[Kernel-packages] [Bug 1713553] Re: Intel i40e PF reset due to incorrect MDD detection

[Dan Streetman]

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  Intel i40e PF reset due to incorrect MDD detection

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  Using an Intel i40e network device, under heavy traffic load with
  TSO enabled, the device will spontaneously reset itself and issue errors
  similar to the following:

  Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:53 hostname kernel: [4253915.476283] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:54 hostname kernel: [4253917.411264] i40e :05:00.1: TX 
driver issue detected, PF reset issued

   This causes a full reset of the PF, which causes an interruption
  in traffic flow.

  This was partially fixed by Xenial commit
  12f8cc59d5886b86372f45290166deca57a60d7a, however there is one
  additional upstream commit required to fully fix the issue:

  commit 841493a3f64395b60554afbcaa17f4350f90e764
  Author: Alexander Duyck 
  Date:   Tue Sep 6 18:05:04 2016 -0700

  i40e: Limit TX descriptor count in cases where frag size is
  greater than 16K

   This fix was never backported into the Xenial 4.4 kernel series, but
  is already present in the Xenial HWE (and Zesty) 4.10 kernel.

  [Testcase]

   In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled. Under heavy load, the card will
  reset itself as described.

  [Regression Potential]

  As with any change to a network card driver, this may cause
  regressions with network I/O through i40e card(s).  However, this
  specific change only increases the likelyhood that any specific large
  TSO tx will need to be linearized, which will avoid the PF reset.
  Linearizing a TSO tx that did not need to be linearized will not cause
  any failures, it may only decrease performance slightly.  However this
  patch should only cause linearization when required to avoid the MDD
  detection and PF reset.

  [Other Info]

  The previous bug for this issue is bug 1700834.

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

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

[Kernel-packages] [Bug 1700834] Re: Intel i40e PF reset under load

[Dan Streetman]

> To me it looks like this issue isn't completely solved since I'm running a 
> more
> recent kernel than the "fix" was commited to.

There is one additional upstream commit required to fully fix this,
please see bug 1713553.

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

Title:
  Intel i40e PF reset under load

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

Bug description:
  SRU Justification:

  Impact:

Using an Intel i40e network device, under heavy traffic load with
  TSO enabled, the device will spontaneously reset itself and issue errors
  similar to the following:

  Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX 
driver issue detected, PF reset issued 
  Jun 14 14:09:53 hostname kernel: [4253915.476283] i40e :05:00.1: TX 
driver issue detected, PF reset issued 
  Jun 14 14:09:54 hostname kernel: [4253917.411264] i40e :05:00.1: TX 
driver issue detected, PF reset issued 

This causes a full reset of the PF, which causes an interruption
  in traffic flow.

In this case, these errors arise from a bug in the i40e device
  driver introduced by commit:

  commit 584a837e26408c66e87df87a022faa6a54c2b020
  Author: Alexander Duyck 
  Date:   Wed Feb 17 11:02:50 2016 -0800

  i40e/i40evf: Rewrite logic for 8 descriptor per packet check

This patch was added to the Xenial kernel beginning with version
  4.4.0-8.23.  This bug does not manifest on any other Ubuntu kernel series.

  
  Fix:

  This error is resolved upstream by:

  commit 3f3f7cb875c0f621485644d4fd7453b0d37f00e4
  Author: Alexander Duyck 
  Date:   Wed Mar 30 16:15:37 2016 -0700

  i40e/i40evf: Limit TSO to 7 descriptors for payload instead of 8 per 
packet
  
This fix was never backported into the Xenial 4.4 kernel series.
  

  Testcase:

In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled.  Under heavy load, the card will
  reset itself as described.  The customer has tested the 3f3f7cb875c patch
  in their environment and confirmed that it resolves the issue.

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

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

[Kernel-packages] [Bug 1711104] Re: [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

[Manoj Iyer]

IBM, How does this bug affect package perforate ? These patches seem to
be kernel patches.

** Changed in: perforate (Ubuntu)
   Status: New => 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/1711104

Title:
  [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New
Status in perforate package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2017-08-16 
04:07:45 ==
  Please integrate the following PMU fixes for P9.

  93fc5ca9a0048c ('powerpc/perf: Cleanup of PM_BR_CMPL vs. PM_BRU_CMPL in 
Power9 event list')
  91e0bd1e62519b ('powerpc/perf: Add PM_LD_MISS_L1 and PM_BR_2PATH to power9 
event list')
  70a7e720998d5b ('powerpc/perf: Factor out PPMU_ONLY_COUNT_RUN check code from 
power8')
  7aa345d84245a7 ('powerpc/perf: Update default sdar_mode value for power9')
  101dd590a7fa37 ('powerpc/perf: Avoid spurious PMU interrupts after idle')
  bdd21ddb919d28 ('powerpc/perf: Avoid spurious PMU interrupts after idle on 
Power9')
  3f0bd8dad0db73 ('powerpc/perf: Add POWER9 alternate PM_RUN_CYC and 
PM_RUN_INST_CMPL events')
  20dd4c624d2515 ('powerpc/perf: Fix SDAR_MODE value for continous sampling on 
Power9')
  24bedcb7c81137 ('powerpc/perf: Fix branch event code for power9')
  8c218578fcbbbd ('powerpc/perf: Fix Power9 test_adder fields')

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1713553

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

Title:
  Intel i40e PF reset due to incorrect MDD detection

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  Using an Intel i40e network device, under heavy traffic load with
  TSO enabled, the device will spontaneously reset itself and issue errors
  similar to the following:

  Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:53 hostname kernel: [4253915.476283] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:54 hostname kernel: [4253917.411264] i40e :05:00.1: TX 
driver issue detected, PF reset issued

   This causes a full reset of the PF, which causes an interruption
  in traffic flow.

  This was partially fixed by Xenial commit
  12f8cc59d5886b86372f45290166deca57a60d7a, however there is one
  additional upstream commit required to fully fix the issue:

  commit 841493a3f64395b60554afbcaa17f4350f90e764
  Author: Alexander Duyck 
  Date:   Tue Sep 6 18:05:04 2016 -0700

  i40e: Limit TX descriptor count in cases where frag size is
  greater than 16K

   This fix was never backported into the Xenial 4.4 kernel series, but
  is already present in the Xenial HWE (and Zesty) 4.10 kernel.

  [Testcase]

   In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled. Under heavy load, the card will
  reset itself as described.

  [Regression Potential]

  As with any change to a network card driver, this may cause
  regressions with network I/O through i40e card(s).  However, this
  specific change only increases the likelyhood that any specific large
  TSO tx will need to be linearized, which will avoid the PF reset.
  Linearizing a TSO tx that did not need to be linearized will not cause
  any failures, it may only decrease performance slightly.  However this
  patch should only cause linearization when required to avoid the MDD
  detection and PF reset.

  [Other Info]

  The previous bug for this issue is bug 1700834.

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

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

[Kernel-packages] [Bug 1713553] [NEW] Intel i40e PF reset due to incorrect MDD detection

[Dan Streetman]

Public bug reported:

[Impact]

Using an Intel i40e network device, under heavy traffic load with
TSO enabled, the device will spontaneously reset itself and issue errors
similar to the following:

Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX driver 
issue detected, PF reset issued
Jun 14 14:09:53 hostname kernel: [4253915.476283] i40e :05:00.1: TX driver 
issue detected, PF reset issued
Jun 14 14:09:54 hostname kernel: [4253917.411264] i40e :05:00.1: TX driver 
issue detected, PF reset issued

 This causes a full reset of the PF, which causes an interruption
in traffic flow.

This was partially fixed by Xenial commit
12f8cc59d5886b86372f45290166deca57a60d7a, however there is one
additional upstream commit required to fully fix the issue:

commit 841493a3f64395b60554afbcaa17f4350f90e764
Author: Alexander Duyck 
Date:   Tue Sep 6 18:05:04 2016 -0700

i40e: Limit TX descriptor count in cases where frag size is greater
than 16K

 This fix was never backported into the Xenial 4.4 kernel series, but is
already present in the Xenial HWE (and Zesty) 4.10 kernel.

[Testcase]

 In this case, the issue occurs at a customer site using i40e based
Intel network cards with SR-IOV enabled. Under heavy load, the card will
reset itself as described.

[Regression Potential]

As with any change to a network card driver, this may cause regressions
with network I/O through i40e card(s).  However, this specific change
only increases the likelyhood that any specific large TSO tx will need
to be linearized, which will avoid the PF reset.  Linearizing a TSO tx
that did not need to be linearized will not cause any failures, it may
only decrease performance slightly.  However this patch should only
cause linearization when required to avoid the MDD detection and PF
reset.

[Other Info]

The previous bug for this issue is bug 1700834.

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

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

Title:
  Intel i40e PF reset due to incorrect MDD detection

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  Using an Intel i40e network device, under heavy traffic load with
  TSO enabled, the device will spontaneously reset itself and issue errors
  similar to the following:

  Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:53 hostname kernel: [4253915.476283] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:54 hostname kernel: [4253917.411264] i40e :05:00.1: TX 
driver issue detected, PF reset issued

   This causes a full reset of the PF, which causes an interruption
  in traffic flow.

  This was partially fixed by Xenial commit
  12f8cc59d5886b86372f45290166deca57a60d7a, however there is one
  additional upstream commit required to fully fix the issue:

  commit 841493a3f64395b60554afbcaa17f4350f90e764
  Author: Alexander Duyck 
  Date:   Tue Sep 6 18:05:04 2016 -0700

  i40e: Limit TX descriptor count in cases where frag size is
  greater than 16K

   This fix was never backported into the Xenial 4.4 kernel series, but
  is already present in the Xenial HWE (and Zesty) 4.10 kernel.

  [Testcase]

   In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled. Under heavy load, the card will
  reset itself as described.

  [Regression Potential]

  As with any change to a network card driver, this may cause
  regressions with network I/O through i40e card(s).  However, this
  specific change only increases the likelyhood that any specific large
  TSO tx will need to be linearized, which will avoid the PF reset.
  Linearizing a TSO tx that did not need to be linearized will not cause
  any failures, it may only decrease performance slightly.  However this
  patch should only cause linearization when required to avoid the MDD
  detection and PF reset.

  [Other Info]

  The previous bug for this issue is bug 1700834.

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

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

[Kernel-packages] [Bug 1712508] Re: Disappearing screen and flickering after upgrade to 16.04

[udippel]

at #4: I'd love to, but need to get rid of all kernel modules (hopefully 
without breaking the system).
The link isn't specific on how to do that. Here I have

$ sudo dkms status
acpi-call, 1.1.0, 3.13.0-128-generic, x86_64: installed
acpi-call, 1.1.0, 4.4.0-92-generic, x86_64: installed
acpi-call, 1.1.0, 4.4.0-93-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 3.13.0-128-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 4.4.0-92-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 4.4.0-93-generic, x86_64: installed
tp-smapi, 0.41, 3.13.0-128-generic, x86_64: installed
tp-smapi, 0.41, 4.4.0-92-generic, x86_64: installed
tp-smapi, 0.41, 4.4.0-93-generic, x86_64: installed
vboxhost, 4.3.40, 3.13.0-128-generic, x86_64: installed
vboxhost, 4.3.40, 4.4.0-92-generic, x86_64: installed
vboxhost, 4.3.40, 4.4.0-93-generic, x86_64: installed

Could you provide a link on the HowTo, please, as well?

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

Title:
  Disappearing screen and flickering after upgrade to 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have two Lenovo T410s that I upgraded from 14.04 to 16.04.
  Since then, one is working fine while the other shows mainly an ever 
disappearing screen and flickering.

  I have asked here: 
https://askubuntu.com/questions/947233/i-upgraded-from-kubuntu-14-04-lts-to-16-04-lts-and-now-my-screen-shows-up-and-di?noredirect=1#comment1506995_947233
  I also found I am not the only one: 
https://askubuntu.com/questions/927407/flickering-screen-with-intel-graphics-on-ubuntu-17-04?noredirect=1#comment1507937_927407
  The latter has tried pretty much that could be tried already, to no avail.

  I think that I can help with this problem, since my two T410s are
  identical in hard- and software, including BIOS, except that one is a
  type 2924 (with NVIDIA-card, though disabled in the BIOS), and the
  other one is a 2904 (without NVIDIA card).

  I have checked for differences at boot time and found DMAR as major 
difference:
  T410s, 2924: [ 0.335616] DMAR: Disabling batched IOTLB flush on Ironlake
  T410s, 2904: [ 0.355681] DMAR: BIOS has allocated no shadow GTT; disabling 
IOMMU for graphics 

  Should this be initially at the root of the problem, I'd consider the
  kernel package as responsible, therefore I marked it as above.

  The outputs of lspci -k | grep -EA3 'VGA|3D|Display' are identical to
  the point.

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

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

[Kernel-packages] [Bug 1711104] Re: [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

[Manoj Iyer]

** Also affects: linux
   Importance: Undecided
   Status: New

** Project changed: linux => linux (Ubuntu)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New
Status in perforate package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2017-08-16 
04:07:45 ==
  Please integrate the following PMU fixes for P9.

  93fc5ca9a0048c ('powerpc/perf: Cleanup of PM_BR_CMPL vs. PM_BRU_CMPL in 
Power9 event list')
  91e0bd1e62519b ('powerpc/perf: Add PM_LD_MISS_L1 and PM_BR_2PATH to power9 
event list')
  70a7e720998d5b ('powerpc/perf: Factor out PPMU_ONLY_COUNT_RUN check code from 
power8')
  7aa345d84245a7 ('powerpc/perf: Update default sdar_mode value for power9')
  101dd590a7fa37 ('powerpc/perf: Avoid spurious PMU interrupts after idle')
  bdd21ddb919d28 ('powerpc/perf: Avoid spurious PMU interrupts after idle on 
Power9')
  3f0bd8dad0db73 ('powerpc/perf: Add POWER9 alternate PM_RUN_CYC and 
PM_RUN_INST_CMPL events')
  20dd4c624d2515 ('powerpc/perf: Fix SDAR_MODE value for continous sampling on 
Power9')
  24bedcb7c81137 ('powerpc/perf: Fix branch event code for power9')
  8c218578fcbbbd ('powerpc/perf: Fix Power9 test_adder fields')

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

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

[Kernel-packages] [Bug 1709220] Re: RPT related fixes missing in Ubuntu 16.04.3

[Manoj Iyer]

** Tags added: triage-g

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

Title:
  RPT related fixes missing in Ubuntu 16.04.3

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  == SRU Justification ==
  These four commits are Radix performance patches specific to powerpc.  

  The patches are reported to help anywhere from 40% up to 3.5X on
  unixbench fork/exec testcases.

  The first patch was included in mainlne as of 4.12-rc1.  The last three 
patches are
  still in linux-next.


  ---Problem Description---

  The following patches are missing in the ubuntu 16.04.3 kernel

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/156104.html

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/156105.html

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/157130.html

  ---uname output---

  4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 UTC 2017
  ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = power9

  ---Steps to Reproduce---

  Did a fork and exec benchmark to look at the performance and they
  pointed to radix routines.

  Upstream commits mentioned:

  commit  f7327e0ba3805470cced2acfa053e795362ee41d

  powerpc/mm/radix: Remove unnecessary ptesync

  commit  f6b0df55cad252fedd60aa2ba75a0207d0006283

  powerpc/mm/radix: Don't do page walk cache flush when doing full mm
  flush

  commit  a5998fcb92552a18713b6aa5c146aa400e4d75ee

  powerpc/mm/radix: Optimise tlbiel flush all case

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

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

[Kernel-packages] [Bug 1711104] [NEW] [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Shriya R. Kulkarni  - 2017-08-16 04:07:45 
==
Please integrate the following PMU fixes for P9.

93fc5ca9a0048c ('powerpc/perf: Cleanup of PM_BR_CMPL vs. PM_BRU_CMPL in Power9 
event list')
91e0bd1e62519b ('powerpc/perf: Add PM_LD_MISS_L1 and PM_BR_2PATH to power9 
event list')
70a7e720998d5b ('powerpc/perf: Factor out PPMU_ONLY_COUNT_RUN check code from 
power8')
7aa345d84245a7 ('powerpc/perf: Update default sdar_mode value for power9')
101dd590a7fa37 ('powerpc/perf: Avoid spurious PMU interrupts after idle')
bdd21ddb919d28 ('powerpc/perf: Avoid spurious PMU interrupts after idle on 
Power9')
3f0bd8dad0db73 ('powerpc/perf: Add POWER9 alternate PM_RUN_CYC and 
PM_RUN_INST_CMPL events')
20dd4c624d2515 ('powerpc/perf: Fix SDAR_MODE value for continous sampling on 
Power9')
24bedcb7c81137 ('powerpc/perf: Fix branch event code for power9')
8c218578fcbbbd ('powerpc/perf: Fix Power9 test_adder fields')

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

** Affects: ubuntu-power-systems
 Importance: High
 Status: New

** Affects: perforate (Ubuntu)
 Importance: High
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-157728 severity-high 
targetmilestone-inin16043 triage-a
-- 
[P9][Ubuntu 16.04.03] Additional PMU fixes for P9
https://bugs.launchpad.net/bugs/1711104
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1709964] Re: Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode on POWER9 DD2.0

[Manoj Iyer]

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

** Changed in: ubuntu-power-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/1709964

Title:
  Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode
  on POWER9 DD2.0

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  == SRU Justification ==
  Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode on 
POWER9 DD2.0.

  This is a regression introduced by mainline commit 8d911904f3ce.  This 
regression
  is resolved by commit 8c218578fcbbbdb10416c8614658bf32e3bf1655.

  Commit 8c218578fc is available in mailine as of 4.12-rc5.



  ---Problem Description---
  Unable to count pm_run_inst_cmpl using perf tool on boston dd2.0

  root@isvbos3:~# perf stat -e r500fa,r600f4 -a  sleep 1

   Performance counter stats for 'system wide':

       r500fa
   8,162,912  r600f4

     1.001562716 seconds time elapsed

  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = p9 dd2.0

  ---Steps to Reproduce---
   root@isvbos3:~# perf stat -e r500fa,r600f4 -a  sleep 1

   Performance counter stats for 'system wide':

       r500fa
   8,162,912  r600f4

     1.001562716 seconds time elapsed

  > Also we need this upstream fix 8c218578fcbbbdb10416c8614658bf32e3bf1655 in
  > the distro.

  $ git log 8c218578fcbbbdb10416c8614658 -1
  commit 8c218578fcbbbdb10416c8614658bf32e3bf1655
  Author: Madhavan Srinivasan 
  Date:   Fri May 26 13:38:27 2017 +0530

  powerpc/perf: Fix Power9 test_adder fields

  Commit 8d911904f3ce4 ('powerpc/perf: Add restrictions to PMC5 in power9 
DD1')
  was added to restrict the use of PMC5 in Power9 DD1. Intention was to 
disable
  the use of PMC5 using raw event code. But instead of updating the
  power9_isa207_pmu structure (used on DD1), the commit incorrectly updated 
the
  power9_pmu structure. Fix it.

  Fixes: 8d911904f3ce ("powerpc/perf: Add restrictions to PMC5 in power9 
DD1")
  Reported-by: Shriya 
  Signed-off-by: Madhavan Srinivasan 
  Tested-by: Shriya 
  Signed-off-by: Michael Ellerman 

  $ git describe --contains 8c218578fcbbbdb
  v4.12-rc7~9^2~13
  $

  Commit 8c218578fc is available with kernel 4.12-rc7 afterwards.

  I don't see this fix in the Ubuntu 16.04.3 Zesty tree (the P9 hwe
  kernel, 4.10 based).

  Need to mirror to Canonical to request they pull in:
  8c218578fcbbbdb10416c8614658bf32e3bf1655

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1713535

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

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

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

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

** Tags added: artful

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

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```

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

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

[Kernel-packages] [Bug 1713535] [NEW] No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

[Olivier Louvignes]

Public bug reported:

It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
Intel recent Celeron NUCs (NUC6CAYS).

```
# uname -a
Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial
```

Modules are properly loaded (but looks like it is not used)

```
# lsmod | grep -e dog -e wdt
iTCO_wdt   16384  0
iTCO_vendor_support16384  1 iTCO_wdt
```

No device found in kernel.log:
```
Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO WatchDog 
Timer Driver v1.11
```

No device found by the service:

```
# service watchdog status
● watchdog.service - watchdog daemon
   Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
   Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
  Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
  Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
 Main PID: 2768 (watchdog)
Tasks: 1
   Memory: 732.0K
  CPU: 13ms
   CGroup: /system.slice/watchdog.service
   └─2768 /usr/sbin/watchdog

août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to check
août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno = 
2 = 'No such file or directory')
```

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


** Tags: artful

** Description changed:

  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).
  
  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```
  
- Modules are properly loaded
+ Modules are properly loaded (but looks like it is not used)
  
  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```
  
- No device.
+ No errors in the kern.log, sounds loaded:
+ 
+ ```
+ Aug 28 05:05:32 player-e656 kernel: [   13.179745] iTCO_vendor_support: 
vendor-support=0
+ Aug 28 05:05:32 player-e656 kernel: [   13.193303] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
+ Aug 28 05:05:32 player-e656 kernel: [   13.193463] iTCO_wdt: Found a Intel 
PCH TCO device (Version=4, TCOBASE=0x0400)
+ Aug 28 05:05:32 player-e656 kernel: [   13.193956] iTCO_wdt: initialized. 
heartbeat=30 sec (nowayout=0)
+ ```
+ 
+ No device found by the service:
  
  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
-Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
-Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
-   Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
-   Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
-  Main PID: 2768 (watchdog)
- Tasks: 1
-Memory: 732.0K
-   CPU: 13ms
-CGroup: /system.slice/watchdog.service
-└─2768 /usr/sbin/watchdog
+    Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
+    Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
+   Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
+   Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
+  Main PID: 2768 (watchdog)
+ Tasks: 1
+    Memory: 732.0K
+   CPU: 

[Kernel-packages] [Bug 1713518] Re: package linux-libc-dev 4.4.0-92.115 [modified: usr/include/x86_64-linux-gnu/asm/bootparam.h usr/include/x86_64-linux-gnu/asm/ist.h usr/include/x86_64-linux-gnu/asm/

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1713518

Title:
  package linux-libc-dev 4.4.0-92.115 [modified: usr/include/x86_64
  -linux-gnu/asm/bootparam.h usr/include/x86_64-linux-gnu/asm/ist.h
  usr/include/x86_64-linux-gnu/asm/msgbuf.h] failed to install/upgrade:
  unable to move aside './usr/include/x86_64-linux-gnu/asm/errno.h' to
  install new version: Structure needs cleaning

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After running kernel updates to 4.4.0-93.116 an error has occurred.
  Same with "sudo apt-get upgrade".

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-libc-dev 4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h]
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luc2113 F pulseaudio
   /dev/snd/controlC1:  luc2113 F pulseaudio
  Date: Mon Aug 28 16:56:20 2017
  Dependencies:
   
  DuplicateSignature:
   package:linux-libc-dev:4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h]
   Unpacking linux-libc-dev:amd64 (4.4.0-93.116) over (4.4.0-92.115) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_4.4.0-93.116_amd64.deb (--unpack):
unable to move aside './usr/include/x86_64-linux-gnu/asm/errno.h' to 
install new version: Structure needs cleaning
  ErrorMessage: unable to move aside 
'./usr/include/x86_64-linux-gnu/asm/errno.h' to install new version: Structure 
needs cleaning
  HibernationDevice: RESUME=UUID=727192a5-d347-4c41-bce6-bf45d67f3941
  MachineType: Sony Corporation VPCEB4M1E
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=670bb4d5-cff7-47ad-8196-362e14bd1457 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.12
  SourcePackage: linux
  Title: package linux-libc-dev 4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h] failed to install/upgrade: unable to 
move aside './usr/include/x86_64-linux-gnu/asm/errno.h' to install new version: 
Structure needs cleaning
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1170Y8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1170Y8:bd01/28/2011:svnSonyCorporation:pnVPCEB4M1E:pvrC6087YJR:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEB4M1E
  dmi.product.version: C6087YJR
  dmi.sys.vendor: Sony Corporation

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

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

[Kernel-packages] [Bug 1610715] Re: Repeated (spurious?) pcieport errors in logs (PCIe Bus Error)

[Julian Alarcon]

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

** This bug has been marked a duplicate of bug 1521173
   AER: Corrected error received: id=00e0

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

Title:
  Repeated (spurious?) pcieport errors in logs (PCIe Bus Error)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 16.04 LTS ASUS R558U.

  Similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/671979

  I find repeated error/Logs in all virtual consoles, because of which I
  can't work in the virtual consoles. I am not using nvidia proprietary
  drivers.

  Below is the error/log printed (Pasted from dmesg)

  [ 1431.552877] pcieport :00:1c.5: AER: Multiple Corrected error received: 
id=00e5
  [ 1431.553286] pcieport :00:1c.5: can't find device of ID00e5
  [ 1431.553304] pcieport :00:1c.5: AER: Corrected error received: id=00e5
  [ 1431.553321] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  [ 1431.553330] pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
  [ 1431.553339] pcieport :00:1c.5:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nova   3697 F pulseaudio
  CRDA:
   country IN: DFS-JP
    (2402 - 2482 @ 40), (N/A, 20), (N/A)
    (5170 - 5250 @ 80), (N/A, 20), (N/A)
    (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
    (5735 - 5835 @ 80), (N/A, 20), (N/A)
  CurrentDesktop: Unity
  Date: Sun Aug  7 22:31:46 2016
  HibernationDevice: RESUME=UUID=1e323818-6a1a-4387-9d9e-309fbfd07949
  InstallationDate: Installed on 2016-07-16 (22 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X556UF
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=169951e0-8588-4ed4-8b79-8c247c4aee05 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UF.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UF
  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.:bvrX556UF.206:bd09/10/2015:svnASUSTeKCOMPUTERINC.:pnX556UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X556UF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-07-16 (25 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.14-040414-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1702221] Re: Get spammed by PCIe Bus Error

[Julian Alarcon]

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

** This bug has been marked a duplicate of bug 1521173
   AER: Corrected error received: id=00e0

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

Title:
  Get spammed by PCIe Bus Error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm spammed by PCIe Bus Error. I get this error 10 times per second in 
console. Error is:
  pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical 
Layer, id=00e0(Receiver ID) device [8086:a112] error 
status/mask=0001/
  pcieport :00:1c.0: [ 0] Receiver Error (First)

  I collected some sys info:
  lspci -vt>lspci_vt.log
  lspci -nnv>lspci_nnv.log
  lscpu>lscpu.log
  cat /proc/cpuinfo >proc_cpuinfo.log
  uname -a>uname_a.log
  lshw>lshw.log
  lsusb -v>lsusb_v.log
  dmidecode>dmidecode.log
  lsb_release -a>lsb_release.log
  iwconfig >iwconfig.log

  I run latest Ubuntu 17.04 on VivoBook Pro N752VX notebook
  (https://www.asus.com/Laptops/VivoBook-Pro-N752VX/specifications/).

  This pcieport 1c.0 is connected to RTL8192EE PCIe Wireless Network
  Adapter (see lspci_vt.log).

  I can disable this message by adding pci=nomsi kernel parameter, but
  this is not a bug fix, only a workaround. Also after appling this
  parameter wifi connection is quite slow and unstable. On windows 10 I
  get approx ping time 3ms to my wifi router. On Linux ping time is
  min/avg/max 5.548/60.137/261.145 with very good signal strength (see
  iwconfig.log).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-26-generic 4.10.0-26.30
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmoukhataev   1907 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jul  4 08:33:04 2017
  InstallationDate: Installed on 2017-05-18 (46 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. N752VX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed 
root=UUID=1365c792-1a17-47ad-8c37-f738d0645d3d ro nosplash pci=nomsi
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N752VX.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N752VX
  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.:bvrN752VX.301:bd08/18/2016:svnASUSTeKCOMPUTERINC.:pnN752VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN752VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N752VX
  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/1702221/+subscriptions

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

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[Julian Alarcon]

Still happening with Ubuntu 17.10 kernel Linux P01A30136
4.12.0-12-generic #13-Ubuntu SMP Thu Aug 17 16:13:25 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux and updated BIOS.


Aug 28 10:55:08 LAPTOPNAME kernel: [ 5632.967441] pcieport :00:1c.5: AER: 
Corrected error received: id=00e5
Aug 28 10:55:08 LAPTOPNAME kernel: [ 5632.967445] pcieport :00:1c.5: PCIe 
Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 28 10:55:08 LAPTOPNAME kernel: [ 5632.967447] pcieport :00:1c.5:   
device [8086:9d15] error status/mask=0001/2000
Aug 28 10:55:08 LAPTOPNAME kernel: [ 5632.967449] pcieport :00:1c.5:[ 
0] Receiver Error (First)

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

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1588428] Re: PCI bus error on startup while booting into login screen (Kubuntu 16.04)

[Julian Alarcon]

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

** This bug has been marked a duplicate of bug 1521173
   AER: Corrected error received: id=00e0

-- 
You 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 1713476] Re: Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

[Mohamed Zouaghi]

I'm not sure what should be the status plz feel free to change it

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

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1713476] Re: Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

[Mohamed Zouaghi]

Probel has been fixed (by itself?), I've restarted system and started
with kernel  4.10.0-19-generic and touchpad was back alive again. It
worked perfectly. I've then restarted again with kernel
4.10.0-32-generic and this time touchpad *worked*. I'm not sure what was
the issue because I've already tried to restart a couple of times
earlier and this didn't do anything...

In all cases I'm going to  close this (until it happens again)

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

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

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 

[Kernel-packages] [Bug 1696375] Re: cpupower suggests installation of non-existent linux-cloud-tools-generic package

[Joseph Salisbury]

** Tags removed: kernel-key
** Tags added: kernel-da-key

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

Title:
  cpupower suggests installation of non-existent linux-cloud-tools-
  generic package

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem Description
  ===
  cpupower suggests installation of non-existent linux-cloud-tools-generic 
package

  Problem occurs on an IBM POWER 16.04 LTS system. Unknown whether it
  occurs on other architectures or later releases.

  When run _without package "linux-tools-$(uname -r)" installed_,
  cpupower will issue a complaint, suggesting to install (among others),
  some linux-cloud-tools-*-generic packages:

  $ cpupower
  WARNING: cpupower not found for kernel 4.4.0-75

You may need to install the following packages for this specific kernel:
  linux-tools-4.4.0-75-generic
  linux-cloud-tools-4.4.0-75-generic

You may also want to install one of the following packages to keep up to 
date:
  linux-tools-generic
  linux-cloud-tools-generic

  However, those linux-cloud-tools-*-generic package appear not to exist
  --at least not in the default repos.

  Package linux-cloud-tools-common exists, but none of the *-generic
  packages are available:

  $ apt-cache policy "linux-cloud-*"
  $ cat xxx
  linux-cloud-tools-common:
Installed: (none)
Candidate: 4.4.0-78.99
Version table:
   4.4.0-78.99 500
  500 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el 
Packages
   4.4.0-77.98 500
  500 http://us.ports.ubuntu.com/ubuntu-ports xenial-updates/main 
ppc64el Packages
   4.4.0-75.96 500
  500 http://us.ports.ubuntu.com/ubuntu-ports xenial-updates/main 
ppc64el Packages
  500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main ppc64el 
Packages
  [...]
   4.4.0-21.37 500
  500 http://us.ports.ubuntu.com/ubuntu-ports xenial/main ppc64el 
Packages

  
  The cpupower command works (at least doesn't give this complaint) if the 
appropriate linux-tools-$(uname -r) (perhaps via linux-tools-generic) is 
installed, so the cloud package is maybe not needed (as least for some 
functionality).

  I think the fix is to either: 
  a) supply the cloud packages for POWER, or 
  b) remove the non-existent packages from cpupower's complaint message.
   
  ---uname output---
  Linux fs3 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:55:30 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Firestone 
   
  ---Steps to Reproduce---
   Install linux-tools-common but NOT linux-tools-*-generic on a POWER 16.04 
LTS system, then run cpupower.

  Userspace rpm: linux-tools-common

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

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

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

[Joseph Salisbury]

** Tags removed: kernel-key

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1712831] Re: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests

[Joseph Salisbury]

** Tags removed: kernel-key
** Tags added: kernel-da-key

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

Title:
  4.12.0-11-generic - crashing in infrastructure on i386 openvswitch
  tests

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  this seems to me to be a kernel crash of some sorts.
  Somewhat in the spirit of older bugs:
  - bug 1630940
  - bug 1630578

  Xnox asked me to look into a hang on openvswitch dep8 tests.
  What I found initially was in the log just
"ERROR: Removing temporary files on testbed timed out"
  That message brought me to the two bugs above.

  But in there I read that this was the infra running dep8 crashing.
  So for a better bug report I tried to reproduce locally and that actually 
seems to work very reliable.

  To reproduce do:
  $ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G
  $ pull-lp-source openvswitch
  $ autopkgtest --apt-upgrade --shell --no-built-binaries 
openvswitch_2.8.0~git20170809.7aa47a19d-0ubuntu1.dsc -- qemu 
~/work/autopkgtest-artful-i386.img
  # This guest currently will crash after a while of testing

  
  But with that running you can attach to the console and monitor of that guest.
  For example:
  $ sudo nc -U /tmp/autopkgtest-virt-qemu.*/ttyS0

  That gave me a crash on the hang which kind of matches the older bugs, here 
the console:
  [   54.256253] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   54.257156] IP: add_grec+0x28/0x440
  [   54.257553] *pdpt = 1a869001 *pde =  
  [   54.257555] 
  [   54.258338] Oops:  [#1] SMP
  [   54.258638] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm irqbypass joydev 
input_leds serio_raw 9pnet_virtio parport_pc 9pnet parport qemu_fw_cfg 
i2c_piix4 mac_hid ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net floppy pata_acpi
  [   54.261891] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW   
4.12.0-11-generic #12-Ubuntu
  [   54.262715] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.1-1ubuntu1~cloud0 04/01/2014
  [   54.263610] task: c7b622c0 task.stack: c7b5a000
  [   54.264039] EIP: add_grec+0x28/0x440
  [   54.264378] EFLAGS: 00010202 CPU: 0
  [   54.264711] EAX:  EBX: dd062540 ECX: 0006 EDX: dd062540
  [   54.265308] ESI: dd1e6e00 EDI: dd1e6e00 EBP: dbcc5f30 ESP: dbcc5ef0
  [   54.265793]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   54.266297] CR0: 80050033 CR2:  CR3: 1e930d80 CR4: 06f0
  [   54.266885] Call Trace:
  [   54.267120]  
  [   54.267349]  mld_ifc_timer_expire+0xfe/0x250
  [   54.267754]  ? mld_dad_timer_expire+0x50/0x50
  [   54.268173]  call_timer_fn+0x30/0x120
  [   54.268524]  ? mld_dad_timer_expire+0x50/0x50
  [   54.268942]  ? mld_dad_timer_expire+0x50/0x50
  [   54.269364]  run_timer_softirq+0x3c5/0x420
  [   54.269760]  ? __softirqentry_text_start+0x8/0x8
  [   54.270198]  __do_softirq+0xa9/0x245
  [   54.270539]  ? __softirqentry_text_start+0x8/0x8
  [   54.270976]  do_softirq_own_stack+0x24/0x30
  [   54.271373]  
  [   54.271611]  irq_exit+0xad/0xb0
  [   54.271913]  smp_apic_timer_interrupt+0x38/0x50
  [   54.272344]  apic_timer_interrupt+0x39/0x40
  [   54.272745] EIP: native_safe_halt+0x5/0x10
  [   54.273139] EFLAGS: 0246 CPU: 0
  [   54.273624] EAX:  EBX:  ECX: 0001 EDX: 
  [   54.274000] ESI:  EDI: c7b622c0 EBP: c7b5bf10 ESP: c7b5bf10
  [   54.274361]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   54.274687]  default_idle+0x1c/0xf0
  [   54.274896]  arch_cpu_idle+0xe/0x10
  [   54.275286]  default_idle_call+0x1e/0x30
  [   54.275787]  do_idle+0x145/0x1c0
  [   54.276092]  cpu_startup_entry+0x65/0x70
  [   54.276441]  rest_init+0x62/0x70
  [   54.276718]  start_kernel+0x3be/0x3d7
  [   54.276974]  i386_start_kernel+0x9d/0xa1
  [   54.277260]  startup_32_smp+0x16b/0x16d
  [   54.277509] Code: 00 00 00 3e 8d 74 26 00 55 89 e5 57 56 53 89 c6 83 ec 34 
89 4d e8 65 a1 14 00 00 00 89 45 f0 31 c0 8b 42 10 f6 42 48 08 89 45 cc <8b> 00 
c7 45 ec 00 00 00 00 89 45 c8 89 f0 0f 85 b4 02 00 00 8b
  [   54.279314] EIP: add_grec+0x28/0x440 SS:ESP: 0068:dbcc5ef0
  [   54.279829] CR2: 
  [   54.280143] ---[ end trace 3164b1c0dd7745bc ]---
  [   54.280550] Kernel panic - not syncing: Fatal exception in interrupt
  [   54.281078] Kernel Offset: 0x600 from 0xc100 (relocation range: 
0xc000-0xdfbfdfff)
  [   54.281797] ---[ end Kernel panic - not syncing: Fatal exception in 
interrupt

  But since this is lovely qemu the machine isn't as dead as real HW now, so 
via the monitor
  $ sudo nc -U /tmp/autopkgtest-virt-qemu.*/monitor
  I took a dump.

  Fetching the i386 debug kernel shows me I can load that 

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

[bugproxy]

--- Comment From ar...@us.ibm.com 2017-08-28 11:27 EDT---
> I built a Zesty test kernel with a pick of commit be9ba9ff93cc.  The test
> kernel can be downloaded from:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1709179
>
> Can you test this kernel and see if it resolves this bug?

Seems to work! Thank you.

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

Title:
  Drop GPL from of_node_to_nid() export to match other arches

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  == Comment: #0 - Reza A. Arbab  - 2017-08-07 15:34:04 ==
  We need to backport mainline commit be9ba9ff93cc ("Drop GPL from 
of_node_to_nid() export to match other arches") to the Ubuntu 4.10 kernel.

  This exposes functionality needed by the Nvidia device driver on
  POWER9.

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

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

[Kernel-packages] [Bug 1712345] Re: sort ABI files with C.UTF-8 locale

[Thadeu Lima de Souza Cascardo]

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

Title:
  sort ABI files with C.UTF-8 locale

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux source package in Vivid:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Incomplete

Bug description:
  Whenever we update the ABI files, the files may be sorted in a
  different order, even though their contents are the same. That happens
  because the system updating the ABI files may use a different locale
  than the one that was used previously.

  Always using the C.UTF-8 locale should fix that.

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

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

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

[Ubuntu Kernel Bot]

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

Title:
  package linux-libc-dev 4.4.0-92.115 [modified: usr/include/x86_64
  -linux-gnu/asm/bootparam.h usr/include/x86_64-linux-gnu/asm/ist.h
  usr/include/x86_64-linux-gnu/asm/msgbuf.h] failed to install/upgrade:
  unable to move aside './usr/include/x86_64-linux-gnu/asm/errno.h' to
  install new version: Structure needs cleaning

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After running kernel updates to 4.4.0-93.116 an error has occurred.
  Same with "sudo apt-get upgrade".

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-libc-dev 4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h]
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luc2113 F pulseaudio
   /dev/snd/controlC1:  luc2113 F pulseaudio
  Date: Mon Aug 28 16:56:20 2017
  Dependencies:
   
  DuplicateSignature:
   package:linux-libc-dev:4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h]
   Unpacking linux-libc-dev:amd64 (4.4.0-93.116) over (4.4.0-92.115) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_4.4.0-93.116_amd64.deb (--unpack):
unable to move aside './usr/include/x86_64-linux-gnu/asm/errno.h' to 
install new version: Structure needs cleaning
  ErrorMessage: unable to move aside 
'./usr/include/x86_64-linux-gnu/asm/errno.h' to install new version: Structure 
needs cleaning
  HibernationDevice: RESUME=UUID=727192a5-d347-4c41-bce6-bf45d67f3941
  MachineType: Sony Corporation VPCEB4M1E
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=670bb4d5-cff7-47ad-8196-362e14bd1457 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.12
  SourcePackage: linux
  Title: package linux-libc-dev 4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h] failed to install/upgrade: unable to 
move aside './usr/include/x86_64-linux-gnu/asm/errno.h' to install new version: 
Structure needs cleaning
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1170Y8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1170Y8:bd01/28/2011:svnSonyCorporation:pnVPCEB4M1E:pvrC6087YJR:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEB4M1E
  dmi.product.version: C6087YJR
  dmi.sys.vendor: Sony Corporation

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

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

[Kernel-packages] [Bug 1713243] Re: package kerneloops-daemon 0.12+git20140509-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package kerneloops-daemon 0.12+git20140509-2ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in kerneloops package in Ubuntu:
  New

Bug description:
  mohammed@Moha:~$ sudo apt-get upgrade
  [sudo] password for mohammed: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 0 B/18.5 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  dpkg: error processing package kerneloops-daemon (--configure):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting configuration
  Errors were encountered while processing:
   kerneloops-daemon
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  mohammed@Moha:~$

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kerneloops-daemon 0.12+git20140509-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Aug 26 19:34:13 2017
  DuplicateSignature:
   package:kerneloops-daemon:0.12+git20140509-2ubuntu1
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package kerneloops-daemon (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-07-24 (32 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: kerneloops
  Title: package kerneloops-daemon 0.12+git20140509-2ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2017-08-06 (19 days ago)

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

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

[Kernel-packages] [Bug 1705169] Re: Hotkeys on new Thinkpad systems aren't working

[Alex Hung]

** Changed in: hwe-next
   Status: Fix Committed => 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/1705169

Title:
  Hotkeys on new Thinkpad systems aren't working

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This includes mic-mute, bluetooth, video switch and wireless on/off

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

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

[Kernel-packages] [Bug 1682644] Re: IPR driver causes multipath to fail paths/stuck IO on Medium Errors

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => 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/1682644

Title:
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: stuck I/O to multipath disks with medium errors (on IPR controllers)
  Fix: upstream commit for IPR driver to allow SCSI layer to handle the error
  Testcase: perform I/O to a failing disk which is multipathed (on IPR
controller), which returns SCSI Medium Errors (without the fix,
the I/O gets stuck). 
the commit message describes a test-case w/ sg_dd.

  
  ---Problem Description---
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

  This problem is resolved with this upstream accepted patch, scheduled for 
4.11.
  The detailed problem description and resolution are described in the commit 
message.

  > scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION
  > 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=785a470496d8e0a32e3d39f376984eb2c98ca5b3

  Please apply to 17.04 (target 16.04.3 HWE kernel) and 16.04 (GA kernel).
  Patch already applied to 17.10.

  The business justification for the SRU is:

  Clients with a dual-controller multipathed IPR configuration that
  eventually runs into failing disk/sectors, will experience an I/O hang
  once the drive reports a Medium Error, which can hang an application
  or even the root filesystem (whatever is doing I/O to the failing
  drive), potentially hanging the system.

  Thanks.

  ---Additional Hardware Info---
  Dual (IPR) controller setup, multipath enabled

  ---Steps to Reproduce---
  1) Use a disk with bad sectors (or force such condition, via internal/special 
tools)
  2) Multipath that disk
  3) Run IO to the multipath device on the bad sectors
  4) Both paths will be failed, and IO is stuck due to queue_if_no_path 
(enabled by default for IPR)

  The detailed problem description and resolution are described in the
  commit message.

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

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

[Kernel-packages] [Bug 1707643] Re: HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) does not work

[Kleber Sacilotto de Souza]

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

Title:
  HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) does not work

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

Bug description:
  HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) modem does not work without this 
patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.13-rc3=a68491f895a937778bb25b0795830797239de31f

  Modem connects, but does not receive any packets.
  ifconfig shows;
  wwp0s20f0u10c3 Link encap:Ethernet  HWaddr 9e:63:76:8e:c0:91  
inet addr:10.137.74.102  Bcast:10.137.74.103  Mask:255.255.255.252
UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:3465 (3.4 KB)

  Booting to http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc3/
  fixes the problem. Modem works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.83.89
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  it 1334 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Jul 31 15:40:55 2017
  HibernationDevice: RESUME=UUID=9e656f3b-ee00-4e30-83e9-43a15bd0a6d1
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b595 Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 03f0:a31d Hewlett-Packard 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 430 G4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=b7cbc0e4-b6dd-4df5-ac7a-7a3b513743d9 ro splash quiet vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-83-generic N/A
   linux-backports-modules-4.4.0-83-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P85 Ver. 01.04
  dmi.board.name: 822C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 42.65
  dmi.chassis.asset.tag: 5CD7274GN2
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP85Ver.01.04:bd04/12/2017:svnHP:pnHPProBook430G4:pvr:rvnHP:rn822C:rvrKBCVersion42.65:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 430 G4
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1707643] Re: HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) does not work

[Stefan Bader]

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

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

Title:
  HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) does not work

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

Bug description:
  HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) modem does not work without this 
patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.13-rc3=a68491f895a937778bb25b0795830797239de31f

  Modem connects, but does not receive any packets.
  ifconfig shows;
  wwp0s20f0u10c3 Link encap:Ethernet  HWaddr 9e:63:76:8e:c0:91  
inet addr:10.137.74.102  Bcast:10.137.74.103  Mask:255.255.255.252
UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:3465 (3.4 KB)

  Booting to http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc3/
  fixes the problem. Modem works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.83.89
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  it 1334 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Jul 31 15:40:55 2017
  HibernationDevice: RESUME=UUID=9e656f3b-ee00-4e30-83e9-43a15bd0a6d1
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b595 Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 03f0:a31d Hewlett-Packard 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 430 G4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=b7cbc0e4-b6dd-4df5-ac7a-7a3b513743d9 ro splash quiet vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-83-generic N/A
   linux-backports-modules-4.4.0-83-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P85 Ver. 01.04
  dmi.board.name: 822C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 42.65
  dmi.chassis.asset.tag: 5CD7274GN2
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP85Ver.01.04:bd04/12/2017:svnHP:pnHPProBook430G4:pvr:rvnHP:rn822C:rvrKBCVersion42.65:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 430 G4
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1712345] Re: sort ABI files with C.UTF-8 locale

[Kleber Sacilotto de Souza]

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

Title:
  sort ABI files with C.UTF-8 locale

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux source package in Vivid:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  Incomplete

Bug description:
  Whenever we update the ABI files, the files may be sorted in a
  different order, even though their contents are the same. That happens
  because the system updating the ABI files may use a different locale
  than the one that was used previously.

  Always using the C.UTF-8 locale should fix that.

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

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

[Kernel-packages] [Bug 1712345] Re: sort ABI files with C.UTF-8 locale

[Stefan Bader]

** Also affects: linux (Ubuntu Artful)
   Importance: Undecided
   Status: Incomplete

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

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

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

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

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

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

Title:
  sort ABI files with C.UTF-8 locale

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux source package in Vivid:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  Incomplete

Bug description:
  Whenever we update the ABI files, the files may be sorted in a
  different order, even though their contents are the same. That happens
  because the system updating the ABI files may use a different locale
  than the one that was used previously.

  Always using the C.UTF-8 locale should fix that.

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

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

[Kernel-packages] [Bug 1713462] Re: linux: 4.4.0-94.117 -proposed tracker

[Kleber Sacilotto de Souza]

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.4.0-94.117 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

Title:
  linux: 4.4.0-94.117 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the  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

  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469

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

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

[Kernel-packages] [Bug 1712746] Re: mwifiex causes kernel oops when AP mode is enabled

[Kleber Sacilotto de Souza]

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

Title:
  mwifiex causes kernel oops when AP mode is enabled

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

Bug description:
  When it's in AP mode, there's quite a chance to find kernel oops
  during reboot.

  This is caused by the wiphy may be NULL for some reason. It's likely a
  bug in mwifiex. We've already pinged Marvell and Murata. Before
  there's a real fix available, we should check wiphy before accessing
  it.

  I've tried a 4.13-rc6 kernel. Though it has oops for NULL pointer
  deference too, it happens in a different function in mwifiex. Thus the
  workaround for Xenial may or may not help for other series. Will need
  to reproduce this issue with Zesty and then we can decide whether this
  workaround should be applied to Zesty.

  [   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
  [   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.716494] PGD 0
  [   30.718575] Oops:  [#1] SMP
  [   30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni
  [   30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [   30.845018] Hardware name: Dell Inc. Edge Gateway 5000/  , BIOS 
01.05.00 10/18/2016
  [   30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex]
  [   30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 
880075e48000
  [   30.868018] RIP: 0010:[]  [] 
mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.877484] RSP: 0018:880075e4bbf8  EFLAGS: 00010202
  [   30.882920] RAX:  RBX: 0004 RCX: 
0004
  [   30.890221] RDX: 001000110010 RSI: 0004 RDI: 
0004
  [   30.897520] RBP: 880075e4bc28 R08: 0003 R09: 
0001
  [   30.904821] R10: 0001 R11: 02ff R12: 
0095
  [   30.912123] R13:  R14: 880075e4 R15: 
0095
  [   30.919425] FS:  () GS:88007130() 
knlGS:
  [   30.927701] CS:  0010 DS:  ES:  CR0: 8005003b
  [   30.933581] CR2: 00f0 CR3: 01e0a000 CR4: 
001006e0
  [   30.940882] Stack:
  [   30.942944]  0118 880075e4 8800750c4000 
880075e3ed59
  [   30.950592]  0095 880075e3ee01 880075e4bcd0 
c05846fc
  [   30.958232]   880075e4bc50 8140bcb5 
880075e4bc70
  [   30.965873] Call Trace:
  [   30.968397]  [] 
mwifiex_parse_single_response_buf+0x1fc/0x560 [mwifiex]
  [   30.976772]  [] ? find_next_bit+0x15/0x20
  [   30.982490]  [] 
mwifiex_handle_event_ext_scan_report+0x15c/0x340 [mwifiex]
  [   30.991139]  [] mwifiex_process_sta_event+0x276/0xb40 
[mwifiex]
  [   30.998806]  [] mwifiex_process_event+0x102/0x1c0 
[mwifiex]
  [   31.006120]  [] mwifiex_main_process+0x5de/0x8d0 
[mwifiex]
  [   31.013346]  [] mwifiex_main_work_queue+0x1f/0x30 
[mwifiex]
  [   31.020650]  [] process_one_work+0x165/0x480
  [   31.026624]  [] worker_thread+0x4b/0x4c0
  [   31.032240]  [] ? process_one_work+0x480/0x480
  [   31.038387]  [] kthread+0xd8/0xf0
  [   31.043384]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.050071]  [] ret_from_fork+0x3f/0x70
  [   31.055596]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 
df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00
  [   31.082756] RIP  [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   31.089820]  RSP 
  [   31.093392] CR2: 00f0
  [   31.096787] ---[ end trace f3a762be5787f138 ]---

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

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

[Kernel-packages] [Bug 1713243] Re: package kerneloops-daemon 0.12+git20140509-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti

[Tyler Hicks]

** Information type changed from Private Security to Public

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

Title:
  package kerneloops-daemon 0.12+git20140509-2ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in kerneloops package in Ubuntu:
  New

Bug description:
  mohammed@Moha:~$ sudo apt-get upgrade
  [sudo] password for mohammed: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 0 B/18.5 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  dpkg: error processing package kerneloops-daemon (--configure):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting configuration
  Errors were encountered while processing:
   kerneloops-daemon
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  mohammed@Moha:~$

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kerneloops-daemon 0.12+git20140509-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Aug 26 19:34:13 2017
  DuplicateSignature:
   package:kerneloops-daemon:0.12+git20140509-2ubuntu1
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package kerneloops-daemon (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-07-24 (32 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: kerneloops
  Title: package kerneloops-daemon 0.12+git20140509-2ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2017-08-06 (19 days ago)

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

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

[Kernel-packages] [Bug 1713518] Re: package linux-libc-dev 4.4.0-92.115 [modified: usr/include/x86_64-linux-gnu/asm/bootparam.h usr/include/x86_64-linux-gnu/asm/ist.h usr/include/x86_64-linux-gnu/asm/

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-libc-dev 4.4.0-92.115 [modified: usr/include/x86_64
  -linux-gnu/asm/bootparam.h usr/include/x86_64-linux-gnu/asm/ist.h
  usr/include/x86_64-linux-gnu/asm/msgbuf.h] failed to install/upgrade:
  unable to move aside './usr/include/x86_64-linux-gnu/asm/errno.h' to
  install new version: Structure needs cleaning

Status in linux package in Ubuntu:
  New

Bug description:
  After running kernel updates to 4.4.0-93.116 an error has occurred.
  Same with "sudo apt-get upgrade".

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-libc-dev 4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h]
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luc2113 F pulseaudio
   /dev/snd/controlC1:  luc2113 F pulseaudio
  Date: Mon Aug 28 16:56:20 2017
  Dependencies:
   
  DuplicateSignature:
   package:linux-libc-dev:4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h]
   Unpacking linux-libc-dev:amd64 (4.4.0-93.116) over (4.4.0-92.115) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_4.4.0-93.116_amd64.deb (--unpack):
unable to move aside './usr/include/x86_64-linux-gnu/asm/errno.h' to 
install new version: Structure needs cleaning
  ErrorMessage: unable to move aside 
'./usr/include/x86_64-linux-gnu/asm/errno.h' to install new version: Structure 
needs cleaning
  HibernationDevice: RESUME=UUID=727192a5-d347-4c41-bce6-bf45d67f3941
  MachineType: Sony Corporation VPCEB4M1E
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=670bb4d5-cff7-47ad-8196-362e14bd1457 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.12
  SourcePackage: linux
  Title: package linux-libc-dev 4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h] failed to install/upgrade: unable to 
move aside './usr/include/x86_64-linux-gnu/asm/errno.h' to install new version: 
Structure needs cleaning
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1170Y8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1170Y8:bd01/28/2011:svnSonyCorporation:pnVPCEB4M1E:pvrC6087YJR:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEB4M1E
  dmi.product.version: C6087YJR
  dmi.sys.vendor: Sony Corporation

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

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

[Kernel-packages] [Bug 1713518] [NEW] package linux-libc-dev 4.4.0-92.115 [modified: usr/include/x86_64-linux-gnu/asm/bootparam.h usr/include/x86_64-linux-gnu/asm/ist.h usr/include/x86_64-linux-gnu/as

[Ubucolors]

Public bug reported:

After running kernel updates to 4.4.0-93.116 an error has occurred.
Same with "sudo apt-get upgrade".

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-libc-dev 4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h]
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  luc2113 F pulseaudio
 /dev/snd/controlC1:  luc2113 F pulseaudio
Date: Mon Aug 28 16:56:20 2017
Dependencies:
 
DuplicateSignature:
 package:linux-libc-dev:4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h]
 Unpacking linux-libc-dev:amd64 (4.4.0-93.116) over (4.4.0-92.115) ...
 dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_4.4.0-93.116_amd64.deb (--unpack):
  unable to move aside './usr/include/x86_64-linux-gnu/asm/errno.h' to install 
new version: Structure needs cleaning
ErrorMessage: unable to move aside './usr/include/x86_64-linux-gnu/asm/errno.h' 
to install new version: Structure needs cleaning
HibernationDevice: RESUME=UUID=727192a5-d347-4c41-bce6-bf45d67f3941
MachineType: Sony Corporation VPCEB4M1E
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=670bb4d5-cff7-47ad-8196-362e14bd1457 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.12
SourcePackage: linux
Title: package linux-libc-dev 4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h] failed to install/upgrade: unable to 
move aside './usr/include/x86_64-linux-gnu/asm/errno.h' to install new version: 
Structure needs cleaning
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/28/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1170Y8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1170Y8:bd01/28/2011:svnSonyCorporation:pnVPCEB4M1E:pvrC6087YJR:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCEB4M1E
dmi.product.version: C6087YJR
dmi.sys.vendor: Sony Corporation

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-libc-dev 4.4.0-92.115 [modified: usr/include/x86_64
  -linux-gnu/asm/bootparam.h usr/include/x86_64-linux-gnu/asm/ist.h
  usr/include/x86_64-linux-gnu/asm/msgbuf.h] failed to install/upgrade:
  unable to move aside './usr/include/x86_64-linux-gnu/asm/errno.h' to
  install new version: Structure needs cleaning

Status in linux package in Ubuntu:
  New

Bug description:
  After running kernel updates to 4.4.0-93.116 an error has occurred.
  Same with "sudo apt-get upgrade".

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-libc-dev 4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h]
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luc2113 F pulseaudio
   /dev/snd/controlC1:  luc2113 F pulseaudio
  Date: Mon Aug 28 16:56:20 2017
  Dependencies:
   
  DuplicateSignature:
   package:linux-libc-dev:4.4.0-92.115 [modified: 
usr/include/x86_64-linux-gnu/asm/bootparam.h 
usr/include/x86_64-linux-gnu/asm/ist.h 
usr/include/x86_64-linux-gnu/asm/msgbuf.h]
   Unpacking linux-libc-dev:amd64 (4.4.0-93.116) over (4.4.0-92.115) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_4.4.0-93.116_amd64.deb (--unpack):
unable to move aside './usr/include/x86_64-linux-gnu/asm/errno.h' to 
install new version: Structure needs cleaning
  ErrorMessage: unable to move aside 
'./usr/include/x86_64-linux-gnu/asm/errno.h' to install new version: Structure 
needs cleaning
  HibernationDevice: RESUME=UUID=727192a5-d347-4c41-bce6-bf45d67f3941
  MachineType: Sony Corporation VPCEB4M1E
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1713470] Re: linux: 4.10.0-34.38 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.10.0-34.38 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

Title:
  linux: 4.10.0-34.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  New

Bug description:
  This bug is for tracking the  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

  backports: 1713471,1713472
  derivatives: 1713473

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

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

[Kernel-packages] [Bug 1682644] Re: IPR driver causes multipath to fail paths/stuck IO on Medium Errors

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Zesty)
   Status: Triaged => 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/1682644

Title:
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: stuck I/O to multipath disks with medium errors (on IPR controllers)
  Fix: upstream commit for IPR driver to allow SCSI layer to handle the error
  Testcase: perform I/O to a failing disk which is multipathed (on IPR
controller), which returns SCSI Medium Errors (without the fix,
the I/O gets stuck). 
the commit message describes a test-case w/ sg_dd.

  
  ---Problem Description---
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

  This problem is resolved with this upstream accepted patch, scheduled for 
4.11.
  The detailed problem description and resolution are described in the commit 
message.

  > scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION
  > 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=785a470496d8e0a32e3d39f376984eb2c98ca5b3

  Please apply to 17.04 (target 16.04.3 HWE kernel) and 16.04 (GA kernel).
  Patch already applied to 17.10.

  The business justification for the SRU is:

  Clients with a dual-controller multipathed IPR configuration that
  eventually runs into failing disk/sectors, will experience an I/O hang
  once the drive reports a Medium Error, which can hang an application
  or even the root filesystem (whatever is doing I/O to the failing
  drive), potentially hanging the system.

  Thanks.

  ---Additional Hardware Info---
  Dual (IPR) controller setup, multipath enabled

  ---Steps to Reproduce---
  1) Use a disk with bad sectors (or force such condition, via internal/special 
tools)
  2) Multipath that disk
  3) Run IO to the multipath device on the bad sectors
  4) Both paths will be failed, and IO is stuck due to queue_if_no_path 
(enabled by default for IPR)

  The detailed problem description and resolution are described in the
  commit message.

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

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

[Kernel-packages] [Bug 1709964] Re: Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode on POWER9 DD2.0

[Thadeu Lima de Souza Cascardo]

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

Title:
  Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode
  on POWER9 DD2.0

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  == SRU Justification ==
  Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode on 
POWER9 DD2.0.

  This is a regression introduced by mainline commit 8d911904f3ce.  This 
regression
  is resolved by commit 8c218578fcbbbdb10416c8614658bf32e3bf1655.

  Commit 8c218578fc is available in mailine as of 4.12-rc5.



  ---Problem Description---
  Unable to count pm_run_inst_cmpl using perf tool on boston dd2.0

  root@isvbos3:~# perf stat -e r500fa,r600f4 -a  sleep 1

   Performance counter stats for 'system wide':

       r500fa
   8,162,912  r600f4

     1.001562716 seconds time elapsed

  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = p9 dd2.0

  ---Steps to Reproduce---
   root@isvbos3:~# perf stat -e r500fa,r600f4 -a  sleep 1

   Performance counter stats for 'system wide':

       r500fa
   8,162,912  r600f4

     1.001562716 seconds time elapsed

  > Also we need this upstream fix 8c218578fcbbbdb10416c8614658bf32e3bf1655 in
  > the distro.

  $ git log 8c218578fcbbbdb10416c8614658 -1
  commit 8c218578fcbbbdb10416c8614658bf32e3bf1655
  Author: Madhavan Srinivasan 
  Date:   Fri May 26 13:38:27 2017 +0530

  powerpc/perf: Fix Power9 test_adder fields

  Commit 8d911904f3ce4 ('powerpc/perf: Add restrictions to PMC5 in power9 
DD1')
  was added to restrict the use of PMC5 in Power9 DD1. Intention was to 
disable
  the use of PMC5 using raw event code. But instead of updating the
  power9_isa207_pmu structure (used on DD1), the commit incorrectly updated 
the
  power9_pmu structure. Fix it.

  Fixes: 8d911904f3ce ("powerpc/perf: Add restrictions to PMC5 in power9 
DD1")
  Reported-by: Shriya 
  Signed-off-by: Madhavan Srinivasan 
  Tested-by: Shriya 
  Signed-off-by: Michael Ellerman 

  $ git describe --contains 8c218578fcbbbdb
  v4.12-rc7~9^2~13
  $

  Commit 8c218578fc is available with kernel 4.12-rc7 afterwards.

  I don't see this fix in the Ubuntu 16.04.3 Zesty tree (the P9 hwe
  kernel, 4.10 based).

  Need to mirror to Canonical to request they pull in:
  8c218578fcbbbdb10416c8614658bf32e3bf1655

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

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

[Kernel-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

[Tyler Hicks]

The kernel patches were committed to the Ubuntu Artful kernel git repo:
https://lists.ubuntu.com/archives/kernel-team/2017-August/086714.html

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

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

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

[Kernel-packages] [Bug 1712232] Re: [Feature] KNM: KNM NIs Enabling

[ChristianEhrhardt]

Qemu change upstream since 2.8 and the other one since 2.9 - since we moved to 
2.10 a week ago this bug is fix released in Artful.
Adapting task status to reflect that.

** Changed in: qemu (Ubuntu Artful)
   Status: Triaged => Fix Released

** Changed in: qemu (Ubuntu Artful)
 Assignee: ChristianEhrhardt (paelzer) => (unassigned)

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

Title:
  [Feature] KNM: KNM NIs Enabling

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in qemu source package in Artful:
  Fix Released

Bug description:
  KNM NIs Enabling, including avx512 4vnniw, 4fmaps, vpopcntdq

  
  AVX512_4VNNIW and AVX512_4FMAPS

  Linux kernel commit id: 4504b5c9414c55da37f26b1faf49c09a2acbf255

  QEMU commit id: 95ea69fb46266aaa46d0c8b7f0ba8c4903dbe4e3

  AVX512_VPOPCNTDQ
  QEMU commit id: f77543772dcd38fa438470d9b80bafbd3a3ebbd7

  This feature should have been merged to 17.10 beta1.  Create it for
  track.

  Target Release: 17.10

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

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

[Kernel-packages] [Bug 1713462] Re: linux: -proposed tracker

[Stefan Bader]

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the  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

  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469

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

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

[Kernel-packages] [Bug 1713458] Re: linux-lts-trusty: -proposed tracker

[Stefan Bader]

** Also affects: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

Title:
  linux-lts-trusty:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the  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 --
  kernel-stable-master-bug: 1713456

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

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

[Kernel-packages] [Bug 1713467] Re: linux-aws: -proposed tracker

[Stefan Bader]

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

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

Bug description:
  This bug is for tracking the  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 --
  kernel-stable-master-bug: 1713462

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

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

[Kernel-packages] [Bug 1713456] Re: linux: -proposed tracker

[Stefan Bader]

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the  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

  backports: 1713458
  derivatives:

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

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

[Kernel-packages] [Bug 1713455] Re: linux: -proposed tracker

[Stefan Bader]

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-lbm series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

Bug description:
  This bug is for tracking the  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

  backports: 
  derivatives:

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

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

[Kernel-packages] [Bug 1713459] Re: linux: -proposed tracker

[Stefan Bader]

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

Bug description:
  This bug is for tracking the  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

  backports: 1713461
  derivatives:

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

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

[Kernel-packages] [Bug 1713461] Re: linux-lts-vivid: -proposed tracker

[Stefan Bader]

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

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

Title:
  linux-lts-vivid:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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  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 --
  kernel-stable-master-bug: 1713459

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

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

[Kernel-packages] [Bug 1713470] Re: linux: -proposed tracker

[Stefan Bader]

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  New

Bug description:
  This bug is for tracking the  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

  backports: 1713471,1713472
  derivatives: 1713473

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

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

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

[Mohamed Zouaghi]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1713476/+attachment/4940120/+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/1713476

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

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

[Mohamed Zouaghi]

apport information

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

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

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

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

[Mohamed Zouaghi]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1713476/+attachment/4940121/+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/1713476

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

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

[Mohamed Zouaghi]

apport information

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

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

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

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

[Mohamed Zouaghi]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1713476/+attachment/4940127/+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/1713476

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1713476] ProcCpuinfoMinimal.txt

[Mohamed Zouaghi]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1713476/+attachment/4940122/+files/ProcCpuinfoMinimal.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/1713476

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

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

[Mohamed Zouaghi]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1713476/+attachment/4940128/+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/1713476

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

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

[Mohamed Zouaghi]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1713476/+attachment/4940124/+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/1713476

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

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

[Mohamed Zouaghi]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1713476/+attachment/4940126/+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/1713476

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

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

[Mohamed Zouaghi]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1713476/+attachment/4940125/+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/1713476

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

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

[Mohamed Zouaghi]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1713476/+attachment/4940119/+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/1713476

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

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

[Mohamed Zouaghi]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1713476/+attachment/4940118/+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/1713476

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

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

[Mohamed Zouaghi]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1713476/+attachment/4940117/+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/1713476

Title:
  Touchpad not recongnized anymore in Lenovo ideapad 700 15ISK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In my Lenovo ideapad 700, the touchpad is not working anymore, It's
  completely unresponsive. I've last used it a couple of days ago
  (2017/08/26).

  Today when I checked the system settings, all settings related to the
  touchpad have vanished. External mouse works properly though. I've
  tried few commands but it seems that the system doesn't recognize the
  touchpad anymore:

   $ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=10   [slave  
pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=11   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  Note: The entry "Microsoft... Mouse..." the mouse I'm using as workaround
   
  OS and kernel versions:
  $ uname -amoving
  Linux zoua-machine 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  $ cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04

  As per https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo
  I've attached the /proc/bus/input/devices the dmeg and the Xorg.0.log

  As for the context, a couple of days ago I've disabled the touchpad "tap to 
click" feature because my hands kept touching it while typing causing the 
cursor to fly from line to line... On the next login the touchpad stopped 
working and disappeared from system settings.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   zouaghi1861 F...m pulseaudio
   /dev/snd/controlC0:  zouaghi1861 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7c2973ee-463c-46cb-8c11-059675c15466
  InstallationDate: Installed on 2017-08-18 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN53WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN53WW:bd07/11/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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