[Kernel-packages] [Bug 1288055] Re: Nvidia and Pulseaudio

[Launchpad Bug Tracker]

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

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

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

Title:
  Nvidia and Pulseaudio

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Nvidia está causando incompatibilidade no Ubuntu 13.10.
  Minha placa de vídeo e uma nVidia GeoForce 550 ti.
  A um bug também no pulseaudio, eu tenho que instalar um painel de controle 
pulseaudio para poder abilitar o microfone
  frontal para poder falar no Skype.
  Obrigado pela paciência.
  ASS : THAUAN7020

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-17-generic 3.11.0-17.31
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  soneca 1417 F pulseaudio
   /dev/snd/controlC0:  soneca 1417 F pulseaudio
  CurrentDmesg:
   [   17.861452] atl1c :03:00.0: atl1c: eth0 NIC Link is Up<1000 Mbps Full 
Duplex>
   [   41.596084] systemd-hostnamed[1896]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
   [   86.328044] usb 1-8: reset high-speed USB device number 3 using ehci-pci
   [  299.136040] atl1c :03:00.0: vpd r/w failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update.
  Date: Wed Mar  5 01:58:20 2014
  HibernationDevice: RESUME=UUID=caa5d39c-44e4-4f1d-b2cc-529628b1c907
  InstallationDate: Installed on 2014-03-03 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. G41MT-S2P
  MarkForUpload: True
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=544fb0e8-c375-4dca-9e2d-c1d058564b2e ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-17-generic N/A
   linux-backports-modules-3.11.0-17-generic  N/A
   linux-firmware 1.116.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: G41MT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41MT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device

[Launchpad Bug Tracker]

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

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

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

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device

Status in linux package in Ubuntu:
  Expired

Bug description:
  Disabled a wireless adapter via NetworkManager. Got a kernel trace in
  dmesg.

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
  Network Adapter (rev 32)

  uname -r
  4.10.0-9-generic

  https://paste.ubuntu.com/24131142/

  There are also usb hot-plug messages in between ath10k related ones -
  this is because I disabled a wireless adapter and immediately plugged
  in a usb type-c dock so don't mind those.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-9-generic 4.10.0-9.11
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dima   3007 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar  7 17:28:37 2017
  InstallationDate: Installed on 2017-02-27 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-9-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open pcie_aspm=off
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-9-generic N/A
   linux-backports-modules-4.10.0-9-generic  N/A
   linux-firmware1.163
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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

[Kernel-packages] [Bug 1690633] Re: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  problemas con ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  victor 2377 F pulseaudio
   /dev/snd/controlC1:  victor 2377 F pulseaudio
  Date: Sat May 13 23:44:19 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=86b91b32-81f7-4b0a-bbea-977565334d5a
  InstallationDate: Installed on 2016-12-26 (139 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP 625
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=7d808db4-8b94-40cc-9d2b-6887cbbc0cfa 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~beta3-4ubuntu2
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-03-26 (48 days ago)
  dmi.bios.date: 11/10/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DVA Ver. F.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1475
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 72.14
  dmi.chassis.asset.tag: 5CG0510500
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DVAVer.F.60:bd11/10/2015:svnHewlett-Packard:pnHP625:pvr:rvnHewlett-Packard:rn1475:rvrKBCVersion72.14:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP 625
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1689853] Re: Kernel bug after probable OOM?

[Launchpad Bug Tracker]

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

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

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

Title:
  Kernel bug after probable OOM?

Status in linux package in Ubuntu:
  Expired

Bug description:
  Symptoms were a hung tab in Firefox (nightly) which then left a zombie
  process lingering around after introducing the processes to Mr Kill
  -KILL.

  I don't have swap configured because I like to be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed May 10 17:28:21 2017
  HibernationDevice: RESUME=UUID=fda86ae0-6316-4551-a064-a782b5d2a754
  InstallationDate: Installed on 2015-07-04 (676 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: MSI MS-7917
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=c992784f-51c3-441c-b9ae-e4e9278f2a4b ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (16 days ago)
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 5 (MS-7917)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7917
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1690632] Re: SATA card SiL 3112 doesn't work well

[Launchpad Bug Tracker]

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

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

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

Title:
  SATA card SiL 3112 doesn't work well

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 14.04.5 i386
  Ubuntu 16.04.2 i386

  I have a small DIY server for long time and I used PCI card with chip
  "SiL 3112" to connect SATA drives, to have RAID volume; I use SW RAID
  (mdadm). I am sure that when I built this system long time ago, it
  worked fine but it reports many DMA errors now, too many errors and it
  works slowly because there are many retries. I changed all my SATA
  cables, etc but that was not a source of the trouble. Real trouble is
  chip SiL3112. I believe that some change in Linux kernel module
  sata_sil started the trouble. I cannot tell when it happened, 2017,
  2016 or even 2015?

  Anyway, I replaced my SATA card with card based on SiL 3114 and it
  works fine!

  $ lspci | grep 3114
  00:0d.0 Mass storage controller: Silicon Image, Inc. SiI 3114 
[SATALink/SATARaid] Serial ATA Controller (rev 02)

  I see this message in dmesg output (14.04.5, 3.13.0-117-generic
  #164-Ubuntu SMP Fri Apr 7 11:06:36 UTC 2017 i686):

  [3.543370] sata_sil :00:0d.0: version 2.4
  [3.544339] sata_sil :00:0d.0: Applying R_ERR on DMA activate FIS 
errata fix

  Could be the same "workarround" applied to SiL 3112 card? I know that
  when SiL 3112 is in my PC, I cannot find any message "Applying R_ERR
  on DMA activate FIS errata fix" in dmesg output.

  BTW, I have found some comments on the net, that these cards are
  "broken" and should be avoided as plague, etc. Well, I think that my
  SiL 3112 worked fine in the past and SiL 3114 works fine just now, so
  it is driver problem (and some HW design bug, so the performance of
  chips is limited by this SW workaround).

  This report is from Ubuntu 14.04.4 but I already tried 16.04.2 but it
  was not better, DMA errors were there but were more visible
  (annoying).

  I can update this report with details about SiL 3112 card but it is
  out of my PC now...

  SATA card with SiL 3112 is loaded with Non-RAID BIOS v 4.2.84.
  http://www.latticesemi.com/view_document?document_id=51771
  file b4284.bin

  ---
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/hwC0D0', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=468d6e78-760e-4825-9e16-3b8e4110f981
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Compaq Deskpro EN Series SFF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-117-generic 
root=UUID=afab7acb-1aa5-4ac8-a8ff-4cb3c57b5eb7 ro quiet splash acpi=force 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-117-generic N/A
   linux-backports-modules-3.13.0-117-generic  N/A
   linux-firmware  1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-117-generic i686
  UpgradeStatus: Upgraded to trusty on 2015-03-08 (797 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 08/21/99
  dmi.bios.vendor: Compaq
  dmi.bios.version: 686T5
  dmi.board.name: 042Ch
  dmi.board.vendor: Compaq
  dmi.chassis.asset.tag: 8031DLCC0314
  dmi.chassis.type: 3
  dmi.chassis.vendor: Compaq
  dmi.modalias: 
dmi:bvnCompaq:bvr686T5:bd08/21/99:svnCompaq:pnDeskproENSeriesSFF:pvr:rvnCompaq:rn042Ch:rvr:cvnCompaq:ct3:cvr:
  dmi.product.name: Deskpro EN Series SFF
  dmi.sys.vendor: Compaq

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

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

[Kernel-packages] [Bug 1689423] Re: annoying freezing

[Launchpad Bug Tracker]

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

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

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

Title:
  annoying freezing

Status in linux package in Ubuntu:
  Expired

Bug description:
  My system suddenly freezes and stops working completely when i for
  example play a video online while i have a song played from my drive,
  this is becoming annoying now because it's effecting my work and the
  system keeps freezing with no any solution than forcing shutdown... i
  need some help here people.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demolator   1745 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue May  9 03:30:13 2017
  MachineType: ASUSTeK COMPUTER INC. X556UF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=4ffdc348-2840-4817-8c12-b551c86e0534 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UF.404
  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.404:bd05/20/2016: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.

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

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

[Kernel-packages] [Bug 1690569] Re: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  Automatically filed report (Ubuntu GNOME 17.04 Zesty Zapus)

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1023 F pulseaudio
sahekyto   1400 F pulseaudio
  Date: Sat May 13 19:35:38 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-05-13 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 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 1c4f:0048 SiGma Micro 
   Bus 001 Device 003: ID 5986: Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Lemur
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=ed0bafa6-440e-491a-8285-41a4db80695e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76
  dmi.board.version: lemu7
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/17/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A:
  dmi.product.name: Lemur
  dmi.product.version: lemu7
  dmi.sys.vendor: System76

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

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

[Kernel-packages] [Bug 1689697] Re: Laptop Touchpad doesn't work at all

[Launchpad Bug Tracker]

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

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

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

Title:
  Laptop Touchpad  doesn't work at all

Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm having Dell Inspiron 15r 5537 laptop.
  I've installed Ubuntu 16.04 after removing windows 10.
  After installation now my touchpad is not working at all. I tried external 
mouse and it is working but touchpad isn't.The touchpad was working fine with 
windows but after i installed ubuntu it stopped working.

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

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

[Kernel-packages] [Bug 1690490] Re: no sound

[Launchpad Bug Tracker]

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

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

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

Title:
  no sound

Status in linux package in Ubuntu:
  Expired

Bug description:
  power outage no battery

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Fri May 12 21:55:09 2017
  HibernationDevice: RESUME=UUID=afe10987-bd60-4356-aa71-790cef4f64fb
  InstallationDate: Installed on 2012-12-22 (1602 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer, inc. Aspire 4520
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=776a497e-7cf0-491b-8c63-5a35aaded5dd ro drm.debug=0xe plymouth:debug
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2007
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.3620
  dmi.board.name: Mono
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv1.3620:bd09/14/2007:svnAcer,inc.:pnAspire4520:pvrNotApplicable:rvnAcer,Inc.:rnMono:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 4520
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

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

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

[Kernel-packages] [Bug 1687174] Re: no wifi after software update on Dell Latitude D630

[Launchpad Bug Tracker]

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

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

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

Title:
  no wifi after software update on Dell Latitude D630

Status in linux package in Ubuntu:
  Expired

Bug description:
  Just after software update tonight, computer lost Wifi connection and
  was not seeing any Wifi Access Point.

  --> I rebooted computer. Usually Wifi is always ON after reboot, it
  was OFF. I switch it to ON, but this did not help.

  --> I completely shutdown computer and switch on again. I find again
  after startup, Wifi is switched to OFF. I switch to ON again but
  computer can not see any Wifi Access Points.

  I checked the software update log but could not find any package
  related to Wifi / network manager :

  tail -n25 /var/log/apt/history.log

  Start-Date: 2017-04-28  21:30:08
  Commandline: aptdaemon role='role-commit-packages' sender=':1.135'
  Upgrade: gir1.2-gtk-3.0:amd64 (3.18.9-1ubuntu3.2, 3.18.9-1ubuntu3.3), 
libnss3-nssdb:amd64 (2:3.26.2-0ubuntu0.16.04.2, 2:3.28.4-0ubuntu0.16.04.1), 
libapt-inst2.0:amd64 (1.2.19, 1.2.20), appstream:amd64 (0.9.4-1ubuntu2, 
0.9.4-1ubuntu3), libsystemd0:amd64 (229-4ubuntu16, 229-4ubuntu17), 
libsystemd0:i386 (229-4ubuntu16, 229-4ubuntu17), libgtk-3-common:amd64 
(3.18.9-1ubuntu3.2, 3.18.9-1ubuntu3.3), apt:amd64 (1.2.19, 1.2.20), 
libgtk-3-0:amd64 (3.18.9-1ubuntu3.2, 3.18.9-1ubuntu3.3), libgs9:amd64 
(9.18~dfsg~0-0ubuntu2.3, 9.18~dfsg~0-0ubuntu2.4), snapd:amd64 (2.22.6, 2.24.1), 
snap-confine:amd64 (2.22.6, 2.24.1), libnspr4-0d:amd64 
(2:4.12-0ubuntu0.16.04.1, 2:4.13.1-0ubuntu0.16.04.1), udev:amd64 
(229-4ubuntu16, 229-4ubuntu17), libapt-pkg5.0:amd64 (1.2.19, 1.2.20), 
libnss3-1d:amd64 (2:3.26.2-0ubuntu0.16.04.2, 2:3.28.4-0ubuntu0.16.04.1), 
libudev1:amd64 (229-4ubuntu16, 229-4ubuntu17), libudev1:i386 (229-4ubuntu16, 
229-4ubuntu17), dpkg:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2), 
libgtk-3-bin:amd64 (3.18.9-1ubuntu3.2, 3.18.9-1ubuntu3.3), libudev-dev:amd64 
(229-4ubuntu16, 229-4ubuntu17), libgtk-3-dev:amd64 (3.18.9-1ubuntu3.2, 
3.18.9-1ubuntu3.3), systemd-sysv:amd64 (229-4ubuntu16, 229-4ubuntu17), 
chromium-codecs-ffmpeg-extra:amd64 (57.0.2987.98-0ubuntu0.16.04.1276, 
58.0.3029.81-0ubuntu0.16.04.1277), ubuntu-core-launcher:amd64 (2.22.6, 2.24.1), 
libpam-systemd:amd64 (229-4ubuntu16, 229-4ubuntu17), libgail-3-0:amd64 
(3.18.9-1ubuntu3.2, 3.18.9-1ubuntu3.3), ghostscript:amd64 
(9.18~dfsg~0-0ubuntu2.3, 9.18~dfsg~0-0ubuntu2.4), systemd:amd64 (229-4ubuntu16, 
229-4ubuntu17), mysql-common:amd64 (5.7.17-0ubuntu0.16.04.2, 
5.7.18-0ubuntu0.16.04.1), apt-utils:amd64 (1.2.19, 1.2.20), ghostscript-x:amd64 
(9.18~dfsg~0-0ubuntu2.3, 9.18~dfsg~0-0ubuntu2.4), libmysqlclient20:i386 
(5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1), libgs9-common:amd64 
(9.18~dfsg~0-0ubuntu2.3, 9.18~dfsg~0-0ubuntu2.4), thermald:amd64 (1.5-2ubuntu3, 
1.5-2ubuntu4), libnss3:amd64 (2:3.26.2-0ubuntu0.16.04.2, 
2:3.28.4-0ubuntu0.16.04.1), apt-transport-https:amd64 (1.2.19, 1.2.20), 
libappstream3:amd64 (0.9.4-1ubuntu2, 0.9.4-1ubuntu3), xsltproc:amd64 
(1.1.28-2.1, 1.1.28-2.1ubuntu0.1), libdpkg-perl:amd64 (1.18.4ubuntu1.1, 
1.18.4ubuntu1.2), libnspr4:amd64 (2:4.12-0ubuntu0.16.04.1, 
2:4.13.1-0ubuntu0.16.04.1), libxslt1.1:amd64 (1.1.28-2.1, 1.1.28-2.1ubuntu0.1), 
libxslt1.1:i386 (1.1.28-2.1, 1.1.28-2.1ubuntu0.1), dpkg-dev:amd64 
(1.18.4ubuntu1.1, 1.18.4ubuntu1.2)

  lspci -nn | grep 0280
  0c:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG 
[Golan] Network Connection [8086:4222] (rev 02)

  I could not find what was the package which caused this regression so
  can could not revert it.

  So until I get a fix, my wifi will not be working ...

  What is the full computer model number (ex. HP G32-301TX Notebook PC)?
  --> Laptop Dell Latitude D630 model PP18L

  sudo iw dev wlan0 scan | grep -i "ds parameter set"
  [sudo] password for remi:
  command failed: Network is down (-100)

  even if "Enable Networking" is ON and LAN/Ethernet connection works.

  apt-cache policy linux-firmware
  linux-firmware:
    Installed: 1.157.8
    Candidate: 1.157.8
    Version table:
   *** 1.157.8 500
  500 http://archive.linux.duke.edu/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.linux.duke.edu/ubuntu xenial-updates/main i386 
Packages
  500 http://archive.linux.duke.edu/ubuntu xenial-security/main amd64 
Packages
  500 http://archive.linux.duke.edu/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://archive.linux.duke.edu/ubuntu xenial/main amd64 Packages
  500 http://archive.linux.duke.edu/ubuntu xenial/main i386 Packages

  cat /var/log/dmesg | grep "firmware version"
  [   33.519189] iwl3945 :0c:00.0: loaded firmware version 

[Kernel-packages] [Bug 1689918] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000018

[Launchpad Bug Tracker]

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

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

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0018

Status in linux package in Ubuntu:
  Expired

Bug description:
  I ran K3B with a DVD-RW inserted while extracting an archive.

  My desktop froze and I found this in dmesg:

  [ 3293.518501] sr 4:0:0:0: [sr0] tag#5 CDB: Read(10) 28 00 00 23 04 00 00 00 
02 00
  [ 3293.518502] blk_update_request: I/O error, dev sr0, sector 9179136
  [ 3293.518506] Buffer I/O error on dev sr0, logical block 1147392, async page 
read
  [ 3293.606203] sr 4:0:0:0: [sr0] tag#7 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [ 3293.606208] sr 4:0:0:0: [sr0] tag#7 Sense Key : Illegal Request [current] 
  [ 3293.606212] sr 4:0:0:0: [sr0] tag#7 Add. Sense: Logical block address out 
of range
  [ 3293.606216] sr 4:0:0:0: [sr0] tag#7 CDB: Read(10) 28 00 00 23 05 3a 00 00 
02 00
  [ 3293.606219] blk_update_request: I/O error, dev sr0, sector 9180392
  [ 3293.617985] sr 4:0:0:0: [sr0] tag#8 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [ 3293.617990] sr 4:0:0:0: [sr0] tag#8 Sense Key : Illegal Request [current] 
  [ 3293.617994] sr 4:0:0:0: [sr0] tag#8 Add. Sense: Logical block address out 
of range
  [ 3293.617998] sr 4:0:0:0: [sr0] tag#8 CDB: Read(10) 28 00 00 23 05 3a 00 00 
02 00
  [ 3293.618001] blk_update_request: I/O error, dev sr0, sector 9180392
  [ 3293.618009] Buffer I/O error on dev sr0, logical block 1147549, async page 
read
  [ 3302.607388] isofs_fill_super: root inode is not a directory. Corrupted 
media?
  [ 3328.320211] BUG: unable to handle kernel NULL pointer dereference at 
0018
  [ 3328.320257] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 
[i915]
  [ 3328.320274] PGD 0 

  [ 3328.320287] Oops: 0002 [#1] SMP
  [ 3328.320296] Modules linked in: isofs bnep pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport iptable_filter 
binfmt_misc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic aesni_intel 
crypto_simd intel_cstate glue_helper cryptd intel_rapl_perf aes_x86_64 
nls_iso8859_1 dm_crypt snd_hda_intel snd_hda_codec snd_hda_core snd_usb_audio 
snd_usbmidi_lib snd_hwdep input_leds snd_seq_midi snd_seq_midi_event 
snd_rawmidi uvcvideo videobuf2_vmalloc snd_seq videobuf2_memops videobuf2_v4l2 
videobuf2_core snd_pcm snd_seq_device videodev media joydev snd_timer snd 
soundcore serio_raw mei_me shpchp mei intel_pch_thermal hci_uart mac_hid btbcm
  [ 3328.320453]  btqca btintel acpi_als bluetooth intel_lpss_acpi intel_lpss 
kfifo_buf acpi_pad industrialio parport_pc ppdev lp parport ip_tables x_tables 
autofs4 btrfs xor raid6_pq hid_generic usbhid mxm_wmi i915 i2c_algo_bit 
drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt ptp fb_sys_fops 
pps_core drm ahci libahci wmi video pinctrl_sunrisepoint pinctrl_intel i2c_hid 
hid fjes
  [ 3328.320533] CPU: 1 PID: 1371 Comm: Xorg Tainted: G   OE   
4.10.0-20-generic #22-Ubuntu
  [ 3328.320553] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./B150M Pro4S/D3, BIOS P7.00 12/06/2016
  [ 3328.320575] task: 9c01613d2b00 task.stack: b72801ca4000
  [ 3328.320600] RIP: 
0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  [ 3328.320617] RSP: :b72801ca7898 EFLAGS: 00010246
  [ 3328.320629] RAX: 9c00b2bf2040 RBX: 0003 RCX: 
0003
  [ 3328.320645] RDX:  RSI: 9c015bc82000 RDI: 
9c015d3b
  [ 3328.320670] RBP: b72801ca78f0 R08:  R09: 

  [ 3328.320692] R10:  R11: 9c016dfd5dc0 R12: 
9c00c9aee000
  [ 3328.320709] R13: 9c00eb435110 R14: fffd5000 R15: 
1000
  [ 3328.320726] FS:  7f34ee1eba40() GS:9c016dd0() 
knlGS:
  [ 3328.320744] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3328.320757] CR2: 0018 CR3: 0001dcce6000 CR4: 
002406e0
  [ 3328.320774] Call Trace:
  [ 3328.320792]  gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
  [ 3328.320807]  ? swiotlb_map_sg_attrs+0x49/0x110
  [ 3328.320827]  gen8_alloc_va_range+0x23d/0x470 [i915]
  [ 3328.320849]  i915_vma_bind+0x7e/0x170 [i915]
  [ 3328.320870]  __i915_vma_do_pin+0x2a5/0x450 [i915]
  [ 3328.320891]  i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
  [ 3328.320915]  i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
  [ 3328.320938]  i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915]
  [ 3328.320954]  ? kmem_cache_alloc_trace+0x142/0x190
  [ 3328.320973]  ? 

[Kernel-packages] [Bug 1690683] Re: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  Thought I was doing a normal apt-get update, then apt-get upgrade. Had
  to do apt configure -a then something alse and updates seemed
  toproceed. After reboot while doing something alse entirely got pop-up
  letting me know I had encountered some error and was led to this page
  to report it. Here I am, this is what I know. I'm not seeing any
  actual behavioral problems with my system. Maybe the suspicion of an
  error is actually an error. I don't know.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  grouch0   26203 F pulseaudio
   /dev/snd/controlC1:  grouch0   26203 F pulseaudio
  Date: Sun May 14 17:09:33 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2016-10-29 (197 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC 
Webcam / CNF7129
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK Computer Inc. G73Jh
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=58565aff-e47e-4bdb-a715-e77f859cd531 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~beta3-4ubuntu2
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (28 days ago)
  dmi.bios.date: 01/27/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G73Jh.213
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G73Jh
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG73Jh.213:bd01/27/2011:svnASUSTeKComputerInc.:pnG73Jh:pvr1.0:rvnASUSTeKComputerInc.:rnG73Jh:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: G73Jh
  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/1690683/+subscriptions

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

[Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

[Keary Parinis]

Neither kernel worked unfortunately. Please see attached. Additionally,
my touch screen was not recognized.

** Attachment added: "kernel_411.0-11_error.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658345/+attachment/4914904/+files/kernel_411.0-11_error.png

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

Title:
  Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not 
recognize the touchpad (it does recognize the touch screen nicely though). When 
I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, 
which recognizes the touchpad from Elantech. I searched online for days and I 
found Elantech drivers for Ubuntu 14.04, however, I was unable to load older 
versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad 
in future updates? I attached a screen shot of my xinput -list output. Please 
let me know if you require any additional information. Thank you.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keary  2345 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
  InstallationDate: Installed on 2017-01-18 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80U3
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2MCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Sofia-F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1130
  dmi.modalias: 
dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130:
  dmi.product.name: 80U3
  dmi.product.version: Lenovo ideapad FLEX 4-1130
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1704343] Re: Ubuntu17.10: Changing guest timebase offset breaks host

[Joseph Salisbury]

This commit is now in the Ubuntu-4.11.0-10.15~36 17.10 kernel.

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

** Changed in: linux (Ubuntu Artful)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Joseph Salisbury (jsalisbury)

** Changed in: ubuntu-power-systems
   Status: Triaged => 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/1704343

Title:
  Ubuntu17.10: Changing guest timebase offset breaks host

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - NAGESWARA R. SASTRY  -
  2017-07-04 07:20:40 ==

  ---Problem Description---
  With little load on the system seeing kernel stack traces and soft lockup 
issues.
   
  Contact Information = nasas...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston25 4.12.0-041200rc6-generic #201706191233 SMP Mon Jun 19 
17:38:35 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Boston Power9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   With little load on the system seeing the stack trace. Start 2-3 guests or 
run some workload.
   
  Stack trace output:
   [56954.376790] NMI watchdog: BUG: soft lockup - CPU#44 stuck for 22s! [CPU 
3/KVM:48428]
  [56954.376949] Modules linked in: vhost_net vhost tap xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter input_leds joydev mac_hid idt_89hpesx 
at24 nvmem_core ofpart binfmt_misc cmdlinepart powernv_flash mtd 
uio_pdrv_genirq uio ibmpowernv opal_prd ipmi_powernv ipmi_devintf vmx_crypto 
ipmi_msghandler ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas
  [56954.377200]  hid_generic usbhid hid ast i2c_algo_bit ttm drm_kms_helper 
syscopyarea crct10dif_vpmsum sysfillrect crc32c_vpmsum sysimgblt fb_sys_fops 
drm i40e aacraid
  [56954.377263] CPU: 44 PID: 48428 Comm: CPU 3/KVM Not tainted 
4.12.0-041200rc6-generic #201706191233
  [56954.377269] task: c000200a74621000 task.stack: c000200a811cc000
  [56954.377277] NIP: c01a4464 LR: c01a4424 CTR: 
c008a970
  [56954.377283] REGS: c000200a811cf7c0 TRAP: 0901   Not tainted  
(4.12.0-041200rc6-generic)
  [56954.377287] MSR: 9280b033 
  [56954.377325]   CR: 48244224  XER: 2000
  [56954.377328] CFAR: c01a4470 SOFTE: 1
 GPR00: c01a4404 c000200a811cfa40 c1503800 
0022
 GPR04: 0022 0022  
0001
 GPR08: 0001 0003 c000200a95599518 
c1541ec0
 GPR12: c008a970 cfadce00
  [56954.377403] NIP [c01a4464] smp_call_function_many+0x374/0x400
  [56954.377414] LR [c01a4424] smp_call_function_many+0x334/0x400
  [56954.377417] Call Trace:
  [56954.377429] [c000200a811cfa40] [c01a4404] 
smp_call_function_many+0x314/0x400 (unreliable)
  [56954.377444] [c000200a811cfac0] [c01a462c] 
kick_all_cpus_sync+0x3c/0x50
  [56954.377459] [c000200a811cfae0] [c006e01c] pmdp_invalidate+0x7c/0xc0
  [56954.377473] [c000200a811cfb10] [c03315f4] 
change_huge_pmd+0x1d4/0x290
  [56954.377486] [c000200a811cfb80] [c02e59c8] 
change_protection_range+0xa38/0xcf0
  [56954.377500] [c000200a811cfcc0] [c030ff88] 
change_prot_numa+0x38/0xb0
  [56954.377514] [c000200a811cfcf0] [c0130584] 
task_numa_work+0x2c4/0x3e0
  [56954.377527] [c000200a811cfdb0] [c0115060] task_work_run+0x140/0x1a0
  [56954.377541] [c000200a811cfe00] [c001cd14] 
do_notify_resume+0xf4/0x100
  [56954.377556] [c000200a811cfe30] [c000b544] 
ret_from_except_lite+0x70/0x74
  [56954.377562] Instruction dump:
  [56954.377571] 409dfd80 3d420004 394aa580 78691f24 7d2a482a e95e 7d4a4a14 
812a0018
  [56954.377597] 71280001 4182001c 6042 7c210b78 <7c421378> 812a0018 
71270001 4082fff0
  [56998.366340] NMI watchdog: BUG: soft lockup - CPU#37 stuck for 22s! 
[qemu-system-ppc:47850]
  [56998.366461] Modules linked in: vhost_net vhost tap xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc 

[Kernel-packages] [Bug 1704374] Re: system randomly hangs itself

[morris]

It seems that the new Kernel 4.12.1 has solved the problem. If it should
occur again I'll notify it. If the problem concerns with the kernel it
is possible to state that 4.10 kernel presents a bug at least for a
specific hardware platform and or bios.

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

Title:
  system randomly hangs itself

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this problem affect my system on Kubuntu 17.04 64bit
  Kde Plasma: 5.10.3
  kernel: 4.10.0.26
  Kde frameworks: 5.36.0
  Qt release: 5.7.1
  Probably I've solved with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash 
intel_idle.max_cstate=1"

  Randomly the operating system hangs both eist and or c1e options enabled or 
disabled. I hope that Kubuntu has not damaged my hardware. However what kind of 
workaround should be made on the klernel to have this problem solved once and 
forever?
  My hardware specs:
  maximus eteme;
  latest bios;
  8gb ram 4x2gb corsaire xms 1333;
  gigabyte gt 730 1gb OC
  xonar d2x.

  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
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  1353 F pulseaudio
   /dev/snd/controlC1:  james  1353 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jul 14 12:39:32 2017
  InstallationDate: Installed on 2017-04-25 (79 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer Maximus Extreme
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=52f9b441-fe75-4643-bbec-f912736d397b ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Maximus Extreme
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/24/2009:svnSystemmanufacturer:pnMaximusExtreme:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusExtreme:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: Maximus Extreme
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1670508] Re: CIFS: Enable encryption for SMB3

[Pavel Shilovsky]

Hi Kleber,

I tested the Xenial kernel from -proposed and got the following crash:

Jul 13 14:38:05 ubuntu-vm kernel: [  770.262084] BUG: unable to handle kernel 
NULL pointer dereference at   (null)
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262087] IP: [] 
cifs_discard_remaining_data+0xc/0x70 [cifs]
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262098] PGD 7db4fb067 PUD 7d5e3a067 
PMD 0
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262100] Oops:  [#1] SMP
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262340] Modules linked in: cifs drbg 
ansi_cprng cmac arc4 md4 nls_utf8 ccm fscache crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel i2c_piix4 aes_x86_64 8250_fintek lrw hyperv_fb 
gf128mul hv_balloon glue_helper ablk_helper cryptd input_leds serio_raw joydev 
mac_hid nfsd auth_rpcgss nfs_acl lockd grace sunrpc parport_pc ppdev lp parport 
autofs4 hid_generic hv_netvsc hv_utils ptp hid_hyperv hv_storvsc pps_core hid 
scsi_transport_fc hyperv_keyboard psmouse pata_acpi hv_vmbus floppy fjes [last 
unloaded: cifs]
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262360] CPU: 2 PID: 18568 Comm: cifsd 
Not tainted 4.4.0-85-generic #108-Ubuntu
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262361] Hardware name: Microsoft 
Corporation Virtual Machine/Virtual Machine, BIOS 090006  01/06/2017
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262362] task: 8807e1440f00 ti: 
8807da868000 task.ti: 8807da868000
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262363] RIP: 0010:[] 
 [] cifs_discard_remaining_data+0xc/0x70 [cifs]
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262371] RSP: 0018:8807da86bdc0  
EFLAGS: 00010246
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262372] RAX: ffc3 RBX: 
8807df0ae200 RCX: 
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262373] RDX: c0390b80 RSI: 
 RDI: 8807db71c000
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262373] RBP: 8807da86bdd0 R08: 
004d R09: 8807da86bcfc
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262374] R10: 01fc R11: 
 R12: 004d
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262375] R13: 8800f2fa1c00 R14: 
8800f2fa1c00 R15: 8807df2ea680
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262376] FS:  () 
GS:8807e568() knlGS:
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262377] CS:  0010 DS:  ES:  
CR0: 80050033
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262377] CR2:  CR3: 
0007de707000 CR4: 003406e0
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262379] DR0:  DR1: 
 DR2: 
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262380] DR3:  DR6: 
fffe0ff0 DR7: 0400
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262380] Stack:
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262381]  8807df0ae200 
004d 8807da86bdf8 c034159e
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262382]  8807db71c000 
004d 8807df0ae200 8807da86be40
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262383]  c0341694 
  8807e1440f00
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262385] Call Trace:
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262391]  [] 
cifs_readv_discard+0x1e/0x40 [cifs]
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262396]  [] 
cifs_readv_receive+0xd4/0x590 [cifs]
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262402]  [] 
cifs_demultiplex_thread+0x778/0xac0 [cifs]
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262408]  [] ? 
cifs_handle_standard+0x130/0x130 [cifs]
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262410]  [] 
kthread+0xe5/0x100
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262412]  [] ? 
kthread_create_on_node+0x1e0/0x1e0
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262414]  [] 
ret_from_fork+0x3f/0x70
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262415]  [] ? 
kthread_create_on_node+0x1e0/0x1e0
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262416] Code: 84 69 fe ff ff 44 89 f0 
eb 92 41 81 4d 00 00 00 02 00 e9 31 ff ff ff e8 03 fc d3 c0 0f 1f 00 0f 1f 44 
00 00 55 48 89 e5 41 54 53 <8b> 06 bb 04 00 00 00 2b 9f 60 03 00 00 49 89 fc 0f 
c8 25 ff ff
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262429] RIP  [] 
cifs_discard_remaining_data+0xc/0x70 [cifs]
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262435]  RSP 
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262435] CR2: 
Jul 13 14:38:05 ubuntu-vm kernel: [  770.262437] ---[ end trace 
5ac5926a1424b7e6 ]---

