date:20170925

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

Title:
  fullscreen does not work correctly

Status in linux package in Ubuntu:
  Expired

Bug description:
  in fullscreen mode, after moving the mouse, the window is maximized
  instead

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cheese 3.18.1-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul 25 18:31:22 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-29 (1061 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. XPS13 9333
  RelatedPackageVersions:
   cheese3.18.1-2ubuntu3
   cheese-common 3.18.1-2ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  benedikt   2691 F pulseaudio
   /dev/snd/controlC0:  benedikt   2691 F pulseaudio
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=df019d1b-7a79-4508-bdfc-2c1166a87d38
  InstallationDate: Installed on 2014-08-29 (1061 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=UUID=0ded76d6-3843-4156-855c-8ae7a04cadc1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-87-generic N/A
   linux-backports-modules-4.4.0-87-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirtd lpadmin lxd plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1706275] Re: Kernel Panic from intel_dp_set_idle_link_train

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

Title:
  Kernel Panic from intel_dp_set_idle_link_train

Status in linux package in Ubuntu:
  Expired

Bug description:
  When putting my laptop on a docking station the system did not detect
  the external monitor attached via DP. I took the laptop of the station
  and put it back on. Still nothing happend so I decided to reboot the
  system. I opened a browser when the system froze. The mouse was still
  moving but X was dead in all other regards. To see whether something
  was alive I tried to switch to the console via Ctr-Alt-F1. Nothing
  happend for about 5 to 10 seconds and then the kernel panic came up. I
  took a quick photo of the screen which I attached.

  My system is running Ubuntu 17.04. I'm using an upstream kernel:

  Linux 4.11.11-04-generic #201707150838 SMP x86_64 x86_64 x86_64
  GNU/Linux

  My Laptop is a ThinkPad T460s and I'm using the graphics drivers from
  intel.

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

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

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

[Kernel-packages] [Bug 1706977] Re: Issues with Nvidia GeForce GT 240M. Can't define monitor and set proper resolution. Also, Redshift doesn't work.

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

Title:
  Issues with Nvidia GeForce GT 240M. Can't define monitor and set
  proper resolution. Also, Redshift doesn't work.

Status in linux package in Ubuntu:
  Expired

Bug description:
  Kernel: 4.4.0-87. Nvidia screen (after boot) has disappeared.
  System: Linux Mint 18.1 MATE
  Laptop: Fujitsu Amilo Pi 3560

  I'm using 4.4.0-72 kernel for now with no such issues.

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

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

[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

2017-09-25 Thread Kai-Heng Feng

Okay, you also need to add more data to
/usr/share/usb_modeswitch/configPack.tar.gz.

$ cat 148f\:2878 
# RaLink MT7601U
TargetVendor=0x148f
TargetProduct=0x7601
StandardEject=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/1716301

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  New

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110
  [ 4757.730870] usbcore: registered new interface driver mt7601u
  // end

[Kernel-packages] [Bug 1712765] Re: reboot instead of shutdown

2017-09-25 Thread Kai-Heng Feng

Does the BIOS have anything related to autoboot? e.g. Wake of Lan. Try
to disable them in the BIOS may help.

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

Title:
  reboot instead of shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Acer Aspire v5 571g laptop which initially had Windows
  installed. After I installed Ubuntu (and overwrote Windows) the
  computer shuts down when a restart is requested. Windows did not
  exhibit this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   felix  1929 F...m pulseaudio
   /dev/snd/controlC0:  felix  1929 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Aug 24 10:24:56 2017
  HibernationDevice: RESUME=UUID=9aa9aa29-eb16-473f-b28d-5d6c340eac81
  InstallationDate: Installed on 2017-06-14 (70 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Acer Aspire V5-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/12/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.12
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV1.12:bd06/12/2012:svnAcer:pnAspireV5-571G:pvrV1.12:rvnAcer:rnAspireV5-571G:rvrV1.12:cvnAcer:ct9:cvrV1.12:
  dmi.product.name: Aspire V5-571G
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1718936] Re: Can't boot Artful 17.10 live images on XPS 15 (9560)

2017-09-25 Thread Kai-Heng Feng

Can you add this to your kernel parameters "blacklist=nouveau
modprobe.blacklist=nouveau" and try 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/1718936

Title:
  Can't boot Artful 17.10 live images on XPS 15 (9560)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I usually test Ubuntu beta releases. With Artful, I haven't been able
  to boot the image on my XPS 15 (9560) Dell laptop because the boot
  process stops half way.

  The boot proceeds properly if I pass the "nomodeset" kernel boot
  option but that won't work because there is no more hiDPI support and
  dual display doesn't work.

  This has been ongoing for several weeks, around the 4.12 kernel.
  Please fix it. It would be a shame for this product not to boot Artful
  out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1701 F pulseaudio
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 12:38:09 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170921)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

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

2017-09-25 Thread NancyHsu

The bug didn't happened on test kernel 4.1.0-1.
 Test step:
 1. PXE install Ubuntu 16.04.3.
 2. Downgrade kernel to 4.1.0-1.
 3. The screen goes normally after a reboot.

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1709179] Re: Drop GPL from of_node_to_nid() export to match other arches

2017-09-25 Thread bugproxy

--- Comment From ar...@us.ibm.com 2017-09-25 21:12 EDT---
(In reply to comment #13)
> This bug is awaiting verification that the kernel in -proposed solves the
> problem. Please test the kernel and update this bug with the results. If the
> problem is solved, change the tag 'verification-needed-zesty' to
> 'verification-done-zesty'. If the problem still exists, change the tag
> 'verification-needed-zesty' to 'verification-failed-zesty'.

I verified that linux-image-4.10.0-36-generic/zesty-proposed has this
fix.

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

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

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

Bug description:
  == SRU Justification ==
  The commit requested in this bug exposes functionality needed by the Nvidia 
device driver on POWER9.

  This patch is a clean cherry pick and specific to powerpc.

  This commit is in mainline as of 4.11-rc1.

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

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

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

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

[Kernel-packages] [Bug 1714783] Re: [amdgpu] screen scrambling upon startup

2017-09-25 Thread Charlie Luna

I'm trying to update all of my bug reports per your request to do so.
It's just taking some time to get to it. So far, this particular
instance hasn't occurred 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/1714783

Title:
  [amdgpu] screen scrambling upon startup

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue just happened with this beta 1 release. This was during a
  cold startup. I'll retry a cold startup after this to see if the
  problem is replicated and then I'll make comments in regards to that
  investigation. I'm including a pic of what happened. I apologize for
  the flash, it's automatic on my phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 07:12:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-01 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-01 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Tags:  artful
  Uname: Linux 4.13.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714783/+subscriptions

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

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

2017-09-25 Thread @Spazm

Hit by this today after updating packages on ubuntu 17.10 running on dell 9360.
This upgraded the kernel to '4.13.0-11-generic #12-Ubuntu SMP'

The same pcieport messages as dan-mulholland was seeing.

[ 1423.748011] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e4(Transmitter ID)
[ 1423.748015] pcieport :00:1c.4:   device [8086:9d14] error 
status/mask=1000/2000
[ 1423.748017] pcieport :00:1c.4:[12] Replay Timer Timeout  
[ 1428.702571] pcieport :00:1c.4: AER: Corrected error received: id=00e4
[ 1428.702577] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e4(Transmitter ID)
...

% lcpci | grep 1c.4

00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root
Port #5 (rev f1)

Will try with a stock kernel.

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

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

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

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

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

  

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

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

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

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

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

Re: [Kernel-packages] [Bug 1718936] Re: Can't boot Artful 17.10 live images on XPS 15 (9560)

2017-09-25 Thread Anmar Oueja

I just tried today's image and I it isn't booting still. Like Joseph, I
tried

On Mon, Sep 25, 2017 at 11:18 AM, Joseph Salisbury
 wrote:
> Can you see if this issue also happens with the latest daily image?  It can 
> be downloaded from:
> Desktop:
> http://cdimage.ubuntu.com/daily-live/current/
> Server:
> http://cdimage.ubuntu.com/ubuntu-server/daily/current/
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => High
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> ** Tags added: kernel-da-key
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1718936
>
> Title:
>   Can't boot Artful 17.10 live images on XPS 15 (9560)
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I usually test Ubuntu beta releases. With Artful, I haven't been able
>   to boot the image on my XPS 15 (9560) Dell laptop because the boot
>   process stops half way.
>
>   The boot proceeds properly if I pass the "nomodeset" kernel boot
>   option but that won't work because there is no more hiDPI support and
>   dual display doesn't work.
>
>   This has been ongoing for several weeks, around the 4.12 kernel.
>   Please fix it. It would be a shame for this product not to boot Artful
>   out of the box.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: linux-image-4.13.0-11-generic 4.13.0-11.12
>   ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
>   Uname: Linux 4.13.0-11-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu1
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  ubuntu 1701 F pulseaudio
>   CasperVersion: 1.384
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Sep 22 12:38:09 2017
>   LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170921)
>   MachineType: Dell Inc. XPS 15 9560
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 EFI VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
> file=/cdrom/preseed/username.seed boot=casper quiet splash --- nomodeset
>   RelatedPackageVersions:
>linux-restricted-modules-4.13.0-11-generic N/A
>linux-backports-modules-4.13.0-11-generic  N/A
>linux-firmware 1.168
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/30/2017
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.5.0
>   dmi.board.name: 0JHP5H
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: 
> dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.family: XPS
>   dmi.product.name: XPS 15 9560
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718936/+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/1718936

Title:
  Can't boot Artful 17.10 live images on XPS 15 (9560)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I usually test Ubuntu beta releases. With Artful, I haven't been able
  to boot the image on my XPS 15 (9560) Dell laptop because the boot
  process stops half way.

  The boot proceeds properly if I pass the "nomodeset" kernel boot
  option but that won't work because there is no more hiDPI support and
  dual display doesn't work.

  This has been ongoing for several weeks, around the 4.12 kernel.
  Please fix it. It would be a shame for this product not to boot Artful
  out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1701 F pulseaudio
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 12:38:09 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170921)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably

[Kernel-packages] [Bug 1718713] Re: upon reboot monitor came up with flickerty screen

2017-09-25 Thread ventrical

tested 4.14. .x-x kernel. no network but flickerty not there.

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

** Tags added: kernek-fixed-updtream

** Tags removed: kernek-fixed-updtream
** Tags added: kerne-fixed-updtream

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

Title:
  upon reboot monitor came up with flickerty screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the  upgrade of kernel and reboot the VT went black with one
  line of verbose code  then started to flash  with full screen of code
  at least 6 times , top down, bottom up. Then gdm screen and was able
  to logon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ventrical   1935 F pulseaudio
   /dev/snd/controlC0:  ventrical   1935 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Sep 21 11:26:13 2017
  HibernationDevice: RESUME=UUID=73906ed5-985c-4166-9fc2-13fb389012cf
  InstallationDate: Installed on 2017-09-05 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Dell Inc. Precision WorkStation T3400
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=cdef7dd2-7ccb-446a-a39a-df77fea13ef0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0TP412
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd01/31/2008:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T3400
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1718980] Re: linux: 4.13.0-12.13 -proposed tracker

** Changed in: kernel-development-workflow/automated-testing
   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/1718980

Title:
  linux: 4.13.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

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

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

  -- swm properties --
  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-development-workflow/+bug/1718980/+subscriptions

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

[Kernel-packages] [Bug 1711358] Re: 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver

2017-09-25 Thread Jean-Baptiste Lallement

This bug is also reproducible with the end user stage of an OEM
installation which runs ubiquity-dm like a boot from an ISO.

