[Kernel-packages] [Bug 1753489] Re: kernel BUG at /build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!

2018-04-05 Thread Manoj Iyer
reference:  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754053

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

Title:
  kernel BUG at /build/linux-hwe-Fuabdm/linux-
  hwe-4.13.0/fs/jbd2/transaction.c:1868!

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  Incomplete

Bug description:
  [ 1678.415861] kernel BUG at 
/build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!
  [ 1678.425019] Internal error: Oops - BUG: 0 [#1] SMP
  [ 1678.430358] Modules linked in: nls_iso8859_1 i2c_thunderx i2c_smbus 
cavium_rng_vf thunderx_edac thunderx_zip shpchp ipmi_ssif cavium_rng gpio_keys 
ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea aes_ce_blk 
sysfillrect sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce drm 
ghash_ce sha2_ce sha1_ce ahci libahci thunder_bgx thunder_xcv mdio_thunder 
thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd
  [ 1678.503033] CPU: 3 PID: 776 Comm: jbd2/dm-1-8 Tainted: GWL  
4.13.0-36-generic #40~16.04.1-Ubuntu
  [ 1678.515386] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [ 1678.525143] task: 801f8a75e900 task.stack: 801f633fc000
  [ 1678.532489] PC is at __jbd2_journal_temp_unlink_buffer+0x104/0x160
  [ 1678.540140] LR is at __jbd2_journal_file_buffer+0x8c/0x1f8
  [ 1678.547111] pc : [] lr : [] pstate: 
80400145
  [ 1678.556071] sp : 801f633ffb70
  [ 1678.560960] x29: 801f633ffb70 x28: 7e007ca625c0
  [ 1678.567890] x27:  x26: 801ecd5776e8
  [ 1678.574845] x25:  x24: 01400040
  [ 1678.581812] x23: 0001 x22: 801f3f4bb8f0
  [ 1678.588799] x21: 0003 x20: 801f3f4bb8f0
  [ 1678.595787] x19: 801f4a18ea50 x18: 
  [ 1678.602807] x17:  x16: 
  [ 1678.609844] x15: ddd41681 x14: 3a7accb0
  [ 1678.616895] x13: 4d1a8a2c x12: 91b5ac46
  [ 1678.623964] x11: 801f79729770 x10: 093c8c08
  [ 1678.631058] x9 : 001d x8 : 801ecd577750
  [ 1678.638182] x7 :  x6 : 0001
  [ 1678.645323] x5 :  x4 : 0040
  [ 1678.652468] x3 : 0016 x2 : 801f6d655a28
  [ 1678.659633] x1 :  x0 : 801f6d655a00
  [ 1678.666808] Process jbd2/dm-1-8 (pid: 776, stack limit = 
0x801f633fc000)

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

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


[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-04-05 Thread Damian Kidd
Can confirm test kernal fixed my hard lock issue as well:
/proc/version_signature 
Ubuntu 4.13.0-38.43+lp1759920.1-generic 4.13.16
/proc/cmdline
BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-38-generic 
root=UUID=7dcb6f6f-1069-4315-a421-0d60fffecef9 ro rootflags=subvol=@
dmesg -t | grep -i microcode
microcode: microcode updated early to revision 0x2d, date = 2018-02-07
microcode: sig=0x206a7, pf=0x2, revision=0x2d
microcode: Microcode Update Driver: v2.2.

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in intel-microcode source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in intel-microcode source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in intel-microcode source package in Artful:
  Invalid
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Some systems experience kernel lockups after updating to the latest 
intel-microcode
 package or when receiving updated microcode from a BIOS update.

   * In many cases, the lockups occur before users can reach the login screen 
which makes
 it very difficult to debug/workaround.

  [Test Case]

   * The most reliable test case currently known is to install the sssd 
package. Lockups
 may occur during package installation (disable IBPB by writing 0 to
 /proc/sys/kernel/ibpb_enabled to prevent this from happening). A lockup 
will most
 likely occur just after booting the system up as the lock screen is 
displayed.

  [Regression Potential]

   * The fix is in the task switching code of the kernel so complexity of the 
change is
 relatively high.

  [Original Report]

  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
     https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
     
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
     sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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


[Kernel-packages] [Bug 1761610] [NEW] Hisilicon network subsystem 3 support

2018-04-05 Thread dann frazier
Public bug reported:

The HiSilicon D06 server includes a NIC controlled by the hns3 drivers.
Currently this device doesn't work by default in Ubuntu because the
drivers fail to autoload, and they are not available in the server
installer.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Summary changed:

- hns3 support
+ Hisilicon Network Subsystem Support HNS3

** Summary changed:

- Hisilicon Network Subsystem Support HNS3
+ Hisilicon network subsystem 3 support

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

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

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

Title:
  Hisilicon network subsystem 3 support

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The HiSilicon D06 server includes a NIC controlled by the hns3
  drivers. Currently this device doesn't work by default in Ubuntu
  because the drivers fail to autoload, and they are not available in
  the server installer.

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

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


[Kernel-packages] [Bug 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el

2018-04-05 Thread Ryan Finnie
** Attachment added: "libvirt XML file for instance"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+attachment/5103368/+files/1761626-libvirt.xml

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

Title:
  [regression] bionic 4.15.0-13-generic panics on qemu ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel
  panics before initrd.  Going back to xenial 4.4.0 works correctly.

  linux-image-4.15.0-13-generic:
Installed: 4.15.0-13.14
Candidate: 4.15.0-13.14
Version table:
   *** 4.15.0-13.14 500
  500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main 
ppc64el Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic ppc64le
  .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 16:11 seq
   crw-rw 1 root audio 116, 33 Apr  5 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Apr  5 16:13:28 2018
  HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic 
root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro
  ProcLoadAvg: 3.04 2.18 0.92 3/119 1643
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1225 00:12:470 0 EOF
   2: POSIX  ADVISORY  WRITE 841 00:12:459 0 EOF
   3: FLOCK  ADVISORY  WRITE 832 00:12:449 0 EOF
   4: POSIX  ADVISORY  WRITE 802 00:12:432 0 EOF
   5: POSIX  ADVISORY  WRITE 350 00:12:294 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/vda3   partition1408960 0   -1
  ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP 
Mon Apr 2 16:08:02 UTC 2018
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-119-generic N/A
   linux-backports-modules-4.4.0-119-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago)
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

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


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

2018-04-05 Thread 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 1761583

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

Title:
  Asus 200ha, no keyboard or touchpad support

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  17.10.1 - Asus 200ha, keyboard and touchpad not supported, working
  under 16.04.4

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

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


[Kernel-packages] [Bug 1761583] [NEW] Asus 200ha, no keyboard or touchpad support

2018-04-05 Thread Devin Petroff
Public bug reported:

17.10.1 - Asus 200ha, keyboard and touchpad not supported, working under
16.04.4

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

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

Title:
  Asus 200ha, no keyboard or touchpad support

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  17.10.1 - Asus 200ha, keyboard and touchpad not supported, working
  under 16.04.4

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

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


[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-04-05 Thread Kamal Mostafa
Our next kernel version cycle includes the fix for the possibly-related
bug #1759920 (for both the Xenial-generic and linux-aws kernels).  Those
kernels are available for testing now, hot off the builders.  Please
test:

linux-aws:
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/14537808/+files/linux-image-4.4.0-1055-aws_4.4.0-1055.64_amd64.deb
  (full .debs set) 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/14537808

Xenial generic:
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/14537117/+files/linux-image-4.4.0-120-generic_4.4.0-120.144_amd64.deb
  (full .debs set) 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/14537117

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress
Status in linux-aws source package in Xenial:
  In Progress

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1746806/+subscriptions

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


[Kernel-packages] [Bug 1761445] Re: linux-kvm: 4.4.0-1021.26 -proposed tracker

2018-04-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

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

Title:
  linux-kvm: 4.4.0-1021.26 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1761438
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el

2018-04-05 Thread Ryan Finnie
** Attachment added: "Kernel boot log for 4.15.0-13-generic"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+attachment/5103357/+files/1761626-4.15.0-13-generic.boot.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/1761626

Title:
  [regression] bionic 4.15.0-13-generic panics on qemu ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel
  panics before initrd.  Going back to xenial 4.4.0 works correctly.

  linux-image-4.15.0-13-generic:
Installed: 4.15.0-13.14
Candidate: 4.15.0-13.14
Version table:
   *** 4.15.0-13.14 500
  500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main 
ppc64el Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic ppc64le
  .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 16:11 seq
   crw-rw 1 root audio 116, 33 Apr  5 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Apr  5 16:13:28 2018
  HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic 
root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro
  ProcLoadAvg: 3.04 2.18 0.92 3/119 1643
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1225 00:12:470 0 EOF
   2: POSIX  ADVISORY  WRITE 841 00:12:459 0 EOF
   3: FLOCK  ADVISORY  WRITE 832 00:12:449 0 EOF
   4: POSIX  ADVISORY  WRITE 802 00:12:432 0 EOF
   5: POSIX  ADVISORY  WRITE 350 00:12:294 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/vda3   partition1408960 0   -1
  ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP 
Mon Apr 2 16:08:02 UTC 2018
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-119-generic N/A
   linux-backports-modules-4.4.0-119-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago)
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

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


[Kernel-packages] [Bug 1745646] Re: Battery drains when laptop is off (shutdown)

2018-04-05 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
408c9861c6979db974455b9e7a9bcadd60e0934c

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

When you run uname -a this time, the kernel should have this string in
the name: 201804041858

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

Title:
  Battery drains when laptop is off  (shutdown)

Status in Linux:
  Unknown
Status in acpi package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in acpi source package in Artful:
  New
Status in linux source package in Artful:
  In Progress

Bug description:
  I am using hp AY008tx laptop , and many other laptop users (HP) are also 
facing the same issue . The problem don't occur when i install windows 10 . 
Now, only ubuntu is installed.
  i am using latest bios insyde20 rev 5.(latest)
  WOL disabled and no usb device connected
  checked my battery .
  it don't happen when i remove battery and plug it again after shutdown.
  tried laptop_mode_tools and tpl too

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 26 22:50:53 2018
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gopal  2391 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 0a5c:216d Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  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.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EC
  dmi.board.vendor: HP
  dmi.board.version: 61.58
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1761583] Re: Asus 200ha, no keyboard or touchpad support

2018-04-05 Thread Devin Petroff
Can't access terminal due to nonfunctioning keyboard & touchpad

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

Title:
  Asus 200ha, no keyboard or touchpad support

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  17.10.1 - Asus 200ha, keyboard and touchpad not supported, working
  under 16.04.4

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

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


[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-04-05 Thread QkiZ
@Tyler when we should expect this fix in official Ubuntu repository?

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in intel-microcode source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in intel-microcode source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in intel-microcode source package in Artful:
  Invalid
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Some systems experience kernel lockups after updating to the latest 
intel-microcode
 package or when receiving updated microcode from a BIOS update.

   * In many cases, the lockups occur before users can reach the login screen 
which makes
 it very difficult to debug/workaround.

  [Test Case]

   * The most reliable test case currently known is to install the sssd 
package. Lockups
 may occur during package installation (disable IBPB by writing 0 to
 /proc/sys/kernel/ibpb_enabled to prevent this from happening). A lockup 
will most
 likely occur just after booting the system up as the lock screen is 
displayed.

  [Regression Potential]

   * The fix is in the task switching code of the kernel so complexity of the 
change is
 relatively high.

  [Original Report]

  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
     https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
     
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
     sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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


[Kernel-packages] [Bug 1761443] Re: linux-aws: 4.4.0-1055.64 -proposed tracker

2018-04-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1761438
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1761438] Re: linux: 4.4.0-120.144 -proposed tracker

2018-04-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1761439 (linux-aws), bug 1761441 (linux-lts-xenial)
  derivatives: bug 1761443 (linux-aws), bug 1761444 (linux-euclid), bug 1761445 
(linux-kvm), bug 1761446 (linux-raspi2), bug 1761448 (linux-snapdragon)
  kernel-stable-phase-changed:Thursday, 05. April 2018 14:30 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.4.0-120.144 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1761439 (linux-aws), bug 1761441 (linux-lts-xenial)
  derivatives: bug 1761443 (linux-aws), bug 1761444 (linux-euclid), bug 1761445 
(linux-kvm), bug 1761446 (linux-raspi2), bug 1761448 (linux-snapdragon)
  kernel-stable-phase-changed:Thursday, 05. April 2018 14:30 UTC
  kernel-stable-phase:Uploaded

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

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

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


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

2018-04-05 Thread luca
in17.04 sound work with the patch, but my 64Gb microSD does not, nor the
inernation.
In addition if the notebook is closed, the sound is removed and does not
return if the computer is not turned off and sometimes does not load
correctly during boot. Unfortunately, this PC, even it's perfect with
linux, was not born for this and even for windows that takes up all the
memory... you have to adapt or sell it.

Il gio 5 apr 2018 22:06 Devin Petroff <1563...@bugs.launchpad.net> ha
scritto:

> Just wanted to follow up on the status of this?  It says fix committed
> and released, however speakers/headphone jack still not supported in
> 16.04.4 and 17.10.1
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1563110
>
> Title:
>   No sound on Asus e200ha, intel sst with cx2072x codec
>
> Status in ALSA driver:
>   Unknown
> Status in alsa-driver package in Ubuntu:
>   Fix Committed
> Status in linux package in Ubuntu:
>   Fix Released
>
> Bug description:
>   I've recently bought an Asus e200ha.
>   Sound in this laptop doesn't work.
>   The sound card is an intel sst with codec conexant cx2072x
>
>   aplay -l:
>   aplay: device_list:268: no soundcard found...
>   in the sound setting there is a "Dummy output"
>   ---
>   ApportVersion: 2.14.1-0ubuntu3.19
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: XFCE
>   DistroRelease: Ubuntu 14.04
>   HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
>   InstallationDate: Installed on 2016-03-28 (0 days ago)
>   InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
>   Lsusb:
>Bus 002 Device 002: ID 0781:5583 SanDisk Corp.
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 13d3:3496 IMC Networks
>Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: ASUSTeK COMPUTER INC. E200HA
>   Package: linux (not installed)
>   ProcEnviron:
>TERM=xterm
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=it_IT.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic
> root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
>   RelatedPackageVersions:
>linux-restricted-modules-3.19.0-32-generic N/A
>linux-backports-modules-3.19.0-32-generic  N/A
>linux-firmware 1.127.16
>   Tags:  rosa
>   Uname: Linux 3.19.0-32-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 11/26/2015
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: E200HA.203
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: E200HA
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: 1.0
>   dmi.chassis.asset.tag: ATN12345678901234567
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK COMPUTER INC.
>   dmi.chassis.version: 1.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
>   dmi.product.name: E200HA
>   dmi.product.version: 1.0
>   dmi.sys.vendor: ASUSTeK COMPUTER INC.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions
>

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

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

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

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

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b 

[Kernel-packages] [Bug 1754979] Re: zfs-dkms 0.6.5.6-0ubuntu19: zfs kernel module failed to build

2018-04-05 Thread Laurent Dinclaux
Since kernel 4.13.0-37

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu19: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Happened on a simple software update.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu19
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.13.0-36-generic (x86_64)
   Sun Mar 11 09:58:57 MDT 2018
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.13.0-36-generic
  Date: Sun Mar 11 09:59:00 2018
  InstallationDate: Installed on 2017-12-16 (84 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageVersion: 0.6.5.6-0ubuntu19
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu19: zfs kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1745646] Re: Battery drains when laptop is off (shutdown)

2018-04-05 Thread Gopal
4.12.0-041200-generic #201804051118  is 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/1745646

Title:
  Battery drains when laptop is off  (shutdown)

Status in Linux:
  Unknown
Status in acpi package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in acpi source package in Artful:
  New
Status in linux source package in Artful:
  In Progress

Bug description:
  I am using hp AY008tx laptop , and many other laptop users (HP) are also 
facing the same issue . The problem don't occur when i install windows 10 . 
Now, only ubuntu is installed.
  i am using latest bios insyde20 rev 5.(latest)
  WOL disabled and no usb device connected
  checked my battery .
  it don't happen when i remove battery and plug it again after shutdown.
  tried laptop_mode_tools and tpl too

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 26 22:50:53 2018
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gopal  2391 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 0a5c:216d Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  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.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EC
  dmi.board.vendor: HP
  dmi.board.version: 61.58
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1761534] Re: "ip a" command on a guest VM shows UNKNOWN status