I think this issue is caused by commit
http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=master-
next=bdf2bdef7c7b61663266d942fabd528a4c7eddda which is a copy of
upstream commit. In upstream the issue has been fixed by commit
https://github.com/torvalds/linux/commit/350be257ea83029daee974c72b1fe2e6f1f8e615.
I did cherry-picked it into your Xenial branch and run small tests - it
went well. Can you please apply the latter commit as well to the
proposed 

[Kernel-packages] [Bug 1689946] Re: Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with split op

[Seth Forshee]

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

Title:
  Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with
  split op

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

Bug description:
   State: Open by: mdate on 19 March 2017 12:33:34 

  On a Bolt adapter in a system with Ubuntu 16.04, I've formatted the
  Bolt for T10 and am using it to do a dd with a 2M block size.

  Here are the commands:
  nvme format /dev/nvme0n1 --lbaf=1 --pil=0 --ms=0 --pi=2

  dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct count=1

  I get an error on the dd.
root@x1623bp1:~# dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct 
count=1
dd: error writing '/dev/nvme0n1': Input/output error
1+0 records in
0+0 records out
0 bytes copied, 0.0525061 s, 0.0 kB/s

  dmesg shows:
  [589997.985151] blk_update_request: I/O error, dev nvme0n1, sector 0

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

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

[Kernel-packages] [Bug 1697892] Re: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds

[Seth Forshee]

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

Title:
  linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link
  speeds

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

Bug description:
  These upstream patches are needed to correctly handle 5G, 25G and 50G
  speeds in 802.3ad:

  19ddde1eeca1 bonding: add 802.3ad support for 25G speeds
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e

  c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af

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

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

[Kernel-packages] [Bug 1673564] Re: ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with vhost=on

[Seth Forshee]

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

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

Title:
  ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with
  vhost=on

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

Bug description:
  [Impact]
  VMs can cause interrupts to be disabled on the host CPU, resulting in hangs.

  [Test Case]
  See Comment #1.

  [Regression Risk]
  (TBD, once proposed patches are finalized)

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

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

[Kernel-packages] [Bug 1704479] [NEW] Change CONFIG_IBMVETH to module

[bugproxy]

Public bug reported:

== Comment: #0 - Breno Leitao  - 2017-07-14 15:07:47 ==
Dear Canonical,

Please change the CONFIG_IBMVETH=y to module on artful kernel.

Thank you,
Breno

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


** Tags: architecture-ppc64le bugnameltc-156720 severity-high 
targetmilestone-inin1710

** Tags added: architecture-ppc64le bugnameltc-156720 severity-high
targetmilestone-inin1710

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

Title:
  Change CONFIG_IBMVETH to module

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Breno Leitao  - 2017-07-14 15:07:47 ==
  Dear Canonical,

  Please change the CONFIG_IBMVETH=y to module on artful kernel.

  Thank you,
  Breno

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

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

[Kernel-packages] [Bug 1704479] [NEW] Change CONFIG_IBMVETH to module

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Breno Leitao  - 2017-07-14 15:07:47 ==
Dear Canonical,

Please change the CONFIG_IBMVETH=y to module on artful kernel.

Thank you,
Breno

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


** Tags: architecture-ppc64le bugnameltc-156720 severity-high 
targetmilestone-inin1710
-- 
Change CONFIG_IBMVETH to module
https://bugs.launchpad.net/bugs/1704479
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 1704469] 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/1704469

Title:
  r8169 :02:00.0: invalid large VPD tag 7f at offset 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg:
  [ 1025.813826] r8169 :02:00.0: invalid large VPD tag 7f at offset 0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1801 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Jul 14 15:30:03 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (9 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-07-05 (8 days ago)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1704471] 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/1704471

