[Kernel-packages] [Bug 1712580] Can you please help test kernel for bug #712580

[Manoj Iyer]

Jeff,

I have a test kernel in 
https://launchpad.net/~centriq-team/+archive/ubuntu/lp1712580/  This 
kernel has patches to fix the Ubunt u bug 
https://launchpad.net/bugs/1712580

Could you also please reply-all and share the test case and test setup 
along with your test results on QDF2400 platform? I need to be able to 
verify that it works for other architectures as well, especially for 
amd64 and ppc64el because these patches impact the generic kernel.

Thanks
Manoj Iyer.

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

Title:
  [SRU][Zesty]PCI: Add pci_mmap_resource_range() and use it for ARM64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  uio device binding inside VM would fail with errors
  EAL: Detected 3 lcore(s)
  EAL: Probing VFIO support...
  EAL: PCI device :00:01.0 on NUMA socket -1
  EAL: probe driver: 1af4:1000 net_virtio
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource1: No such file or 
directory
  EAL: Cannot open /sys/bus/pci/devices/:00:01.0/resource0: No such file or 
directory
  EAL: Error - exiting with code: 1
Cause: Requested device :00:01.0 cannot be used

  [Fix]
  Fixed in linus kernel by patch 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/include/asm/pci.h?h=v4.13-rc4=f719582435afe9c7985206e42d804ea6aa315d33

  [Test]

  [Regression Potential]

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

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

[Kernel-packages] [Bug 1712495] Re: Please sponsor bluez 5.46-0ubuntu2 to artful

[Jeremy Bicha]

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

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

Title:
  Please sponsor bluez 5.46-0ubuntu2 to artful

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Please sponsor bluez 5.46-0ubuntu2 to artful

  This fixes a crash of zyga's that's been discussed a lot in the past
  but never opened as an official bug report. It has however already
  been fixed upstream and will be included in 5.47.

  It's not yet clear exactly which existing LP bug/error reports this
  will resolve. We'll find out later by tracking errors.ubuntu.com (I
  suspect it might resolve a couple).

  If you need a proper bug report then please ask
  zygmunt.kryni...@canonical.com

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

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

[Kernel-packages] [Bug 344878] Re: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry)

[mhalcrow]

If you want to use ext4 encryption with a subdirectory of your home
directory and don't mind using the e4crypt or fscrypt tools to set it
up, you shouldn't run into any real problems. If you want feature parity
with how eCryptfs works in Ubuntu (i.e., automatically unlocking your
home directory when logging in), I'd wait until 17.10 comes out with
full support for that. fscrypt has all the functionality needed to
implement unlock-on-login, but until 17.10 you'll have to go through the
trouble of setting up PAM and what not yourself.

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

Title:
  file name too long when creating new file (ecryptfs_lookup:
  lookup_one_len() returned [-36] on lower_dentry)

Status in eCryptfs:
  Fix Released
Status in ecryptfs-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in ecryptfs-utils source package in Natty:
  Won't Fix
Status in linux source package in Natty:
  Won't Fix
Status in ecryptfs-utils source package in Oneiric:
  Won't Fix
Status in linux source package in Oneiric:
  Won't Fix
Status in ecryptfs-utils source package in Precise:
  Invalid
Status in linux source package in Precise:
  Fix Released

Bug description:
  ===
  IMPORTANT: eCryptfs can only store filenames of up to 143 characters when 
filename encryption is enabled. The remaining 112 characters are used for 
storing metadata such as the encrypted filename prefix, the signature of the 
filename encryption key, and an identifier for the cipher used, as well as 
random bytes to make /foo/file and /bar/file encrypt to different ciphertext 
and padding bytes to achieve proper cipher block size alignment.

  This bug is considered 'fixed' by the upstream maintainers. The
  eCryptfs kernel error message has been reduced to a debug level log
  message and eCryptfs now correctly reports its maximum supported
  filename length through the statfs() syscall. This is all that can be
  done without implementing a completely new encrypted filename design.
  A design that allows 255 character filenames without introducing other
  design limitations has not been identified and no one is currently
  working to come up with such a design.

  Please do not add comments or create new bugs saying that mv reports
  'File name too long' or that you can't create a long filename in your
  eCryptfs mounts. It is an unfortunate design limitation that cannot be
  avoided at this time.

  Please do create new bugs when an application generates filenames that are 
too long to be stored in an eCryptfs mount. The application may be able to use 
the statfs() syscall to check the filename length limits of eCryptfs. Note that 
this does not include something like a torrent or ftp client trying to download 
a file with a long filename. The application is not generating the filename in 
those cases, it is just downloading the file that the user told it to download.
  ===

  When trying to create a new file with a relatively long filename (f. ex. 
dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt)
  I get an error: file name to long, when in fact the file name is not to long, 
but the encrypted name created for this file is to long, so, the file was not 
created.

  this is no problem when I try to create a file, but when I'm copying a
  lot of files to my home folder I get some: filename to long error's
  and it's hard to fix (first locate the file, create shorter name, move
  again)

  so, maybe you could create a check for to long filenames?

  I'm using ext4 here...

  mv 
dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt
 /home/jens/
  mv: cannot stat 