2018-04-05 Thread Eric Desrochers
** Description changed:

+ 
+ [Impact] 
+ 
+ "ip a" command on a guest VM shows UNKNOWN status.
+ 
+ [Test Case]
+ 
+ * Environment : Running a guest VM with a virtio-net adaptor interface, 
running on DPDK.
+ * Perform "ip a" inside the guest VM shows state "UNKNOWN" as follow example:
+ 
+ 2: eth0:  mtu 1500 qdisc pfifo_fast state 
UNKNOWN group default qlen 1000
+ .
+ 
+ [Regression Potential]
+ 
+  * Regression is low, the patch fix the operstate logic for virtio when no 
VIRTIO_NET_F_STATUS.[1]
+  * The patch has been first accepted in net-next, then move into Linus's git.
+ 
+ [1] - VIRTIO_NET_F_STATUS
+ Allow the host to inform us that the link is down by adding a 
VIRTIO_NET_F_STATUS which indicates that device status is available in 
virtio_net config.
+ 
+ [Other Info]
+  
+  * Linus: 
https://github.com/torvalds/linux/commit/bda7fab54828bbef2164bb23c0f6b1a7d05cc718
+ 
+  * Net-next:
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=bda7fab54828bbe
 
+ 
+ [Original Description]
  It has been brought to our attention the following bug :
  
  
  Environment: The guest VM is using a canonical ubuntu image, and the eth0 is 
a virtio-net adaptor, running on DPDK.
  
  Background: "ip a" command relies on the operstate variable of the
  net_device structure maintained by the kernel. This is based on the
  operational state as defined in the IF MIB (RFC 2863). Device drivers
  are expected to update this member. But many older drivers don’t seem to
  be using this. So in general, IF_OPER_UP and IF_OPER_UNKNOWN are treated
  as equal, in some sense, to maintain backward compatibility. Even if we
  look at https://elixir.free-
  electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L3468,
  the function to check if interface is up, is written as follows, which
  says that OPER_UNKNOWN is not something to be alarmed about, and just
  reflective of a state that some drivers don’t care to update about.
  
  static inline bool netif_oper_up(const struct net_device *dev)
  {
  return (dev->operstate == IF_OPER_UP ||
  dev->operstate == IF_OPER_UNKNOWN /* backward compat */);
  }
  
  Code Ref:
  
  1. 
https://elixir.free-electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L1739
  2. 
https://elixir.free-electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L3468
  3. https://www.kernel.org/doc/Documentation/networking/operstates.txt
  
  Now, for traditional kernel mode network adapter drivers, this state is 
supposed to be manipulated by the driver. And we can safely assume that most 
current kernel model drivers do keep this updated.
  

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

Title:
  "ip a" command on a guest VM shows UNKNOWN status

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  
  [Impact] 

  "ip a" command on a guest VM shows UNKNOWN status.

  [Test Case]

  * Environment : Running a guest VM with a virtio-net adaptor interface, 
running on DPDK.
  * Perform "ip a" inside the guest VM shows state "UNKNOWN" as follow example:

  2: eth0:  mtu 1500 qdisc pfifo_fast state 
UNKNOWN group default qlen 1000
  .

  [Regression Potential]

   * Regression is low, the patch fix the operstate logic for virtio when no 
VIRTIO_NET_F_STATUS.[1]
   * The patch has been first accepted in net-next, then move into Linus's git.

  [1] - VIRTIO_NET_F_STATUS
  Allow the host to inform us that the link is down by adding a 
VIRTIO_NET_F_STATUS which indicates that device status is available in 
virtio_net config.

  [Other Info]
   
   * Linus: 
https://github.com/torvalds/linux/commit/bda7fab54828bbef2164bb23c0f6b1a7d05cc718

   * Net-next:
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=bda7fab54828bbe
 

  [Original Description]
  It has been brought to our attention the following bug :

  
  Environment: The guest VM is using a canonical ubuntu image, and the eth0 is 
a virtio-net adaptor, running on DPDK.

  Background: "ip a" command relies on the operstate variable of the
  net_device structure maintained by the kernel. This is based on the
  operational state as defined in the IF MIB (RFC 2863). Device drivers
  are expected to update this member. But many older drivers don’t seem
  to be using this. So in general, IF_OPER_UP and IF_OPER_UNKNOWN are
  treated as equal, in some sense, to maintain backward compatibility.
  Even if we look at 

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

2018-04-05 Thread Devin Petroff
Just wanted to follow up on the status of this?  It says fix committed
and released, however speakers/headphone jack still not supported in
16.04.4 and 17.10.1

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

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

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

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

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

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

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


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

2018-04-05 Thread bugproxy
--- Comment From wenxi...@us.ibm.com 2018-04-05 16:57 EDT---
Based on comment #34, subsystem-reset works fine with the latest kernel. Close 
the bug.

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

Title:
  Ubuntu 18.04 - Kernel crash on nvme subsystem-reset /dev/nvme0 (Bolt /
  NVMe)

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

Bug description:
  == Comment: #1 - NAVEED A. UPPINANGADY SALIH  -
  2018-02-25 23:45:13 ==

  
  == Comment: #6 - Wen Xiong  - 2018-02-27 10:41:23 ==
  hi Naveed,

  nvme subsystem-reset calls EEH recovery path. Is EEH recovery working
  with Bolt on this machine?

  Thanks,
  Wendy

  == Comment: #11 - Wen Xiong  - 2018-03-02 16:03:46 ==
  The following patch should fix the issue.

  http://lists.infradead.org/pipermail/linux-
  nvme/2018-February/015745.html

  It should be accepted into community soon. Keith has agreed to queue
  up for 4.16.

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

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


[Kernel-packages] [Bug 1761619] [NEW] eventfd / poll interaction bug

2018-04-05 Thread Garrett D'Amore
Public bug reported:

In 17.10, I'm running into a new problem.  This didn't happen to me on
16.04.

I have some code that uses eventfds to signal things, and the code is
not working -- after writing the eventfd, it does not come back readable
from another thread using poll().

Here's a snippet from strace:

```
eventfd2(0, 0)  = 5
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
write(1, "OPEN FD 5\n", 10OPEN FD 5
) = 10
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
nanosleep({tv_sec=0, tv_nsec=1}, 0x7fffd0cea1a0) = 0
poll([{fd=5, events=POLLRDNORM}], 1, 100) = 0 (Timeout)
```

The write(1,... ) is debugging output.  The nanosleep was intended to
see if sleeping a bit before polling would help.  Note that the write(5,
...) and the poll() come from different threads.

Note that using two descriptors from a pipe() (which I do for other
platforms) is fine, so this is some kind of issue specific to eventfd.

Also, trying to reproduce this with a simpler single threaded program
did not succeed.  I'm wondering if there is some underlying cache
synchronization problem?

I'm testing this in a VMware Fusion virtual machine (Fusion 10.1.1)
running on 2017 macbook pro (underlying OS is macOS 10.13).

For now I'm going to switch back to pipes, since eventfd() seems
unreliable -- if you can spot anything obviously wrong about the system
call sequence above, I'd love to hear it.

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

Title:
  eventfd / poll interaction bug

Status in linux package in Ubuntu:
  New

Bug description:
  In 17.10, I'm running into a new problem.  This didn't happen to me on
  16.04.

  I have some code that uses eventfds to signal things, and the code is
  not working -- after writing the eventfd, it does not come back
  readable from another thread using poll().

  Here's a snippet from strace:

  ```
  eventfd2(0, 0)  = 5
  fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
  write(1, "OPEN FD 5\n", 10OPEN FD 5
  ) = 10
  write(5, "\1\0\0\0\0\0\0\0", 8) = 8
  nanosleep({tv_sec=0, tv_nsec=1}, 0x7fffd0cea1a0) = 0
  poll([{fd=5, events=POLLRDNORM}], 1, 100) = 0 (Timeout)
  ```

  The write(1,... ) is debugging output.  The nanosleep was intended to
  see if sleeping a bit before polling would help.  Note that the
  write(5, ...) and the poll() come from different threads.

  Note that using two descriptors from a pipe() (which I do for other
  platforms) is fine, so this is some kind of issue specific to eventfd.

  Also, trying to reproduce this with a simpler single threaded program
  did not succeed.  I'm wondering if there is some underlying cache
  synchronization problem?

  I'm testing this in a VMware Fusion virtual machine (Fusion 10.1.1)
  running on 2017 macbook pro (underlying OS is macOS 10.13).

  For now I'm going to switch back to pipes, since eventfd() seems
  unreliable -- if you can spot anything obviously wrong about the
  system call sequence above, I'd love to hear it.

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

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


[Kernel-packages] [Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport

2018-04-05 Thread Ersin
Today's 18.04 upgrade from 17.10, using 4k or 1080 monitor with display port or 
with HDMI for Radeon RX 460 booting until bios,then screen flashing with 
jumbled colors every few seconds, shutdown displays Ubuntu logo.
Removing graphics card and using onboard HDMI for both is same as above, but 
shows Ubuntu loading animation, then no signal.
Starting without monitor the plugging in 1080 shows attached picture between 
flashing

** Attachment added: "Screenshot_20180405-153332.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723619/+attachment/5103173/+files/Screenshot_20180405-153332.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/1723619

Title:
  Ubuntu Desktop ISO fails to boot with nouveau on a displayport

Status in Linux:
  Confirmed
Status in Release Notes for Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the latest daily artful image (/current as of 2017-10-14), the
  following occurs on a system with nVidia graphics (on my system, a
  GTX970) when connected to a 4k display over a displayport:
  https://photos.app.goo.gl/gLUva3Vgvtv0lAmj2

  Steps to reproduce:
  - Download latest daily image, check checksums, burn to USB
  - Boot from USB.
  - Choose "Install Ubuntu" or "try ubuntu" at the menu.

  This happens on the livecd, but also upon ugrading the system from a
  previous daily with a different kernel: my "old" daily booted and
  installed fine with kernel 4.12.0-12, then failed with same error once
  dist-upgraded.

  On the faulty system I could test with, it seems to *only* happen over
  displayport/on a 4k screen (I don't own a non-4k displayport screen to
  test the 4k out).

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

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


Re: [Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-04-05 Thread Tyler Hicks
On 04/05/2018 03:25 PM, QkiZ wrote:
> @Tyler when we should expect this fix in official Ubuntu repository?
A little over 2 weeks from now. The week of April 23rd is the current
target.

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in intel-microcode source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in intel-microcode source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in intel-microcode source package in Artful:
  Invalid
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Some systems experience kernel lockups after updating to the latest 
intel-microcode
 package or when receiving updated microcode from a BIOS update.

   * In many cases, the lockups occur before users can reach the login screen 
which makes
 it very difficult to debug/workaround.

  [Test Case]

   * The most reliable test case currently known is to install the sssd 
package. Lockups
 may occur during package installation (disable IBPB by writing 0 to
 /proc/sys/kernel/ibpb_enabled to prevent this from happening). A lockup 
will most
 likely occur just after booting the system up as the lock screen is 
displayed.

  [Regression Potential]

   * The fix is in the task switching code of the kernel so complexity of the 
change is
 relatively high.

  [Original Report]

  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
     https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
     
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
     sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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


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

2018-04-05 Thread 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/1761626

Title:
  [regression] bionic 4.15.0-13-generic panics on qemu ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel
  panics before initrd.  Going back to xenial 4.4.0 works correctly.

  linux-image-4.15.0-13-generic:
Installed: 4.15.0-13.14
Candidate: 4.15.0-13.14
Version table:
   *** 4.15.0-13.14 500
  500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main 
ppc64el Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic ppc64le
  .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 16:11 seq
   crw-rw 1 root audio 116, 33 Apr  5 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Apr  5 16:13:28 2018
  HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic 
root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro
  ProcLoadAvg: 3.04 2.18 0.92 3/119 1643
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1225 00:12:470 0 EOF
   2: POSIX  ADVISORY  WRITE 841 00:12:459 0 EOF
   3: FLOCK  ADVISORY  WRITE 832 00:12:449 0 EOF
   4: POSIX  ADVISORY  WRITE 802 00:12:432 0 EOF
   5: POSIX  ADVISORY  WRITE 350 00:12:294 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/vda3   partition1408960 0   -1
  ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP 
Mon Apr 2 16:08:02 UTC 2018
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-119-generic N/A
   linux-backports-modules-4.4.0-119-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago)
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

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


[Kernel-packages] [Bug 1745646] Re: Battery drains when laptop is off (shutdown)

2018-04-05 Thread Gopal
4.12.0-041200-generic #201804051944 SMP Thu Apr 5 19:47:43 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux
 before shutdown : http://paste.ubuntu.com/p/538Y9Fgjft/

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

Title:
  Battery drains when laptop is off  (shutdown)

Status in Linux:
  Unknown
Status in acpi package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in acpi source package in Artful:
  New
Status in linux source package in Artful:
  In Progress

Bug description:
  I am using hp AY008tx laptop , and many other laptop users (HP) are also 
facing the same issue . The problem don't occur when i install windows 10 . 
Now, only ubuntu is installed.
  i am using latest bios insyde20 rev 5.(latest)
  WOL disabled and no usb device connected
  checked my battery .
  it don't happen when i remove battery and plug it again after shutdown.
  tried laptop_mode_tools and tpl too

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 26 22:50:53 2018
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gopal  2391 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 0a5c:216d Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  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.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EC
  dmi.board.vendor: HP
  dmi.board.version: 61.58
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

2018-04-05 Thread Tyler Hicks
Thanks! I just submitted the pull request for bionic. We're too late for
the current SRU cycle for the stable releases (17.10, 16.04 LTS, and
14.04 LTS) so we'll have to pick them up in the next SRU cycle.

Note that I didn't include the section mismatch warning since it hadn't
been reviewed or merged into linux-next but the patch was sufficient in
showing me that the warning isn't an issue. Thanks for following up on
that.

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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


[Kernel-packages] [Bug 1753114] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel

2018-04-05 Thread dino99
*** This bug is a duplicate of bug 1760876 ***
https://bugs.launchpad.net/bugs/1760876

** No longer affects: r8168 (Ubuntu)

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

Title:
  DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y,
  please install libelf-dev, libelf-devel or elfutils-libelf-devel

Status in bcmwl package in Ubuntu:
  Confirmed
Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Had the need to install r8168-dkms, but got a make.log error:

  
  DKMS make.log for r8168-8.045.08 for kernel 4.15.0-11-generic (x86_64)
  Sat Mar  3 16:08:17 CET 2018
  make: Entering directory '/usr/src/linux-headers-4.15.0-11-generic'
  Makefile:962: "Cannot use CONFIG_STACK_VALIDATION=y, please install 
libelf-dev, libelf-devel or elfutils-libelf-devel"
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_n.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_asf.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtl_eeprom.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtltool.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.o
Building modules, stage 2.
MODPOST 1 modules
CC  /var/lib/dkms/r8168/8.045.08/build/r8168.mod.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.ko
  make: Leaving directory '/usr/src/linux-headers-4.15.0-11-generic'
  

  so i have installed libelf-dev, and reinstalled r8168-dkms again. Next
  the make.log looks:

  ***
  DKMS make.log for r8168-8.045.08 for kernel 4.15.0-11-generic (x86_64)
  Sat Mar  3 16:15:11 CET 2018
  make: Entering directory '/usr/src/linux-headers-4.15.0-11-generic'
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_n.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_asf.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtl_eeprom.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtltool.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.o
Building modules, stage 2.
MODPOST 1 modules
CC  /var/lib/dkms/r8168/8.045.08/build/r8168.mod.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.ko
  make: Leaving directory '/usr/src/linux-headers-4.15.0-11-generic'
  **

  So please, add libelf-dev as r8168-dkms dependency.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: r8168-dkms 8.045.08-2
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar  3 16:11:00 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: r8168
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1611644] Re: Error parsing configuration file '~/.nvidia-settings-rc' '0/TextureSharpen=0' (Unrecognized attribute name)