Title:
  package linux-image-4.10.0-26-lowlatency (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Non so perché si è verificato questo errore

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-26-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-24.28-lowlatency 4.10.15
  Uname: Linux 4.10.0-24-lowlatency i686
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vittorio   1238 F pulseaudio
   /dev/snd/controlC0:  vittorio   1238 F pulseaudio
  Date: Fri Jul 14 19:33:03 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=0e09baa8-8c43-499d-8006-7275dc5c1086
  InstallationDate: Installed on 2017-05-08 (67 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release i386 
(20161012.1)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-lowlatency 
root=UUID=5395e556-416c-40c3-a8ef-6790431337c1 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~beta3-4ubuntu2.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-26-lowlatency (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-06-16 (28 days ago)
  dmi.bios.date: 06/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41T-M LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1704470] 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/1704470

Title:
  playback fails using alsa in mpd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using 4.11.0-10.15 kernel from playback fails using this mpd.conf

  ##Pulseaudio
  #audio_output {
  # type "pulse"
  # name "Local MPD"
  # server "127.0.0.1"
  #}

  ##Alsa
  audio_output {
  type "alsa"
   name "Cambridge Audio DAC100 USB 2 - USB Audio"
   device "hw:1,0"
   auto_resample "no"
   auto_format "no"
   auto_channels "no"
   replay_gain_handler "none"
   mixer_type "none"
  }

  If I reboot into 4.10.0-26 then playback with alsa works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wolf   1742 F pulseaudio
   /dev/snd/pcmC1D0p:   wolf   1742 F...m pulseaudio
   /dev/snd/controlC1:  wolf   1742 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Jul 14 20:27:17 2017
  HibernationDevice: RESUME=UUID=9f10a8f1-df29-4691-b2cc-7fbe68244587
  MachineType: NOVATECH LTD MBB-44608
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=c81d4267-4905-4511-9011-d51db8eb0c3a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

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

[Kernel-packages] [Bug 1704470] Re: playback fails using alsa in mpd

[Kev Bowring]

appears to be intermittent - experimented with kernel from artful
proposed reverting to using alsa, that worked. rebooted to 4.11.0-10.15
and it works again.

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

Title:
  playback fails using alsa in mpd

Status in linux package in Ubuntu:
  New

Bug description:
  Using 4.11.0-10.15 kernel from playback fails using this mpd.conf

  ##Pulseaudio
  #audio_output {
  # type "pulse"
  # name "Local MPD"
  # server "127.0.0.1"
  #}

  ##Alsa
  audio_output {
  type "alsa"
   name "Cambridge Audio DAC100 USB 2 - USB Audio"
   device "hw:1,0"
   auto_resample "no"
   auto_format "no"
   auto_channels "no"
   replay_gain_handler "none"
   mixer_type "none"
  }

  If I reboot into 4.10.0-26 then playback with alsa works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wolf   1742 F pulseaudio
   /dev/snd/pcmC1D0p:   wolf   1742 F...m pulseaudio
   /dev/snd/controlC1:  wolf   1742 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Jul 14 20:27:17 2017
  HibernationDevice: RESUME=UUID=9f10a8f1-df29-4691-b2cc-7fbe68244587
  MachineType: NOVATECH LTD MBB-44608
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=c81d4267-4905-4511-9011-d51db8eb0c3a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

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

[Kernel-packages] [Bug 1704471] Re: package linux-image-4.10.0-26-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[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/1704471

Title:
  package linux-image-4.10.0-26-lowlatency (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Non so perché si è verificato questo errore

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-26-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-24.28-lowlatency 4.10.15
  Uname: Linux 4.10.0-24-lowlatency i686
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vittorio   1238 F pulseaudio
   /dev/snd/controlC0:  vittorio   1238 F pulseaudio
  Date: Fri Jul 14 19:33:03 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=0e09baa8-8c43-499d-8006-7275dc5c1086
  InstallationDate: Installed on 2017-05-08 (67 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release i386 
(20161012.1)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-lowlatency 
root=UUID=5395e556-416c-40c3-a8ef-6790431337c1 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~beta3-4ubuntu2.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-26-lowlatency (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-06-16 (28 days ago)
  dmi.bios.date: 06/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41T-M LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1704471] [NEW] package linux-image-4.10.0-26-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Vittorio]

Public bug reported:

Non so perché si è verificato questo errore

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-26-lowlatency (not installed)
ProcVersionSignature: Ubuntu 4.10.0-24.28-lowlatency 4.10.15
Uname: Linux 4.10.0-24-lowlatency i686
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  vittorio   1238 F pulseaudio
 /dev/snd/controlC0:  vittorio   1238 F pulseaudio
Date: Fri Jul 14 19:33:03 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=0e09baa8-8c43-499d-8006-7275dc5c1086
InstallationDate: Installed on 2017-05-08 (67 days ago)
InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release i386 (20161012.1)
MachineType: System manufacturer System Product Name
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-lowlatency 
root=UUID=5395e556-416c-40c3-a8ef-6790431337c1 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~beta3-4ubuntu2.1
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-4.10.0-26-lowlatency (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: Upgraded to zesty on 2017-06-16 (28 days ago)
dmi.bios.date: 06/08/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5G41T-M LX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: apport-package i386 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/1704471

Title:
  package linux-image-4.10.0-26-lowlatency (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Non so perché si è verificato questo errore

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-26-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-24.28-lowlatency 4.10.15
  Uname: Linux 4.10.0-24-lowlatency i686
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vittorio   1238 F pulseaudio
   /dev/snd/controlC0:  vittorio   1238 F pulseaudio
  Date: Fri Jul 14 19:33:03 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=0e09baa8-8c43-499d-8006-7275dc5c1086
  InstallationDate: Installed on 2017-05-08 (67 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release i386 
(20161012.1)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-lowlatency 
root=UUID=5395e556-416c-40c3-a8ef-6790431337c1 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~beta3-4ubuntu2.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-26-lowlatency (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-06-16 (28 days ago)
  dmi.bios.date: 06/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41T-M LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  

[Kernel-packages] [Bug 1704469] [NEW] r8169 0000:02:00.0: invalid large VPD tag 7f at offset 0

[Cristian Aravena Romero]

Public bug reported:

dmesg:
[ 1025.813826] r8169 :02:00.0: invalid large VPD tag 7f at offset 0

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.11.0-10-generic 4.11.0-10.15
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   1801 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Jul 14 15:30:03 2017
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2017-07-05 (9 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.11.0-10-generic N/A
 linux-backports-modules-4.11.0-10-generic  N/A
 linux-firmware 1.167
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-07-05 (8 days ago)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug 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/1704469

Title:
  r8169 :02:00.0: invalid large VPD tag 7f at offset 0

Status in linux package in Ubuntu:
  New

Bug description:
  dmesg:
  [ 1025.813826] r8169 :02:00.0: invalid large VPD tag 7f at offset 0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1801 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Jul 14 15:30:03 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (9 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-07-05 (8 days ago)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1704470] Re: playback fails using alsa in mpd

[Kev Bowring]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704470/+attachment/4914826/+files/lspci-vnvn.log

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

Title:
  playback fails using alsa in mpd

Status in linux package in Ubuntu:
  New

Bug description:
  Using 4.11.0-10.15 kernel from playback fails using this mpd.conf

  ##Pulseaudio
  #audio_output {
  # type "pulse"
  # name "Local MPD"
  # server "127.0.0.1"
  #}

  ##Alsa
  audio_output {
  type "alsa"
   name "Cambridge Audio DAC100 USB 2 - USB Audio"
   device "hw:1,0"
   auto_resample "no"
   auto_format "no"
   auto_channels "no"
   replay_gain_handler "none"
   mixer_type "none"
  }

  If I reboot into 4.10.0-26 then playback with alsa works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wolf   1742 F pulseaudio
   /dev/snd/pcmC1D0p:   wolf   1742 F...m pulseaudio
   /dev/snd/controlC1:  wolf   1742 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Jul 14 20:27:17 2017
  HibernationDevice: RESUME=UUID=9f10a8f1-df29-4691-b2cc-7fbe68244587
  MachineType: NOVATECH LTD MBB-44608
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=c81d4267-4905-4511-9011-d51db8eb0c3a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

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

[Kernel-packages] [Bug 1704470] [NEW] playback fails using alsa in mpd

[Kev Bowring]

Public bug reported:

Using 4.11.0-10.15 kernel from playback fails using this mpd.conf

##Pulseaudio
#audio_output {
# type "pulse"
# name "Local MPD"
# server "127.0.0.1"
#}

##Alsa
audio_output {
type "alsa"
 name "Cambridge Audio DAC100 USB 2 - USB Audio"
 device "hw:1,0"
 auto_resample "no"
 auto_format "no"
 auto_channels "no"
 replay_gain_handler "none"
 mixer_type "none"
}

If I reboot into 4.10.0-26 then playback with alsa works.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.11.0-10-generic 4.11.0-10.15
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  wolf   1742 F pulseaudio
 /dev/snd/pcmC1D0p:   wolf   1742 F...m pulseaudio
 /dev/snd/controlC1:  wolf   1742 F pulseaudio
CurrentDesktop: XFCE
Date: Fri Jul 14 20:27:17 2017
HibernationDevice: RESUME=UUID=9f10a8f1-df29-4691-b2cc-7fbe68244587
MachineType: NOVATECH LTD MBB-44608
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=c81d4267-4905-4511-9011-d51db8eb0c3a ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.11.0-10-generic N/A
 linux-backports-modules-4.11.0-10-generic  N/A
 linux-firmware 1.167
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-DS2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: 7383241-001
dmi.chassis.type: 3
dmi.chassis.vendor: NOVATECH LTD
dmi.chassis.version: V1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
dmi.product.name: MBB-44608
dmi.product.version: V1.0
dmi.sys.vendor: NOVATECH LTD

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


** Tags: amd64 apport-bug artful

** Attachment added: "version.log"
   
https://bugs.launchpad.net/bugs/1704470/+attachment/4914809/+files/version.log

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

Title:
  playback fails using alsa in mpd

Status in linux package in Ubuntu:
  New

Bug description:
  Using 4.11.0-10.15 kernel from playback fails using this mpd.conf

  ##Pulseaudio
  #audio_output {
  # type "pulse"
  # name "Local MPD"
  # server "127.0.0.1"
  #}

  ##Alsa
  audio_output {
  type "alsa"
   name "Cambridge Audio DAC100 USB 2 - USB Audio"
   device "hw:1,0"
   auto_resample "no"
   auto_format "no"
   auto_channels "no"
   replay_gain_handler "none"
   mixer_type "none"
  }

  If I reboot into 4.10.0-26 then playback with alsa works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wolf   1742 F pulseaudio
   /dev/snd/pcmC1D0p:   wolf   1742 F...m pulseaudio
   /dev/snd/controlC1:  wolf   1742 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Jul 14 20:27:17 2017
  HibernationDevice: RESUME=UUID=9f10a8f1-df29-4691-b2cc-7fbe68244587
  MachineType: NOVATECH LTD MBB-44608
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=c81d4267-4905-4511-9011-d51db8eb0c3a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

-- 
Mailing list: 

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

[Joerg Schulz]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1704430/+attachment/4914790/+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/1704430

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuxm   2962 F pulseaudio
   /dev/snd/pcmC1D0p:   tuxm   2962 F...m pulseaudio
   /dev/snd/controlC1:  tuxm   2962 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-01-31 (163 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 8087:07da Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W840SU Series
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy lpadmin 
netdev plugdev root sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W840SU Series
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 

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

[Joerg Schulz]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1704430/+attachment/4914788/+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/1704430

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuxm   2962 F pulseaudio
   /dev/snd/pcmC1D0p:   tuxm   2962 F...m pulseaudio
   /dev/snd/controlC1:  tuxm   2962 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-01-31 (163 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 8087:07da Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W840SU Series
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy lpadmin 
netdev plugdev root sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W840SU Series
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 

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

[Joerg Schulz]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1704430/+attachment/4914787/+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/1704430

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuxm   2962 F pulseaudio
   /dev/snd/pcmC1D0p:   tuxm   2962 F...m pulseaudio
   /dev/snd/controlC1:  tuxm   2962 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-01-31 (163 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 8087:07da Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W840SU Series
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy lpadmin 
netdev plugdev root sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W840SU Series
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 

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

[Joerg Schulz]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1704430/+attachment/4914789/+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/1704430

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuxm   2962 F pulseaudio
   /dev/snd/pcmC1D0p:   tuxm   2962 F...m pulseaudio
   /dev/snd/controlC1:  tuxm   2962 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-01-31 (163 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 8087:07da Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W840SU Series
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy lpadmin 
netdev plugdev root sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W840SU Series
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 

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

[Joerg Schulz]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1704430/+attachment/4914783/+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/1704430

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuxm   2962 F pulseaudio
   /dev/snd/pcmC1D0p:   tuxm   2962 F...m pulseaudio
   /dev/snd/controlC1:  tuxm   2962 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-01-31 (163 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 8087:07da Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W840SU Series
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy lpadmin 
netdev plugdev root sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W840SU Series
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 

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

[Joerg Schulz]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1704430/+attachment/4914786/+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/1704430

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuxm   2962 F pulseaudio
   /dev/snd/pcmC1D0p:   tuxm   2962 F...m pulseaudio
   /dev/snd/controlC1:  tuxm   2962 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-01-31 (163 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 8087:07da Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W840SU Series
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy lpadmin 
netdev plugdev root sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W840SU Series
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 

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

[Joerg Schulz]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1704430/+attachment/4914785/+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/1704430

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuxm   2962 F pulseaudio
   /dev/snd/pcmC1D0p:   tuxm   2962 F...m pulseaudio
   /dev/snd/controlC1:  tuxm   2962 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-01-31 (163 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 8087:07da Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W840SU Series
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy lpadmin 
netdev plugdev root sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W840SU Series
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  

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

[Joerg Schulz]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1704430/+attachment/4914784/+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/1704430

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuxm   2962 F pulseaudio
   /dev/snd/pcmC1D0p:   tuxm   2962 F...m pulseaudio
   /dev/snd/controlC1:  tuxm   2962 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-01-31 (163 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 8087:07da Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W840SU Series
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy lpadmin 
netdev plugdev root sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W840SU Series
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 

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

[Joerg Schulz]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1704430/+attachment/4914782/+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/1704430

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuxm   2962 F pulseaudio
   /dev/snd/pcmC1D0p:   tuxm   2962 F...m pulseaudio
   /dev/snd/controlC1:  tuxm   2962 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-01-31 (163 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 8087:07da Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W840SU Series
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy lpadmin 
netdev plugdev root sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W840SU Series
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  

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

[Joerg Schulz]

apport information

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

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

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuxm   2962 F pulseaudio
   /dev/snd/pcmC1D0p:   tuxm   2962 F...m pulseaudio
   /dev/snd/controlC1:  tuxm   2962 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-01-31 (163 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 8087:07da Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W840SU Series
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy lpadmin 
netdev plugdev root sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W840SU Series
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 

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

[Joerg Schulz]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1704430/+attachment/4914781/+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/1704430

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuxm   2962 F pulseaudio
   /dev/snd/pcmC1D0p:   tuxm   2962 F...m pulseaudio
   /dev/snd/controlC1:  tuxm   2962 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-01-31 (163 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 8087:07da Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W840SU Series
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy lpadmin 
netdev plugdev root sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W840SU Series
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 

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

[Joerg Schulz]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1704430/+attachment/4914780/+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/1704430

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuxm   2962 F pulseaudio
   /dev/snd/pcmC1D0p:   tuxm   2962 F...m pulseaudio
   /dev/snd/controlC1:  tuxm   2962 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-01-31 (163 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 8087:07da Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W840SU Series
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy lpadmin 
netdev plugdev root sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W840SU Series
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 

[Kernel-packages] [Bug 1704430] Re: Middle mouse button lost function after Upgrade to Mint 18.2

[Joerg Schulz]

apport information

** Tags added: apport-collected sonya

** Description changed:

  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0
  
  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in the
  gnome-tweak-tool is has been enabled.
  
  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.
  
  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic
  
  Joerg
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  tuxm   2962 F pulseaudio
+  /dev/snd/pcmC1D0p:   tuxm   2962 F...m pulseaudio
+  /dev/snd/controlC1:  tuxm   2962 F pulseaudio
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux 18.2
+ InstallationDate: Installed on 2017-01-31 (163 days ago)
+ InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
+ Lsusb:
+  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 002 Device 002: ID 8087:07da Intel Corp. 
+  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Notebook W840SU Series
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.10.0-26-generic N/A
+  linux-backports-modules-4.10.0-26-generic  N/A
+  linux-firmware 1.157.11
+ Tags:  sonya
+ Uname: Linux 4.10.0-26-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy lpadmin 
netdev plugdev root sambashare scanner sudo tape video
+ _MarkForUpload: True
+ dmi.bios.date: 09/30/2013
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 4.6.5
+ dmi.board.asset.tag: Tag 12345
+ dmi.board.name: W840SU Series
+ dmi.board.vendor: Notebook
+ dmi.board.version: Not Applicable
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Notebook
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/30/2013:svnNotebook:pnW840SUSeries:pvrNotApplicable:rvnNotebook:rnW840SUSeries:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
+ dmi.product.name: W840SU Series
+ dmi.product.version: Not Applicable
+ dmi.sys.vendor: Notebook

** Attachment added: "AlsaInfo.txt"
   

[Kernel-packages] [Bug 1693345] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [khugepaged:38]

[FOFafik]

I have this problem during booting Ubuntu 17.04/XUbuntu 16.04.2 with new dell 
5580 Intel Kabylake + Nvidia 940MX, system never finish startup. Solution is 
here:
https://askubuntu.com/questions/875173/nmi-watchdog-bug-soft-lockup-cpu2-stuck-for-23s-plymouthd305
If system boot, it must set nouveau.modeset=0 ..., if boot with Nvidia 
proprietary, is it OK.

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [khugepaged:38]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The problem occurs in the _raw_spin_lock function.

  May be related to:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1689316

  ***
  *journalctl -b -1:*
  ***
  -- Logs begin at Mon 2017-05-08 08:54:15 IST, end at Thu 2017-05-25 01:31:26 
IST. --
  May 24 21:09:28 LiCL kernel: microcode: microcode updated early to revision 
0x1f, date = 2016-04-01
  May 24 21:09:28 LiCL kernel: Linux version 4.10.0-21-generic 
(buildd@lgw01-12) (gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) ) 
#23-Ubuntu
  May 24 21:09:28 LiCL kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=3fd29d97-25ad-421f-aed1-5261567fd0c1 r
  May 24 21:09:28 LiCL kernel: KERNEL supported cpus:
  May 24 21:09:28 LiCL kernel:   Intel GenuineIntel
  May 24 21:09:28 LiCL kernel:   AMD AuthenticAMD
  May 24 21:09:28 LiCL kernel:   Centaur CentaurHauls
  May 24 21:09:28 LiCL kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 
floating point registers'
  May 24 21:09:28 LiCL kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE 
registers'
  May 24 21:09:28 LiCL kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX 
registers'
  May 24 21:09:28 LiCL kernel: x86/fpu: xstate_offset[2]:  576, 
xstate_sizes[2]:  256
  May 24 21:09:28 LiCL kernel: x86/fpu: Enabled xstate features 0x7, context 
size is 832 bytes, using 'standard' format.
  May 24 21:09:28 LiCL kernel: e820: BIOS-provided physical RAM map:
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0x-0x00057fff] usable
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0x00058000-0x00058fff] reserved
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0x00059000-0x0009dfff] usable
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0x0009e000-0x0009] reserved
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0x0010-0xcafccfff] usable
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xcafcd000-0xcafd3fff] ACPI NVS
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xcafd4000-0xcb3fcfff] usable
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xcb3fd000-0xcb9f8fff] reserved
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xcb9f9000-0xda854fff] usable
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xda855000-0xdabc5fff] reserved
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xdabc6000-0xdabf4fff] ACPI data
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xdabf5000-0xdb570fff] ACPI NVS
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xdb571000-0xdbffefff] reserved
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xdbfff000-0xdbff] usable
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xdd00-0xdf1f] reserved
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xf800-0xfbff] reserved
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xfec0-0xfec00fff] reserved
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xfed0-0xfed03fff] reserved
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xfed1c000-0xfed1] reserved
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xfee0-0xfee00fff] reserved
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0xff00-0x] reserved
  May 24 21:09:28 LiCL kernel: BIOS-e820: [mem 
0x0001-0x00021fdf] usable
  May 24 21:09:28 LiCL kernel: NX (Execute Disable) protection: active
  May 24 21:09:28 LiCL kernel: efi: EFI v2.31 by American Megatrends
  ...skipping...
  May 25 01:28:23 LiCL kernel: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 
22s! [DOM Worker:3683]
  May 25 01:28:23 LiCL kernel: Modules linked in: ccm rfcomm bnep nls_iso8859_1 
hid_rmi joydev dell_wmi sparse_keymap intel_rapl x86_pkg_temp_therm
  May 25 01:28:23 LiCL kernel:  btrtl btbcm btintel bluetooth snd_seq 
snd_seq_device snd_timer snd lpc_ich mei_me soundcore mei shpchp snd_soc_sst_
  May 25 01:28:23 LiCL kernel:  wmi i2c_hid sdhci_acpi video hid sdhci fjes
  May 25 01:28:23 LiCL kernel: CPU: 2 PID: 3683 Comm: DOM Worker Tainted: G 
 D  L  4.10.0-21-generic #23-Ubuntu
  May 25 

[Kernel-packages] [Bug 1702521] Re: cxlflash update request in the Xenial SRU stream

[Frank Heimes]

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

Title:
  cxlflash update request in the Xenial SRU stream

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

Bug description:
  ---Problem Description---
  Request to update cxlflash in the Xenial SRU stream

  There are multiple patches in upstream that are of interest and would
  like to see them pulled into the Xenial SRU stream. I have listed the
  patches that are in upstream/master tree.

  41b99e1a30a6d04df7585905e5ffc7251099c6d3 scsi: cxlflash: Avoid mutex when 
destroying context
  44ef38f9a2af8644c24ace6cbe1132dc70174c39 scsi: cxlflash: Cache owning adapter 
within context
  888baf069f49529f33c0b1dfb0fc4811dc0ca1d2 scsi: cxlflash: Add kref to context
  cd34af40a09c678abad36304eb68e1774640e908 scsi: cxlflash: Transition to 
application close model
  de9f0b0cbb86da288a2d38e35f2953a85608a6aa scsi: cxlflash: Remove adapter file 
descriptor cache
  9442c9b0ed5c6f3a86dce0d6f714ef43f7f6cd53 scsi: cxlflash: Update documentation
  f80132613d576e7e705344d0c33f3b5e65d9e16a scsi: cxlflash: Refactor WWPN setup
  c4a11827b760ef8dcda26b5731d072b1d8fb7c81 scsi: cxlflash: Fix context 
reference tracking on detach
  68ab2d76e4be785a7003fdb42b7c4ed8bba56ae2 scsi: cxlflash: Set sg_tablesize to 
1 instead of SG_NONE
  8a2605430a64bdf0361af5a18043717a2c59972f scsi: cxlflash: Fix crash in 
cxlflash_restore_luntable()
  3d2f617d448f5e1d15d2844b803c13763ed51f1f scsi: cxlflash: Improve 
context_reset() logic
  11f7b1844ac01d0298aad6a0ec2591bef4a1c3a2 scsi: cxlflash: Avoid command room 
violation
  e7ab2d401dbf633eaafe5bd1f39e84492848668f scsi: cxlflash: Remove unused buffer 
from AFU command
  350bb478f57387df1e0b830fc64be2d1c3d55b6b scsi: cxlflash: Allocate memory 
instead of using command pool for AFU sync
  5fbb96c8f1ba89fb220efb7e4eeed7cb5112becd scsi: cxlflash: Use cmd_size for 
private commands
  25bced2b61b43b6372a73008dafa2183c5d53c39 scsi: cxlflash: Remove private 
command pool
  de01283baa334b1d938cfd9121198c517ad6dc89 scsi: cxlflash: Wait for active AFU 