I think 4.14 (from Canonical kernel team's ppa) fixes the issue. I
installed this kernel during the OEM prepare stage, then the image boots
fine during the end user setup.

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

Title:
  20170817 - ISO hangs on boot on qemu with splash screen enabled and
  qxl graphics driver

Status in linux package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Test Case
  1. Boot artful desktop 20170817 under qemu with qxl
  2. Wait until ubiquity-dm is displayed

  Expected result
  It boots

  Actual result
  It hangs on the splash screen and the dots below the Ubuntu logo are not 
blinking. If the option 'splash' is removed from the boot command line it boots 
successfully.

  It also boots successfully with -vga std but in this case the splash
  screen is in text mode not graphical unlike with the qxl driver.

  - It started with kernel 4.12.
  - It is still happening with kernel 4.13.
  - It only happens when booting from an ISO and not on an installed system.
  - It works with cirrus/vga, but not qxl
  - It works if nosplash is set (or splash removed from the boot command line)
  - It works on Xenial but not on Artful

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

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

[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard

2017-09-25 Thread Ubiratan Pires Alberton

I am on 17.04 - I've just installed the proposed kernel (4.10.36) and
verified that it does indeed solve my problem. My keyboard works through
multiple reboots and "re-pluggings" as described above.

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

Title:
  Kernel has troule recognizing Corsair Strafe RGB keyboard

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

Bug description:
  I recently bought a Corsair Strafe RGB keyboard, and while it works
  well when successfully recognized by Ubuntu at boot, that doesn't
  always happen.

  I see messages like this when booting my desktop up:

  [6.619510] usb 3-10: unable to read config index 0 descriptor/all
  [6.619543] usb 3-10: can't read configurations, error -110

  They sometimes repeat at 5-second intervals, culminating on a "can't
  set config #1" message or even "unable to enumerate USB device". This
  happens on the logic that deals with a new USB device being connected,
  so when it doesn't work it never gets to the HID drivers part of the
  code. When it does, hid-generic is quite able to control the keyboard,
  though this message appears on dmesg:

  [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt
  endpoint

  
  From what I have been able to determine, the Corsair Strafe RGB has three 
inputs, with the last one being used as input/output and having something to do 
with the LEDs. It only has a single USB configuration, though I don't know why 
it times out.

  Searching on Google has a lot of people recommending this userspace
  drive to me: https://github.com/mattanger/ckb-next , and I've tried
  it, but it seems to be more about programming lighting effects into
  the keyboard than in controlling its basic operation, which is all I'm
  interested in. Its daemon was supposed to handle that part too, but it
  didn't fix those connection errors on boot.

  I have the following boot parameter set in my kernel, following advice
  from ckb-next's README, but it doesn't see to have an appreciable
  effect on my success rate:

  usbhid.quirks=0x1B1C:0x1B20:0x2448

  ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT
  as well in an attempt to improve things, without success.

  GRUB is always able to correctly identify the keyboard and get it to
  work, too, which makes the fact that the full kernel can't always do
  it a little more frustrating.

  I would be happy to provide any extra information you require on this
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-45-generic 4.8.0-45.48
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bira   2322 F pulseaudio
   /dev/snd/controlC0:  bira   2322 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Apr  1 10:23:52 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-24 (767 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic 
root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash 
usbhid.quirks=0x1B1C:0x1B20:0x2448
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-45-generic N/A
   linux-backports-modules-4.8.0-45-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/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: Z97M-D3H
  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: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97M-D3H
  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/1678477/+subscriptions

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

[Kernel-packages] [Bug 1717796] Re: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle

2017-09-25 Thread Daniel van Vugt

Thanks. Unfortunately it appears bluetoothd is a single-threaded program
spinning its g_main_loop without actually doing any heavy work on each
iteration. This makes it hard to identify the cause of the problem
without running it through a profiler.

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

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

Title:
  Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle

Status in bluez package in Ubuntu:
  New

Bug description:
  When bluetooth keyboard goes in idle bluetoothd fills 100% CPU. At
  this point you have to press any key to reconnect the device and let
  bluetoothd to return to work normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Sep 17 19:02:40 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2016-08-06 (406 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: GIGABYTE GB-BXBT-2807
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed 
root=UUID=8931ead4-8d43-4aef-8946-c7845c63c7d3 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MZBAYAP-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.:bvrF8:bd10/22/2015:svnGIGABYTE:pnGB-BXBT-2807:pvr1.x:rvnGIGABYTE:rnMZBAYAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GB-BXBT-2807
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: DC:85:DE:FD:2F:BC  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN ISCAN 
RX bytes:528225 acl:32183 sco:0 events:1134 errors:0
TX bytes:33849 acl:338 sco:0 commands:388 errors:1

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

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

[Kernel-packages] [Bug 1718143] Re: linux: 4.10.0-36.40 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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/1718143

Title:
  linux: 4.10.0-36.40 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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: 1718145,1718146
  derivatives: 1718147
  -- 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/1718143/+subscriptions

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

[Kernel-packages] [Bug 1718980] Re: linux: 4.13.0-12.13 -proposed tracker

** Changed in: kernel-development-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-development-workflow/regression-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.13.0-12.13 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-phase:Promoted to proposed
+ kernel-phase-changed:Monday, 25. September 2017 21:32 UTC

** Description changed:

  This bug is for tracking the 4.13.0-12.13 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-phase:Promoted to proposed
- kernel-phase-changed:Monday, 25. September 2017 21:32 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.13.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

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

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

  -- swm properties --
  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-development-workflow/+bug/1718980/+subscriptions

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

[Kernel-packages] [Bug 1719031] Re: sata reset hangs w/ early cn99xx silicon

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

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

Title:
  sata reset hangs w/ early cn99xx silicon

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Early silicon in Cavium cn99xx (previously known as Broadcom Vulcan)
  systems has an errata that can result in SATA hangs. Since this will
  be fixed in later silicon, and the impacted silicon will have a very
  limited distribution/life span for non-production scenarios, there is
  no plan to push a fix upstream. However, it would be valuable for
  users evaluating this silicon if Ubuntu could carry a workaround for
  this issue for the 17.10 cycle.

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

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

[Kernel-packages] [Bug 1716091] Re: Please make linux-libc-dev Provide: aufs-dev

** Tags removed: kernel-key

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

Title:
  Please make linux-libc-dev Provide: aufs-dev

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  The aufs-tools package build-depends on aufs-dev, which is a separate
  package in Debian.  Since the Ubuntu kernel includes aufs, the only
  aufs header, /usr/include/linux/aufs_type.h, is already shipped by
  linux-libc-dev.  Please have linux-libc-dev declare Provides: aufs-dev
  so that this package is buildable in Ubuntu.

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

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

[Kernel-packages] [Bug 1695780] Re: On VMware ESXi with PCI passthru enabled for Intel NVMe Ubuntu Xenial VM does not boot

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

Title:
  On VMware ESXi with PCI passthru enabled for Intel NVMe Ubuntu Xenial
  VM does not boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My set up is a Cisco UCS c240 server with an Intel NVMe 1.6TB drive
  running VMware ESXi version 6.0U2. NVMe device is made available as a
  PCI passthru device and not claimed by ESXi kernel. This NVMe device
  when added to a Ubuntu 16.04.2 running kernel version 4.4.0-62 and
  above does not boot, kernel does not boot fully and hangs for while
  before the VM powers off. However, running kernel versions 4.4.0-43,
  4.4.0-53, 4.4.0-57, and 4.4.0-59 everything works as expected. Earlier
  versions of the kernel also do not work. Here is a short list of the I
  tested with

  4.4.0-31 -> kernel panic (different issue)
  4.4.0-43 -> works
  4.4.0-53 -> works
  4.4.0-57 -> works
  4.4.0-59 -> works
  4.4.0-62 -> fail
  4.4.0-64 -> fail
  4.4.0-75 -> fail
  4.4.0-77 -> fail
  4.8.0-51 -> fail

  ~# cat /proc/version_signature
  Ubuntu 4.4.0-75.96-generic 4.4.59

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

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

[Kernel-packages] [Bug 1701892] Re: [Artful] mlx5e-Introduce RX Page-Reuse

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

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

Title:
  [Artful] mlx5e-Introduce RX Page-Reuse

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

Bug description:
  This feature is a Page-Reuse mechanism in non-Striding RQ RX datapath.
  A WQE (RX descriptor) buffer is a page, that in most cases was fully
  wasted on a packet that is much smaller, requiring a new page for
  the next round.

  In this feature, we implement a page-reuse mechanism, that resembles a
  `SW Striding RQ`.
  We allow the WQE to reuse its allocated page as much as it could,
  until the page is fully consumed.  In each round, the WQE is capable
  of receiving packet of maximal size (MTU). Yet, upon the reception of
  a packet, the WQE knows the actual packet size, and consumes the exact
  amount of memory needed to build a linear SKB. Then, it updates the
  buffer pointer within the page accordingly, for the next round.

  Feature is mutually exclusive with XDP (packet-per-page)
  and LRO (session size is a power of two, needs unused page).

   Upstream acceptance Commits

  accd58833237 net/mlx5e: Introduce RX Page-Reuse
  bce2b2bf6682 net/mlx5e: Enhance RX SKB headroom logic
  78aedd327982 net/mlx5e: Build SKB with exact frag_size

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

-- 
Mailing list: https://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 1718684] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000070

2017-09-25 Thread Scott A Bowman

This happened once after a clean install and doing update/upgrade for 
Artful daily build.

After testing the 4.14 rc2 kernel version, it seemed to have resolved 
the issue

kernel-fixed-upstream

On 09/25/2017 01:55 PM, Joseph Salisbury wrote:
> 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
> tohttps://wiki.ubuntu.com/KernelMainlineBuilds  . Please test the latest
> v4.14 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.14-rc2/
>
> ** 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/1718684

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just extracting a tar.xz ball.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1004 F pulseaudio
scott  1403 F pulseaudio
  Date: Thu Sep 21 09:35:20 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: 0010:vbox_crtc_mode_set+0x41a/0x4c0 [vboxvideo]
  Failure: oops
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  IwConfig:
   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic.efi.signed 
root=UUID=99d714bd-8d7f-49b9-9521-9196afff16c4 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: kerneloops-daemon N/A
  RfKill:

  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0070
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1718760] Re: PCI quirk required for SATA on early cn99xx silicon

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

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

Title:
  PCI quirk required for SATA on early cn99xx silicon

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Early silicon in Cavium cn99xx (previously known as Broadcom Vulcan)
  systems requires a PCI quirk for SATA to work. Since this will be
  fixed in later silicon, and the impacted silicon will have a very
  limited distribution/life span for non-production scenarios, there is
  no plan to push a fix upstream. However, it would be valuable for
  users evaluating this silicon if Ubuntu could carry the quirk patch
  for the 17.10 cycle.

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

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

[Kernel-packages] [Bug 1705099] Re: Kernel 4.13-rc1 with custom patch for troubleshooting

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

Title:
  Kernel 4.13-rc1 with custom patch for troubleshooting

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I kindly got offered to have a kernel built for me with a custom
  patch.

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

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

[Kernel-packages] [Bug 1664663] Re: [Hyper-V] kvp daemon start failure on Zesty

It's been a while since this bug was updated.  Does this bug still
exist, Chris?

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

Title:
  [Hyper-V] kvp daemon start failure on Zesty

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

Bug description:
  Hello,

  On Ubuntu Server 17.04 daily from Febr 14th we see that the KVP daemon
  although it is enabled in systemd, it fails to start at system boot.

  This is shown by error: "KVP: read failed; error:9 Bad file
  descriptor"

  I then manually ran the kvp binary, it returned the KVP data, and it's also 
automatically loading at boot. However, this is of course not the normal 
behavior.
  17.04 daily from Febr 14th is the first build we covered, so I cannot say if 
this is a regression introduced only at some point in 17.04 dailies.

  In syslog these are the only messages for KVP:
  Feb 14 08:01:22 ubuntu systemd[1]: Started Hyper-V KVP Protocol Daemon.
  Feb 14 08:01:22 ubuntu KVP: KVP starting; pid is:1837
  Feb 14 08:01:22 ubuntu KVP: KVP LIC Version: 3.1
  Feb 14 08:02:31 ubuntu KVP: read failed; error:9 Bad file descriptor

  
  systemd status:
  root@ubuntu:~# systemctl status hv-kvp-daemon.service
  ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
 Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Tue 2017-02-14 08:02:31 PST; 1min 
41s ago
   Main PID: 1837 (code=exited, status=1/FAILURE)
CPU: 4ms

  Feb 14 08:01:22 ubuntu systemd[1]: Started Hyper-V KVP Protocol Daemon.
  Feb 14 08:01:22 ubuntu KVP[1837]: KVP starting; pid is:1837
  Feb 14 08:01:22 ubuntu KVP[1837]: KVP LIC Version: 3.1
  Feb 14 08:02:31 ubuntu systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 14 08:02:31 ubuntu systemd[1]: hv-kvp-daemon.service: Unit entered failed 
state.
  Feb 14 08:02:31 ubuntu systemd[1]: hv-kvp-daemon.service: Failed with result 
'exit-code'.

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

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

[Kernel-packages] [Bug 1712765] Re: reboot instead of shutdown

2017-09-25 Thread Felix

Thanks for your suggestions. I tried them all for 4.10.0-35-generic and
4.14.0-rc2 without any change to the issues. I noticed that the shutdown
(until the power LED turns off) is very quick (1 to 2 seconds). The
delay between shutdown and the unwanted reboot is about 3 seconds.

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

Title:
  reboot instead of shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Acer Aspire v5 571g laptop which initially had Windows
  installed. After I installed Ubuntu (and overwrote Windows) the
  computer shuts down when a restart is requested. Windows did not
  exhibit this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   felix  1929 F...m pulseaudio
   /dev/snd/controlC0:  felix  1929 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Aug 24 10:24:56 2017
  HibernationDevice: RESUME=UUID=9aa9aa29-eb16-473f-b28d-5d6c340eac81
  InstallationDate: Installed on 2017-06-14 (70 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Acer Aspire V5-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/12/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.12
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV1.12:bd06/12/2012:svnAcer:pnAspireV5-571G:pvrV1.12:rvnAcer:rnAspireV5-571G:rvrV1.12:cvnAcer:ct9:cvrV1.12:
  dmi.product.name: Aspire V5-571G
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1700980] Re: Invalid EA on pre 4.9 kernels

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

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

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

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

Title:
  Invalid EA on pre 4.9 kernels

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

Bug description:
  == Comment: #0 - Breno Leitao  - 2017-06-28 08:00:40 ==
  When a process accesses an invalid EA it results in a SEGV signal being
  sent to the process, which typically results in the process being
  killed. Process death isn't instantaneous however, the process may catch
  the SEGV signal and continue somehow, or the kernel may start writing a
  core dump for the process, either of which means it's possible for the
  process to be preempted while its processing the SEGV but before it's
  been killed.

  We need to have this fix on kernel 4.4 and 4.8:

  https://patchwork.ozlabs.org/patch/779346/

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

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

[Kernel-packages] [Bug 1716091] Re: Please make linux-libc-dev Provide: aufs-dev

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

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

Title:
  Please make linux-libc-dev Provide: aufs-dev

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  The aufs-tools package build-depends on aufs-dev, which is a separate
  package in Debian.  Since the Ubuntu kernel includes aufs, the only
  aufs header, /usr/include/linux/aufs_type.h, is already shipped by
  linux-libc-dev.  Please have linux-libc-dev declare Provides: aufs-dev
  so that this package is buildable in Ubuntu.

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

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

[Kernel-packages] [Bug 1706033] Re: [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results in call traces and system goes for reboot.

Breno,

Could you please test with the kernel provided to you by the kernel team
and report back here?

** Changed in: ubuntu-power-systems
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Breno Leitão 
(breno-leitao)

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

Title:
  [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command
  results in call traces and system goes for reboot.

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni <> - 2017-06-14 04:38:16 ==
  Problem Description :
  =
   
  While running perftool - testsuite, the perf hw breakpoint fails and it 
result in call traces , hence system goes for reboot .

  Machine details :
  ==
  System : P9 , WSP , Bare metal.
  OS : Ubuntu 16.04.03
  uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 
9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Install perf.
  2. git clone perftool-testsuite.
  https://github.com/rfmvh/perftool-testsuite
  3. Do make.
  4. Test fails at step : -- [ FAIL ] -- perf_stat :: test_hw_breakpoints :: 
kspace address execution mem:0xc035c020:x (command exitcode + output 
regexp parsing
  and call trace is seen as system goes for reboot.

  Call traces :
  ===

  ubuntu@ltc-wspoon3:~$ [1602513.518414] Unable to handle kernel paging request 
for data at address 0xc135d3b8
  [1602513.518553] Faulting instruction address: 0xc02869bc
  [1602513.518694] Oops: Kernel access of bad area, sig: 11 [#1]
  [1602513.518782] SMP NR_CPUS=2048 
  [1602513.518784] NUMA 
  [1602513.518842] PowerNV
  [1602513.518922] Modules linked in: vmx_crypto ofpart ipmi_powernv 
cmdlinepart ipmi_devintf powernv_flash ipmi_msghandler ibmpowernv opal_prd mtd 
at24 nvmem_core uio_pdrv_genirq uio autofs4 ast i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops crc32c_vpmsum ttm drm tg3 ahci 
libahci
  [1602513.519399] CPU: 27 PID: 4069 Comm: sysctl Not tainted 4.10.0-22-generic 
#24
  [1602513.519524] task: c000203968c42c00 task.stack: c00020396571
  [1602513.519624] NIP: c02869bc LR: c03f7348 CTR: 
c0286990
  [1602513.519747] REGS: c000203965713a40 TRAP: 0300   Not tainted  
(4.10.0-22-generic)
  [1602513.519876] MSR: 90009033 
  [1602513.519889]   CR: 22002448  XER: 
  [1602513.520058] CFAR: c03f7344 DAR: c135d3b8 DSISR: 0040 
SOFTE: 1 
  [1602513.520058] GPR00: c03f7348 c000203965713cc0 c145d100 
c134af00 
  [1602513.520058] GPR04:  4ee50300 c000203965713d20 
c000203965713e00 
  [1602513.520058] GPR08:  c135d100  
c0b71020 
  [1602513.520058] GPR12: c0286990 c7b4f300  
 
  [1602513.520058] GPR16:    
 
  [1602513.520058] GPR20:    
0001 
  [1602513.520058] GPR24: 3fffc542f5a0 0400 c000203965713e00 
4ee50300 
  [1602513.520058] GPR28: c134af00  c03fee038800 
 
  [1602513.521280] NIP [c02869bc] dirty_ratio_handler+0x2c/0x90
  [1602513.521374] LR [c03f7348] proc_sys_call_handler+0x138/0x1c0
  [1602513.521481] Call Trace:
  [1602513.521526] [c000203965713cc0] [c000203965713d00] 0xc000203965713d00 
(unreliable)
  [1602513.521655] [c000203965713d00] [c03f7348] 
proc_sys_call_handler+0x138/0x1c0
  [1602513.521797] [c000203965713d70] [c03436ec] __vfs_read+0x3c/0x70
  [1602513.521907] [c000203965713d90] [c034516c] vfs_read+0xbc/0x1b0
  [1602513.522016] [c000203965713de0] [c0346dd8] SyS_read+0x68/0x110
  [1602513.522112] [c000203965713e30] [c000b184] system_call+0x38/0xe0
  [1602513.522243] Instruction dump:
  [1602513.522303] 6042 3c4c011d 38426770 7c0802a6 6000 7c0802a6 
fbc1fff0 fbe1fff8 
  [1602513.522445] f8010010 f821ffc1 3d22fff0 7c9f2378  4be66da9 
6000 3d22fff0 
  [1602513.522564] ---[ end trace 17c76e13e641d3c6 ]---
  [1602513.522657] 

  It goes for reboot :

  After booting to Ubuntu , I see series of call traces.

  Ubuntu 16.04.2 LTS ltc-wspoon3 hvc0

  ltc-wspoon3 login: [ 3476.626263] Unable to handle kernel paging request for 
data at address 0xc13ad438
  [ 3476.626422] Faulting instruction address: 0xc029a140
  [ 3476.626537] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 3476.626615] SMP NR_CPUS=2048 
  [ 3476.626616] NUMA 
  [ 3476.626673] PowerNV
  [ 3476.626746] Modules linked in: ipmi_powernv at24 ipmi_devintf nvmem_core 
ipmi_msghandler ofpart

[Kernel-packages] [Bug 1678745] Re: Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c

** Changed in: ubuntu-power-systems
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Breno Leitão 
(breno-leitao)

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

Title:
  Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c

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

Bug description:
  == Comment: #0 - Lata Kuntal  - 2017-03-30 09:44:23 ==
  Ubuntu 17.04 KVM guest gusg8 was having ubuntu 16.04.2 and was running stress 
test IO, Base,TCP and NFS.The guest is having XFS as rootFS and after running 
few hours of regression test it dropped at xmon.

  Console logs :
  
  root@guskvm:~# virsh console gusg8 --force
  Connected to domain gusg8
  Escape character is ^]

  
  1:mon> r
  R00 = d288edf4   R16 = 024200ca
  R01 = c000378cb1f0   R17 = 
  R02 = d2936080   R18 = 0020
  R03 = 0001   R19 = c002734d1800
  R04 = c000378cb190   R20 = 
  R05 =    R21 = 
  R06 = 3c00d03fe056   R22 = c0027e26ccf0
  R07 =    R23 = 
  R08 = c48492d0   R24 = 
  R09 = 3c00d03fe056   R25 = 
  R10 = 3c00d03fe062   R26 = 00024df4cd49
  R11 = d28fa360   R27 = 
  R12 =    R28 = d28ac7b0
  R13 = cfb80900   R29 = c4849000
  R14 =    R30 = 
  R15 = c137ad08   R31 = 
  pc  = d288ee0c xfs_perag_get_tag+0x6c/0x170 [xfs]
  cfar= c096a494 perf_trace_mmc_request_start+0x104/0x440
  lr  = d288edf4 xfs_perag_get_tag+0x54/0x170 [xfs]
  msr = 80010280b033   cr  = 82428424
  ctr = c05e4950   xer = 2000   trap =  300
  dar = 3c00d03fe062   dsisr = 4000
  1:mon> t
  [c000378cb250] d28ac7b0 xfs_reclaim_inodes_count+0x70/0xa0 [xfs]
  [c000378cb290] d28c0ea8 xfs_fs_nr_cached_objects+0x28/0x40 [xfs]
  [c000378cb2b0] c03292d8 super_cache_count+0x68/0x120
  [c000378cb2f0] c0271530 shrink_slab.part.14+0x150/0x4f0
  [c000378cb430] c0276db8 shrink_node+0x158/0x3f0
  [c000378cb4f0] c0277178 do_try_to_free_pages+0x128/0x460
  [c000378cb590] c02775ac try_to_free_pages+0xfc/0x280
  [c000378cb620] c0260158 __alloc_pages_nodemask+0x758/0xe30
  [c000378cb7e0] c02dbb98 alloc_pages_vma+0x108/0x360
  [c000378cb880] c029d080 wp_page_copy+0xf0/0x9d0
  [c000378cb920] c02a0770 do_wp_page+0x210/0xb20
  [c000378cb9b0] c02a656c handle_mm_fault+0x9cc/0x14c0
  [c000378cba60] c0b511a0 do_page_fault+0x260/0x7d0
  [c000378cbb10] c0008948 handle_page_fault+0x10/0x30
  --- Exception: 301 (Data Access) at c010aec4 schedule_tail+0x84/0xb0
  [c000378cbe30] c0009844 ret_from_fork+0x4/0x54
  --- Exception: c00 (System Call) at 3fffa2b5bf44
  1:mon> d
      ||
  1:mon> c
  cpus stopped: 0x0-0x3
  1:mon>

  Kernel host build
  =
  root@guskvm:~# uname -r
  4.10.0-13-generic
  root@guskvm:~#

  
  == Comment: #1 - Luciano Chavez  - 2017-03-30 10:42:15 ==
  At first glance, based on the following assembly from around the failure 
point:

  d288edd4  38c1  li  r6,1
  d288edd8  7f8802a6  mflrr28
  d288eddc  78a70020  clrldi  r7,r5,32
  d288ede0  7c7d1b78  mr  r29,r3
  d288ede4  7c852378  mr  r5,r4
  d288ede8  386302c8  addir3,r3,712
  d288edec  38810020  addir4,r1,32
  d288edf0  4806b571  bl  d28fa360# 
exit_xfs_fs+0x180c/0xfd44 [xfs]
  d288edf4  e8410018  ld  r2,24(r1)
  d288edf8  2f83  cmpwi   cr7,r3,0
  d288edfc  409d0104  ble cr7,d288ef00# 
xfs_perag_get_tag+0x160/0x170 [xfs]
  d288ee00  7c0004ac  sync
  d288ee04  e9210020  ld  r9,32(r1)
  d288ee08  3949000c  addir10,r9,12
  d288ee0c  7fc05028  lwarx   r30,0,r10
  d288ee10  33de0001  addic   r30,r30,1
  d288ee14  7fc0512d  stwcx.  r30,0,r10

  I believe the crash in fs_perag_get_tag() is after we come back from
  the radix_tree_gang_lookup_tag() call and are attempting the
  atomic_inc_return() and struct xfs_perag*pag is R09 =
  3c00d03fe056 which is invalid.

   85 rcu_read_lock();  
 
   86 found = radix_tree_gang_lookup_tag(>m_perag_tree,

[Kernel-packages] [Bug 1649513] Re: [Ubuntu 16.10] NMI watchdog and soft lockup while running htx memory tests in kernel 4.8.0-17-generic

Please note that release 16.10 is no longer supported, if this problem
is still valid for 16.04.3 or in the latest development release please
open a separate bug.

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

** Changed in: ubuntu-power-systems
   Status: Incomplete => Invalid

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

Title:
  [Ubuntu 16.10] NMI watchdog and soft lockup while running htx memory
  tests in kernel 4.8.0-17-generic

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

Bug description:
  Issue:
  --
  NMI Watchdog Bug and soft lockup occurs when htx memory test is run in ubuntu 
16.10.

  Environment:
  --
  Arch : ppc64le
  Platform : Ubuntu KVM Guest
  Host : ubuntu 16.10 [4.8.0-17 -kernel ]
  Guest : ubuntu 16.10 [4.8.0-17 - Kernel]

  Steps To Reproduce:
  ---

  1 - Install a Ubuntu KVM Guest and install htx package in the guest got from 
the link,
  http://ausgsa.ibm.com/projects/h/htx/public_html/htxonly/htxubuntu-413.deb 

  2 - Run the Htx mdt.mem

  3 - The system Hits soft lockup Issue as below:

  dmesg o/p:
  [60287.590335] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 1141s! 
[hxemem64:23468]
  [60287.590572] Modules linked in: vmx_crypto ip_tables x_tables autofs4 
ibmvscsi crc32c_vpmsum
  [60287.590585] CPU: 3 PID: 23468 Comm: hxemem64 Tainted: G L  
4.8.0-17-generic #19-Ubuntu
  [60287.590587] task: c012a0971e00 task.stack: c012a2d4
  [60287.590589] NIP: c0015004 LR: c0015004 CTR: 
c0165e90
  [60287.590591] REGS: c012a2d439a0 TRAP: 0901   Tainted: G L   
(4.8.0-17-generic)
  [60287.590592] MSR: 80009033   CR: 48004244  
XER: 
  [60287.590603] CFAR: c0165890 SOFTE: 1 
 GPR00: c0165f9c c012a2d43c20 c14e5e00 
0900 
 GPR04:  0008 000100e4d61a 
 
 GPR08:  0006 000100e4d619 
c012bfee3130 
 GPR12: 3fffae6cdc70 3fffae436900 
  [60287.590627] NIP [c0015004] arch_local_irq_restore+0x74/0x90
  [60287.590630] LR [c0015004] arch_local_irq_restore+0x74/0x90
  [60287.590631] Call Trace:
  [60287.590634] [c012a2d43c20] [c012bfeccd80] 0xc012bfeccd80 
(unreliable)
  [60287.590639] [c012a2d43c40] [c0165f9c] 
run_timer_softirq+0x10c/0x230
  [60287.590644] [c012a2d43ce0] [c0b94adc] __do_softirq+0x18c/0x3fc
  [60287.590648] [c012a2d43de0] [c00d5828] irq_exit+0xc8/0x100
  [60287.590653] [c012a2d43e00] [c0024810] timer_interrupt+0xa0/0xe0
  [60287.590657] [c012a2d43e30] [c0002814] 
decrementer_common+0x114/0x180
  [60287.590659] Instruction dump:
  [60287.590662] 994d023a 2fa3 409e0024 e92d0020 61298000 7d210164 38210020 
e8010010 
  [60287.590670] 7c0803a6 4e800020 6042 4bfed259 <6000> 4be4 
6042 e92d0020 
  [63127.581494] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 339s! 
[hxemem64:23467]
  [63127.629682] Modules linked in: vmx_crypto ip_tables x_tables autofs4 
ibmvscsi crc32c_vpmsum
  [63127.629699] CPU: 2 PID: 23467 Comm: hxemem64 Tainted: G L  
4.8.0-17-generic #19-Ubuntu
  [63127.629701] task: c012a0965800 task.stack: c012a2d58000
  [63127.629703] NIP: 10011e60 LR: 1000ec6c CTR: 
00f33196
  [63127.629706] REGS: c012a2d5bea0 TRAP: 0901   Tainted: G L   
(4.8.0-17-generic)
  [63127.629707] MSR: 8001d033   CR: 
42004482  XER: 
  [63127.629719] CFAR: 10011e68 SOFTE: 1 
 GPR00: 1000e854 3fffadc2e540 10047f00 
000d 
 GPR04: 0200 3ff5a800 5a5a5a5a5a5a5a5a 
3ff5b0667348 
 GPR08:  1006c8e0 1006ca04 
f001 
 GPR12: 3fffae6cdc70 3fffadc36900 
  [63127.629740] NIP [10011e60] 0x10011e60
  [63127.629742] LR [1000ec6c] 0x1000ec6c
  [63127.629743] Call Trace:

  == Comment: #3 - Santhosh G  - 2016-09-28 02:17:29 ==
  Memory Info :

  root@ubuntu:~# cat /proc/meminfo 
  MemTotal:   78539776 kB
  MemFree:72219392 kB
  MemAvailable:   77217088 kB
  Buffers:  212544 kB
  Cached:  5249088 kB
  SwapCached:0 kB
  Active:  1440832 kB
  Inactive:4107264 kB
  Active(anon):  93888 kB
  Inactive(anon): 8640 kB
  Active(file):1346944 kB
  Inactive(file):  4098624 kB
  Unevictable:   0 kB
  Mlocked:   0 kB
  SwapTotal:   3443648 kB
  SwapFree:

[Kernel-packages] [Bug 1710877] Re: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd

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

Title:
   Fn Keys Not working Ubuntu 16.04 Asus FX553Vd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have an ASUS FX553VD machne. Some of my Fn keys are not working. For 
example,
  Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the 
keyboard LED brightness and Fn+F2(Airplane Mode).

  sudo dmidecode -s bios-version
  GL553VD.302

  uname-a
  Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | grep -i asus

  [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_)
  [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 
01072009 INTL 20160422)
  [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 
01072009 MSFT 0097)
  [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS 
GL553VD.302 03/06/2017
  [ 3.113648] asus_wmi: ASUS WMI generic driver loaded
  [ 3.114634] asus_wmi: Initialization: 0x1
  [ 3.114680] asus_wmi: BIOS WMI version: 8.1
  [ 3.114732] asus_wmi: SFUN value: 0x4a0061
  [ 3.115047] input: Asus WMI hotkeys as 
/devices/platform/asus-nb-wmi/input/input9
  [ 3.115210] asus_wmi: Number of fans: 1

  sudo evtest
  No device specified, trying to scan all of /dev/input/event*
  Available devices:
  /dev/input/event0:Sleep Button
  /dev/input/event1:Power Button
  /dev/input/event2:Lid Switch
  /dev/input/event3:Power Button
  /dev/input/event4:AT Translated Set 2 keyboard
  /dev/input/event5:Video Bus
  /dev/input/event6:Video Bus
  /dev/input/event7:ITE Tech. Inc. ITE Device(8910)
  /dev/input/event8:Asus WMI hotkeys
  /dev/input/event9:USB2.0 UVC HD Webcam
  /dev/input/event10:   HDA Intel PCH Headphone
  /dev/input/event11:   HDA Intel PCH HDMI/DP,pcm=3
  /dev/input/event12:   HDA Intel PCH HDMI/DP,pcm=7
  /dev/input/event13:   HDA Intel PCH HDMI/DP,pcm=8
  /dev/input/event14:   ELAN1200:00 04F3:3045 Touchpad
  Select the device event number [0-14]:
  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mlp1552 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187
  InstallationDate: Installed on 2017-08-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 13d3:5654 IMC Networks
   Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-91-generic N/A
   linux-backports-modules-4.4.0-91-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial
  Uname: Linux 4.4.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  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.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL553VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1715073] Re: SRIOV: warning if unload VFs

2017-09-25 Thread bugproxy

--- Comment From cls...@us.ibm.com 2017-09-25 16:50 EDT---
Verified with this one 4.13.0-11-generic #12-Ubuntu

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

Title:
  SRIOV: warning if unload VFs

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

Bug description:
  == Comment: #0 - Carol L. Soto  - 2017-02-23 16:11:47 ==
  ---Problem Description---
  When doing SRIOV if I unload VFs will see a warning:

  Feb 23 16:05:56 powerio-le11 kernel: [  201.343397] 
mlx5_3:wait_for_async_commands:674:(pid 6272): done with all pending requests
  Feb 23 16:05:56 powerio-le11 kernel: [  201.603999] iommu: Removing device 
0004:01:00.2 from group 7
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604078] pci 0004:01: 0.2: [PE# 
00] Removing DMA window #0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604084] pci 0004:01: 0.2: [PE# 
00] Disabling 64-bit DMA bypass
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604350] mlx5_core 0004:01:00.0: 
VF BAR0: [mem 0x2400-0x2401 64bit pref] shifted to [mem 
0x2400-0x2401 64bit pref] (Disabling 1 VFs shifted by 0)
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604363] mlx5_core 0004:01:00.0: 
can't update enabled VF BAR0 [mem 0x2400-0x2401 64bit pref]
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604379] [ cut here 
]
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604386] WARNING: CPU: 14 PID: 
6272 at /build/linux-twbIHf/linux-4.10.0/drivers/pci/iov.c:584 
pci_iov_update_resource+0x178/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604388] Modules linked in: 
mlx5_ib 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 kvm_hv kvm_pr kvm 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp 
llc binfmt_misc ipmi_powernv ipmi_devintf uio_pdrv_genirq ipmi_msghandler uio 
vmx_crypto powernv_rng powernv_op_panel leds_powernv ibmpowernv ib_iser rdma_cm 
iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi knem(OE) 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 mlx4_en ses enclosure scsi_transport_sas 
crc32c_vpmsum mlx5_core mlx4_core
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604451]  tg3 ipr devlink
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604456] CPU: 14 PID: 6272 Comm: 
bash Tainted: G   OE   4.10.0-8-generic #10-Ubuntu
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604457] task: c00f40a6d600 
task.stack: c00f40ac8000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604459] NIP: c06721b8 LR: 
c06721b4 CTR: 
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604461] REGS: c00f40acb590 
TRAP: 0700   Tainted: G   OE(4.10.0-8-generic)
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604462] MSR: 9282b033 

  Feb 23 16:05:56 powerio-le11 kernel: [  201.604470]   CR: 42424422  XER: 