`/home/jens/dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt':
 File name too long

  libecryptfs0:
    Installed: 71-0ubuntu2
    Candidate: 71-0ubuntu2
    Version table:
   *** 71-0ubuntu2 0
  500 http://be.archive.ubuntu.com jaunty/main Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1672361] Fix included in openstack/tripleo-puppet-elements 7.0.0.0rc1

[OpenStack Infra]

This issue was fixed in the openstack/tripleo-puppet-elements 7.0.0.0rc1
release candidate.

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

Title:
  Ubuntu 17.04: Crash tool fails with error "crash: invalid structure
  size: tnt".

Status in crash package in Ubuntu:
  Fix Released

Bug description:
  Please cherry pick

   Upstream commit 651c824ffe2fd7eb8e416dbf4ff5c9a1da6ef7c6
   commit 24a696228c56fd4354d29abe05b206373e0c8bfb

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

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

[Kernel-packages] [Bug 1445458] Re: BCM4360 bcmwl-kernel-source System Freeze every few Seconds

[Matthew Gregg]

Using 17.04 and get hangs/freezes when using this driver with a BCM4360
based card. Only seems to happen when connected at 5Ghz.

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

Title:
  BCM4360 bcmwl-kernel-source System Freeze every few Seconds

Status in bcmwl package in Ubuntu:
  Fix Committed

Bug description:
  Every newer version of bcmwl-kernel-source than 6.30.223.141+bdcom-
  0ubuntu2 causes complete Freezes on my System every few Seconds.
  Removing the wl module restores the system to its normal state.
  Compiling the latest version 6.30.223.248 from the Broadcom STA Source
  makes no difference as well as using the latest Mainline-Kernel. So
  some of the changes between 6.30.223.141 and 6.30.223.248 must be
  responsible.

  Version 6.30.223.248+bdcom-0ubuntu0.1 installs without any Errors but
  as soon as the wl Module is loaded the Freezes occur. Dmesg shows
  nothing of note.

  $ lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  $ apt-cache policy bcmwl-kernel-source
  bcmwl-kernel-source:
Installiert:   6.30.223.141+bdcom-0ubuntu1
Installationskandidat: 6.30.223.248+bdcom-0ubuntu0.1
Versionstabelle:
   6.30.223.248+bdcom-0ubuntu0.1 0
  500 http://at.archive.ubuntu.com/ubuntu/ trusty-updates/restricted 
amd64 Packages
   6.30.223.141+bdcom-0ubuntu2 0
  500 http://at.archive.ubuntu.com/ubuntu/ trusty/restricted amd64 
Packages
   *** 6.30.223.141+bdcom-0ubuntu1 0
  100 /var/lib/dpkg/status

  Hardware: Asus PCE-AC66
  02:00.0 Network controller: Broadcom Corporation BCM4360 802.11ac Wireless 
Network Adapter (rev 02)

  Apport-Info:
  ProblemType: Bug
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 17 13:55:22 2015
  Dependencies:
   adduser 3.113+nmu3ubuntu3
   apt-utils 1.0.1ubuntu2.6
   base-passwd 3.5.33
   binutils 2.24-5ubuntu3.1
   busybox-initramfs 1:1.21.0-1ubuntu1
   coreutils 8.21-1ubuntu5.1
   cpio 2.11+dfsg-1ubuntu1.1
   cpp 4:4.8.2-1ubuntu6
   cpp-4.8 4.8.2-19ubuntu1
   dbus 1.6.18-0ubuntu4.3
   debconf 1.5.51ubuntu2
   debconf-i18n 1.5.51ubuntu2
   debianutils 4.4
   dkms 2.2.0.3-1.1ubuntu5.14.04
   dpkg 1.17.5ubuntu5.4
   e2fslibs 1.42.9-3ubuntu1.2
   e2fsprogs 1.42.9-3ubuntu1.2
   fakeroot 1.20-3ubuntu2
   findutils 4.4.2-7
   gcc 4:4.8.2-1ubuntu6
   gcc-4.8 4.8.2-19ubuntu1
   gcc-4.8-base 4.8.2-19ubuntu1
   gcc-4.9-base 4.9.1-0ubuntu1
   ifupdown 0.7.47.2ubuntu4.1
   initramfs-tools 0.103ubuntu4.2
   initramfs-tools-bin 0.103ubuntu4.2
   initscripts 2.88dsf-41ubuntu6.1
   insserv 1.14.0-5ubuntu2
   iproute2 3.12.0-2
   isc-dhcp-client 4.2.4-7ubuntu12.1
   isc-dhcp-common 4.2.4-7ubuntu12.1
   klibc-utils 2.0.3-0ubuntu1
   kmod 15-0ubuntu6
   libacl1 2.2.52-1
   libapparmor1 2.8.95~2430-0ubuntu5.1
   libapt-inst1.5 1.0.1ubuntu2.6
   libapt-pkg4.12 1.0.1ubuntu2.6
   libasan0 4.8.2-19ubuntu1
   libatm1 1:2.5.1-1.5
   libatomic1 4.8.2-19ubuntu1
   libattr1 1:2.4.47-1ubuntu1
   libaudit-common 1:2.3.2-2ubuntu1
   libaudit1 1:2.3.2-2ubuntu1
   libblkid1 2.20.1-5.1ubuntu20.4
   libbz2-1.0 1.0.6-5
   libc-dev-bin 2.19-0ubuntu6.6
   libc6 2.19-0ubuntu6.6
   libc6-dev 2.19-0ubuntu6.6
   libcap2 1:2.24-0ubuntu2
   libcgmanager0 0.24-0ubuntu7.3
   libcloog-isl4 0.18.2-1
   libcomerr2 1.42.9-3ubuntu1.2
   libdb5.3 5.3.28-3ubuntu3
   libdbus-1-3 1.6.18-0ubuntu4.3
   libdebconfclient0 0.187ubuntu1
   libdrm2 2.4.56-1~ubuntu2
   libexpat1 2.1.0-4ubuntu1
   libfakeroot 1.20-3ubuntu2
   libgcc-4.8-dev 4.8.2-19ubuntu1
   libgcc1 1:4.9.1-0ubuntu1
   libgmp10 2:5.1.3+dfsg-1ubuntu1
   libgomp1 4.8.2-19ubuntu1
   libgpm2 1.20.4-6.1
   libisl10 0.12.2-1
   libitm1 4.8.2-19ubuntu1
   libjson-c2 0.11-3ubuntu1.2
   libjson0 0.11-3ubuntu1.2
   libklibc 2.0.3-0ubuntu1
   libkmod2 15-0ubuntu6
   liblocale-gettext-perl 1.05-7build3
   liblzma5 5.1.1alpha+20120614-2ubuntu2
   libmount1 2.20.1-5.1ubuntu20.4
   libmpc3 1.0.1-1ubuntu1
   libmpfr4 3.1.2-1
   libncurses5 5.9+20140118-1ubuntu1
   libncursesw5 5.9+20140118-1ubuntu1
   libnih-dbus1 1.0.3-4ubuntu25
   libnih1 1.0.3-4ubuntu25
   libpam-modules 1.1.8-1ubuntu2
   libpam-modules-bin 1.1.8-1ubuntu2
   libpam-runtime 1.1.8-1ubuntu2
   libpam-systemd 204-5ubuntu20.11
   libpam0g 1.1.8-1ubuntu2
   libpcre3 1:8.31-2ubuntu2
   libplymouth2 0.8.8-0ubuntu17.1
   libpng12-0 1.2.50-1ubuntu2
   libprocps3 1:3.3.9-1ubuntu2.2
   libquadmath0 4.8.2-19ubuntu1
   libselinux1 2.2.2-1ubuntu0.1
   libsemanage-common 2.2-1
   libsemanage1 2.2-1
   libsepol1 2.2-1ubuntu0.1
   libslang2 2.2.4-15ubuntu1
   libss2 1.42.9-3ubuntu1.2
   libstdc++6 4.8.2-19ubuntu1
   libsystemd-daemon0 204-5ubuntu20.11
   libsystemd-login0 204-5ubuntu20.11
   libtext-charwidth-perl 0.04-7build3
   libtext-iconv-perl 1.7-5build2
   libtext-wrapi18n-perl 0.06-7
   libtinfo5 5.9+20140118-1ubuntu1
   libtsan0 4.8.2-19ubuntu1
   libudev1 204-5ubuntu20.11
   

[Kernel-packages] [Bug 1578944] Re: regular system freeze - 16.04

[Glenn Fletcher]

had this prob with 16.04 since day one
been with linux since win98 fiasco now ready to go back to win 10
this freezing is a bloody disaster as it freezes with ram at 100% also
has the win98 dev team migrated to ubuntu 16.04
for gods sake release ubuntu 18

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

Title:
  regular system freeze - 16.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  Seems this is common enough to have a few requests on Ask Ubuntu:
  http://askubuntu.com/search?q=16.04+freeze

  I would update my kernel, as suggested, however there are not clear
  instructions and I have had issues doing kernel upgrades in the past.
  The freezes are not Chrome only, as they also occur when Chrome is not
  running, though, from memory, Steam uses some of the same things as
  Chrome.  Once the freeze happens a hard reset (holding down the power
  button) and restarting is the only solution (I can't even open a CLI
  instance).

  Thanks for your time, hope there is a fix soon.  Best regards,

  Taz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tamsyn 1886 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  6 16:45:25 2016
  HibernationDevice: RESUME=UUID=318736d3-a7a7-4b0e-8e64-6cce65e801ad
  InstallationDate: Installed on 2016-04-22 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Acer Aspire E5-511
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=35b282c1-4348-4d7a-90db-fef77f539874 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2014
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.03
  dmi.board.name: Aspire E5-511
  dmi.board.vendor: Acer
  dmi.board.version: V1.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV1.03:bd05/16/2014:svnAcer:pnAspireE5-511:pvrV1.03:rvnAcer:rnAspireE5-511:rvrV1.03:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-511
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1692538] Re: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

[bugproxy]

--- Comment From b...@us.ibm.com 2017-08-24 16:07 EDT---
Works for us.

** Tags added: verification-done-xenial

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

Title:
  Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

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

Bug description:
  == Comment: #0 - BRYANT G. LY  - 2017-05-22 08:40:16 ==
  ---Problem Description---

   - Issue 1: ibmveth doesn't support largesend and checksum offload features
 when configured as "Trunk". Driver has explicit checks to prevent
 enabling these offloads.

   - Issue 2: SYN packet drops seen at destination VM. When the packet
 originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to
 IO server's inbound Trunk ibmveth, on validating "checksum good" bits
 in ibmveth receive routine, SKB's ip_summed field is set with
 CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux
 Bridge) and delivered to outbound Trunk ibmveth. At this point the
 outbound ibmveth transmit routine will not set "no checksum" and
 "checksum good" bits in transmit buffer descriptor, as it does so only
 when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets
 delivered to destination VM, TCP layer receives the packet with checksum
 value of 0 and with no checksum related flags in ip_summed field. This
 leads to packet drops. So, TCP connections never goes through fine.

   - Issue 3: First packet of a TCP connection will be dropped, if there is
 no OVS flow cached in datapath. OVS while trying to identify the flow,
 computes the checksum. The computed checksum will be invalid at the
 receiving end, as ibmveth transmit routine zeroes out the pseudo
 checksum value in the packet. This leads to packet drop.

   - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.
 When Physical NIC has GRO enabled and when OVS bridges these packets,
 OVS vport send code will end up calling dev_queue_xmit, which in turn
 calls validate_xmit_skb.
 In validate_xmit_skb routine, the larger packets will get segmented into
 MSS sized segments, if SKB has a frag_list and if the driver to which
 they are delivered to doesn't support NETIF_F_FRAGLIST feature.
   
  Contact Information = Bryant G. Ly/b...@us.ibm.com 
   
  ---uname output---
  4.8.0-51.54
   
  Machine Type = p8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Increases performance greatly

  The patch has been accepted upstream: 
  https://patchwork.ozlabs.org/patch/764533/

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

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

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

[bugproxy]

--- Comment From lakun...@in.ibm.com 2017-08-24 14:43 EDT---
hmc : daan1.isst.aus.stglabs.ibm.com has address 9.3.48.91 (hscroot/abc123)
CEC : rose
lpar : roselp2.isst.aus.stglabs.ibm.com has address 10.33.23.15 (root/don2rry)

to access the console of lpar
rmvterm -m rose -p roselp2
mkvterm -m rose -p roselp2

lpar is at xmon and ready to debug

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: drop in xmon when running dlpar
  tests under stress

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

Bug description:
  == Comment: #0 - Ping Tian Han  - 2016-12-26 21:59:52 ==
  ---Problem Description---
  When testing DLPAR, include slot/cpu/mem, under stress on roselp4, system 
dropped into xmon:

  roselp4 login: [   95.511790] sysrq: SysRq : Changing Loglevel
  [   95.511816] sysrq: Loglevel set to 9
  [  289.363833] mlx4_en 0292:60:00.0: removed PHC
  [  293.123896] iommu: Removing device 0292:60:00.0 from group 3
  [  303.173744] pci_bus 0292:60: busn_res: [bus 60-ff] is released
  [  303.173865] rpadlpar_io: slot PHB 658 removed
  [  335.853779] iommu: Removing device 0021:01:00.0 from group 0
  [  345.893764] pci_bus 0021:01: busn_res: [bus 01-ff] is released
  [  345.893869] rpadlpar_io: slot PHB 33 removed
  [  382.204003] min_free_kbytes is not updated to 16885 because user defined 
value 551564 is preferred
  [  446.143648] cpu 152 (hwid 152) Ready to die...
  [  446.464057] cpu 153 (hwid 153) Ready to die...
  [  446.473525] cpu 154 (hwid 154) Ready to die...
  [  446.474077] cpu 155 (hwid 155) Ready to die...
  [  446.483529] cpu 156 (hwid 156) Ready to die...
  [  446.493532] cpu 157 (hwid 157) Ready to die...
  [  446.494078] cpu 158 (hwid 158) Ready to die...
  [  446.503527] cpu 159 (hwid 159) Ready to die...
  [  446.664534] cpu 144 (hwid 144) Ready to die...
  [  446.964113] cpu 145 (hwid 145) Ready to die...
  [  446.973525] cpu 146 (hwid 146) Ready to die...
  [  446.974094] cpu 147 (hwid 147) Ready to die...
  [  446.983944] cpu 148 (hwid 148) Ready to die...
  [  446.984062] cpu 149 (hwid 149) Ready to die...
  [  446.993518] cpu 150 (hwid 150) Ready to die...
  [  446.993543] Querying DEAD? cpu 150 (150) shows 2
  [  446.994098] cpu 151 (hwid 151) Ready to die...
  [  447.133726] cpu 136 (hwid 136) Ready to die...
  [  447.403532] cpu 137 (hwid 137) Ready to die...
  [  447.403772] cpu 138 (hwid 138) Ready to die...
  [  447.403839] cpu 139 (hwid 139) Ready to die...
  [  447.403887] cpu 140 (hwid 140) Ready to die...
  [  447.403937] cpu 141 (hwid 141) Ready to die...
  [  447.403979] cpu 142 (hwid 142) Ready to die...
  [  447.404038] cpu 143 (hwid 143) Ready to die...
  [  447.513546] cpu 128 (hwid 128) Ready to die...
  [  447.693533] cpu 129 (hwid 129) Ready to die...
  [  447.693999] cpu 130 (hwid 130) Ready to die...
  [  447.703530] cpu 131 (hwid 131) Ready to die...
  [  447.704087] Querying DEAD? cpu 132 (132) shows 2
  [  447.704102] cpu 132 (hwid 132) Ready to die...
  [  447.713534] cpu 133 (hwid 133) Ready to die...
  [  447.714064] Querying DEAD? cpu 134 (134) shows 2
  cpu 0x86: Vector: 300 (Data Access) at [c7b0fd40]
  pc: 1ec3072c
  lr: 1ec2fee0
  sp: 1faf6bd0
 msr: 800102801000
 dar: 212d6c1a2a20c
   dsisr: 4200
current = 0xc00474c6d600
paca= 0xc7b6b600   softe: 0irq_happened: 0x01
  pid   = 0, comm = swapper/134
  Linux version 4.8.0-34-generic (buildd@bos01-ppc64el-026) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Wed Dec 
21 18:53:20 UTC 2016 (Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11)
  WARNING: exception is not recoverable, can't continue
  enter ? for help
  SP (1faf6bd0) is in userspace
  86:mon> 
  86:mon> t
  SP (1faf6bd0) is in userspace
  86:mon> r
  R00 = 000212d6c1a2a20f   R16 = c0ff1c38
  R01 = 1faf6bd0   R17 = c00474c9c080
  R02 = 1ed1be80   R18 = c00474c9c000
  R03 = 1faf6c80   R19 = c13fdf08
  R04 = 0018   R20 = c00474c9c080
  R05 = 00e0   R21 = c13e8ad0
  R06 = 9e04   R22 = c00474c9c000
  R07 = 1faf6d30   R23 = c0047a9a1c40
  R08 = 1faf6d28   R24 = 0002
  R09 = 000212d6c1a2a20c   R25 = c0fd4e6c
  R10 = 1ec1b118   R26 = c0fd4e6c
  R11 = 1ee7e040   R27 = c14daae0
  R12 = 0163c1d8   R28 = 
  R13 = c7b6b600   R29 = 0086
  R14 = c14defb0   R30 = c0fd4e68
  R15 = 0001   R31 = 1faf6bd0
  pc  = 1ec3072c
  cfar= 1ec2fedc
  lr  = 1ec2fee0
  msr = 800102801000   cr  = 4200
  ctr = 1ec48788   xer = 

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

[bugproxy]

--- Comment From lakun...@in.ibm.com 2017-08-24 14:38 EDT---
As not much info was there in the bug, I tested the kernels (mentioned in 
comment 57) on ubuntu 16.04 (LTS- 4.4.0-92-generic). When tried IO 
(Austin,hydepar EN, Shiner, Glacierpar) and CPU dlpar on both the kernel I 
didnt see any issue. But while removing memory (after adding the to mem to 
lpar), lpar dropped at xmon.

console logs
===
root@roselp2:~# [15615.010274] kernel BUG at mm/memory_hotplug.c:1908!
cpu 0x2a: Vector: 700 (Program Check) at [c0024524b780]
pc: c035d720: remove_memory+0x100/0x120
lr: c035d6ac: remove_memory+0x8c/0x120
sp: c0024524ba00
msr: 80029033
current = 0xc001b2f05c00
paca= 0xcfadb900   softe: 0irq_happened: 0x01
pid   = 48226, comm = drmgr
kernel BUG at mm/memory_hotplug.c:1908!
Linux version 4.13.0-rc5-next-20170817 (bauermann@u1604le) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4)) #2 SMP Mon Aug 21 19:07:20 BRT 
2017
enter ? for help
[c0024524ba40] c00c3554 pseries_remove_memblock+0xe4/0x140
[c0024524ba90] c00c37dc pseries_memory_notifier+0x22c/0x280
[c0024524bad0] c012d1f0 notifier_call_chain+0xa0/0x110
[c0024524bb20] c012d7f8 __blocking_notifier_call_chain+0x78/0xb0
[c0024524bb70] c0a304f8 of_property_notify+0x58/0xc0
[c0024524bbb0] c0a2b320 of_update_property+0x110/0x150
[c0024524bc10] c00b7340 ofdt_write+0x1d0/0x6d0
[c0024524bcd0] c043db7c proc_reg_write+0x8c/0xd0
[c0024524bd00] c0391938 __vfs_write+0x48/0x200
[c0024524bd90] c03936f4 vfs_write+0xd4/0x270
[c0024524bde0] c039558c SyS_write+0x6c/0x110
[c0024524be30] c000b184 system_call+0x58/0x6c
--- Exception: c01 (System Call) at 201ce09c
SP (7fffe1582790) is in userspace
2a:mon> c
cpus stopped: 0x0-0x9f
2a:mon> t
[c0024524ba40] c00c3554 pseries_remove_memblock+0xe4/0x140
[c0024524ba90] c00c37dc pseries_memory_notifier+0x22c/0x280
[c0024524bad0] c012d1f0 notifier_call_chain+0xa0/0x110
[c0024524bb20] c012d7f8 __blocking_notifier_call_chain+0x78/0xb0
[c0024524bb70] c0a304f8 of_property_notify+0x58/0xc0
[c0024524bbb0] c0a2b320 of_update_property+0x110/0x150
[c0024524bc10] c00b7340 ofdt_write+0x1d0/0x6d0
[c0024524bcd0] c043db7c proc_reg_write+0x8c/0xd0
[c0024524bd00] c0391938 __vfs_write+0x48/0x200
[c0024524bd90] c03936f4 vfs_write+0xd4/0x270
[c0024524bde0] c039558c SyS_write+0x6c/0x110
[c0024524be30] c000b184 system_call+0x58/0x6c
--- Exception: c01 (System Call) at 201ce09c
SP (7fffe1582790) is in userspace
2a:mon> r
R00 = c035d6ac   R16 = 
R01 = c0024524ba00   R17 = 
R02 = c15bfb00   R18 = 
R03 = 0001   R19 = 
R04 = c0027668ade8   R20 = 
R05 = c002766a1fe8   R21 = 
R06 = 00015f60   R22 = 
R07 = 0001   R23 = 0100111ecca8
R08 = 0007   R24 = 0100112106b0
R09 = 0002   R25 = c0027e089810
R10 = c0023aa97c80   R26 = 0001
R11 = 303078302d303030   R27 = 1000
R12 = 2200   R28 = 
R13 = cfadb900   R29 = c1494548
R14 =    R30 = 0100
R15 =    R31 = 00028000
pc  = c035d720 remove_memory+0x100/0x120
cfar= c035d6b0 remove_memory+0x90/0x120
lr  = c035d6ac remove_memory+0x8c/0x120
msr = 80029033   cr  = 22002424
ctr =    xer = 2000   trap =  700
2a:mon> d
    ||
2a:mon>

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: drop in xmon when running dlpar
  tests under stress

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

Bug description:
  == Comment: #0 - Ping Tian Han  - 2016-12-26 21:59:52 ==
  ---Problem Description---
  When testing DLPAR, include slot/cpu/mem, under stress on roselp4, system 
dropped into xmon:

  roselp4 login: [   95.511790] sysrq: SysRq : Changing Loglevel
  [   95.511816] sysrq: Loglevel set to 9
  [  289.363833] mlx4_en 0292:60:00.0: removed PHC
  [  293.123896] iommu: Removing device 0292:60:00.0 from group 3
  [  303.173744] pci_bus 0292:60: busn_res: [bus 60-ff] is released
  [  303.173865] rpadlpar_io: slot PHB 658 removed
  [  335.853779] iommu: Removing device 0021:01:00.0 from group 0
  [  345.893764] pci_bus 0021:01: busn_res: [bus 01-ff] is released
  [  345.893869] rpadlpar_io: 

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

[Blake Henderson]

Also see Bug 1709784  -- seems to be the same issue.

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

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

Status in linux package in Ubuntu:
  Incomplete

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

  HWE was out of date so needed to update

  Steps:

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

  afterwards - system seemed ok - kernel 4.4.0.92 installed

  However, launching a Ubuntu VM failed

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

[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

[maravento]

To fix it edit /etc/sysctl.conf and add:
kernel.watchdog_thresh=30
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/1530405

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Dec 31 19:13:12 COMPUTERNAME kernel: [   

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

[bugproxy]

--- Comment From wenxi...@us.ibm.com 2017-08-24 13:16 EDT---
Hi Indira,

Can you verify the Mauricio's kernel with your test?

Thanks,
Wendy

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

Title:
  ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while
  changing SMT value with Leaf IO and BASE tests

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

Bug description:
  == Comment: #0 - INDIRA P. JOGA  - 2017-07-07 
03:56:54 ==
  Description:
  --
  Started Leaf IO and BASE(without smt tests)and then tried to change the SMT 
value manually where it hangs

UBUNTU BUILD: 4.10.0-26-generic

  Steps to re-create:
  --
  > Installed latest Ubuntu160403 kernel on system lotkvm
  4.10.0-26-generic

  > Leaf microcode: KMIPP113

  > Started Leaf IO and BASE tests(without smt tests).

  root@lotkvm:/home# show.report.py
  HOSTNAMEKERNEL VERSION   DISTRO INFO
  ----
  lotkvm  4.10.0-26-genericUbuntu 16.04.2 LTS \n \l

   Current Time: Tue Jul  4 00:55:37 2017 
  Job-IDFOCUS   Start-Time  DurationFunction
  ---   --  
  1 IO  20170704-00:44:45   0.0 hr(s) 10.0 min(s)   IO_Focus
  2 BASE20170704-00:44:52   0.0 hr(s) 10.0 min(s)   Test

  FOCUS IO  BASESUM
  TOTAL 76  25  101
  FAIL  0   4   4
  PASS  76  21  97
  (%)   (100%)  (84%)   (96%)

  >Now manually changed the smt value

  root@lotkvm:/home# ppc64_cpu --smt
  SMT=8
  root@lotkvm:/home# date
  Tue Jul  4 00:46:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=2
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=2
  root@lotkvm:/home# date
  Tue Jul  4 00:50:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=4
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=4
  root@lotkvm:/home# date
  Tue Jul  4 00:54:38 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=8

  
  [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2055.142915]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2055.143226]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 
seconds.
  [ 2055.143647]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 
seconds.
  [ 2055.144029]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds.
  [ 2055.144353]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds.
  [ 2055.144665]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds.
  [ 2055.144936]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds.
  [ 2055.145195]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2175.974848]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2175.975144]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2175.975206] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  
  >  root@lotkvm:# ps -eaf | grep ppc*
  root  48054  12068  0 01:24 pts/000:00:00 grep --color=auto ppc*
  root  80305   5719  0 00:54 hvc0 00:00:00 ppc64_cpu --smt 8

  > ppc64_cpu --smt command hangs here . Not able to change the SMT
  value 

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

[bugproxy]

--- Comment From jhop...@us.ibm.com 2017-08-24 12:41 EDT---
(In reply to comment #15)
> The fixes were applied to zesty/master-next branch and will be available on
> the next kernel SRU cycle.
>
> I removed the verification-done-zesty tag because it must be added only
> after the fixes have been tested with a kernel that's at least in -proposed.
> So the verification will need to be done again when the next SRU kernel hits
> -proposed (a comment will be added when that happens).

Oops sorry, got too excited about verification ;)  Thanks for the info.

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

Title:
  RPT related fixes missing in Ubuntu 16.04.3

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

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

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

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


  ---Problem Description---

  The following patches are missing in the ubuntu 16.04.3 kernel

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

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

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

  ---uname output---

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

  Machine Type = power9

  ---Steps to Reproduce---

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

  Upstream commits mentioned:

  commit  f7327e0ba3805470cced2acfa053e795362ee41d

  powerpc/mm/radix: Remove unnecessary ptesync

  commit  f6b0df55cad252fedd60aa2ba75a0207d0006283

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

  commit  a5998fcb92552a18713b6aa5c146aa400e4d75ee

  powerpc/mm/radix: Optimise tlbiel flush all case

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

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

[Kernel-packages] [Bug 1711056] Re: Backport more recent Broadcom bnxt_en driver

[Kleber Sacilotto de Souza]

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

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

Title:
  Backport more recent Broadcom bnxt_en driver

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

Bug description:
  [Impact]

  The current Xenial bnxt_en driver only supports a limited (old) set of
  Broadcom NICs. We want to support newer NICs in Xenial without adding
  risk for existing users.

  The plan is to provide a separate driver called bnxt_en_bpo which is a
  backported driver from Broadcom. This driver will be modified to only
  support the new NICs that the current kernel driver does not support
  so that they both can co-exist.

  In other words, NICs that used to be supported by Xenial will still be
  managed by the current (unmodified) bnxt_en driver. Newer NICs will be
  managed by the new bnxt_en_bpo driver.

  [Test Case]

  Due to the unavailability of Broadcom HW, the only test that was run
  was to manually load both the bnxt_en and bnxt_en_bpo module to ensure
  that they can co-exist.

  [Regression Potential]

  There should be no regression potential, since the current driver is
  not modified and the new driver only loads for NICs that are not
  handled by the current driver.

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

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

[Kernel-packages] [Bug 1712024] Re: igb: Support using Broadcom 54616 as PHY

[Jim Hodapp]

SRU justification: The igb driver fails to work when using Broadcom
54616 as PHY, thus we need this patch to enable MAAS so that it can use
the management interface on switch platforms that contain this Broadcom
chipset.

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

Title:
  igb: Support using Broadcom 54616 as PHY

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

Bug description:
  The igb driver fails to work when using Broadcom 54616 as PHY.

  00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)

  $ dmesg | grep igb
  [3.472655] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
  [3.480475] igb: Copyright (c) 2007-2014 Intel Corporation.
  [3.584768] igb: probe of :00:14.0 failed with error -2
  [3.965971] igb :00:14.1: added PHC on eth0
  [3.971066] igb :00:14.1: Intel(R) Gigabit Ethernet Network Connection
  [4.010706] igb :00:14.1: eth0: PBA No: 002000-000
  [4.016458] igb :00:14.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.399662] igb :00:14.2: added PHC on eth1
  [4.404738] igb :00:14.2: Intel(R) Gigabit Ethernet Network Connection
  [4.412489] igb :00:14.2: eth1: PBA No: 002000-000
  [4.418235] igb :00:14.2: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.428206] igb :00:14.1 enp0s20f1: renamed from eth0
  [4.465744] igb :00:14.2 enp0s20f2: renamed from eth1

  A patch can be found in OpenNetworkLinux:
  
https://github.com/opencomputeproject/OpenNetworkLinux/blob/master/packages/base/any/kernels/3.18.25/patches
  /driver-support-intel-igb-bcm54616-phy.patch

  It should be safe to include this in an SRU release since the new code
  is only functioning when certain ID is found.

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

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

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

[bugproxy]

--- Comment From jhop...@us.ibm.com 2017-08-24 12:31 EDT---
(In reply to comment #18)
> I built a 17.04(Zesty) test kernel with a pick of commit 8c218578fcbbbdb104.
> This kernel can be downloaded from:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1709964
>
> Can you test this kernel and see if it resolves this bug?

Puvi confirmed in a meeting that this test kernel fixed the PMC5 issue.
Thanks!

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

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

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

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

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

   Performance counter stats for 'system wide':

   r500fa   
   8,162,912  r600f4
  

 1.001562716 seconds time elapsed
   
  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = p9 dd2.0 

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

   Performance counter stats for 'system wide':

   r500fa   
   8,162,912  r600f4
  

 1.001562716 seconds time elapsed

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

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

  powerpc/perf: Fix Power9 test_adder fields
  
  Commit 8d911904f3ce4 ('powerpc/perf: Add restrictions to PMC5 in power9 
DD1')
  was added to restrict the use of PMC5 in Power9 DD1. Intention was to 
disable
  the use of PMC5 using raw event code. But instead of updating the
  power9_isa207_pmu structure (used on DD1), the commit incorrectly updated 
the
  power9_pmu structure. Fix it.
  
  Fixes: 8d911904f3ce ("powerpc/perf: Add restrictions to PMC5 in power9 
DD1")
  Reported-by: Shriya 
  Signed-off-by: Madhavan Srinivasan 
  Tested-by: Shriya 
  Signed-off-by: Michael Ellerman 

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

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

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

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

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

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

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

[Joseph Salisbury]

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

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

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

Thanks in advance

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

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

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

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

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

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

  Repro rate: 100%

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

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

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

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

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

[Kernel-packages] [Bug 1696154] Re: [17.10 FEAT] Sign POWER host/NV kernels

[bugproxy]

** Tags removed: targetmilestone-inin1710
** Tags added: targetmilestone-inin1804

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

Title:
  [17.10 FEAT] Sign POWER host/NV kernels

Status in Launchpad itself:
  Fix Committed
Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-signed package in Ubuntu:
  In Progress

Bug description:
  Feature Description:

  Sign POWER host and NV kernels with sign-file in anticipation of POWER
  secure boot.  Provide the  associated certificate.  Ideally it would
  be possible to reuse the UEFI shim private key and certificate used to
  sign and verify x86_64 kernels.  More details to follow.  Guest
  kernels will be addressed in a future separate feature request.

  
  Business Case: 

  As a system administrator I want to verify the integrity of my kernels
  so that I can prevent malicious kernels from being executed.

  Use Case:

  Signed POWER kernels will be validated by OPAL as OpenPOWER systems
  boot when keys are properly installed and the system is booted in
  secure mode.

  
  Test Case:

  Sign and install a POWER kernel on an OpenPOWER machine with a
  firmware level that supports secure boot.  Install a PK, distro KEK
  certificat, and distro DB certificate.  Boot the system and verify
  that it will boot the kernel.  Negative tests:  Separately remove the
  signature, install an usigned kernel, and modify the kernel image and
  test that the kernel will not boot.

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

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

[Kernel-packages] [Bug 1712857] [NEW] inode-flags stressor is reporting directory errors on startup

[Colin Ian King]

Public bug reported:

Running more than 1 stressor instance throws up the following issue:

  stress-ng: debug: [26676] 4 processors online, 4 processors configured
  stress-ng: info:  [26676] dispatching hogs: 4 inode-flags
  stress-ng: debug: [26676] cache allocate: reducing cache level from L3 (too 
high) to L1
  stress-ng: debug: [26676] cache allocate: default cache size: 64K
  stress-ng: debug: [26676] starting stressors
  stress-ng: debug: [26677] stress-ng-inode-flags: started [26677] (instance 0)
  stress-ng: debug: [26678] stress-ng-inode-flags: started [26678] (instance 1)
  stress-ng: debug: [26679] stress-ng-inode-flags: started [26679] (instance 2)
  stress-ng: debug: [26676] 4 stressors spawned
  stress-ng: debug: [26680] stress-ng-inode-flags: started [26680] (instance 3)
  stress-ng: fail:  [26680] stress-ng-inode-flags: mkdir failed, errno=1 
(Operation not permitted)
  stress-ng: debug: [26680] stress-ng-inode-flags: exited [26680] (instance 3)
  stress-ng: debug: [26678] stress-ng-inode-flags: exited [26678] (instance 1)
  stress-ng: debug: [26677] stress-ng-inode-flags: exited [26677] (instance 0)
  stress-ng: debug: [26679] stress-ng-inode-flags: exited [26679] (instance 2)
  stress-ng: debug: [26676] process [26677] terminated
  stress-ng: debug: [26676] process [26678] terminated
  stress-ng: debug: [26676] process [26679] terminated
  stress-ng: error: [26676] process 26680 (stress-ng-inode_flags) terminated 
with an error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [26676] process [26680] terminated
  stress-ng: info:  [26676] unsuccessful run completed in 5.37s

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Colin Ian King (colin-king)
 Status: 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/1712857

Title:
  inode-flags stressor is reporting directory errors on startup

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Running more than 1 stressor instance throws up the following issue:

stress-ng: debug: [26676] 4 processors online, 4 processors configured
stress-ng: info:  [26676] dispatching hogs: 4 inode-flags
stress-ng: debug: [26676] cache allocate: reducing cache level from L3 (too 
high) to L1
stress-ng: debug: [26676] cache allocate: default cache size: 64K
stress-ng: debug: [26676] starting stressors
stress-ng: debug: [26677] stress-ng-inode-flags: started [26677] (instance 
0)
stress-ng: debug: [26678] stress-ng-inode-flags: started [26678] (instance 
1)
stress-ng: debug: [26679] stress-ng-inode-flags: started [26679] (instance 
2)
stress-ng: debug: [26676] 4 stressors spawned
stress-ng: debug: [26680] stress-ng-inode-flags: started [26680] (instance 
3)
stress-ng: fail:  [26680] stress-ng-inode-flags: mkdir failed, errno=1 
(Operation not permitted)
stress-ng: debug: [26680] stress-ng-inode-flags: exited [26680] (instance 3)
stress-ng: debug: [26678] stress-ng-inode-flags: exited [26678] (instance 1)
stress-ng: debug: [26677] stress-ng-inode-flags: exited [26677] (instance 0)
stress-ng: debug: [26679] stress-ng-inode-flags: exited [26679] (instance 2)
stress-ng: debug: [26676] process [26677] terminated
stress-ng: debug: [26676] process [26678] terminated
stress-ng: debug: [26676] process [26679] terminated
stress-ng: error: [26676] process 26680 (stress-ng-inode_flags) terminated 
with an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [26676] process [26680] terminated
stress-ng: info:  [26676] unsuccessful run completed in 5.37s

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

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

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

[ChristianEhrhardt]

ok, every bot is different, this one wants confirmed to be silent.
Setting that ...

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

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

  But since this is lovely qemu the machine isn't as dead as real HW now, so 
via the monitor
  $ sudo nc -U 

[Kernel-packages] [Bug 1712857] Re: inode-flags stressor is reporting directory errors on startup

[Colin Ian King]

Fix committed: http://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=8a95d739ca957aa00b65ca7f186653e13f06b4e8

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

Title:
  inode-flags stressor is reporting directory errors on startup

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Running more than 1 stressor instance throws up the following issue:

stress-ng: debug: [26676] 4 processors online, 4 processors configured
stress-ng: info:  [26676] dispatching hogs: 4 inode-flags
stress-ng: debug: [26676] cache allocate: reducing cache level from L3 (too 
high) to L1
stress-ng: debug: [26676] cache allocate: default cache size: 64K
stress-ng: debug: [26676] starting stressors
stress-ng: debug: [26677] stress-ng-inode-flags: started [26677] (instance 
0)
stress-ng: debug: [26678] stress-ng-inode-flags: started [26678] (instance 
1)
stress-ng: debug: [26679] stress-ng-inode-flags: started [26679] (instance 
2)
stress-ng: debug: [26676] 4 stressors spawned
stress-ng: debug: [26680] stress-ng-inode-flags: started [26680] (instance 
3)
stress-ng: fail:  [26680] stress-ng-inode-flags: mkdir failed, errno=1 
(Operation not permitted)
stress-ng: debug: [26680] stress-ng-inode-flags: exited [26680] (instance 3)
stress-ng: debug: [26678] stress-ng-inode-flags: exited [26678] (instance 1)
stress-ng: debug: [26677] stress-ng-inode-flags: exited [26677] (instance 0)
stress-ng: debug: [26679] stress-ng-inode-flags: exited [26679] (instance 2)
stress-ng: debug: [26676] process [26677] terminated
stress-ng: debug: [26676] process [26678] terminated
stress-ng: debug: [26676] process [26679] terminated
stress-ng: error: [26676] process 26680 (stress-ng-inode_flags) terminated 
with an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [26676] process [26680] terminated
stress-ng: info:  [26676] unsuccessful run completed in 5.37s

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1712831

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

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

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

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

[Kernel-packages] [Bug 1708096] Re: Ubuntu16.04.3 Installation fails for JFS file system

[bugproxy]

** Tags removed: bugnameltc-156861 kernel-da-key kernel-key severity-
high 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/1708096

Title:
  Ubuntu16.04.3 Installation fails for JFS file system

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

Bug description:
  ---Problem Description---

  Ubuntu16.04.3 installation fails for JFS file system.

  
  ---Environment---
  Garrison Power8

  
  ---Steps to reproduce---
   Install Ubuntu 16.04.3 with 
   - prepboot
  - /root [JFS filesystem]
  - swap space

  
  ---Fails in below step---

   ?? [!!] Install the GRUB boot loader on a hard disk ??
? ?
?  ?Unable to install GRUB in /dev/sdi1 ? ?
?  ? Executing 'grub-install /dev/sdi1' failed. ? ?
?  ?? ?
? Running "? This is a fatal error. ? ?
?  ?? ?
 ? ?
   ??
   ??



  
   moves;  selects;  activates buttons



  
   ? [!!] Install the GRUB boot loader on a hard disk ??
   ?   ?
   ? Installation step failed  ?
   ? An installation step failed. You can try to run the failing item  ?
   ? again from the menu, or skip it and choose something else. The?
   ? failing step is: Install the GRUB boot loader on a hard disk  ?
   ?   ?
   ? ?
   ?   ?
   ?



  
   moves;  selects;  activates buttons

  
  Comment 3 2017-07-20 04:31:05 CDT

  Based on your error, may be you deleted partition 1 (8MB the PReP boot
  partition) which is required for installing the boot loader in IBM
  power systems.  Or maybe you changed the use type to JFS from PReP
  boot.

  Partition 1 (PReP boot) does NOT contain a filesystem and is not
  mounted.Grub is written to it raw and the firmware loads the contents
  of the partition into ram and executes it raw.

  Can you try one more time,
  Pick the default guided partitioning, then change the root 
partition(partition 2) from ext4(or  filesystem) to JFS.Do not delete and 
create any partitions from the default guided setup. Paste the results.

  Comment 4  2017-07-20 09:22:22 CDT

  (In reply to comment #3)
  > Based on your error, may be you deleted partition 1 (8MB the PReP boot
  > partition) which is required for installing the boot loader in IBM power
  > systems.  Or maybe you changed the use type to JFS from PReP boot. 
  > 
  > Partition 1 (PReP boot) does NOT contain a filesystem and is not
  > mounted.Grub is written to it raw and the firmware loads the contents of the
  > partition into ram and executes it raw.
  > 
  > Can you try one more time,
  > Pick the default guided partitioning, then change the root
  > partition(partition 2) from ext4(or  filesystem) to JFS.Do not delete
  > and create any partitions from the default guided setup. Paste the results.

  No, I have not deleted partition and I have not changed the use type
  to JFS from PReP boot.

  Any ways I tried again and it still fails.

  ?? [!!] Partition disks ???
? ?
? This is an overview of your currently configured partitions and mount   ?
? points. Select a partition to modify its settings (file system, mount   ?
? point, etc.), a free space to create partitions, or a device to ?
? initialize its partition table. ?
? ?
?  SCSI4 (0,0,0) (sdi) - 1.0 TB ATA ST1000NX0313  ?
?  >1.0 MBFREE SPACE  ?   ?
?  > #1 7.3 MB K  ?   ?
?  > #2   959.7 GB F  ext4  / ?   ?
?  > #340.5 GB f  swap  swap  ?
?  >  728.6 kBFREE SPACE  ?   ?
?  SCSI5 (0,0,0) (sdj) - 1.0 TB ATA ST1000NX0313  ?   

[Kernel-packages] [Bug 1708096] Re: Ubuntu16.04.3 Installation fails for JFS file system

[Joseph Salisbury]

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

Title:
  Ubuntu16.04.3 Installation fails for JFS file system

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

Bug description:
  ---Problem Description---

  Ubuntu16.04.3 installation fails for JFS file system.

  
  ---Environment---
  Garrison Power8

  
  ---Steps to reproduce---
   Install Ubuntu 16.04.3 with 
   - prepboot
  - /root [JFS filesystem]
  - swap space

  
  ---Fails in below step---

   ?? [!!] Install the GRUB boot loader on a hard disk ??
? ?
?  ?Unable to install GRUB in /dev/sdi1 ? ?
?  ? Executing 'grub-install /dev/sdi1' failed. ? ?
?  ?? ?
? Running "? This is a fatal error. ? ?
?  ?? ?
 ? ?
   ??
   ??



  
   moves;  selects;  activates buttons



  
   ? [!!] Install the GRUB boot loader on a hard disk ??
   ?   ?
   ? Installation step failed  ?
   ? An installation step failed. You can try to run the failing item  ?
   ? again from the menu, or skip it and choose something else. The?
   ? failing step is: Install the GRUB boot loader on a hard disk  ?
   ?   ?
   ? ?
   ?   ?
   ?



  
   moves;  selects;  activates buttons

  
  Comment 3 2017-07-20 04:31:05 CDT

  Based on your error, may be you deleted partition 1 (8MB the PReP boot
  partition) which is required for installing the boot loader in IBM
  power systems.  Or maybe you changed the use type to JFS from PReP
  boot.

  Partition 1 (PReP boot) does NOT contain a filesystem and is not
  mounted.Grub is written to it raw and the firmware loads the contents
  of the partition into ram and executes it raw.

  Can you try one more time,
  Pick the default guided partitioning, then change the root 
partition(partition 2) from ext4(or  filesystem) to JFS.Do not delete and 
create any partitions from the default guided setup. Paste the results.

  Comment 4  2017-07-20 09:22:22 CDT

  (In reply to comment #3)
  > Based on your error, may be you deleted partition 1 (8MB the PReP boot
  > partition) which is required for installing the boot loader in IBM power
  > systems.  Or maybe you changed the use type to JFS from PReP boot. 
  > 
  > Partition 1 (PReP boot) does NOT contain a filesystem and is not
  > mounted.Grub is written to it raw and the firmware loads the contents of the
  > partition into ram and executes it raw.
  > 
  > Can you try one more time,
  > Pick the default guided partitioning, then change the root
  > partition(partition 2) from ext4(or  filesystem) to JFS.Do not delete
  > and create any partitions from the default guided setup. Paste the results.

  No, I have not deleted partition and I have not changed the use type
  to JFS from PReP boot.

  Any ways I tried again and it still fails.

  ?? [!!] Partition disks ???
? ?
? This is an overview of your currently configured partitions and mount   ?
? points. Select a partition to modify its settings (file system, mount   ?
? point, etc.), a free space to create partitions, or a device to ?
? initialize its partition table. ?
? ?
?  SCSI4 (0,0,0) (sdi) - 1.0 TB ATA ST1000NX0313  ?
?  >1.0 MBFREE SPACE  ?   ?
?  > #1 7.3 MB K  ?   ?
?  > #2   959.7 GB F  ext4  / ?   ?
?  > #340.5 GB f  swap  swap  ?
?  >  728.6 kBFREE SPACE  ?   ?
?  SCSI5 (0,0,0) (sdj) - 1.0 TB ATA ST1000NX0313  ?   ?
?  > #1  primary4.2 MB  B

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

[ChristianEhrhardt]

Hi Bot,
this issue does not need the usual logs IMHO, reproducible as instructed "on 
demand" - setting back to new.

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

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

Status in linux package in Ubuntu:
  New

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

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

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

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

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

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

  But since this is lovely qemu the machine isn't as dead as real HW now, so 
via the monitor
  $ sudo 

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

[Joseph Salisbury]

We can perform a "Reverse" bisect to identify the commit that partially
fixes this issue.  We first need to know the last kernel that had the
bug and the first kernel version that did not.  Can you test the
following kernel next:

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

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

Title:
   Fn Keys Not working Ubuntu 16.04 Asus FX553Vd

Status in linux package in Ubuntu:
  Confirmed

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: 

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

[Ubuntu Kernel Bot]

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

apport-collect 1712831

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

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

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

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

** Tags added: artful

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

[Kernel-packages] [Bug 1712495] Re: Please sponsor bluez 5.46-0ubuntu2 to artful

[Konrad Zapałowicz]

@Timo,

thanks man, appreciated.

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

Title:
  Please sponsor bluez 5.46-0ubuntu2 to artful

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Please sponsor bluez 5.46-0ubuntu2 to artful

  This fixes a crash of zyga's that's been discussed a lot in the past
  but never opened as an official bug report. It has however already
  been fixed upstream and will be included in 5.47.

  It's not yet clear exactly which existing LP bug/error reports this
  will resolve. We'll find out later by tracking errors.ubuntu.com (I
  suspect it might resolve a couple).

  If you need a proper bug report then please ask
  zygmunt.kryni...@canonical.com

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

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

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

[ChristianEhrhardt]

The last two known good runs on LP infra also were on the same kernel 
4.12.0.11.12, no idea yet what has changed.
Maybe the openvswitch upload itself a while ago - but that worked as well on LP 
infra ... ?

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

  But since this is lovely qemu the machine isn't as dead as real HW 

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

[ChristianEhrhardt]

Public bug reported:

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

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

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

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


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

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

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

Fetching the i386 debug kernel shows me I can load that in crash.


But I'd leave the authoritative look what happened to the kernel Team. So I 
shared via fileshare.
Please load with debug-kernel of linux-image-4.12.0-11-generic-dbgsym.
I have issues properly loading that in crash as this is a i386 artful on a 
64bit KVM, so the format of the kdump generated by qemu is x86_64 and something 
seems to disagree.
But since I have simple repro steps above I hope you can crash and analyze it 
the way you want/need.

In case you still want my dump fetch it from 

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

[Varga Péter]

I *think* I have the same touchpad issue with an IdeaPad 320. How do I
find out if I have the same touchpad as in the Flex? I have no Windows
to find out running it:(

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

[Kernel-packages] [Bug 1712495] Re: Please sponsor bluez 5.46-0ubuntu2 to artful

[Timo Aaltonen]

sponsored, though I didn't notice before uploading that it won't close
this bug.. so do it manually once it's in the archive

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

Title:
  Please sponsor bluez 5.46-0ubuntu2 to artful

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Please sponsor bluez 5.46-0ubuntu2 to artful

  This fixes a crash of zyga's that's been discussed a lot in the past
  but never opened as an official bug report. It has however already
  been fixed upstream and will be included in 5.47.

  It's not yet clear exactly which existing LP bug/error reports this
  will resolve. We'll find out later by tracking errors.ubuntu.com (I
  suspect it might resolve a couple).

  If you need a proper bug report then please ask
  zygmunt.kryni...@canonical.com

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

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

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2017-08-24 08:39 EDT---
IBM Bugzilla status: closed-> available with kernel 4.11 in artfiul

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

Title:
  [17.10 FEAT] Architecture-conforming PGID generation

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  All non-Linux z Systems operating systems implement a "New" format for
  PGID generation:

  New Path Group Identifier Format (11 bytes)
  -
  | xxyyzyyy| CSSID   | LPAR id |CPU serial #|CPU model|TOD Clock |
  -
  1 2 3 46 8 11
 
  where xx = 00 means old PGID format
 10 means new PGID format
 01 reserved for future use  
 11 reserved for future use  
z = 1 means PGID was created by the hipervisor (VM) 

  Linux makes use of the same format, with the exception of the CSSID
  field. Linux stores the effective CSSID (always 0 for non-MCSS-E
  systems), whereas all other operating systems store the real CSSID.
  While this difference does not have an immediate functional effect,
  with mechanisms like Query Host Access to Volume support, PGIDs are
  now a user-visible data point and using the correct CSSID field helps
  in identifying hosts via their PGID in case of problems.

  This item is about changing the Linux PGID generation code to query
  the actual CSSID of a subchannel, and to use that CSSID in the
  generation of Linux-provided PGIDs. The real CSSID can be obtained
  e.g. using the Store Domain Config Attributes List CHSC. There may be
  other places where the real CSSID information associated with a
  CHPID/subchannel may be useful (e.g. SysFS, lscss).

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

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

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

[Blake Henderson]

not able to run apport-collect


It appears that the latest upstream stable kernel is v4.4.83 -- I have that 
installed and it is ok- no issues- the problem does not exist in this kernel.

However, a apt update installed 4.4.0-92 - this one did have issues.  I
have 9 more systems to update- it would be better if an apt update
installed 4.4.83- not 4.4.92

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

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

Status in linux package in Ubuntu:
  Incomplete

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

  HWE was out of date so needed to update

  Steps:

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

  afterwards - system seemed ok - kernel 4.4.0.92 installed

  However, launching a Ubuntu VM failed

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1712804

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

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

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

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

** Tags added: artful

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

Title:
  4.12.0-11-generic rejects kernel modules signed with enrolled key

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I've been signing my DKMS modules manually for some time and it was
  working just fine with 17.04 but since I upgraded to 17.10 and signing
  the modules again the kernel rejects them.

  Version: Ubuntu 4.12.0-11.12-generic 4.12.5

  ```
  $ sudo mokutil --import MOK.der 
  SKIP: MOK.der is already enrolled

  $ sudo /usr/src/linux-headers-4.12.0-11-generic/scripts/sign-file
  sha512 MOK.priv MOK.der
  /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko

  $ sudo hexdump -C /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko | 