commands to timeout upon tear down
  9ba848acbf4fbc6d99a0992df9ef5eb1b4842ba9 scsi: cxlflash: Remove AFU command 
lock
  d4ace35166e55e73afe72a05d166342996063d35 scsi: cxlflash: Cleanup send_tmf()
  9d89326c6660bc287b74983b51239460da10e189 scsi: cxlflash: Cleanup 
queuecommand()
  48b4be36edf8a2cb0dedcb2d28f598e51249e805 scsi: cxlflash: Migrate IOARRIN 
specific routines to function pointers
  fe7f96982a4e7103ffab45fba34c57ee19b62639 scsi: cxlflash: Migrate scsi command 
pointer to AFU command
  9c7d1ee5f13a7130f6d3df307ec010e9e003fa98 scsi: cxlflash: Refactor context 
reset to share reset logic
  696d0b0c715360ce28fedd3c8b009d3771a5ddeb scsi: cxlflash: Support SQ Command 
Mode
  fb67d44dfbdf85d984b9b40284e90636a3a7b21d scsi: cxlflash: Cleanup prints
  0df5bef739601f18bffc0d256ae451f239a826bd scsi: cxlflash: Cancel scheduled 
workers before stopping AFU
  943445200b049d5179b95297e5372d399c8ab0e2 scsi: cxlflash: Enable PCI device ID 
for future IBM CXL Flash AFU
  76a6ebbeef26b004c36a0c8ee0496bae5428fc31 scsi: cxlflash: Separate RRQ 
processing from the RRQ interrupt handler
  f918b4a8e6f8bb59c44045f85d10fd9cc7e5a4c0 scsi: cxlflash: Serialize RRQ access 
and support offlevel processing
  cba06e6de4038cd44a3e93a92ad982c372b8a14e scsi: cxlflash: Implement IRQ 
polling for RRQ processing
  3b225cd32a05b627a6ca366f364a824beaabecc5 scsi: cxlflash: Update sysfs helper 
routines to pass config structure
  78ae028e823701148e4915759459ee79597ea8ec scsi: cxlflash: Support dynamic 
number of FC ports
  8fa4f1770d56af6f0a5a862f1fd298a4eeea94f3 scsi: cxlflash: Remove port 
configuration assumptions
  0aa14887c60c27e3385295ee85f5ac079ae2ffb5 scsi: cxlflash: Hide FC internals 
behind common access routine
  565180723294b06b3e60030033847277b9d6d4bb scsi: cxlflash: SISlite updates to 
support 4 ports
  1cd7fabc82eb06c834956113ff287f8848811fb8 scsi: cxlflash: Support up to 4 ports
  323e33428ea23bfb1ae5010b18b4540048b2ad51 scsi: cxlflash: Fence EEH during 
probe
  50b787f7235efbd074bbdf4315e0cc261d85b4d7 scsi: cxlflash: Remove unnecessary 
DMA mapping
  cd41e18daf1a21fea5a195a5a74c97c6b183c15a scsi: cxlflash: Fix power-of-two 
validations
  fcc87e74a987dc9c0c85f53546df944ede76486a scsi: cxlflash: Fix warnings/errors
  e2ef33fa5958c51ebf0c6f18db19fe927e2185fa scsi: cxlflash: Improve asynchronous 
interrupt processing
  bfc0bab172cabf3bb25c48c4c521b317ff4a909d scsi: cxlflash: Support multiple 
hardware queues
  3065267a80c88d775e8eb34196280e8eee33322f scsi: cxlflash: Add hardware queues 
attribute
  1dd0c0e4fd02dc5e5bfaf89bd4656aabe4ae3cb3 scsi: cxlflash: Introduce hardware 
queue steering
   

  
  The patches are required on 

[Kernel-packages] [Bug 1704430] Re: Middle mouse button lost function after Upgrade to Mint 18.2

[Joerg Schulz]

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

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

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg

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

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

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

[Marek]

had somebody tryed sound with kernel 4.12 ??

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

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

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

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

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions

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