2018-04-05 Thread dino99
** Changed in: nvidia-settings (Ubuntu)
   Status: New => Invalid

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

Title:
   Error parsing configuration file '~/.nvidia-settings-rc'
  '0/TextureSharpen=0' (Unrecognized attribute name)

Status in nvidia-settings package in Ubuntu:
  Invalid

Bug description:
  This is now logged with the 367 version:

  journalctl | grep nvidia-settings
  nvidia-settings-autostart.desktop[3783]: ERROR: Error parsing configuration 
file '/home/oem/.nvidia-settings-rc' on
  nvidia-settings-autostart.desktop[3783]:line 26: '0/TextureSharpen=0' 
(Unrecognized attribute name).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nvidia-settings 367.35-0ubuntu1
  ProcVersionSignature: Ubuntu 4.7.0-0.3-generic 4.7.0
  Uname: Linux 4.7.0-0-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug 10 09:34:11 2016
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1611644/+subscriptions

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


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

2018-04-05 Thread 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 1761619

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

Title:
  eventfd / poll interaction bug

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In 17.10, I'm running into a new problem.  This didn't happen to me on
  16.04.

  I have some code that uses eventfds to signal things, and the code is
  not working -- after writing the eventfd, it does not come back
  readable from another thread using poll().

  Here's a snippet from strace:

  ```
  eventfd2(0, 0)  = 5
  fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
  write(1, "OPEN FD 5\n", 10OPEN FD 5
  ) = 10
  write(5, "\1\0\0\0\0\0\0\0", 8) = 8
  nanosleep({tv_sec=0, tv_nsec=1}, 0x7fffd0cea1a0) = 0
  poll([{fd=5, events=POLLRDNORM}], 1, 100) = 0 (Timeout)
  ```

  The write(1,... ) is debugging output.  The nanosleep was intended to
  see if sleeping a bit before polling would help.  Note that the
  write(5, ...) and the poll() come from different threads.

  Note that using two descriptors from a pipe() (which I do for other
  platforms) is fine, so this is some kind of issue specific to eventfd.

  Also, trying to reproduce this with a simpler single threaded program
  did not succeed.  I'm wondering if there is some underlying cache
  synchronization problem?

  I'm testing this in a VMware Fusion virtual machine (Fusion 10.1.1)
  running on 2017 macbook pro (underlying OS is macOS 10.13).

  For now I'm going to switch back to pipes, since eventfd() seems
  unreliable -- if you can spot anything obviously wrong about the
  system call sequence above, I'd love to hear it.

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

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


[Kernel-packages] [Bug 1745646] Re: Battery drains when laptop is off (shutdown)

2018-04-05 Thread Gopal
4.12.0-041200-generic #201804051944 is bad

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

Title:
  Battery drains when laptop is off  (shutdown)

Status in Linux:
  Unknown
Status in acpi package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in acpi source package in Artful:
  New
Status in linux source package in Artful:
  In Progress

Bug description:
  I am using hp AY008tx laptop , and many other laptop users (HP) are also 
facing the same issue . The problem don't occur when i install windows 10 . 
Now, only ubuntu is installed.
  i am using latest bios insyde20 rev 5.(latest)
  WOL disabled and no usb device connected
  checked my battery .
  it don't happen when i remove battery and plug it again after shutdown.
  tried laptop_mode_tools and tpl too

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 26 22:50:53 2018
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gopal  2391 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 0a5c:216d Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  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.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EC
  dmi.board.vendor: HP
  dmi.board.version: 61.58
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1748487] Re: Please upgrade to get kernel management

2018-04-05 Thread dino99
Still getting these errors with 4.15.0-15

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

Title:
  Please upgrade to get  kernel management

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  Bionic still has that old version from 2013
  Debian have a more recent version: 
http://metadata.ftp-master.debian.org/changelogs/main/a/acpi-support/acpi-support_0.142-8_changelog
  Actual source: http://www.uefi.org/acpi

  Kernel (upstream) is supposed to have fixed the problem:
  
https://github.com/torvalds/linux/blob/eceeae414edccb07fad683011c0c65abe8a3a554/include/acpi/acpixf.h#L195

  Does ubuntu kernel apply that patch ?
  https://bugzilla.kernel.org/show_bug.cgi?id=117671

  Because kernel 4.15.0-9 still log these errors:

  kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, 
AE_NOT_FOUND (20170831/dswload-210)
  kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20170831/psobject-252)
  kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20170831/tbxfload-228)
  kernel: ACPI Error: 1 table load failures, 5 successful 
(20170831/tbxfload-246)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: acpi-support 0.142
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb  9 17:49:39 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: acpi-support
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools

2018-04-05 Thread Seth Arnold
One of the udev rules files appears to be untranslated:

./thunderbolt-tools_0.9.3-1_amd64/lib/udev/rules.d/tbtacl.rules:
# Thunderbolt udev rules for ACL (device auto approval)
SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="add"
ATTR{authorized}=="0" RUN+="@UDEV_BIN_DIR@/tbtacl add$devpath"
SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="change" 
ATTR{authorized}!="0" RUN+="@UDEV_BIN_DIR@/tbtacl change $devpath"

The proper contents are in .../60-tbtacl.rules so probably the fix is
easy.

Thanks

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

Title:
   [MIR] thunderbolt-tools

Status in thunderbolt-tools package in Ubuntu:
  Confirmed