tail
  00085530  73 59 c9 38 05 53 a3 95  df df c6 ca 93 ef ad 87  |sY.8.S..|
  00085540  38 52 a4 41 4b b6 79 e7  1f 02 49 d7 ba 7c 60 21  |8R.AK.y...I..|`!|
  00085550  94 9a b8 c2 d2 73 68 91  fc e8 12 c1 e9 68 21 eb  |.sh..h!.|
  00085560  55 d1 0b 6f 4e 04 ee b2  e7 a7 47 42 07 bb 0e 3b  |U..oN.GB...;|
  00085570  8a fa 9c d0 7f 1e d5 af  92 8a a3 db 13 32 6d f1  |.2m.|
  00085580  c0 c7 6a 31 c6 39 39 14  0d ec 19 73 7e 14 1b e6  |..j1.99s~...|
  00085590  8d 1b 5c 7a 0c 26 00 00  02 00 00 00 00 00 00 00  |..\z.&..|
  000855a0  01 8b 7e 4d 6f 64 75 6c  65 20 73 69 67 6e 61 74  |..~Module signat|
  000855b0  75 72 65 20 61 70 70 65  6e 64 65 64 7e 0a|ure appended~.|
  000855be

  $ sudo modprobe vboxdrv
  modprobe: ERROR: could not insert 'vboxdrv': Required key not available
  ```

  dmesg shows:
  ```
  [260594.834844] PKCS#7 signature not signed with a trusted key
  ```

  It also seems like modinfo doesn't recognize/shows the signing
  details:

  ```
  $ sudo modinfo /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko
  filename:   /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko
  version:5.1.26_Ubuntu r117224 (0x002a)
  license:GPL
  description:Oracle VM VirtualBox Support Driver
  author: Oracle Corporation
  srcversion: 135FF31DCB56FAD62FFCD36
  depends:
  vermagic:   4.12.0-11-generic SMP mod_unload 
  signat: PKCS#7
  signer: 
  sig_key:
  sig_hashalgo:   md4
  parm:   force_async_tsc:force the asynchronous TSC mode (int)
  ```

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

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

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2017-08-24 08:13 EDT---
IBM Bugzilla Staus: closed -> already implemented

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