[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug

[Joseph Salisbury]

The purpose of testing v4.12-rc7 is to narrow down that last kernel
version that had the hang bug(The bad kernel) and the first kernel
version that did not(The good kernel).  This will allow us to identify
the exact commit that fixes the hang bug.  This can be accomplished by
performing a "Reverse" bisect[0].  Once we know the commit that fixes
the bug, we can SRU it to all the previous Ubuntu releases.


Are you not able to test for the hang bug without compiling the DKMS-OpenAFS 
packages?  If so, did they compile okay when you tested v4.12-rc8?


[0] https://wiki.ubuntu.com/Kernel/KernelBisection

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  

[Kernel-packages] [Bug 1704430] Re: Middle mouse button lost function after Upgrade to Mint 18.2

[Joerg Schulz]

** Attachment added: "get info about mouse porps via xinput command"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704430/+attachment/4914742/+files/xinput.log

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

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg

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

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

[Kernel-packages] [Bug 1704430] Re: Middle mouse button lost function after Upgrade to Mint 18.2

[Joerg Schulz]

added xinput.log (getting info about mouse porperties) and system.log with some 
information
what Linux I'am running.

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

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg

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

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

[Kernel-packages] [Bug 1704374] Re: system randomly hangs itself

[morris]

Ok I've just installed 4.12.1 kernel that's one of the report after
kernel installation

sudo dpkg -i 
linux-image-4.12.1-041201-generic_4.12.1-041201.201707121132_amd64.deb
Selezionato il pacchetto linux-image-4.12.1-041201-generic non precedentemente 
selezionato.
(Lettura del database... 238426 file e directory attualmente installati.)
Preparativi per estrarre 
linux-image-4.12.1-041201-generic_4.12.1-041201.201707121132_amd64.deb...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 
4.12.1-041201-generic /boot/vmlinuz-4.12.1-041201-generic
Done.
Estrazione di linux-image-4.12.1-041201-generic (4.12.1-041201.201707121132)...
Configurazione di linux-image-4.12.1-041201-generic 
(4.12.1-041201.201707121132)...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.12.1-041201-generic /boot/vmlinuz-4.12.1-041201-generic   
  
run-parts: executing /etc/kernel/postinst.d/dkms 4.12.1-041201-generic 
/boot/vmlinuz-4.12.1-041201-generic 
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
4.12.1-041201-generic /boot/vmlinuz-4.12.1-041201-generic   
   
update-initramfs: Generating /boot/initrd.img-4.12.1-041201-generic 
   
W: Possible missing firmware /lib/firmware/nvidia/gm20b/pmu/sig.bin for module 
nouveau 
W: Possible missing firmware /lib/firmware/nvidia/gm20b/pmu/image.bin for 
module nouveau   
W: Possible missing firmware /lib/firmware/nvidia/gm20b/pmu/desc.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/sig.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/image.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/desc.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/nvdec/scrubber.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_method_init.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_bundle_init.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_nonctx.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_ctx.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_data.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_inst.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_bl.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_data.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_inst.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_bl.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/ucode_unload.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/ucode_load.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/unload_bl.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/bl.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/sig.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/image.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/desc.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/nvdec/scrubber.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_method_init.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_bundle_init.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_nonctx.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_ctx.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_data.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_inst.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_bl.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/fecs_sig.bin 

[Kernel-packages] [Bug 1704430] Re: Middle mouse button lost function after Upgrade to Mint 18.2

[Joerg Schulz]

** Attachment added: "basic infos about my Linux"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704430/+attachment/4914743/+files/system.log

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

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg

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

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

[Kernel-packages] [Bug 1704435] [NEW] [Xenial] nvme: Quirks for PM1725 controllers

[Leann Ogasawara]

Public bug reported:

== SRU Xenial ==
Pick up the following device quirk to resolve a hardware/firmware bug affectung 
some NVMe drives that use the PM1725 controller. Under adverse circumstances 
the bug can result in data corruption and loss. 

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d554b5e1ca64d23e4f839e6531490fee8479fbaf

nvme: Quirks for PM1725 controllers
PM1725 controllers have a couple of quirks that need to be handled in
the driver:

 - I/O queue depth must be limited to 64 entries on controllers that do
   not report MQES.

 - The host interface registers go offline briefly while resetting the
   chip. Thus a delay is needed before checking whether the controller
   is ready.

Note that the admin queue depth is also limited to 64 on older versions
of this board. Since our NVME_AQ_DEPTH is now 32 that is no longer an
issue.

Signed-off-by: Martin K. Petersen 
Signed-off-by: Sagi Grimberg 

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Triaged

** Affects: linux (Ubuntu Xenial)
 Importance: Critical
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Triaged

** Affects: linux (Ubuntu Yakkety)
 Importance: Critical
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Triaged

** Affects: linux (Ubuntu Zesty)
 Importance: Critical
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Triaged

** Affects: linux (Ubuntu Artful)
 Importance: Critical
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Triaged

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  [Xenial] nvme: Quirks for PM1725 controllers

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  == SRU Xenial ==
  Pick up the following device quirk to resolve a hardware/firmware bug 
affectung some NVMe drives that use the PM1725 controller. Under adverse 
circumstances the bug can result in data corruption and loss. 

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d554b5e1ca64d23e4f839e6531490fee8479fbaf

  nvme: Quirks for PM1725 controllers
  PM1725 controllers have a couple of quirks that need to be handled in
  the driver:

   - I/O queue depth must be limited to 64 entries on controllers that do
 not report MQES.

   - The host interface registers go offline briefly while resetting the
 chip. Thus a delay is needed before checking whether the controller
 is ready.

  Note that the admin queue depth is also limited to 64 on older versions
  of this board. Since our NVME_AQ_DEPTH is now 32 that is no longer an
  issue.

  Signed-off-by: Martin K. Petersen 
  Signed-off-by: Sagi Grimberg 

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

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

[Kernel-packages] [Bug 1704430] 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 1704430

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

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

  The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in
  the gnome-tweak-tool is has been enabled.

  After setting this property to "1" with
>> xinput --set-prop 12 399 1
  my middle mouse button is working as expected.

  May be worth to mention:
  I'am running the following kernel:
  >> uname -r
  4.10.0-26-generic

  Joerg

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

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

[Kernel-packages] [Bug 1704430] [NEW] Middle mouse button lost function after Upgrade to Mint 18.2

[Joerg Schulz]

Public bug reported:

It looks an old bug report (#1581088) is back. 
I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
"Logitech M557"
Searching for root cause I found this bug report #1581088.
Following resolution attemps I could figure the same root cause and solution.
After upgrade :
>> xinput list-props 12
Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev Wheel Emulation Button (403): 4
Evdev Drag Lock Buttons (404):  0

The porperty 399 (Evdev Wheel Emulation) was set to  "0", even in in the
gnome-tweak-tool is has been enabled.

After setting this property to "1" with
  >> xinput --set-prop 12 399 1
my middle mouse button is working as expected.

May be worth to mention:
I'am running the following kernel:
>> uname -r
4.10.0-26-generic

Joerg

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

Title:
  Middle mouse button lost function after Upgrade to Mint 18.2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It looks an old bug report (#1581088) is back. 
  I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a 
Bluetooth Mouse
  "Logitech M557"
  Searching for root cause I found this bug report #1581088.
  Following resolution attemps I could figure the same root cause and solution.
  After upgrade :
  >> xinput list-props 12
  Device 'Bluetooth Mouse M557':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (264): 0
Device Accel Constant Deceleration (265):   1.00
Device Accel Adaptive Deceleration (266):   1.00
Device Accel Velocity Scaling (267):10.00
Device Product ID (259):1133, 45072
Device Node (260):  "/dev/input/event12"
Evdev Axis Inversion (387): 0, 0
Evdev Axes Swap (389):  0
Axis Labels (390):  "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" 
(385), "Rel Vert Wheel" (386)
Button Labels (391):"Button Left" (141), "Button Middle" (142), 
"Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), 
"Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button 
Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), 
"Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button 
Unknown" (379), "Button Unknown" (379)
Evdev Scrolling Distance (392): 1, 1, 1
Evdev Middle Button Emulation (393):1
Evdev Middle Button Timeout (394):  50
Evdev Third Button Emulation (395): 0
Evdev Third Button Emulation Timeout (396): 1000
Evdev Third Button Emulation Button (397):  3
Evdev Third Button Emulation Threshold (398):   20
Evdev Wheel Emulation (399):1
Evdev Wheel Emulation Axes (400):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (401):10
Evdev Wheel Emulation Timeout (402):200
Evdev 

[Kernel-packages] [Bug 1702521] Re: cxlflash update request in the Xenial SRU stream

[bugproxy]

** Tags added: bugnameltc-154010 severity-high

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

Title:
  cxlflash update request in the Xenial SRU stream

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

Bug description:
  ---Problem Description---
  Request to update cxlflash in the Xenial SRU stream

  There are multiple patches in upstream that are of interest and would
  like to see them pulled into the Xenial SRU stream. I have listed the
  patches that are in upstream/master tree.

  41b99e1a30a6d04df7585905e5ffc7251099c6d3 scsi: cxlflash: Avoid mutex when 
destroying context
  44ef38f9a2af8644c24ace6cbe1132dc70174c39 scsi: cxlflash: Cache owning adapter 
within context
  888baf069f49529f33c0b1dfb0fc4811dc0ca1d2 scsi: cxlflash: Add kref to context
  cd34af40a09c678abad36304eb68e1774640e908 scsi: cxlflash: Transition to 
application close model
  de9f0b0cbb86da288a2d38e35f2953a85608a6aa scsi: cxlflash: Remove adapter file 
descriptor cache
  9442c9b0ed5c6f3a86dce0d6f714ef43f7f6cd53 scsi: cxlflash: Update documentation
  f80132613d576e7e705344d0c33f3b5e65d9e16a scsi: cxlflash: Refactor WWPN setup
  c4a11827b760ef8dcda26b5731d072b1d8fb7c81 scsi: cxlflash: Fix context 
reference tracking on detach
  68ab2d76e4be785a7003fdb42b7c4ed8bba56ae2 scsi: cxlflash: Set sg_tablesize to 
1 instead of SG_NONE
  8a2605430a64bdf0361af5a18043717a2c59972f scsi: cxlflash: Fix crash in 
cxlflash_restore_luntable()
  3d2f617d448f5e1d15d2844b803c13763ed51f1f scsi: cxlflash: Improve 
context_reset() logic
  11f7b1844ac01d0298aad6a0ec2591bef4a1c3a2 scsi: cxlflash: Avoid command room 
violation
  e7ab2d401dbf633eaafe5bd1f39e84492848668f scsi: cxlflash: Remove unused buffer 
from AFU command
  350bb478f57387df1e0b830fc64be2d1c3d55b6b scsi: cxlflash: Allocate memory 
instead of using command pool for AFU sync
  5fbb96c8f1ba89fb220efb7e4eeed7cb5112becd scsi: cxlflash: Use cmd_size for 
private commands
  25bced2b61b43b6372a73008dafa2183c5d53c39 scsi: cxlflash: Remove private 
command pool
  de01283baa334b1d938cfd9121198c517ad6dc89 scsi: cxlflash: Wait for active AFU 
commands to timeout upon tear down
  9ba848acbf4fbc6d99a0992df9ef5eb1b4842ba9 scsi: cxlflash: Remove AFU command 
lock
  d4ace35166e55e73afe72a05d166342996063d35 scsi: cxlflash: Cleanup send_tmf()
  9d89326c6660bc287b74983b51239460da10e189 scsi: cxlflash: Cleanup 
queuecommand()
  48b4be36edf8a2cb0dedcb2d28f598e51249e805 scsi: cxlflash: Migrate IOARRIN 
specific routines to function pointers
  fe7f96982a4e7103ffab45fba34c57ee19b62639 scsi: cxlflash: Migrate scsi command 
pointer to AFU command
  9c7d1ee5f13a7130f6d3df307ec010e9e003fa98 scsi: cxlflash: Refactor context 
reset to share reset logic
  696d0b0c715360ce28fedd3c8b009d3771a5ddeb scsi: cxlflash: Support SQ Command 
Mode
  fb67d44dfbdf85d984b9b40284e90636a3a7b21d scsi: cxlflash: Cleanup prints
  0df5bef739601f18bffc0d256ae451f239a826bd scsi: cxlflash: Cancel scheduled 
workers before stopping AFU
  943445200b049d5179b95297e5372d399c8ab0e2 scsi: cxlflash: Enable PCI device ID 
for future IBM CXL Flash AFU
  76a6ebbeef26b004c36a0c8ee0496bae5428fc31 scsi: cxlflash: Separate RRQ 
processing from the RRQ interrupt handler
  f918b4a8e6f8bb59c44045f85d10fd9cc7e5a4c0 scsi: cxlflash: Serialize RRQ access 
and support offlevel processing
  cba06e6de4038cd44a3e93a92ad982c372b8a14e scsi: cxlflash: Implement IRQ 
polling for RRQ processing
  3b225cd32a05b627a6ca366f364a824beaabecc5 scsi: cxlflash: Update sysfs helper 
routines to pass config structure
  78ae028e823701148e4915759459ee79597ea8ec scsi: cxlflash: Support dynamic 
number of FC ports
  8fa4f1770d56af6f0a5a862f1fd298a4eeea94f3 scsi: cxlflash: Remove port 
configuration assumptions
  0aa14887c60c27e3385295ee85f5ac079ae2ffb5 scsi: cxlflash: Hide FC internals 
behind common access routine
  565180723294b06b3e60030033847277b9d6d4bb scsi: cxlflash: SISlite updates to 
support 4 ports
  1cd7fabc82eb06c834956113ff287f8848811fb8 scsi: cxlflash: Support up to 4 ports
  323e33428ea23bfb1ae5010b18b4540048b2ad51 scsi: cxlflash: Fence EEH during 
probe
  50b787f7235efbd074bbdf4315e0cc261d85b4d7 scsi: cxlflash: Remove unnecessary 
DMA mapping
  cd41e18daf1a21fea5a195a5a74c97c6b183c15a scsi: cxlflash: Fix power-of-two 
validations
  fcc87e74a987dc9c0c85f53546df944ede76486a scsi: cxlflash: Fix warnings/errors
  e2ef33fa5958c51ebf0c6f18db19fe927e2185fa scsi: cxlflash: Improve asynchronous 
interrupt processing
  bfc0bab172cabf3bb25c48c4c521b317ff4a909d scsi: cxlflash: Support multiple 
hardware queues
  3065267a80c88d775e8eb34196280e8eee33322f scsi: cxlflash: Add hardware queues 
attribute
  1dd0c0e4fd02dc5e5bfaf89bd4656aabe4ae3cb3 scsi: cxlflash: Introduce hardware 
queue steering
   

  
  The patches are required on 16.04.3 HWE v4.10 kernel.

  I also have 

[Kernel-packages] [Bug 1703944] Re: ethtool - "vmalloc: allocation failure: 0 bytes" message

[Eric Desrochers]

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

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

Title:
  ethtool - "vmalloc: allocation failure: 0 bytes" message

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Won't Fix

Bug description:
  If ->get_regs_len() callback return 0, we allocate 0 bytes of memory,
  what print the following warning in kern.log :

  vmalloc: allocation failure: 0 bytes
  ethtool: page allocation failure: order:0, mode:0x24080c2
  CPU: 21 PID: 7668 Comm: ethtool Tainted: G 4.4.0-62-generic #83-Ubuntu
  Hardware name:
  0286 5949f325 8801fddcfba8 813f7c63
  024080c2 81ccfe30 8801fddcfc38 8119498a
  81ccfe30 8801fddcfbc8 0018 8801fddcfc48
  Call Trace:
  [] dump_stack+0x63/0x90
  [] warn_alloc_failed+0xfa/0x150
  [] __vmalloc_node_range+0x202/0x290
  [] ? _raw_spin_unlock_bh+0x1e/0x20
  [] vzalloc+0x54/0x60
  [] ? dev_ethtool+0xfc7/0x1ef0
  [] dev_ethtool+0xfc7/0x1ef0
  [] dev_ioctl+0x182/0x580
  [] sock_do_ioctl+0x42/0x50
  [] sock_ioctl+0x1d2/0x290
  [] do_vfs_ioctl+0x29f/0x490
  [] ? __do_page_fault+0x1b4/0x400
  [] SyS_ioctl+0x79/0x90
  [] entry_SYSCALL_64_fastpath+0x16/0x71

  break-fix: - 3808d34838184fd29088d6b3a364ba2f1c018fb6

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

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

[Kernel-packages] [Bug 1701697] Re: sock_recvmsg has dropped size argument

[Thadeu Lima de Souza Cascardo]

iscsitarget, 1.4.20.3+svn499, 4.4.0-21-generic, x86_64: installed
iscsitarget, 1.4.20.3+svn499, 4.4.0-79-generic, x86_64: installed
iscsitarget, 1.4.20.3+svn499, 4.4.0-83-lowlatency, x86_64: installed
iscsitarget, 1.4.20.3+svn499, 4.4.0-86-generic, x86_64: installed


iscsitarget, 1.4.20.3+svn502, 4.4.0-21-generic, x86_64: installed
iscsitarget, 1.4.20.3+svn502, 4.4.0-79-generic, x86_64: installed
iscsitarget, 1.4.20.3+svn502, 4.4.0-83-generic, x86_64: installed
iscsitarget, 1.4.20.3+svn502, 4.4.0-86-generic, x86_64: installed


** Tags removed: verification-needed-trusty verification-needed-xenial
** Tags added: verification-done-trusty verification-done-xenial

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

Title:
  sock_recvmsg has dropped size argument

Status in iscsitarget package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in iscsitarget source package in Trusty:
  Fix Committed
Status in iscsitarget source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  In linux-4.4.0-84, we backported commit
  2da62906b1e298695e1bb725927041cd59942c98 ("[net] drop 'size' argument
  of sock_recvmsg()"), which breaks building iscsitarget.

  Cascardo.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: User Name 4.4.0-79.100-generic 4.4.67
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-79-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  modified.conffile..etc.iet.ietd.conf: [inaccessible: [Errno 13] Permission 
denied: u'/etc/iet/ietd.conf']

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

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

[Kernel-packages] [Bug 1701697] Re: sock_recvmsg has dropped size argument

[Thadeu Lima de Souza Cascardo]

Added -proposed, did an upgrade and further dkms install and iscsitarget
dkms was installed with success on all those kernels.

iscsitarget-dkms was upgraded when doing the linux-generic and linux-
generic-lts-xenial upgrades, or whenever installing the linux-
headers-4.4.0-86-{generic,lowlatency} packages.

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

Title:
  sock_recvmsg has dropped size argument

Status in iscsitarget package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in iscsitarget source package in Trusty:
  Fix Committed
Status in iscsitarget source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  In linux-4.4.0-84, we backported commit
  2da62906b1e298695e1bb725927041cd59942c98 ("[net] drop 'size' argument
  of sock_recvmsg()"), which breaks building iscsitarget.

  Cascardo.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: User Name 4.4.0-79.100-generic 4.4.67
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-79-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  modified.conffile..etc.iet.ietd.conf: [inaccessible: [Errno 13] Permission 
denied: u'/etc/iet/ietd.conf']

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

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

[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

[F. H.]

I attached parts of the requested dmesg to this comment.

Is this enough information? I'm a little bit afraid of posting my full dmesg, 
due to privacy...
(Maybe someone could tell me, how I can automatically censor MAC addresses / 
other sensitive information..?)

** Attachment added: "dmesg |grep -i "i2c""
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700657/+attachment/4914705/+files/dmesg_grepped.log

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 263140] Re: Hardy/Intrepid/Jaunty boot hangs with the message: "ACPI: EC: non-query interrupt received, switching to interrupt mode"

[Sid Lori]

Bug still present on Ubuntu 16.04 LTS, running on an HP Elitebook 850
G2.  Ubuntu is installed on an SSD, and I noticed that there were long
delays that the hard drive light wasn't active.  A check of dmesg showed
two ~6 second delays in the boot process, both on the same problem:

...SNIP...
[0.141122] ACPI: bus type PCI registered
[0.141123] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[0.141183] PCI: MMCONFIG for domain  [bus 00-ff] at [mem 
0xe000-0xefff] (base 0xe000)
[0.141184] PCI: not using MMCONFIG
[0.141185] PCI: Using configuration type 1 for base access
[0.157183] HugeTLB registered 1 GB page size, pre-allocated 0 pages
[0.157184] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[0.157406] ACPI: Added _OSI(Module Device)
[0.157406] ACPI: Added _OSI(Processor Device)
[0.157407] ACPI: Added _OSI(3.0 _SCP Extensions)
[0.157408] ACPI: Added _OSI(Processor Aggregator Device)
[0.164672] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[0.169886] ACPI: Dynamic OEM Table Load:
[0.169894] ACPI: SSDT 0xA08A05621000 0003F3 (v02 PmRef  Cpu0Cst  
3001 INTL 20130927)
[0.170667] ACPI: Dynamic OEM Table Load:
[0.170674] ACPI: SSDT 0xA08A055F8800 0005DB (v02 PmRef  ApIst
3000 INTL 20130927)
[0.171490] ACPI: Dynamic OEM Table Load:
[0.171495] ACPI: SSDT 0xA08A0568AA00 000119 (v02 PmRef  ApCst
3000 INTL 20130927)
[0.172854] ACPI : EC: EC started
[6.094429] ACPI: Interpreter enabled
[6.094459] ACPI: (supports S0 S3 S4 S5)
[6.094460] ACPI: Using IOAPIC for interrupt routing
[6.094480] PCI: MMCONFIG for domain  [bus 00-ff] at [mem 
0xe000-0xefff] (base 0xe000)
[6.094904] PCI: MMCONFIG at [mem 0xe000-0xefff] reserved in ACPI 
motherboard resources
[6.094917] PCI: Using host bridge windows from ACPI; if necessary, use 
"pci=nocrs" and report a bug
[6.096366] ACPI: Power Resource [APPR] (off)
[6.098669] ACPI: Power Resource [COMP] (on)
[6.098863] ACPI: Power Resource [LPP] (on)
[6.099525] ACPI: Power Resource [PXP2] (on)
[6.218841] ACPI: Power Resource [WRST] (on)
[6.221957] ACPI: PCI Root Bridge [PCI0] (domain  [bus 00-fe])
[6.221962] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM 
Segments MSI]
[6.223644] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER 
PCIeCapability]
[6.223645] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS 
configuration
[6.224136] PCI host bridge to bus :00
[6.224138] pci_bus :00: root bus resource [io  0x-0x0cf7 window]
[6.224139] pci_bus :00: root bus resource [io  0x0d00-0x window]
[6.224140] pci_bus :00: root bus resource [mem 0x000a-0x000b 
window]
[6.224141] pci_bus :00: root bus resource [mem 0xae80-0xdfff 
window]
[6.224144] pci_bus :00: root bus resource [mem 0xf000-0xfed3 
window]
[6.224145] pci_bus :00: root bus resource [mem 0xfed45000-0xfedf 
window]
[6.224146] pci_bus :00: root bus resource [mem 0xfee01000-0x 
window]
[6.224148] pci_bus :00: root bus resource [bus 00-fe]
[6.224155] pci :00:00.0: [8086:1604] type 00 class 0x06
[6.224278] pci :00:02.0: [8086:1616] type 00 class 0x03
[6.224288] pci :00:02.0: reg 0x10: [mem 0xc000-0xc0ff 64bit]
[6.224294] pci :00:02.0: reg 0x18: [mem 0xb000-0xbfff 64bit 
pref]
[6.224298] pci :00:02.0: reg 0x20: [io  0x5000-0x503f]
[6.224429] pci :00:03.0: [8086:160c] type 00 class 0x040300
[6.224436] pci :00:03.0: reg 0x10: [mem 0xc133-0xc1333fff 64bit]
[6.224571] pci :00:14.0: [8086:9cb1] type 00 class 0x0c0330
[6.224584] pci :00:14.0: reg 0x10: [mem 0xc132-0xc132 64bit]
[6.224636] pci :00:14.0: PME# supported from D3hot D3cold
[6.224702] pci :00:14.0: System wakeup disabled by ACPI
[6.224739] pci :00:16.0: [8086:9cba] type 00 class 0x078000
[6.224756] pci :00:16.0: reg 0x10: [mem 0xc133b000-0xc133b01f 64bit]
[6.224828] pci :00:16.0: PME# supported from D0 D3hot D3cold
[6.224931] pci :00:19.0: [8086:15a2] type 00 class 0x02
[6.224944] pci :00:19.0: reg 0x10: [mem 0xc130-0xc131]
[6.224951] pci :00:19.0: reg 0x14: [mem 0xc133d000-0xc133dfff]
[6.224958] pci :00:19.0: reg 0x18: [io  0x5080-0x509f]
[6.225017] pci :00:19.0: PME# supported from D0 D3hot D3cold
[6.225083] pci :00:19.0: System wakeup disabled by ACPI
[6.225117] pci :00:1b.0: [8086:9ca0] type 00 class 0x040300
[6.225131] pci :00:1b.0: reg 0x10: [mem 0xc1334000-0xc1337fff 64bit]
[6.225182] pci :00:1b.0: PME# supported from D0 D3hot D3cold
[6.225279] pci :00:1c.0: [8086:9c90] type 01 class 0x060400
[6.225345] pci :00:1c.0: PME# supported from D0 D3hot D3cold
[   

[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS

[Thadeu Lima de Souza Cascardo]

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

Title:
  Ath10k to read different board data file if specify in SMBIOS

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

Bug description:
  Board Data File (BDF) is loaded upon driver boot-up procedure. The right
  board data file is identified, among others, by device and sybsystem ids.

  The problem, however, can occur when the (default) board data file cannot
  fulfill with the vendor requirements and it is necessary to use a different
  board data file.

  To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name
  Extension to specify the extension/variant name. The driver will take the
  extension suffix into consideration and will load the right (non-default)
  board data file if necessary.

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

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

[Kernel-packages] [Bug 1701316] Re: Data corruption with hio driver

[Thadeu Lima de Souza Cascardo]

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

Title:
  Data corruption with hio driver

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Impact: Data corruption is seen when using the hio driver with 4.10
  and later kernels.

  Fix: Patch to fix incorrect use of enumerated values as bitmasks.

  Test case: See below.

  Regression potential: Very low. Changes are simple and Obviously
  Correct (TM), and they only affect the hio driver.

  ---

  We are seeing data corruption issues using the hio driver with kernel
  4.10.0

  # uname -a
  Linux arbok 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  Making xfs fails:

  root@arbok:~# mkfs.xfs /dev/hioa
  meta-data=/dev/hioa  isize=512agcount=4, agsize=48835584 blks
   =   sectsz=512   attr=2, projid32bit=1
   =   crc=1finobt=1, sparse=0
  data =   bsize=4096   blocks=195342336, imaxpct=25
   =   sunit=0  swidth=0 blks
  naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
  log  =internal log   bsize=4096   blocks=95382, version=2
   =   sectsz=512   sunit=0 blks, lazy-count=1
  realtime =none   extsz=4096   blocks=0, rtextents=0
  bad magic number
  bad magic number
  Metadata corruption detected at xfs_sb block 0x0/0x200
  libxfs_writebufr: write verifer failed on xfs_sb bno 0x0/0x200

  The drive appears to be healthy. Firmware has been upgraded to ver
  656:

  root@arbok:~# hio_info -d /dev/hioa
  hioaSerial number:  022XWV10G2000325
  Size(GB):   800
  Max size(GB):   800
  Hardware version:   1.0
  Firmware version:   656
  Driver version: 2.1.0.28
  Work mode:  MLC
  Run time (sec.):8910490
  Total  read(MB):8499
  Total write(MB):0
  Lifetime remaining: 99.844%
  Max bad block rate: 0.167%
  Health: OK
  Comment:NA

  No relevant entries about read/write errors in dmesg

  Also just copying 8G random data and reading those back gives a hash mismatch:
  root@arbok:~# dd if=/dev/urandom of=test.dat bs=1G count=8 iflag=fullblock
  8+0 records in
  8+0 records out
  8589934592 bytes (8.6 GB, 8.0 GiB) copied, 85.6076 s, 100 MB/s
  root@arbok:~# dd if=test.dat of=/dev/hioa bs=1G count=8 iflag=fullblock
  8+0 records in
  8+0 records out
  8589934592 bytes (8.6 GB, 8.0 GiB) copied, 10.6034 s, 810 MB/s
  root@arbok:~# dd if=/dev/hioa of=read-back.dat bs=1G count=8 iflag=fullblock
  sha256sum test.dat read-
  8+0 records in
  8+0 records out
  8589934592 bytes (8.6 GB, 8.0 GiB) copied, 66.1872 s, 130 MB/s
  root@arbok:~# sha256sum test.dat read-back.dat
  6376d245a07c42c990589a3c17c44e63d826d1cb583fc5a065deff9dae69fd3a  test.dat
  ebfb4ef19ae410f190327b5ebd312711263bc7579970e87d9c1e2d84e06b3c25  
read-back.dat

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

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

[Kernel-packages] [Bug 1702521] Re: cxlflash update request in the Xenial SRU stream

[Frank Heimes]

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

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

Title:
  cxlflash update request in the Xenial SRU stream

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

Bug description:
  ---Problem Description---
  Request to update cxlflash in the Xenial SRU stream

  There are multiple patches in upstream that are of interest and would
  like to see them pulled into the Xenial SRU stream. I have listed the
  patches that are in upstream/master tree.

  41b99e1a30a6d04df7585905e5ffc7251099c6d3 scsi: cxlflash: Avoid mutex when 
destroying context
  44ef38f9a2af8644c24ace6cbe1132dc70174c39 scsi: cxlflash: Cache owning adapter 
within context
  888baf069f49529f33c0b1dfb0fc4811dc0ca1d2 scsi: cxlflash: Add kref to context
  cd34af40a09c678abad36304eb68e1774640e908 scsi: cxlflash: Transition to 
application close model
  de9f0b0cbb86da288a2d38e35f2953a85608a6aa scsi: cxlflash: Remove adapter file 
descriptor cache
  9442c9b0ed5c6f3a86dce0d6f714ef43f7f6cd53 scsi: cxlflash: Update documentation
  f80132613d576e7e705344d0c33f3b5e65d9e16a scsi: cxlflash: Refactor WWPN setup
  c4a11827b760ef8dcda26b5731d072b1d8fb7c81 scsi: cxlflash: Fix context 
reference tracking on detach
  68ab2d76e4be785a7003fdb42b7c4ed8bba56ae2 scsi: cxlflash: Set sg_tablesize to 
1 instead of SG_NONE
  8a2605430a64bdf0361af5a18043717a2c59972f scsi: cxlflash: Fix crash in 
cxlflash_restore_luntable()
  3d2f617d448f5e1d15d2844b803c13763ed51f1f scsi: cxlflash: Improve 
context_reset() logic
  11f7b1844ac01d0298aad6a0ec2591bef4a1c3a2 scsi: cxlflash: Avoid command room 
violation
  e7ab2d401dbf633eaafe5bd1f39e84492848668f scsi: cxlflash: Remove unused buffer 
from AFU command
  350bb478f57387df1e0b830fc64be2d1c3d55b6b scsi: cxlflash: Allocate memory 
instead of using command pool for AFU sync
  5fbb96c8f1ba89fb220efb7e4eeed7cb5112becd scsi: cxlflash: Use cmd_size for 
private commands
  25bced2b61b43b6372a73008dafa2183c5d53c39 scsi: cxlflash: Remove private 
command pool
  de01283baa334b1d938cfd9121198c517ad6dc89 scsi: cxlflash: Wait for active AFU 
commands to timeout upon tear down
  9ba848acbf4fbc6d99a0992df9ef5eb1b4842ba9 scsi: cxlflash: Remove AFU command 
lock
  d4ace35166e55e73afe72a05d166342996063d35 scsi: cxlflash: Cleanup send_tmf()
  9d89326c6660bc287b74983b51239460da10e189 scsi: cxlflash: Cleanup 
queuecommand()
  48b4be36edf8a2cb0dedcb2d28f598e51249e805 scsi: cxlflash: Migrate IOARRIN 
specific routines to function pointers
  fe7f96982a4e7103ffab45fba34c57ee19b62639 scsi: cxlflash: Migrate scsi command 
pointer to AFU command
  9c7d1ee5f13a7130f6d3df307ec010e9e003fa98 scsi: cxlflash: Refactor context 
reset to share reset logic
  696d0b0c715360ce28fedd3c8b009d3771a5ddeb scsi: cxlflash: Support SQ Command 
Mode
  fb67d44dfbdf85d984b9b40284e90636a3a7b21d scsi: cxlflash: Cleanup prints
  0df5bef739601f18bffc0d256ae451f239a826bd scsi: cxlflash: Cancel scheduled 
workers before stopping AFU
  943445200b049d5179b95297e5372d399c8ab0e2 scsi: cxlflash: Enable PCI device ID 
for future IBM CXL Flash AFU
  76a6ebbeef26b004c36a0c8ee0496bae5428fc31 scsi: cxlflash: Separate RRQ 
processing from the RRQ interrupt handler
  f918b4a8e6f8bb59c44045f85d10fd9cc7e5a4c0 scsi: cxlflash: Serialize RRQ access 
and support offlevel processing
  cba06e6de4038cd44a3e93a92ad982c372b8a14e scsi: cxlflash: Implement IRQ 
polling for RRQ processing
  3b225cd32a05b627a6ca366f364a824beaabecc5 scsi: cxlflash: Update sysfs helper 
routines to pass config structure
  78ae028e823701148e4915759459ee79597ea8ec scsi: cxlflash: Support dynamic 
number of FC ports
  8fa4f1770d56af6f0a5a862f1fd298a4eeea94f3 scsi: cxlflash: Remove port 
configuration assumptions
  0aa14887c60c27e3385295ee85f5ac079ae2ffb5 scsi: cxlflash: Hide FC internals 
behind common access routine
  565180723294b06b3e60030033847277b9d6d4bb scsi: cxlflash: SISlite updates to 
support 4 ports
  1cd7fabc82eb06c834956113ff287f8848811fb8 scsi: cxlflash: Support up to 4 ports
  323e33428ea23bfb1ae5010b18b4540048b2ad51 scsi: cxlflash: Fence EEH during 
probe
  50b787f7235efbd074bbdf4315e0cc261d85b4d7 scsi: cxlflash: Remove unnecessary 
DMA mapping
  cd41e18daf1a21fea5a195a5a74c97c6b183c15a scsi: cxlflash: Fix power-of-two 
validations
  fcc87e74a987dc9c0c85f53546df944ede76486a scsi: cxlflash: Fix warnings/errors
  e2ef33fa5958c51ebf0c6f18db19fe927e2185fa scsi: cxlflash: Improve asynchronous 
interrupt processing
  bfc0bab172cabf3bb25c48c4c521b317ff4a909d scsi: cxlflash: Support multiple 
hardware queues
  3065267a80c88d775e8eb34196280e8eee33322f scsi: cxlflash: Add hardware queues 
attribute
  1dd0c0e4fd02dc5e5bfaf89bd4656aabe4ae3cb3 scsi: cxlflash: Introduce hardware 
queue steering
   

  
  The patches are required on 16.04.3 HWE v4.10 

[Kernel-packages] [Bug 1699004] Re: APST gets enabled against explicit kernel option

[Thadeu Lima de Souza Cascardo]

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

Title:
  APST gets enabled against explicit kernel option

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact] 
  The NVMe driver doesn't set APSTE on APST quirked devices at initialization. 
If the BIOS or NVMe enables APST before driver loading, APST will never be 
disabled, it also ignores explicit kernel option as result.
  So the faulty NVMe may not work as intended. 

  [Test Case]
  $ sudo nvme get-feature -f 0x0c -H /dev/nvme0
  ...will show APST is "Disabled" instead of "Enabled"

  [Regression Potential] 
  Very low.
  This SRU didn't change anything really - it just explicitly set APSTE at 
initialization.

  ---

  I have a Lenovo ThinkPad X270 with a Toshiba nvme SSD

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev
    
 - -- 
 
  /dev/nvme0n1 177S10WYTAMT THNSF5256GPUK TOSHIBA   
 1 256.06  GB / 256.06  GB512   B +  0 B   51025KLA

  I was affected by this bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184?comments=all
  before. After disabling APST by adding 
"nvme_core.default_ps_max_latency_us=0" in /etc/default/grub, the bug went away.

  Since yesterday, however the bug has returned, with the system dying
  with I/O errors after an hour or so.

  I verified, that the kernel option is still being set

  $ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7

  however it turns out that it is being ignored for some reason, and
  running

  $ sudo nvme get-feature -f 0x0c -H /dev/nvme0

  reports that APST is enabled. I can successfully disable it manually
  using

  $ sudo nvme set-feature -f 0x0c -v=0 /dev/nvme0

  and the problem goes away. However, after any reboot and even after
  waking the system from suspend, it is reenabled, causing the system to
  crash after a short while.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maeher 1669 F...m pulseaudio
   /dev/snd/controlC0:  maeher 1669 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 19 23:29:31 2017
  InstallationDate: Installed on 2017-04-17 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20HN001RUS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET30W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN001RUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET30W(1.08):bd01/16/2017:svnLENOVO:pn20HN001RUS:pvrThinkPadX270:rvnLENOVO:rn20HN001RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HN001RUS
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1689946] Re: Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with split op

[Joseph Salisbury]

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

** Also affects: linux (Ubuntu Artful)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

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

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

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

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

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with
  split op

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

Bug description:
   State: Open by: mdate on 19 March 2017 12:33:34 

  On a Bolt adapter in a system with Ubuntu 16.04, I've formatted the
  Bolt for T10 and am using it to do a dd with a 2M block size.

  Here are the commands:
  nvme format /dev/nvme0n1 --lbaf=1 --pil=0 --ms=0 --pi=2

  dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct count=1

  I get an error on the dd.
root@x1623bp1:~# dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct 
count=1
dd: error writing '/dev/nvme0n1': Input/output error
1+0 records in
0+0 records out
0 bytes copied, 0.0525061 s, 0.0 kB/s

  dmesg shows:
  [589997.985151] blk_update_request: I/O error, dev nvme0n1, sector 0

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

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

[Kernel-packages] [Bug 1702521] Re: cxlflash update request in the Xenial SRU stream

[bugproxy]

** Tags removed: bugnameltc-154010 kernel-da-key severity-high

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

Title:
  cxlflash update request in the Xenial SRU stream

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

Bug description:
  ---Problem Description---
  Request to update cxlflash in the Xenial SRU stream

  There are multiple patches in upstream that are of interest and would
  like to see them pulled into the Xenial SRU stream. I have listed the
  patches that are in upstream/master tree.

  41b99e1a30a6d04df7585905e5ffc7251099c6d3 scsi: cxlflash: Avoid mutex when 
destroying context
  44ef38f9a2af8644c24ace6cbe1132dc70174c39 scsi: cxlflash: Cache owning adapter 
within context
  888baf069f49529f33c0b1dfb0fc4811dc0ca1d2 scsi: cxlflash: Add kref to context
  cd34af40a09c678abad36304eb68e1774640e908 scsi: cxlflash: Transition to 
application close model
  de9f0b0cbb86da288a2d38e35f2953a85608a6aa scsi: cxlflash: Remove adapter file 
descriptor cache
  9442c9b0ed5c6f3a86dce0d6f714ef43f7f6cd53 scsi: cxlflash: Update documentation
  f80132613d576e7e705344d0c33f3b5e65d9e16a scsi: cxlflash: Refactor WWPN setup
  c4a11827b760ef8dcda26b5731d072b1d8fb7c81 scsi: cxlflash: Fix context 
reference tracking on detach
  68ab2d76e4be785a7003fdb42b7c4ed8bba56ae2 scsi: cxlflash: Set sg_tablesize to 
1 instead of SG_NONE
  8a2605430a64bdf0361af5a18043717a2c59972f scsi: cxlflash: Fix crash in 
cxlflash_restore_luntable()
  3d2f617d448f5e1d15d2844b803c13763ed51f1f scsi: cxlflash: Improve 
context_reset() logic
  11f7b1844ac01d0298aad6a0ec2591bef4a1c3a2 scsi: cxlflash: Avoid command room 
violation
  e7ab2d401dbf633eaafe5bd1f39e84492848668f scsi: cxlflash: Remove unused buffer 
from AFU command
  350bb478f57387df1e0b830fc64be2d1c3d55b6b scsi: cxlflash: Allocate memory 
instead of using command pool for AFU sync
  5fbb96c8f1ba89fb220efb7e4eeed7cb5112becd scsi: cxlflash: Use cmd_size for 
private commands
  25bced2b61b43b6372a73008dafa2183c5d53c39 scsi: cxlflash: Remove private 
command pool
  de01283baa334b1d938cfd9121198c517ad6dc89 scsi: cxlflash: Wait for active AFU 
commands to timeout upon tear down
  9ba848acbf4fbc6d99a0992df9ef5eb1b4842ba9 scsi: cxlflash: Remove AFU command 
lock
  d4ace35166e55e73afe72a05d166342996063d35 scsi: cxlflash: Cleanup send_tmf()
  9d89326c6660bc287b74983b51239460da10e189 scsi: cxlflash: Cleanup 
queuecommand()
  48b4be36edf8a2cb0dedcb2d28f598e51249e805 scsi: cxlflash: Migrate IOARRIN 
specific routines to function pointers
  fe7f96982a4e7103ffab45fba34c57ee19b62639 scsi: cxlflash: Migrate scsi command 
pointer to AFU command
  9c7d1ee5f13a7130f6d3df307ec010e9e003fa98 scsi: cxlflash: Refactor context 
reset to share reset logic
  696d0b0c715360ce28fedd3c8b009d3771a5ddeb scsi: cxlflash: Support SQ Command 
Mode
  fb67d44dfbdf85d984b9b40284e90636a3a7b21d scsi: cxlflash: Cleanup prints
  0df5bef739601f18bffc0d256ae451f239a826bd scsi: cxlflash: Cancel scheduled 
workers before stopping AFU
  943445200b049d5179b95297e5372d399c8ab0e2 scsi: cxlflash: Enable PCI device ID 
for future IBM CXL Flash AFU
  76a6ebbeef26b004c36a0c8ee0496bae5428fc31 scsi: cxlflash: Separate RRQ 
processing from the RRQ interrupt handler
  f918b4a8e6f8bb59c44045f85d10fd9cc7e5a4c0 scsi: cxlflash: Serialize RRQ access 
and support offlevel processing
  cba06e6de4038cd44a3e93a92ad982c372b8a14e scsi: cxlflash: Implement IRQ 
polling for RRQ processing
  3b225cd32a05b627a6ca366f364a824beaabecc5 scsi: cxlflash: Update sysfs helper 
routines to pass config structure
  78ae028e823701148e4915759459ee79597ea8ec scsi: cxlflash: Support dynamic 
number of FC ports
  8fa4f1770d56af6f0a5a862f1fd298a4eeea94f3 scsi: cxlflash: Remove port 
configuration assumptions
  0aa14887c60c27e3385295ee85f5ac079ae2ffb5 scsi: cxlflash: Hide FC internals 
behind common access routine
  565180723294b06b3e60030033847277b9d6d4bb scsi: cxlflash: SISlite updates to 
support 4 ports
  1cd7fabc82eb06c834956113ff287f8848811fb8 scsi: cxlflash: Support up to 4 ports
  323e33428ea23bfb1ae5010b18b4540048b2ad51 scsi: cxlflash: Fence EEH during 
probe
  50b787f7235efbd074bbdf4315e0cc261d85b4d7 scsi: cxlflash: Remove unnecessary 
DMA mapping
  cd41e18daf1a21fea5a195a5a74c97c6b183c15a scsi: cxlflash: Fix power-of-two 
validations
  fcc87e74a987dc9c0c85f53546df944ede76486a scsi: cxlflash: Fix warnings/errors
  e2ef33fa5958c51ebf0c6f18db19fe927e2185fa scsi: cxlflash: Improve asynchronous 
interrupt processing
  bfc0bab172cabf3bb25c48c4c521b317ff4a909d scsi: cxlflash: Support multiple 
hardware queues
  3065267a80c88d775e8eb34196280e8eee33322f scsi: cxlflash: Add hardware queues 
attribute
  1dd0c0e4fd02dc5e5bfaf89bd4656aabe4ae3cb3 scsi: cxlflash: Introduce hardware 
queue steering
   

  
  The patches are required on 16.04.3 HWE v4.10 

[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Ath10k to read different board data file if specify in SMBIOS

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

Bug description:
  Board Data File (BDF) is loaded upon driver boot-up procedure. The right
  board data file is identified, among others, by device and sybsystem ids.

  The problem, however, can occur when the (default) board data file cannot
  fulfill with the vendor requirements and it is necessary to use a different
  board data file.

  To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name
  Extension to specify the extension/variant name. The driver will take the
  extension suffix into consideration and will load the right (non-default)
  board data file if necessary.

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

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

[Kernel-packages] [Bug 1702521] Re: cxlflash update request in the Xenial SRU stream

[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/1702521

Title:
  cxlflash update request in the Xenial SRU stream

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

Bug description:
  ---Problem Description---
  Request to update cxlflash in the Xenial SRU stream

  There are multiple patches in upstream that are of interest and would
  like to see them pulled into the Xenial SRU stream. I have listed the
  patches that are in upstream/master tree.

  41b99e1a30a6d04df7585905e5ffc7251099c6d3 scsi: cxlflash: Avoid mutex when 
destroying context
  44ef38f9a2af8644c24ace6cbe1132dc70174c39 scsi: cxlflash: Cache owning adapter 
within context
  888baf069f49529f33c0b1dfb0fc4811dc0ca1d2 scsi: cxlflash: Add kref to context
  cd34af40a09c678abad36304eb68e1774640e908 scsi: cxlflash: Transition to 
application close model
  de9f0b0cbb86da288a2d38e35f2953a85608a6aa scsi: cxlflash: Remove adapter file 
descriptor cache
  9442c9b0ed5c6f3a86dce0d6f714ef43f7f6cd53 scsi: cxlflash: Update documentation
  f80132613d576e7e705344d0c33f3b5e65d9e16a scsi: cxlflash: Refactor WWPN setup
  c4a11827b760ef8dcda26b5731d072b1d8fb7c81 scsi: cxlflash: Fix context 
reference tracking on detach
  68ab2d76e4be785a7003fdb42b7c4ed8bba56ae2 scsi: cxlflash: Set sg_tablesize to 
1 instead of SG_NONE
  8a2605430a64bdf0361af5a18043717a2c59972f scsi: cxlflash: Fix crash in 
cxlflash_restore_luntable()
  3d2f617d448f5e1d15d2844b803c13763ed51f1f scsi: cxlflash: Improve 
context_reset() logic
  11f7b1844ac01d0298aad6a0ec2591bef4a1c3a2 scsi: cxlflash: Avoid command room 
violation
  e7ab2d401dbf633eaafe5bd1f39e84492848668f scsi: cxlflash: Remove unused buffer 
from AFU command
  350bb478f57387df1e0b830fc64be2d1c3d55b6b scsi: cxlflash: Allocate memory 
instead of using command pool for AFU sync
  5fbb96c8f1ba89fb220efb7e4eeed7cb5112becd scsi: cxlflash: Use cmd_size for 
private commands
  25bced2b61b43b6372a73008dafa2183c5d53c39 scsi: cxlflash: Remove private 
command pool
  de01283baa334b1d938cfd9121198c517ad6dc89 scsi: cxlflash: Wait for active AFU 
commands to timeout upon tear down
  9ba848acbf4fbc6d99a0992df9ef5eb1b4842ba9 scsi: cxlflash: Remove AFU command 
lock
  d4ace35166e55e73afe72a05d166342996063d35 scsi: cxlflash: Cleanup send_tmf()
  9d89326c6660bc287b74983b51239460da10e189 scsi: cxlflash: Cleanup 
queuecommand()
  48b4be36edf8a2cb0dedcb2d28f598e51249e805 scsi: cxlflash: Migrate IOARRIN 
specific routines to function pointers
  fe7f96982a4e7103ffab45fba34c57ee19b62639 scsi: cxlflash: Migrate scsi command 
pointer to AFU command
  9c7d1ee5f13a7130f6d3df307ec010e9e003fa98 scsi: cxlflash: Refactor context 
reset to share reset logic
  696d0b0c715360ce28fedd3c8b009d3771a5ddeb scsi: cxlflash: Support SQ Command 
Mode
  fb67d44dfbdf85d984b9b40284e90636a3a7b21d scsi: cxlflash: Cleanup prints
  0df5bef739601f18bffc0d256ae451f239a826bd scsi: cxlflash: Cancel scheduled 
workers before stopping AFU
  943445200b049d5179b95297e5372d399c8ab0e2 scsi: cxlflash: Enable PCI device ID 
for future IBM CXL Flash AFU
  76a6ebbeef26b004c36a0c8ee0496bae5428fc31 scsi: cxlflash: Separate RRQ 
processing from the RRQ interrupt handler
  f918b4a8e6f8bb59c44045f85d10fd9cc7e5a4c0 scsi: cxlflash: Serialize RRQ access 
and support offlevel processing
  cba06e6de4038cd44a3e93a92ad982c372b8a14e scsi: cxlflash: Implement IRQ 
polling for RRQ processing
  3b225cd32a05b627a6ca366f364a824beaabecc5 scsi: cxlflash: Update sysfs helper 
routines to pass config structure
  78ae028e823701148e4915759459ee79597ea8ec scsi: cxlflash: Support dynamic 
number of FC ports
  8fa4f1770d56af6f0a5a862f1fd298a4eeea94f3 scsi: cxlflash: Remove port 
configuration assumptions
  0aa14887c60c27e3385295ee85f5ac079ae2ffb5 scsi: cxlflash: Hide FC internals 
behind common access routine
  565180723294b06b3e60030033847277b9d6d4bb scsi: cxlflash: SISlite updates to 
support 4 ports
  1cd7fabc82eb06c834956113ff287f8848811fb8 scsi: cxlflash: Support up to 4 ports
  323e33428ea23bfb1ae5010b18b4540048b2ad51 scsi: cxlflash: Fence EEH during 
probe
  50b787f7235efbd074bbdf4315e0cc261d85b4d7 scsi: cxlflash: Remove unnecessary 
DMA mapping
  cd41e18daf1a21fea5a195a5a74c97c6b183c15a scsi: cxlflash: Fix power-of-two 
validations
  fcc87e74a987dc9c0c85f53546df944ede76486a scsi: cxlflash: Fix warnings/errors
  e2ef33fa5958c51ebf0c6f18db19fe927e2185fa scsi: cxlflash: Improve asynchronous 
interrupt processing
  bfc0bab172cabf3bb25c48c4c521b317ff4a909d scsi: cxlflash: Support multiple 
hardware queues
  3065267a80c88d775e8eb34196280e8eee33322f scsi: cxlflash: Add hardware queues 
attribute
  1dd0c0e4fd02dc5e5bfaf89bd4656aabe4ae3cb3 scsi: cxlflash: Introduce hardware 
queue steering
   

  
  The patches are required on 16.04.3 HWE v4.10 

[Kernel-packages] [Bug 1699004] Re: APST gets enabled against explicit kernel option

[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/1699004

Title:
  APST gets enabled against explicit kernel option

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact] 
  The NVMe driver doesn't set APSTE on APST quirked devices at initialization. 
If the BIOS or NVMe enables APST before driver loading, APST will never be 
disabled, it also ignores explicit kernel option as result.
  So the faulty NVMe may not work as intended. 

  [Test Case]
  $ sudo nvme get-feature -f 0x0c -H /dev/nvme0
  ...will show APST is "Disabled" instead of "Enabled"

  [Regression Potential] 
  Very low.
  This SRU didn't change anything really - it just explicitly set APSTE at 
initialization.

  ---

  I have a Lenovo ThinkPad X270 with a Toshiba nvme SSD

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev
    
 - -- 
 
  /dev/nvme0n1 177S10WYTAMT THNSF5256GPUK TOSHIBA   
 1 256.06  GB / 256.06  GB512   B +  0 B   51025KLA

  I was affected by this bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184?comments=all
  before. After disabling APST by adding 
"nvme_core.default_ps_max_latency_us=0" in /etc/default/grub, the bug went away.

  Since yesterday, however the bug has returned, with the system dying
  with I/O errors after an hour or so.

  I verified, that the kernel option is still being set

  $ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7

  however it turns out that it is being ignored for some reason, and
  running

  $ sudo nvme get-feature -f 0x0c -H /dev/nvme0

  reports that APST is enabled. I can successfully disable it manually
  using

  $ sudo nvme set-feature -f 0x0c -v=0 /dev/nvme0

  and the problem goes away. However, after any reboot and even after
  waking the system from suspend, it is reenabled, causing the system to
  crash after a short while.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maeher 1669 F...m pulseaudio
   /dev/snd/controlC0:  maeher 1669 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 19 23:29:31 2017
  InstallationDate: Installed on 2017-04-17 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20HN001RUS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET30W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN001RUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET30W(1.08):bd01/16/2017:svnLENOVO:pn20HN001RUS:pvrThinkPadX270:rvnLENOVO:rn20HN001RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HN001RUS
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1701316] Re: Data corruption with hio driver

[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/1701316

Title:
  Data corruption with hio driver

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Impact: Data corruption is seen when using the hio driver with 4.10
  and later kernels.

  Fix: Patch to fix incorrect use of enumerated values as bitmasks.

  Test case: See below.

  Regression potential: Very low. Changes are simple and Obviously
  Correct (TM), and they only affect the hio driver.

  ---

  We are seeing data corruption issues using the hio driver with kernel
  4.10.0

  # uname -a
  Linux arbok 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  Making xfs fails:

  root@arbok:~# mkfs.xfs /dev/hioa
  meta-data=/dev/hioa  isize=512agcount=4, agsize=48835584 blks
   =   sectsz=512   attr=2, projid32bit=1
   =   crc=1finobt=1, sparse=0
  data =   bsize=4096   blocks=195342336, imaxpct=25
   =   sunit=0  swidth=0 blks
  naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
  log  =internal log   bsize=4096   blocks=95382, version=2
   =   sectsz=512   sunit=0 blks, lazy-count=1
  realtime =none   extsz=4096   blocks=0, rtextents=0
  bad magic number
  bad magic number
  Metadata corruption detected at xfs_sb block 0x0/0x200
  libxfs_writebufr: write verifer failed on xfs_sb bno 0x0/0x200

  The drive appears to be healthy. Firmware has been upgraded to ver
  656:

  root@arbok:~# hio_info -d /dev/hioa
  hioaSerial number:  022XWV10G2000325
  Size(GB):   800
  Max size(GB):   800
  Hardware version:   1.0
  Firmware version:   656
  Driver version: 2.1.0.28
  Work mode:  MLC
  Run time (sec.):8910490
  Total  read(MB):8499
  Total write(MB):0
  Lifetime remaining: 99.844%
  Max bad block rate: 0.167%
  Health: OK
  Comment:NA

  No relevant entries about read/write errors in dmesg

  Also just copying 8G random data and reading those back gives a hash mismatch:
  root@arbok:~# dd if=/dev/urandom of=test.dat bs=1G count=8 iflag=fullblock
  8+0 records in
  8+0 records out
  8589934592 bytes (8.6 GB, 8.0 GiB) copied, 85.6076 s, 100 MB/s
  root@arbok:~# dd if=test.dat of=/dev/hioa bs=1G count=8 iflag=fullblock
  8+0 records in
  8+0 records out
  8589934592 bytes (8.6 GB, 8.0 GiB) copied, 10.6034 s, 810 MB/s
  root@arbok:~# dd if=/dev/hioa of=read-back.dat bs=1G count=8 iflag=fullblock
  sha256sum test.dat read-
  8+0 records in
  8+0 records out
  8589934592 bytes (8.6 GB, 8.0 GiB) copied, 66.1872 s, 130 MB/s
  root@arbok:~# sha256sum test.dat read-back.dat
  6376d245a07c42c990589a3c17c44e63d826d1cb583fc5a065deff9dae69fd3a  test.dat
  ebfb4ef19ae410f190327b5ebd312711263bc7579970e87d9c1e2d84e06b3c25  
read-back.dat

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

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

[Kernel-packages] [Bug 1703437] Re: New ACPI identifiers for ThunderX SMMU

[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/1703437

Title:
  New ACPI identifiers for ThunderX SMMU

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

Bug description:
  [Impact]
  With current firmware (e.g. AMI 018 for CRBs), Cavium ThunderX-based nodes in 
ACPI mode fail to boot due to an undetected SMMU device. This doesn't impact 
the currently certified Cavium ThunderX-based systems, which boot in non-ACPI 
mode by default. However, future ThunderX-based platforms will likely use ACPI 
by default, and they would suffer from this bug.

  [Test Case]
  Boot a Cavium CRB w/ 018 firmware. Note that lack of SMMU boot messages, and 
the failure to boot due to undetected devies (specifically, no root disk found).

  [Regression Risk]
  The upstream fix is adding support for new device IDs, which were previously 
unsupported and would've previously failed to probe w/ -ENODEV.

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

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

[Kernel-packages] [Bug 1702749] Re: arm64: fix crash reading /proc/kcore

[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/1702749

Title:
  arm64: fix crash reading /proc/kcore

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

Bug description:
  [Impact]
  Reading /proc/kcore can lead to a crash on arm64 systems.
  This was found to cause crashes when, e.g. annotating symbols in a perf top 
session.

  [Test Case]
  # cat /proc/kcore > /dev/null

  [Regression Risk]
  2 upstream patches need to be cherry-picked to fix this. 

  The 1st patch is a simplification to the kcore driver that impacts all
  architectures. Instead of re-checking at read time for vmalloc/module
  addresses, it just checks for a flag that was set during kcore driver
  init. This looks correct to me but could of course have an unnoticed
  bug.

  The second patch is arm64-specific, and regression risk has been
  mitigated by testing on arm64 hardware.

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

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

[Kernel-packages] [Bug 1704146] Re: hns: under heavy load, NIC may fail and require reboot

[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/1704146

Title:
  hns: under heavy load, NIC may fail and require reboot

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

Bug description:
  [Impact]
  The onboard NIC on HiSilicon D05 boards can fail under heavy load, requiring 
a reboot to recover.

  [Test Case]
  There isn't a known reliable reproducer.

  [Regression Risk]
  This is a driver-specific fix, so regression risk is limited to devices that 
we can directly test.

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

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

[Kernel-packages] [Bug 1698706] Re: Quirk for non-compliant PCI bridge on HiSilicon D05 board

[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/1698706

Title:
  Quirk for non-compliant PCI bridge on HiSilicon D05 board

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

Bug description:
  SRU Justification

  [Impact]
  Xorg autodetection does not work on HiSilicon D05 boards.

  [Fix]
  The HiSilicon D05 board has some PCI bridges (PCI ID 19e5:1610) that are not 
spec-compliant: they do not set the VGA Enable bit when a VGA card is behind 
the bridge. This stops vgaarb setting the device as a boot vga device, breaking 
Xorg auto-detection. [0]

  Despite this, the hibmc VGA card (PCI ID 19e5:1711) is known to work
  when behind these bridges.

  Provide a quirk so that this combination of bridge and card works.

  [Testcase]
  On an affected board, run:
  # find /sys/devices -name boot_vga -exec cat \{\} \;

  This should print 0 without this patch and 1 with this patch.

  [Regression Potential]
  There is a risk with overriding the VGA arbiter that adding additional VGA 
cards to the board may go wrong somehow. The fixup specifically tests for the 
bridge and card on the board, so regressions should be limited to that 
combination of bridge and card.

  [Notes]
  HiSilicon is hoping to have 16.04.3 HWE kernel support their board, hence the 
submission of this patch before it has been accepted upstream. The patch has 
been submitted upstream and I will continue to work with upstream to land it.[1]

  [0] https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991 - this
  bug tracked debugging of a segfault and then this issue. Comments 25
  (https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/25)
  and 31 onwards detail this issue.

  [1] https://patchwork.ozlabs.org/patch/778054/

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

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

Re: [Kernel-packages] [Bug 1694167] Re: unity does not start when booting with 4.11.3 kernel

[Christoph Grimmer-Dietrich]

Hallo Joseph,

The bug did only occur when using 4.11.3 from kernel.ubuntu.com. 4.11.2 was
running fine as well as my currently used 4.11.8. I switched to the
upstream kernel due to severe problems with my bluetooth headset as well as
the lacking DP support.

2017-07-14 15:32 GMT+02:00 Joseph Salisbury 
:

> 4.11.3 sounds like an upstream kernel.  Does this bug also happen with
> the stock Ubuntu kernel?
>
> ** Tags added: kernel-da-key
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1694167
>
> Title:
>   unity does not start when booting with 4.11.3 kernel
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I installed the recent 4.11.3 kernel from the packages downloaded from
>   kernel.ubuntu.org
>
>   After rebooting unity did not start properly. I had no dash, no
>   decorations and no dock. After starting unity manually from the
>   command line I got window decorations for a program that is run after
>   login but nothing else.
>
>   After switching back to 4.11.2 the system is working fine again.
>
>   > lsb_release -rd
>   Description:  Ubuntu 17.04
>   Release:  17.04
>
>
>   If you need further information please let me know!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1694167/+subscriptions
>

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

Title:
  unity does not start when booting with 4.11.3 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed the recent 4.11.3 kernel from the packages downloaded from
  kernel.ubuntu.org

  After rebooting unity did not start properly. I had no dash, no
  decorations and no dock. After starting unity manually from the
  command line I got window decorations for a program that is run after
  login but nothing else.

  After switching back to 4.11.2 the system is working fine again.

  > lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  
  If you need further information please let me know!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-01 (347 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: linux (not installed)
  Tags:  zesty
  Uname: Linux 4.11.8-041108-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (79 days ago)
  UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1694167] Re: unity does not start when booting with 4.11.3 kernel

[Christoph Grimmer-Dietrich]

apport information

** Tags added: apport-collected

** Description changed:

  I installed the recent 4.11.3 kernel from the packages downloaded from
  kernel.ubuntu.org
  
  After rebooting unity did not start properly. I had no dash, no
  decorations and no dock. After starting unity manually from the command
  line I got window decorations for a program that is run after login but
  nothing else.
  
  After switching back to 4.11.2 the system is working fine again.
  
  > lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04
  
  
  If you need further information please let me know!
+ --- 
+ ApportVersion: 2.20.4-0ubuntu4.4
+ Architecture: amd64
+ CurrentDesktop: Unity:Unity7
+ DistroRelease: Ubuntu 17.04
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2016-08-01 (347 days ago)
+ InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ Package: linux (not installed)
+ Tags:  zesty
+ Uname: Linux 4.11.8-041108-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: Upgraded to zesty on 2017-04-26 (79 days ago)
+ UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1694167/+attachment/4914627/+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/1694167

Title:
  unity does not start when booting with 4.11.3 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed the recent 4.11.3 kernel from the packages downloaded from
  kernel.ubuntu.org

  After rebooting unity did not start properly. I had no dash, no
  decorations and no dock. After starting unity manually from the
  command line I got window decorations for a program that is run after
  login but nothing else.

  After switching back to 4.11.2 the system is working fine again.

  > lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  
  If you need further information please let me know!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-01 (347 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: linux (not installed)
  Tags:  zesty
  Uname: Linux 4.11.8-041108-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (79 days ago)
  UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1694167] ProcCpuinfoMinimal.txt

[Christoph Grimmer-Dietrich]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1694167/+attachment/4914628/+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/1694167

Title:
  unity does not start when booting with 4.11.3 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed the recent 4.11.3 kernel from the packages downloaded from
  kernel.ubuntu.org

  After rebooting unity did not start properly. I had no dash, no
  decorations and no dock. After starting unity manually from the
  command line I got window decorations for a program that is run after
  login but nothing else.

  After switching back to 4.11.2 the system is working fine again.

  > lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  
  If you need further information please let me know!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-01 (347 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: linux (not installed)
  Tags:  zesty
  Uname: Linux 4.11.8-041108-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (79 days ago)
  UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

[Christoph Grimmer-Dietrich]

apport information

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

Title:
  unity does not start when booting with 4.11.3 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed the recent 4.11.3 kernel from the packages downloaded from
  kernel.ubuntu.org

  After rebooting unity did not start properly. I had no dash, no
  decorations and no dock. After starting unity manually from the
  command line I got window decorations for a program that is run after
  login but nothing else.

  After switching back to 4.11.2 the system is working fine again.

  > lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  
  If you need further information please let me know!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-01 (347 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: linux (not installed)
  Tags:  zesty
  Uname: Linux 4.11.8-041108-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (79 days ago)
  UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1627828] Re: iwl3945 crashes randomly

[John Pilkington]

The VPD error message is addressed in this document from HP

http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=mmr_kc-0131686

which has links to kernel patches from SUSE that are related to the one
in comment #25

It isn't clear to me how much of this is already in the 'buntu kernels,
or what effect the "VPD" problem has on the loading of the iwl3945
firmware and my wifi access.

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

Title:
  iwl3945 crashes randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Out of nothing a once properly working 
  0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] 
Network Connection (rev 02)
  started to crash with:
  Sep 22 14:38:16 seba-Latitude-D630 kernel: [26707.320032] iwl3945 
:0c:00.0: Error sending C_POWER_TBL: time out after 500ms.
  Sep 22 14:38:16 seba-Latitude-D630 kernel: [26707.320039] iwl3945 
:0c:00.0: set power fail, ret = -110
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.012031] iwl3945 
:0c:00.0: Queue 2 stuck for 2500 ms.
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.012039] iwl3945 
:0c:00.0: On demand firmware reload
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.050333] ieee80211 phy0: 
Hardware restart was requested
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.084769] retire_capture_urb: 
33 callbacks suppressed
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.098359] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.098364] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.145087] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.145089] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.191802] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.191805] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.238526] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.238528] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.285272] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.285275] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.322030] iwl3945 
:0c:00.0: Unable to initialize device after 5 attempts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seba   1421 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Sep 26 16:38:18 2016
  HibernationDevice: RESUME=UUID=64d7608d-53a8-46a6-884c-0ccf1814fb03
  InstallationDate: Installed on 2016-08-28 (29 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude D630
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=dce979b5-6a44-48cf-a87a-d314263a895c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Kernel-packages] [Bug 1704232] Re: Halt doesn't power system down