Bug description:
  == Overview ==

  Intel Thunderbolt userspace components provides components for using
  Intel Thunderbolt controllers with security level features.
  Thunderbolt™ technology is a transformational high-speed, dual
  protocol I/O that provides unmatched performance with up to 40Gbps bi-
  directional transfer speeds. It provides flexibility and simplicity by
  supporting both data (PCIe, USB3.1) and video (DisplayPort) on a
  single cable connection that can daisy-chain up to six devices.

  [ See https://github.com/intel/thunderbolt-software-user-space ]

  == Answers to UbuntuMainInclusionRequirements ==

  = Requirements =

  1. Availability
 Package is in universe: 
https://launchpad.net/ubuntu/+source/thunderbolt-tools

  2. Rationale
 Package a device enabler for users with Thunderbolt technology

  3. Security:
 No security issues exposed so far. However, the tools have only been in 
Ubuntu since
 2017-12-09, so this currently is less than the 90 days threshold.

  4. Quality assurance:
 * Manual is provided
 * No debconf questions higher than medium
 * No major outstanding bugs. I'm also helping Intel fix issues that I'm 
finding with
   static analysis tools such as scan-build, cppcheck and CoverityScan
   Bugs outstanding:
 #883857 please backport for stretch-backports
 #882525 thunderbolt-tools: FTBFS on kFreeBSD: 
_ZN5boost6system15system_categoryEv undefined
   - I can fix this, but it makes no sense to run on kFreeBSD
 * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an 
industry standard
   and the support for the tools are in the 4.13+ kernels
 * No Test Suite shipped with the package
 * Does not rely on obsolete or demoted packages

  5. UI standards:
 * This is a CLI tool. Tool has normal CLI style short help and man pages
 * No desktop file required as it is a CLI tool.

  6. Binary Dependencies:
libboost-dev(main)
libboost-filesystem-dev (main)
libboost-program-options-dev(main)
udev(main)

  7. Standards compliance:
 lintian clean and meets the FHS + Debian Policy standards to the best of 
my knowledge

  8. Maintenance
 * Package owning team: The Ubuntu Kernel Team
 * Debian package maintained by Colin Ian King (myself from the Kernel Team)

  9. Background Information
 The user-space components implement device approval support:

 a. Easier interaction with the kernel module for approving connected 
devices.
 b. ACL for auto-approving devices white-listed by the user.

 Tools provided by this package:

  tbtacl - triggered by udev (see the udev rules in tbtacl.rules).
  It auto-approves devices that are found in ACL.

  tbtadm - user-facing CLI tool. It provides operations for device
  approval, handling the ACL and more.

  The user-space components operate in coordination with the
  upstream Thunderbolt kernel driver (found in v4.13) to provide the
  Thunderbolt functionalities. These components are NOT compatible with
  the old out-of-tree Thunderbolt kernel module.

  = Security checks =

http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability 
Database using the package as a keyword
* No CVEs found

http://secunia.com/advisories/search/: search for the package as a keyword
* No security advisories found

Ubuntu CVE Tracker
  http://people.ubuntu.com/~ubuntu-security/cve/main.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/universe.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/partner.html
  * No

  Check for security relevant binaries. If any are present, this
  requires a more in-depth security review.

  Executables which have the suid or sgid bit set.
* Not applicable

  Executables in /sbin, /usr/sbin.
* None in these paths

  Packages which install daemons (/etc/init.d/*)
* No

  Packages which open privileged ports (ports < 1024).
* 

[Kernel-packages] [Bug 1665972] Re: kernel: cgroup: new mount options do not match the existing superblock

2018-04-05 Thread dino99
** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

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

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

Title:
  kernel: cgroup: new mount options do not match the existing superblock

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

Bug description:
  From journalctl

  kernel: cgroup: new mount options do not match the existing superblock

  Looks like that patch is needed with kernel 4.10, as that issue was
  not seen with the previous kernels

  https://www.spinics.net/lists/kernel/msg2447988.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-8-generic 4.10.0-8.10
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem   11316 F pulseaudio
   /dev/snd/pcmC0D0p:   oem   11316 F...m pulseaudio
   /dev/snd/controlC0:  oem   11316 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Feb 19 08:05:08 2017
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   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: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-8-generic N/A
   linux-backports-modules-4.10.0-8-generic  N/A
   linux-firmware1.163
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Kernel-packages] [Bug 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el

2018-04-05 Thread Ryan Finnie
Same result with 4.16.0-041600-generic and 4.13.0-38-generic

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

Title:
  [regression] bionic 4.15.0-13-generic panics on qemu ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel
  panics before initrd.  Going back to xenial 4.4.0 works correctly.

  linux-image-4.15.0-13-generic:
Installed: 4.15.0-13.14
Candidate: 4.15.0-13.14
Version table:
   *** 4.15.0-13.14 500
  500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main 
ppc64el Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic ppc64le
  .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 16:11 seq
   crw-rw 1 root audio 116, 33 Apr  5 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Apr  5 16:13:28 2018
  HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic 
root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro
  ProcLoadAvg: 3.04 2.18 0.92 3/119 1643
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1225 00:12:470 0 EOF
   2: POSIX  ADVISORY  WRITE 841 00:12:459 0 EOF
   3: FLOCK  ADVISORY  WRITE 832 00:12:449 0 EOF
   4: POSIX  ADVISORY  WRITE 802 00:12:432 0 EOF
   5: POSIX  ADVISORY  WRITE 350 00:12:294 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/vda3   partition1408960 0   -1
  ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP 
Mon Apr 2 16:08:02 UTC 2018
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-119-generic N/A
   linux-backports-modules-4.4.0-119-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago)
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

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


[Kernel-packages] [Bug 1761433] Re: linux-lts-trusty: 3.13.0-145.194~precise1 -proposed tracker

2018-04-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-precise

** Tags added: block-proposed

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

Title:
  linux-lts-trusty: 3.13.0-145.194~precise1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1761430
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1761430] Re: linux: 3.13.0-145.194 -proposed tracker

2018-04-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-trusty

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1761433 (linux-lts-trusty)
  derivatives:
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 05. April 2018 15:30 UTC
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 3.13.0-145.194 -proposed tracker

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

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

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

  backports: bug 1761433 (linux-lts-trusty)
  derivatives:
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 05. April 2018 15:30 UTC

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

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

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


[Kernel-packages] [Bug 1761456] Re: linux: 4.13.0-39.44 -proposed tracker

2018-04-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-artful

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 
1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem)
  derivatives: bug 1761458 (linux-raspi2)
  kernel-stable-phase-changed:Thursday, 05. April 2018 14:32 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.13.0-39.44 -proposed tracker

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

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

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

  backports: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 
1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem)
  derivatives: bug 1761458 (linux-raspi2)
  kernel-stable-phase-changed:Thursday, 05. April 2018 14:32 UTC
  kernel-stable-phase:Uploaded

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

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

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


[Kernel-packages] [Bug 1736549] Re: Poor kernel builtin r8169 driver performance, r8168-dkms driver not compatible with kernels > 4.7

2018-04-05 Thread dino99
Works with actual kernels

** No longer affects: r8168-dkms (Ubuntu)

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

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

Title:
  Poor kernel builtin r8169 driver performance, r8168-dkms driver not
  compatible with kernels > 4.7

Status in linux package in Ubuntu:
  Invalid

Bug description:
  From the Bionic archive (universe) the r8168-dkms driver is supposed
  to get better performance compared to the kernel builin r8169 one,
  which has degraded speed mainly due to MTU 576 and only using 100
  Mbits/s.

  Installing that driver onto a 4.13.13 based kernel goes as expected,
  but after rebooting there is no network at all, ping fails.
  Blacklisting r8169 or not makes no difference.

  An issue is opened on https://github.com/mtorromeo/r8168/issues/9

  So that driver is not usable actually with the proposed kernels from
  the recent ubuntu releases; maybe the driver description could point
  that limitation, if a bypass is not found.

  Will get a chance to the propositions found on:
  https://wiki.hetzner.de/index.php/Installation_des_r8168-Treibers/en

  About the kernel itself, maybe the builtin r8169 driver could deliver better 
performance , for example setting MTU to >=1492 at least.
  ---
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1288 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: r8168-dkms 8.045.08-1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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.
  modified.conffile..etc.modprobe.d.r8168-dkms.conf: [modified]
  mtime.conffile..etc.modprobe.d.r8168-dkms.conf: 2017-12-05T17:18:49.107998

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

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


[Kernel-packages] [Bug 1758856] Re: retpoline hints: primary infrastructure and initial hints

2018-04-05 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Artful)
   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/1758856

Title:
  retpoline hints: primary infrastructure and initial hints

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Tracking bug for the application of the retpoline hint tracking
  support.

  We are having terrible trouble with hints changing on every build.
  Upstream is moving to hinting those indirections which have been
  reviewed and are good.  This includes direct hinting of PVOPS and the
  like which are the ones which change all the time as new ones appear
  and dissappear.

  Backport the hint support and add our own bespoke checkers against
  this data.

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

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


[Kernel-packages] [Bug 1761430] [NEW] linux: -proposed tracker

2018-04-05 Thread Kleber Sacilotto de Souza
Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

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

backports: bug 1761433 (linux-lts-trusty)
derivatives:

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Trusty)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.04.02-1 kernel-sru-master-kernel trusty

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: trusty

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: 

[Kernel-packages] [Bug 1761456] [NEW] linux: -proposed tracker

2018-04-05 Thread Kleber Sacilotto de Souza
Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

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

backports: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 
1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem)
derivatives: bug 1761458 (linux-raspi2)

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Artful)
 Importance: Medium
 Status: Confirmed


** Tags: artful kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.04.02-1 kernel-sru-master-kernel

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: artful

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta

[Kernel-packages] [Bug 1761468] [NEW] Debian-installer missing mmc bcm2835 module

2018-04-05 Thread Adam Smith
Public bug reported:

Testing the latest arm64 18.04 mini ISO on a raspberry pi 3, I found the
internal sd card reader was not recognised.  This is the main storage on
a pi.  Manually extracting the mmc/host/bcm2835 module from the extras
package and insmod'ing it got it working on the d-i installer.

It would be great if the sd card could be recognised out of the box.  I
think all that is needed is to include the module in the block storage
udeb.

Note the pi has two SD controllers.  A second is used for the WiFi (but
can also be used for the sd card reader).  That is also missing from the
debian installer as far as I can tell.

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

Title:
  Debian-installer missing mmc bcm2835 module

Status in linux package in Ubuntu:
  New

Bug description:
  Testing the latest arm64 18.04 mini ISO on a raspberry pi 3, I found
  the internal sd card reader was not recognised.  This is the main
  storage on a pi.  Manually extracting the mmc/host/bcm2835 module from
  the extras package and insmod'ing it got it working on the d-i
  installer.

  It would be great if the sd card could be recognised out of the box.
  I think all that is needed is to include the module in the block
  storage udeb.

  Note the pi has two SD controllers.  A second is used for the WiFi
  (but can also be used for the sd card reader).  That is also missing
  from the debian installer as far as I can tell.

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

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


[Kernel-packages] [Bug 1381968] Re: Fstrim destroys data on loopback device

2018-04-05 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
 Assignee: Andy Whitcroft (apw) => (unassigned)

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

Title:
  Fstrim destroys data on loopback device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've upgraded Ubuntu Server 12.04 LTS to 14.04 LTS.

  The setup contains a loopback device (/dev/loop3) mounted into a
  software raid 1 (/dev/md2).

  After the weekly cronjob (/etc/cron.weekly/fstrim) ran, I've
  discovered that it wiped all data on the loopback device from the
  raid.

  fstrim-all skips check because the loopback device is part of device mapper 
raid.
  if [ "${REALDEV#/dev/dm-}" != "$REALDEV" ]; then
  echo "device $DEV is on devmapper, skipping TRIM feature check"

  Issue can be reproduced on raid setup and plain loopback mount setup!

  Here is step-by-step how to reproduce the issue:

  1.) create sparse image file
  dd of=/sparse-file bs=1k seek=1024000

  2.) losetup loopback device
  losetup /dev/loop3 /sparse-file

  3.) create raid1
  mdadm --create /dev/md2 --auto md --level=1 --raid-devices=1 /dev/loop3

  4.) create fs
  mkfs.ext4 /dev/md2

  4.1.) check sparse-file size
  ls -lash /sparse-file

  5.) mount and copy data
  mount /dev/md2 /mnt
  copy some random files on /mnt

  5.1.) check sparse-file size again
  ls -lash /sparse-file -> size indicates it contains the copied data

  6.) destroy loopback via fstrim
  fstrim -v /mnt

  7.) data is wiped
  umount /mnt
  ls -lash /sparse-file -> size indicates that all data is wiped out!
  fsck -v -f /dev/md2 -> will report infinite errors on filesystem

  I could not find any similiar bugreport.

  Best Regards
  Daniel

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

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


[Kernel-packages] [Bug 1728651] Re: System hangs after iwlwifi firmware crash

2018-04-05 Thread Alistair Cunningham
Upon upgrading to Ubuntu 18.04 beta, which runs kernel 4.15.0-13-generic
and iwlwifi 8265 driver firmware 34.0.1, this problem seems to have gone
away.

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

Title:
  System hangs after iwlwifi firmware crash

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Kubuntu 17.10 my HP EliteBook 820 G3 hangs at
  unpredictable times. I have experienced probably 20 hangs. Once the
  system is hung no mouse movement, NumLock toggle, VT switch,
  Ctrl+Alt+Del, SysRq keys, SSH attempts have any effect whatsoever. Any
  audio playing is stuck looping in the hardware buffer. The system is
  really stuck. Only the keyboard backlight is still responsive.

  The only correlation I have noticed is that the system only hangs if
  WiFi is enabled. This morning I experienced two hangs in ten minutes
  necessitating reboots. Having disabled WiFi the system has been stable
  since ~1100 (~5 hours).

  Often, I see a iwlwifi hardware reset in the logs before the system
  dies:

  /var/log/syslog:Oct 30 11:49:30 fry kernel: [ 6529.550751] iwlwifi
  :02:00.0: Microcode SW error detected.  Restarting 0x8200.

  (apport has hopefully uploaded the full log, please lmk if not).
  Sometimes the message doesn't make it into the logs, and ext4
  truncates the file at the next mount.

  There seems to be no correlation with any messages immediately before
  the wifi chip dies. It doesn't seem to matter whether I'm at home or
  at work. I have wired ethernet at work simultaneously with wifi, but
  the wifi provides IPv6 so I would imagine most traffic uses wifi, so
  it's hard to say whether there's any effect of the traffic load on the
  probability of failure.

  Here is a sample of the firmware load:

  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.604743] iwlwifi 
:02:00.0: enabling device ( -> 0002)
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611790] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-33.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611930] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-32.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.620028] iwlwifi 
:02:00.0: loaded firmware version 31.532993.0 op_mode iwlmvm
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.650972] iwlwifi 
:02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208

  02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

  Any help appreciated.

  Thanks,
  Bruce

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Oct 30 16:15:43 2017
  DistUpgraded: 2017-10-15 14:47:25,517 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: kubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:807c]
  InstallationDate: Installed on 2016-09-09 (416 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP EliteBook 820 G3
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-15 (15 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.13
  dmi.board.name: 807C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.74
  dmi.chassis.asset.tag: 5CG6354JW5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.74:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 820 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

[Kernel-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

2018-04-05 Thread Daniel van Vugt
Found it. The fix is bluez commit
1873096352f518d3247f8efb3c2e0aa8804e50ac


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

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Triaged
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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


[Kernel-packages] [Bug 1761438] [NEW] linux: -proposed tracker

2018-04-05 Thread Kleber Sacilotto de Souza
Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

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

backports: bug 1761439 (linux-aws), bug 1761441 (linux-lts-xenial)
derivatives: bug 1761443 (linux-aws), bug 1761444 (linux-euclid), bug 1761445 
(linux-kvm), bug 1761446 (linux-raspi2), bug 1761448 (linux-snapdragon)

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.04.02-1 kernel-sru-master-kernel xenial

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   

[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

2018-04-05 Thread Sander
Confirmed, 4.4.0-119-generic #143 does not solve this problem, still a
hard freeze during boot. Adding "noibpb" to GRUB_CMDLINE_LINUX= in
/etc/default/grub allowed the machine to boot. Interestingly enough my
server is on VMware, so the problem exists there too

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1761456] Re: linux: -proposed tracker

2018-04-05 Thread Kleber Sacilotto de Souza
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 
1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem)
+ derivatives: bug 1761458 (linux-raspi2)

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

Title:
  linux:  -proposed tracker

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

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

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

  backports: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 
1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem)
  derivatives: bug 1761458 (linux-raspi2)

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

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


[Kernel-packages] [Bug 1760876] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel

2018-04-05 Thread Diego Germán Gonzalez
The problem is solved in my Ubuntu 18.04

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

Title:
  DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y,
  please install libelf-dev, libelf-devel or elfutils-libelf-devel

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Was installing the kernel 4.15.0-14-generic when that crash happened.
  Now libelf-dev is requested and need to be added as a dependency.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: fwts-efi-runtime-dkms 18.03.00-0ubuntu1
  Uname: Linux 4.16.0-041600-generic x86_64
  NonfreeKernelModules: r8168
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 15:39:06 2018
  PackageVersion: 18.03.00-0ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: fwts
  Title: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1751266] Re: Missing firmware in linux-image-4.15.0-10-generic

2018-04-05 Thread Thorsten
Linux 4.14 is getting rid of its in-kernel firmware/ tree.

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

So it will probably be like Debian that you can load missing firmware
during the installation

The GIT repo https://git.kernel.org/pub/scm/linux/kernel/git/firmware
/linux-firmware.git/

I've got the same problem with linux-image-generic-hwe-16.04-edge on
Xenial.

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

Title:
  Missing firmware in linux-image-4.15.0-10-generic

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  linux-image-4.15.0-10-generic doesn't have the firmware that linux-
  image-4.13.0-32-generic has. It doesn't have any of the files that are
  present in 4.13 in /lib/firmware/4.13.0-32-generic/.

  For me, this means i can boot 4.15, but my network wont work because
  of:

  kernel: [   13.468996] bnx2 :0b:00.0: Direct firmware load for 
bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2
  kernel: [   13.468998] bnx2: Can't load firmware file 
"bnx2/bnx2-mips-09-6.2.1b.fw"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 feb 23 13:12 seq
   crw-rw 1 root audio 116, 33 feb 23 13:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Feb 23 13:50:38 2018
  InstallationDate: Installed on 2018-02-14 (9 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180212)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: IBM System x3550 M3 -[7944S77]-
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=4a958e16-f948-4619-bad5-51d238213cc5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: IBM Corp.
  dmi.bios.version: -[D6E158AUS-1.16]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 00D4062
  dmi.board.vendor: IBM
  dmi.board.version: (none)
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: IBM
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnIBMCorp.:bvr-[D6E158AUS-1.16]-:bd11/26/2012:svnIBM:pnSystemx3550M3-[7944S77]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone:
  dmi.product.family: System x
  dmi.product.name: System x3550 M3 -[7944S77]-
  dmi.product.version: 00
  dmi.sys.vendor: IBM

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

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


[Kernel-packages] [Bug 1761468] Re: Debian-installer missing mmc bcm2835 module

2018-04-05 Thread Adam Smith
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Tags added: bionic

** Tags added: arm64

** Tags added: 18.04

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

Title:
  Debian-installer missing mmc bcm2835 module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Testing the latest arm64 18.04 mini ISO on a raspberry pi 3, I found
  the internal sd card reader was not recognised.  This is the main
  storage on a pi.  Manually extracting the mmc/host/bcm2835 module from
  the extras package and insmod'ing it got it working on the d-i
  installer.

  It would be great if the sd card could be recognised out of the box.
  I think all that is needed is to include the module in the block
  storage udeb.

  Note the pi has two SD controllers.  A second is used for the WiFi
  (but can also be used for the sd card reader).  That is also missing
  from the debian installer as far as I can tell.

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

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


[Kernel-packages] [Bug 1760876] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel

2018-04-05 Thread Kleber Sacilotto de Souza
** Also affects: linux (Ubuntu Bionic)
   Importance: High
 Assignee: Andy Whitcroft (apw)
   Status: Fix Committed

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

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

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

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

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

Title:
  DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y,
  please install libelf-dev, libelf-devel or elfutils-libelf-devel

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Was installing the kernel 4.15.0-14-generic when that crash happened.
  Now libelf-dev is requested and need to be added as a dependency.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: fwts-efi-runtime-dkms 18.03.00-0ubuntu1
  Uname: Linux 4.16.0-041600-generic x86_64
  NonfreeKernelModules: r8168
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 15:39:06 2018
  PackageVersion: 18.03.00-0ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: fwts
  Title: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1739665] Re: [FFE][Feature] KVM CLX avx512_vnni

2018-04-05 Thread ChristianEhrhardt
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3225

Regression test against ppa was ok tonighz, but I need to respin to add
more things before pushing to Bionic.

If you want to pre-test feel free to use this PPA.
Given the change thou I assume we can just let it roll in (under usual 
regression checks being ok)

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

Title:
  [FFE][Feature] KVM CLX avx512_vnni

Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Triaged
Status in xen package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in qemu source package in Bionic:
  Triaged
Status in xen source package in Bionic:
  New

Bug description:
  This feature has been released in ICX platform and the definition of 
AVX512_VNNI as below
   AVX512_VNNI Vector Nerual Network Instructions, an addition to AVX512. 
cpuid.(7,0). ECX[11]

  This is a new instruction to support machine learning. This
  instructions is pure HW features, currently, there is no test cases
  for this new instruction, we only check CPUID info by cpuid tool.

  Target Kernel: 4.16
  Target Qemu: 2.12
  Target Release: 18.04

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

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


[Kernel-packages] [Bug 1760876] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel

2018-04-05 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Trusty)
   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/1760876

Title:
  DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y,
  please install libelf-dev, libelf-devel or elfutils-libelf-devel

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Was installing the kernel 4.15.0-14-generic when that crash happened.
  Now libelf-dev is requested and need to be added as a dependency.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: fwts-efi-runtime-dkms 18.03.00-0ubuntu1
  Uname: Linux 4.16.0-041600-generic x86_64
  NonfreeKernelModules: r8168
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 15:39:06 2018
  PackageVersion: 18.03.00-0ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: fwts
  Title: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1761438] Re: linux: -proposed tracker

2018-04-05 Thread Kleber Sacilotto de Souza
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: bug 1761439 (linux-aws), bug 1761441 (linux-lts-xenial)
+ derivatives: bug 1761443 (linux-aws), bug 1761444 (linux-euclid), bug 1761445 
(linux-kvm), bug 1761446 (linux-raspi2), bug 1761448 (linux-snapdragon)

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1761439 (linux-aws), bug 1761441 (linux-lts-xenial)
  derivatives: bug 1761443 (linux-aws), bug 1761444 (linux-euclid), bug 1761445 
(linux-kvm), bug 1761446 (linux-raspi2), bug 1761448 (linux-snapdragon)

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

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


[Kernel-packages] [Bug 1758856] Re: retpoline hints: primary infrastructure and initial hints

2018-04-05 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Trusty)
   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/1758856

Title:
  retpoline hints: primary infrastructure and initial hints

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Tracking bug for the application of the retpoline hint tracking
  support.

  We are having terrible trouble with hints changing on every build.
  Upstream is moving to hinting those indirections which have been
  reviewed and are good.  This includes direct hinting of PVOPS and the
  like which are the ones which change all the time as new ones appear
  and dissappear.

  Backport the hint support and add our own bespoke checkers against
  this data.

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

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


[Kernel-packages] [Bug 1761433] [NEW] linux-lts-trusty: -proposed tracker

2018-04-05 Thread Kleber Sacilotto de Souza
Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1761430

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Precise)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1761430 kernel-sru-cycle-2018.04.02-1 precise

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Also affects: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Tags added: precise

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Confirmed

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) 

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

2018-04-05 Thread bugproxy
--- Comment From pavra...@in.ibm.com 2018-04-05 07:34 EDT---
Issue is resolved in 4.15.0-15-generic kernel.

root@ltc-wspoon4:~# ppc64_cpu --smt
SMT is off

Starting Kernel crash dump capture service...
[   11.747657] kdump-tools[952]: Starting kdump-tools:  * running makedumpfile 
-c -d 31 /proc/vmcore /var/crash/201804050626/dump-incomplete
Copying data  : [100.0 %] \   eta: 
0s
[   27.390223] kdump-tools[952]: The kernel version is not supported.
[   27.390438] kdump-tools[952]: The makedumpfile operation may be incomplete.
[   27.390563] kdump-tools[952]: The dumpfile is saved to 
/var/crash/201804050626/dump-incomplete.
[   27.390726] kdump-tools[952]: makedumpfile Completed.
[   27.405543] kdump-tools[952]:  * kdump-tools: saved vmcore in 
/var/crash/201804050626
[   30.762418] kdump-tools[952]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201804050626/dmesg.201804050626
[   30.802776] kdump-tools[952]: The kernel version is not supported.
[   30.802923] kdump-tools[952]: The makedumpfile operation may be incomplete.
[   30.803025] kdump-tools[952]: The dmesg log is saved to 
/var/crash/201804050626/dmesg.201804050626.
[   30.803145] kdump-tools[952]: makedumpfile Completed.
[   30.803263] kdump-tools[952]:  * kdump-tools: saved dmesg content in 
/var/crash/201804050626
[   30.888353] kdump-tools[952]: Thu, 05 Apr 2018 06:26:24 -0500
[   31.035631] kdump-tools[952]: Rebooting.
[   31.126613] reboot: Restarting system
[ 1577.265030518,5] OPAL: Reboot request...

root@ltc-wspoon4:~# ppc64_cpu --smt
SMT=2

Starting Kernel crash dump capture service...
[   13.378626] kdump-tools[952]: Starting kdump-tools:  * running makedumpfile 
-c -d 31 /proc/vmcore /var/crash/201804050631/dump-incomplete
Copying data  : [100.0 %] |   eta: 
0s
[   27.102530] kdump-tools[952]: The kernel version is not supported.
[   27.102659] kdump-tools[952]: The makedumpfile operation may be incomplete.
[   27.102787] kdump-tools[952]: The dumpfile is saved to 
/var/crash/201804050631/dump-incomplete.
[   27.102910] kdump-tools[952]: makedumpfile Completed.
[   27.112064] kdump-tools[952]:  * kdump-tools: saved vmcore in 
/var/crash/201804050631
[   29.632162] kdump-tools[952]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201804050631/dmesg.201804050631
[   29.672730] kdump-tools[952]: The kernel version is not supported.
[   29.672890] kdump-tools[952]: The makedumpfile operation may be incomplete.
[   29.672997] kdump-tools[952]: The dmesg log is saved to 
/var/crash/201804050631/dmesg.201804050631.
[   29.673111] kdump-tools[952]: makedumpfile Completed.
[   29.673249] kdump-tools[952]:  * kdump-tools: saved dmesg content in 
/var/crash/201804050631
[   29.774672] kdump-tools[952]: Thu, 05 Apr 2018 06:31:40 -0500
[   29.913780] kdump-tools[952]: Rebooting.

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

Title:
  Ubuntu 18.04 [ WSP DD2.2 with stop4 and stop5 enabled ]: kdump fails
  to capture dump when smt=2 or off.

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

Bug description:
  ---Problem Description---

  Ubuntu 18.04 [ WSP DD2.2 with stop4 and stop5 enabled ]: kdump fails
  to capture dump when smt=2 or off.

  ---Environment--
  Kernel Build:  4.15.0-13-generic
  System Name :  ltc-wspoon4
  Model/Type  :  P9
  Platform:  BML

  ---Steps to reproduce--

  1. Configure kdump.
  2. Set smt=off
  # ppc64_cpu --smt=off
  3. trigger crash.
  echo 1 > /proc/sys/kernel/sysrq
  echo "c" > /proc/sysrq-trigger

  ---Logs

  root@ltc-wspoon4:~# dpkg -l|grep kexec
  ii  kexec-tools 1:2.0.16-1ubuntu1 
ppc64el  tools to support fast kexec reboots
  root@ltc-wspoon4:~# makedumpfile -v
  makedumpfile: version 1.6.3 (released on 29 Jun 2018)
  lzo   enabled
  snappydisabled

  
  [  285.519832] [c01fe2d83de0] [c03d1898] SyS_write+0x68/0x110
  [  285.519926] [c01fe2d83e30] [c000b184] system_call+0x58/0x6c
  [  285.520007] Instruction dump:
  [  285.520053] 4bfff9f1 4bfffe50 3c4c00f0 3842e800 7c0802a6 6000 3921 
3d42001c 
  [  285.520158] 394a6db0 912a 7c0004ac 3940 <992a> 4e800020 
3c4c00f0 3842e7d0 
  [  285.520261] ---[ end trace 90a666dc7ca6f0ec ]---
  [  286.525787] 
  [  286.525883] Sending IPI to other CPUs
  [  28[  401.296284048,5] OPAL: Switch to big-endian OS
  [  402.297026662,3] OPAL: CPU 0x1 not in OPAL !
  6.851284] IPI complete
  [  403.455520784,3] OPAL: CPU 0x1 not in OPAL !nce.
  [  403.455569636,5] OPAL: Switch to little-endian OS
  [  404.455711332,3] OPAL: CPU 0x1 not in OPAL !
  [  404.470276386,3] PHB#[0:0]: CRESET: Unexpected slot state 

[Kernel-packages] [Bug 1740666] Re: systemd-timesyncd doesn't sync time after resume from hibernate

2018-04-05 Thread Pavel
#1744988 bug not resolved this for me.

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

Title:
  systemd-timesyncd doesn't sync time after resume from hibernate

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When resuming, the clock remains at the time when the hibernate
  happened, even if timedatectl claims that it is being synced:

  $ timedatectl status
Local time: Вс 2017-12-31 13:46:16 +05
Universal time: Вс 2017-12-31 08:46:16 UTC
  RTC time: Вс 2017-12-31 08:46:16
 Time zone: Asia/Yekaterinburg (+05, +0500)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  I've tried waiting a bit, but this persisted for some minutes, so I
  forced an update with

  systemctl restart systemd-timesyncd.service

  And afterwards the time was (apparently) correctly synced.

  Please, let me know what further informations are needed to debug the
  issue, and I would be happy to do some other test.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Dec 31 13:41:51 2017
  InstallationDate: Installed on 2017-06-05 (208 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 
zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago)
  dmi.bios.date: 06/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1761445] [NEW] linux-kvm: -proposed tracker

2018-04-05 Thread Kleber Sacilotto de Souza
Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1761438

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-kvm (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-kvm (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.04.02-1 kernel-sru-derivative-of-1761438 xenial

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: 

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

2018-04-05 Thread 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 1761468

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

Title:
  Debian-installer missing mmc bcm2835 module

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Testing the latest arm64 18.04 mini ISO on a raspberry pi 3, I found
  the internal sd card reader was not recognised.  This is the main
  storage on a pi.  Manually extracting the mmc/host/bcm2835 module from
  the extras package and insmod'ing it got it working on the d-i
  installer.

  It would be great if the sd card could be recognised out of the box.
  I think all that is needed is to include the module in the block
  storage udeb.

  Note the pi has two SD controllers.  A second is used for the WiFi
  (but can also be used for the sd card reader).  That is also missing
  from the debian installer as far as I can tell.

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

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


[Kernel-packages] [Bug 1761468] Re: Debian-installer missing mmc bcm2835 module

2018-04-05 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Debian-installer missing mmc bcm2835 module

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Testing the latest arm64 18.04 mini ISO on a raspberry pi 3, I found
  the internal sd card reader was not recognised.  This is the main
  storage on a pi.  Manually extracting the mmc/host/bcm2835 module from
  the extras package and insmod'ing it got it working on the d-i
  installer.

  It would be great if the sd card could be recognised out of the box.
  I think all that is needed is to include the module in the block
  storage udeb.

  Note the pi has two SD controllers.  A second is used for the WiFi
  (but can also be used for the sd card reader).  That is also missing
  from the debian installer as far as I can tell.

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

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


[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

2018-04-05 Thread Ivan Ivanov
Thanks broadmind (gustavo-vegas).
I also have a same problem lockup during boot with newly installed updates 
today (4/4/2018). The kernel version is 4.4.0-119-generic #143. I also tried to 
boot with an older one (4.4.0-116 perhaps)to no avail. I can only boot in 
upstart mode on these kernels, also there were no problems when loading 
4.4.0-112.
Adding "noibpb" to GRUB_CMDLINE_LINUX= in /etc/default/grub allowed the machine 
to boot fully without problems.

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

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1761443] [NEW] linux-aws: -proposed tracker

2018-04-05 Thread Kleber Sacilotto de Souza
Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1761438

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-aws (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.04.02-1 kernel-sru-derivative-of-1761438 xenial

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided 

[Kernel-packages] [Bug 1761439] [NEW] linux-aws: -proposed tracker

2018-04-05 Thread Kleber Sacilotto de Souza
Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1761438

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-aws (Ubuntu Trusty)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1761438 kernel-sru-cycle-2018.04.02-1 trusty

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: trusty

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: 

[Kernel-packages] [Bug 1605843] Re: Kernel crashes from time to time when using ftrace

2018-04-05 Thread Andy Whitcroft
This commit was applied in Ubuntu-4.4.0-67.88.  Closing this out.

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

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

Title:
  Kernel crashes from time to time when using ftrace

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  While performing some tracing suing ftrace-cmd I came across the
  following OOPS:

  [  333.051723] invalid opcode:  [#1] SMP 
  [  333.051742] Modules linked in: drbg ansi_cprng ctr ccm xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
arc4 bridge stp llc ebtable_filter ebtables ath9k_htc ath9k_common ath9k_hw ath 
mac80211 cfg80211 binfmt_misc snd_hda_codec_hdmi dcdbas dell_smm_hwmon 
snd_hda_codec_realtek snd_hda_codec_generic intel_rapl uvcvideo snd_hda_intel 
x86_pkg_temp_thermal intel_powerclamp coretemp videobuf2_vmalloc snd_hda_codec 
videobuf2_memops input_leds videobuf2_v4l2 snd_usb_audio crct10dif_pclmul 
videobuf2_core snd_hda_core v4l2_common crc32_pclmul snd_usbmidi_lib videodev 
snd_hwdep aesni_intel media snd_pcm aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw 
snd_seq snd_seq_device snd_timer lpc_ich snd ie31200_edac
  [  333.051972]  edac_core soundcore mei_me mei 8250_fintek mac_hid kvm_intel 
ip6t_REJECT nf_reject_ipv6 kvm nf_log_ipv6 irqbypass xt_hl ip6t_rt 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns 
nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack 
iptable_filter ip_tables parport_pc x_tables ppdev lp parport autofs4 hid_apple 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear 
dm_mirror dm_region_hash dm_log i915 i2c_algo_bit drm_kms_helper psmouse 
syscopyarea sysfillrect sysimgblt fb_sys_fops e1000e ahci libahci drm ptp
  [  333.052206]  pps_core fjes video
  [  333.052216] CPU: 1 PID: 5616 Comm: trace-cmd Not tainted 4.4.0-31-generic 
#50-Ubuntu
  [  333.052235] Hardware name: Dell Inc. Precision T1650/0X9M3X, BIOS A15 
09/09/2013
  [  333.052254] task: 8804066b1b80 ti: 88040b474000 task.ti: 
88040b474000
  [  333.052272] RIP: 0010:[]  [] 
ftrace_stub+0x0/0x8
  [  333.052296] RSP: 0018:88040b477f00  EFLAGS: 00010286
  [  333.052309] RAX:  RBX: 8800d9a4ec00 RCX: 
88040b477f18
  [  333.052326] RDX: 2000 RSI: 0237d690 RDI: 
8800d9a4ec00
  [  333.052343] RBP: 88040b477f48 R08: 7f89df102cf8 R09: 
0021
  [  333.052360] R10: 000d R11: 0246 R12: 
8800d9a4ec00
  [  333.052377] R13: 0237d690 R14: 2000 R15: 
0237d690
  [  333.052395] FS:  7f89df50f700() GS:88041e24() 
knlGS:
  [  333.052414] CS:  0010 DS:  ES:  CR0: 80050033
  [  333.052428] CR2: 00a78d88 CR3: 0003c3542000 CR4: 
001406e0
  [  333.052445] Stack:
  [  333.052451]  8120d165 8120df35 7fff364487e5 

  [  333.052473]  eee5d05c   
0006
  [  333.052494]  0008 2000 8182db32 
0004
  [  333.052515] Call Trace:
  [  333.052525]  [] ? vfs_read+0x5/0x130
  [  333.052538]  [] ? SyS_read+0x55/0xc0
  [  333.052553]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [  333.052568] Code: 8b 44 24 48 48 8b 7c 24 70 48 8b 74 24 68 48 8b 54 24 60 
48 8b 4c 24 58 48 8b 44 24 50 48 8b 6c 24 20 48 81 c4 d0 00 00 00 e9 fd  ff 
ff 80 00 00 00 00 9c 55 ff 74 24 18 55 48 89 e5 ff 74 24 
  [  333.052685] RIP  [] ftrace_stub+0x0/0x8
  [  333.052700]  RSP 

  
  All code
  
 0: 8b 44 24 48 mov0x48(%rsp),%eax
 4: 48 8b 7c 24 70  mov0x70(%rsp),%rdi
 9: 48 8b 74 24 68  mov0x68(%rsp),%rsi
 e: 48 8b 54 24 60  mov0x60(%rsp),%rdx
13: 48 8b 4c 24 58  mov0x58(%rsp),%rcx
18: 48 8b 44 24 50  mov0x50(%rsp),%rax
1d: 48 8b 6c 24 20  mov0x20(%rsp),%rbp
22: 48 81 c4 d0 00 00 00add$0xd0,%rsp
29:*e9 fd ff ff ff  jmpq   0x2b <-- trapping 
instruction
2e: 80 00 00addb   $0x0,(%rax)
31: 00 00   add%al,(%rax)
33: 9c  pushfq 
34: 55  push   %rbp
35: ff 74 24 18 pushq  0x18(%rsp)
39: 55  push   %rbp
3a: 48 89 e5mov%rsp,%rbp
3d: ff  .byte 0xff
3e: 74 24   je 

[Kernel-packages] [Bug 1757008] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’]

2018-04-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel
  module failed to build [error: implicit declaration of function
  ‘init_timer’]

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  The module fails to build, as it is missing the necessary patches for
  the latest HWE kernel.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-13-generic
  Date: Mon Mar 19 15:02:46 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-06-05 (287 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1761158] Re: linux: -proposed tracker

2018-04-05 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-release series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

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

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

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

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


[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

2018-04-05 Thread Martin
Dear Tyler, thank you for your efforts. Unfortunately it's the same with
me as with Lei: The new kernel freezes when waking up.  Cheers, Martin

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

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

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

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1761161] Re: linux-aws: -proposed tracker

2018-04-05 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-release series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Invalid

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

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

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

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


[Kernel-packages] [Bug 1761177] Re: linux: 4.15.0-15.16 -proposed tracker

2018-04-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1761184 (linux-hwe-edge)
  derivatives: bug 1761178 (linux-raspi2), bug 1761179 (linux-aws), bug 1761181 
(linux-azure), bug 1761182 (linux-gcp), bug 1761183 (linux-kvm)
- kernel-phase:Uploaded
- kernel-phase-changed:Wednesday, 04. April 2018 14:31 UTC
- 
  -- swm properties --
  phase: Uploaded
+ kernel-phase:Promoted to proposed
+ kernel-phase-changed:Thursday, 05. April 2018 08:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1761184 (linux-hwe-edge)
  derivatives: bug 1761178 (linux-raspi2), bug 1761179 (linux-aws), bug 1761181 
(linux-azure), bug 1761182 (linux-gcp), bug 1761183 (linux-kvm)
  -- swm properties --
- phase: Uploaded
- kernel-phase:Promoted to proposed
- kernel-phase-changed:Thursday, 05. April 2018 08:31 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.15.0-15.16 -proposed tracker

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

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

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

  backports: bug 1761184 (linux-hwe-edge)
  derivatives: bug 1761178 (linux-raspi2), bug 1761179 (linux-aws), bug 1761181 
(linux-azure), bug 1761182 (linux-gcp), bug 1761183 (linux-kvm)
  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-04-05 Thread Claus Stovgaard
I can confirm the suspicion for this issue to relate to Meltdown/Spectre
patching.

Running an Ubuntu 16.04 desktop in a virtual machine (VMware Workstation 
12.5.9) on top of Windows 7.
The hardware is a Dell T1700 with an i7-4770, and it seems the issue arose 
after BIOS and Microcode update.

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress
Status in linux-aws source package in Xenial:
  In Progress

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1746806/+subscriptions

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


[Kernel-packages] [Bug 1761164] Re: linux-kvm: -proposed tracker

2018-04-05 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-release series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Invalid

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

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

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

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


[Kernel-packages] [Bug 1761159] Re: linux: -proposed tracker

2018-04-05 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-release series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

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

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

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

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


[Kernel-packages] [Bug 1758856] Re: retpoline hints: primary infrastructure and initial hints

2018-04-05 Thread 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/1758856

Title:
  retpoline hints: primary infrastructure and initial hints

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  New
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Tracking bug for the application of the retpoline hint tracking
  support.

  We are having terrible trouble with hints changing on every build.
  Upstream is moving to hinting those indirections which have been
  reviewed and are good.  This includes direct hinting of PVOPS and the
  like which are the ones which change all the time as new ones appear
  and dissappear.

  Backport the hint support and add our own bespoke checkers against
  this data.

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

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


[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

2018-04-05 Thread ChristianEhrhardt
Regression tests good as well, moving it to x-unapproved for the SRU Team to 
consider.
=> qemu_2.5+dfsg-5ubuntu10.25_source.changes

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

** Changed in: qemu (Ubuntu)
   Status: New => Fix Released

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

Title:
  ubuntu-kvm-unit test failed with emulator test on ppc64le

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

Bug description:
  [Impact]

   * on start of qemu-system-ppc64 MSR_SF is not set correctly
     So it doesn't start 64bit as it should

   * Todays guests usually work around this and are fine, but it is
     incorrect and might be an issue down the road. Furthermore this is also
     a fixup to some verification tests at the same time.

  [Test Case]

   * 1. deploy xenial + HWE kernel on a ppc64el box
     2. sudo apt-get install qemu-kvm -y
     3. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
     4. cd kvm-unit-tests
     5. ./configure --endian=little; make
     6. sudo ppc64_cpu --smt=off
     7. sudo ./run_tests.sh -v

  [Regression Potential]

   * The changes are ppc only and provided by IBM so the potential risk is
     retained to the owner of the Area.
     Further the change is very small, so it has a very low amount of being
     misunderstood.

  [Other Info]

   * n/a

  ---

  Similar to bug 1723904, bug 1712803.
  The failed "emulator" test from kvm-unit-test will pass with qemu-2.7.1 built 
from source.

  ubuntu@modoc:~/kvm-unit-tests$ sudo /bin/bash -c "TESTNAME=emulator 
TIMEOUT=90s ACCEL= ./powerpc/run powerpc/emulator.elf -smp 1
  > "
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults 
-machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial 
stdio -kernel powerpc/emulator.elf -smp 1 # -initrd /tmp/tmp.BJ2sE7V2Jc
  FAIL: emulator: 64bit: detected
  PASS: emulator: invalid: exception
  PASS: emulator: lswx: alignment
  PASS: emulator: lswi: alignment
  SUMMARY: 4 tests, 1 unexpected failures

  EXIT: STATUS=3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1
  ProcVersionSignature: User Name 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: ppc64el
  Date: Mon Oct 16 10:10:46 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.00 0.00 0.57 1/1457 83356
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1604 00:14:19651 0 EOF
   2: POSIX  ADVISORY  WRITE 2937 00:14:55331 0 EOF
   3: FLOCK  ADVISORY  WRITE 3046 00:14:67623 0 EOF
   4: POSIX  ADVISORY  WRITE 3124 00:14:57398 0 EOF
   5: POSIX  ADVISORY  WRITE 3047 00:14:87068 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.10.0-37-generic (buildd@bos01-ppc64el-026) (gcc 
version 5.4.0 20160609 (User Name/IBM 5.4.0-6ubuntu1~16.04.4) ) 
#41~16.04.1-User Name SMP Fri Oct 6 22:44:24 UTC 2017
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT is off

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

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


[Kernel-packages] [Bug 1761379] Re: File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu 17.10 and above

2018-04-05 Thread Frank Heimes
This probably affects one of the packages linux-tools-* that I can't mark, 
hence using linux (kernel) for now.
It looks to me that we don't ship "libperf-jvmti.so" with any package (and 
never have been).
But letting the kernel-team leave a comment on this ...

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

** Summary changed:

- File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu 17.10 
and above
+ File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu 17.10 
and 18.04

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
  17.10 and 18.04

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

Bug description:
  ---Problem Description---
  File libperf-jvmti.so is missing in linux-tools-common deb making it 
impossible to use perf for the JVM JITed methods
   
  ---uname output---
  inux-image-4.13.0-36-generic
   
  Machine Type = not relevant 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   File libperf-jvmti.so is missing in linux-tools-common deb provided for 
Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also 
checked if the file is available on launchpad 
(https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) 
at it's also absent there:

  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm
  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm

  I do see the file in tools/perf/jvmti dir in the source .tar.gz, but
  apparently it's no being packaged in any .deb file?

  Thanks. 
   

   
  Userspace tool common name: perf 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace tool obtained from project website:  na

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

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


[Kernel-packages] [Bug 1757166] Re: linux-aws: 4.15.0-1002.2 -proposed tracker

2018-04-05 Thread Andy Whitcroft
** Tags removed: kernel-sru-cycle-devel-2018.03.16-1
** Tags added: kernel-sru-cycle-d2018.03.16-1

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

Title:
  linux-aws: 4.15.0-1002.2 -proposed tracker

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

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

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

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

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


[Kernel-packages] [Bug 1761379] [NEW] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu 17.10 and above

2018-04-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

---Problem Description---
File libperf-jvmti.so is missing in linux-tools-common deb making it impossible 
to use perf for the JVM JITed methods
 
---uname output---
inux-image-4.13.0-36-generic
 
Machine Type = not relevant 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 
17.10 making it impossible to use perf for the JVM JITed methods. I also 
checked if the file is available on launchpad 
(https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) 
at it's also absent there:

gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb 
| fgrep jvm
gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm

I do see the file in tools/perf/jvmti dir in the source .tar.gz, but
apparently it's no being packaged in any .deb file?

Thanks. 
 

 
Userspace tool common name: perf 
 
The userspace tool has the following bit modes: 64-bit 

Userspace tool obtained from project website:  na

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


** Tags: architecture-ppc64le bugnameltc-166440 severity-medium 
targetmilestone-inin1804
-- 
File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu 17.10 and 
above
https://bugs.launchpad.net/bugs/1761379
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le

2018-04-05 Thread ChristianEhrhardt
Regression tests good as well, moving it to x-unapproved for the SRU Team to 
consider.
=> qemu_2.5+dfsg-5ubuntu10.25_source.changes

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

Title:
  ubuntu-kvm-unit test failed with sprs test on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in qemu source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * Certain Guest features (SPRS) of power8 isa are not working

   * This is part of the ongoing LTS HW exploitation and a fixup to some
     verification tests at the same time.

  [Test Case]

   * 1. deploy xenial + HWE kernel on a ppc64el box
     2. sudo apt-get install qemu-kvm -y
     3. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
     4. cd kvm-unit-tests
     5. ./configure --endian=little; make
     6. sudo ppc64_cpu --smt=off
     7. sudo ./run_tests.sh -v

  [Regression Potential]

   * The changes are ppc only and provided by IBM so the potential risk is
     retained to the owner of the Area.
     Further if these registers are not used they do nothing, so in most
     cases it will be a nop.
     OTOH the changes are rather huge (in terms of LOC) so there is some
     risk left.

  [Other Info]

   * n/a

  ---

  The sprs test has failed on ppc64le
  This issue can be spotted on Zesty and Xenial. There is no history for this 
test on Artful

  $ sudo /bin/bash -c "MIGRATION=yes TESTNAME=sprs TIMEOUT=90s ACCEL= 
./powerpc/run powerpc/sprs.elf -smp 1 -append '-w'"
  run_migration timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 
-nodefaults -machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none 
-serial stdio -kernel powerpc/sprs.elf -smp 1 -append -w # -initrd 
/tmp/tmp.RUTL6E2JSi
  Settings SPRs to 0xcafefacec0debabe...
  Now migrate the VM, then press a key or send NMI...
  Checking SPRs...
  PASS: SPR 3:  0x00debabe <==> 0x00debabe
  PASS: SPR 13: 0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 17: 0x00debabe <==> 0x00debabe
  PASS: SPR 18: 0xc0debabe <==> 0xc0debabe
  PASS: SPR 19: 0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 29: 0xcafefacec0debabe <==> 0xcafefacec0debabe
  FAIL: SPR 61: 0x4054504440541014 <==> 00
  PASS: SPR 153:0x0a84 <==> 0x0a84
  PASS: SPR 157:0xcfcfc0cf <==> 0xcfcfc0cf
  FAIL: SPR 159:0xc0debabe <==> 00
  PASS: SPR 256:0xc0debabe <==> 0xc0debabe
  PASS: SPR 259:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 274:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 275:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 769:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 770:0xcafefacec006babe <==> 0xcafefacec006babe
  PASS: SPR 771:0xc0debabe <==> 0xc0debabe
  PASS: SPR 772:0xc0debabe <==> 0xc0debabe
  PASS: SPR 773:0xc0debabe <==> 0xc0debabe
  PASS: SPR 774:0xc0debabe <==> 0xc0debabe
  PASS: SPR 775:0xc0debabe <==> 0xc0debabe
  PASS: SPR 776:0xc0debabe <==> 0xc0debabe
  PASS: SPR 779:0xfa8b1afe <==> 0xfa8b1afe
  PASS: SPR 780:0xcafefacec0debabc <==> 0xcafefacec0debabc
  PASS: SPR 781:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 782:0xcafefacec0debabe <==> 0xcafefacec0debabe
  FAIL: SPR 784:0xcafefacec0debabe <==> 00
  PASS: SPR 785:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 786:0xcafefacec006babe <==> 0xcafefacec006babe
  PASS: SPR 787:0xc0debabe <==> 0xc0debabe
  PASS: SPR 788:0xc0debabe <==> 0xc0debabe
  PASS: SPR 789:0xc0debabe <==> 0xc0debabe
  PASS: SPR 790:0xc0debabe <==> 0xc0debabe
  PASS: SPR 791:0xc0debabe <==> 0xc0debabe
  PASS: SPR 792:0xc0debabe <==> 0xc0debabe
  PASS: SPR 795:0xfa8b1afe <==> 0xfa8b1afe
  PASS: SPR 796:0xcafefacec0debabc <==> 0xcafefacec0debabc
  PASS: SPR 797:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 798:0xcafefacec0debabe <==> 0xcafefacec0debabe
  PASS: SPR 800:0x8000c000 <==> 0x8000c000
  PASS: SPR 801:0x8000 <==> 0x8000
  PASS: SPR 802:0x8000c000 <==> 0x8000c000
  PASS: SPR 803:0x8000 <==> 0x8000
  PASS: SPR 

[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

2018-04-05 Thread Tyler Hicks
Thanks for giving it a try. I'm disappointed that it didn't fix the
issue for you.

I'd appreciate it if at least one more affected user could give the test
kernel a shot to help rule out the chance of multiple bugs being
involved.

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

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

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

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-04-05 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Artful)
   Status: In Progress => Fix Committed

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

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in intel-microcode source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in intel-microcode source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in intel-microcode source package in Artful:
  Invalid
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Some systems experience kernel lockups after updating to the latest 
intel-microcode
 package or when receiving updated microcode from a BIOS update.

   * In many cases, the lockups occur before users can reach the login screen 
which makes
 it very difficult to debug/workaround.

  [Test Case]

   * The most reliable test case currently known is to install the sssd 
package. Lockups
 may occur during package installation (disable IBPB by writing 0 to
 /proc/sys/kernel/ibpb_enabled to prevent this from happening). A lockup 
will most
 likely occur just after booting the system up as the lock screen is 
displayed.

  [Regression Potential]

   * The fix is in the task switching code of the kernel so complexity of the 
change is
 relatively high.

  [Original Report]

  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
     https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
     
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
     sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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


[Kernel-packages] [Bug 1755509] Re: Xenial update to 4.4.115 stable release

2018-04-05 Thread 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/1755509

Title:
  Xenial update to 4.4.115 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree
     or a minimally backported form of that patch. The 4.4.115 upstream
     stable stable patch set is now available. It should be included
     in the Ubuntu kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.115 stable release shall be
     applied:

 * loop: fix concurrent lo_open/lo_release
 * bpf: fix branch pruning logic
 * x86: bpf_jit: small optimization in emit_bpf_tail_call()
 * bpf: fix bpf_tail_call() x64 JIT
 * bpf: introduce BPF_JIT_ALWAYS_ON config
 * bpf: arsh is not supported in 32 bit alu thus reject it
 * bpf: avoid false sharing of map refcount with max_entries
 * bpf: fix divides by zero
 * bpf: fix 32-bit divide by zero
 * bpf: reject stores into ctx via st and xadd
 * x86/pti: Make unpoison of pgd for trusted boot work for real
 * kaiser: fix intel_bts perf crashes
 * ALSA: seq: Make ioctls race-free
 * crypto: aesni - handle zero length dst buffer
 * crypto: af_alg - whitelist mask and type
 * power: reset: zx-reboot: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
 * gpio: iop: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
 * gpio: ath79: add missing MODULE_DESCRIPTION/LICENSE
 * mtd: nand: denali_pci: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
 * igb: Free IRQs when device is hotplugged
 * KVM: x86: emulator: Return to user-mode on L1 CPL=0 emulation failure
 * KVM: x86: Don't re-execute instruction when not passing CR2 value
 * KVM: X86: Fix operand/address-size during instruction decoding
 * KVM: x86: ioapic: Fix level-triggered EOI and IOAPIC reconfigure race
 * KVM: x86: ioapic: Clear Remote IRR when entry is switched to 
edge-triggered
 * KVM: x86: ioapic: Preserve read-only values in the redirection table
 * ACPI / bus: Leave modalias empty for devices which are not present
 * cpufreq: Add Loongson machine dependencies
 * bcache: check return value of register_shrinker
 * drm/amdgpu: Fix SDMA load/unload sequence on HWS disabled mode
 * drm/amdkfd: Fix SDMA ring buffer size calculation
 * drm/amdkfd: Fix SDMA oversubsription handling
 * openvswitch: fix the incorrect flow action alloc size
 * mac80211: fix the update of path metric for RANN frame
 * btrfs: fix deadlock when writing out space cache
 * KVM: VMX: Fix rflags cache during vCPU reset
 * xen-netfront: remove warning when unloading module
 * nfsd: CLOSE SHOULD return the invalid special stateid for NFSv4.x (x>0)
 * nfsd: Ensure we check stateid validity in the seqid operation checks
 * grace: replace BUG_ON by WARN_ONCE in exit_net hook
 * nfsd: check for use of the closed special stateid
 * lockd: fix "list_add double add" caused by legacy signal interface
 * hwmon: (pmbus) Use 64bit math for DIRECT format values
 * net: ethernet: xilinx: Mark XILINX_LL_TEMAC broken on 64-bit
 * quota: Check for register_shrinker() failure.
 * SUNRPC: Allow connect to return EHOSTUNREACH
 * kmemleak: add scheduling point to kmemleak_scan()
 * drm/omap: Fix error handling path in 'omap_dmm_probe()'
 * xfs: ubsan fixes
 * scsi: aacraid: Prevent crash in case of free interrupt during scsi EH 
path
 * scsi: ufs: ufshcd: fix potential NULL pointer dereference in 
ufshcd_config_vreg
 * media: usbtv: add a new usbid
 * usb: gadget: don't dereference g until after it has been null checked
 * staging: rtl8188eu: Fix incorrect response to SIOCGIWESSID
 * usb: option: Add support for FS040U modem
 * USB: serial: pl2303: new device id for Chilitag
 * USB: cdc-acm: Do not log urb submission errors on disconnect
 * CDC-ACM: apply quirk for card reader
 * USB: serial: io_edgeport: fix possible sleep-in-atomic
 * usbip: prevent bind loops on devices attached to vhci_hcd
 * usbip: list: don't list devices attached to vhci_hcd
 * USB: serial: simple: add Motorola Tetra driver
 * usb: f_fs: Prevent gadget unbind if it is already unbound
 * usb: uas: unconditionally bring back host after reset
 * selinux: general protection fault in sock_has_perm
 * serial: imx: Only wakeup via RTSDEN bit if the system has RTS/CTS
 * spi: imx: do not 

[Kernel-packages] [Bug 1756121] Re: Xenial update to 4.4.116 stable release

2018-04-05 Thread 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/1756121

Title:
  Xenial update to 4.4.116 stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree
 or a minimally backported form of that patch. The 4.4.116 upstream
 stable stable patch set is now available. It should be included
 in the Ubuntu kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.116 stable release shall be
 applied:

 * Linux 4.4.116
 * ftrace: Remove incorrect setting of glob search field
 * mn10300/misalignment: Use SIGSEGV SEGV_MAPERR to report a failed user 
copy
 * ovl: fix failure to fsync lower dir
 * ACPI: sbshc: remove raw pointer from printk() message
 * nvme: Fix managing degraded controllers
 * btrfs: Handle btrfs_set_extent_delalloc failure in fixup worker
 * pktcdvd: Fix pkt_setup_dev() error path
 * EDAC, octeon: Fix an uninitialized variable warning
 * xtensa: fix futex_atomic_cmpxchg_inatomic
 * alpha: fix reboot on Avanti platform
 * alpha: fix crash if pthread_create races with signal delivery
 * signal/sh: Ensure si_signo is initialized in do_divide_error
 * signal/openrisc: Fix do_unaligned_access to send the proper signal
 * Bluetooth: btusb: Restore QCA Rome suspend/resume fix with a "rewritten" 
version
 * Revert "Bluetooth: btusb: fix QCA Rome suspend/resume"
 * Bluetooth: btsdio: Do not bind to non-removable BCM43341
 * HID: quirks: Fix keyboard + touchpad on Toshiba Click Mini not working
 * kernel/async.c: revert "async: simplify lowest_in_progress()"
 * media: cxusb, dib0700: ignore XC2028_I2C_FLUSH
 * media: ts2020: avoid integer overflows on 32 bit machines
 * watchdog: imx2_wdt: restore previous timeout after suspend+resume
 * KVM: nVMX: Fix races when sending nested PI while dest enters/leaves L2
 * arm: KVM: Fix SMCCC handling of unimplemented SMC/HVC calls
 * crypto: caam - fix endless loop when DECO acquire fails
 * media: v4l2-compat-ioctl32.c: refactor compat ioctl32 logic
 * media: v4l2-compat-ioctl32.c: don't copy back the result for certain 
errors
 * media: v4l2-compat-ioctl32.c: drop pr_info for unknown buffer type
 * media: v4l2-compat-ioctl32.c: copy clip list in put_v4l2_window32
 * media: v4l2-compat-ioctl32: Copy v4l2_window->global_alpha
 * media: v4l2-compat-ioctl32.c: make ctrl_is_pointer work for subdevs
 * media: v4l2-compat-ioctl32.c: fix ctrl_is_pointer
 * media: v4l2-compat-ioctl32.c: copy m.userptr in put_v4l2_plane32
 * media: v4l2-compat-ioctl32.c: avoid sizeof(type)
 * media: v4l2-compat-ioctl32.c: move 'helper' functions to 
__get/put_v4l2_format32
 * media: v4l2-compat-ioctl32.c: fix the indentation
 * media: v4l2-compat-ioctl32.c: add missing VIDIOC_PREPARE_BUF
 * vb2: V4L2_BUF_FLAG_DONE is set after DQBUF
 * media: v4l2-ioctl.c: don't copy back the result for -ENOTTY
 * nsfs: mark dentry with DCACHE_RCUACCESS
 * crypto: poly1305 - remove ->setkey() method
 * crypto: cryptd - pass through absence of ->setkey()
 * crypto: hash - introduce crypto_hash_alg_has_setkey()
 * ahci: Add Intel Cannon Lake PCH-H PCI ID
 * ahci: Add PCI ids for Intel Bay Trail, Cherry Trail and Apollo Lake AHCI
 * ahci: Annotate PCI ids for mobile Intel chipsets as such
 * kernfs: fix regression in kernfs_fop_write caused by wrong type
 * NFS: reject request for id_legacy key without auxdata
 * NFS: commit direct writes even if they fail partially
 * NFS: Add a cond_resched() to nfs_commit_release_pages()
 * nfs/pnfs: fix nfs_direct_req ref leak when i/o falls back to the mds
 * ubi: block: Fix locking for idr_alloc/idr_remove
 * mtd: nand: sunxi: Fix ECC strength choice
 * mtd: nand: Fix nand_do_read_oob() return value
 * mtd: nand: brcmnand: Disable prefetch by default
 * mtd: cfi: convert inline functions to macros
 * media: dvb-usb-v2: lmedm04: move ts2020 attach to dm04_lme2510_tuner
 * media: dvb-usb-v2: lmedm04: Improve logic checking of warm start
 * dccp: CVE-2017-8824: use-after-free in DCCP code
 * sched/rt: Up the root domain ref count when passing it around via IPIs
 * sched/rt: Use container_of() to get root domain in 
rto_push_irq_work_func()
 * usb: gadget: uvc: Missing files for configfs interface
 * posix-timer: Properly 

[Kernel-packages] [Bug 1752655] Re: retpoline: ignore %cs:0xNNN constant indirections

2018-04-05 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  retpoline: ignore %cs:0xNNN constant indirections

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  These are paravirt style indirections and can be ignored.

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

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


[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-04-05 Thread Rob Johnson
I've tested Ty's 4.4 kernel from comment #78 and can confirm it has let me log 
in with an LDAP user.
Uname:
  Linux M3520 4.4.0-119-generic #143+lp1759920.1 SMP Wed Apr 4 21:32:55 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

version_signature:
  Ubuntu 4.4.0-119.143+lp1759920.1-generic 4.4.114

cmdline:
  BOOT_IMAGE=/vmlinuz-4.4.0-119-generic root=/dev/mapper/ubuntu--vg-root ro

dmesg:
microcode: CPU0 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU1 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU2 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU3 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU4 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU5 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU6 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU7 sig=0x906e9, pf=0x20, revision=0x84
microcode: Microcode Update Driver: v2.01 , Peter 
Oruba

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in intel-microcode source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in intel-microcode source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in intel-microcode source package in Artful:
  Invalid
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Some systems experience kernel lockups after updating to the latest 
intel-microcode
 package or when receiving updated microcode from a BIOS update.

   * In many cases, the lockups occur before users can reach the login screen 
which makes
 it very difficult to debug/workaround.

  [Test Case]

   * The most reliable test case currently known is to install the sssd 
package. Lockups
 may occur during package installation (disable IBPB by writing 0 to
 /proc/sys/kernel/ibpb_enabled to prevent this from happening). A lockup 
will most
 likely occur just after booting the system up as the lock screen is 
displayed.

  [Regression Potential]

   * The fix is in the task switching code of the kernel so complexity of the 
change is
 relatively high.

  [Original Report]

  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
     https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
     
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
     sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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


[Kernel-packages] [Bug 1758910] Re: Important Kernel fixes to be backported for Power9 (kvm)

2018-04-05 Thread bugproxy
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1804

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

Title:
  Important Kernel fixes to be backported for Power9 (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-03-26 
02:18:44 ==
  ---Problem Description---
  Important Kernel fixes to be backported for Power9 (kvm)
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-13-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Following upstream patches are need to be backported for Power9 KVM to 
function well.

  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=ff6781fd1bb404d8a551c02c35c70cec1da17ff1
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
  and
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=a5d4b5891c2f1f865a2def1eb0030f534e77ff86

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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


[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

2018-04-05 Thread Breno Leitão
Patch sent to the mailing list: https://lists.ozlabs.org/pipermail
/linuxppc-dev/2018-April/171510.html

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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


[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

2018-04-05 Thread Breno Leitão
Hi Tyler,

Yes, we need to backport this patchset to all the current supported
kernel. Since most of the supported kernel contains the whole RFI infra
structure, I do not expect it to be hard. If you need help, I can find
someone to help on the backport.

Regarding the problem you are facing, I talked to the powerpc maintainer
(Michael Ellerman) and he suggested squashing the warning using
something as the code below. He will be also sending the patch upstream.

```
diff --git a/arch/powerpc/kernel/setup_64.c b/arch/powerpc/kernel/setup_64.c
index 66f2b6299c40..44c30dd38067 100644
--- a/arch/powerpc/kernel/setup_64.c
+++ b/arch/powerpc/kernel/setup_64.c
@@ -880,7 +880,7 @@ void rfi_flush_enable(bool enable)
 rfi_flush = enable;
 }
 
-static void init_fallback_flush(void)
+static void __ref init_fallback_flush(void)
 {
 u64 l1d_size, limit;
 int cpu;

```

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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


[Kernel-packages] [Bug 1761438] Re: linux: 4.4.0-120.144 -proposed tracker

2018-04-05 Thread Kleber Sacilotto de Souza
** Summary changed:

- linux:  -proposed tracker
+ linux: 4.4.0-120.144 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

Title:
  linux: 4.4.0-120.144 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1761439 (linux-aws), bug 1761441 (linux-lts-xenial)
  derivatives: bug 1761443 (linux-aws), bug 1761444 (linux-euclid), bug 1761445 
(linux-kvm), bug 1761446 (linux-raspi2), bug 1761448 (linux-snapdragon)

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

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


[Kernel-packages] [Bug 1752655] Re: retpoline: ignore %cs:0xNNN constant indirections

2018-04-05 Thread Stefan Bader
** Changed in: linux (Ubuntu Artful)
   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/1752655

Title:
  retpoline: ignore %cs:0xNNN constant indirections

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  These are paravirt style indirections and can be ignored.

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

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


[Kernel-packages] [Bug 1761502] Re: i8042 generating thousands of spurious keypress interrupts

2018-04-05 Thread TJ
** Changed in: linux (Ubuntu)
   Status: New => Triaged

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => TJ (tj)

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

Title:
  i8042 generating thousands of spurious keypress interrupts

Status in linux package in Ubuntu:
  Triaged

Bug description:
  i8042 generating thousands of spurious keypress interrupts

  I am having an issue where the + key is repeating in all text fields
  when I am logged in and before logged in.  Seems to happen as soon as
  I get to any login screen command line or GUI too.  I don't think this
  happens before then but could be wrong.  This is annoying but seems to
  also have stopped a few times but will come back out of the blue.

  Beyond that, I have popped the key off and cleaned under there with no
  luck.  I have also used the mainline kernel and still having issues.

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

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


[Kernel-packages] [Bug 1751266] Re: Missing firmware in linux-image-4.15.0-10-generic

2018-04-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Missing firmware in linux-image-4.15.0-10-generic

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-firmware source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  linux-image-4.15.0-10-generic doesn't have the firmware that linux-
  image-4.13.0-32-generic has. It doesn't have any of the files that are
  present in 4.13 in /lib/firmware/4.13.0-32-generic/.

  For me, this means i can boot 4.15, but my network wont work because
  of:

  kernel: [   13.468996] bnx2 :0b:00.0: Direct firmware load for 
bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2
  kernel: [   13.468998] bnx2: Can't load firmware file 
"bnx2/bnx2-mips-09-6.2.1b.fw"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 feb 23 13:12 seq
   crw-rw 1 root audio 116, 33 feb 23 13:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Feb 23 13:50:38 2018
  InstallationDate: Installed on 2018-02-14 (9 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180212)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: IBM System x3550 M3 -[7944S77]-
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=4a958e16-f948-4619-bad5-51d238213cc5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: IBM Corp.
  dmi.bios.version: -[D6E158AUS-1.16]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 00D4062
  dmi.board.vendor: IBM
  dmi.board.version: (none)
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: IBM
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnIBMCorp.:bvr-[D6E158AUS-1.16]-:bd11/26/2012:svnIBM:pnSystemx3550M3-[7944S77]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone:
  dmi.product.family: System x
  dmi.product.name: System x3550 M3 -[7944S77]-
  dmi.product.version: 00
  dmi.sys.vendor: IBM

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

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


[Kernel-packages] [Bug 1761456] Re: linux: 4.13.0-39.44 -proposed tracker

2018-04-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 
1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem)
  derivatives: bug 1761458 (linux-raspi2)
+ kernel-stable-phase-changed:Thursday, 05. April 2018 14:32 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 
1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem)
  derivatives: bug 1761458 (linux-raspi2)
  kernel-stable-phase-changed:Thursday, 05. April 2018 14:32 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.13.0-39.44 -proposed tracker

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

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

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

  backports: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 
1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem)
  derivatives: bug 1761458 (linux-raspi2)
  kernel-stable-phase-changed:Thursday, 05. April 2018 14:32 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1761445] Re: linux-kvm: -proposed tracker

2018-04-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1761438
+ kernel-stable-phase-changed:Thursday, 05. April 2018 14:31 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1761438
- kernel-stable-phase-changed:Thursday, 05. April 2018 14:31 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1761438
  phase: Packaging

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

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


[Kernel-packages] [Bug 1761443] Re: linux-aws: -proposed tracker

2018-04-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1761438
+ kernel-stable-phase-changed:Thursday, 05. April 2018 14:31 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1761438
- kernel-stable-phase-changed:Thursday, 05. April 2018 14:31 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1761438
  phase: Packaging

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

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


[Kernel-packages] [Bug 1761456] Re: linux: 4.13.0-39.44 -proposed tracker

2018-04-05 Thread Stefan Bader
** Summary changed:

- linux:  -proposed tracker
+ linux: 4.13.0-39.44 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

Title:
  linux: 4.13.0-39.44 -proposed tracker

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

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

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

  backports: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 
1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem)
  derivatives: bug 1761458 (linux-raspi2)

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

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


[Kernel-packages] [Bug 1761502] [NEW] i8042 generating thousands of spurious keypress interrupts

2018-04-05 Thread Amelia Rose Khan
Public bug reported:

i8042 generating thousands of spurious keypress interrupts

I am having an issue where the + key is repeating in all text fields
when I am logged in and before logged in.  Seems to happen as soon as I
get to any login screen command line or GUI too.  I don't think this
happens before then but could be wrong.  This is annoying but seems to
also have stopped a few times but will come back out of the blue.

Beyond that, I have popped the key off and cleaned under there with no
luck.  I have also used the mainline kernel and still having issues.

** Affects: linux (Ubuntu)
 Importance: Low
 Assignee: TJ (tj)
 Status: Triaged

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

Title:
  i8042 generating thousands of spurious keypress interrupts

Status in linux package in Ubuntu:
  Triaged

Bug description:
  i8042 generating thousands of spurious keypress interrupts

  I am having an issue where the + key is repeating in all text fields
  when I am logged in and before logged in.  Seems to happen as soon as
  I get to any login screen command line or GUI too.  I don't think this
  happens before then but could be wrong.  This is annoying but seems to
  also have stopped a few times but will come back out of the blue.

  Beyond that, I have popped the key off and cleaned under there with no
  luck.  I have also used the mainline kernel and still having issues.

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

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


[Kernel-packages] [Bug 1759893] Re: [18.04][config] regression: nvme and nvme_core couldn't be built as modules starting 4.15-rc2

2018-04-05 Thread Seth Forshee
** Changed in: linux (Ubuntu Bionic)
   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/1759893

Title:
  [18.04][config] regression: nvme and nvme_core couldn't be built as
  modules starting 4.15-rc2

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

Bug description:
  Some regression was introduced into NVME-related kernel configuration
  by 32c662c58a9b9 into 4.15-rc2, which was pulled later into ubuntu-
  bionic.git

  In result, "nvme" and "nvme_core" drivers are built into the kernel,
  we can't build them as modules. It caused incompatibility of NMVe-OF
  target and initiator modules (nvmet, nvme-rdma) installed by Mellanox
  OFED with the inbox "nvme" driver.

  Root cause analysis.

  In the drivers/lightnvm/Kconfig file - kernel configuration for the 
OpenChannel SSDs (lightnvm) we have:
   
  menuconfig NVM
  bool "Open-Channel SSD target support"
  depends on BLOCK && HAS_DMA && PCI
  select BLK_DEV_NVME
  help
Say Y here to get to enable Open-channel SSDs.
  ...

  
  It means that BLK_DEV_NVME is selected to "y" when  NVM (CONFIG_NVM) is 
selected.
  NVM parameter is 2 state (on / off, i.e. "y" or "no"), it couldn't be built 
as a module.
  So that it triggers the change of BLK_DEV_NAME=y and NVME_CORE=y

  $ git blame drivers/lightnvm/Kconfig
   
  32c662c58a9b9 (Rakesh Pandit   2017-10-13 14:45:55 +0200  7)depends on 
BLOCK && HAS_DMA && PCI
  32c662c58a9b9 (Rakesh Pandit   2017-10-13 14:45:55 +0200  8)select 
BLK_DEV_NVME

  commit 32c662c58a9b9d0c99e713a14ca323a9a91c73a0
  Author: Rakesh Pandit 
  Date:   Fri Oct 13 14:45:55 2017 +0200

  lightnvm: include NVM Express driver if OCSSD is selected for
  build

  Because NVM needs BLK_DEV_NVME, select it automatically if we mark NVM
  in config file before building kernel.  Also append PCI to depends as
  select doesn't automatically add dependencies.

  Signed-off-by: Rakesh Pandit 
  Signed-off-by: Matias Bjørling 
  Signed-off-by: Jens Axboe 

   drivers/lightnvm/Kconfig | 3 ++-
   1 file changed, 2 insertions(+), 1 deletion(-)

  $ git diff 32c662c58a9b9^1..32c662c58a9b9
  diff --git a/drivers/lightnvm/Kconfig b/drivers/lightnvm/Kconfig
  index ead61a93cb4e..2a953efec4e1 100644
  --- a/drivers/lightnvm/Kconfig
  +++ b/drivers/lightnvm/Kconfig
  @@ -4,7 +4,8 @@

   menuconfig NVM
  bool "Open-Channel SSD target support"
  -   depends on BLOCK && HAS_DMA
  +   depends on BLOCK && HAS_DMA && PCI
  +   select BLK_DEV_NVME
  help
Say Y here to get to enable Open-channel SSDs.

  
  Proposed fix is following:

  diff --git a/drivers/lightnvm/Kconfig b/drivers/lightnvm/Kconfig
  index 2a953efec4e1..9969236314d7 100644
  --- a/drivers/lightnvm/Kconfig
  +++ b/drivers/lightnvm/Kconfig
  @@ -4,8 +4,7 @@

   menuconfig NVM
  bool "Open-Channel SSD target support"
  -   depends on BLOCK && HAS_DMA && PCI
  -   select BLK_DEV_NVME
  +   depends on BLOCK && HAS_DMA && PCI && BLK_DEV_NVME
  help
Say Y here to get to enable Open-channel SSDs.

  
  Regards, Yurii Shestakov
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 29 17:05 seq
   crw-rw 1 root audio 116, 33 Mar 29 17:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/mapper/vg2-swap_1
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/vg2-root ro net.ifnames=0 biosdevname=0 quiet nofb nomodeset 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Kernel-packages] [Bug 1737761] Re: zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2

2018-04-05 Thread Stefan Bader
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2

Status in linux package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Incomplete
Status in zfs-linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in zfs-linux source package in Artful:
  Fix Released

Bug description:
  == SRU Justification, Xenial, Artful ==

  Running ZFS userspace utils with newer 0.7.x ZFS kernel drivers breaks
  ZFS send/receive because of changes in the ioctl command structure.

  == Testcase ==

  ubuntu ADT ZFS tests autotests/client/tests/ubuntu-zfs-smoke-tests
  will show a failure in ZFS SEND, with userspace zfs tools segfaulting.

  == Fix ==

  Fix is to detect if ZFS kernel driver is version 0.7.x and copy the
  0.6.5.x zfs ioctl command structure to a ZFS 0.7.x version, call the
  ioctl() and then copy the result back.

  == Regression Potential ==

  This will only affect the ZFS ioctl interface and this can be fully
  tested using the ZFS autotests with 0.7.0 and 0.6.5.x ZFS enabled
  kernels to check for the compatibility change regressions.

  --

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/z/zfs-linux/20171212_032601_d0613@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/arm64/z/zfs-linux/20171212_020008_d0613@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/ppc64el/z/zfs-linux/20171212_024359_d0613@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/z/zfs-linux/20171212_032349_d0613@/log.gz

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

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


  1   2   >