Title:
  [17.10 FEAT] Enable NVMe driver - kernel

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Distributor ToDos:
  - Enable Linux kernel configuration options related to the Linux PCI NVMe 
device driver (CONFIG_BLK_DEV_NVME)
  - Include NVMe driver in kdump kernel

  - Include package "nvme-cli" on s390x -> already available !

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

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

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

[bugproxy]

** Tags removed: severity-critical
** Tags added: severity-high

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

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

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

Bug description:
  SRU Justification:

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

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

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

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

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

  The business justification for the SRU is:

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

  Thanks.

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

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

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

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

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

[Kernel-packages] [Bug 1712804] Re: 4.12.0-11-generic rejects kernel modules signed with enrolled key

[fish]

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

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

Title:
  4.12.0-11-generic rejects kernel modules signed with enrolled key

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  I've been signing my DKMS modules manually for some time and it was
  working just fine with 17.04 but since I upgraded to 17.10 and signing
  the modules again the kernel rejects them.

  Version: Ubuntu 4.12.0-11.12-generic 4.12.5

  ```
  $ sudo mokutil --import MOK.der 
  SKIP: MOK.der is already enrolled

  $ sudo /usr/src/linux-headers-4.12.0-11-generic/scripts/sign-file
  sha512 MOK.priv MOK.der
  /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko

  $ sudo hexdump -C /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko | 
tail
  00085530  73 59 c9 38 05 53 a3 95  df df c6 ca 93 ef ad 87  |sY.8.S..|
  00085540  38 52 a4 41 4b b6 79 e7  1f 02 49 d7 ba 7c 60 21  |8R.AK.y...I..|`!|
  00085550  94 9a b8 c2 d2 73 68 91  fc e8 12 c1 e9 68 21 eb  |.sh..h!.|
  00085560  55 d1 0b 6f 4e 04 ee b2  e7 a7 47 42 07 bb 0e 3b  |U..oN.GB...;|
  00085570  8a fa 9c d0 7f 1e d5 af  92 8a a3 db 13 32 6d f1  |.2m.|
  00085580  c0 c7 6a 31 c6 39 39 14  0d ec 19 73 7e 14 1b e6  |..j1.99s~...|
  00085590  8d 1b 5c 7a 0c 26 00 00  02 00 00 00 00 00 00 00  |..\z.&..|
  000855a0  01 8b 7e 4d 6f 64 75 6c  65 20 73 69 67 6e 61 74  |..~Module signat|
  000855b0  75 72 65 20 61 70 70 65  6e 64 65 64 7e 0a|ure appended~.|
  000855be

  $ sudo modprobe vboxdrv
  modprobe: ERROR: could not insert 'vboxdrv': Required key not available
  ```

  dmesg shows:
  ```
  [260594.834844] PKCS#7 signature not signed with a trusted key
  ```

  It also seems like modinfo doesn't recognize/shows the signing
  details:

  ```
  $ sudo modinfo /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko
  filename:   /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko
  version:5.1.26_Ubuntu r117224 (0x002a)
  license:GPL
  description:Oracle VM VirtualBox Support Driver
  author: Oracle Corporation
  srcversion: 135FF31DCB56FAD62FFCD36
  depends:
  vermagic:   4.12.0-11-generic SMP mod_unload 
  signat: PKCS#7
  signer: 
  sig_key:
  sig_hashalgo:   md4
  parm:   force_async_tsc:force the asynchronous TSC mode (int)
  ```

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1712803

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

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

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

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

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

Title:
  spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe
  kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel: 4.10.0-33.37~16.04.1

  I think this issue was introduced by the old qemu version (similar
  issue was spotted on Xenial before), will need to investigate this
  further.

  
  qemu-system-ppc64 -machine pseries,accel=kvm -bios powerpc/boot_rom.bin 
-display none -serial stdio -kernel powerpc/spapr_hcall.elf -smp 1
  FAIL: hypercall: h_set_sprg0: sprg0 = 0xcafebabedeadbeef
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x41a588
  FAIL: hypercall: h_page_init: h_zero_page
  FAIL: hypercall: h_page_init: h_copy_page
  FAIL: hypercall: h_page_init: h_copy_page+h_zero_page
  FAIL: hypercall: h_page_init: h_zero_page unaligned dst
  FAIL: hypercall: h_page_init: h_copy_page unaligned src
  XFAIL: hypercall: h_random: h-call available

  SUMMARY: 9 tests, 8 unexpected failures, 1 expected failures

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was a distro provided on a magazine. A few years ago. I am trying to 
start using Linux but had to put this machine away for some time. Now I have 
come back to it to find this error. I have attempted to obtain updates and 
upgrades to no avail. I may try a different version of Linux if this does not 
work. Admittedly, it is an old portable computer but I did not like the idea of 
working equipment being sent for scrap or recycling.
  All the best. Ian

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-84-generic (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic i686
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 997 F pulseaudio
  Date: Thu Aug 24 12:35:12 2017
  DuplicateSignature: package:linux-image-3.19.0-84-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=4e3df44a-93e5-40f0-a2d5-e09806eb9d50
  InstallationDate: Installed on 2015-08-29 (725 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  IwConfig:
   irda0 no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard HP Compaq nc6000 (DP894A#ABU)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=23e721d5-1b3f-418c-bcab-e03f284d2e71 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-22ubuntu1.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-3.19.0-84-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2004
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68BDD Ver. F.0F
  dmi.board.name: 0890
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 8051 Version 1A.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68BDDVer.F.0F:bd07/23/2004:svnHewlett-Packard:pnHPCompaqnc6000(DP894A#ABU):pvrF.0F:rvnHewlett-Packard:rn0890:rvr8051Version1A.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nc6000 (DP894A#ABU)
  dmi.product.version: F.0F
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1712804] [NEW] 4.12.0-11-generic rejects kernel modules signed with enrolled key

[fish]

Public bug reported:

Hi,

I've been signing my DKMS modules manually for some time and it was
working just fine with 17.04 but since I upgraded to 17.10 and signing
the modules again the kernel rejects them.

Version: Ubuntu 4.12.0-11.12-generic 4.12.5

```
$ sudo mokutil --import MOK.der 
SKIP: MOK.der is already enrolled