[Jeff Lane]

On Fri, Jul 14, 2017 at 9:25 AM, Joseph Salisbury
 wrote:
> Did this issue start happening after an update/upgrade?

No, it's done this as long as I've had the machine (It's home-built,
not an OEM designed system).  16.04 GA was the first OS on it and the
soft-power-off stuff has never worked on it.  I just finally got
around to filing the bug.

> Was there a prior kernel version where you were not having this
particular problem?

No, see above

> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.12 kernel[0].

Sure, but can't do that until this weekend.

>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".

Got 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/1704232

Title:
  Halt doesn't power system down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Skylake Core i7 system running up-to-date 16.04.1 (4.4
  kernel).

  Whenever I issue a halt (either shutdown -h now, or halt) the shutdown
  process gets as far as showing the "Target shutdown reached" on the
  console, but instead of actually powering the system down, it just
  sits there idling.

  I have to manually power the system off by holding the power button
  down.

  What should happen, is that 'shutdown -h now' should actually shut the
  OS down and power the computer off without any further intervention.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-83-generic 4.4.0-83.106
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bladernr  28322 F pulseaudio
   /dev/snd/pcmC0D0p:   bladernr  28322 F...m pulseaudio
   /dev/snd/controlC0:  bladernr  28322 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 13 17:42:14 2017
  HibernationDevice: RESUME=UUID=0ca350ae-0a5d-4d84-9ac5-f0f83959aa62
  InstallationDate: Installed on 2016-02-11 (518 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  MachineType: Gigabyte Technology Co., Ltd. Z170MX-Gaming 5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed 
root=UUID=fa272e99-2333-4360-a2f3-edbde23a1fed ro quiet splash 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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1704102] Re: bonding: stack dump when unregistering a netdev