2000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] CFAR: c0b49db4 
SOFTE: 1
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR00: c06721b4 
c00f40acb810 c143c900 0063
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR04: 0001 
0539 c01fff70 00021a50
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR08: 0007 
0007 0001 656d5b2030524142
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR12: 4400 
cfb87e00 10180df8 10189e60
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR16: 10189ed8 
c00fdd0a2400 c01fff97d180 c0d46268
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR20: c0d4e410 
c0d41df8 c01fff97d190 c0d4d8d8
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR24: c0d4d8e0 
c00fe8f460a0 0001 
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR28: c00fe8f80f80 
 c00fe8f46580 c00fe8f46000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604498] NIP [c06721b8] 
pci_iov_update_resource+0x178/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604501] LR [c06721b4] 
pci_iov_update_resource+0x174/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604501] Call Trace:
  Feb 23 16:05:56 powerio-le11

[Kernel-packages] [Bug 1416277] Re: toshiba_acpi: Unknown key 158

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

Title:
  toshiba_acpi: Unknown key 158

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I press the wireless key (see attached image) on my Toshiba P50W I
  get the following error in dmesg:

  toshiba_acpi: Unknown key 158

  I'd expect this key to toggle flight mode.
  --- 
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob2980 F pulseaudio
   /dev/snd/controlC1:  bob2980 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12
  InstallationDate: Installed on 2013-12-26 (400 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite P50W-B
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-11-generic N/A
   linux-backports-modules-3.18.0-11-generic  N/A
   linux-firmware 1.141
  Tags:  vivid
  Uname: Linux 3.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2013-12-26 (400 days ago)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin netdev plugdev 
sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/08/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P50W-B
  dmi.product.version: PSVP2A-00F002
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1717443] Re: Call trace observed when running xfstests on btrfs filesystem

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

** Tags added: triage-g

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

Title:
  Call trace observed when running xfstests on btrfs filesystem

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

Bug description:
  == Comment: #0 - Harish Sriram <> - 2017-07-21 00:34:58 ==
  Problem Description
  
  Call trace observed when running xfstests on btrfs filesystem

  Environment
  --
  Kernel Build:  4.11.0-10-generic
  System Name : ltc-boston124
  Model  : 9006-22C
  Platform:  PowerNV ( P9 )

  Uname output
  ---
  # uname -a
  Linux ltc-boston124 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux

  
  Steps to reproduce:
  
  1. Create a loop device with btrfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5.. Run xfstests-dev test  : ./check tests/btrfs/130

  Dmesg:
  --
  [Fri Jul 21 01:26:55 2017] INFO: rcu_sched self-detected stall on CPU
  [Fri Jul 21 01:26:55 2017]4-...: (210013 ticks this GP) 
idle=6db/141/0 softirq=18227470/18227470 fqs=104791 
  [Fri Jul 21 01:26:55 2017] (t=210039 jiffies g=10179019 c=10179018 q=1388)
  [Fri Jul 21 01:26:55 2017] Task dump for CPU 4:
  [Fri Jul 21 01:26:55 2017] btrfs   R  running task0 24224  
19847 0x00042006
  [Fri Jul 21 01:26:55 2017] Call Trace:
  [Fri Jul 21 01:26:55 2017] [c0002003dd62efb0] [c01240dc] 
sched_show_task+0xcc/0x150 (unreliable)
  [Fri Jul 21 01:26:55 2017] [c0002003dd62f020] [c0b80d20] 
rcu_dump_cpu_stacks+0xd0/0x134
  [Fri Jul 21 01:26:55 2017] [c0002003dd62f070] [c0177214] 
rcu_check_callbacks+0x9f4/0xb40
  [Fri Jul 21 01:26:55 2017] [c0002003dd62f1a0] [c0180968] 
update_process_times+0x48/0x90
  [Fri Jul 21 01:26:55 2017] [c0002003dd62f1d0] [c0197a70] 
tick_sched_handle.isra.7+0x30/0xb0
  [Fri Jul 21 01:26:55 2017] [c0002003dd62f200] [c0197b54] 
tick_sched_timer+0x64/0xd0
  [Fri Jul 21 01:26:55 2017] [c0002003dd62f240] [c0181408] 
__hrtimer_run_queues+0x108/0x390
  [Fri Jul 21 01:26:55 2017] [c0002003dd62f2c0] [c0182458] 
hrtimer_interrupt+0xf8/0x330
  [Fri Jul 21 01:26:55 2017] [c0002003dd62f390] [c0023dcc] 
__timer_interrupt+0x8c/0x270
  [Fri Jul 21 01:26:55 2017] [c0002003dd62f3e0] [c00241cc] 
timer_interrupt+0x9c/0xe0
  [Fri Jul 21 01:26:55 2017] [c0002003dd62f410] [c00090a4] 
decrementer_common+0x114/0x120
  [Fri Jul 21 01:26:55 2017] --- interrupt: 901 at 
find_parent_nodes+0x97c/0x1680 [btrfs]
 LR = find_parent_nodes+0x930/0x1680 [btrfs]
  [Fri Jul 21 01:26:55 2017] [c0002003dd62f700] [c008571bcbfc] 
find_parent_nodes+0x874/0x1680 [btrfs] (unreliable)
  [Fri Jul 21 01:26:55 2017] [c0002003dd62f840] [c008571bee64] 
iterate_extent_inodes+0x3ec/0x440 [btrfs]
  [Fri Jul 21 01:26:55 2017] [c0002003dd62f960] [c008571ccddc] 
process_extent+0x804/0xc00 [btrfs]
  [Fri Jul 21 01:26:55 2017] [c0002003dd62fa80] [c008571d06cc] 
changed_cb+0x574/0xe00 [btrfs]
  [Fri Jul 21 01:26:55 2017] [c0002003dd62fb40] [c008571d1f74] 
btrfs_ioctl_send+0x101c/0x10e0 [btrfs]
  [Fri Jul 21 01:26:55 2017] [c0002003dd62fc40] [c00857186218] 
btrfs_ioctl+0x16e0/0x23f0 [btrfs]
  [Fri Jul 21 01:26:55 2017] [c0002003dd62fd40] [c0372124] 
do_vfs_ioctl+0xd4/0x8c0
  [Fri Jul 21 01:26:55 2017] [c0002003dd62fde0] [c03729e4] 
SyS_ioctl+0xd4/0xf0
  [Fri Jul 21 01:26:55 2017] [c0002003dd62fe30] [c000b184] 
system_call+0x38/0xe0
  [Fri Jul 21 01:27:58 2017] INFO: rcu_sched self-detected stall on CPU
  [Fri Jul 21 01:27:58 2017]4-...: (225763 ticks this GP) 
idle=6db/141/0 softirq=18227470/18227470 fqs=112651 
  [Fri Jul 21 01:27:58 2017] (t=225792 jiffies g=10179019 c=10179018 q=2542)
  [Fri Jul 21 01:27:58 2017] Task dump for CPU 4:
  [Fri Jul 21 01:27:58 2017] btrfs   R  running task0 24224  
19847 0x00042006
  [Fri Jul 21 01:27:58 2017] Call Trace:
  [Fri Jul 21 01:27:58 2017] [c0002003dd62efb0] [c01240dc] 
sched_show_task+0xcc/0x150 (unreliable)
  [Fri Jul 21 01:27:58 2017] [c0002003dd62f020] [c0b80d20] 
rcu_dump_cpu_stacks+0xd0/0x134
  [Fri Jul 21 01:27:58 2017] [c0002003dd62f070] [c0177214] 
rcu_check_callbacks+0x9f4/0xb40
  [Fri Jul 21 01:27:58 2017] [c0002003dd62f1a0] [c0180968] 
update_process_times+0x48/0x90
  [Fri Jul 21 01:27:58 2017] [c0002003dd62f1d0] [c0197a70]

[Kernel-packages] [Bug 1685899] Re: [Ubuntu 17.04] - JFS related call traces and system enters xmon when rebooted after installation

** Changed in: ubuntu-power-systems
   Status: Incomplete => Opinion

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

** Changed in: ubuntu-power-systems
   Importance: High => Medium

** Changed in: linux (Ubuntu)
   Importance: High => 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/1685899

Title:
  [Ubuntu 17.04] - JFS related call traces and system enters xmon when
  rebooted after installation

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

Bug description:
  Issue:
  
  JFS related call traces and system enters xmon when rebooted after 