$ sudo /usr/src/linux-headers-4.12.0-11-generic/scripts/sign-file sha512
MOK.priv MOK.der /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko

$ sudo hexdump -C /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko | tail
00085530  73 59 c9 38 05 53 a3 95  df df c6 ca 93 ef ad 87  |sY.8.S..|
00085540  38 52 a4 41 4b b6 79 e7  1f 02 49 d7 ba 7c 60 21  |8R.AK.y...I..|`!|
00085550  94 9a b8 c2 d2 73 68 91  fc e8 12 c1 e9 68 21 eb  |.sh..h!.|
00085560  55 d1 0b 6f 4e 04 ee b2  e7 a7 47 42 07 bb 0e 3b  |U..oN.GB...;|
00085570  8a fa 9c d0 7f 1e d5 af  92 8a a3 db 13 32 6d f1  |.2m.|
00085580  c0 c7 6a 31 c6 39 39 14  0d ec 19 73 7e 14 1b e6  |..j1.99s~...|
00085590  8d 1b 5c 7a 0c 26 00 00  02 00 00 00 00 00 00 00  |..\z.&..|
000855a0  01 8b 7e 4d 6f 64 75 6c  65 20 73 69 67 6e 61 74  |..~Module signat|
000855b0  75 72 65 20 61 70 70 65  6e 64 65 64 7e 0a|ure appended~.|
000855be

$ sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available
```

dmesg shows:
```
[260594.834844] PKCS#7 signature not signed with a trusted key
```

It also seems like modinfo doesn't recognize/shows the signing details:

```
$ sudo modinfo /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko
filename:   /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko
version:5.1.26_Ubuntu r117224 (0x002a)
license:GPL
description:Oracle VM VirtualBox Support Driver
author: Oracle Corporation
srcversion: 135FF31DCB56FAD62FFCD36
depends:
vermagic:   4.12.0-11-generic SMP mod_unload 
signat: PKCS#7
signer: 
sig_key:
sig_hashalgo:   md4
parm:   force_async_tsc:force the asynchronous TSC mode (int)
```

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

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