[Joseph Salisbury]

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

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

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  bonding: stack dump when unregistering a netdev

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

Bug description:
  Here is the reproducer:

  ip netns add foo
  ip -n foo link add dummy1 type dummy
  ip -n foo link add dummy2 type dummy
  modprobe bonding
  ip -n foo link add bond1 type bond
  ip -n foo link set dev bond1 down
  ip -n foo addr add 10.10.10.1/24 dev bond1
  ip -n foo link set dev bond1 up
  ip -n foo link set dummy1 master bond1
  ip -n foo link set dummy2 master bond1
  ip -n foo link set bond1 mtu 1540

  # Move slaves to init_net
  ip -n foo link set dummy1 netns 1
  ip -n foo link set dummy2 netns 1

  # idev are still in netns foo for dummy interfaces:
  ip netns exec foo ls /proc/sys/net/ipv4/conf/
  ip netns exec foo ls /proc/net/dev_snmp6/

  ip netns del foo
  dmesg

  The bug has been fixed upstream by this patch:

  f51048c3e07b ("bonding: avoid NETDEV_CHANGEMTU event when
  unregistering slave")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/bonding?id=f51048c3e07b

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

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

[Kernel-packages] [Bug 1701019] Re: linux: 4.8.0-59.64 -proposed tracker

[Kleber Sacilotto de Souza]

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

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

Title:
  linux: 4.8.0-59.64 -proposed tracker

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

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: 1701020
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1696165] Re: [SRU][Zesty] fix soft lockup on overcommited hugepages

[Manoj Iyer]

== with hwpoison-inject module ==

Test case fails as expected .. and does not result in soft-lockups.
$ uname -r
4.10.0-28-generic

$ sudo ./run_hugepage_overcommit.sh
sudo: unable to resolve host awsdp0
hwpoison-inject module is loaded.

***
Pay attention:

This test checks that hugepage soft-offlining works under overcommitting.
***


-
TestCase ./thugetlb_overcommit 1
FAIL: migration failed.
Unpoisoning.

Num of Executed Test Case: 1Num of Failed Case: 1

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

Title:
  [SRU][Zesty] fix soft lockup on overcommited hugepages

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  On failing to migrate a page, soft_offline_huge_page() performs the necessary 
update to the hugepage ref-count.

  But when !hugepage_migration_supported() , unmap_and_move_hugepage()
  also decrements the page ref-count for the hugepage. The combined
  behaviour leaves the ref-count in an inconsistent state.

  This leads to soft lockups when running the overcommitted hugepage
  test from mce-tests suite

  [Testing]
  Run the mce-test/cases/function/hwpoison/run_hugepage_overcommit.sh and you 
should see softlock up if hugepage migration support is not enabled.

  [Fix]
  upstream commit:
  30809f559a0d mm/migrate: fix refcount handling when 
!hugepage_migration_supported()

  [Regression Potential]

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

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

[Kernel-packages] [Bug 1689980] Re: AACRAID for power9 platform

[Kleber Sacilotto de Souza]

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

Title:
  AACRAID for power9 platform

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

Bug description:
  SRU Justification

  Impact: Various issues found during integration of Microsemi adapters
  on Power 8 and Power 9 systems.

  Fix: Update the aacraid driver to version 50834 by cherry picking
  patches from upstream and from linux-next.

  Test case: Updated driver has been tested by IBM on Power systems and
  regression tested by Microsemi on other platforms.

  Regression potential: Changes (aside from trivial typo fixes) are
  limited to aacraid driver, so there's no regression potential outside
  of this driver. Regression testing has been done by Microsemi on
  relevant platforms.

  ---

  Hello team,
  It seems Microsemi team has requested to backport few AACRAID driver patches 
for Power 9 platform for 17.04 and 16.04.3 kernel.

  Hi Narinder,

  We have submitted a handful of critical fixes for the AACRAID driver
  on to the kernel.org, targeting 4.11. These patches are bug fixes and
  our customer IBM is expecting these patches to go into the 16.04.3
  release, for to use with the Power9 platforms.

  Can you please let me know if these patches will be backported by your
  kernel team on to the upcoming 16.04.3? Do you also have a schedule in
  place for 16.04.3 release?

  Thanks,
  Gana

  Below are the patch details.

  Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc
  fixes

  This patchset primarily focuses on tweaking and hardening the
  controller reset support for both ARC and HBA1000 devices. Now the
  driver can only reset the controller thru eh reset. Included a srb
  memory fix and pci dma allocation fix.

  Changes in V2:
   - Corrected heading and description for srb memory patch and removed stray
     comment.
   - Removed incorrect up function call and cleared fib wait flag after call
     to down interruptible in the ioctl return on ctrl reset patch.
   - Added review acknowledgements by David Carroll thank you Dave for
     finding the above issues in the above 2 patches.

  Raghava Aditya Renukunta (19):
  [SCSI] aacraid: Remove __GFP_DMA for raw srb memory
  [SCSI] aacraid: Fix DMAR issues with  iommu=pt
  [SCSI] aacraid: Added 32 and 64 queue depth for arc natives
  [SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks
  [SCSI] aacraid: Remove reset support from check_health
  [SCSI] aacraid: Change wait time for fib completion
  [SCSI] aacraid: Log count info of scsi cmds before reset
  [SCSI] aacraid: Print ctrl status before eh reset
  [SCSI] aacraid: Using single reset mask for IOP reset
  [SCSI] aacraid: Rework IOP reset
  [SCSI] aacraid: Add periodic checks to see IOP reset status
  [SCSI] aacraid: Rework SOFT reset code
  [SCSI] aacraid: Rework aac_src_restart
  [SCSI] aacraid: Use correct function to get ctrl health
  [SCSI] aacraid: Make sure ioctl returns on controller reset
  [SCSI] aacraid: Enable ctrl reset for both hba and arc
  [SCSI] aacraid: Add reset debugging statements
  [SCSI] aacraid: Remove reference to Series-9
  [SCSI] aacraid: Update driver version to 50834

  drivers/scsi/aacraid/aachba.c   |  17 ++-
  drivers/scsi/aacraid/aacraid.h  |  22 +++-
  drivers/scsi/aacraid/commctrl.c |  15 ++-
  drivers/scsi/aacraid/comminit.c |  18 +---
  drivers/scsi/aacraid/commsup.c  |  78 +++---
  drivers/scsi/aacraid/linit.c| 232 
  drivers/scsi/aacraid/src.c  | 136 +--

   7 files changed, 298 insertions(+), 220 deletions(-)

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

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

[Kernel-packages] [Bug 1704343] Re: Ubuntu17.10: Changing guest timebase offset breaks host

[Frank Heimes]

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

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

Title:
  Ubuntu17.10: Changing guest timebase offset breaks host

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

Bug description:
  == Comment: #0 - NAGESWARA R. SASTRY  -
  2017-07-04 07:20:40 ==

  ---Problem Description---
  With little load on the system seeing kernel stack traces and soft lockup 
issues.
   
  Contact Information = nasas...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston25 4.12.0-041200rc6-generic #201706191233 SMP Mon Jun 19 
17:38:35 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Boston Power9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   With little load on the system seeing the stack trace. Start 2-3 guests or 
run some workload.
   
  Stack trace output:
   [56954.376790] NMI watchdog: BUG: soft lockup - CPU#44 stuck for 22s! [CPU 
3/KVM:48428]
  [56954.376949] Modules linked in: vhost_net vhost tap xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter input_leds joydev mac_hid idt_89hpesx 
at24 nvmem_core ofpart binfmt_misc cmdlinepart powernv_flash mtd 
uio_pdrv_genirq uio ibmpowernv opal_prd ipmi_powernv ipmi_devintf vmx_crypto 
ipmi_msghandler ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas
  [56954.377200]  hid_generic usbhid hid ast i2c_algo_bit ttm drm_kms_helper 
syscopyarea crct10dif_vpmsum sysfillrect crc32c_vpmsum sysimgblt fb_sys_fops 
drm i40e aacraid
  [56954.377263] CPU: 44 PID: 48428 Comm: CPU 3/KVM Not tainted 
4.12.0-041200rc6-generic #201706191233
  [56954.377269] task: c000200a74621000 task.stack: c000200a811cc000
  [56954.377277] NIP: c01a4464 LR: c01a4424 CTR: 
c008a970
  [56954.377283] REGS: c000200a811cf7c0 TRAP: 0901   Not tainted  
(4.12.0-041200rc6-generic)
  [56954.377287] MSR: 9280b033 
  [56954.377325]   CR: 48244224  XER: 2000
  [56954.377328] CFAR: c01a4470 SOFTE: 1
 GPR00: c01a4404 c000200a811cfa40 c1503800 
0022
 GPR04: 0022 0022  
0001
 GPR08: 0001 0003 c000200a95599518 
c1541ec0
 GPR12: c008a970 cfadce00
  [56954.377403] NIP [c01a4464] smp_call_function_many+0x374/0x400
  [56954.377414] LR [c01a4424] smp_call_function_many+0x334/0x400
  [56954.377417] Call Trace:
  [56954.377429] [c000200a811cfa40] [c01a4404] 
smp_call_function_many+0x314/0x400 (unreliable)
  [56954.377444] [c000200a811cfac0] [c01a462c] 