installation 

  Steps to reproduce:
  -
  1 - Install Ubuntu 17.04 the system with 
   - prepboot
  - /root [JFS filesystem]
  - swap space

  2 -After installation when rebooted it gives out call traces like as
  below:

  [3.895246] Unable to handle kernel paging request for data at address 
0x
  [3.895278] Faulting instruction address: 0xd4c5df1c
  [3.895284] Oops: Kernel access of bad area, sig: 11 [#1]
  [3.895287] SMP NR_CPUS=2048 [3.895288] NUMA 
  [3.895290] pSeries
  [3.895292] Modules linked in: ip_tables x_tables autofs4 jfs ibmvscsi 
crc32c_vpmsum
  [3.895301] CPU: 30 PID: 923 Comm: ureadahead Not tainted 4.9.0-15-generic 
#16-Ubuntu
  [3.895304] task: c00381d3c800 task.stack: c00381fd
  [3.895307] NIP: d4c5df1c LR: d4c5deb0 CTR: 
c01279d0
  [3.895310] REGS: c00381fd3500 TRAP: 0300   Not tainted  
(4.9.0-15-generic)
  [3.895313] MSR: 8280b033 [
3.895322]   CR: 48008804  XER: 0001
  [3.895324] CFAR: c0008a60 DAR:  DSISR: 4000 
SOFTE: 1 
  GPR00: d4c5deb0 c00381fd3780 d4c78c28 c003802f40f0 
  GPR04: d4c6f6f0 d4c72b58 0563 d4c78c28 
  GPR08:  00180e97  d4c6a608 
  GPR12: c01279d0 cfb90e00   
  GPR16:     
  GPR20:     
  GPR24:  1000  d4c72b38 
  GPR28: 00180e97 f0e1d5c0 c003812af240 c003802f40b0 
  NIP [d4c5df1c] __get_metapage+0x204/0x6f0 [jfs]
  [3.895372] LR [d4c5deb0] __get_metapage+0x198/0x6f0 [jfs]
  [3.895374] Call Trace:
  [3.895378] [c00381fd3780] [d4c5de6c] 
__get_metapage+0x154/0x6f0 [jfs] (unreliable)
  [3.895384] [c00381fd3870] [d4c4c368] diRead+0x130/0x260 [jfs]
  [3.895388] [c00381fd3920] [d4c424f4] jfs_iget+0x6c/0x1e0 [jfs]
  [3.895393] [c00381fd3950] [d4c43adc] jfs_lookup+0xe4/0x100 
[jfs]
  [3.895398] [c00381fd3a80] [c032a120] lookup_slow+0xe0/0x240
  [3.895402] [c00381fd3b00] [c032e8a8] 
walk_component+0x2d8/0x3f0
  [3.895406] [c00381fd3b70] [c032eb94] 
link_path_walk+0x1d4/0x600
  [3.895409] [c00381fd3c00] [c0330c1c] path_openat+0xbc/0x480
  [3.895413] [c00381fd3c80] [c03328ac] do_filp_open+0xec/0x160
  [3.895417] [c00381fd3db0] [c031863c] do_sys_open+0x1cc/0x380
  [3.895421] [c00381fd3e30] [c000bd84] system_call+0x38/0xe0
  [3.895424] Instruction dump:
  [3.895426] 7909f00e 7fc9f214 3921 f93f0028 fbdf0030 e93d 71280800 
41820460 
  [3.895433] ebdd0030 41920034 e91d0008 e93f0038  811e 
80e70090 39080001 
  [3.895441] ---[ end trace c2aa9ba09ea05eac ]---
  [3.895443] 
  [4.088560] systemd-journald[925]: Received request to flush runtime 
journal from PID 1
  [4.362062] crypto_register_alg 'aes' = 0
  [4.362112] crypto_register_alg 'cbc(aes)' = 0
  [4.362150] crypto_register_alg 'ctr(aes)' = 0
  [4.362191] crypto_register_alg 'xts(aes)' = 0
  [4.366949] pseries_rng: Registering IBM pSeries RNG driver

  When I first connected to the LPAR, it was unresponsive so I restarted
  it from the HMC and surprisingly it came up to the login prompt and I
  logged into the shell. I proceeded to install the matching linux-
  image-4.10.0-15-generic-dbgsym_4.10.0-15.17_ppc64el.ddeb. However, the
  installation of the matching dbgsym wasn't as helpful as I wanted it
  to be. objdump, crash tool, or addr2line wouldn't give me the source
  line correspond to the NIP address.

  I then restarted the LPAR with xmon enabled and it would drop to xmon
  immediately after attempting to remount / and at the same location as
  before at __get_metapage+0x204/0x6f0 [jfs] and again with a
  dereference of 0x0 as the cause of the data exception

[Kernel-packages] [Bug 1711075] Re: [Power 9, Power NV][WSP/Boston]Ubuntu 16.04.03 : perf test is hung at Breakpoint overflow signal handler

IBM, could you pls test the kernel provided by Joe and report back here?

** Package changed: kernel-package (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/1711075

Title:
  [Power 9, Power NV][WSP/Boston]Ubuntu 16.04.03 : perf test is hung at
  Breakpoint overflow signal handler

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

Bug description:
  == Comment: # - Shriya R. Kulkarni <> - 2017-06-14 01:11:02 ==
  Problem Description :
  =
  perf test is hung at Breakpoint overflow signal handler.

  Machine details :
  ==
  System : WSP , P9 baremetal.
  OS : Ubuntu 16.04.03
  uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 
9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Testing:
  
  root@ltc-wspoon3:~# perf test
   1: vmlinux symtab matches kallsyms: Skip
   2: Detect openat syscall event: Ok
   3: Detect openat syscall event on all cpus: Ok
   4: Read samples using the mmap interface  : Ok
   5: Parse event definition strings : Ok
   6: PERF_RECORD_* events & perf_sample fields  : Ok
   7: Parse perf pmu format  : Ok
   8: DSO data read  : Ok
   9: DSO data cache : Ok
  10: DSO data reopen: Ok
  11: Roundtrip evsel->name  : Ok
  12: Parse sched tracepoints fields : Ok
  13: syscalls:sys_enter_openat event fields : Ok
  14: Setup struct perf_event_attr   : Skip
  15: Match and link multiple hists  : Ok
  16: 'import perf' in python: Ok
  17: Breakpoint overflow signal handler :^C

  root@ltc-wspoon3:~# perf test -v 17
  17: Breakpoint overflow signal handler :
  --- start ---
  test child forked, pid 3802
  failed opening event 0
  failed opening event 0

  Attach : strace output.

  Steps to reproduce :
  
  1. Install perf. 
  2. Run perf test.
  3. When system hangs , exit it by : ^c.

  == Comment: # - Ravikumar B. Bangoria <> - 2017-07-13 04:44:29 ==
  Shriya,

  Can you please check after applying:
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=d89ba5353f301971dd7d2f9fdf25c4432728f38e

  == Comment: # - Shriya R. Kulkarni <> - 2017-07-19 06:28:13 ==
  Verified and Tested on Ubuntu 16.04.03:
  =
  uname -a : 4.10.0-27-generic
  System : Boston

  Testing without patch using distro perf:
  
  root@ltc-boston27:~# perf test
   1: vmlinux symtab matches kallsyms: Skip
   2: Detect openat syscall event: Ok
   3: Detect openat syscall event on all cpus: Ok
   4: Read samples using the mmap interface  : Ok
   5: Parse event definition strings : Ok
   6: PERF_RECORD_* events & perf_sample fields  : Ok
   7: Parse perf pmu format  : Ok
   8: DSO data read  : Ok
   9: DSO data cache : Ok
  10: DSO data reopen: Ok
  11: Roundtrip evsel->name  : Ok
  12: Parse sched tracepoints fields : Ok
  13: syscalls:sys_enter_openat event fields : Ok
  14: Setup struct perf_event_attr   : Skip
  15: Match and link multiple hists  : Ok
  16: 'import perf' in python: Ok
  17: Breakpoint overflow signal handler :^C
  root@ltc-boston27:~# 

  
  Testing with Patch using distro perf :
  ==
  root@ltc-boston27:~/linux-hwe-4.10.0/tools/perf# ./perf test
   1: vmlinux symtab matches kallsyms: Ok
   2: Detect openat syscall event: Ok
   3: Detect openat syscall event on all cpus: Ok
   4: Read samples using the mmap interface  : Ok
   5: Parse event definition strings : Ok
   6: PERF_RECORD_* events & perf_sample fields  : Ok
   7: Parse perf pmu format  : Ok
   8: DSO data read  : Ok
   9: DSO data cache : Ok
  10: DSO data reopen: Ok
  11: Roundtrip evsel->name  : Ok
  12: Parse sched tracepoints fields : Ok
  13: syscalls:sys_enter_openat event fields : Ok
  14: Setup struct perf_event_attr   : Ok
  15: Match and link multiple hists  : Ok
  16: 'import perf' in python: Ok
  17: Breakpoint overflow signal handler : FAILED!
  18: Breakpoint overflow sampling   : FAILED!
  19: Number of exit events of a simple workload : Ok
  20: Software clock events period values: Ok
  21: Object code reading: FAILED!
  22:

[Kernel-packages] [Bug 1718155] Re: linux-aws: 4.4.0-1036.45 -proposed tracker

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

Title:
  linux-aws: 4.4.0-1036.45 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1718149
  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/1718155/+subscriptions

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

[Kernel-packages] [Bug 1711075] [NEW] [Power 9, Power NV][WSP/Boston]Ubuntu 16.04.03 : perf test is hung at Breakpoint overflow signal handler

You have been subscribed to a public bug:

== Comment: # - Shriya R. Kulkarni <> - 2017-06-14 01:11:02 ==
Problem Description :
=
perf test is hung at Breakpoint overflow signal handler.

Machine details :
==
System : WSP , P9 baremetal.
OS : Ubuntu 16.04.03
uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 9 
10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

Testing:

root@ltc-wspoon3:~# perf test
 1: vmlinux symtab matches kallsyms: Skip
 2: Detect openat syscall event: Ok
 3: Detect openat syscall event on all cpus: Ok
 4: Read samples using the mmap interface  : Ok
 5: Parse event definition strings : Ok
 6: PERF_RECORD_* events & perf_sample fields  : Ok
 7: Parse perf pmu format  : Ok
 8: DSO data read  : Ok
 9: DSO data cache : Ok
10: DSO data reopen: Ok
11: Roundtrip evsel->name  : Ok
12: Parse sched tracepoints fields : Ok
13: syscalls:sys_enter_openat event fields : Ok
14: Setup struct perf_event_attr   : Skip
15: Match and link multiple hists  : Ok
16: 'import perf' in python: Ok
17: Breakpoint overflow signal handler :^C

root@ltc-wspoon3:~# perf test -v 17
17: Breakpoint overflow signal handler :
--- start ---
test child forked, pid 3802
failed opening event 0
failed opening event 0

Attach : strace output.

Steps to reproduce :

1. Install perf. 
2. Run perf test.
3. When system hangs , exit it by : ^c.

== Comment: # - Ravikumar B. Bangoria <> - 2017-07-13 04:44:29 ==
Shriya,

Can you please check after applying:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=d89ba5353f301971dd7d2f9fdf25c4432728f38e

== Comment: # - Shriya R. Kulkarni <> - 2017-07-19 06:28:13 ==
Verified and Tested on Ubuntu 16.04.03:
=
uname -a : 4.10.0-27-generic
System : Boston

Testing without patch using distro perf:

root@ltc-boston27:~# perf test
 1: vmlinux symtab matches kallsyms: Skip
 2: Detect openat syscall event: Ok
 3: Detect openat syscall event on all cpus: Ok
 4: Read samples using the mmap interface  : Ok
 5: Parse event definition strings : Ok
 6: PERF_RECORD_* events & perf_sample fields  : Ok
 7: Parse perf pmu format  : Ok
 8: DSO data read  : Ok
 9: DSO data cache : Ok
10: DSO data reopen: Ok
11: Roundtrip evsel->name  : Ok
12: Parse sched tracepoints fields : Ok
13: syscalls:sys_enter_openat event fields : Ok
14: Setup struct perf_event_attr   : Skip
15: Match and link multiple hists  : Ok
16: 'import perf' in python: Ok
17: Breakpoint overflow signal handler :^C
root@ltc-boston27:~# 


Testing with Patch using distro perf :
==
root@ltc-boston27:~/linux-hwe-4.10.0/tools/perf# ./perf test
 1: vmlinux symtab matches kallsyms: Ok
 2: Detect openat syscall event: Ok
 3: Detect openat syscall event on all cpus: Ok
 4: Read samples using the mmap interface  : Ok
 5: Parse event definition strings : Ok
 6: PERF_RECORD_* events & perf_sample fields  : Ok
 7: Parse perf pmu format  : Ok
 8: DSO data read  : Ok
 9: DSO data cache : Ok
10: DSO data reopen: Ok
11: Roundtrip evsel->name  : Ok
12: Parse sched tracepoints fields : Ok
13: syscalls:sys_enter_openat event fields : Ok
14: Setup struct perf_event_attr   : Ok
15: Match and link multiple hists  : Ok
16: 'import perf' in python: Ok
17: Breakpoint overflow signal handler : FAILED!
18: Breakpoint overflow sampling   : FAILED!
19: Number of exit events of a simple workload : Ok
20: Software clock events period values: Ok
21: Object code reading: FAILED!
22: Sample parsing : Ok
23: Use a dummy software event to keep tracking: Ok
24: Parse with no sample_id_all bit set: Ok
25: Filter hist entries: Ok
26: Lookup mmap thread : Ok
27: Share thread mg: Ok
28: Sort output of hist entries: Ok
29: Cumulate child hist entries: Ok
30: Track with sched_switch: Ok
31: Filter fds with revents mask in a fdarray  : Ok
32: Add fd to a fdarray, making it autogrow: Ok
33: kmod_path__parse   : Ok
34: Thread map : Ok
35: LLVM search and

[Kernel-packages] [Bug 1718149] Re: linux: 4.4.0-97.120 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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/1718149

Title:
  linux: 4.4.0-97.120 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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: 1718150,1718151
  derivatives: 1718153,1718154,1718155,1718156,1718157
  -- 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/1718149/+subscriptions

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

[Kernel-packages] [Bug 1714065] Re: ZFS NULL pointer dereference

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

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

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

Title:
  ZFS NULL pointer dereference

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  Invalid

Bug description:
  I am using a file-backed ZFS pool for LXD containers.  I have a few
  running and I got a few ZFS null pointer dereferences that make the
  system unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Aug 30 13:00:37 2017
  InstallationDate: Installed on 2017-04-21 (130 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
  MachineType: Micro-Star International Co., Ltd MS-7A34
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7
  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.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 TOMAHAWK (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.60:bd06/22/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.name: MS-7A34
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

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

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

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

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

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

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

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

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

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

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

  
  Host and guest kernel build
  =
  4.10.0-8-generic

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

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

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

[Kernel-packages] [Bug 1718897] Re: perf broken on 4.13.0-11-generic (artful): libbfd-2.29-system.so: cannot open shared object file: No such file or directory

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

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

Title:
  perf broken on 4.13.0-11-generic (artful): libbfd-2.29-system.so:
  cannot open shared object file: No such file or directory

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

Bug description:
  perf fails to start on my Artful install.

  This bug is very similar to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702056

  ... which was marked "fix released" a month ago. I do not have
  "-proposed" enabled.

  
  Full error:

  faux@astoria:~% perf
  /usr/lib/linux-tools/4.13.0-11-generic/perf: error while loading shared 
libraries: libbfd-2.29-system.so: cannot open shared object file: No such file 
or directory

  
  System state:

  faux@astoria:~% uname -a
  Linux astoria.goeswhere.com 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12 
16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  faux@astoria:~% dpkg -L binutils|grep bfd|grep so
  [nothing]

  faux@astoria:~% ls -1 /usr/lib/x86_64-linux-gnu/*libbfd*
  /usr/lib/x86_64-linux-gnu/libbfd-2.29.1-multiarch.so
  /usr/lib/x86_64-linux-gnu/libbfd-2.29.1-system.so
  /usr/lib/x86_64-linux-gnu/libbfd.a
  /usr/lib/x86_64-linux-gnu/libbfd.so

  faux@astoria:~% dpkg -S /usr/lib/x86_64-linux-gnu/libbfd-2.29.1-system.so
  libbinutils:amd64: /usr/lib/x86_64-linux-gnu/libbfd-2.29.1-system.so

  faux@astoria:~% apt-cache policy libbinutils
  libbinutils:
Installed: 2.29.1-1ubuntu1
Candidate: 2.29.1-1ubuntu1
Version table:
   *** 2.29.1-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  faux@astoria:~% ldd /usr/lib/linux-tools/4.13.0-11-generic/perf | fgrep -2 bfd
libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1 
(0x7ff43e595000)
libslang.so.2 => /lib/x86_64-linux-gnu/libslang.so.2 
(0x7ff43e0b3000)
libbfd-2.29-system.so => not found
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7ff43de96000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7ff43dc7)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  faux   2664 F pulseaudio
   /dev/snd/pcmC0D0p:   faux   2664 F...m pulseaudio
   /dev/snd/controlC0:  faux   2664 F pulseaudio
  Date: Fri Sep 22 10:33:50 2017
  HibernationDevice: RESUME=UUID=a99845b9-8854-43ea-9c9d-c9248cea15ab
  IwConfig:
   em1   no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=UUID=672510b8-afb9-425f-a58d-bd325f7c987a ro rootflags=subvol=@ nofb
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-09-12 (9 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V
  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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  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/1718897/+subscriptions

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

2017-09-25 Thread Benjamin Wynne

Well, I couldn't let this one go. I did the following - call me paranoid
if you like...

1) Downloaded WinIAP_Fix Touchpad.zip, and the MSI firmware I mentioned earlier 
as a comparison.
2) Compared the readable strings of corresponding executables - nothing 
suspicious, files look like different versions of same executable.
3) Uploaded file to a number of virus-scanning websites - nothing suspicious 
reported.
4) Loaded Win10 virtual machine, opened the firmware update utility, then ran 
virus scanners in VM - nothing suspicious reported.

Finally

5) Installed the firmware update in my real Win10 partition.

Confirming that this fixes the touchpad in Ubuntu 17.04, and that the
touchpad still works in Win10.

I still can't guarantee that this didn't install a virus somewhere, but
it's nice to have the touchpad working!

Regards,
Ben

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

  cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B:

[Kernel-packages] [Bug 1718292] Re: POWER9: NX842 module changes

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

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

** Tags added: triage-g

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

Title:
  POWER9: NX842 module changes

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

Bug description:
  This feature request will be used to submit NX842 changes needed to
  support on p9 - Using VAS interfaces instead of icswx to communicate
  with VAS (on PowerNV), modification of HCALL interface (on PowerVM, if
  needed) and other format changes.

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

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

[Kernel-packages] [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected

2017-09-25 Thread Piotr Kołaczkowski

4.14.rc2 network problem fixed by running:

sudo ln -s /etc/apparmor.d/sbin.dhclient /etc/apparmor.d/disable/
sudo /etc/init.d/apparmor reload

Now I can use 4.14.rc2 and will let you know how stable it is.

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

Title:
  System often freezes or panics if I log in with Dell Dock WD15
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Dell Precision 5520 with Ubuntu 17.04.

  If I first start a Unity session and then connect Dell WD15 USB-C dock
  with an external diplay plugged in, the system detects it properly and
  all the things work flawlessly (ethernet, external keyboard, external
  display, external storage connected to USB on the dock). I can plug-in
  and plug-out the dock multiple times and it just works.

  However if I boot the laptop with the dock already plugged in, first I
  get to the login screen and initially all is ok. Both screens are
  activated, and I can log in using the keyboard connected to the dock.

  When I hit "Enter", both screens go blank for a while, then they turn
  back on and I can see the desktop. A second or maybe two seconds later
  things start falling apart. When I move the mouse pointer a second
  after logging, it is kinda "jumpy", the movement is not smooth. The
  move freezes for a few times. I observed this behaviour only when
  moving the wireless mouse connected to the USB of the laptop. The
  builtin touchpad works smoothly.

  If it was the only issue, this would be a very minor annoyance.
  Sometimes, after a few short mouse pointer freezes the system starts
  working smoothly and all is rock stable from that point. However quite
  often I noticed much worse things happen:

  1. The mouse pointer and everything freezes totally after a few
  seconds from displaying the desktop. It is not possible to switch to
  the console with Ctrl-Alt-F1. This happens in >50% of logins.

  2. Kernel panic.

  I observed this behavior with stable Ubuntu kernel 4.10.0-20, as well
  as 4.11.0 - 4.11.8 (which I'm using now, because 4.11.x seems more
  stable than 4.10.0-x) and also 4.12.rc5 which I tried once.

  Even if everything goes fine, I noticed the following errors printed
  in syslog. I'm not sure if they are related, but they look very iffy
  to me:

  Jun 30 10:46:23 p5520 kernel: [   38.391971] DMAR: DRHD: handling fault 
status reg 2
  Jun 30 10:46:23 p5520 kernel: [   38.391977] DMAR: [INTR-REMAP] Request 
device [3e:00.0] fault index 1e [fault reason 38] Blocked an interrupt request 
due to source-id verification failure
  Jun 30 10:46:23 p5520 kernel: [   38.472490] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.472496] usb usb4: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.472497] usb 4-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.472498] usb 4-1.2: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7510] device 
(eth0): state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
  Jun 30 10:46:23 p5520 ModemManager[1076]:   (net/eth0): released by 
modem 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7537] devices 
removed (path: 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0,
 iface: eth0)
  Jun 30 10:46:23 p5520 kernel: [   38.552718] xhci_hcd :0a:00.0: Host halt 
failed, -19
  Jun 30 10:46:23 p5520 kernel: [   38.552721] xhci_hcd :0a:00.0: Host not 
accessible, reset failed.
  Jun 30 10:46:23 p5520 kernel: [   38.552722] xhci_hcd :0a:00.0: USB bus 4 
deregistered
  Jun 30 10:46:23 p5520 kernel: [   38.552728] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.552731] usb usb3: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1.5: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 kernel: [   38.553322] usb 3-1.7: USB disconnect, 
device number 4
  Jun 30 10:46:23 p5520 kernel: [   38.556064] BUG: unable to handle kernel 
paging request at 002018387ad8
  Jun 30 10:46:23 p5520 kernel: [   38.556173] IP: __radix_tree_lookup+0x10/0xf0
  Jun 30 10:46:23 p5520 kernel: [   38.556230] PGD 0 
  Jun 30 10:46:23 p5520 kernel: [   38.556232] 
  Jun 30 10:46:24 p5520 kernel: [   38.556280] Oops:  [#1] SMP
  Jun 30 10:46:24 p5520 kernel: [   38.556320] Modules linked in: ccm rfcomm 
cdc_ether usbnet snd_usb_audio snd_usbmidi_lib r8152 mii snd_hda_codec_hdmi 
cmac msr uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl joydev hid_multitouch

[Kernel-packages] [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected

2017-09-25 Thread Piotr Kołaczkowski

just FYI: 4.14.rc2 networking failure seems to be caused by dhcp client
crash. Where to submit bug report for this?

Sep 25 21:07:47 p5520 nm-applet[3178]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Sep 25 21:07:48 p5520 wpa_supplicant[1521]: wlp2s0: SME: Trying to authenticate 
with 90:5c:44:98:88:43 (SSID='UPCFB73B8F' freq=5500 MHz)
Sep 25 21:07:48 p5520 kernel: [   87.302852] wlp2s0: authenticate with 
90:5c:44:98:88:43
Sep 25 21:07:48 p5520 NetworkManager[1133]:   [1506366468.3216] device 
(wlp2s0): supplicant interface state: scanning -> authenticating
Sep 25 21:07:48 p5520 kernel: [   87.309769] wlp2s0: send auth to 
90:5c:44:98:88:43 (try 1/3)
Sep 25 21:07:48 p5520 nm-applet[3178]: Can't set a parent on widget which has a 
parent
Sep 25 21:07:48 p5520 wpa_supplicant[1521]: wlp2s0: Trying to associate with 
90:5c:44:98:88:43 (SSID='UPCFB73B8F' freq=5500 MHz)
Sep 25 21:07:48 p5520 kernel: [   87.332279] wlp2s0: authenticated
Sep 25 21:07:48 p5520 kernel: [   87.333039] wlp2s0: associating with AP with 
corrupt probe response
Sep 25 21:07:48 p5520 kernel: [   87.336133] wlp2s0: associate with 
90:5c:44:98:88:43 (try 1/3)
Sep 25 21:07:48 p5520 NetworkManager[1133]:   [1506366468.3494] device 
(wlp2s0): supplicant interface state: authenticating -> associating
Sep 25 21:07:48 p5520 nm-applet[3178]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Sep 25 21:07:48 p5520 kernel: [   87.374203] wlp2s0: RX AssocResp from 
90:5c:44:98:88:43 (capab=0x511 status=0 aid=2)
Sep 25 21:07:48 p5520 kernel: [   87.376217] wlp2s0: associated
Sep 25 21:07:48 p5520 nm-applet[3178]: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
Sep 25 21:07:48 p5520 wpa_supplicant[1521]: wlp2s0: Associated with 
90:5c:44:98:88:43
Sep 25 21:07:48 p5520 kernel: [   87.376544] IPv6: ADDRCONF(NETDEV_CHANGE): 
wlp2s0: link becomes ready
Sep 25 21:07:48 p5520 NetworkManager[1133]:   [1506366468.3949] device 
(wlp2s0): supplicant interface state: associating -> associated
Sep 25 21:07:48 p5520 NetworkManager[1133]:   [1506366468.4180] device 
(wlp2s0): supplicant interface state: associated -> 4-way handshake
Sep 25 21:07:48 p5520 wpa_supplicant[1521]: wlp2s0: WPA: Key negotiation 
completed with 90:5c:44:98:88:43 [PTK=CCMP GTK=CCMP]
Sep 25 21:07:48 p5520 wpa_supplicant[1521]: wlp2s0: CTRL-EVENT-CONNECTED - 
Connection to 90:5c:44:98:88:43 completed [id=0 id_str=]
Sep 25 21:07:48 p5520 NetworkManager[1133]:   [1506366468.4255] device 
(wlp2s0): supplicant interface state: 4-way handshake -> completed
Sep 25 21:07:48 p5520 NetworkManager[1133]:   [1506366468.4257] device 
(wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  
Connected to wireless network 'UPCFB73B8F'.
Sep 25 21:07:48 p5520 NetworkManager[1133]:   [1506366468.4260] device 
(wlp2s0): state change: config -> ip-config (reason 'none') [50 70 0]
Sep 25 21:07:48 p5520 NetworkManager[1133]:   [1506366468.4278] dhcp4 
(wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Sep 25 21:07:48 p5520 NetworkManager[1133]:   [1506366468.4354] dhcp4 
(wlp2s0): dhclient started with pid 3528
Sep 25 21:07:48 p5520 kernel: [   87.429289] audit: type=1400 
audit(1506366468.435:156): apparmor="DENIED" operation="create" 
profile="/sbin/dhclient" pid=3528 comm="dhclient" family="unix" 
sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create"
Sep 25 21:07:48 p5520 kernel: [   87.430998] audit: type=1400 
audit(1506366468.435:157): apparmor="DENIED" operation="create" 
profile="/sbin/dhclient" pid=3528 comm="dhclient" family="unix" 
sock_type="stream" protocol=0 requested_mask="create" denied_mask="create"
Sep 25 21:07:48 p5520 kernel: [   87.431007] audit: type=1400 
audit(1506366468.435:158): apparmor="DENIED" operation="create" 
profile="/sbin/dhclient" pid=3528 comm="dhclient" family="unix" 
sock_type="stream" protocol=0 requested_mask="create" denied_mask="create"
Sep 25 21:07:48 p5520 kernel: [   87.443292] audit: type=1400 
audit(1506366468.447:159): apparmor="DENIED" operation="create" 
profile="/usr/lib/NetworkManager/nm-dhcp-helper" pid=3529 comm="nm-dhcp-helper" 
family="unix" sock_type="stream" protocol=0 requested_mask="create" 
denied_mask="create"
Sep 25 21:07:48 p5520 NetworkManager[1133]:   [1506366468.4560] dhcp4 
(wlp2s0): client pid 3528 killed by signal 15
Sep 25 21:07:48 p5520 NetworkManager[1133]:   [1506366468.4562] dhcp4 
(wlp2s0): state changed unknown -> fail
Sep 25 21:07:48 p5520 NetworkManager[1133]:   [1506366468.4566] dhcp4 
(wlp2s0): canceled DHCP transaction
Sep 25 21:07:48 p5520 NetworkManager[1133]:   [1506366468.4566] dhcp4 
(wlp2s0): state changed fail -> done

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

Title:
  System often freezes or panics if I log in with Dell Dock WD15
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug

[Kernel-packages] [Bug 1685190] Re: Intermittent wireless network problem with RTL8821AE and 802.11n/EWC

2017-09-25 Thread Matteo Cossar

Update: connectivity restored by downloading, compiling and installing
lwfinger/rtlwifi_new drivers from github, even if Network Manager Applet
does not manage connection anymore and just shows Wireless networks:
device not ready.

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

Title:
  Intermittent wireless network problem with RTL8821AE and 802.11n/EWC

Status in linux package in Ubuntu:
  Expired

Bug description:
  An intermittent but very repeatable problem has started occurring upon
  upgrading from Ubuntu 16.10 (kernel 4.8) to Kubuntu 17.04 (kernel
  4.10). After about 10 to 30 minutes the wireless network will stop
  working. The network manager will still report that the network is
  "connected" but all network requests will timeout. This problem occurs
  only with the wireless network and not the wired ethernet connection.
  After walking through the kernel bug reporting instructions
  (https://wiki.ubuntu.com/Kernel/LinuxWireless) I found that turning
  off "802.11n/EWC" in my router solves the problem. I have logged this
  as a problem with the kernel since it appears to be specific to my
  hardware. Please correct me if this was an incorrect assumption.

  Attached is two samples of the system log (obtained using KSystemLog) after 
running through the following method twice:
  1. Restart computer.
  2. Browse the web until problem occurs (about 10 to 30 minutes)
  3. Save system log.

  Here is the hardware info from `lshw -c network`:
*-network
 description: Wireless interface
 product: RTL8821AE 802.11ac PCIe Wireless Network Adapter
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlp3s0
 version: 00
 serial: 6e:77:8e:04:bf:fb
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list ethernet physical wireless
 configuration: broadcast=yes driver=rtl8821ae 
driverversion=4.10.0-19-generic firmware=N/A ip=192.168.0.4 latency=0 link=yes 
multicast=yes wireless=IEEE 802.11
 resources: irq:50 ioport:3000(size=256) memory:b200-b2003fff

  Here is my full answers to the questions asked in
  https://wiki.ubuntu.com/Kernel/LinuxWireless:

  Q: What is the full computer model number (ex. HP G32-301TX Notebook PC)?
  A: ASUSPRO P2520LA 
https://www.asus.com/au/Commercial-Notebooks/ASUSPRO-P2520LA/overview/

  Q: If you update your BIOS to the newest version following the guide here, 
does this change anything?
  A: No

  Regarding your wireless Access Point (AP):

  Q: 3a. What is the current AP manufacturer, full model, revision, and 
firmware version?
  A: Board ID:  F@ST3864V2
 Symmetric CPU Threads: 2
 HardWare Version:  253561846
 Serial Number: N7161262J001520
 Mac Address:   88:a6:c6:8b:b5:72
 Build Timestamp:   160325_1801
 Software Version:  8.353.1_F@ST5350_Optus
 Bootloader (CFE) Version:  8.337
 DSL PHY and Driver Version:A2pv6F039p.d26b
 Wireless Driver Version:   6.37.14.4803.cpe4.14L04.0-kdb
 Voice Service Version: Voice
 Manufacturer: Sagecom

  Q: 3b. If you update the AP to the latest firmware does it change 
anything?
  A: No

  Q: 3c. What wireless connection type are you using (802.11ac, 802.11n 
150/300, 802.11g, etc.)?
  A: I think 802.11n given that "802.11n/EWC" option in router is set to 
"Auto".

  3d. If you switch to a different wireless type (802.11g or 802.11n if you 
are using 802.11g) does this change anything?
  A: Yes. The problem is solved when "802.11n/EWC" is set to "Disabled".

  Q: 3e. What channel specifically are you using when this problem is 
reproducible?
  A: It doesn't seem to depend on the channel but the router commonly 
chooses channel 6 and 11.

  Q: 3f. In order to understand the wireless environment your AP is
  working in, please provide the output of the following terminal
  command:

  sudo iw dev wlan0 scan | grep -i "ds parameter set"
  A:
  DS Parameter set: channel 11
  DS Parameter set: channel 11
  DS Parameter set: channel 1
  DS Parameter set: channel 1
  DS Parameter set: channel 11
  DS Parameter set: channel 1

  Q: 3g. What encryption type are you using (ex. WEP, WPA2-PSK, etc.)?
  A: WPA2-PSK

  Q: 3h. If you change and remove encryption entirely does this change 
anything?
  A: I don't think so. I can repeat my testing if certainty is required on 
this one.

  Q: 3i. Do you have QoS (Quality of Service)/WMM (Wi-Fi Multimedia) 
enabled?
  A: Yes (It is set to "Auto").

  Q: 3j. If you disable/enable QoS/WMM does it change anything?
  A: No.

  Q: 3k. What is the current beacon

[Kernel-packages] [Bug 1719290] Re: CONFIG_DEBUG_FS is not enabled by "make zfcpdump_defconfig" with Ubuntu 17.10 (kernel 4.13)

2017-09-25 Thread Frank Heimes

I just did a brief check on an Artful install based on the daily image
from the 22nd and it looks like it's indeed already enabled:

ubuntu@s1lp11:/$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10
Codename:   artful
ubuntu@s1lp11:/$ uname -r
4.13.0-11-generic
ubuntu@s1lp11:/$ grep CONFIG_DEBUG_FS /boot/config-4.13.0-11-generic 
CONFIG_DEBUG_FS=y


** Changed in: ubuntu-z-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/1719290

Title:
  CONFIG_DEBUG_FS is not enabled by "make zfcpdump_defconfig" with
  Ubuntu 17.10 (kernel 4.13)

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

Bug description:
  Ubuntu 17.10 uses kernel 4.13.

  We just found out that on this kernel version CONFIG_DEBUG_FS is not
  enabled by "make zfcpdump_defconfig".

  This makes zfcpdump fail with the following error message:

  ERROR: Unable to mount debugfs 
  No such file or directory

  Patch solving this problem is attached

  As reference following bugzilla
  As reference h
  IBM bugzilla for enabling zfcpdump: 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=139974

  or Launchpad 
  https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1565841

  == Comment: #1 - Heinz-Werner Seeck  -
  2017-09-25 06:00:23 ==

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

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

[Kernel-packages] [Bug 1704730] Re: xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no extents ( ext4 )

It looks like the mainline ppc builds have been failing since v4.13-rc5.
The -rc4 kernel did build:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/

** Tags added: kernel-key

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

Title:
  xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no
  extents ( ext4 )

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

Bug description:
  xfstests fails non-zero size but no extents on ext4 filesystem

  Environment
  --
  Kernel Build:  4.12.1-041201-generic

  Model  : 8247-22L
  Platform:  PowerNV ( P8 )

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 
17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with ext4 filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/044

  The test 044 fails with following
  generic/044 - output mismatch (see 
/root/harish/xfstests-dev/results//generic/044.out.bad)
  --- tests/generic/044.out 2017-07-13 06:04:36.208323135 -0400
  +++ /root/harish/xfstests-dev/results//generic/044.out.bad
2017-07-14 06:24:08.153731112 -0400
  @@ -1 +1,1000 @@
   QA output created by 044
  +corrupt file /mnt/scratch/1 - non-zero size but no extents
  +corrupt file /mnt/scratch/2 - non-zero size but no extents
  +corrupt file /mnt/scratch/3 - non-zero size but no extents
  +corrupt file /mnt/scratch/4 - non-zero size but no extents
  +corrupt file /mnt/scratch/5 - non-zero size but no extents
  +corrupt file /mnt/scratch/6 - non-zero size but no extents
  ...
  (Run 'diff -u tests/generic/044.out 
/root/harish/xfstests-dev/results//generic/044.out.bad'  to see the entire diff)
  Ran: generic/044
  Failures: generic/044
  Failed 1 of 1 tests

  
  Dmesg:
  --
  [17244.878673] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: (null)
  [17245.517227] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.697100] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.710634] run fstests generic/044 at 2017-07-14 06:23:49
  [17246.534410] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17246.535534] EXT4-fs (loop2): shut down requested (1)
  [17246.535625] Aborting journal on device loop2-8.
  [17247.278467] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17259.888304] EXT4-fs (loop2): shut down requested (2)
  [17259.995751] Aborting journal on device loop2-8.
  [17260.113582] EXT4-fs (loop2): recovery complete
  [17260.113902] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17260.190076] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17264.821978] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr


  == Comment: #2 - SEETEENA THOUFEEK  - 2017-07-17 
02:10:52 ==
  Issue does not happen when running the same test with xfs file system. (ie, 
creating loop device with xfs file system).

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

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

[Kernel-packages] [Bug 1704730] Re: xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no extents ( ext4 )

I'll investigate the mainline build failures.

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

Title:
  xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no
  extents ( ext4 )

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

Bug description:
  xfstests fails non-zero size but no extents on ext4 filesystem

  Environment
  --
  Kernel Build:  4.12.1-041201-generic

  Model  : 8247-22L
  Platform:  PowerNV ( P8 )

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 
17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with ext4 filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/044

  The test 044 fails with following
  generic/044 - output mismatch (see 
/root/harish/xfstests-dev/results//generic/044.out.bad)
  --- tests/generic/044.out 2017-07-13 06:04:36.208323135 -0400
  +++ /root/harish/xfstests-dev/results//generic/044.out.bad
2017-07-14 06:24:08.153731112 -0400
  @@ -1 +1,1000 @@
   QA output created by 044
  +corrupt file /mnt/scratch/1 - non-zero size but no extents
  +corrupt file /mnt/scratch/2 - non-zero size but no extents
  +corrupt file /mnt/scratch/3 - non-zero size but no extents
  +corrupt file /mnt/scratch/4 - non-zero size but no extents
  +corrupt file /mnt/scratch/5 - non-zero size but no extents
  +corrupt file /mnt/scratch/6 - non-zero size but no extents
  ...
  (Run 'diff -u tests/generic/044.out 
/root/harish/xfstests-dev/results//generic/044.out.bad'  to see the entire diff)
  Ran: generic/044
  Failures: generic/044
  Failed 1 of 1 tests

  
  Dmesg:
  --
  [17244.878673] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: (null)
  [17245.517227] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.697100] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.710634] run fstests generic/044 at 2017-07-14 06:23:49
  [17246.534410] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17246.535534] EXT4-fs (loop2): shut down requested (1)
  [17246.535625] Aborting journal on device loop2-8.
  [17247.278467] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17259.888304] EXT4-fs (loop2): shut down requested (2)
  [17259.995751] Aborting journal on device loop2-8.
  [17260.113582] EXT4-fs (loop2): recovery complete
  [17260.113902] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17260.190076] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17264.821978] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr


  == Comment: #2 - SEETEENA THOUFEEK  - 2017-07-17 
02:10:52 ==
  Issue does not happen when running the same test with xfs file system. (ie, 
creating loop device with xfs file system).

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

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

[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1678477

Title:
  Kernel has troule recognizing Corsair Strafe RGB keyboard

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

Bug description:
  I recently bought a Corsair Strafe RGB keyboard, and while it works
  well when successfully recognized by Ubuntu at boot, that doesn't
  always happen.

  I see messages like this when booting my desktop up:

  [6.619510] usb 3-10: unable to read config index 0 descriptor/all
  [6.619543] usb 3-10: can't read configurations, error -110

  They sometimes repeat at 5-second intervals, culminating on a "can't
  set config #1" message or even "unable to enumerate USB device". This
  happens on the logic that deals with a new USB device being connected,
  so when it doesn't work it never gets to the HID drivers part of the
  code. When it does, hid-generic is quite able to control the keyboard,
  though this message appears on dmesg:

  [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt
  endpoint

  
  From what I have been able to determine, the Corsair Strafe RGB has three 
inputs, with the last one being used as input/output and having something to do 
with the LEDs. It only has a single USB configuration, though I don't know why 
it times out.

  Searching on Google has a lot of people recommending this userspace
  drive to me: https://github.com/mattanger/ckb-next , and I've tried
  it, but it seems to be more about programming lighting effects into
  the keyboard than in controlling its basic operation, which is all I'm
  interested in. Its daemon was supposed to handle that part too, but it
  didn't fix those connection errors on boot.

  I have the following boot parameter set in my kernel, following advice
  from ckb-next's README, but it doesn't see to have an appreciable
  effect on my success rate:

  usbhid.quirks=0x1B1C:0x1B20:0x2448

  ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT
  as well in an attempt to improve things, without success.

  GRUB is always able to correctly identify the keyboard and get it to
  work, too, which makes the fact that the full kernel can't always do
  it a little more frustrating.

  I would be happy to provide any extra information you require on this
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-45-generic 4.8.0-45.48
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bira   2322 F pulseaudio
   /dev/snd/controlC0:  bira   2322 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Apr  1 10:23:52 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-24 (767 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic 
root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash 
usbhid.quirks=0x1B1C:0x1B20:0x2448
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-45-generic N/A
   linux-backports-modules-4.8.0-45-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/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: Z97M-D3H
  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: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

[Kernel-packages] [Bug 1718980] Re: linux: 4.13.0-12.13 -proposed tracker

** Changed in: kernel-development-workflow/promote-to-proposed
   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/1718980

Title:
  linux: 4.13.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

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

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

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

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

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

[Kernel-packages] [Bug 1719042] Re: External USB ports ignored in kernel 4.4.0.96

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 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.14-rc2/


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

Title:
  External USB ports ignored in kernel 4.4.0.96

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using 16.04-3.I have a Dell Inspiron Zino HD (AMD 64) with a Dell 1703FP 
monitor.  The monitor has 4 USB ports which attach my keyboard, mouse, and 
speakers. the kernel 4.4.0.96 generic ignores those ports when it gets to 
asking for the password and does not let me use my keyboard. Those ports work 
in BIOS and GRUB. They also work when I run the 4.4.0.93 kernel. 
  I have found that the 4.4.0.96 kernel uses the USB ports which are on the 
motherboard and I can boot up if I attach the keyboard there.

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

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

[Kernel-packages] [Bug 1718925] Re: btrfs/130 test causing soft lockup and rcu_sched self-detected stall on CPU

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

** Tags added: kernel-da-key

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

Title:
  btrfs/130 test causing soft lockup and  rcu_sched self-detected stall
  on CPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This issue was found by the regression test suite.
  This test will hang and get killed with our timeout setting.

  It's not a regression as I can see that it will time out on older
  kernels as well. And it can be seen on different releases (although I
  haven't check if they all have the same dmesg output)

  The stalled process will hinder the test for xfs filesystem. As the
  partition was occupied and cannot be destroyed.

  There is a similar bug 1717443

  [  215.728801] BTRFS: device fsid 97eb2b12-1ed4-4cab-bdb8-de78292ab2d1 devid 
1 transid 3 /dev/sdb2
  [  215.808560] BTRFS info (device sdb2): disk space caching is enabled
  [  215.808564] BTRFS: has skinny extents
  [  215.808566] BTRFS: flagging fs with big metadata feature
  [  215.922083] BTRFS: creating UUID tree
  [  216.295453] BTRFS: device fsid 18dbdc70-b4a8-4a1d-bd6e-629a7c44c769 devid 
1 transid 3 /dev/sdb2
  [  216.374891] BTRFS info (device sdb2): disk space caching is enabled
  [  216.374894] BTRFS: has skinny extents
  [  216.374896] BTRFS: flagging fs with big metadata feature
  [  216.397006] BTRFS: creating UUID tree
  [  222.588433] perf interrupt took too long (3642 > 2500), lowering 
kernel.perf_event_max_sample_rate to 5
  [  256.078072] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[btrfs:12947]
  [  256.078507] Modules linked in: ipmi_ssif intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass sb_edac edac_core hpilo 
8250_fintek ipmi_si ipmi_msghandler lpc_ich shpchp acpi_power_meter ioatdma dca 
mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel ses enclosure aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd tg3 ptp pps_core hpsa scsi_transport_sas wmi fjes
  [  256.078570] CPU: 0 PID: 12947 Comm: btrfs Not tainted 4.4.0-96-generic 
#119-Ubuntu
  [  256.078573] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, 
BIOS P89 12/27/2015
  [  256.078576] task: 880858118e00 ti: 880859eec000 task.ti: 
880859eec000
  [  256.078579] RIP: 0010:[]  [] 
find_parent_nodes+0x5c4/0x7a0 [btrfs]
  [  256.078618] RSP: 0018:880859eef928  EFLAGS: 0282
  [  256.078620] RAX: 88083fb29c40 RBX:  RCX: 
880859eef970
  [  256.078623] RDX: 88083fb29c20 RSI: 01c78000 RDI: 
880854561000
  [  256.078625] RBP: 880859eef9f8 R08: 02400040 R09: 
000180330021
  [  256.078627] R10: 88083fc6f5a0 R11: 0001a890 R12: 
880854561000
  [  256.078628] R13: 88083fc6f500 R14:  R15: 
880859eefa50
  [  256.078632] FS:  7f52288698c0() GS:88085f20() 
knlGS:
  [  256.078634] CS:  0010 DS:  ES:  CR0: 80050033
  [  256.078636] CR2: 7f52277ebe38 CR3: 0008547cd000 CR4: 
003406f0
  [  256.078638] DR0:  DR1:  DR2: 

  [  256.078640] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  256.078642] Stack:
  [  256.078644]   88085b318000  
880854561000
  [  256.078648]  880859eefa50 00c4  
8808592091b0
  [  256.078652]  592093f0 8808580e5ce0 1063 
880859eef980
  [  256.078656] Call Trace:
  [  256.078683]  [] ? dir_changed.isra.15+0xa0/0xa0 [btrfs]
  [  256.078706]  [] iterate_extent_inodes+0x109/0x350 [btrfs]
  [  256.078726]  [] ? extent_from_logical+0x198/0x230 [btrfs]
  [  256.078747]  [] process_extent+0x771/0x1000 [btrfs]
  [  256.078767]  [] ? __record_deleted_ref+0x30/0x30 [btrfs]
  [  256.078786]  [] changed_cb+0x231/0xad0 [btrfs]
  [  256.078805]  [] btrfs_ioctl_send+0x1134/0x1210 [btrfs]
  [  256.078828]  [] btrfs_ioctl+0x2a3/0x28b0 [btrfs]
  [  256.078833]  [] ? task_move_group_fair+0x57/0x60
  [  256.078839]  [] ? __enqueue_entity+0x6c/0x70
  [  256.078842]  [] ? enqueue_entity+0x3a7/0xd10
  [  256.078846]  [] ? enqueue_task_fair+0xaa/0x8b0
  [  256.078850]  [] ? sched_clock+0x9/0x10
  [  256.078854]  [] ? sched_clock_cpu+0x8f/0xa0
  [  256.078859]  [] do_vfs_ioctl+0x29f/0x490
  [  256.078863]  [] ? _do_fork+0xec/0x360
  [  256.078867]  [] SyS_ioctl+0x79/0x90
  [  256.078872]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [  256.078875] Code: a8 01 00 00 75 32 48 8b 85 78 ff ff ff 48 85 c0 0f

[Kernel-packages] [Bug 1718936] Re: Can't boot Artful 17.10 live images on XPS 15 (9560)

Can you see if this issue also happens with the latest daily image?  It can be 
downloaded from:
Desktop:
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/

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

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

** Tags added: kernel-da-key

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

Title:
  Can't boot Artful 17.10 live images on XPS 15 (9560)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I usually test Ubuntu beta releases. With Artful, I haven't been able
  to boot the image on my XPS 15 (9560) Dell laptop because the boot
  process stops half way.

  The boot proceeds properly if I pass the "nomodeset" kernel boot
  option but that won't work because there is no more hiDPI support and
  dual display doesn't work.

  This has been ongoing for several weeks, around the 4.12 kernel.
  Please fix it. It would be a shame for this product not to boot Artful
  out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1701 F pulseaudio
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 12:38:09 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170921)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1711251] Re: vhost guest network randomly drops under stress (kvm)

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

** Tags added: verification-needed-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/1711251

Title:
vhost guest network randomly drops under stress (kvm)

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

Bug description:
== SRU Justification ==

A vhost performance patch was introduced in the 4.10 kernel upstream,
and is currently included in the Zesty 4.10 kernel:

commit 809ecb9bca6a9424ccd392d67e368160f8b76c92
Author: Jason Wang
Date: Mon Dec 12 14:46:49 2016 +0800

vhost: cache used event for better performance

However I recently hit a functional issue linked to this patch which
would cause random guests to lose their network connection under
stress. This is not architecture specific and more likely to be hit
with high network stress (i.e. lots of uperf instances).

The patch author has now reverted this patch upstream:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/vhost?id=8d65843c44269c21e95c98090d9bb4848d473853

which reads:
"
Revert "vhost: cache used event for better performance"
This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it
was reported to break vhost_net. We want to cache used event and use
it to check for notification. The assumption was that guest won't move
the event idx back, but this could happen in fact when 16 bit index
wraps around after 64K entries.

Signed-off-by: Jason Wang
Acked-by: Michael S. Tsirkin
Signed-off-by: David S. Miller
"

I am requesting this patch to revert the problematic one be pulled
into Ubuntu Zesty (anything 4.10+).

---uname output---
Linux p82qvirt 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:19
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

Machine Type = 8247-22L

---Steps to Reproduce---
I can recreate the scenario with the following setup:
- on a 20core host, start 20 1core VMs
- I have a single linux bridge assigned to all guests using virtio
- start a uperf benchmark between each guest pair (10 total) using a high
number of uperf nprocs (32)

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

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

[Kernel-packages] [Bug 1713884] Re: [CIFS] Fix maximum SMB2 header size

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1713884

Title:
  [CIFS] Fix maximum SMB2 header size

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  In Progress

Bug description:
  Currently the maximum size of SMB2/3 header is set incorrectly which
  leads to hanging of directory listing operations on encrypted SMB3
  connections. Fix this by setting the maximum size to 170 bytes that
  is calculated as RFC1002 length field size (4) + transform header
  size (52) + SMB2 header size (64) + create response size (56).

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de

  This applies across the board 3.16, 4.4, 4.10, artful, and azure.
  Microsoft would be happy to help test.

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

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

[Kernel-packages] [Bug 1716091] Re: Please make linux-libc-dev Provide: aufs-dev

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Please make linux-libc-dev Provide: aufs-dev

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The aufs-tools package build-depends on aufs-dev, which is a separate
  package in Debian.  Since the Ubuntu kernel includes aufs, the only
  aufs header, /usr/include/linux/aufs_type.h, is already shipped by
  linux-libc-dev.  Please have linux-libc-dev declare Provides: aufs-dev
  so that this package is buildable in Ubuntu.

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

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

[Kernel-packages] [Bug 1715812] Re: Neighbour confirmation broken, breaks ARP cache aging

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1715812

Title:
  Neighbour confirmation broken, breaks ARP cache aging

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

Bug description:
  [SRU Justification]

  [Impact]
  A host can lose access to another host whose MAC address changes if they have 
active connections to other hosts that share a route. The ARP cache does not 
time out as expected - instead the old MAC address is continuously reconfirmed.

  [Fix]
  Apply series [1], which changes the algorithm for neighbour confirmation.
  That is, from upstream:
  51ce8bd4d17a net: pending_confirm is not used anymore 
  0dec879f636f net: use dst_confirm_neigh for UDP, RAW, ICMP, L2TP 
  63fca65d0863 net: add confirm_neigh method to dst_ops 
  c3a2e8370534 tcp: replace dst_confirm with sk_dst_confirm 
  c86a773c7802 sctp: add dst_pending_confirm flag 
  4ff0620354f2 net: add dst_pending_confirm flag to skbuff 
  9b8805a32559 sock: add sk_dst_pending_confirm flag 

  [Test case]
  Create 3 real or virtual systems, all hooked up to a switch.
  One system needs an active-backup bond with fail_over_mac=1 num_grat_arp=0.

  Put all the systems in the same subnet, e.g. 192.168.200.0/24

  Call the system with the bond A, and the other two systems B and C.

  On B, run in 3 shells:
   - netperf -t TCP_RR to C
   - ping -f A
   - watch 'ip -s neigh show 192.168.200.0/24'

  On A, cause the bond to fail over.

  Observe that:

   - without the patches, B intermittently fails to notice the change in
  A's MAC address. This presents as the ping failing and not recovering,
  and the arp table showing the old mac address never timing out and
  never being replace with a new mac address.

   - with the patches, the arp cache times out and B sends another mac
  probe and detects A's new address.

  It helps to use taskset to put ping and netperf on the same CPU, or
  use single-CPU vms.

  See [2] for more details.

  [References]
  [2] Original report: 
https://www.mail-archive.com/netdev@vger.kernel.org/msg138762.html
  [1]: https://www.spinics.net/lists/linux-rdma/msg45907.html

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

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

[Kernel-packages] [Bug 1715073] Re: SRIOV: warning if unload VFs

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1715073

Title:
  SRIOV: warning if unload VFs

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

Bug description:
  == Comment: #0 - Carol L. Soto  - 2017-02-23 16:11:47 ==
  ---Problem Description---
  When doing SRIOV if I unload VFs will see a warning:

  Feb 23 16:05:56 powerio-le11 kernel: [  201.343397] 
mlx5_3:wait_for_async_commands:674:(pid 6272): done with all pending requests
  Feb 23 16:05:56 powerio-le11 kernel: [  201.603999] iommu: Removing device 
0004:01:00.2 from group 7
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604078] pci 0004:01: 0.2: [PE# 
00] Removing DMA window #0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604084] pci 0004:01: 0.2: [PE# 
00] Disabling 64-bit DMA bypass
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604350] mlx5_core 0004:01:00.0: 
VF BAR0: [mem 0x2400-0x2401 64bit pref] shifted to [mem 
0x2400-0x2401 64bit pref] (Disabling 1 VFs shifted by 0)
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604363] mlx5_core 0004:01:00.0: 
can't update enabled VF BAR0 [mem 0x2400-0x2401 64bit pref]
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604379] [ cut here 
]
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604386] WARNING: CPU: 14 PID: 
6272 at /build/linux-twbIHf/linux-4.10.0/drivers/pci/iov.c:584 
pci_iov_update_resource+0x178/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604388] Modules linked in: 
mlx5_ib 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 kvm_hv kvm_pr kvm 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp 
llc binfmt_misc ipmi_powernv ipmi_devintf uio_pdrv_genirq ipmi_msghandler uio 
vmx_crypto powernv_rng powernv_op_panel leds_powernv ibmpowernv ib_iser rdma_cm 
iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi knem(OE) 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 mlx4_en ses enclosure scsi_transport_sas 
crc32c_vpmsum mlx5_core mlx4_core
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604451]  tg3 ipr devlink
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604456] CPU: 14 PID: 6272 Comm: 
bash Tainted: G   OE   4.10.0-8-generic #10-Ubuntu
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604457] task: c00f40a6d600 
task.stack: c00f40ac8000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604459] NIP: c06721b8 LR: 
c06721b4 CTR: 
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604461] REGS: c00f40acb590 
TRAP: 0700   Tainted: G   OE(4.10.0-8-generic)
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604462] MSR: 9282b033 

  Feb 23 16:05:56 powerio-le11 kernel: [  201.604470]   CR: 42424422  XER: 
2000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] CFAR: c0b49db4 
SOFTE: 1
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR00: c06721b4 
c00f40acb810 c143c900 0063
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR04: 0001 
0539 c01fff70 00021a50
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR08: 0007 
0007 0001 656d5b2030524142
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR12: 4400 
cfb87e00 10180df8 10189e60
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR16: 10189ed8 
c00fdd0a2400 c01fff97d180 c0d46268
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR20: c0d4e410 
c0d41df8 c01fff97d190 c0d4d8d8
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR24: c0d4d8e0 
c00fe8f460a0 0001 
  Feb 23 16:05:56

[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  Middle button of trackpoint doesn't work

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

Bug description:
  Middle button doesn't work on several Thinkpad laptops like E570,
  E475, E470, E575 and X1Carbon.

  When middle button fails to work, logs show:
  psmouse serio2: trackpoint: failed to get extended button data

  It fails to read out ext button info via PS2 command.
  Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails 
to read button info.

  And on Lenovo X1, there is a new version of trackpoint, add this ID
  for this new device.

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

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

[Kernel-packages] [Bug 1713884] Re: [CIFS] Fix maximum SMB2 header size

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  [CIFS] Fix maximum SMB2 header size

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  In Progress

Bug description:
  Currently the maximum size of SMB2/3 header is set incorrectly which
  leads to hanging of directory listing operations on encrypted SMB3
  connections. Fix this by setting the maximum size to 170 bytes that
  is calculated as RFC1002 length field size (4) + transform header
  size (52) + SMB2 header size (64) + create response size (56).

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de

  This applies across the board 3.16, 4.4, 4.10, artful, and azure.
  Microsoft would be happy to help test.

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

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

[Kernel-packages] [Bug 1718983] Re: usb 3-4: 2:1: cannot get freq at ep 0x1

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

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

Title:
  usb 3-4: 2:1: cannot get freq at ep 0x1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  dmesg:
  [  802.537927] usb 3-4: 2:1: cannot get freq at ep 0x1
  [  859.203968] usb 3-4: 2:1: cannot get freq at ep 0x1

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   caravena   1773 F...m pulseaudio
   /dev/snd/controlC1:  caravena   1773 F pulseaudio
   /dev/snd/controlC0:  caravena   1773 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep 22 14:15:10 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (78 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.13.0-11-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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.family: ChiefRiver System
  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/1718983/+subscriptions

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

[Kernel-packages] [Bug 1715812] Re: Neighbour confirmation broken, breaks ARP cache aging

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  Neighbour confirmation broken, breaks ARP cache aging

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

Bug description:
  [SRU Justification]

  [Impact]
  A host can lose access to another host whose MAC address changes if they have 
active connections to other hosts that share a route. The ARP cache does not 
time out as expected - instead the old MAC address is continuously reconfirmed.

  [Fix]
  Apply series [1], which changes the algorithm for neighbour confirmation.
  That is, from upstream:
  51ce8bd4d17a net: pending_confirm is not used anymore 
  0dec879f636f net: use dst_confirm_neigh for UDP, RAW, ICMP, L2TP 
  63fca65d0863 net: add confirm_neigh method to dst_ops 
  c3a2e8370534 tcp: replace dst_confirm with sk_dst_confirm 
  c86a773c7802 sctp: add dst_pending_confirm flag 
  4ff0620354f2 net: add dst_pending_confirm flag to skbuff 
  9b8805a32559 sock: add sk_dst_pending_confirm flag 

  [Test case]
  Create 3 real or virtual systems, all hooked up to a switch.
  One system needs an active-backup bond with fail_over_mac=1 num_grat_arp=0.

  Put all the systems in the same subnet, e.g. 192.168.200.0/24

  Call the system with the bond A, and the other two systems B and C.

  On B, run in 3 shells:
   - netperf -t TCP_RR to C
   - ping -f A
   - watch 'ip -s neigh show 192.168.200.0/24'

  On A, cause the bond to fail over.

  Observe that:

   - without the patches, B intermittently fails to notice the change in
  A's MAC address. This presents as the ping failing and not recovering,
  and the arp table showing the old mac address never timing out and
  never being replace with a new mac address.

   - with the patches, the arp cache times out and B sends another mac
  probe and detects A's new address.

  It helps to use taskset to put ping and netperf on the same CPU, or
  use single-CPU vms.

  See [2] for more details.

  [References]
  [2] Original report: 
https://www.mail-archive.com/netdev@vger.kernel.org/msg138762.html
  [1]: https://www.spinics.net/lists/linux-rdma/msg45907.html

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

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

[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1715271

Title:
  Middle button of trackpoint doesn't work

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

Bug description:
  Middle button doesn't work on several Thinkpad laptops like E570,
  E475, E470, E575 and X1Carbon.

  When middle button fails to work, logs show:
  psmouse serio2: trackpoint: failed to get extended button data

  It fails to read out ext button info via PS2 command.
  Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails 
to read button info.

  And on Lenovo X1, there is a new version of trackpoint, add this ID
  for this new device.

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

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

[Kernel-packages] [Bug 1708852] Re: Touchpad not detected

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  Touchpad not detected

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

Bug description:
  SRU Justifications:

  [Impact] 
  Touchpad on Lenovo ideapad 320-14IKB does not work.

  [Test Case]
  After adding the ID to the elan_i2c driver, the touchpad works.

  
  [Regression Potential]
  Very low.
  It only adds device ID to the driver, no functional changes.

  ---

  The touchpad is not working in any linux distribution, but works in
  Windows. It is not getting detected. Seems like a kernel bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-30-generic 4.10.0-30.34
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matheus1504 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Aug  5 12:58:21 2017
  InstallationDate: Installed on 2017-08-05 (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 5986:1127 Acer, Inc
   Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc.
   Bus 001 Device 002: ID 0101:0007
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80YF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed 
root=UUID=d7c89f65-c9a7-4e7f-9bce-ed58751f0619 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-30-generic N/A
   linux-backports-modules-4.10.0-30-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN16WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 4A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-14IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN16WW:bd02/22/2017:svnLENOVO:pn80YF:pvrLenovoideapad320-14IKB:rvnLENOVO:rnCairo4A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-14IKB:
  dmi.product.name: 80YF
  dmi.product.version: Lenovo ideapad 320-14IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1708852] Re: Touchpad not detected

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1708852

Title:
  Touchpad not detected

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

Bug description:
  SRU Justifications:

  [Impact] 
  Touchpad on Lenovo ideapad 320-14IKB does not work.

  [Test Case]
  After adding the ID to the elan_i2c driver, the touchpad works.

  
  [Regression Potential]
  Very low.
  It only adds device ID to the driver, no functional changes.

  ---

  The touchpad is not working in any linux distribution, but works in
  Windows. It is not getting detected. Seems like a kernel bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-30-generic 4.10.0-30.34
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matheus1504 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Aug  5 12:58:21 2017
  InstallationDate: Installed on 2017-08-05 (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 5986:1127 Acer, Inc
   Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc.
   Bus 001 Device 002: ID 0101:0007
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80YF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed 
root=UUID=d7c89f65-c9a7-4e7f-9bce-ed58751f0619 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-30-generic N/A
   linux-backports-modules-4.10.0-30-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN16WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 4A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-14IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN16WW:bd02/22/2017:svnLENOVO:pn80YF:pvrLenovoideapad320-14IKB:rvnLENOVO:rnCairo4A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-14IKB:
  dmi.product.name: 80YF
  dmi.product.version: Lenovo ideapad 320-14IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1713821] Re: arm64 arch_timer fixes

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1713821

Title:
  arm64 arch_timer fixes

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

Bug description:
  [Impact]
  This bug captures a few issues with the ARM arch_timer driver:

  1) Some arm64 systems have hardware defects in their architected timer
  implementations that require errata, which we workaround in the
  kernel. However, it's possible that this workaround will not be
  applied if the timer was reset w/ the user access bit set.

  2) The Juno board fails to initialize a timer at boot:

    arch_timer: Unable to map frame @ 0x
    arch_timer: Frame missing phys irq.
    Failed to initialize '/timer@2a81': -22

  3) Possible boot warning from arch_timer_mem_of_init():
     'Trying to vfree() nonexistent vm area'

  4) There's a theoretical problem where the first frame of a timer
  could be used even though a better suited timer frame is available.

  5) An infinite recursion loop will occur when enabling the function
  tracer in builds with CONFIG_PREEMPT_TRACER=y. Ubuntu does not enable
  CONFIG_PREEMPT_TRACER, so this will only be a problem if that changes.

  [Test Case]
  I've regression tested this on both a system w/ an errata workaround 
(HiSilicon D05) and one that is not (Cavium ThunderX CRB1S). In both cases the 
timer was initialized correctly. Verified by looking at the boot messages:

  dannf@d05-3:~$ dmesg | grep arch_timer
  [0.00] arch_timer: Enabling global workaround for HiSilicon erratum 
161010101
  [0.00] arch_timer: CPU0: Trapping CNTVCT access
  [0.00] arch_timer: cp15 timer(s) running at 50.00MHz (phys).
  [0.194241] arch_timer: CPU1: Trapping CNTVCT access
  [0.197305] arch_timer: CPU2: Trapping CNTVCT access
  <.>
  [0.396228] arch_timer: CPU62: Trapping CNTVCT access
  [0.399752] arch_timer: CPU63: Trapping CNTVCT access

  ubuntu@grotrian:~$ dmesg | grep arch_timer
  [0.00] arch_timer: cp15 timer(s) running at 100.00MHz (phys).

  [Regression Risk]
  The regression risk is restricted to ARM systems, as this driver only applies 
there. Regressions could lead to a timer failing to initialize, or a system 
that requires errata not having the appropriate workaround applied. (Which are 
also the  conditions that the suggested backports are attempting to fix).

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

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

[Kernel-packages] [Bug 1709179] Re: Drop GPL from of_node_to_nid() export to match other arches

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1709179

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

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

Bug description:
  == SRU Justification ==
  The commit requested in this bug exposes functionality needed by the Nvidia 
device driver on POWER9.

  This patch is a clean cherry pick and specific to powerpc.

  This commit is in mainline as of 4.11-rc1.

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

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

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

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

[Kernel-packages] [Bug 1718973] Re: Ubuntu 16.04 freezing

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 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.14-rc2/


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

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

Title:
  Ubuntu 16.04 freezing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed ubuntu 16.04 clean from live usb after wiping windows off of
  lenovo laptop - unity will freeze randomly, except for mouse. freeze
  lasts ~5 minutes usually. not running memory-intensive processes or
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-96-generic 4.4.0-96.119
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   jharman25   1691 F...m pulseaudio
   /dev/snd/controlC1:  jharman25   1691 F pulseaudio
   /dev/snd/controlC0:  jharman25   1691 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 22 09:23:57 2017
  HibernationDevice: RESUME=UUID=40b02c52-ca8d-4ecc-b4e2-0e3a97f73bda
  InstallationDate: Installed on 2017-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20270
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=ed75310a-045b-455f-b401-603706b71df7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-96-generic N/A
   linux-backports-modules-4.4.0-96-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7CCN59WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Cherry 4A Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad U430 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr7CCN59WW:bd06/13/2014:svnLENOVO:pn20270:pvrIdeaPadU430Touch:rvnLENOVO:rnCherry4ATouch:rvr31900058STD:cvnLENOVO:ct10:cvrIdeaPadU430Touch:
  dmi.product.name: 20270
  dmi.product.version: IdeaPad U430 Touch
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1718982] Re: usb usb4-port2: cannot disable (err = -32)

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

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

Title:
  usb usb4-port2: cannot disable (err = -32)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  dmesg:
  [ 7294.705364] usb usb4-port2: cannot disable (err = -32)

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   caravena   1773 F...m pulseaudio
   /dev/snd/controlC1:  caravena   1773 F pulseaudio
   /dev/snd/controlC0:  caravena   1773 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep 22 14:13:45 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (78 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.13.0-11-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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.family: ChiefRiver System
  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/1718982/+subscriptions

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

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

ou may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ideapad 300s AMD A9 7th generation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-96-generic 4.4.0-96.119
  Uname: Linux 4.10.0-33-generic x86_64
  Architecture: amd64
  Date: Sun Sep 24 16:23:03 2017
  Df:
   Filesystem 1K-blocks Used Available Use% Mounted on
   /dev/sda1  953606004 12780512 892362032   2% /
   udev 37903240   3790324   0% /dev
   tmpfs 767868 9628758240   2% /run
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  SourcePackage: linux
  Title: package linux-image-4.4.0-96-generic 4.4.0-96.119 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2

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

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

[Kernel-packages] [Bug 1626984] Re: kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1626984

Title:
  kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-
  xenial-4.4.0/security/apparmor/include/context.h:69!

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

Bug description:
  I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 
4.4.0-38-generic, it get oops while copying 
/sys/module/apparmor/parameters/audit. and it also can be triggered with
  cat /sys/module/apparmor/parameters/audit.

  [  213.174092] [ cut here ]
  [  213.174130] kernel BUG at 
/build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!
  [  213.174187] invalid opcode:  [#1] SMP 
  [  213.174215] Modules linked in: ppdev lp joydev serio_raw parport_pc 
parport psmouse virtio_scsi floppy
  [  213.174283] CPU: 0 PID: 2246 Comm: cat Not tainted 4.4.0-38-generic 
#57~14.04.1-Ubuntu
  [  213.174324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
  [  213.174380] task: 880037b15780 ti: 8800399c4000 task.ti: 
8800399c4000
  [  213.174419] RIP: 0010:[]  [] 
aa_current_raw_label.part.6+0x4/0x6
  [  213.174478] RSP: 0018:8800399c7d60  EFLAGS: 00010246
  [  213.174506] RAX:  RBX: 88003a426000 RCX: 
88003e3802a0
  [  213.174542] RDX: 88003a426000 RSI: 81ddc0d8 RDI: 
88003a426000
  [  213.174578] RBP: 8800399c7d60 R08: 88003e3802a0 R09: 

  [  213.174614] R10: 1000 R11: 0246 R12: 
81e44ae0
  [  213.174658] R13: 88003e3802a0 R14: 81e4c220 R15: 
88003c2b2e40
  [  213.174702] FS:  7f7bea106740() GS:88003fc0() 
knlGS:
  [  213.174743] CS:  0010 DS:  ES:  CR0: 80050033
  [  213.174781] CR2: 00a40038 CR3: 3cdfa000 CR4: 
06f0
  [  213.174819] Stack:
  [  213.174832]  8800399c7d88 8136d58a 88003a426000 
88003a426000
  [  213.174885]  88003e3802a0 8800399c7da0 8136fda2 
88003e39c5f0
  [  213.174928]  8800399c7dd0 8109a7e4 88003c2b2e40 
81a170c0
  [  213.174971] Call Trace:
  [  213.174996]  [] policy_view_capable+0x1ba/0x220
  [  213.175030]  [] param_get_audit+0x12/0x50
  [  213.175062]  [] param_attr_show+0x54/0xa0
  [  213.175092]  [] module_attr_show+0x1d/0x30
  [  213.175130]  [] sysfs_kf_seq_show+0xc2/0x1a0
  [  213.175162]  [] kernfs_seq_show+0x23/0x30
  [  213.175199]  [] seq_read+0xe5/0x350
  [  213.175227]  [] kernfs_fop_read+0x10d/0x170
  [  213.176170]  [] __vfs_read+0x18/0x40
  [  213.177101]  [] vfs_read+0x7f/0x130
  [  213.178016]  [] SyS_read+0x46/0xa0
  [  213.178932]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  213.179814] Code: 80 3d 1a 7f b8 00 00 75 1d 55 be 2e 00 00 00 48 c7 c7 f0 
2f cb 81 48 89 e5 e8 7c 50 cf ff 5d c6 05 fb 7e b8 00 01 c3 55 48 89 e5 <0f> 0b 
b8 01 00 00 00 3e 0f c1 07 ff c0 ff c8 7f 26 80 3d df 7e 
  [  213.182634] RIP  [] aa_current_raw_label.part.6+0x4/0x6
  [  213.183528]  RSP 

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

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

[Kernel-packages] [Bug 1718871] Re: s4 get Error taking CPU down -34

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 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.14-rc2/

** Tags added: kernel-da-key needs-bisect

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

Title:
  s4 get Error taking CPU down -34

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When test S4 on Huawei 1288H V5 server as 
   #echo disk>/sys/power/state
  It show error of
Error taking CPU79 down: -34
Non-boot CPUs are not disabled 

  The echo command return with error of:
Write error: Numerical result out of range 

  From the dmesg it show error of:
CPU79 disable failed: CPU have 2 vectors assigned and there are only 1 
available 
Error taking CPU79 down: -34

  This server have been passed 16.04 certification
  (https://certification.ubuntu.com/hardware/201707-25617/).

  The test kernel is lasted 16.04.1 of linux-image-4.4.0-93-generic. It
  is also failed on 16.04 with kernel of 4.4.9-21-generic,
  4.12.0-041200-generic,4.14.0-999-generic which was download from
  （http://kernel.ubuntu.com/~kernel-ppa/mainline/). But it works on
  14.04 with kernel 3.13.0-24-generic and download kernel of
  3.13.0-031300-generic from above link.

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

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

[Kernel-packages] [Bug 1718713] Re: upon reboot monitor came up with flickerty screen

2017-09-25 Thread ventrical

Hi Joseph,

I had installed  lightdm and removed gdm3 and it boots just fine now.
Then all other packages were clean because I used it to build a unity7
17.10 remix and so it is running on the 4.13 kernel by default. All
other kernels being removed.

If I have time I may try to emulate bug - but for now you can mark this
bug as invalid.

regards..

Dale

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

Title:
  upon reboot monitor came up with flickerty screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the  upgrade of kernel and reboot the VT went black with one
  line of verbose code  then started to flash  with full screen of code
  at least 6 times , top down, bottom up. Then gdm screen and was able
  to logon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ventrical   1935 F pulseaudio
   /dev/snd/controlC0:  ventrical   1935 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Sep 21 11:26:13 2017
  HibernationDevice: RESUME=UUID=73906ed5-985c-4166-9fc2-13fb389012cf
  InstallationDate: Installed on 2017-09-05 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Dell Inc. Precision WorkStation T3400
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=cdef7dd2-7ccb-446a-a39a-df77fea13ef0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0TP412
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd01/31/2008:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T3400
  dmi.sys.vendor: Dell Inc.

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

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

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

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1713553

Title:
  Intel i40e PF reset due to incorrect MDD detection

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

Bug description:
  [Impact]

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

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

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

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

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

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

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

  [Testcase]

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

  [Regression Potential]

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

  [Other Info]

  The previous bug for this issue is bug 1700834.

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

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

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

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1670634

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

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

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
  [

[Kernel-packages] [Bug 1719290] Re: CONFIG_DEBUG_FS is not enabled by "make zfcpdump_defconfig" with Ubuntu 17.10 (kernel 4.13)

CONFIG_DEBUG_FS should be enabled as of Ubuntu-4.13.0-10.11~171.  Can
you test that version or newer and see if this bug is resolved?

** Tags added: kernel-da-key

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

Title:
  CONFIG_DEBUG_FS is not enabled by "make zfcpdump_defconfig" with
  Ubuntu 17.10 (kernel 4.13)

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Ubuntu 17.10 uses kernel 4.13.

  We just found out that on this kernel version CONFIG_DEBUG_FS is not
  enabled by "make zfcpdump_defconfig".

  This makes zfcpdump fail with the following error message:

  ERROR: Unable to mount debugfs 
  No such file or directory

  Patch solving this problem is attached

  As reference following bugzilla
  As reference h
  IBM bugzilla for enabling zfcpdump: 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=139974

  or Launchpad 
  https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1565841

  == Comment: #1 - Heinz-Werner Seeck  -
  2017-09-25 06:00:23 ==

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

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

[Kernel-packages] [Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

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

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

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using artful kernel 4.12.0-13.14, Bluetooth audio works great.

  Upgrading to artful kernel 4.13.0-11.12, there are severe Bluetooth
  audio issues which have manifested in a variety of weird ways:

  1) Playback would stall after 10-20 seconds
  2) Upon removing the device and attempting to redo pairing, no devices could 
be found to pair with
  3) After the device ended up reverting to low quality mono HSP mode, it could 
not be switched back to A2DP

  This is all rather vague - sorry - but it felt better to get notice of
  this regression into the bugtracker sooner rather than later.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maxb   2091 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 24 21:24:00 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=635db8ca-b352-4622-87eb-08f74460324b
  InstallationDate: Installed on 2016-08-16 (404 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Spectre Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=4989886a-f95e-4802-ab51-dcbf53167aeb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-08-31 (23 days ago)
  dmi.bios.date: 02/21/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81A0
  dmi.board.vendor: HP
  dmi.board.version: 48.54
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd02/21/2017:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.54:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1719311] Re: BUG: unable to handle kernel paging request at 00000003ffffffff

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.14 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.14-rc2/

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

Title:
  BUG: unable to handle kernel paging request at 0003

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have 12,000 files in my music library, the scanning of the library
  stopped after # 3,085. It stayed on that number for say 1 minute and
  afterwards this crash happened.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-11-generic.
  Annotation: Your system might become unstable now and might need to be 
restarted.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 
82801AA-ICH]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bertadmin   1714 F...m pulseaudio
   /dev/snd/controlC0:  bertadmin   1714 F pulseaudio
   /dev/snd/timer:  bertadmin   1714 f pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with AD1980 at irq 21'
 Mixer name : 'Analog Devices AD1980'
 Components : 'AC97a:41445370'
 Controls  : 46
 Simple ctrls  : 32
  Date: Mon Sep 25 09:06:20 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:0x3
  Failure: oops
  HibernationDevice: RESUME=UUID=a6a86a55-6b71-479e-b3a2-dd2fecee19f6
  InstallationDate: Installed on 2017-09-23 (1 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170831)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=ceddb6c8-5ac7-4df4-b508-2f403cc0e8de ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: BUG: unable to handle kernel paging request at 0003
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1715609] Re: kernel warning: skb_warn_bad_offload

Can you also give the mainline kernel a test?  A link to it is posted in
comment #13.

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

Title:
  kernel warning: skb_warn_bad_offload

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

Bug description:
  Since upgrading to kernel version 4.10.0-33.37, we're seeing a lot of
  call traces triggered by skb_warn_bad_offload in the syslog.

  Regression introduced when fixing this bug?
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705447


  kernel: [570943.49] [ cut here ]
  kernel: [570943.494448] WARNING: CPU: 3 PID: 21982 at 
/build/linux-hwe-YA6IuF/linux-hwe-4.10.0/net/core/dev.c:2576 
skb_warn_bad_offload+0xd1/0x120
  kernel: [570943.494450] e1000e: caps=(0x0030002149a9, 0x) 
len=1701 data_len=1659 gso_size=1480 gso_type=2 ip_summed=0
  kernel: [570943.494451] Modules linked in: udp_diag tcp_diag inet_diag 
echainiv authenc xfrm4_mode_tunnel xt_state binfmt_misc veth xfrm_user 
xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo bridge stp 
llc iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ppdev 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf hci_uart 
ie31200_edac btbcm edac_core intel_pch_thermal btqca serio_raw btintel 
bluetooth parport_pc parport mac_hid intel_lpss_acpi acpi_pad intel_lpss autofs4
  kernel: [570943.494500]  btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 
e1000e psmouse ptp ahci pps_core libahci wmi pinctrl_sunrisepoint i2c_hid video 
pinctrl_intel hid fjes
  kernel: [570943.494524] CPU: 3 PID: 21982 Comm: charon Tainted: GW
   4.10.0-33-generic #37~16.04.1-Ubuntu
  kernel: [570943.494524] Hardware name: ...
  kernel: [570943.494525] Call Trace:
  kernel: [570943.494541]  
  kernel: [570943.494544]  dump_stack+0x63/0x90
  kernel: [570943.494545]  __warn+0xcb/0xf0
  kernel: [570943.494546]  warn_slowpath_fmt+0x5f/0x80
  kernel: [570943.494547]  ? ___ratelimit+0xa2/0xf0
  kernel: [570943.494549]  skb_warn_bad_offload+0xd1/0x120
  kernel: [570943.494550]  __skb_gso_segment+0x17d/0x190
  kernel: [570943.494564]  validate_xmit_skb+0x14f/0x2a0
  kernel: [570943.494565]  validate_xmit_skb_list+0x43/0x70
  kernel: [570943.494567]  sch_direct_xmit+0x16b/0x1c0
  kernel: [570943.494568]  __dev_queue_xmit+0x47e/0x690
  kernel: [570943.494569]  dev_queue_xmit+0x10/0x20
  kernel: [570943.494570]  ip_finish_output2+0x27a/0x370
  kernel: [570943.494571]  ip_finish_output+0x176/0x270
  kernel: [570943.494571]  ip_output+0x76/0xe0
  kernel: [570943.494572]  ? ip_fragment.constprop.49+0x80/0x80
  kernel: [570943.494573]  ip_forward_finish+0x43/0x70
  kernel: [570943.494574]  ip_forward+0x385/0x460
  kernel: [570943.494575]  ? ip_frag_mem+0x50/0x50
  kernel: [570943.494575]  ip_rcv_finish+0x11b/0x400
  kernel: [570943.494576]  ip_rcv+0x28b/0x3a0
  ...
  kernel: [570943.494632] ---[ end trace f01d0adcc1256afe ]---

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

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

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

It is possible.  I've added a systemd bug task.

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

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

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

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  In Progress
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress
Status in systemd source package in Artful:
  New

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

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

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

  Repro rate: 100%

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

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

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

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

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

[Kernel-packages] [Bug 1719290] Re: CONFIG_DEBUG_FS is not enabled by "make zfcpdump_defconfig" with Ubuntu 17.10 (kernel 4.13)

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

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

** Also affects: linux (Ubuntu Artful)
   Importance: High
 Assignee: Skipper Bug Screeners (skipper-screen-team)
   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/1719290

Title:
  CONFIG_DEBUG_FS is not enabled by "make zfcpdump_defconfig" with
  Ubuntu 17.10 (kernel 4.13)

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Ubuntu 17.10 uses kernel 4.13.

  We just found out that on this kernel version CONFIG_DEBUG_FS is not
  enabled by "make zfcpdump_defconfig".

  This makes zfcpdump fail with the following error message:

  ERROR: Unable to mount debugfs 
  No such file or directory

  Patch solving this problem is attached

  As reference following bugzilla
  As reference h
  IBM bugzilla for enabling zfcpdump: 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=139974

  or Launchpad 
  https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1565841

  == Comment: #1 - Heinz-Werner Seeck  -
  2017-09-25 06:00:23 ==

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

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

[Kernel-packages] [Bug 1718688] Re: Can't connect to a Cisco AP with Wi-Fi Direct Client Policy enabled

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 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.14-rc2/

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

Title:
Can't connect to a Cisco AP with Wi-Fi Direct Client Policy enabled

Status in linux package in Ubuntu:
Incomplete

Bug description:
There is a setting available on selected Cisco hardware named "Wi-Fi
Direct Client Policy". One of the allowed option there is 'not-allow'.
It's intention is to block WiFi P2P capable devices from connecting to
it. If a device trying to associate with an AP with this setting
enabled is identified as "P2P capable" it gets blacklisted (I believe
for a preconfigured time). More info about the option available at [1]
and [2].

This leads to a situation that it is impossible to connect to certain
APs using certain WiFi chips using iwlwifi driver. I was able to
determine that this at least affects Intel 8260 chip.

What's going on on the WiFi level is:
The AP broadcasts beacon frames with P2P IE:
Tag: Vendor Specific: Wi-FiAll: P2P
Tag Number: Vendor Specific (221)
Tag length: 8
OUI: 50-6f-9a (Wi-FiAll)
Vendor Specific OUI Type: 9
P2P Manageability: Bitmap field 0x5
Attribute Type: P2P Manageability (10)
Attribute Length: 1
Manageability Bitmap field: 0x05
...1 = P2P Device Management: 0x1
..0. = Cross Connection Permitted: 0x0
.1.. = Coexistence Optional: 0x1

The client then sends a Probe Request, also with a P2P IE in it:
Tag: Vendor Specific: Wi-FiAll: P2P
Tag Number: Vendor Specific (221)
Tag length: 17
OUI: 50-6f-9a (Wi-FiAll)
Vendor Specific OUI Type: 9
P2P Capability: Device 0x25 Group 0x0
Attribute Type: P2P Capability (2)
Attribute Length: 2
Device Capability Bitmap: 0x25
...1 = Service Discovery: 0x1
..0. = P2P Client Discoverability: 0x0
.1.. = Concurrent Operation: 0x1
0... = P2P Infrastructure Managed: 0x0
...0 = P2P Device Limit: 0x0
..1. = P2P Invitation Procedure: 0x1
Group Capability Bitmap: 0x00
...0 = P2P Group Owner: 0x0
..0. = Persistent P2P Group: 0x0
.0.. = P2P Group Limit: 0x0
0... = Intra-BSS Distribution: 0x0
...0 = Cross Connection: 0x0
..0. = Persistent Reconnect: 0x0
.0.. = Group Formation: 0x0
Listen Channel: Operating Class 81 Channel Number 1
Attribute Type: Listen Channel (6)
Attribute Length: 5
Country String: XX\004
Operating Class: 81
Channel Number: 1

The AP never replies to that Probe Request and blacklists the device
for a given period of time from all communication.

I was able to test a custom kernel with all P2P interfaces commented
out from iwlwifi/mvm/mac80211.c - it was able to connect to the AP
without any issues.

For instance this issue does not affect bcm43224 device running with
brcm80211 - in this case the client device sends a Probe Request
without the P2P IE. Despite it's is actually P2P-capable the AP does
not recognize it as such and allows it to connect.

I have also started a mailing list thread about it [3].

What I think could fix it is either:
* making it behave more like the broadcom driver so it allows users to connect
* provide an user-friendly option of disabling p2p capabilites (including
transmitting probe reuqests without P2P IE)
* as suggested on the ML [4] implement sections 3.4.3/3.4.4 of the WiFi
Direct spec in the driver

According to my knowledge it affects all currently supported releases:
Trusty, Xenial, Zesty plus Artful.

[1]
https://supportforums.cisco.com/t5/security-and-network-management/wi-fi-direct-client-policy/td-p/2253033
[2]
https://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_01010.html
[3] https://marc.info/?l=linux-wireless=150306048824814=2
[4] https://marc.info/?l=linux-wireless=150461784431430=2

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

--
Mailing list:

[Kernel-packages] [Bug 1718761] Re: It's not possible to use OverlayFS (mount -t overlay) to stack directories on a ZFS volume

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

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

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

Title:
  It's not possible to use OverlayFS (mount -t overlay) to stack
  directories on a ZFS volume

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  -- Configuration
  # echo -e $(grep VERSION= /etc/os-release)\\nSIGNATURE=\"$(cat 
/proc/version_signature)\"
  VERSION="16.04.3 LTS (Xenial Xerus)"
  SIGNATURE="Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17"
  # dpkg --list | grep zfs
  ii  libzfs2linux0.6.5.6-0ubuntu18
  ii  zfs-doc 0.6.5.6-0ubuntu18
  ii  zfs-initramfs   0.6.5.6-0ubuntu18
  ii  zfs-zed 0.6.5.6-0ubuntu18
  ii  zfsutils-linux  0.6.5.6-0ubuntu18

  -- Fault: Creating an overlay of multiple directories on a ZFS volume 
does not work
  # df /var/tmp
  Filesystem Type 1K-blocks  Used Available Use% Mounted on
  tank07/var/tmp zfs  129916288   128 129916160   1% /var/tmp
  # mkdir /var/tmp/{lower,middle,upper,workdir,overlay}
  # mount -t overlay overlay 
-olowerdir=/var/tmp/middle:/var/tmp/lower,upperdir=/var/tmp/upper,workdir=/var/tmp/workdir
 /var/tmp/overlay
  mount: wrong fs type, bad option, bad superblock on overlay,
 missing codepage or helper program, or other error

 In some cases useful info is found in syslog - try
 dmesg | tail or so.
  # dmesg|tail -1
  [276328.438284] overlayfs: filesystem on '/var/tmp/upper' not supported as 
upperdir

  -- Control test 1: Creating an overlay of multiple directories on 
another filesystem works
  # df /tmp
  Filesystem Type  1K-blocks   Used Available Use% Mounted on
  tmpfs  tmpfs   1048576 133492915084  13% /tmp
  # mkdir /tmp/{lower,middle,upper,workdir,overlay}
  # mount -t overlay overlay 
-olowerdir=/tmp/middle:/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/workdir 
/tmp/overlay
  # mount | grep overlay
  overlay on /tmp/overlay type overlay 
(rw,relatime,lowerdir=/tmp/middle:/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/workdir)

  -- Control test 2: Creating an overlay using AuFS works on ZFS volume 
and elsewhere
  # mount -t aufs -obr=/tmp/lower:/tmp/middle:/tmp/upper:/tmp/workdir none 
/tmp/overlay
  # mount -t aufs 
-obr=/var/tmp/lower:/var/tmp/middle:/var/tmp/upper:/var/tmp/workdir none 
/var/tmp/overlay
  # mount | grep aufs
  none on /var/tmp/overlay type aufs (rw,relatime,si=9ead1ecae778b250)
  none on /tmp/overlay type aufs (rw,relatime,si=9ead1ec9257d1250)

  -- Remark
  While the use of AuFS can be used as a workaround in the above scenario, AuFS 
in turn will not work with [fuse.]glusterfs mounts (this has been documented 
elsewhere). Given that OverlayFS is part of the (upstream) kernel and Ubuntu 
now officially supports ZFS, the above should be fixed.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 18 16:12 seq
   crw-rw 1 root audio 116, 33 Sep 18 16:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: Red Hat KVM
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: 
BOOT_IMAGE=/ROOT/ubuntu1604@/boot/vmlinuz-4.10.0-35-generic 
root=ZFS=tank07/ROOT/ubuntu1604 ro
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.157.12
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.9.1-5.el7_3.3
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.chassis.version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.9.1-5.el7_3.3:bd04/01/2014:svnRedHat:pnKVM:pvrRHEL7.3.0PC(i440FX+PIIX,1996):cvnRedHat:ct1:cvrRHEL7.3.0PC(i440FX+PIIX,1996):
  dmi.product.name: KVM
  dmi.product.version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
  dmi.sys.vendor: Red Hat
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 18 16:12 seq
   crw-rw 1 root audio 116, 33 Sep 18 16:12 timer
  AplayDevices:

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

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.14 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.14-rc2/

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just extracting a tar.xz ball.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1004 F pulseaudio
scott  1403 F pulseaudio
  Date: Thu Sep 21 09:35:20 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: 0010:vbox_crtc_mode_set+0x41a/0x4c0 [vboxvideo]
  Failure: oops
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic.efi.signed 
root=UUID=99d714bd-8d7f-49b9-9521-9196afff16c4 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0070
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1718713] Re: upon reboot monitor came up with flickerty screen

Does this bug go away if you boot back into the prior kernel version?

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

Title:
  upon reboot monitor came up with flickerty screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the  upgrade of kernel and reboot the VT went black with one
  line of verbose code  then started to flash  with full screen of code
  at least 6 times , top down, bottom up. Then gdm screen and was able
  to logon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ventrical   1935 F pulseaudio
   /dev/snd/controlC0:  ventrical   1935 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Sep 21 11:26:13 2017
  HibernationDevice: RESUME=UUID=73906ed5-985c-4166-9fc2-13fb389012cf
  InstallationDate: Installed on 2017-09-05 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Dell Inc. Precision WorkStation T3400
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=cdef7dd2-7ccb-446a-a39a-df77fea13ef0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0TP412
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd01/31/2008:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T3400
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1718713] Re: upon reboot monitor came up with flickerty screen

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 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.14-rc2/

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

Title:
  upon reboot monitor came up with flickerty screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the  upgrade of kernel and reboot the VT went black with one
  line of verbose code  then started to flash  with full screen of code
  at least 6 times , top down, bottom up. Then gdm screen and was able
  to logon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ventrical   1935 F pulseaudio
   /dev/snd/controlC0:  ventrical   1935 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Sep 21 11:26:13 2017
  HibernationDevice: RESUME=UUID=73906ed5-985c-4166-9fc2-13fb389012cf
  InstallationDate: Installed on 2017-09-05 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Dell Inc. Precision WorkStation T3400
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=cdef7dd2-7ccb-446a-a39a-df77fea13ef0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0TP412
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd01/31/2008:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T3400
  dmi.sys.vendor: Dell Inc.

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

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

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