Title:
  4.12.0-11-generic rejects kernel modules signed with enrolled key

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  I've been signing my DKMS modules manually for some time and it was
  working just fine with 17.04 but since I upgraded to 17.10 and signing
  the modules again the kernel rejects them.

  Version: Ubuntu 4.12.0-11.12-generic 4.12.5

  ```
  $ sudo mokutil --import MOK.der 
  SKIP: MOK.der is already enrolled

  $ sudo /usr/src/linux-headers-4.12.0-11-generic/scripts/sign-file
  sha512 MOK.priv MOK.der
  /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko

  $ sudo hexdump -C /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko | 
tail
  00085530  73 59 c9 38 05 53 a3 95  df df c6 ca 93 ef ad 87  |sY.8.S..|
  00085540  38 52 a4 41 4b b6 79 e7  1f 02 49 d7 ba 7c 60 21  |8R.AK.y...I..|`!|
  00085550  94 9a b8 c2 d2 73 68 91  fc e8 12 c1 e9 68 21 eb  |.sh..h!.|
  00085560  55 d1 0b 6f 4e 04 ee b2  e7 a7 47 42 07 bb 0e 3b  |U..oN.GB...;|
  00085570  8a fa 9c d0 7f 1e d5 af  92 8a a3 db 13 32 6d f1  |.2m.|
  00085580  c0 c7 6a 31 c6 39 39 14  0d ec 19 73 7e 14 1b e6  |..j1.99s~...|
  00085590  8d 1b 5c 7a 0c 26 00 00  02 00 00 00 00 00 00 00  |..\z.&..|
  000855a0  01 8b 7e 4d 6f 64 75 6c  65 20 73 69 67 6e 61 74  |..~Module signat|
  000855b0  75 72 65 20 61 70 70 65  6e 64 65 64 7e 0a|ure appended~.|
  000855be

  $ sudo modprobe vboxdrv
  modprobe: ERROR: could not insert 'vboxdrv': Required key not available
  ```

  dmesg shows:
  ```
  [260594.834844] PKCS#7 signature not signed with a trusted key
  ```

  It also seems like modinfo doesn't recognize/shows the signing
  details:

  ```
  $ sudo modinfo /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko
  filename:   /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko
  version:5.1.26_Ubuntu r117224 (0x002a)
  license:GPL
  description:Oracle VM VirtualBox Support Driver
  author: Oracle Corporation
  srcversion: 135FF31DCB56FAD62FFCD36
  depends:
  vermagic:   4.12.0-11-generic SMP mod_unload 
  signat: PKCS#7
  signer: 
  sig_key:
  sig_hashalgo:   md4
  parm:   force_async_tsc:force the asynchronous TSC mode (int)
  ```

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

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

[Kernel-packages] [Bug 1712802] Re: package linux-image-3.19.0-84-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  This was a distro provided on a magazine. A few years ago. I am trying to 
start using Linux but had to put this machine away for some time. Now I have 
come back to it to find this error. I have attempted to obtain updates and 
upgrades to no avail. I may try a different version of Linux if this does not 
work. Admittedly, it is an old portable computer but I did not like the idea of 
working equipment being sent for scrap or recycling.
  All the best. Ian

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-84-generic (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic i686
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 997 F pulseaudio
  Date: Thu Aug 24 12:35:12 2017
  DuplicateSignature: package:linux-image-3.19.0-84-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=4e3df44a-93e5-40f0-a2d5-e09806eb9d50
  InstallationDate: Installed on 2015-08-29 (725 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  IwConfig:
   irda0 no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard HP Compaq nc6000 (DP894A#ABU)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=23e721d5-1b3f-418c-bcab-e03f284d2e71 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-22ubuntu1.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-3.19.0-84-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2004
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68BDD Ver. F.0F
  dmi.board.name: 0890
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 8051 Version 1A.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68BDDVer.F.0F:bd07/23/2004:svnHewlett-Packard:pnHPCompaqnc6000(DP894A#ABU):pvrF.0F:rvnHewlett-Packard:rn0890:rvr8051Version1A.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nc6000 (DP894A#ABU)
  dmi.product.version: F.0F
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1712802] [NEW] package linux-image-3.19.0-84-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Ian Parker]

Public bug reported:

This was a distro provided on a magazine. A few years ago. I am trying to start 
using Linux but had to put this machine away for some time. Now I have come 
back to it to find this error. I have attempted to obtain updates and upgrades 
to no avail. I may try a different version of Linux if this does not work. 
Admittedly, it is an old portable computer but I did not like the idea of 
working equipment being sent for scrap or recycling.
All the best. Ian

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-84-generic (not installed)
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic i686
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ian 997 F pulseaudio
Date: Thu Aug 24 12:35:12 2017
DuplicateSignature: package:linux-image-3.19.0-84-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
ErrorMessage: subprocess new pre-installation script returned error exit status 
1
HibernationDevice: RESUME=UUID=4e3df44a-93e5-40f0-a2d5-e09806eb9d50
InstallationDate: Installed on 2015-08-29 (725 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
IwConfig:
 irda0 no wireless extensions.
 
 lono wireless extensions.
 
 eth0  no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard HP Compaq nc6000 (DP894A#ABU)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=23e721d5-1b3f-418c-bcab-e03f284d2e71 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-22ubuntu1.1
RfKill:
 
SourcePackage: linux
Title: package linux-image-3.19.0-84-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/23/2004
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68BDD Ver. F.0F
dmi.board.name: 0890
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 8051 Version 1A.19
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68BDDVer.F.0F:bd07/23/2004:svnHewlett-Packard:pnHPCompaqnc6000(DP894A#ABU):pvrF.0F:rvnHewlett-Packard:rn0890:rvr8051Version1A.19:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq nc6000 (DP894A#ABU)
dmi.product.version: F.0F
dmi.sys.vendor: Hewlett-Packard

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


** Tags: apport-package i386 vivid

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  This was a distro provided on a magazine. A few years ago. I am trying to 
start using Linux but had to put this machine away for some time. Now I have 
come back to it to find this error. I have attempted to obtain updates and 
upgrades to no avail. I may try a different version of Linux if this does not 
work. Admittedly, it is an old portable computer but I did not like the idea of 
working equipment being sent for scrap or recycling.
  All the best. Ian

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-84-generic (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic i686
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 997 F pulseaudio
  Date: Thu Aug 24 12:35:12 2017
  DuplicateSignature: package:linux-image-3.19.0-84-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=4e3df44a-93e5-40f0-a2d5-e09806eb9d50
  InstallationDate: Installed on 2015-08-29 (725 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  IwConfig:
   irda0 no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 

[Kernel-packages] [Bug 1712803] [NEW] spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

[Po-Hsu Lin]

Public bug reported:

kernel: 4.10.0-33.37~16.04.1

I think this issue was introduced by the old qemu version (similar issue
was spotted on Xenial before), will need to investigate this further.


qemu-system-ppc64 -machine pseries,accel=kvm -bios powerpc/boot_rom.bin 
-display none -serial stdio -kernel powerpc/spapr_hcall.elf -smp 1
FAIL: hypercall: h_set_sprg0: sprg0 = 0xcafebabedeadbeef
FAIL: hypercall: h_set_sprg0: sprg0 = 0x
FAIL: hypercall: h_set_sprg0: sprg0 = 0x41a588
FAIL: hypercall: h_page_init: h_zero_page
FAIL: hypercall: h_page_init: h_copy_page
FAIL: hypercall: h_page_init: h_copy_page+h_zero_page
FAIL: hypercall: h_page_init: h_zero_page unaligned dst
FAIL: hypercall: h_page_init: h_copy_page unaligned src
XFAIL: hypercall: h_random: h-call available

SUMMARY: 9 tests, 8 unexpected failures, 1 expected failures

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


** Tags: bot-stop-nagging

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

Title:
  spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe
  kernel

Status in linux package in Ubuntu:
  New

Bug description:
  kernel: 4.10.0-33.37~16.04.1

  I think this issue was introduced by the old qemu version (similar
  issue was spotted on Xenial before), will need to investigate this
  further.

  
  qemu-system-ppc64 -machine pseries,accel=kvm -bios powerpc/boot_rom.bin 
-display none -serial stdio -kernel powerpc/spapr_hcall.elf -smp 1
  FAIL: hypercall: h_set_sprg0: sprg0 = 0xcafebabedeadbeef
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x41a588
  FAIL: hypercall: h_page_init: h_zero_page
  FAIL: hypercall: h_page_init: h_copy_page
  FAIL: hypercall: h_page_init: h_copy_page+h_zero_page
  FAIL: hypercall: h_page_init: h_zero_page unaligned dst
  FAIL: hypercall: h_page_init: h_copy_page unaligned src
  XFAIL: hypercall: h_random: h-call available

  SUMMARY: 9 tests, 8 unexpected failures, 1 expected failures

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

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

[Kernel-packages] [Bug 1712481] Re: HID: multitouch: Support ALPS PTP Stick and Touchpad devices

[Kleber Sacilotto de Souza]

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

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

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

Title:
  HID: multitouch: Support ALPS PTP Stick and Touchpad devices

Status in HWE Next:
  In Progress
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:
  [Impact]
  Support to ALPS PTP Stick and Touchpad devices found on latest Dell Latitude 
systems.

  [Fix]
  This fix in two parts:
  1. Requires cherry-pick of patch submitted by ALPS in upstream kernel 4.13
  See: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.13-rc6=504c932c7c47a6b4c572302a13873f7d83af1ff3

  2. Additional sauce patch adds the device-id of the new PTP stick. This
  patch is already submitted to linux-input and is pending review.
  See: http://marc.info/?l=linux-input=150235885218076=2

  [Test Case]
  Verified on the systems affected with this issue and confirmed that this 
solution works.

  [Regression Potential]
  The patch adds new device ids to hid multi-touch driver. With strict 
conditional filtering based on these device-ids, regression potential is 
minimal.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load

[Yngvi Hrafn Pétursson]

Having same same issue on HP EliteDesk 705 G3 Desktop Mini (W4V44AV)
Broadcom Corporation NetXtreme BCM5762 Gigabit Ethernet PCIe (rev 10) and tg3 
module

Error is triggered after the link speed is set or negotiated to 100Mbps
Usually within 15sec of ping ower 100Mbps link
But but works ok with 1Gbps links.

Can be triggered by pluging to 100Mbps port, changin the switch port to 100Mbps 
or:
# ethtool -s eno1 speed 100 duplex full autoneg off

Netboot works until the tg3 module takes ower.
Windows works ok.
Tested:
- multiple cables, computers and switch vendors
- upgrading bios
- ethtool disable eee and hardware offload
- ubuntu 12.04 - 17.04
- new kernel linux-generic-hwe-16.04-edge Version: 4.11.0.14.22
- disable power management in bios
- disable power management with grup switches
- iommu=soft iommu=on iommu=off
- disable highdma

None of the workarounds that i found on Google worked for me.

modinfo tg3 | grep -v alias
filename:   
/lib/modules/4.4.0-92-generic/kernel/drivers/net/ethernet/broadcom/tg3.ko
firmware:   tigon/tg3_tso5.bin
firmware:   tigon/tg3_tso.bin
firmware:   tigon/tg3.bin
version:3.137
license:GPL
description:Broadcom Tigon3 ethernet driver
author: David S. Miller (da...@redhat.com) and Jeff Garzik 
(jgar...@pobox.com)
srcversion: 8C06FB0EBBF221DF79133B9
depends:ptp
intree: Y
vermagic:   4.4.0-92-generic SMP mod_unload modversions 
parm:   tg3_debug:Tigon3 bitmapped debugging message enable value (int)

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

Title:
  14e4:1687 broadcom tg3 network driver disconnects under high load

Status in linux package in Ubuntu:
  Triaged
Status in linux package in Debian:
  New

Bug description:
  The tg3 broadcom network driver that binds with chipset 5762 goes offline and 
unable to recover (even with tg3 watchdog timeout) when network transmit is 
under high load.  Call trace:
  https://launchpadlibrarian.net/204185480/dmesg

  When this happens, only a reboot would be able to fix it.  Sometimes,
  however, bringing the interface offline and online (via ifconfig)
  would recover networking.  I've also tested with the latest tg3 driver
  (dec 2014 version) and networking is still problematic.  I have also
  disabled TSO, GSO etc... with ethtool and the bug still surfaces.
  This bug may be related to the integrated Firmware.

  Here is the procedure to replicate the issue because it is hard to
  replicate it under moderate network load.

  1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a 
Ubuntu/Kubunu Live CD 14.04-15.04.
  2. from another machine: start 5 sessions, repetitively copy (scp with public 
key authentication) a 70 meg file back and forth to the tg3 machine in each 
session. (not sure if this is necessary)
  3. create a 1GB file on the tg3 machine, with something like dd 
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
  4. from another machine: repetitively scp copy that 1GB file from the tg3 
machine. This can be done with something like:

  while [ 0 ]; do
     scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
  done;

  Networking will mostly goes offline in about 10-30 minutes.

  WORKAROUND: Add udev rule to make the changes permanent in 
/etc/udev/rules.d/80-tg3-fix.rules :
  ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4", 
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kubuntu3748 F pulseaudio
   /dev/snd/controlC0:  kubuntu3748 F pulseaudio
  CasperVersion: 1.360
  Date: Thu Apr 23 11:16:24 2015
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
  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-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:

  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: 

[Kernel-packages] [Bug 1712024] Re: igb: Support using Broadcom 54616 as PHY

[Jesse Sung]

** Description changed:

  The igb driver fails to work when using Broadcom 54616 as PHY.
  
  00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  
  $ dmesg | grep igb
  [3.472655] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
  [3.480475] igb: Copyright (c) 2007-2014 Intel Corporation.
  [3.584768] igb: probe of :00:14.0 failed with error -2
  [3.965971] igb :00:14.1: added PHC on eth0
  [3.971066] igb :00:14.1: Intel(R) Gigabit Ethernet Network Connection
  [4.010706] igb :00:14.1: eth0: PBA No: 002000-000
  [4.016458] igb :00:14.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.399662] igb :00:14.2: added PHC on eth1
  [4.404738] igb :00:14.2: Intel(R) Gigabit Ethernet Network Connection
  [4.412489] igb :00:14.2: eth1: PBA No: 002000-000
  [4.418235] igb :00:14.2: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.428206] igb :00:14.1 enp0s20f1: renamed from eth0
  [4.465744] igb :00:14.2 enp0s20f2: renamed from eth1
  
  A patch can be found in OpenNetworkLinux:
  
https://github.com/opencomputeproject/OpenNetworkLinux/blob/master/packages/base/any/kernels/3.18.25/patches
  /driver-support-intel-igb-bcm54616-phy.patch
+ 
+ It should be safe to include this in an SRU release since the new code
+ is only functioning when certain ID is found.

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

Title:
  igb: Support using Broadcom 54616 as PHY

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

Bug description:
  The igb driver fails to work when using Broadcom 54616 as PHY.

  00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)

  $ dmesg | grep igb
  [3.472655] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
  [3.480475] igb: Copyright (c) 2007-2014 Intel Corporation.
  [3.584768] igb: probe of :00:14.0 failed with error -2
  [3.965971] igb :00:14.1: added PHC on eth0
  [3.971066] igb :00:14.1: Intel(R) Gigabit Ethernet Network Connection
  [4.010706] igb :00:14.1: eth0: PBA No: 002000-000
  [4.016458] igb :00:14.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.399662] igb :00:14.2: added PHC on eth1
  [4.404738] igb :00:14.2: Intel(R) Gigabit Ethernet Network Connection
  [4.412489] igb :00:14.2: eth1: PBA No: 002000-000
  [4.418235] igb :00:14.2: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.428206] igb :00:14.1 enp0s20f1: renamed from eth0
  [4.465744] igb :00:14.2 enp0s20f2: renamed from eth1

  A patch can be found in OpenNetworkLinux:
  
https://github.com/opencomputeproject/OpenNetworkLinux/blob/master/packages/base/any/kernels/3.18.25/patches
  /driver-support-intel-igb-bcm54616-phy.patch

  It should be safe to include this in an SRU release since the new code
  is only functioning when certain ID is found.

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

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

[Kernel-packages] [Bug 1712024] Re: igb: Support using Broadcom 54616 as PHY

[Kleber Sacilotto de Souza]

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

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

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

Title:
  igb: Support using Broadcom 54616 as PHY

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

Bug description:
  The igb driver fails to work when using Broadcom 54616 as PHY.

  00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)

  $ dmesg | grep igb
  [3.472655] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
  [3.480475] igb: Copyright (c) 2007-2014 Intel Corporation.
  [3.584768] igb: probe of :00:14.0 failed with error -2
  [3.965971] igb :00:14.1: added PHC on eth0
  [3.971066] igb :00:14.1: Intel(R) Gigabit Ethernet Network Connection
  [4.010706] igb :00:14.1: eth0: PBA No: 002000-000
  [4.016458] igb :00:14.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.399662] igb :00:14.2: added PHC on eth1
  [4.404738] igb :00:14.2: Intel(R) Gigabit Ethernet Network Connection
  [4.412489] igb :00:14.2: eth1: PBA No: 002000-000
  [4.418235] igb :00:14.2: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.428206] igb :00:14.1 enp0s20f1: renamed from eth0
  [4.465744] igb :00:14.2 enp0s20f2: renamed from eth1

  A patch can be found in OpenNetworkLinux:
  
https://github.com/opencomputeproject/OpenNetworkLinux/blob/master/packages/base/any/kernels/3.18.25/patches
  /driver-support-intel-igb-bcm54616-phy.patch

  It should be safe to include this in an SRU release since the new code
  is only functioning when certain ID is found.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Karl-Philipp Richter]

** Description changed:

- hallo
- i have a acer aspire v5 571g laptop with former windows. after i installed 
ubuntu the computer refuses to shut down, instead it does a restart.
- thanks
+ 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
+  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
+  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

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

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

[Kleber Sacilotto de Souza]

The fixes were applied to zesty/master-next branch and will be available
on the next kernel SRU cycle.

I removed the verification-done-zesty tag because it must be added only
after the fixes have been tested with a kernel that's at least in
-proposed. So the verification will need to be done again when the next
SRU kernel hits -proposed (a comment will be added when that happens).

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

Title:
  RPT related fixes missing in Ubuntu 16.04.3

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

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

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

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


  ---Problem Description---

  The following patches are missing in the ubuntu 16.04.3 kernel

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

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

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

  ---uname output---

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

  Machine Type = power9

  ---Steps to Reproduce---

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

  Upstream commits mentioned:

  commit  f7327e0ba3805470cced2acfa053e795362ee41d

  powerpc/mm/radix: Remove unnecessary ptesync

  commit  f6b0df55cad252fedd60aa2ba75a0207d0006283

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

  commit  a5998fcb92552a18713b6aa5c146aa400e4d75ee

  powerpc/mm/radix: Optimise tlbiel flush all case

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

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

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

[Kleber Sacilotto de Souza]

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

** Tags removed: 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/1709220

Title:
  RPT related fixes missing in Ubuntu 16.04.3

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

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

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

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


  ---Problem Description---

  The following patches are missing in the ubuntu 16.04.3 kernel

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

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

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

  ---uname output---

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

  Machine Type = power9

  ---Steps to Reproduce---

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

  Upstream commits mentioned:

  commit  f7327e0ba3805470cced2acfa053e795362ee41d

  powerpc/mm/radix: Remove unnecessary ptesync

  commit  f6b0df55cad252fedd60aa2ba75a0207d0006283

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

  commit  a5998fcb92552a18713b6aa5c146aa400e4d75ee

  powerpc/mm/radix: Optimise tlbiel flush all case

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

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

[Kernel-packages] [Bug 1711096] Re: dma-buf: performance issue when looking up the fence status

[Kleber Sacilotto de Souza]

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

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

Title:
  dma-buf: performance issue when looking up the fence status

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

Bug description:
  SRU Request:

  [Impact]
  When a timeout of zero is specified, the caller is only interested in
  the fence status.

  In the current implementation, dma_fence_default_wait will always call
  schedule_timeout() at least once for an unsignaled fence. This adds a
  significant overhead to a fence status query.

  Avoid this overhead by returning early if a zero timeout is specified.

  [Test Case]
  1) Install the new kernel

  2) Download amdgpu-pro-17.30-465504.tar.xz from http://support.amd.com
  /en-us/kb-articles/Pages/AMDGPU-PRO-Driver-for-Linux-Release-
  Notes.aspx, and follow the install guide to install the driver on
  Ubuntu 16.04.3

  3) Install Unigine Heaven to get performance score

  4) Rmeove DKMS, remove this patch
  
http://git.amd.com:8080/gitweb?p=brahma/ec/linux.git;a=commit;h=8586edda6677b90f3971919f3c6babbbec4b5b8c
  from DKMS source code, and install DKMS

  5) re-run the benchmark, and check if there's any obvious performance
  drop.

  [Regression Potential]
  Low, the patch is very small, and it is already available upstream.

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

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

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

[Kernel-packages] [Bug 1711098] Re: AMD RV platforms with SNPS 3.1 USB controller stop responding (S3 issue)

[Kleber Sacilotto de Souza]

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

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

Title:
  AMD RV platforms with SNPS 3.1 USB controller stop responding (S3
  issue)

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

Bug description:
  SRU Request:

  [Impact]
  AMD RV platforms with SNPS 3.1 USB controllers will stop responding because 
of an RTL bug.

  This workaround fixes S3 on RV platform with a USB keyboard

  [Test Case]
  1) Install the new kernel

  2) Run pm-suspend

  3) Press any key to wake up the system

  [Regression Potential]
  Low, the patch is very small, and it is already available upstream.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/usb/host
  /xhci-hub.c?h=v4.13-rc2=28a2369f7d72ece55089f33e7d7b9c1223673cc3

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

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

[Kernel-packages] [Bug 344878] Re: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry)

[iGadget]

Thanks mhalcrow for your elaborate reply. While appreciated, IMHO you
don't need to apologize. It's not your fault we as end-users weren't
notified of this limitation during installation.

For a lot of us, the situation looks pretty sad. There's eCryptfs which
has the file name limitation and there's full disk encryption which is
(AFAIK) only available on the alternate installer. And last time I
heard, full disk encryption poses problems when Windows is installed on
the same disk, leaving eCryptfs as the only option to many of us. So
kudos for trying to fix this!

About your proposed solution - as an Ubuntu 16.04.2 user with
(currently) 4.10 kernel, does this mean I could use ext4 encryption
without too much risks or would I still be in "early adopter" territory?

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

Title:
  file name too long when creating new file (ecryptfs_lookup:
  lookup_one_len() returned [-36] on lower_dentry)

Status in eCryptfs:
  Fix Released
Status in ecryptfs-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in ecryptfs-utils source package in Natty:
  Won't Fix
Status in linux source package in Natty:
  Won't Fix
Status in ecryptfs-utils source package in Oneiric:
  Won't Fix
Status in linux source package in Oneiric:
  Won't Fix
Status in ecryptfs-utils source package in Precise:
  Invalid
Status in linux source package in Precise:
  Fix Released

Bug description:
  ===
  IMPORTANT: eCryptfs can only store filenames of up to 143 characters when 
filename encryption is enabled. The remaining 112 characters are used for 
storing metadata such as the encrypted filename prefix, the signature of the 
filename encryption key, and an identifier for the cipher used, as well as 
random bytes to make /foo/file and /bar/file encrypt to different ciphertext 
and padding bytes to achieve proper cipher block size alignment.

  This bug is considered 'fixed' by the upstream maintainers. The
  eCryptfs kernel error message has been reduced to a debug level log
  message and eCryptfs now correctly reports its maximum supported
  filename length through the statfs() syscall. This is all that can be
  done without implementing a completely new encrypted filename design.
  A design that allows 255 character filenames without introducing other
  design limitations has not been identified and no one is currently
  working to come up with such a design.

  Please do not add comments or create new bugs saying that mv reports
  'File name too long' or that you can't create a long filename in your
  eCryptfs mounts. It is an unfortunate design limitation that cannot be
  avoided at this time.

  Please do create new bugs when an application generates filenames that are 
too long to be stored in an eCryptfs mount. The application may be able to use 
the statfs() syscall to check the filename length limits of eCryptfs. Note that 
this does not include something like a torrent or ftp client trying to download 
a file with a long filename. The application is not generating the filename in 
those cases, it is just downloading the file that the user told it to download.
  ===

  When trying to create a new file with a relatively long filename (f. ex. 
dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt)
  I get an error: file name to long, when in fact the file name is not to long, 
but the encrypted name created for this file is to long, so, the file was not 
created.

  this is no problem when I try to create a file, but when I'm copying a
  lot of files to my home folder I get some: filename to long error's
  and it's hard to fix (first locate the file, create shorter name, move
  again)

  so, maybe you could create a check for to long filenames?

  I'm using ext4 here...

  mv 
dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt
 /home/jens/
  mv: cannot stat 
`/home/jens/dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt':
 File name too long

  libecryptfs0:
    Installed: 71-0ubuntu2
    Candidate: 71-0ubuntu2
    Version table:
   *** 71-0ubuntu2 0
  500 http://be.archive.ubuntu.com jaunty/main Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1712746] Re: mwifiex causes kernel oops when AP mode is enabled

[Jesse Sung]

** Description changed:

  When it's in AP mode, there's quite a chance to find kernel oops during
  reboot.
  