kick_all_cpus_sync+0x3c/0x50
  [56954.377459] [c000200a811cfae0] [c006e01c] pmdp_invalidate+0x7c/0xc0
  [56954.377473] [c000200a811cfb10] [c03315f4] 
change_huge_pmd+0x1d4/0x290
  [56954.377486] [c000200a811cfb80] [c02e59c8] 
change_protection_range+0xa38/0xcf0
  [56954.377500] [c000200a811cfcc0] [c030ff88] 
change_prot_numa+0x38/0xb0
  [56954.377514] [c000200a811cfcf0] [c0130584] 
task_numa_work+0x2c4/0x3e0
  [56954.377527] [c000200a811cfdb0] [c0115060] task_work_run+0x140/0x1a0
  [56954.377541] [c000200a811cfe00] [c001cd14] 
do_notify_resume+0xf4/0x100
  [56954.377556] [c000200a811cfe30] [c000b544] 
ret_from_except_lite+0x70/0x74
  [56954.377562] Instruction dump:
  [56954.377571] 409dfd80 3d420004 394aa580 78691f24 7d2a482a e95e 7d4a4a14 
812a0018
  [56954.377597] 71280001 4182001c 6042 7c210b78 <7c421378> 812a0018 
71270001 4082fff0
  [56998.366340] NMI watchdog: BUG: soft lockup - CPU#37 stuck for 22s! 
[qemu-system-ppc:47850]
  [56998.366461] Modules linked in: vhost_net vhost tap xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter input_leds joydev mac_hid idt_89hpesx 
at24 nvmem_core ofpart binfmt_misc cmdlinepart powernv_flash mtd 
uio_pdrv_genirq uio ibmpowernv opal_prd ipmi_powernv ipmi_devintf vmx_crypto 
ipmi_msghandler ib_iser rdma_cm iw_cm ib_cm ib_core 

[Kernel-packages] [Bug 1699172] Re: bitwig 1.3.16 don't open with linux 4.8.0-56-generic

[Joan]

OK, this problem is solved when upgrade the linux kernel
4.8.0-58-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/1699172

Title:
  bitwig 1.3.16 don't open with linux 4.8.0-56-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi, I can't open Bitwig-Studio with the last kernel (Linux
  4.8.0-56-generic), and Ubuntu 16.04. If I change via GRUB the kernel
  to Linux 4.8.0-54-generic, Bitwig-Studio works perfectly.

  
  Another thing. Renoise work perfectly with both kernels.

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

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

[Kernel-packages] [Bug 1704374] Re: system randomly hangs itself

[morris]

If I remember this issue appears since I made the upgrade to Kubuntu
17.04 on my specific hardware platform. the issue didn't affect a
previous system based on 4coredual-sata2 (where ftw tool detect ACPI
2.0). No longer problem appears since I've troubleshooted it by the
suggestion explained on this thread:
https://askubuntu.com/questions/801586/freezing-of-screen-on-
ubuntu-16-04/801597

The issue could happen since the beginning; example: I simple open the
menu start.

The issue could happen randomly after several hours. After restarting
because of system hangs, the problem tends to occur immediately.

No overclock is set; all internal led of the main board are green except
the FSB frequency led that is blue in default position.

The only element I note is that in every case hard drive seems to be
invoked in action so to increase the cpu utilization just before the
system hangs (many times the problem happened during mouse movement or
scrolling the page when hard drive have to manage new elements). The
hard drive has no issue:SMART is good. Could be the stepping management?
however the issue happened also disabling both c1e and eist in the BIOS.
The issue affected also another CPU the e6850 model. SO now or the main
board is broken or other hardware is broken, or BIOS is broken, or the
kernel mismatches the ACPI requirements.

However now that I've applied the workaround the problems seems to be
fixed. So I've to conclude that that's not a hardware issue but a kernel
issue.

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

Title:
  system randomly hangs itself

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this problem affect my system on Kubuntu 17.04 64bit
  Kde Plasma: 5.10.3
  kernel: 4.10.0.26
  Kde frameworks: 5.36.0
  Qt release: 5.7.1
  Probably I've solved with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash 
intel_idle.max_cstate=1"

  Randomly the operating system hangs both eist and or c1e options enabled or 
disabled. I hope that Kubuntu has not damaged my hardware. However what kind of 
workaround should be made on the klernel to have this problem solved once and 
forever?
  My hardware specs:
  maximus eteme;
  latest bios;
  8gb ram 4x2gb corsaire xms 1333;
  gigabyte gt 730 1gb OC
  xonar d2x.

  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
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  1353 F pulseaudio
   /dev/snd/controlC1:  james  1353 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jul 14 12:39:32 2017
  InstallationDate: Installed on 2017-04-25 (79 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer Maximus Extreme
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=52f9b441-fe75-4643-bbec-f912736d397b ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Maximus Extreme
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/24/2009:svnSystemmanufacturer:pnMaximusExtreme:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusExtreme:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: Maximus Extreme
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1696143] Re: [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy driver.

[Manoj Iyer]

== Testing kernel in - proposed ==

The kernel installs and boots fine on the QDF2400 platform.

$ uname -a
Linux awsdp0 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:33:10 UTC 2017 
aarch64 aarch64 aarch64 GNU/Linux

$ apt policy linux-image-4.10.0-28-generic
linux-image-4.10.0-28-generic:
  Installed: 4.10.0-28.32
  Candidate: 4.10.0-28.32
  Version table:
 *** 4.10.0-28.32 500
500 http://ports.ubuntu.com/ubuntu-ports zesty-proposed/main arm64 
Packages
 

$ lsmod | grep -E "qcom_emac|at803x"
at803x 16384  1
qcom_emac  49152  0

The qcom-emac nic is able to get a DHCP lease.

$ ifconfig
enP1s1Link encap:Ethernet  HWaddr 24:8a:07:2a:ca:ca  
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0  Link encap:Ethernet  HWaddr 8c:fd:f0:06:90:cd  
  inet addr:10.228.66.101  Bcast:10.228.66.255  Mask:255.255.255.0
  inet6 addr: fe80::8efd:f0ff:fe06:90cd/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1010 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1086 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:100434 (100.4 KB)  TX bytes:171324 (171.3 KB)
  Interrupt:39 


** Tags removed: verification-needed-zesty
** Tags added: 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/1696143

Title:
  [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
  driver.

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  qcom_emac is unable to get ip address with at803x phy driver. Use software 
polling (PHY_POLL) to check for link state changes instead of relying on the 
EMAC's hardware polling feature.  Some PHY drivers are unable to get a 
functioning link because the HW polling is not robust enough.

  The emac interface is the onboard nic on the QDF2400 platform. A non
  working emac would be a cert blocker for this platform.

  [Test]
  Boot the netboot DI installer on QDF2400, and chose the emac interface, the 
install will fail because the emac interface is unable to get an IP lease. 
Also, on an installed system the emac driver is unable to get ip address.

  [Fix]
  Patch is in Dave Miller's 'net' repo: 
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/id=246096690be0742d9bb5f3456d2cb95b68f7b46d

  [Regression]
  The patch is to emac driver which is only available on the QDF2400 platform 
so there is no risk of regression to other ARM64 platforms or platforms based 
on other architectures. You can see detailed test results on the comments 
sections below.

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

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

[Kernel-packages] [Bug 1696165] Re: [SRU][Zesty] fix soft lockup on overcommited hugepages

[Manoj Iyer]

== Testing kernel in -proposed ==

The kernel installs and boots fine on the QDF2400 platform.

$ uname -a 
Linux awsdp0 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:33:10 UTC 2017 
aarch64 aarch64 aarch64 GNU/Linux

$ apt policy linux-image-4.10.0-28-generic
linux-image-4.10.0-28-generic:
  Installed: 4.10.0-28.32
  Candidate: 4.10.0-28.32
  Version table:
 *** 4.10.0-28.32 500
500 http://ports.ubuntu.com/ubuntu-ports zesty-proposed/main arm64 
Packages
100 /var/lib/dpkg/status

The testcase needs hwpoison-inject module to run. But it is not enabled
in the Configs by default.

$ sudo ./run_hugepage_overcommit.sh
sysctl: cannot stat /proc/sys/vm/memory_failure_early_kill: No such file or 
directory
modprobe: FATAL: Module hwpoison-inject not found in directory 
/lib/modules/4.10.0-28-generic
DIE: Failed to load hwpoison-inject module. Abort.
DIE: Failed to load hwpoison-inject module. Abort.

I can confirm that rebuilding the kernel with the hwpoison-inject
module, and running the test, the kernel does not get soft-lockups and
test works as expected.


** Tags removed: verification-needed-zesty
** Tags added: 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/1696165

Title:
  [SRU][Zesty] fix soft lockup on overcommited hugepages

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  On failing to migrate a page, soft_offline_huge_page() performs the necessary 
update to the hugepage ref-count.

  But when !hugepage_migration_supported() , unmap_and_move_hugepage()
  also decrements the page ref-count for the hugepage. The combined
  behaviour leaves the ref-count in an inconsistent state.

  This leads to soft lockups when running the overcommitted hugepage
  test from mce-tests suite

  [Testing]
  Run the mce-test/cases/function/hwpoison/run_hugepage_overcommit.sh and you 
should see softlock up if hugepage migration support is not enabled.

  [Fix]
  upstream commit:
  30809f559a0d mm/migrate: fix refcount handling when 
!hugepage_migration_supported()

  [Regression Potential]

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

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

[Kernel-packages] [Bug 1699172] Re: bitwig 1.3.16 don't open with linux 4.8.0-56-generic

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12

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

** Tags added: needs-bisect

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

Title:
  bitwig 1.3.16 don't open with linux 4.8.0-56-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi, I can't open Bitwig-Studio with the last kernel (Linux
  4.8.0-56-generic), and Ubuntu 16.04. If I change via GRUB the kernel
  to Linux 4.8.0-54-generic, Bitwig-Studio works perfectly.

  
  Another thing. Renoise work perfectly with both kernels.

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

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

[Kernel-packages] [Bug 1694167] Re: unity does not start when booting with 4.11.3 kernel

[Joseph Salisbury]

4.11.3 sounds like an upstream kernel.  Does this bug also happen with
the stock Ubuntu kernel?

** Tags added: kernel-da-key

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

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

Title:
  unity does not start when booting with 4.11.3 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed the recent 4.11.3 kernel from the packages downloaded from
  kernel.ubuntu.org

  After rebooting unity did not start properly. I had no dash, no
  decorations and no dock. After starting unity manually from the
  command line I got window decorations for a program that is run after
  login but nothing else.

  After switching back to 4.11.2 the system is working fine again.

  > lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  
  If you need further information please let me know!

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

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

[Kernel-packages] [Bug 1704374] Re: system randomly hangs itself

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12

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

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

Title:
  system randomly hangs itself

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this problem affect my system on Kubuntu 17.04 64bit
  Kde Plasma: 5.10.3
  kernel: 4.10.0.26
  Kde frameworks: 5.36.0
  Qt release: 5.7.1
  Probably I've solved with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash 
intel_idle.max_cstate=1"

  Randomly the operating system hangs both eist and or c1e options enabled or 
disabled. I hope that Kubuntu has not damaged my hardware. However what kind of 
workaround should be made on the klernel to have this problem solved once and 
forever?
  My hardware specs:
  maximus eteme;
  latest bios;
  8gb ram 4x2gb corsaire xms 1333;
  gigabyte gt 730 1gb OC
  xonar d2x.

  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
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  1353 F pulseaudio
   /dev/snd/controlC1:  james  1353 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jul 14 12:39:32 2017
  InstallationDate: Installed on 2017-04-25 (79 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer Maximus Extreme
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=52f9b441-fe75-4643-bbec-f912736d397b ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Maximus Extreme
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/24/2009:svnSystemmanufacturer:pnMaximusExtreme:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusExtreme:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: Maximus Extreme
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1704363] Re: Add firmware for Redpine 9113 chipset

[Joseph Salisbury]

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

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

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

Title:
  Add firmware for Redpine 9113 chipset

Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  Latest firmware images provided by Redpine in 1.2 production release
  are updated to ubuntu's linux-firmware.git

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

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

[Kernel-packages] [Bug 1704232] Re: Halt doesn't power system down

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12

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

** Tags added: kernel-da-key

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

Title:
  Halt doesn't power system down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Skylake Core i7 system running up-to-date 16.04.1 (4.4
  kernel).

  Whenever I issue a halt (either shutdown -h now, or halt) the shutdown
  process gets as far as showing the "Target shutdown reached" on the
  console, but instead of actually powering the system down, it just
  sits there idling.

  I have to manually power the system off by holding the power button
  down.

  What should happen, is that 'shutdown -h now' should actually shut the
  OS down and power the computer off without any further intervention.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-83-generic 4.4.0-83.106
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bladernr  28322 F pulseaudio
   /dev/snd/pcmC0D0p:   bladernr  28322 F...m pulseaudio
   /dev/snd/controlC0:  bladernr  28322 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 13 17:42:14 2017
  HibernationDevice: RESUME=UUID=0ca350ae-0a5d-4d84-9ac5-f0f83959aa62
  InstallationDate: Installed on 2016-02-11 (518 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  MachineType: Gigabyte Technology Co., Ltd. Z170MX-Gaming 5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed 
root=UUID=fa272e99-2333-4360-a2f3-edbde23a1fed ro quiet splash 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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1704343] Re: Ubuntu17.10: Changing guest timebase offset breaks host

[Joseph Salisbury]

** Tags added: kernel-da-key

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

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

** Also affects: linux (Ubuntu Artful)
   Importance: Medium
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
   Status: Triaged

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

Title:
  Ubuntu17.10: Changing guest timebase offset breaks host

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

Bug description:
  == Comment: #0 - NAGESWARA R. SASTRY  -
  2017-07-04 07:20:40 ==

  ---Problem Description---
  With little load on the system seeing kernel stack traces and soft lockup 
issues.
   
  Contact Information = nasas...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston25 4.12.0-041200rc6-generic #201706191233 SMP Mon Jun 19 
17:38:35 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Boston Power9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   With little load on the system seeing the stack trace. Start 2-3 guests or 
run some workload.
   
  Stack trace output:
   [56954.376790] NMI watchdog: BUG: soft lockup - CPU#44 stuck for 22s! [CPU 
3/KVM:48428]
  [56954.376949] Modules linked in: vhost_net vhost tap xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter input_leds joydev mac_hid idt_89hpesx 
at24 nvmem_core ofpart binfmt_misc cmdlinepart powernv_flash mtd 
uio_pdrv_genirq uio ibmpowernv opal_prd ipmi_powernv ipmi_devintf vmx_crypto 
ipmi_msghandler ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas
  [56954.377200]  hid_generic usbhid hid ast i2c_algo_bit ttm drm_kms_helper 
syscopyarea crct10dif_vpmsum sysfillrect crc32c_vpmsum sysimgblt fb_sys_fops 
drm i40e aacraid
  [56954.377263] CPU: 44 PID: 48428 Comm: CPU 3/KVM Not tainted 
4.12.0-041200rc6-generic #201706191233
  [56954.377269] task: c000200a74621000 task.stack: c000200a811cc000
  [56954.377277] NIP: c01a4464 LR: c01a4424 CTR: 
c008a970
  [56954.377283] REGS: c000200a811cf7c0 TRAP: 0901   Not tainted  
(4.12.0-041200rc6-generic)
  [56954.377287] MSR: 9280b033 
  [56954.377325]   CR: 48244224  XER: 2000
  [56954.377328] CFAR: c01a4470 SOFTE: 1
 GPR00: c01a4404 c000200a811cfa40 c1503800 
0022
 GPR04: 0022 0022  
0001
 GPR08: 0001 0003 c000200a95599518 
c1541ec0
 GPR12: c008a970 cfadce00
  [56954.377403] NIP [c01a4464] smp_call_function_many+0x374/0x400
  [56954.377414] LR [c01a4424] smp_call_function_many+0x334/0x400
  [56954.377417] Call Trace:
  [56954.377429] [c000200a811cfa40] [c01a4404] 
smp_call_function_many+0x314/0x400 (unreliable)
  [56954.377444] [c000200a811cfac0] [c01a462c] 
kick_all_cpus_sync+0x3c/0x50
  [56954.377459] [c000200a811cfae0] [c006e01c] pmdp_invalidate+0x7c/0xc0
  [56954.377473] [c000200a811cfb10] [c03315f4] 
change_huge_pmd+0x1d4/0x290
  [56954.377486] [c000200a811cfb80] [c02e59c8] 
change_protection_range+0xa38/0xcf0
  [56954.377500] [c000200a811cfcc0] [c030ff88] 
change_prot_numa+0x38/0xb0
  [56954.377514] [c000200a811cfcf0] [c0130584] 
task_numa_work+0x2c4/0x3e0
  [56954.377527] [c000200a811cfdb0] [c0115060] task_work_run+0x140/0x1a0
  [56954.377541] [c000200a811cfe00] [c001cd14] 
do_notify_resume+0xf4/0x100
  [56954.377556] [c000200a811cfe30] [c000b544] 
ret_from_except_lite+0x70/0x74
  [56954.377562] Instruction dump:
  [56954.377571] 409dfd80 3d420004 394aa580 78691f24 7d2a482a e95e 7d4a4a14 
812a0018
  [56954.377597] 71280001 4182001c 6042 7c210b78 <7c421378> 812a0018 
71270001 4082fff0
  [56998.366340] NMI watchdog: BUG: soft lockup - CPU#37 stuck for 22s! 
[qemu-system-ppc:47850]
  [56998.366461] Modules linked in: vhost_net vhost tap xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm ebtable_filter ebtables 
ip6table_filter ip6_tables 

[Kernel-packages] [Bug 1704287] Re: wifi on lenovo ideapad 310 does not work

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12

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

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

Title:
  wifi on lenovo ideapad 310 does not work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm having the same problem as the issue #1640194

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-28-generic 4.10.0-28.32
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   z-lmutt1319 F...m pulseaudio
   /dev/snd/controlC0:  z-lmutt1319 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jul 14 08:07:45 2017
  InstallationDate: Installed on 2017-06-29 (14 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 5986:06b1 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80SM
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=41018553-7104-4a7b-bee0-d926fad5969f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN36WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN36WW:bd08/30/2016:svnLENOVO:pn80SM:pvrLenovoideapad310-15ISK:rvnLENOVO:rnToronto5A2:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15ISK:
  dmi.product.name: 80SM
  dmi.product.version: Lenovo ideapad 310-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1704373] Re: operating system randomly hangs itself

[Joseph Salisbury]

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

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

** This bug has been marked a duplicate of bug 1704374
   system randomly hangs itself

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

Title:
  operating system randomly hangs itself

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this problem affect my system on Kubuntu 17.04 64bit
  Kde Plasma: 5.10.3
  kernel: 4.10.0.26
  Kde frameworks: 5.36.0
  Qt release: 5.7.1
  Probably I've solved with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash 
intel_idle.max_cstate=1"

  Randomly the operating system hangs both eist and or c1e options enabled or 
disabled. I hope that Kubuntu has not damaged my hardware. However what kind of 
workaround should be made on the klernel to have this problem solved once and 
forever?
  My hardware specs:
  maximus eteme;
  latest bios;
  8gb ram 4x2gb corsaire xms 1333;
  gigabyte gt 730 1gb OC
  xonar d2x.

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

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

[Kernel-packages] [Bug 1704177] Re: Flood on syslog

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12

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

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

Title:
  Flood on syslog

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Flood with messages like this:

  xhci_hcd :00:14.0: WARN Event TRB for slot 1 ep 8 with no TDs
  queued?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-83-generic 4.4.0-83.106
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-83-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Thu Jul 13 18:27:50 2017
  HibernationDevice: RESUME=UUID=e0eca0c3-f13a-4513-abc6-62782fcb58a5
  InstallationDate: Installed on 2017-05-30 (43 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 04e6:5116 SCM Microsystems, Inc. SCR331-LC1 / SCR3310 
SmartCard Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GIGABYTE GB-BACE-3150
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed 
root=UUID=f47774e8-2041-4a23-88a2-49a3c28f345d ro
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MZBSWBP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3150:pvr1.x:rvnGIGABYTE:rnMZBSWBP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GB-BACE-3150
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

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

[Kernel-packages] [Bug 1703396] Re: linux: 3.13.0-125.174 -proposed tracker

[Kleber Sacilotto de Souza]

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

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

Title:
  linux: 3.13.0-125.174 -proposed tracker

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

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: 1703397
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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