+ This is caused by the wiphy may be NULL for some reason. It's likely a
+ bug in mwifiex. We've already pinged Marvell and Murata. Before there's
+ a real fix available, we should check wiphy before accessing it.
+ 
+ I've tried a 4.13-rc6 kernel. Though it has oops for NULL pointer
+ deference too, it happens in a different function in mwifiex. Thus the
+ workaround for Xenial may or may not help for other series. Will need to
+ reproduce this issue with Zesty and then we can decide whether this
+ workaround should be applied to Zesty.
+ 
  [   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
  [   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
- [   30.716494] PGD 0 
- [   30.718575] Oops:  [#1] SMP 
+ [   30.716494] PGD 0
+ [   30.718575] Oops:  [#1] SMP
  [   30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni
  [   30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [   30.845018] Hardware name: Dell Inc. Edge Gateway 5000/  , BIOS 
01.05.00 10/18/2016
  [   30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex]
  [   30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 
880075e48000
  [   30.868018] RIP: 0010:[]  [] 
mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.877484] RSP: 0018:880075e4bbf8  EFLAGS: 00010202
  [   30.882920] RAX:  RBX: 0004 RCX: 
0004
  [   30.890221] RDX: 001000110010 RSI: 0004 RDI: 
0004
  [   30.897520] RBP: 880075e4bc28 R08: 0003 R09: 
0001
  [   30.904821] R10: 0001 R11: 02ff R12: 
0095
  [   30.912123] R13:  R14: 880075e4 R15: 
0095
  [   30.919425] FS:  () GS:88007130() 
knlGS:
  [   30.927701] CS:  0010 DS:  ES:  CR0: 8005003b
  [   30.933581] CR2: 00f0 CR3: 01e0a000 CR4: 
001006e0
  [   30.940882] Stack:
  [   30.942944]  0118 880075e4 8800750c4000 
880075e3ed59
  [   30.950592]  0095 880075e3ee01 880075e4bcd0 
c05846fc
  [   30.958232]   880075e4bc50 8140bcb5 
880075e4bc70
  [   30.965873] Call Trace:
  [   30.968397]  [] 
mwifiex_parse_single_response_buf+0x1fc/0x560 [mwifiex]
  [   30.976772]  [] ? find_next_bit+0x15/0x20
  [   30.982490]  [] 
mwifiex_handle_event_ext_scan_report+0x15c/0x340 [mwifiex]
  [   30.991139]  [] mwifiex_process_sta_event+0x276/0xb40 
[mwifiex]
  [   30.998806]  [] mwifiex_process_event+0x102/0x1c0 
[mwifiex]
  [   31.006120]  [] mwifiex_main_process+0x5de/0x8d0 
[mwifiex]
  [   31.013346]  [] mwifiex_main_work_queue+0x1f/0x30 
[mwifiex]
  [   31.020650]  [] process_one_work+0x165/0x480
  [   31.026624]  [] worker_thread+0x4b/0x4c0
  [   31.032240]  [] ? process_one_work+0x480/0x480
  [   31.038387]  [] kthread+0xd8/0xf0
  [   31.043384]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.050071]  [] ret_from_fork+0x3f/0x70
  [   31.055596]  [] ? kthread_create_on_node+0x1e0/0x1e0
- [   31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 
df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00 
+ [   31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 
df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00
  [   31.082756] RIP  [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   31.089820]  RSP 
  [   31.093392] CR2: 00f0
  [   31.096787] ---[ end trace f3a762be5787f138 ]---

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

Title:
  mwifiex causes kernel oops when AP mode is enabled

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New

Bug description:
  When it's in AP mode, there's quite a chance to find kernel oops
  during reboot.

  This is caused by the wiphy may be NULL for some reason. It's likely a
  bug in mwifiex. We've already pinged Marvell and Murata. Before
  there's a real fix available, we should check wiphy before accessing
  it.

  I've tried a 4.13-rc6 kernel. Though it has oops for NULL pointer
  deference too, it happens in a different function in mwifiex. Thus the
  workaround for Xenial may or may not help for other series. Will need
  to reproduce this issue with Zesty and then we can decide whether this
  workaround should be applied to Zesty.

  [   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
  [   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  reboot instead of shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  hallo
  i have a acer aspire v5 571g laptop with former windows. after i installed 
ubuntu the computer refuses to shut down, instead it does a restart.
  thanks

  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 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

[Stuart Page]

Just wanting to report that I am also experiencing this issue with a
freshly installed Ubuntu Server 16.04.3 with 4.10 kernel on the 22nd
August 2017. All the updates applied and running as a KVM host with
hardware:

Ryzen 1700 (non-x)
Motherboard: Asus prime B350-Plus
Bios: -  Version 0805
 - Disabled SMT
 - Disabled c-states




** Attachment added: "image of issues showing in console"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085/+attachment/4937902/+files/IMG_20170824_092441948x.png

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   

[Kernel-packages] [Bug 1712481] Re: HID: multitouch: Support ALPS PTP Stick and Touchpad devices

[Stefan Bader]

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

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

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

Title:
  HID: multitouch: Support ALPS PTP Stick and Touchpad devices

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New

Bug description:
  [Impact]
  Support to ALPS PTP Stick and Touchpad devices found on latest Dell Latitude 
systems.

  [Fix]
  This fix in two parts:
  1. Requires cherry-pick of patch submitted by ALPS in upstream kernel 4.13
  See: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.13-rc6=504c932c7c47a6b4c572302a13873f7d83af1ff3

  2. Additional sauce patch adds the device-id of the new PTP stick. This
  patch is already submitted to linux-input and is pending review.
  See: http://marc.info/?l=linux-input=150235885218076=2

  [Test Case]
  Verified on the systems affected with this issue and confirmed that this 
solution works.

  [Regression Potential]
  The patch adds new device ids to hid multi-touch driver. With strict 
conditional filtering based on these device-ids, regression potential is 
minimal.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1709171] Re: Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE

[Kleber Sacilotto de Souza]

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

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

Title:
  Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE

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

Bug description:
  == SRU Justification ==
  IBM is requesting that we disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE in 
  the current ppc64el kernels up to 16.04.3.

  This was requested originally in LP#1706380, but it was not integrated
  in that bug.

  This chanage has already been made in Artful(Commit 8f189e08c9a), so that 
  is where I cherry picked the patch from.

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

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

[Kernel-packages] [Bug 1712724] Re: s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c

[Stefan Bader]

The BUG statement which triggers here seems to be introduced by

commit 723cacb
Author: Gerald Schaefer 
Date:   Fri Apr 15 16:38:40 2016 +0200

s390/mm: fix asce_bits handling with dynamic pagetable levels

and will be modified by

commit 1aea9b3
Author: Martin Schwidefsky 
Date:   Mon Apr 24 18:19:10 2017 +0200

s390/mm: implement 5 level pages tables

Maybe this only happens in certain cases which we do not always hit or
4.12 contains something which starts to use the upgrade incorrectly.
Otherwise we should have observed something like this since Yakkety
(4.8).

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

Title:
  s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [  543.516708] kernel BUG at 
/build/linux-a7axPg/linux-4.12.0/arch/s390/mm/pgalloc.c:84!
  [  543.516783] illegal operation: 0001 ilc:1 [#1] SMP 
  [  543.516785] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp bridge stp llc iptable_filter 
openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) 
zavl(PO) zcommon(PO) znvpair(PO) spl(O) vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp 
auth_rpcgss nfs_acl lockd grace libiscsi_tcp libiscsi sunrpc 
scsi_transport_iscsi ip_tables x_tables btrfs zlib_deflate raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 linear ghash_s390 prng aes_s390 des_s390 des_generic 
sha512_s390 sha256_s390 virtio_net sha1_s390 sha_common virtio_blk virtio_scsi
  [  543.516828] CPU: 0 PID: 10024 Comm: task-size-overr Tainted: P   O 
   4.12.0-12-generic #13-Ubuntu
  [  543.516829] Hardware name: IBM 2964 N63 400 (KVM/Linux)
  [  543.516830] task: 0cdb9e00 task.stack: 099e8000
  [  543.516831] Krnl PSW : 0704d0018000 001274ec 
(crst_table_upgrade+0x124/0x130)
  [  543.516841]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 
RI:0 EA:3
  [  543.516842] Krnl GPRS: 0001 0400 243d7800 
0020
  [  543.516843]1000  0032 

  [  543.516844]8000 0020  
1000
  [  543.516845]0020 243d7800 001239f6 
099ebbe0
  [  543.516853] Krnl Code: 001274de: c0e5002446c1  brasl   
%r14,5b0260
  [  543.516853]001274e4: a7f4ffb8  brc 
15,127454
  [  543.516853]   #001274e8: a7f40001  brc 
15,1274ea
  [  543.516853]   >001274ec: a728fff4  lhi %r2,-12
  [  543.516853]001274f0: a7f4ffee  brc 
15,1274cc
  [  543.516853]001274f4: 0707  bcr 0,%r7
  [  543.516853]001274f6: 0707  bcr 0,%r7
  [  543.516853]001274f8: c004  brcl0,1274f8
  [  543.516862] Call Trace:
  [  543.516864] ([<085d8578>] 0x85d8578)
  [  543.516868]  [<002f529a>] get_unmapped_area+0x72/0x120 
  [  543.516870]  [<002f931a>] do_mmap+0xfa/0x3e0 
  [  543.516873]  [<002d6292>] vm_mmap_pgoff+0xca/0x120 
  [  543.516874]  [<002f6962>] SyS_mmap_pgoff+0x10a/0x2a0 
  [  543.516875]  [<002f6b72>] SyS_old_mmap+0x7a/0xa8 
  [  543.516880]  [<00864c1c>] system_call+0xc4/0x27c 
  [  543.516881] Last Breaking-Event-Address:
  [  543.516882]  [<001274e8>] crst_table_upgrade+0x120/0x130
  [  543.516883]  
  [  543.516883] ---[ end trace 036f94bf79a83905 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-12-generic 4.12.0-12.13
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic s390x
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Thu Aug 24 05:01:08 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   

[Kernel-packages] [Bug 1712765] [NEW] reboot instead of shutdown

[Felix]

Public bug reported:

hallo
i have a acer aspire v5 571g laptop with former windows. after i installed 
ubuntu the computer refuses to shut down, instead it does a restart.
thanks

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

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


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

Title:
  reboot instead of shutdown

Status in linux package in Ubuntu:
  New

Bug description:
  hallo
  i have a acer aspire v5 571g laptop with former windows. after i installed 
ubuntu the computer refuses to shut down, instead it does a restart.
  thanks

  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 1711401] Re: accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

[Kleber Sacilotto de Souza]

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

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

Title:
  accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

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

Bug description:
  [SRU REQUEST][XENIAL]

  When running stress-ng --dev stressor accessing /dev/hvc1 causes the
  stressor to lock up and never terminal.

  [FIX]
  Upstream commmit:From bbc3dfe8805de86874b1a1b1429a002e8670043e Mon Sep 17 
00:00:00 2001
  From: Sam Mendoza-Jonas 
  Date: Mon, 11 Jul 2016 13:38:57 +1000
  Subject: [PATCH] tty/hvc: Use IRQF_SHARED for OPAL hvc consoles

  [TESTING]
  Without the fix, stress-ng --dev run as root hangs, and one gets an irq 
failed error and an oops:

  [ 2096.476610] hvc_open: request_irq failed with rc -16.
  [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
  [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
  [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV

  With the fix, the stressor runs w/o any issues

  [REGRESSION POTENTIAL]
  This is specific to one driver for ppc64el, so the risk potential is limited. 
The fix has limited regression potential as it essentially marks a flag to 
allow interrupt to be shared and fundamentally this is a very minor change to  
the interrupt handling functionality in the driver.

  ---

  stress-ng run as root, --dev stressor, accessing /dev/hvc1:

  [ 2096.476610] hvc_open: request_irq failed with rc -16.
  [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
  [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
  [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV
  [ 2096.476657] Modules linked in: kvm_hv kvm_pr kvm cuse userio hci_vhci 
bluetooth uhid hid vhost_net vhost macvtap macvlan snd_seq snd_seq_device 
snd_timer snd soundcore ipmi_powernv ipmi_msghandler vmx_crypto leds_powernv 
uio_pdrv_genirq uio powernv_rng ibmpowernv 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 dm_round_robin ses 
enclosure ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath
  [ 2096.476718] CPU: 74 PID: 23074 Comm: stress-ng-dev Not tainted 
4.4.0-92-generic #115-Ubuntu
  [ 2096.476724] task: c00fe8499030 ti: c00f0fa0c000 task.ti: 
c00f0fa0c000
  [ 2096.476728] NIP: c0b0d8a4 LR: c069648c CTR: 
c0696450
  [ 2096.476732] REGS: c00f0fa0f6b0 TRAP: 0300   Not tainted  
(4.4.0-92-generic)
  [ 2096.476736] MSR: 90009033   CR: 2248  
XER: 
  [ 2096.476749] CFAR: c0008468 DAR: 00a8 DSISR: 4000 
SOFTE: 0
     GPR00: c069648c c00f0fa0f930 c15f8000 
00a8
     GPR04: c00ff0082400 0002 001ffe7d 
0036
     GPR08: c3236b90  804a 
c01e4e568880
     GPR12: c0696450 cfb6bf00 000f 
010023d22660
     GPR16: 3fff9ca5 0080 c01e43dde100 
c00fe459c800
     GPR20:  0001 0e51 
00010004
     GPR24: 00010800  f000 
c1892448
     GPR28: c00fef98da28 c00fe459c800 0001 
00a8
  [ 2096.476805] NIP [c0b0d8a4] _raw_spin_lock_irqsave+0x44/0x130
  [ 2096.476812] LR [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476815] Call Trace:
  [ 2096.476818] [c00f0fa0f930] [c00f0fa0f970] 0xc00f0fa0f970 
(unreliable)
  [ 2096.476824] [c00f0fa0f970] [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476829] [c00f0fa0f9f0] [c066c514] tty_open+0x194/0x7c0
  [ 2096.476836] [c00f0fa0fa90] [c02ec234] chrdev_open+0x114/0x270
  [ 2096.476841] [c00f0fa0faf0] [c02e1480] 
do_dentry_open+0x2c0/0x460
  [ 2096.476846] [c00f0fa0fb50] [c02f9aa8] do_last+0x178/0xff0
  [ 2096.476851] [c00f0fa0fc10] [c02fab3c] path_openat+0xcc/0x3c0
  [ 2096.476857] [c00f0fa0fc90] [c02fca5c] do_filp_open+0xfc/0x170
  [ 2096.476861] [c00f0fa0fdb0] [c02e3270] do_sys_open+0x1c0/0x3b0
  [ 2096.476867] [c00f0fa0fe30] [c0009204] system_call+0x38/0xb4
  [ 2096.476870] Instruction dump:
  [ 2096.476873] fbe1fff8 f8010010 f821ffc1 7c7f1b78 6000 

[Kernel-packages] [Bug 1710868] Re: memory-hotplug test needs to be fixed

[Kleber Sacilotto de Souza]

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

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

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

Title:
  memory-hotplug test needs to be fixed

Status in linux package in Ubuntu:
  In Progress
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:
  SRU Justification:

  Impact: 
  The memory-hotplug test in the kernel tree 
(tools/testing/selftests/memory-hotplug/) needs to be fixed:
  1. The test will pass even the memory blocks are failed to be offlined [1].
  2. It's using a random number generator to decide if each memory block needs 
to be offlined, which is not ideal for testing as the block it tries to unplug 
might be different between two runs.
  3. The "-r" flag, percent-of-memory-to-offline, does not match what is says. 
It's being used as the percentage to get a memory block offlined instead.

  Fix: 
  Apply the following patch from upstream can fix these issues:
  593f9278 - selftests: typo correction for memory-hotplug test
  a34b28c9 - selftests: check hot-pluggagble memory for memory-hotplug test
  72441ea5 - selftests: check percentage range for memory-hotplug test
  02d8f075 - selftests: add missing test name in memory-hotplug test
  5ff0c60b - selftests: fix memory-hotplug test

  Testcase:
  Run the script directly, it will fail when all memory blocks are busy. And it 
will try to unplug memory blocks in a fixed order.

  Regression Potential:
  Negligible, it's just affecting this specific test case among those testing 
tools.

  [1] https://paste.ubuntu.com/25318445/

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

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

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

[udippel]

For comparison, here is the dmesg of a functional machine, same type,
lenovo T410s, same software, same BIOS; but with deactivated NVIDIA
graphics (type 2924)

** Attachment added: "dmesg_good"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712508/+attachment/4937882/+files/dmesg_good

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

Title:
  Disappearing screen and flickering after upgrade to 16.04

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1686019] Re: Ubuntu 16.04.3: Qemu fails on P9

[Kleber Sacilotto de Souza]

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

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

Title:
  Ubuntu 16.04.3: Qemu fails on P9

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

Bug description:
  Trying to start KVM on Ubuntu 16.04.3 with QEMU from dgibson 2.10
  tree[1], I see the following error when trying to boot a 17.04 image.

  8000 DISK : "QEMU QEMU HARDDISK2.5+"
  Populating /pci@8002000
  No NVRAM common partition, re-initializing...
  Scanning USB 
  Using default console: /vdevice/vty@7100
   ted RAM kernel at 40 (17995b0 bytes) C08FF
Welcome to Open Firmware

Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
This program and the accompanying materials are made available
under the terms of the BSD License available at
http://www.opensource.org/licenses/bsd-license.php

  Booting from memory...
  OF stdout device is: /vdevice/vty@7100
  Preparing to boot Linux version 4.10.0-19-generic (buildd@bos01-ppc64el-009) 
(gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) ) #21-Ubuntu SMP Thu Apr 6 
17:03:05 UTC 2017 (Ubuntu 4.10.0-19.21-generic 4.10.8)
  Detected machine type: 0101
  command line: debug initcall_debug udbg-immortal console=/dev/hvc0
  Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 01bb
alloc_top: 1000
alloc_top_hi : 8000
rmo_top  : 1000
ram_top  : 8000
  instantiating rtas at 0x0daf... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x041c -> 0x041c09fd
  Device tree struct  0x041d -> 0x041e
  Quiescing Open Firmware ...
  Booting Linux via __start() @ 0x0040 ...

  
  I tried to add some debug options as "debug initcall_debug udbg-immortal 
console=/dev/hvc0" but no luck. 

  [1] https://github.com/dgibson/qemu.git branch ppc-for-2.10
   
  ---uname output---
  4.10.0-19

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

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

[Kernel-packages] [Bug 1698470] Re: [Zesty][Yakkety] rtl8192e bug fixes

[cheltspy]

Ping

Any movement on Zesty and now that 4.10 is being used on 16.04LTS.

Its appears other users have problems.

https://askubuntu.com/questions/948811/how-to-fix-unstable-wifi-
connection-on-ubuntu-17-04-amd64

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

Title:
  [Zesty][Yakkety] rtl8192e bug fixes

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Triaged

Bug description:
  The following commits needed to be added to 4.10 and 4.8 kernels for
  stable operation of r8192e_pci driver. They are already in 4.11 and in
  4.4.

  commit baabd567f87be05330faa5140f72a91960e7405a upstream
  staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.

  commit 867510bde14e7b7fc6dd0f50b48f6753cfbd227a upstream.
  staging: rtl8192e: fix 2 byte alignment of register BSSIDR.

  commit 90be652c9f157d44b9c2803f902a8839796c090d upstream.
  staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of EPROM_CMD.

  commit 95d93e271d920dfda369d4740b1cc1061d41fe7f upstream.
  staging: rtl8192e: GetTs Fix invalid TID 7 warning.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  canaries-64   2006 F pulseaudio
   /dev/snd/controlC0:  canaries-64   2006 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Jun 16 23:11:13 2017
  HibernationDevice: RESUME=UUID=f23ec6f5-7e6a-4559-a7f1-af640124e970
  InstallationDate: Installed on 2015-10-31 (594 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=48898cca-fae3-4cdc-9785-fc0b97f4cbd9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: rtllib r8192e_pci
  UpgradeStatus: Upgraded to zesty on 2016-10-23 (236 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: N3700-ITX
  dmi.board.vendor: ASRock
  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.:bvrP1.70:bd04/18/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1712746] Re: mwifiex causes kernel oops when AP mode is enabled

[Stefan Bader]

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

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

Title:
  mwifiex causes kernel oops when AP mode is enabled

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New

Bug description:
  When it's in AP mode, there's quite a chance to find kernel oops
  during reboot.

  [   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
  [   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.716494] PGD 0 
  [   30.718575] Oops:  [#1] SMP 
  [   30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni
  [   30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [   30.845018] Hardware name: Dell Inc. Edge Gateway 5000/  , BIOS 
01.05.00 10/18/2016
  [   30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex]
  [   30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 
880075e48000
  [   30.868018] RIP: 0010:[]  [] 
mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.877484] RSP: 0018:880075e4bbf8  EFLAGS: 00010202
  [   30.882920] RAX:  RBX: 0004 RCX: 
0004
  [   30.890221] RDX: 001000110010 RSI: 0004 RDI: 
0004
  [   30.897520] RBP: 880075e4bc28 R08: 0003 R09: 
0001
  [   30.904821] R10: 0001 R11: 02ff R12: 
0095
  [   30.912123] R13:  R14: 880075e4 R15: 
0095
  [   30.919425] FS:  () GS:88007130() 
knlGS:
  [   30.927701] CS:  0010 DS:  ES:  CR0: 8005003b
  [   30.933581] CR2: 00f0 CR3: 01e0a000 CR4: 
001006e0
  [   30.940882] Stack:
  [   30.942944]  0118 880075e4 8800750c4000 
880075e3ed59
  [   30.950592]  0095 880075e3ee01 880075e4bcd0 
c05846fc
  [   30.958232]   880075e4bc50 8140bcb5 
880075e4bc70
  [   30.965873] Call Trace:
  [   30.968397]  [] 
mwifiex_parse_single_response_buf+0x1fc/0x560 [mwifiex]
  [   30.976772]  [] ? find_next_bit+0x15/0x20
  [   30.982490]  [] 
mwifiex_handle_event_ext_scan_report+0x15c/0x340 [mwifiex]
  [   30.991139]  [] mwifiex_process_sta_event+0x276/0xb40 
[mwifiex]
  [   30.998806]  [] mwifiex_process_event+0x102/0x1c0 
[mwifiex]
  [   31.006120]  [] mwifiex_main_process+0x5de/0x8d0 
[mwifiex]
  [   31.013346]  [] mwifiex_main_work_queue+0x1f/0x30 
[mwifiex]
  [   31.020650]  [] process_one_work+0x165/0x480
  [   31.026624]  [] worker_thread+0x4b/0x4c0
  [   31.032240]  [] ? process_one_work+0x480/0x480
  [   31.038387]  [] kthread+0xd8/0xf0
  [   31.043384]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.050071]  [] ret_from_fork+0x3f/0x70
  [   31.055596]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 
df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00 
  [   31.082756] RIP  [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   31.089820]  RSP 
  [   31.093392] CR2: 00f0
  [   31.096787] ---[ end trace f3a762be5787f138 ]---

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

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

[Kernel-packages] [Bug 1709123] Re: [SRU][Zesty] [QDF2400] pl011 E44 erratum patch needed for 2.0 firmware and 1.1 silicon

[Kleber Sacilotto de Souza]

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

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

Title:
  [SRU][Zesty] [QDF2400] pl011 E44 erratum patch needed for 2.0 firmware
  and 1.1 silicon

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

Bug description:
  [Impact]
  Another bug was found in the pl011/spcr code that implements the work-around 
for erratum E44. This erratum affects QDF2400 v1.1 silicon. The software bug is 
only exposed when using Firmware 2.0 or later (estimated release October 2017).

  To ensure compatibility with future firmware, the Ubuntu kernel should
  apply the aforementioned patch. Without this patch, customers using
  the 2.0 firmware and 1.1 silicon might not have a functional UART
  console, either sometimes or always.

  It is expected that this problem does not occur with 2.0 or later
  silicon.

  [Test Case]
  Upgrade firmware to v2.0 on a QDF2400 server with 1.1 silicon, and the kernel 
should fail to boot, with the patch applied, we should see no boot failure.

  [Fix]
  Following patch in linux-next fixes this issue:
  37ef38f3f838 tty: pl011: fix initialization order of QDF2400 E44

  [Regression Potential]
  This is a bug fix to tty driver and limited to qdf2400. Low risk.

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

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

[Kernel-packages] [Bug 1712746] Re: mwifiex causes kernel oops when AP mode is enabled

[Jesse Sung]

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

** Changed in: hwe-next
   Status: New => In Progress

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

Title:
  mwifiex causes kernel oops when AP mode is enabled

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  When it's in AP mode, there's quite a chance to find kernel oops
  during reboot.

  [   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
  [   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.716494] PGD 0 
  [   30.718575] Oops:  [#1] SMP 
  [   30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni
  [   30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [   30.845018] Hardware name: Dell Inc. Edge Gateway 5000/  , BIOS 
01.05.00 10/18/2016
  [   30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex]
  [   30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 
880075e48000
  [   30.868018] RIP: 0010:[]  [] 
mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.877484] RSP: 0018:880075e4bbf8  EFLAGS: 00010202
  [   30.882920] RAX:  RBX: 0004 RCX: 
0004
  [   30.890221] RDX: 001000110010 RSI: 0004 RDI: 
0004
  [   30.897520] RBP: 880075e4bc28 R08: 0003 R09: 
0001
  [   30.904821] R10: 0001 R11: 02ff R12: 
0095
  [   30.912123] R13:  R14: 880075e4 R15: 
0095
  [   30.919425] FS:  () GS:88007130() 
knlGS:
  [   30.927701] CS:  0010 DS:  ES:  CR0: 8005003b
  [   30.933581] CR2: 00f0 CR3: 01e0a000 CR4: 
001006e0
  [   30.940882] Stack:
  [   30.942944]  0118 880075e4 8800750c4000 
880075e3ed59
  [   30.950592]  0095 880075e3ee01 880075e4bcd0 
c05846fc
  [   30.958232]   880075e4bc50 8140bcb5 
880075e4bc70
  [   30.965873] Call Trace:
  [   30.968397]  [] 
mwifiex_parse_single_response_buf+0x1fc/0x560 [mwifiex]
  [   30.976772]  [] ? find_next_bit+0x15/0x20
  [   30.982490]  [] 
mwifiex_handle_event_ext_scan_report+0x15c/0x340 [mwifiex]
  [   30.991139]  [] mwifiex_process_sta_event+0x276/0xb40 
[mwifiex]
  [   30.998806]  [] mwifiex_process_event+0x102/0x1c0 
[mwifiex]
  [   31.006120]  [] mwifiex_main_process+0x5de/0x8d0 
[mwifiex]
  [   31.013346]  [] mwifiex_main_work_queue+0x1f/0x30 
[mwifiex]
  [   31.020650]  [] process_one_work+0x165/0x480
  [   31.026624]  [] worker_thread+0x4b/0x4c0
  [   31.032240]  [] ? process_one_work+0x480/0x480
  [   31.038387]  [] kthread+0xd8/0xf0
  [   31.043384]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.050071]  [] ret_from_fork+0x3f/0x70
  [   31.055596]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 
df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00 
  [   31.082756] RIP  [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   31.089820]  RSP 
  [   31.093392] CR2: 00f0
  [   31.096787] ---[ end trace f3a762be5787f138 ]---

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

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

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

[Ionut Lenghel]

I have tested the kernel provided in the link above. The daemons do not
stop when the integration services are disabled.

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

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

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

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

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

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

  Repro rate: 100%

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

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

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

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

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

[Kernel-packages] [Bug 1712746] [NEW] mwifiex causes kernel oops when AP mode is enabled

[Jesse Sung]

Public bug reported:

When it's in AP mode, there's quite a chance to find kernel oops during
reboot.

[   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
[   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
[   30.716494] PGD 0 
[   30.718575] Oops:  [#1] SMP 
[   30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni
[   30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 4.4.0-57-generic 
#78-Ubuntu
[   30.845018] Hardware name: Dell Inc. Edge Gateway 5000/  , BIOS 01.05.00 
10/18/2016
[   30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex]
[   30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 
880075e48000
[   30.868018] RIP: 0010:[]  [] 
mwifiex_get_cfp+0x49/0x150 [mwifiex]
[   30.877484] RSP: 0018:880075e4bbf8  EFLAGS: 00010202
[   30.882920] RAX:  RBX: 0004 RCX: 0004
[   30.890221] RDX: 001000110010 RSI: 0004 RDI: 0004
[   30.897520] RBP: 880075e4bc28 R08: 0003 R09: 0001
[   30.904821] R10: 0001 R11: 02ff R12: 0095
[   30.912123] R13:  R14: 880075e4 R15: 0095
[   30.919425] FS:  () GS:88007130() 
knlGS:
[   30.927701] CS:  0010 DS:  ES:  CR0: 8005003b
[   30.933581] CR2: 00f0 CR3: 01e0a000 CR4: 001006e0
[   30.940882] Stack:
[   30.942944]  0118 880075e4 8800750c4000 
880075e3ed59
[   30.950592]  0095 880075e3ee01 880075e4bcd0 
c05846fc
[   30.958232]   880075e4bc50 8140bcb5 
880075e4bc70
[   30.965873] Call Trace:
[   30.968397]  [] 
mwifiex_parse_single_response_buf+0x1fc/0x560 [mwifiex]
[   30.976772]  [] ? find_next_bit+0x15/0x20
[   30.982490]  [] 
mwifiex_handle_event_ext_scan_report+0x15c/0x340 [mwifiex]
[   30.991139]  [] mwifiex_process_sta_event+0x276/0xb40 
[mwifiex]
[   30.998806]  [] mwifiex_process_event+0x102/0x1c0 [mwifiex]
[   31.006120]  [] mwifiex_main_process+0x5de/0x8d0 [mwifiex]
[   31.013346]  [] mwifiex_main_work_queue+0x1f/0x30 [mwifiex]
[   31.020650]  [] process_one_work+0x165/0x480
[   31.026624]  [] worker_thread+0x4b/0x4c0
[   31.032240]  [] ? process_one_work+0x480/0x480
[   31.038387]  [] kthread+0xd8/0xf0
[   31.043384]  [] ? kthread_create_on_node+0x1e0/0x1e0
[   31.050071]  [] ret_from_fork+0x3f/0x70
[   31.055596]  [] ? kthread_create_on_node+0x1e0/0x1e0
[   31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 
df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00 
[   31.082756] RIP  [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
[   31.089820]  RSP 
[   31.093392] CR2: 00f0
[   31.096787] ---[ end trace f3a762be5787f138 ]---

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 Status: In Progress


** Tags: originate-from-1654549 plano

** Tags added: originate-from-1654549 plano

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

Title:
  mwifiex causes kernel oops when AP mode is enabled

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  When it's in AP mode, there's quite a chance to find kernel oops
  during reboot.

  [   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
  [   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.716494] PGD 0 
  [   30.718575] Oops:  [#1] SMP 
  [   30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni
  [   30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [   30.845018] Hardware name: Dell Inc. Edge Gateway 5000/  , BIOS 
01.05.00 10/18/2016
  [   30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex]
  [   30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 
880075e48000
  [   30.868018] RIP: 0010:[]  [] 
mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.877484] RSP: 0018:880075e4bbf8  EFLAGS: 00010202
  [   30.882920] RAX:  RBX: 0004 RCX: 
0004
  [   30.890221] RDX: 001000110010 RSI: 0004 RDI: 
0004
  [   30.897520] RBP: 880075e4bc28 R08: 0003 R09: 
0001
  [   30.904821] R10: 0001 R11: 02ff R12: 
0095
  [   30.912123] R13:  R14: 880075e4 R15: 
0095
  [   30.919425] FS:  ()