[Kernel-packages] [Bug 1823320] Re: Asus Zenbook 14 UX433F - NumPad

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1810183
   numpad on touchpad doesn't work in ASUS Zenbook 14

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

Title:
  Asus Zenbook 14 UX433F - NumPad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just bought this amazing laptop, installed Linux Ubuntu 18.04 LTS,
  upgraded the kernel to v5.0.6 to get sound working.

  Everything is working except the new feature of the numpad keys within
  the touchpad.

  Discussion already opened in the past but never solved:
  https://unix.stackexchange.com/questions/494400/asus-zenbook-
  ux433-ux333-configure-touchpad-embedded-numpad-on-linux

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183

  Thanks for any hints

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

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

[Kernel-packages] [Bug 1829942] Re: Address performance issue w/ GICv4-based guests

[Terry Rudd]

Dann, is this still planned for Eoan?

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

Title:
  Address performance issue w/ GICv4-based guests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  In Progress

Bug description:
  [Impact]
  Performance is degraded when a guest is booted w/ vgic v4 support enabled. 

  [Test Case]
  I used a HiSilicon D06 system w/ an Intel 82599 10Gbps NIC. I passed through 
a VF to a guest, and ran "netperf -H " against a 10Gbps-capable target. 
With vgic v4 support, I'm only seeing 5-6Gbps. With vgic v3 support, this was 
in the 9Gbps spectrum. And, after applying the upstream fix, I'm also seeing 
>9Gbps w/ vgic v4 enabled.

  Note: to enable vgic v4 support, pass "kvm-arm.vgic_v4_enable=1" on
  the host kernel cmdline.

  [Fix]
  ca71228b42a96 arm64: KVM: Always set ICH_HCR_EL2.EN if GICv4 is enabled

  [Regression Risk]
  The fix is restricted to the ARM/KVM subsystem.

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

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

[Kernel-packages] [Bug 1824687] Re: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue

[Terry Rudd]

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

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

Title:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged

Bug description:
  [SRU Justification]

  == Impact ==

  Since 05c0b86b96 "ipv6: frags: rewrite ip6_expire_frag_queue()" the
  16.04/4.4 kernel crashes whenever that functions gets called (on busy
  systems this can be every 3-4 hours). While this potentially affects
  Cosmic and later, too, the fix differs on later kernels (Bionic is not
  yet affected as it does not yet carry updates to the frags handling).

  == Fix ==

  For Xenial and Cosmic, the proposed fix would be additional changes to 
ip6_expipre_frag_queue(), taken from follow-up changes to ip_expire().
  For Disco, I would hold back because we have a backlog of stable patches 
there and depending on what got backported to 5.0.y there would be a simpler 
fix.
  For current development kernels, one just needs to ensure that the following 
upstream change is included: 47d3d7fdb10a "ip6: fix skb leak in 
ip6frag_expire_frag_queue()".

  == Testcase ==

  Unfortunately this could not be re-created locally. But a test kernel
  which had the proposed fix applied was showing good testing (see
  comment #37 and #38).

  == Risk of Regression ==

  The modified function is only called in rare cases and the positive
  testing in production would cover this. So I would consider it low.

  ---

  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  After upgrading our server to this Kernel we experience frequent Kernel 
panics (Attachment).
  Every 3 hours.
  Our machine has a throuput of about 600 Mbits/s
  The Panics are around the area of ip6_expire_frag_queue.

    __pskb_pull_tail
    ip6_dst_lookup_tail
    _decode_session6
    __xfrm_decode_session
    icmpv6_route_lookup
    icmp6_send

  It seems similar to Bug Report in Debian.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922488

  According to the bug finder of above bug it also occurred after using a 
Kernel with the change of
  rewrite ip6_expire_frag_queue()

  Intermediate solution. We disabled IPv6 on this machine to avoid further 
Panics.
  Please let me know what information is missing. The ubuntu-bug linux was 
send. And I hope it is attached to this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-145-generic 4.4.0-145.171
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sun Apr 14 11:40:11 2019
  InstallationDate: Installed on 2018-03-18 (391 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to xenial on 2018-10-21 (174 days ago)
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 21:04 seq
   crw-rw 1 root audio 116, 33 Apr 12 21:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/tor3--vg-swap_1
  InstallationDate: Installed on 2018-03-18 (393 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-145-generic 
root=/dev/mapper/hostname--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-145-generic N/A
   linux-backports-modules-4.4.0-145-generic  N/A
   linux-firmware 1.157.21
  RfKill: Err

[Kernel-packages] [Bug 1824864] Re: CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64

[Terry Rudd]

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => 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/1824864

Title:
  CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * Too small dmsg kernel buf ring size leads to loosing/missing early
  boot kernel messages which happen before journald starts slurping them
  up and storing them on disc. This results in messages similar to this
  one on boot "missed NN kernel messages on boot". This is especially
  pronounced on arm64 as the default setting there is way lower than any
  other 32bit or 64bit architecture we ship. Also amd64 appears to have
  the highest setting of 18 among all architectures we ship. The best
  course of action to bump all 64bit arches to 18, and keep all 32bit
  arches at the current & upstream default of 17.

  [Test Case]

   * $ cat /boot/config-`uname -r` | grep CONFIG_LOG_BUF_SHIFT

  on 64bit arches result should be: CONFIG_LOG_BUF_SHIFT=18
  on 32bit arches result should be: CONFIG_LOG_BUF_SHIFT=17

   * run systemd adt test, the boot-and-services test case should not
  fail journald tests with "missed kernel messages" visible in the error
  logs.

  [Regression Potential]

   * Increasing the size of the log_buf, will increase kernel memory
  usage which cannot be reclaimed. It will now become 256kb on arm64,
  ppc64el, s390x instead of 8kB/128kb/128kb respectively. 32bit arches
  remain unchanged at 128kb.

  [Other Info]
   
   * Original bug report

  CONFIG_LOG_BUF_SHIFT
  policy<{
  'amd64'  : '18',
  'arm64'  : '14',
  'armhf'  : '17',
  'i386'   : '17',
  'ppc64el': '17',
  's390x'  : '17'}>

  Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.

  Potentially bump all 64-bit arches to 18 (or higher!) as was done on
  amd64, meaning set 18 on arm64 s390x ppc64el.

  I have a systemd autopkgtest test that asserts that we see Linux
  kernel command line in the dmesg (journalctl -k -b). And it is
  consistently failing on arm64 scalingstack KVM EFI machines with
  messages of "missing 81 kernel messages".

  config LOG_BUF_SHIFT
  int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
  range 12 25
  default 17
  depends on PRINTK
  help
    Select the minimal kernel log buffer size as a power of 2.
    The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
    parameter, see below. Any higher size also might be forced
    by "log_buf_len" boot parameter.

    Examples:
   17 => 128 KB
   16 => 64 KB
   15 => 32 KB
   14 => 16 KB
   13 =>  8 KB
   12 =>  4 KB

  14 sounds like redictiously low for arm64. given that 17 is default
  across 32-bit arches, and 18 is default on amd64.

  On a related note, we have CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT
policy<{'amd64': '13', 'arm64': '13', 'armhf': '13', 'i386': '13', 'ppc64el': 
'13', 's390x': '13'}>
  I'm not sure if we want to bump these up to LOG_BUF_SHIFT size or not.

  Please backport this to xenial and up.

  === systemd ===

  systemd, boot-and-services test case can bump the ring buffer before
  running the tests.

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

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

[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend

[Terry Rudd]

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

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

Title:
  Lid switch triggered suspend takes much longer than UI triggered
  suspend

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  IBM T460
  5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  
  When triggering a suspend even from the lid switch of my Lenovo T460 it takes 
30 seconds to reach suspend state. Several others with different models of 
Lenovo laptops have also reproduced this issue. 

  It seems this is isolated to the lid switch as UI triggered suspend
  (alt+power icon) is far faster.

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

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

[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.

[Terry Rudd]

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

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

Title:
  Azure Instance never recovered during series of instance reboots.

Status in linux-azure package in Ubuntu:
  Incomplete

Bug description:
  Description: During SRU Testing of various Azure Instances, there will
  be some cases where the instance will not respond following a system
  reboot.  SRU Testing only restarts a giving instance once, after it
  preps all of the necessary files to-be-tested.

  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  I initiated a series of tests which rebooted Azure Cloud instances 50
  times. During the 49th Reboot, an Instance failed to return from a
  reboot.. Upon grabbing the console output the following was seen
  scrolling endlessly. I have seen this failure in cases where the
  instance only restarted a handful of times >5

  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus

  In another test attempt I saw the following failure:

  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes

  
  Both of these failures broke networking, Both of these failures were seen at 
least twice to three times, thus may explain why in some cases we never recover 
from an instance reboot.

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

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

[Kernel-packages] [Bug 1840026] Re: Ubuntu 18.04.2: Unable to boot guest with scsi disk having sgio flag

[Terry Rudd]

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

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

Title:
  Ubuntu 18.04.2: Unable to boot guest with scsi disk having sgio flag

Status in The Ubuntu-power-systems project:
  Opinion
Status in libvirt package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  == Comment: #0 - SRIKANTH AITHAL  - 2019-07-03 
22:28:43 ==
  ---Problem Description---
  When we try to boot KVM guest with scsi disk having `sgio="unfiltered"`, 
guest fails to boot throwing below error

  virsh start vm1 --console
  error: Failed to start domain vm1
  error: Requested operation is not valid: unpriv_sgio is not supported by this 
kernel

   
  Contact Information = srikanth/bssrika...@in.ibm.com 
   
  ---uname output---
  Linux pkvmhab008 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:54:50 UTC 
2019 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = witherspoon 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Recreation steps:

  1. Using scsi_debug driver to simulate scsi disk

  #/sbin/modprobe scsi_debug dev_size_mb=2048 lbpu=1
  #lsscsi|grep scsi_debug|awk '{print $6}'
  /dev/sdk

  2. Using below disk xml,

  




  

  3. Try booting KVM guest with above disk,

  # virsh start vm1 --console
  error: Failed to start domain vm1
  error: Requested operation is not valid: unpriv_sgio is not supported by this 
kernel

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Location:
   There was no dump
   
  *Additional Instructions for srikanth/bssrika...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - SRIKANTH AITHAL  - 2019-07-03
  22:30:28 ==

  
  == Comment: #2 - SRIKANTH AITHAL  - 2019-07-03 
22:31:03 ==

  
  == Comment: #3 - SRIKANTH AITHAL  - 2019-07-03 
22:32:34 ==
  unpriv_sgio is required for KVM guest running as qemu   user to be able to 
configure to issue any SCSI commands to storages.

  == Comment: #5 - Fabiano Almeida Rosas  - 2019-07-25 
12:46:15 ==
  It seems libvirt added support to `unpriv_sgio` but the kernel side of the 
feature never got merged. It was then reverted on libvirt's side but the revert 
caused issues so they re-enabled the support. As far as I can tell it will 
always fail.

  Some iterations of the kernel side feature:
  https://lwn.net/Articles/533901/
  https://lwn.net/Articles/535075/
  https://lkml.org/lkml/2013/5/23/294 

  Libvirt side:
  https://www.redhat.com/archives/libvir-list/2013-January/msg00013.html

  Revert of the feature:
  
https://libvirt.org/git/?p=libvirt.git;a=patch;h=ce346623c19f82f4b35f3466e2ee4066847b750c

  Unrevert:
  https://www.redhat.com/archives/libvir-list/2015-June/msg00814.html

  
  @Srikanth
  Is this known to have worked at some point? Because it might be the case that 
the distro is carrying these patches downstream. If that is the case I would 
like to know which distro + version, so we can compare the setups.

  == Comment: #6 - SRIKANTH AITHAL  - 2019-07-25 
22:35:33 ==
  (In reply to comment #5)
  > It seems libvirt added support to `unpriv_sgio` but the kernel side of the
  > feature never got merged. It was then reverted on libvirt's side but the
  > revert caused issues so they re-enabled the support. As far as I can tell it
  > will always fail.
  > 
  > Some iterations of the kernel side feature:
  > https://lwn.net/Articles/533901/
  > https://lwn.net/Articles/535075/
  > https://lkml.org/lkml/2013/5/23/294 
  > 
  > Libvirt side:
  > https://www.redhat.com/archives/libvir-list/2013-January/msg00013.html
  > 
  > Revert of the feature:
  > https://libvirt.org/git/?p=libvirt.git;a=patch;
  > h=ce346623c19f82f4b35f3466e2ee4066847b750c
  > 
  > Unrevert:
  > https://www.redhat.com/archives/libvir-list/2015-June/msg00814.html
  > 
  > 
  > @Srikanth
  > Is this known to have worked at some point? Because it might be the case
  > that the distro is carrying these patches downstream. If that is the case I
  > would like to know which distro + version, so we can compare the setups.

  No, this was uncovered as part of adding new testcases to our existing
  test bucket. So we have not executed this testcase before.

  == Comment: #8 - Daniel Henrique Barboza  - 2019-08-07 
15:32:47 ==
  The error message  "unpriv_sgio is not supported by this kernel" comes from a 
Libvirt code that verifies if the file 'unpriv_sgio' exists in the sysfs path 
of the device. In case it doesn't, this error message is thrown.

  Fabiano is right in comment #5: the feature that implemented
  unpriv_sgio didn't make it upstream. However, I found out that the
  RHEL 7.4 manual [1] talks about the feature. With that in mind, I went
  to a RHEL 7.6 server and verified that the feature exists in its 3.10
  kernel by finding references of 'QUEUE_FLAG_UNPRIV_

Re: [Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID

[Terry Rudd]

Morning Joe,

On 5/14/19 8:40 AM, Joseph Salisbury wrote:
> @marcelo, we do want the changes requested in comment #5 in bug 1819689.
> We can wait for the results of Long Li's investigation before proceeding
> there.
> 
that is the revert in comment #6, right?

Terry

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

Title:
   [linux-azure] Storage performance drop on RAID

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  Fix Committed

Bug description:
  In Azure, FIO 4k tests are showing performance drops on latest proposed 
4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on 
both sequential and random read tests).
  The setup used is 12 disks in RAID0.
  The affected kernels are:
  Ubuntu 14.04 + 4.15.0-1043
  Ubuntu 16.04 + 4.15.0-1044

  Previous kernel versions had reached max IOPS, ~52K IOPS on both read
  tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the
  issue is in the diff from 1043 kernel on trusty vs 1044 kernel on
  xenial.

  The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the 
automation) is this:
  fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 
--overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 
--numjob=8 --output-format=json 
--output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro'

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

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

[Kernel-packages] [Bug 1816669] Re: AMD Rome : Minimal support patches

[Terry Rudd]

Per comment #17 Kim, can you please indicate exactly which kernel you
want these commits in?

Terry

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

Title:
  AMD Rome :  Minimal support patches

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  The following 3 patches need to be back ported to ubuntu 18.04.2(Linux
  4.18) to complete the minimal support for Rome :

  818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum
  e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register
  90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode

  --thanks
  --kim
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-02-28 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp33s0f0  no wireless extensions.
   
   lono wireless extensions.
   
   enp33s0f1  no wireless extensions.
  MachineType: AMD Corporation DAYTONA_X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: RDY0071B
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DAYTONA_X
  dmi.board.vendor: AMD Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 2
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: DAYTONA_X
  dmi.product.sku: Default string
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: AMD Corporation

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

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

[Kernel-packages] [Bug 1816669] Re: AMD Rome : Minimal support patches

[Terry Rudd]

Kim, this works is staged for the next SRU cycle.

Terry

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

Title:
  AMD Rome :  Minimal support patches

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  The following 3 patches need to be back ported to ubuntu 18.04.2(Linux
  4.18) to complete the minimal support for Rome :

  818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum
  e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register
  90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode

  --thanks
  --kim
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-02-28 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp33s0f0  no wireless extensions.
   
   lono wireless extensions.
   
   enp33s0f1  no wireless extensions.
  MachineType: AMD Corporation DAYTONA_X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: RDY0071B
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DAYTONA_X
  dmi.board.vendor: AMD Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 2
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: DAYTONA_X
  dmi.product.sku: Default string
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: AMD Corporation

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

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

[Kernel-packages] [Bug 1816669] Re: AMD Rome : Minimal support patches

[Terry Rudd]

Kim, This is on the plan for applying to the 4.15 kernel in the June SRU
cycle

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

Title:
  AMD Rome :  Minimal support patches

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  The following 3 patches need to be back ported to ubuntu 18.04.2(Linux
  4.18) to complete the minimal support for Rome :

  818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum
  e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register
  90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode

  --thanks
  --kim
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-02-28 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp33s0f0  no wireless extensions.
   
   lono wireless extensions.
   
   enp33s0f1  no wireless extensions.
  MachineType: AMD Corporation DAYTONA_X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: RDY0071B
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DAYTONA_X
  dmi.board.vendor: AMD Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 2
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: DAYTONA_X
  dmi.product.sku: Default string
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: AMD Corporation

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

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

[Kernel-packages] [Bug 1824407] Re: why does booting any livefs squashfs has kernel complaining about unable to read metadata something rather

[Terry Rudd]

@dimitri are you still having this issue?  There isn't much to go on in
this bug submission yet.

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

Title:
   why does booting any livefs squashfs has kernel complaining about
  unable to read metadata something rather

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Apr 11 18:32:52 ubuntu-server kernel: SQUASHFS error: squashfs_read_data 
failed to read block 0x6ff3660032757063
  Apr 11 18:32:52 ubuntu-server kernel: SQUASHFS error: Unable to read metadata 
cache entry [6ff3660032757063]
  Apr 11 18:32:55 ubuntu-server kernel: SQUASHFS error: squashfs_read_data 
failed to read block 0x6261746d79732e
  Apr 11 18:32:55 ubuntu-server kernel: SQUASHFS error: Unable to read metadata 
cache entry [6261746d79732e]
  Apr 11 18:33:05 ubuntu-server kernel: SQUASHFS error: squashfs_read_data 
failed to read block 0x6ff366df00333a37
  Apr 11 18:33:05 ubuntu-server kernel: SQUASHFS error: Unable to read metadata 
cache entry [6ff366df00333a37]

  Happens when booting e.g. subiquity disco image. v5.0.0-8-generic
  kernel

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

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

[Kernel-packages] [Bug 1828134] Re: Wifi not working after suspend/resume cycle

[Terry Rudd]

Hello David, any new information on this problem?

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

Title:
  Wifi not working after suspend/resume cycle

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  About 75% of the time for the past few weeks (I don't have a time
  where this started), my wifi is not working after resume from suspend.
  I'm happy to provide more debugging info if needed.

  I have tried an rmmod/modprobe on on the iwlwifi,iwlmvm modules just
  to see after the resume, and didn't re-enable the card.

  The symptoms are, the wlp4so interface is DOWN, I can't bring it up.
  gnome-network-manager widget turning the interface off/on doesn't
  work.  I don't see anything glaring in dmesg.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-generic 5.0.0.14.15
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dpb4587 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  7 18:49:01 2019
  InstallationDate: Installed on 2018-06-18 (323 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HRCTO1WW
  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-5.0.0-14-generic 
root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-14-generic N/A
   linux-backports-modules-5.0.0-14-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-03-15 (53 days ago)
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET52W(1.37)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET52W(1.37):bd02/14/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output

[Terry Rudd]

With chance of regression quite low, we will not remove this particular
fix prior to release

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

Title:
  Headphone jack switch sense is inverted: plugging in headphones
  disables headphone output

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  On the LattePanda board, the headphone detection signal is not correct, it is
  inverted: plugging in headphones disables headphone output

  [Fix]
  In the codec driver, there already is a fixup, just set the inv_jd1_1 to true.

  [Test Case]
  It is tested by the bug reporter, please refer to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/comments/23

  [Regression Risk]
  Low. This fix is specific to a board which is defined by DMI strings.


  
  My machine is a LattePanda board, which uses a "chtrt5645" device as a sound 
card. It has a single headphone output jack, which I think is a TRRS jack, with 
a mic input, such as is normally used on phones.

  When I don't have headphones plugged in, the system thinks headphones
  *are* plugged in. Gnome Control Center shows my audio device as being
  headphones. If I insert a headphone connector partway into the jack, I
  can even get sound in the headphones.

  But if I plug the headphones all the way in, the system decided that I
  have *un*plugged the headphones, and switches output over to
  "Speaker". The system doesn't actually have a speaker, only a
  headphone jack. And when the system switches over to "Speaker", I get
  no sound out of the headphones, even if I open "pavucontrol" and swap
  over to "Headphones (unplugged)" on the "Output Devices" tab.

  This is what "pacmd"'s "list-cards" command says with my headphones
  *unplugged*:

  2 card(s) available.
  index: 0
   name: 
   driver: 
   owner module: 7
   properties:
    alsa.card = "1"
    alsa.card_name = "Intel HDMI/DP LPE Audio"
    alsa.long_card_name = "Intel HDMI/DP LPE Audio"
    alsa.driver_name = "snd_hdmi_lpe_audio"
    device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
    sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
    device.bus = "pci"
    device.vendor.id = "8086"
    device.vendor.name = "Intel Corporation"
    device.product.id = "22b0"
    device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Series PCI Configuration Registers"
    device.string = "1"
    device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Series PCI Configuration Registers"
    module-udev-detect.discovered = "1"
    device.icon_name = "audio-card-pci"
   profiles:
    output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: 
no)
    output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, 
available: no)
    output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, 
available: no)
    output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, 
available: no)
    output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 
600, available: no)
    output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output 
(priority 600, available: no)
    output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, 
available: no)
    output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 
600, available: no)
    output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output 
(priority 600, available: no)
    off: Off (priority 0, available: unknown)
   active profile: 
   ports:
    hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, 
available: no)
     properties:
  device.icon_name = "video-display"
    hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, 
available: no)
     properties:
  device.icon_name = "video-display"
    hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, 
available: no)
     properties:
  device.icon_name = "video-display"
  index: 1
   name: 
   driver: 
   owner module: 8
   properties:
    alsa.card = "0"
    alsa.card_name = "chtrt5645"
    alsa.long_card_name = 
"AMICorporation-Defaultstring-Defaultstring-CherryTrailCR"
    alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645"
    device.bus_path = "platform-cht-bsw-rt5645"
    sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0"
    device.form_factor = "internal"
    device.string = "0"
    device.description = "Built-in Audio"
    module-udev-detect.discovered = "1"
    device.icon_name = "audio-card"
   profiles:
    HiFi: Default (priority 8000, available: unknown)
    off: Off (priority 0, available: u

[Kernel-packages] [Bug 1828763] Re: Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.

[Terry Rudd]

I've added this bug for SRU in an upcoming SRU Cycle

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

Title:
  Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  * In b49151d684f44 tx_waited has been renamed to tx_dirty_delayed, but
  only in the tracepoint definition (in trace_dmu.h) and not in the rest
  of the code, causing build errors if zfs tracepoints are enabled.

  * Fix by reverting tx_dirty_delayed back to the original name
  tx_waited

  NOTE: this bug doesn't show up in regular kernel builds, because zfs
  tracepoints are not enabled by default, it is possible to see this
  problem only by enabling them and recompiling zfs outside our regular
  build process, but it's a good cleanup anyway (in case we need to
  enable zfs tracepoints in the future).

  [Test Case]

   * enable zfs tracepoints in config and build zfs

  [Fix]

   * Restore the old struct name to fix the build bug

  [Regression Potential]

   * It is a very small fix (just a rename of a struct member), so
  regression potential is minimal

  [Original bug report]

  I tried to build a kernel 4.15.0-48.51 that cloned from the Ubuntu
  kernel git (x86_64-generic flavour).

  commit c50532b9d7b623ff98aeaf0b848e58adae54ca75 (HEAD -> master, tag: 
Ubuntu-4.15.0-48.51, origin/master, origin/HEAD)
  Author: Andrea Righi 
  Date:   Tue Apr 2 18:31:55 2019 +0200

  UBUNTU: Ubuntu-4.15.0-48.51

  Signed-off-by: Andrea Righi 

  1. Build a kernel image with 'zfs_enable' flag set as false.
  2. Build SPL/ZFS modules independently by 'make' command (debug purpose; 
DECLARE_EVENT_CLASS() enabled).

  But 'make' was always failed at the same point,
  'zfs/module/zfs/trace.c' (as seem as below).

  In file included from /home/np/linux-4.15/include/trace/define_trace.h:96:0,
   from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
   from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
  /home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function 
‘trace_event_raw_event_zfs_delay_mintime_class’:
  /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka 
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
    __entry->tx_dirty_delayed  = tx->tx_dirty_delayed;
   ^
  /home/np/linux-4.15/include/trace/trace_events.h:719:4: note: in definition 
of macro ‘DECLARE_EVENT_CLASS’
    { assign; }   \
  ^~
  /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of 
macro ‘TP_fast_assign’
    TP_fast_assign(
    ^~
  In file included from /home/np/linux-4.15/include/trace/define_trace.h:97:0,
   from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
   from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
  /home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function 
‘perf_trace_zfs_delay_mintime_class’:
  /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka 
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
    __entry->tx_dirty_delayed  = tx->tx_dirty_delayed;
   ^
  /home/np/linux-4.15/include/trace/perf.h:66:4: note: in definition of macro 
‘DECLARE_EVENT_CLASS’
    { assign; }   \
  ^~
  /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of 
macro ‘TP_fast_assign’
    TP_fast_assign(
    ^~

  I tried to debug this issue with myself and found something intriguing.
  In 'zfs/include/sys/trace_dmu.h', the failed code accessing 
'tx_dirty_delayed' from 'dmu_tx_t' (which same as 'struct dmu_tx').

  DECLARE_EVENT_CLASS(zfs_delay_mintime_class,
  TP_PROTO(dmu_tx_t *tx, uint64_t dirty, uint64_t min_tx_time),
  TP_ARGS(tx, dirty, min_tx_time),
  TP_STRUCT__entry(
  __field(uint64_t,   tx_txg)
  __field(uint64_t,   tx_lastsnap_txg)
  __field(uint64_t,   tx_lasttried_txg)
  __field(boolean_t,  tx_anyobj)
  __field(boolean_t,  tx_dirty_delayed)
  __field(hrtime_t,   tx_start)
  __field(boolean_t,  tx_wait_dirty)
  __field(int,tx_err)
  __field(uint64_t,   min_tx_time)
  __field(uint64_t,   dirty)
  ),
  TP_fast_assign(
  __entry->tx_txg = tx->tx_txg;
  __entry->tx_lastsnap_txg= tx->tx_lastsnap_txg;
  __entry->tx_lasttried_txg   = tx->tx_lasttried_txg;
  __entry->tx_anyobj  = tx->tx_anyobj;
  __entry->tx_dirty_delayed   

[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu

[Terry Rudd]

The canonical engineering team has been tracking this issue, but
apologies again for the delay in responding to the request for technical
discussion on this bug.

We have escalated the priority of this specific issue, and intend to get
you a technical response by the end of the week.

-- 
You 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:
  [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common
  deb on Ubuntu

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

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

Re: [Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.

[Terry Rudd]

On 5/29/19 6:58 PM, Sean Feole wrote:
> I revisited this particular problem today. I ran a series of restart
> tests across westus2 and westus,  utilizing the same instance and
> series, but with the latest kernel in -proposed.  I was unable to
> reproduce this problem as originally reported in the bug. I also have
> not seen any of our SRU testing stall due to problems of this nature,
> where the instance fails to respond after a restart.
> 
> I think it's safe to say we can close this bug and mark it resolved for
> the time being.
> 

Sean, we plan to do this in today's call.

Terry

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

Title:
  Azure Instance never recovered during series of instance reboots.

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description: During SRU Testing of various Azure Instances, there will
  be some cases where the instance will not respond following a system
  reboot.  SRU Testing only restarts a giving instance once, after it
  preps all of the necessary files to-be-tested.

  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  I initiated a series of tests which rebooted Azure Cloud instances 50
  times. During the 49th Reboot, an Instance failed to return from a
  reboot.. Upon grabbing the console output the following was seen
  scrolling endlessly. I have seen this failure in cases where the
  instance only restarted a handful of times >5

  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus

  In another test attempt I saw the following failure:

  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes

  
  Both of these failures broke networking, Both of these failures were seen at 
least twice to three times, thus may explain why in some cases we never recover 
from an instance reboot.

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

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

[Kernel-packages] [Bug 1830740] Re: [linux-azure] Delay during boot of some instance sizes

[Terry Rudd]

We will be investigation this situation ASAP but it is pending
submission for SRU for other azure work.

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

Title:
  [linux-azure] Delay during boot of some instance sizes

Status in linux-azure package in Ubuntu:
  New

Bug description:
  We are seeing a long delay, about 100s, when booting new E32s_v3 VMs.

  We don’t see this delay with smaller sized Ubuntu VMs(D2s and NC6
  sizes).

  I attached a screen shot of the boot delay.  You can see between
  7.022911 and 101.325958 seconds there is no activity.

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

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

[Kernel-packages] [Bug 1752002] Re: [P9, POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while running perf fuzzer (perf:)

[Terry Rudd]

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

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

** Changed in: ubuntu-power-systems
   Status: Fix Released => 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/1752002

Title:
  [P9,POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is
  seen while running perf fuzzer (perf:)

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-02-02 
01:21:36 ==
  Problem Description :
  =

  Warn on message is seen while running perf fuzzer tests.

  Machine details :
  ==
  Hardware : Witherspoon (wsp12) + DD2.1
  OS : Ubuntu 1804
  uname -a : 4.13.0-32-generic #35~lp1746225 ( Kernel from the bug : 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7 )

  
  Steps to reproduce :
  
  Build Kernel :
  
  To avoid the kernel crash due to Perf fuzzer , use the kernel mentioned in 
the link : https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7

  #! /bin/bash
  set -x
  git clone https://github.com/deater/perf_event_tests.git
  cd perf_event_tests/include
  mkdir asm
  cd asm
  wget http://9.114.13.132/repo/shriya/perf_regs.h
  cd ../../lib
  make
  sleep 10
  cd ../fuzzer
  make
  sleep 10

  echo 0 > /proc/sys/kernel/nmi_watchdog
  echo 2 > /proc/sys/kernel/perf_event_paranoid
  echo 10 > /proc/sys/kernel/perf_event_max_sample_rate
  ./perf_fuzzer -r 1492143527

  
  Call trace :
  ===
  [  329.228031] [ cut here ]
  [  329.228039] WARNING: CPU: 43 PID: 9088 at 
/home/jsalisbury/bugs/lp1746225/ubuntu-artful/kernel/events/core.c:3038 
perf_pmu_sched_task+0x170/0x180
  [  329.228040] Modules linked in: ofpart at24 uio_pdrv_genirq uio cmdlinepart 
powernv_flash mtd ipmi_powernv vmx_crypto ipmi_devintf ipmi_msghandler 
ibmpowernv opal_prd crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 
crc32c_vpmsum lpfc ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt mlx5_core fb_sys_fops ttm tg3 nvmet_fc drm ahci nvmet nvme_fc libahci 
nvme_fabrics mlxfw nvme_core devlink scsi_transport_fc
  [  329.228068] CPU: 43 PID: 9088 Comm: perf_fuzzer Not tainted 
4.13.0-32-generic #35~lp1746225
  [  329.228070] task: c03f776ac900 task.stack: c03f77728000
  [  329.228071] NIP: c0299b70 LR: c02a4534 CTR: 
c029bb80
  [  329.228073] REGS: c03f7772b760 TRAP: 0700   Not tainted  
(4.13.0-32-generic)
  [  329.228073] MSR: 9282b033 
  [  329.228079]   CR: 24008822  XER: 
  [  329.228080] CFAR: c0299a70 SOFTE: 0 
 GPR00: c02a4534 c03f7772b9e0 c1606200 
c03fef858908 
 GPR04: c03f776ac900 0001  
003fee73 
 GPR08:   c11220d8 
0002 
 GPR12: c029bb80 c7a3d900  
 
 GPR16:    
 
 GPR20:   c03f776ad090 
c0c71354 
 GPR24: c03fef716780 003fee73 c03fe69d4200 
c03f776ad330 
 GPR28: c11220d8 0001 c14c6108 
c03fef858900 
  [  329.228098] NIP [c0299b70] perf_pmu_sched_task+0x170/0x180
  [  329.228100] LR [c02a4534] __perf_event_task_sched_in+0xc4/0x230
  [  329.228101] Call Trace:
  [  329.228102] [c03f7772b9e0] [c02a0678] 
perf_iterate_sb+0x158/0x2a0 (unreliable)
  [  329.228105] [c03f7772ba30] [c02a4534] 
__perf_event_task_sched_in+0xc4/0x230
  [  329.228107] [c03f7772bab0] [c01396dc] 
finish_task_switch+0x21c/0x310
  [  329.228109] [c03f7772bb60] [c0c71354] __schedule+0x304/0xb80
  [  329.228111] [c03f7772bc40] [c0c71c10] schedule+0x40/0xc0
  [  329.228113] [c03f7772bc60] [c01033f4] do_wait+0x254/0x2e0
  [  329.228115] [c03f7772bcd0] [c0104ac0] kernel_wait4+0xa0/0x1a0
  [  329.228117] [c03f7772bd70] [c0104c24] SyS_wait4+0x64/0xc0
  [  329.228121] [c03f7772be30] [c000b184] system_call+0x58/0x6c
  [  329.228121] Instruction dump:
  [  329.228123] 3beafea0 7faa4800 409eff18 e8010060 eb610028 ebc10040 7c0803a6 
38210050 
  [  329.228127] eb81ffe0 eba1ffe8 ebe1fff8 4e800020 <0fe0> 4bbc 
6000 6042 
  [  329.228131] ---[ end trace 8c46856d314c1811 ]---
  [  375.755943] hrtimer: interrupt took 31601 ns

  == Comment: #4 - SEETEENA THOUFEEK  - 2018-02-05
  06:34:09 ==

  
  == Comment: #5 - SEETEENA THOUFEEK  -

[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend

[Terry Rudd]

Chris, any chance we can get the data that Andrea is asking for above?

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

Title:
  Lid switch triggered suspend takes much longer than UI triggered
  suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  IBM T460
  5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  
  When triggering a suspend even from the lid switch of my Lenovo T460 it takes 
30 seconds to reach suspend state. Several others with different models of 
Lenovo laptops have also reproduced this issue. 

  It seems this is isolated to the lid switch as UI triggered suspend
  (alt+power icon) is far faster.

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

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

[Kernel-packages] [Bug 1832641] Re: 4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

[Terry Rudd]

Did this work correctly in previous 4.15.0 kernels?

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

Title:
  4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Bionic 18.04 LTS:
  We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool 
-C adaptive-tx
  Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect 
performance of latency sensitive workloads like memcached.
  Maybe we should backport adaptive-tx support to kernel 4.15 LTS?

  
  Xeon Skylake 8168 x86_64:
  ubuntu kernel 4.15.0-46-generic
  eth: mlx5 connect-5
  ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce)

  X-Gene3 aarch64:
  ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)

  Same Xeon Skylake 8168 x86_64
  latest kernel 5.2.0-rc2
  eth: mlx5 connect-5
  ethtool supports adaptive-tx (ethernet TX interrupt coalesce)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 14:42 seq
   crw-rw 1 root audio 116, 33 Jun 12 14:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  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
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 
iommu.passthrough=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-16-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Ampere(TM)
  dmi.bios.version: 4.8.19
  dmi.board.asset.tag: APCX3A1-A526-16050501200016
  dmi.board.name: OSPREY
  dmi.board.vendor: AmpereComputing(R)
  dmi.board.version: EV-883832-X3-OD1-2
  dmi.chassis.asset.tag: APCX3A1-A526-16050501200016
  dmi.chassis.type: 23
  dmi.chassis.vendor: AmpereComputing(R)
  dmi.chassis.version: APCA1A1-
  dmi.modalias: 
dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-:
  dmi.product.family: eMAG
  dmi.product.name: OSPREY EV-883832-X3-0001
  dmi.product.sku: EV-883832-X3-OBX-1
  dmi.product.version: PR010
  dmi.sys.vendor: AmpereComputing(R)
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 12 15:22 seq
   crw-rw 1 root audio 116, 33 Jun 12 15:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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
  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 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable 
console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname

[Kernel-packages] [Bug 1832290] Re: Raspberry Pi 3 B+: Load average always reported as 4.0 even when idle

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1825235
   Load average inexplicably high with 5.0 kernel on rpi

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

Title:
  Raspberry Pi 3 B+: Load average always reported as 4.0 even when idle

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  $ uptime
   12:40:44 up 1 day, 10:56,  1 user,  load average: 4.00, 4.02, 4.00

  The load is always reported as higher than 4 even on an idle system.

  Seems to be this upstream:
  https://github.com/raspberrypi/linux/issues/2881

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1009-raspi2 5.0.0-1009.9
  ProcVersionSignature: Ubuntu 5.0.0-1009.9-raspi2 5.0.8
  Uname: Linux 5.0.0-1009-raspi2 aarch64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: arm64
  Date: Tue Jun 11 12:33:57 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-raspi2
  UpgradeStatus: Upgraded to disco on 2019-05-22 (19 days ago)

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

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

[Kernel-packages] [Bug 1833464] Re: Request backports of ceph client commits to bionic kernel

[Terry Rudd]

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Connor Kuehl (connork)

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

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

** Also affects: linux (Ubuntu Bionic)
   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/1833464

Title:
  Request backports of ceph client commits to bionic kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  New

Bug description:
  Customer has run into a few ceph client related issues, which were root 
caused to be resolved by the following kernel commits: 
  
https://github.com/ceph/ceph-client/commit/f42a774a2123e6b29bb0ca296e166d0f089e9113
 
  
https://github.com/ceph/ceph-client/commit/093ea205acd4b047cf5aacabc0c6ffecf198d2a9
 
  Can you please backport these into bionic?

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

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

[Kernel-packages] [Bug 1833382] Re: 4.4.0.151.159 is in xenial-updates not xenial-security

[Terry Rudd]

The operation to get mitigated kernels into -security pockets should be
complete now

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

Title:
  4.4.0.151.159 is in xenial-updates not xenial-security

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  The SACK Panic kernel update was uploaded into xenial-updates instead
  of xenial-security:

  https://packages.ubuntu.com/xenial-updates/linux-image-generic

  normally I would expect this to be in the xenial-security component,
  especially because this is a security update. People who only track
  xenial-security and not xenial-updates will now not get the security
  update.

  see https://launchpad.net/ubuntu/+source/linux/4.4.0-151.178 and the
  previous https://launchpad.net/ubuntu/+source/linux/4.4.0-150.176, one
  is Pocket: updates, the older one is Pocket: security.

  # grep sec /etc/apt/sources.list
  deb http://security.ubuntu.com/ubuntu xenial-security xenial-updates main 
restricted universe multiverse
  # apt-cache policy linux-image-4.4.0-150-generic
  linux-image-4.4.0-150-generic:
Installed: 4.4.0-150.176
Candidate: 4.4.0-150.176
Version table:
   *** 4.4.0-150.176 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  # apt-cache search linux-image | grep "generic" | grep "\-15"
  linux-image-4.15.0-15-generic - Linux kernel image for version 4.15.0 on 64 
bit x86 SMP
  linux-image-4.4.0-150-generic - Signed kernel image generic
  linux-image-extra-4.15.0-15-generic - Linux kernel extra modules for version 
4.15.0 on 64 bit x86 SMP
  linux-image-unsigned-4.4.0-150-generic - Linux kernel image for version 4.4.0 
on 64 bit x86 SMP

  https://packages.ubuntu.com/xenial-updates/linux-image-generic
  https://packages.ubuntu.com/xenial/linux-image-generic

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

-- 
Mailing list: https://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 1828166] Re: perf top problem on z with Ubuntu 18.04

[Terry Rudd]

Hello Frank,

On 6/19/19 7:13 AM, Frank Heimes wrote:
> Just tried to cherry-pick 1) 6738028 and 2) ed9adb2 from 5.3-rc3 to bionic's 
> master-next tree:
> git://kernel.ubuntu.com/ubuntu/ubuntu-bionic --branch master-next
> 1) applied cleanly, but 2) did not - I got 3 conflicts while cherry-picking 
> ed9adb2
> Is there something still missing?
> (I used bionic to check, because it's the oldest release this should SRUed 
> to, and master-next is needed, because things progress and some patches might 
> already got accepted on top of master, even if not yet released.)
> 

Sorry I am late getting back to you.   Yes, Kleber set out to do what
you tried and found the same.  he was hoping to finish this before his
vacation but was unable to.  I asked Khaled to try and finish that
trello card and of course he ran into problems and ran out of time due
to impact on our SRU from the SACK Panic release and having to get new
kernels ready for July 1 SRU release in the two weeks we had left.
Khaled is hoping to get back to this card tomorrow, Friday, June 21.

Will keep you updated but hope this is resolved and fix-committed for
SRU 2019.07.01

Terry

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

Title:
  perf top problem on z with Ubuntu 18.04

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The perf top tool hangs and shows error messages, like 'Not enough
  memory for annotating'

  [Fix]

  * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop
  fallbacking to kallsyms for vdso symbols lookup"

  [Test Case]

  * start a benchmark (mem_alloc, but it doesn't really matter what)

  * execute perf top in a second terminal

  * the output of perf top is correct

  * now stop the benchmark

  * and perf top shows an error message, like "Not enough memory for
  annotating '__irf_end' symbol!)"

  * and perf top can't be exited anymore

  [Regression Potential]

  * The regression potential can be considered as low since this happens
  only while using the perf top tool

  * and it is known that the commit (above) fixes the problem

  * and the fix is upstream since 4.19

  [Other Info]

  * current disco and eoan kernels don't show that problem

  * bisecting result points to above commit

  * applies cleanly on cosmic, but has a little conflict on bionic (both 
master-next)
  _

  perf top hangs and shows error messages

  ---uname output---
  Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 
s390x s390x s390x GNU/Linux

  ---Steps to Reproduce---
   I start a benchmark (mem_alloc, but it really doesn't matter) and then issue 
perf top in a second terminal, the output from perf top is correct. Now I stop 
the benchmark: perf top shows a error message (Not enough memory for annotating 
'__irf_end' symbol!) and I can't quit from perf top anymore

  Following analyse took place:
  No problem with current kernel .
  Bi-Secting of perf tool took place and following commit was found:

  commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
  Author: Arnaldo Carvalho de Melo 
  Date:   Tue Oct 16 17:08:29 2018 -0300

  perf tools: Stop fallbacking to kallsyms for vdso symbols lookup

  When you apply this patch the issue is gone, however it is contained
  in these versions:

  git tag --contains  edeb0c90df3581b821
  v4.19
  v4.20
  

  The level I was debugging was kernel 4.15 which does not contain this
  patch.

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

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

[Kernel-packages] [Bug 1813651] Re: hpsa: DMAR invalid read

[Terry Rudd]

Guilherme, is there going to be further work on this 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/1813651

Title:
  hpsa: DMAR invalid read

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  Recently in kernel 4.20-rc1 and newer we observed the following
  spontaneous issue with hpsa when intel_iommu is enabled:

  [ 5173.952022] DMAR: DRHD: handling fault status reg 2
  [ 5174.190649] DMAR: [DMA Read] Request device [03:00.0] fault addr eefdd000 
[fault reason 06] PTE Read access is not set

  There's a commit that touches DMA in hpsa: "scsi: hpsa: switch to generic DMA 
API"
  We've tested with this commit reverted on top of 4.20-rc1 and it reproduces 
(the trigger is a kernel build). We cannot reproduce in 4.19.

  Investigation is ongoing.

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

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

[Kernel-packages] [Bug 1825632] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon

[Terry Rudd]

This looks to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825420  Can you
please confirm?

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: bloqué en boucle sur le traitement des actions
  différées (« triggers »), abandon

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Problem when i installing the new version.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erwan  3106 F pulseaudio
   /dev/snd/controlC1:  erwan  3106 F pulseaudio
  Date: Sat Apr 20 12:37:44 2019
  ErrorMessage: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
  InstallationDate: Installed on 2018-10-07 (194 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=d478b832-a087-4e04-824b-57099769e24e ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  SourcePackage: linux
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
  dmi.bios.date: 05/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LB.603
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LB
  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.:bvrX555LB.603:bd05/06/2016:svnASUSTeKCOMPUTERINC.:pnX555LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LB
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1825698] Re: Upgrade to 19.04 from 18.10 doesnt boot

[Terry Rudd]

This looks to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825420.  Can you
please confirm?

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

Title:
  Upgrade to 19.04 from 18.10 doesnt boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrade completes but shows error message that linux kernel 5.0.0-13 may not 
be in working state.
  After completion of upgrade Ubuntu doesn't boot at all.. Just shows few blank 
screens and hangs.
  I reverted back to my old kernel 4.18.0-17 that was in Ubuntu 18.10 and it 
booted fine..
  Then I dleleted the new 5.0.0-13 kernel and headers.
  Now Ubuntu 19.04 boots fine with old kernel.

  I also tried reinstalling kernel 5.0.0-13. But faced same issue again. So 
again I went back to old kernel.
  I noticed others too have been facing this problem.
  KINDLY LOOK INTO THE BUG AND LET US KNOW THE SOLUTION

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

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

[Kernel-packages] [Bug 1825724] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1825420
   package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: 
triggers looping, abandoned

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue happened during upgrade of a Ubuntu server 18.10 to 19.04.
  Notes: lubuntu-desktop was installed on the server, and xrdp.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sun Apr 21 15:02:58 2019
  ErrorMessage: triggers looping, abandoned
  IwConfig:
   ens18 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=ee536208-21b1-4f22-bce5-b8112499a39e ro maybe-ubiquity
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.12
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.12
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1825704] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1825420
   package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: 
triggers looping, abandoned

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 19.04, this error keeps occuring. Upgrade was not
  successfull.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mwoehrle   2134 F pulseaudio
   /dev/snd/controlC0:  mwoehrle   2134 F pulseaudio
   /dev/snd/controlC1:  mwoehrle   2134 F pulseaudio
  Date: Sun Apr 21 10:17:27 2019
  ErrorMessage: triggers looping, abandoned
  HibernationDevice: RESUME=UUID=f5b7707a-0197-4446-973b-26cee2f07e80
  InstallationDate: Installed on 2016-12-15 (856 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: MSI MS-7977
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=6f7d285a-3e0e-42d8-8bcc-def6e9acfe35 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago)
  dmi.bios.date: 10/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.C0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M5 (MS-7977)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd10/19/2016:svnMSI:pnMS-7977:pvr1.0:rvnMSI:rnZ170AGAMINGM5(MS-7977):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7977
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1825915] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1825420
   package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: 
triggers looping, abandoned

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  greg@mizuno:/var/crash$ cat /proc/version_signature
  Ubuntu 4.18.0-13.14-generic 4.18.17

  greg@mizuno:/var/crash$ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Happened during upgrade from 18.10 to 19.04.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Apr 22 14:19:36 2019
  ErrorMessage: triggers looping, abandoned
  HibernationDevice: RESUME=UUID=94c635e6-8245-4fe1-8c93-432c8d10dbd1
  InstallationDate: Installed on 2012-02-14 (2624 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcFB:
   0 VESA VGA
   1 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  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.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1826289] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1825420
   package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: 
triggers looping, abandoned

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had problems in the 19.04 upgrade, as in
  https://ubuntuforums.org/showthread.php?t=2417517

  The Crash happened during a sudo apt full-upgrade that was requested
  by the team is helping me

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Thu Apr 25 01:27:59 2019
  ErrorMessage: triggers looping, abandoned
  HibernationDevice: RESUME=UUID=16ee3024-b6d7-4569-92e6-334e6d55fb90
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=dcd8f016-29e1-4dc4-a9e1-33ea6b421152 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-23 (1 days ago)
  dmi.bios.date: 09/17/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd09/17/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1826626] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[Terry Rudd]

This bug is a duplicate of LP 1825420.  I was going to mark it so but
Launchpad warns this bug has duplicates itself so I am going to leave it
as is.  Work is ongoing on LP 1825420

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  upgrade to new ubuntu version failed.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kunalss1554 F pulseaudio
   /dev/snd/controlC1:  kunalss1554 F pulseaudio
  Date: Sat Apr 27 09:42:43 2019
  ErrorMessage: triggers looping, abandoned
  HibernationDevice: RESUME=UUID=27221f04-7abb-4a16-8bf9-0d223f3559d6
  InstallationDate: Installed on 2016-10-23 (915 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E7250
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=485acc8d-1178-4d60-baef-b2674d600e32 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  SourcePackage: linux
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-27 (0 days ago)
  dmi.bios.date: 05/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.asset.tag: 72608
  dmi.board.name: 0V8RX3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 72608
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/13/2015:svnDellInc.:pnLatitudeE7250:pvr01:rvnDellInc.:rn0V8RX3:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7250
  dmi.product.sku: Latitude E7250
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1824879] Re: linux-azure: Add the Catapult FPGA Driver

[Terry Rudd]

On 4/30/19 10:11 AM, Joseph Salisbury wrote:
> ** Tags removed: verification-needed-xenial
> ** Tags added: verification-done-xenial
> 


Thank you Joe!

Terry

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

Title:
  linux-azure: Add the Catapult FPGA Driver

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  Add the Catapult FPGA Driver to the custom linux-azure kernel while a
  version is not available upstream.

  [Test Case]

  The catapult driver must be present as a module in the linux-modules
  package (not in the linux-modules-extra).

  [Regression Potential]

  Low risk of regression since that's a new driver.

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

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

[Kernel-packages] [Bug 1827045] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1825420
   package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: 
triggers looping, abandoned

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Right after update to 19.04, don't know anything more

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue Apr 30 12:29:31 2019
  ErrorMessage: triggers looping, abandoned
  HibernationDevice: RESUME=UUID=08b31b8f-4fa4-4d2e-84e3-7b79e615def1
  InstallationDate: Installed on 2015-12-17 (1230 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  MachineType: ASUSTeK COMPUTER INC. G10AJ
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=1b57db95-46e2-43a9-a0a2-928014f1b17f ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-30 (0 days ago)
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0303
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: G10AJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  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.:bvr0303:bd05/15/2014:svnASUSTeKCOMPUTERINC.:pnG10AJ:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnG10AJ:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: Desktop
  dmi.product.name: G10AJ
  dmi.product.sku: All
  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/1827045/+subscriptions

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

[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot

[Terry Rudd]

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

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

Title:
  arm64: cma_alloc errors at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On some arm64 systems[*] we are seeing a spew of messages on the
  console:

  [   19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12

  This appears to be non-fatal - impacted systems all eventually boot.
  But, at least in the case of the HP m400, it slows down boot enough
  that MAAS' default timeout will expire before completing deployment.

  [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well
  as an HP m400 (APM X-Gene) cartridge - although, not on another one
  that - in theory - should be identical.

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

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

[Kernel-packages] [Bug 1827862] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1825420
   package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: 
triggers looping, abandoned

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was following a distribution upgrade from 18.10 to 19.04

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Mon May  6 10:22:10 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-10-29 (188 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: ASUS All Series
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=67cf1bcc-bd72-40e0-a316-c2c7533028ba ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-05-06 (0 days ago)
  dmi.bios.date: 05/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2205
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2205:bd05/26/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

-- 
Mailing list: https://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 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220

[Terry Rudd]

On 7/30/19 3:39 PM, Colin Ian King wrote:
> Tested disco -proposed 5.0.0-23, all OK.
> 
> ** Tags removed: verification-needed-disco
> ** Tags added: verification-done-disco
> 

Hello Colin,

Thanks for all your work.  I am so bummed you have put in so much work
but I sincerely appreciate it.  I hope you get some good sleep.

Terry

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

Title:
  linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == SRU Justification BIONIC HWE, DISCO ==

  Installed Bionic 18.04.2 i386 Desktop (using xubuntu) on a Lenovo
  x220i and upgraded to proposed. The 5.0.0.22 kernel crashes in various
  ways with video corruption being a main visible featured.

  The CPU is a  i3-2350M CPU, a 64 bit capable CPU, being booted with
  EUFI firmware disabled, so using traditional BIOS.

  1. Crashes can be just complete hangs, no ability to switch virtual console
  2. Crashes may just result in screen turning off, no video and hang and/or 
reboot
  3. Crashes sometimes allow virtual console. Can see watchdog hang checks 
appearing on 1 or more CPUs.

  Tried the i386 https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
  kernels:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.21/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.17/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.61/ - OK

  We therefore can conclude:

  1. Issue appears between 4.19.61 and 4.20.17
  2. Issue is in upstream kernel
  3. Issue not a kernel patch per-se (e.g. security fix, ubuntu sauce patch, 
etc)

  I repeated this with a VM installation and I don't see the issue, so
  this probably is a hardware (or firmware?) specific issue.

  == Fix ==

  Backport wiggle of upstream fix

  3f8fd02b1bf1d7ba964485a56f2f4b53ae88c167 ("mm/vmalloc: Sync unmappings
  in __purge_vmap_area_lazy()")

  == Test ==

  Without the fix, i386 xubuntu on various Lenovo platforms crash during
  early boot with random video corruption, hangs,lockups or even
  reboots.

  With the fix, it boots fine.

  == Regression Potential ==

  Higher than normal as this touches the mm sync and the fix has only
  just hit upstream so it has not much of a soak test.  Testing with
  this shows it fixes a kitten killer breakage, so I think the risk vs
  benefit is worth considering

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

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

[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption

[Terry Rudd]

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => 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/1823037

Title:
  amd_iommu possible data corruption

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  If a device has an exclusion range specified in the IVRS
  table, this region needs to be reserved in the iova-domain
  of that device. This hasn't happened until now and can cause
  data corruption on data transfered with these devices.

  The exlcusion range limit register needs to contain the
  base-address of the last page that is part of the range, as
  bits 0-11 of this register are treated as 0xfff by the
  hardware for comparisons.

  So correctly set the exclusion range in the hardware to the
  last page which is _in_ the range.

  [Fixes]
  Cherry pick the following from Mainline
  fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range 
in iova-domain
  3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range 
correctly

  These can be picked from my branches here:
  Bionic:
  https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic 
1823037-amd_iommu-cherrypick
  b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range 
in iova-domain
  ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range 
correctly

  Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic 
1823037-amd_iommu-cherrypick
  0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range 
in iova-domain
  fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range 
correctly

  Disco:
  https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco 
1823037-amd_iommu-cherrypick
  6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range 
correctly

  Note Disco only required f1cd47fe12 as the first patch was already
  picked in LP: #1830934

  Not necessary for Eoan as these are already upstream in 5.2-rc1

  [Regression Risk]
  Low,this adds memory protection to the driver and has already been applied 
upstream and tested by Dell for 24 hours with no failures noted.

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

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

[Kernel-packages] [Bug 1830813] Re: TCP : race condition on socket ownership in tcp_close()

[Terry Rudd]

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => 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/1830813

Title:
  TCP : race condition on socket ownership in tcp_close()

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid

Bug description:
  SRU Justification

  Impact: WARN_ON messages casued by race condition between the close of
  a TCP socket and another process  inspecting the same socket.

  The code of interest is the following; in tcp_close function :
  ...
  release_sock(sk);
  ...
  WARN_ON(sock_owned_by_user(sk));
  ...

  While in release_sock(sk), sock_release_owner function is called which sets 
the 
  sk->sk_lock.owned=0.
  When WARN_ON(sock_owned_by_user(sk)) is called it expects to find that the 
socket is not
  owned by anyone.
  According to upstream commit 8873c064d1de579ea2341,
  while a socket is being closed is possible that other threads find it in 
rtnetlink dump.
  tcp_get_info() function acquires the socket lock ( and sets sk_lock.owned=1 ) 
for 
  a short amount of time, however long enough to trigger this warning.

  
  Fix: 
  Fixed by upstream commit in v4.20:
  Commit: 8873c064d1de579ea23412a6d3eee972593f142b
  "tcp: do not release socket ownership in tcp_close()"

  Commit 8873c064d1de579ea23412a6d3eee972 fixes this bug by delegating the 
release of ownership
  (calling release_sock(sk)) to later; just before exiting tcp_close function.
   

  Testcase:
  Reporter has tested and verified test 4.15 test kernel for Bionic.
  This bug is difficult to be reproduced locally because the race condition 
cannot 
  be triggered in a deterministic way.
  To hit this bug we need the following :
  a) a process closing a socket and while the execution is between 
release_sock(s)
  and WARN_ON(sock_owned_by_user(sk))
  b) another process inspecting the same socket to get into tcp_get_info(), 
acquire
  ownership of the socket and not release it until the first process reaches the
  WARN_ON(sock_owned_by_user(sk)).

  This scenario is difficult to be achieved in a testing environment.

  
  Regression Potential:
  As far as Bionic (4.15 kernel) is concerned the reporter of the bug has 
tested and
  verified a test kernel with the fix.
  Concerning Cosmic (4.18 kernel) the fix has not been tested.
  However, given that 
  a) this fix essentially removes the WARN_ON(sock_owned_by_user(sk))
  and delegates the release of the ownership to later in the tcp_close 
function, and
  b) the relevant code paths in 4.15 and 4.18 are largely the same
  the regression potential should be minimal.

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

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

[Kernel-packages] [Bug 1829942] Re: Address performance issue w/ GICv4-based guests

[Terry Rudd]

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => 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/1829942

Title:
  Address performance issue w/ GICv4-based guests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  In Progress

Bug description:
  [Impact]
  Performance is degraded when a guest is booted w/ vgic v4 support enabled. 

  [Test Case]
  I used a HiSilicon D06 system w/ an Intel 82599 10Gbps NIC. I passed through 
a VF to a guest, and ran "netperf -H " against a 10Gbps-capable target. 
With vgic v4 support, I'm only seeing 5-6Gbps. With vgic v3 support, this was 
in the 9Gbps spectrum. And, after applying the upstream fix, I'm also seeing 
>9Gbps w/ vgic v4 enabled.

  Note: to enable vgic v4 support, pass "kvm-arm.vgic_v4_enable=1" on
  the host kernel cmdline.

  [Fix]
  ca71228b42a96 arm64: KVM: Always set ICH_HCR_EL2.EN if GICv4 is enabled

  [Regression Risk]
  The fix is restricted to the ARM/KVM subsystem.

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

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

[Kernel-packages] [Bug 1834962] Re: add support for Amazon Graviton PCIe controller

[Terry Rudd]

** Changed in: linux-aws (Ubuntu Cosmic)
   Status: In Progress => Invalid

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

Title:
  add support for Amazon Graviton PCIe controller

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-aws source package in Cosmic:
  Invalid
Status in linux-aws source package in Disco:
  Fix Committed
Status in linux-aws source package in Eoan:
  In Progress
Status in linux-aws source package in FF-Series:
  New

Bug description:
  Three patches are needed to add support for Amazon / Annapurna Labs
  "Graviton" PCIe controller, which is required for future AWS instance
  types.

  The feature is to be enabled for Ubuntu kernels >= linux-aws-bionic.

  The first patch is from mainline; the other two are AWS specific
  quirks from Amazon Linux, not yet upstream.

  4166bfe530  PCI: al: Add Amazon Annapurna Labs PCIe host controller driver
  UBUNTU: SAUCE: [aws] irqchip/gic-v2m: invoke from gic-v3 initialization and 
add acpi quirk flow
  UBUNTU: SAUCE: [aws] arm64: acpi/pci: invoke _DSM whether to preserve 
firmware PCI setup

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

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

[Kernel-packages] [Bug 1832388] Re: [power9] [Cosmic] kernel panic while testing kdump

[Terry Rudd]

Manoj, what is next with this bug?  Were we able to isolate it to a
particular hardware platform?

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

Title:
  [power9] [Cosmic] kernel panic while testing kdump

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

Bug description:
  I installed cosmic on power9 (boston) a non-nvme system, installed
  initramfs-tools from -proposed and install kdump-tools. Triggered a
  dump, but I got a kernel panic. This might be a kernel bug/regression.

  ubuntu@tiselius:~$ uname -a 
  Linux tiselius 4.18.0-21-generic #22-Ubuntu SMP Wed May 15 13:12:45 UTC 2019 
ppc64le ppc64le ppc64le GNU/Linux
  ubuntu@tiselius:~$ 

  ubuntu@tiselius:~$ apt policy initramfs-tools
  initramfs-tools:
Installed: 0.131ubuntu15.2
Candidate: 0.131ubuntu15.2
Version table:
   *** 0.131ubuntu15.2 500
  500 http://ports.ubuntu.com/ubuntu-ports cosmic-proposed/main ppc64el 
Packages
  ubuntu@tiselius:~$

  ubuntu@tiselius:~$ apt policy kdump-tools 
  kdump-tools:
Installed: 1:1.6.5-1ubuntu1~18.10.1
Candidate: 1:1.6.5-1ubuntu1~18.10.1
Version table:
   *** 1:1.6.5-1ubuntu1~18.10.1 500
  500 http://ports.ubuntu.com/ubuntu-ports cosmic-updates/main ppc64el 
Packages
  100 /var/lib/dpkg/status
   1:1.6.4-2ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports cosmic/main ppc64el Packages
  ubuntu@tiselius:~$ 

  ubuntu@tiselius:~$ sudo kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.18.0-21-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.18.0-21-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 
nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  ubuntu@tiselius:~$

  ubuntu@tiselius:~$ cat /proc/cmdline 
  root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M
  ubuntu@tiselius:~$

  ubuntu@tiselius:~$ dmesg | grep Reser
  [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System 
RAM: 131072MB)
  [0.00] cma: Reserved 6560 MiB at 0x200e6200
  ubuntu@tiselius:~$

  root@tiselius:/home/ubuntu# echo 1 > /proc/sys/kernel/sysrq
  root@tiselius:/home/ubuntu# echo c > /proc/sysrq-trigger

  tiselius login: [  150.167288] cloud-init[4529]: Cloud-init v. 
19.1-1-gbaa47854-0ubuntu1~18.10.1 running 'modules:final' at Mon, 10 Jun 2019 
19:53:40 +. Up 149.80 seconds.
  [  150.167687] cloud-init[4529]: Cloud-init v. 
19.1-1-gbaa47854-0ubuntu1~18.10.1 finished at Mon, 10 Jun 2019 19:53:40 +. 
Datasource DataSourceMAAS 
[http://10-245-64-0--21.maas-internal:5248/MAAS/metadata/].  Up 150.11 seconds
  [  360.313029] kdump-tools[4915]: Stopping kdump-tools:  * unloaded kdump 
kernel
  [  376.552452] kdump-tools[10449]: Starting kdump-tools:  * Creating symlink 
/var/lib/kdump/vmlinuz
  [  376.553743] kdump-tools[10449]:  * Creating symlink 
/var/lib/kdump/initrd.img
  [  376.585085] kdump-tools[10449]: Modified 
cmdline:root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 
nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb 
elfcorehdr=158784K
  [  376.953223] kdump-tools[10449]:  * loaded kdump kernel
  [  398.517900] sysrq: SysRq : Trigger a crash
  [  398.517952] Unable to handle kernel paging request for data at address 
0x
  [  398.518000] Faulting instruction address: 0xc082a3a8
  [  398.518071] Oops: Kernel access of bad area, sig: 11 [#1]
  [  398.518115] LE SMP NR_CPUS=2048 NUMA PowerNV
  [  398.518172] Modules linked in: joydev input_leds mac_hid vmx_crypto ofpart 
crct10dif_vpmsum ipmi_powernv ipmi_devintf at24 uio_pdrv_genirq ipmi_msghandler 
uio cmdlinepart powernv_flash mtd opal_prd ibmpowernv sch_fq_codel ib_iser 
rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas 
hid_generic usbhid hid ast i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm crc32c_vpmsum i40e aacraid 
drm_panel_orientation_quirks
  [  398.518769] CPU: 0 PID: 10529 Comm: bash Kdump: loaded Not tainted 
4.18.0-21-generic #22-Ubuntu
  [  398.518881] NIP:  c082a3a8 LR: c082b234 CTR: 
c00

[Kernel-packages] [Bug 1835322] Re: [linux-azure] panic in ext4_resize_fs() found during storage testing

[Terry Rudd]

** Changed in: linux-azure (Ubuntu Cosmic)
   Status: Fix Committed => Invalid

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

Title:
  [linux-azure] panic in ext4_resize_fs()  found during storage testing

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure source package in Cosmic:
  Invalid

Bug description:
  A panic was observed during file system testing.  The trace is the
  following:

  [ 8783.243586] kernel BUG at 
/build/linux-azure-3iFJ9j/linux-azure-4.18.0/fs/ext4/resize.c:266!
  [ 8783.252751] invalid opcode:  [#1] SMP PTI
  [ 8783.256735] CPU: 7 PID: 39476 Comm: resize2fs Not tainted 
4.18.0-1023-azure #24~18.04.1-Ubuntu
  [ 8783.256735] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [ 8783.256735] RIP: 0010:ext4_resize_fs+0x73b/0xf10
  [ 8783.256735] Code: 50 ff ff ff 41 8b 75 10 4d 8b 65 00 85 f6 0f 94 c0 4d 85 
e4 0f 94 c1 09 c8 83 bd 5c ff ff ff 01 7e 48 84 c0 0f 84 43 06 00 00 <0f> 0b 48 
c7 c2 68 a7 8d 8f 48 c7 c6 00 fb 88 8f 4c 89 f7 e8 0d f8
  [ 8783.256735] RSP: 0018:984e8dce7cb0 EFLAGS: 00010202
  [ 8783.256735] RAX: 00205c01 RBX: 001f RCX: 

  [ 8783.256735] RDX: 8b1dbe1367d0 RSI:  RDI: 

  [ 8783.256735] RBP: 984e8dce7d88 R08: 984e8dce7d4c R09: 
984e8dce7d54
  [ 8783.256735] R10: 0120 R11: 0001 R12: 
8b1dbe136800
  [ 8783.256735] R13: 8b1d74aefe80 R14: 8b1dbdeb9000 R15: 

  [ 8783.256735] FS:  7f213fed30c0() GS:8b1ded7c() 
knlGS:
  [ 8783.256735] CS:  0010 DS:  ES:  CR0: 80050033
  [ 8783.256735] CR2: 556aa08ae9b8 CR3: 001b8e324005 CR4: 
003606e0
  [ 8783.256735] DR0:  DR1:  DR2: 

  [ 8783.256735] DR3:  DR6: fffe0ff0 DR7: 
0400
  [ 8783.256735] Call Trace:
  [ 8783.256735]  ? security_capable+0x3c/0x60
  [ 8783.256735]  ext4_ioctl+0xf91/0x14d0
  [ 8783.256735]  ? audit_filter_rules.constprop.14+0x325/0xf90
  [ 8783.256735]  ? audit_filter_rules.constprop.14+0x24b/0xf90
  [ 8783.256735]  do_vfs_ioctl+0xa8/0x630
  [ 8783.256735]  ksys_ioctl+0x75/0x80
  [ 8783.256735]  __x64_sys_ioctl+0x1a/0x20
  [ 8783.256735]  do_syscall_64+0x6a/0x1a0
  [ 8783.256735]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 8783.256735] RIP: 0033:0x7f213f3825d7
  [ 8783.256735] Code: b3 66 90 48 8b 05 b1 48 2d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 81 48 2d 00 f7 d8 64 89 01 48
  [ 8783.256735] RSP: 002b:7ffe8effd688 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 8783.256735] RAX: ffda RBX: 556aa08aa980 RCX: 
7f213f3825d7
  [ 8783.256735] RDX: 7ffe8effd7d0 RSI: 40086610 RDI: 
0004
  [ 8783.256735] RBP: 0004 R08:  R09: 

  [ 8783.256735] R10:  R11: 0246 R12: 
556aa08ac980
  [ 8783.256735] R13: 7ffe8effd7d0 R14: 556aa08a92d0 R15: 


  
  This issue is resolved by the following upstream commit:
  f96c3ac8dfc2 ("ext4: fix crash during online resizing")

  
  Commit f96c3ac8dfc2 is in mainline as of v5.1-rc1.  This commit was requested 
in the upstream stable kernels.  However, the Ubuntu kernels are EOL upstream.  
Please include this commit in the 16.04 and 18.04 linux-azure kernels.

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

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

[Kernel-packages] [Bug 1860986] Re: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel

[Terry Rudd]

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

Title:
  openvswitch: same tcp session encapsulated with different udp src port
  for ovs vxlan tunnel

Status in linux package in Ubuntu:
  New

Bug description:
  [SRU Justification]

  [Impact]

  Packets encapsulated into a vxlan tunnel with openvswitch don't have
  the same udp source port for the first packet and the following ones
  of the same  TCP flow in a DOCKER scenario usecase.

  In fact, when using the kernel datapath, the upcall don't include skb
  hash info relatived. As VXLAN module uses the skb hash to select UDP
  src port, the source port is different for the first packet.

  More information can be found here:
  https://mail.openvswitch.org/pipermail/ovs-dev/2019-October/364062.html

  This has been fixed in v5.5 by the following upstream commit:
  bd1903b7c4596 ("net: openvswitch: add hash info to upcall")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/openvswitch?id=bd1903b7c4596ba6f7677d0dfefd05ba5876707d

  The bug exists since the beginning of vxlan support in openvswitch.

  == Fix ==

  Backport the requested patches to Focal (5.4), Eoan (5.3), Bionic (4.15) and
  Xenial (4.4).

  == Risk of Regression ==

  This patch only add hash information when we do upcall, thus the risk
  should be low.

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

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

[Kernel-packages] [Bug 1881096] Re: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf

[Terry Rudd]

** Also affects: linux (Ubuntu Focal)
   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/1881096

Title:
  [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or
  available with perf

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New

Bug description:
  ---Problem Description---
  ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable 
with perf stat -e
   
  ---uname output---
  Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 
s390x s390x s390x GNU/Linux
   
  Machine Type = z15 8561 
   
  ---Steps to Reproduce---
   lscpumf -c gives a list of available counters, but a few of them are not 
usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR
  perf list is also not offering these counters.

  
  A solution will be a backport to 20.04, and tried to made available for next 
SRU , code needed before 06-12. 

  Addl Info from Dev:
  I have downloaded the following repository 
  https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal
  and checked out branch master-next.

  Both patches appended apply without warning and the compilation showed
  no error.

  For the perf tool:
  e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM 
z15

  For the s390 kernel
  d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15

  All accepted for kernel 5.7 rc1

  Please include both patches into Ubuntu 20.04

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

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

[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

[Terry Rudd]

Thiago, can you be more specific about what you're seeing and with
exactly which kernel?

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

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  SRU Justification

  Impact: The KVP daemon fails to start on first boot due to being
  started before the hv_kvp device appears.

  Fix: Update the hv-kvp-daemon service file to start the daemon after
  device node appears.

  Regression Potential: The changes are only to the hv-kvp-daemon
  service file and adding a udev rule, so the worst case regression
  would be that the service does not start. In testing the service did
  start as expected.

  Test Case: See comment #15.

  ---

  
  Launching a recent daily image of disco on azure results in a VM in which the 
hv-kvp-daemon.service fails to start:

  $ systemctl status -o cat hv-kvp-daemon.service
  ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
     Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
pr
     Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 
11min a
   Main PID: 219 (code=exited, status=1/FAILURE)

  Started Hyper-V KVP Protocol Daemon.
  KVP starting; pid is:219
  open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory
  hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE
  hv-kvp-daemon.service: Failed with result 'exit-code'.

  The instance was created with:
  $ az vm create --resource-group [redacted] --image 
Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name 
disco-0313

  As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the 
hv-kvp-daemon.service starts, but it is available a few seconds later. Manually 
starting the daemon once I can ssh in works.
  ---
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure 
root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1011-azure N/A
   linux-backports-modules-4.18.0-1011-azure  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco uec-images
  Uname: Linux 4.18.0-1011-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

[Terry Rudd]

Thank you Thiago, we will investigate further.

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

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  SRU Justification

  Impact: The KVP daemon fails to start on first boot due to being
  started before the hv_kvp device appears.

  Fix: Update the hv-kvp-daemon service file to start the daemon after
  device node appears.

  Regression Potential: The changes are only to the hv-kvp-daemon
  service file and adding a udev rule, so the worst case regression
  would be that the service does not start. In testing the service did
  start as expected.

  Test Case: See comment #15.

  ---

  
  Launching a recent daily image of disco on azure results in a VM in which the 
hv-kvp-daemon.service fails to start:

  $ systemctl status -o cat hv-kvp-daemon.service
  ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
     Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
pr
     Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 
11min a
   Main PID: 219 (code=exited, status=1/FAILURE)

  Started Hyper-V KVP Protocol Daemon.
  KVP starting; pid is:219
  open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory
  hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE
  hv-kvp-daemon.service: Failed with result 'exit-code'.

  The instance was created with:
  $ az vm create --resource-group [redacted] --image 
Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name 
disco-0313

  As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the 
hv-kvp-daemon.service starts, but it is available a few seconds later. Manually 
starting the daemon once I can ssh in works.
  ---
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure 
root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1011-azure N/A
   linux-backports-modules-4.18.0-1011-azure  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco uec-images
  Uname: Linux 4.18.0-1011-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

[Terry Rudd]

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

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

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

** Changed in: linux (Ubuntu)
   Status: Fix Released => 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/1820063

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New
Status in linux source package in Disco:
  Fix Released

Bug description:
  SRU Justification

  Impact: The KVP daemon fails to start on first boot due to being
  started before the hv_kvp device appears.

  Fix: Update the hv-kvp-daemon service file to start the daemon after
  device node appears.

  Regression Potential: The changes are only to the hv-kvp-daemon
  service file and adding a udev rule, so the worst case regression
  would be that the service does not start. In testing the service did
  start as expected.

  Test Case: See comment #15.

  ---

  
  Launching a recent daily image of disco on azure results in a VM in which the 
hv-kvp-daemon.service fails to start:

  $ systemctl status -o cat hv-kvp-daemon.service
  ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
     Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
pr
     Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 
11min a
   Main PID: 219 (code=exited, status=1/FAILURE)

  Started Hyper-V KVP Protocol Daemon.
  KVP starting; pid is:219
  open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory
  hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE
  hv-kvp-daemon.service: Failed with result 'exit-code'.

  The instance was created with:
  $ az vm create --resource-group [redacted] --image 
Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name 
disco-0313

  As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the 
hv-kvp-daemon.service starts, but it is available a few seconds later. Manually 
starting the daemon once I can ssh in works.
  ---
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure 
root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1011-azure N/A
   linux-backports-modules-4.18.0-1011-azure  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco uec-images
  Uname: Linux 4.18.0-1011-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1836708] Re: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10]

[Terry Rudd]

** Also affects: linux (Ubuntu Focal)
   Importance: High
 Assignee: Andy Whitcroft (apw)
   Status: Triaged

** Also affects: linux (Ubuntu Eoan)
   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/1836708

Title:
  Please package libbpf (which is done out of the kernel src) in Debian
  [for 19.10]

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Eoan:
  New
Status in linux source package in Focal:
  Triaged

Bug description:
  Hi,
  Debian packages libbpf and so far does so out of the kernel source [1].
  There is some movement to separate that from the kernel source [2] but this 
isn't ready yet. So far it is just a sync of the subtree out of the kernel 
sources.

  Since we do not share our kernel packaging we will not get this for-free 
without doing anything.
  If there will be an ITP about it in Debian I'll let you know and we can abort 
this, but unless that really happens I wanted to ask if you could as well build 
the libbpf* packages for 19.10 and onward?

  Note: this is not the same bpf lib as [3] despite the similarity in
  names.

  Reasoning:
  BPF becomes more and more important in general and is used in the kernel for 
many things. In the case that brought it to my attention it will be a PMD of 
DPDK that will need it to control XDP [4]. And XDP in general is an interesting 
and rising feature for network acceleration - I'd think it would be helpful to 
have this package around in Ubuntu.

  
  ---

  
  FYI here the package info from buster as of today
  root@d10-buster:~# apt-cache show libbpf-dev libbpf4.19
  Package: libbpf-dev
  Source: linux
  Version: 4.19.28-2
  Installed-Size: 350
  Maintainer: Debian Kernel Team 
  Architecture: amd64
  Depends: libbpf4.19 (= 4.19.28-2)
  Description-en: eBPF helper library (development files)
   libbpf is a library for loading eBPF programs and reading and manipulating
   eBPF objects from user-space.
  Description-md5: b8834dcec31d23cd9577fbae4ac6a867
  Multi-Arch: same
  Homepage: https://www.kernel.org/
  Tag: devel::library, role::devel-lib
  Section: libdevel
  Priority: optional
  Filename: pool/main/l/linux/libbpf-dev_4.19.28-2_amd64.deb
  Size: 262268
  MD5sum: 2ab356bbbc421ac44f4106b6cf234f17
  SHA256: f567734a69bc472f2f5a546ace4ad3abf42d69f09d2613bca52a411d78179718

  Package: libbpf4.19
  Source: linux
  Version: 4.19.28-2
  Installed-Size: 318
  Maintainer: Debian Kernel Team 
  Architecture: amd64
  Depends: libc6 (>= 2.26), libelf1 (>= 0.131)
  Description-en: eBPF helper library (shared library)
   libbpf is a library for loading eBPF programs and reading and manipulating
   eBPF objects from user-space.
  Description-md5: 320aac663a5bd3caf223c7aa27857113
  Multi-Arch: same
  Homepage: https://www.kernel.org/
  Tag: role::shared-lib
  Section: libs
  Priority: optional
  Filename: pool/main/l/linux/libbpf4.19_4.19.28-2_amd64.deb
  Size: 259924
  MD5sum: bbb27965530e4101d43b7226fd563840
  SHA256: 18fdf5da4a90c8f42dedb8db510324d09d28f11eb2fa1b364508b14a95d5179b

  
  ---

  
  [1]: https://packages.debian.org/sid/libbpf-dev
  [2]: https://github.com/libbpf/libbpf
  [3]: https://github.com/iovisor/bcc
  [4]: https://www.iovisor.org/technology/xdp

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

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

[Kernel-packages] [Bug 1836708] Re: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10]

[Terry Rudd]

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

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

Title:
  Please package libbpf (which is done out of the kernel src) in Debian
  [for 19.10]

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Triaged

Bug description:
  Hi,
  Debian packages libbpf and so far does so out of the kernel source [1].
  There is some movement to separate that from the kernel source [2] but this 
isn't ready yet. So far it is just a sync of the subtree out of the kernel 
sources.

  Since we do not share our kernel packaging we will not get this for-free 
without doing anything.
  If there will be an ITP about it in Debian I'll let you know and we can abort 
this, but unless that really happens I wanted to ask if you could as well build 
the libbpf* packages for 19.10 and onward?

  Note: this is not the same bpf lib as [3] despite the similarity in
  names.

  Reasoning:
  BPF becomes more and more important in general and is used in the kernel for 
many things. In the case that brought it to my attention it will be a PMD of 
DPDK that will need it to control XDP [4]. And XDP in general is an interesting 
and rising feature for network acceleration - I'd think it would be helpful to 
have this package around in Ubuntu.

  
  ---

  
  FYI here the package info from buster as of today
  root@d10-buster:~# apt-cache show libbpf-dev libbpf4.19
  Package: libbpf-dev
  Source: linux
  Version: 4.19.28-2
  Installed-Size: 350
  Maintainer: Debian Kernel Team 
  Architecture: amd64
  Depends: libbpf4.19 (= 4.19.28-2)
  Description-en: eBPF helper library (development files)
   libbpf is a library for loading eBPF programs and reading and manipulating
   eBPF objects from user-space.
  Description-md5: b8834dcec31d23cd9577fbae4ac6a867
  Multi-Arch: same
  Homepage: https://www.kernel.org/
  Tag: devel::library, role::devel-lib
  Section: libdevel
  Priority: optional
  Filename: pool/main/l/linux/libbpf-dev_4.19.28-2_amd64.deb
  Size: 262268
  MD5sum: 2ab356bbbc421ac44f4106b6cf234f17
  SHA256: f567734a69bc472f2f5a546ace4ad3abf42d69f09d2613bca52a411d78179718

  Package: libbpf4.19
  Source: linux
  Version: 4.19.28-2
  Installed-Size: 318
  Maintainer: Debian Kernel Team 
  Architecture: amd64
  Depends: libc6 (>= 2.26), libelf1 (>= 0.131)
  Description-en: eBPF helper library (shared library)
   libbpf is a library for loading eBPF programs and reading and manipulating
   eBPF objects from user-space.
  Description-md5: 320aac663a5bd3caf223c7aa27857113
  Multi-Arch: same
  Homepage: https://www.kernel.org/
  Tag: role::shared-lib
  Section: libs
  Priority: optional
  Filename: pool/main/l/linux/libbpf4.19_4.19.28-2_amd64.deb
  Size: 259924
  MD5sum: bbb27965530e4101d43b7226fd563840
  SHA256: 18fdf5da4a90c8f42dedb8db510324d09d28f11eb2fa1b364508b14a95d5179b

  
  ---

  
  [1]: https://packages.debian.org/sid/libbpf-dev
  [2]: https://github.com/libbpf/libbpf
  [3]: https://github.com/iovisor/bcc
  [4]: https://www.iovisor.org/technology/xdp

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

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

[Kernel-packages] [Bug 1852794] Re: Dell PowerEdge R630 won't boot with 4.4.0-168.197 and later

[Terry Rudd]

Hello @Bjorn, we're trying to determine if we have a regression with
this bug, could you please try and get back to us ASAP on the questions
that khaled has asked for follow up on.  Thanks

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

Title:
  Dell PowerEdge R630 won't boot with 4.4.0-168.197 and later

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

Bug description:
  One of our Dell R630 machines in our CI environment won't boot with
  the 4.4.0-168.197 kernel in xenial.

  I've confirmed that it does boot with 4.4.0-166.195, but it won't boot
  with neither 4.4.0-168.197 nor 4.4.0-169.198. I haven't tried with
  4.4.0-167.196, but I'll see if I can try with that one as well.

  I can't give any error message. I first saw this when PXE booting the
  machine. I can see that it downloads the kernel and initrd, but then
  the machine just reboots.

  I also tried installing xenial on the machine, and the same happens
  with grub. No output in the console after selecting the kernel in the
  grub menu, it just reboots.

  I'm attaching the lshw outputs for the two Dell machines we have.
  natasha is the one that isn't working, while opelt works.

  The machine is in our CI lab, and we can provide you access to it for
  more debugging.

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

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

[Kernel-packages] [Bug 1823655] Re: Second SD card on RPi3 CM3 on Ubuntu Core 18 does not work

[Terry Rudd]

** Changed in: linux-raspi2 (Ubuntu)
   Status: Expired => In Progress

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

Title:
  Second SD card on RPi3 CM3 on Ubuntu Core 18 does not work

Status in linux-raspi2 package in Ubuntu:
  In Progress
Status in linux-raspi2 source package in Bionic:
  New

Bug description:
  As suggested in following thread;

  https://forum.snapcraft.io/t/second-sd-card-on-rpi3-cm3-with-ubuntu-
  core-18/10465

  a bug report.

  The configuration works for a Ubuntu Core 16 device.

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

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

[Kernel-packages] [Bug 1853930] [NEW] io RAID Read 100% Rand 128K 4 jobs depth 8 test for Config 1 shows -11.23 % drop in 4.15.0-70.77 than 4.15.0-68.75

[Terry Rudd]

Public bug reported:

This is a test bug to verify that we can instrument each new bug found
in DGX-2 Performance Testing and to refine how we create and manage the
bugs

summary:- fio RAID Read 100% Rand 128K 4 jobs depth 8 test shows -11.32 
% drop in
- 4.15.0-70.77 than 4.15.0-68.75
+ fio RAID Read 100% Rand 128K 4 jobs depth 8 test for Config 1 shows
+ -11.23 % drop in 4.15.0-70.77 than 4.15.0-68.75

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

Title:
  io RAID Read 100% Rand 128K 4 jobs depth 8 test for Config 1 shows
  -11.23 % drop in 4.15.0-70.77 than 4.15.0-68.75

Status in linux package in Ubuntu:
  New

Bug description:
  This is a test bug to verify that we can instrument each new bug found
  in DGX-2 Performance Testing and to refine how we create and manage
  the bugs

  summary:  - fio RAID Read 100% Rand 128K 4 jobs depth 8 test shows -11.32 
% drop in
  - 4.15.0-70.77 than 4.15.0-68.75
  + fio RAID Read 100% Rand 128K 4 jobs depth 8 test for Config 1 shows
  + -11.23 % drop in 4.15.0-70.77 than 4.15.0-68.75

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

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

[Kernel-packages] [Bug 1853928] [NEW] Stream Scale Rate Test shows -11.99% lower for Config 1 in 4.15.0-70.77 than 4.15.0-68.75

[Terry Rudd]

Public bug reported:

This is a test bug to verify that we can instrument each new bug found
in DGX-2 Performance Testing and to refine how we create and manage the
bugs

summary:- Stream Scale Rate is -11.99% lower for Config 1 in 
4.15.0-70.77 than
- 4.15.0-68.75
+ Stream Scale Rate Test shows -11.99% lower for Config 1 in 4.15.0-70.77
+ than 4.15.0-68.75

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

Title:
  Stream Scale Rate Test shows -11.99% lower for Config 1 in
  4.15.0-70.77 than 4.15.0-68.75

Status in linux package in Ubuntu:
  New

Bug description:
  This is a test bug to verify that we can instrument each new bug found
  in DGX-2 Performance Testing and to refine how we create and manage
  the bugs

  summary:  - Stream Scale Rate is -11.99% lower for Config 1 in 
4.15.0-70.77 than
  - 4.15.0-68.75
  + Stream Scale Rate Test shows -11.99% lower for Config 1 in 4.15.0-70.77
  + than 4.15.0-68.75

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

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

[Kernel-packages] [Bug 1853927] [NEW] Stream Scale Time is 12% higher in 4.15.0-70.77 than 4.15.0-68.75

[Terry Rudd]

Public bug reported:

This is a test bug to verify that we can instrument each new bug found
in DGX-2 Performance Testing and to refine how we create and manage the
bugs

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

Title:
  Stream Scale Time is 12% higher in 4.15.0-70.77 than 4.15.0-68.75

Status in linux package in Ubuntu:
  New

Bug description:
  This is a test bug to verify that we can instrument each new bug found
  in DGX-2 Performance Testing and to refine how we create and manage
  the bugs

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

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

[Kernel-packages] [Bug 1860306] Re: Linux kernel 5.3.0-26 breaks nvidia driver

[Terry Rudd]

could you please test with the latest 5.3.0-29 kernel?

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

Title:
  Linux kernel 5.3.0-26 breaks nvidia driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upon installation of kernel update 5.3.0.26.95, after a reboot,
  Second screen would not come on and nvidia control panel was missing majority 
of options
  Graphics driver settings could not be changed and upon reinstallation attempt 
of nvidia driver 390, installation failed and drivers became corrupted. Ended 
up reinstalling OS, but discovered later that booting in an older kernel fixed 
the issue. 

  VERSION.LOG:

  Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21

  Release:

  Description:  Linux Mint 19.3 Tricia
  Release:  19.3

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

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

[Kernel-packages] [Bug 1860306] Re: Linux kernel 5.3.0-26 breaks nvidia driver

[Terry Rudd]

to enable propose - see https://wiki.ubuntu.com/Testing/EnableProposed

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

Title:
  Linux kernel 5.3.0-26 breaks nvidia driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upon installation of kernel update 5.3.0.26.95, after a reboot,
  Second screen would not come on and nvidia control panel was missing majority 
of options
  Graphics driver settings could not be changed and upon reinstallation attempt 
of nvidia driver 390, installation failed and drivers became corrupted. Ended 
up reinstalling OS, but discovered later that booting in an older kernel fixed 
the issue. 

  VERSION.LOG:

  Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21

  Release:

  Description:  Linux Mint 19.3 Tricia
  Release:  19.3

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

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

[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)

[Terry Rudd]

thanks for following up on this

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

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

Title:
  Bluetooth unavailable after updates - Reading Intel version
  information failed (-110)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After 10 days of uptime with automatic updates, I rebooted. Bluetooth,
  which I use every day, is no longer available.

  $ dmesg | grep -i bluetooth
  [4.846072] Bluetooth: Core ver 2.22
  [4.846088] Bluetooth: HCI device and connection manager initialized
  [4.846092] Bluetooth: HCI socket layer initialized
  [4.846094] Bluetooth: L2CAP socket layer initialized
  [4.846096] Bluetooth: SCO socket layer initialized
  [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [5.434082] Bluetooth: BNEP filters: protocol multicast
  [5.434086] Bluetooth: BNEP socket layer initialized
  [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout
  [6.874129] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  $ uname -a
  Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04
  LTS.

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

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

[Kernel-packages] [Bug 1859820] Re: eoan/linux-azure: 5.3.0-1010.11 -proposed tracker

[Terry Rudd]

MSFT had not finished testing

** Changed in: kernel-sru-workflow/security-signoff
   Status: Fix Released => Confirmed

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

Title:
  eoan/linux-azure: 5.3.0-1010.11 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: '1860119'
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Signoff
  phase-changed: Thursday, 30. January 2020 14:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- package in development blackout
security-signoff: Stalled -- waiting for signoff
  trackers:
bionic/linux-azure-5.3: bug 1859819
  variant: debs

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

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

[Kernel-packages] [Bug 1859820] Re: eoan/linux-azure: 5.3.0-1010.11 -proposed tracker

[Terry Rudd]

MSFT had not finished testing

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

Title:
  eoan/linux-azure: 5.3.0-1010.11 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: '1860119'
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Signoff
  phase-changed: Thursday, 30. January 2020 14:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- package in development blackout
security-signoff: Stalled -- waiting for signoff
  trackers:
bionic/linux-azure-5.3: bug 1859819
  variant: debs

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

-- 
Mailing list: https://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 1851446] Re: Backport MPLS patches from 5.3 to 4.15

[Terry Rudd]

On 1/30/20 7:37 AM, Jeff Lane wrote:
> Sam, can you provide a link to your git tree with these commits?
> 

Thanks Jeff,

I'll get these on the notice board.. BTW, 4.15 is a long way back and I
cannot guarantee we can do this without issue.  JFYI.


-- 
Terry

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

Title:
  Backport MPLS patches from 5.3 to 4.15

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Disco:
  New

Bug description:
  Mellanox is requesting a backport of the following commit IDs from 5.3
  back to 4.15.

  Netdevice HW MPLS features are not passed from device driver's
  netdevice to upper netdevice, specifically VLAN and bonding netdevice
  which are created by the kernel when needed.

  This prevents enablement and usage of HW offloads, such as TSO and
  checksumming for MPLS tagged traffic when running via VLAN or bonding
  interface.

  The patches introduce changes to the initialization steps of the VLAN and
  bonding netdevices to inherit the MPLS features from lower netdevices to 
allow the HW offloads.

  Ariel Levkovich (2):
    net: bonding: Inherit MPLS features from slave devices
    net: vlan: Inherit MPLS features from parent device

   drivers/net/bonding/bond_main.c | 11 +++
   net/8021q/vlan_dev.c|  1 +
   2 files changed, 12 insertions(+)

  https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html

  Commit IDs (All landed in 5.3)
  600bb0318c18e9616d97ad123caaa7c5f7bf222c
  8b6912a5019356d7adb1b8a146c9eef5e679bf98
  2e770b507ccde8eedc129946e4b78ceed0a22df2

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

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

[Kernel-packages] [Bug 1861249] Re: clashing with i915 video driver

[Terry Rudd]

Could you please provide more information about your hardware and any
other details?

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

Title:
  clashing with i915 video driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed the new kernel 5.3 but found a black screen at startup.
  Had to remove it and go back to the 5.0 kernel.

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

-- 
Mailing list: https://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 1862239] Re: bionic/linux-azure: 5.0.0-1031.33 -proposed tracker

[Terry Rudd]

On 2/7/20 10:09 PM, Jack Hammons wrote:
> ** Changed in: kernel-sru-workflow/stakeholder-signoff
>Status: Confirmed => Fix Released
> 

Good morning Jack,

The Bionic linux-azure kernel went out about 2 AM Mountain so ~ 1 AM
your time.

Thanks again.
-- 
Terry

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

Title:
  bionic/linux-azure: 5.0.0-1031.33 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1859724
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Security
  phase-changed: Saturday, 08. February 2020 08:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- not ready for security (replication dwell)
  trackers:
bionic/linux-azure/azure-kernel: bug 1862237
  variant: debs

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

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

[Kernel-packages] [Bug 1849493] Re: CONFIG_ANDROID_BINDER_IPC=m is missing in the GCP rolling kernel for bionic

[Terry Rudd]

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Khaled El Mously (kmously)

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

Title:
  CONFIG_ANDROID_BINDER_IPC=m is missing in the GCP rolling kernel for
  bionic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The rolling GCP kernel for bionic is missing
  CONFIG_ANDROID_BINDER_IPC=m which is enabled in the standard Ubuntu
  kernel since 19.04 and available through the HWE kernels in Bionic.

  As we require CONFIG_ANDROID_BINDER_IPC=m for a not released product
  in our kernels it would be great if we can import the relevant config
  changes to the GCP kernel (haven't yet checked our other cloud
  kernels).

  All relevant changes from Christian Brauner to enable binder in the
  Ubuntu kernel are present in the GCP kernel (see
  https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
  gcp/+git/bionic/log/?h=gcp-edge&qt=grep&q=brauner).

  See https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  
bionic.git/commit/debian.master/config/config.common.ubuntu?h=hwe&id=a758aeb0bb0f52ccbee99f850709c57711753b33
  and https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  
bionic.git/commit/debian.master/config/config.common.ubuntu?h=hwe&id=4b44b695fb5ee2f405d0ad4eda2fc2cad856414c
  for the relevant config changes in the Ubuntu kernel from Seth.

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

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

[Kernel-packages] [Bug 1803960] Re: 4.18.0 kernels hang system randomly

[Terry Rudd]

** Changed in: linux (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  4.18.0 kernels hang system randomly

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

Bug description:
  I've been using 18.04 on an Asus T300CHI without issue until I decided
  to switch to the v4.18 kernels from 18.10 via linux-image-lowlatency-
  hwe-18.04-edge.

  Since then the system randomly but regularly completely hangs. Only a
  hard power-off resolves it.

  Frustratingly there are never any clues in the kernel logs so it is
  very difficult to point to anything that might cause it; there is
  never any obvious pattern in the workload, the user interaction, or
  state of the PC when the hang occurs.

  A week ago I switched to the Ubuntu mainline v4.19 builds and that
  resolved the issue.

  I was reminded of it again today when it hung a few minutes ago. After
  the reboot I checked the previous boot log and realised the PC had
  accidentally been booted with the default v4.18 kernel rather than
  v4.19.

  I don't think this report can be debugged but it is worth having a
  tracking bug in case other people experience the same issue with
  v4.18.

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

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

[Kernel-packages] [Bug 1849856] Re: ip commands error with mellanox devices in switchdev mode

[Terry Rudd]

Is there further work to do on this given the apparent resolution of the
problem?

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

Title:
  ip commands error with mellanox devices in switchdev mode

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

Bug description:
  Kernel: using 5.0.0-23-generic from hwe-edge

  Configuring a mellanox connectx device with configured VF's into
  switchdev (rather than legacy) mode result in the ip cli tool erroring
  when trying to query the interface state:

  $ sudo ip link
  Error: Buffer too small for object.
  Dump terminated

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iproute2 4.15.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Fri Oct 25 14:55:36 2019
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1834235] Re: Request backport of ceph commits into bionic Edit

[Terry Rudd]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Connor Kuehl (connork)

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

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

Title:
  Request backport of ceph commits into bionic Edit

Status in linux package in Ubuntu:
  New

Bug description:
  Our internal cluster has run into a few ceph client related issues, which 
were root caused to be resolved by the following commits:
  
https://github.com/ceph/ceph-client/commit/f42a774a2123e6b29bb0ca296e166d0f089e9113
  
https://github.com/ceph/ceph-client/commit/093ea205acd4b047cf5aacabc0c6ffecf198d2a9
  Can you please backport these into bionic?

  3e1d0452edcee ceph: avoid iput_final() while holding mutex or in dispatch 
thread
  1cf89a8dee5e6 ceph: single workqueue for inode related works

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

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

[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures

[Terry Rudd]

Canonical kernel team has this item queued in the hotlist to work on.  I
am assigning to myself to accelerate work

** Changed in: curtin
 Assignee: (unassigned) => Terry Rudd (terrykrudd)

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

Title:
  Tight timeout for bcache removal causes spurious failures

Status in curtin:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  New
Status in linux source package in Eoan:
  Confirmed

Bug description:
  I've had a number of deployment faults where curtin would report
  Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
  deployment of 30+ nodes. Upon retrying the node would usually deploy
  fine. Experimentally I've set the timeout ridiculously high, and it
  seems I'm getting no faults with this. I'm wondering if the timeout
  for removal is set too tight, or might need to be made configurable.

  --- curtin/util.py~ 2018-05-18 18:40:48.0 +
  +++ curtin/util.py  2018-10-05 09:40:06.807390367 +
  @@ -263,7 +263,7 @@
   return _subp(*args, **kwargs)
   
   
  -def wait_for_removal(path, retries=[1, 3, 5, 7]):
  +def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
   if not path:
   raise ValueError('wait_for_removal: missing path parameter')

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

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

[Kernel-packages] [Bug 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open

[Terry Rudd]

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Connor Kuehl (connork)

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

Title:
  4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc
  version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun
  24 10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc-
  kernel_240.snap

  Version signature: 4.15.0-54.58-generic 4.15.18

  Issue is non-deterministic, and happens in roughly 20% of the
  attempts.

  Running on: qemu-kvm, command line:  kvm \
    -bios /usr/share/ovmf/OVMF.fd \
    -smp 2 -m 512 -netdev 
user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \
    -device virtio-net-pci,netdev=mynet0 \
    -drive file=pc.img,format=raw

  Commands that caused the problem:
  cryptsetup -q --type luks2 --key-file  luksFormat /dev/sda4
  LD_PRELOAD=/lib/no-udev.so cryptsetup --type luks2 --key-file  open 
/dev/sda4 crypt-data

  Notes:
  - See https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1589083 for 
more information on the no-udev workaround.
  - The commands are scripted. Also tried to add a 200ms and 1s interval before 
opening the device.

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

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

[Kernel-packages] [Bug 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL

[Terry Rudd]

Alex, 18.10 is EOL as of the end of July so no fix is planned

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

Title:
  Thermald does not set max CPU after reseting the voltage using RAPL

Status in thermald package in Ubuntu:
  Confirmed
Status in thermald source package in Bionic:
  Fix Committed

Bug description:
  Hi,

  I was using Ubuntu 18.10 thermald package, but I noted that, after few
  seconds at max CPU usage (max temp), thermald send the signal to RALP
  to reduce the voltage of the CPU. It set the freq to minimum (800MHz
  in my case). But when the CPU is idle and temp is lowered (35-40ºC) it
  did not send the signal to resume normal operation of the CPU.

  I compiled the latest version of thermald from git
  (https://github.com/intel/thermal_daemon) and now everything works
  fine.

  I started to thought that the problem was the hardware or BIOS
  problem, as I disabled the CPU scaling on the BIOS, but intel_pstate
  continued doing freq scaling (I think for Turbo mode).

  But the real problem was Thermald. The latest version from git works
  really fine and it automatically disables and enable the Intel Turbo
  state and balance the freqs and fan control fine.

  My hardware is a Lenovo Thinkpad P52 with i7-8850H.

  I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7
  processor but with Ubuntu default config (except processor
  family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low-
  Latency Desktop)" and Timer frequency="1000HZ". (Only changed those
  settings from make oldconfig and make deb-pkg).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: thermald (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 14 23:45:01 2019
  InstallationDate: Installed on 2018-12-11 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: thermald
  UpgradeStatus: No upgrade log present (probably fresh install)

  -

  SRU Justification
  ==

  [Impact]
   * As described by the original bug reporter, CPU usage of Lenovo P52 is 
sub-optimal under heavy load.
   * My observation is the machine exhibits a sharp drop of power usage and CPU 
frequency and takes time to slowly ramp up again (refer to the chart at 
https://bit.ly/2OJphB8)
   * Fixed by bisecting and backporting fixes from thermald project.

  [Test Case]
   * One can stress the CPU load of the machine and collect the CPU frequency 
and power usage over time to check for any anamoly. The script at 
https://people.canonical.com/~ypwong/p52_test_cpu.sh can help with this.
   * With the fix, the behaviour should be like this: https://bit.ly/2KA9EXB, a 
consistent power usage can be maintained.

  [Regression Potential]
   * Medium. The fix consists of 7 commits cherry-picked from upstream, these 
changes will affect any machines using RAPL cooling device. The impact may not 
be obvious in normal daily usage but will be manifested during heavy load, 
suggest a longer verification period so that more people can discover any 
adverse effect.

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

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

[Kernel-packages] [Bug 1779640] Re: [Hyper-V] KVP daemon crashes at startup

[Terry Rudd]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

Title:
  [Hyper-V] KVP daemon crashes at startup

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

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  the following issue with the KVP daemon:

  KVP daemon crashes after approximatively 2 minutes of uptime and it enters in 
a failed state. The daemon can be manually started and it enters back in active 
(running) state.
  The error messages from /var/log/syslog after the daemon enters the failed 
state are the following:

  Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with 
result 'exit-code'.
  Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon.

  Note: There was a simmilar issue discussed on this thread
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the
  fixing commit seems to be inclued in this Bionic build.

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

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

[Kernel-packages] [Bug 1813936] Re: kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1813928
   kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!

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

Title:
  kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  happend during normal operation in the background

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-39-generic 4.15.0-39.42
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   hnl1417 F...m pulseaudio
   /dev/snd/controlC0:  hnl1417 F pulseaudio
  Date: Wed Jan 30 21:56:47 2019
  Failure: oops
  HibernationDevice: RESUME=UUID=5835e245-0f6b-49d1-8d73-f7d80ed579cb
  InstallationDate: Installed on 2018-11-14 (76 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 23252F0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23252F0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 100010263594
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn23252F0:pvrThinkPadX230:rvnLENOVO:rn23252F0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 23252F0
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1813999] Re: ubuntu 18.04 linux 4.15.0-44 kernel exception with ThunderBolt display

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1813663
   External monitors does not work anymore 4.15.0-44

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

Title:
  ubuntu 18.04 linux 4.15.0-44 kernel exception with ThunderBolt display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This problem appeared on the first boot Linux 4.15.0-44, and was not
  present in previous kernels, including 4.15.0-43. The problem occurs
  every time with 4.15.0-44. Since the problem occurred, 4.15.0-43
  continues to work w/o issues.  The log should show multiple boots with
  both kernels, both Xorg and Wayland.

  The problem occurs wheen connecting a TB-16 dock-connected external
  display, or when plugging in a TB-16 dock-connected external display
  during an X session.  The symptoms are different with Xorg and
  Wayland, but both cause kernel exceptions.  With Xorg the system
  freezes up, but will still ping.  With Wayland the display goes black,
  but userland is still accessible.  With Xorg the system is gone before
  the Login screen appears.  With Wayland the login screen is okay, but
  the problem occurs immediately after a successful login. The system
  runs normally with both Xorg and Wayland so long as the external
  display is not connected.

  The problem does not occur if the display is plugged in through a USBc
  (non-ThunderBolt) port.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1982 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 30 16:49:20 2019
  HibernationDevice: RESUME=UUID=d15ecb23-8691-42a1-9909-a56f934b536c
  InstallationDate: Installed on 2018-11-19 (72 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=a73e2d3e-5ce3-4130-917d-d116c1316153 ro net.ifnames=0 
mem_sleep_default=deep
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 02MJVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1813957] Re: T480: closed lid and touchpad

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1813663
   External monitors does not work anymore 4.15.0-44

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

Title:
  T480: closed lid and touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After closing the lid and working with externals screens and mouse and
  keyboard, the mouse cursor jumps. The effect is caused by touchpad:
  the workaround is to completely disable it in settings.

  
  This bug is 4.15.0-44 kernel specific. With the previous version 4.15.0-43 
the problem was not observed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  afiergol   9976 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   9976 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   9976 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 30 17:29:35 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (300 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (161 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1814009] Re: Mounting certain LVM2 LV fails with "Structure needs cleaning"

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1813727
   kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled

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

Title:
  Mounting certain LVM2 LV fails with "Structure needs cleaning"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  REGRESSION.

  Per the reports from others as well in
   and
  , some LVM2 LVs are failing to mount with the
  error:

  mount(2) system call failed: Structure needs cleaning.

  e2fsck -f reports things are fine.

  Reverting my kernel package from linux-image-4.15.0-44-generic to
  linux-image-4.15.0-43-generic solved the problem for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
'/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Wed Jan 30 19:21:13 2019
  HibernationDevice: RESUME=UUID=0925b709-2477-4f37-8207-0313728c5c68
  InstallationDate: Installed on 2012-08-18 (2356 days ago)
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/diskvg-ubuntu_root_lv 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.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (256 days ago)
  WifiSyslog:
   
  dmi.bios.date: 11/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2201:bd11/25/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx: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.

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

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

[Kernel-packages] [Bug 1814151] Re: Screen freezes

[Terry Rudd]

I believe this bug a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663. Please
confirm by reviewing that bug to see if your conditions are similar.  At
your earliest convenience could you please try the 4.15.0-45 to it it
resolves your issue?

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

Title:
  Screen freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Screen freezes after wake up from suspend mode on Acer Aspire V3-571G.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrey 2549 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 20:57:28 2019
  HibernationDevice: RESUME=UUID=a27531fc-cfed-43e8-a74e-35d79f38791c
  InstallationDate: Installed on 2018-08-26 (158 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Acer Aspire V3-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=ef195b2c-8777-41a7-ba3d-9fcf3765739d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd12/04/2012:svnAcer:pnAspireV3-571G:pvrV2.09:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.09:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1814117] Re: System hangs when a Dell WD15 dock station is plugged

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1813663
   External monitors does not work anymore 4.15.0-44

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

Title:
  System hangs when a Dell WD15 dock station is plugged

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With the kernel packets in version 4.15.0-43 (the ones I'm running to report 
this bug), I can plug my Dell WD15 dock station normally on the USB-C connector 
of my laptop, before or after booting it: everything works fine.
  When I upgrade to the latest kernel (i.e. install linux-XXX-4.15.0.44 with 
XXX=image, headers, modules and modules-extra), my laptop cannot boot ubuntu 
with the WD15 dock plugged in. It boots normally without WD15, can use normally 
a USB-C memory stick plugged in the same connector, but hangs whenever the WD15 
dock is plugged in: black screen, no reaction to the laptop keyboard even when 
caps lock is pressed (the corresponding LED does not turn on), must reboot with 
a long action on the  power-off button.
  The problem is really specific to 4.15.0.44 and is not present in 4.15.0.43. 
Whit the new version installed, choosing the old kernel in the GRUB menu gives 
a working system. I now un-installed the new version and it works well.

  Enclosed file: Portion of /var/log/kern.log showing a boot sequence
  with WD15 plugged. It begins to differ from the sequence with WD15
  unplugged at line 685 (looking for usb devices), contains a warning at
  line 850 and a OOPS at line 951

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1248 F pulseaudio
delannoy   1712 F pulseaudio
  Date: Thu Jan 31 15:42:55 2019
  InstallationDate: Installed on 2017-09-20 (497 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Latitude 5480
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=4266b673-814e-442f-b0fb-f65e55c0c0ab ro quiet splash vt.handoff=1
  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.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-15 (261 days ago)
  dmi.bios.date: 11/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0T96NR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/12/2018:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn0T96NR:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5480
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1814084] Re: The screen went black - had to restart. Have happened several times today..

[Terry Rudd]

It is possible this bug a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663. Please
confirm by reviewing that bug to see if your conditions are similar. At
your earliest convenience could you please try the 4.15.0-45 to it it
resolves your issue?

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

Title:
  The screen went black - had to restart. Have happened several times
  today..

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The screen went black - had to restart. Have happened several times
  today..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  llk1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 12:35:03 2019
  HibernationDevice: RESUME=UUID=42fc63eb-406d-4733-b480-1ad65586
  InstallationDate: Installed on 2018-10-25 (98 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP EliteBook 850 G5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=beba2df7-1067-4875-bc5e-ae2e91661d24 ro quiet splash acpi_osi= 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q78 Ver. 01.03.00
  dmi.board.name: 83B2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 04.53.00
  dmi.chassis.asset.tag: 5CG8398P9Y
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.03.00:bd07/18/2018:svnHP:pnHPEliteBook850G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.53.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 850 G5
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1814015] Re: After upgrade to kernel .44 docking station and external monitors not working

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1813663
   External monitors does not work anymore 4.15.0-44

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

Title:
  After upgrade to kernel .44 docking station and external monitors not
  working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading the kernel has resulted in displays crashing and external
  displays not working.

  Release: Ubuntu 18.0.4 LTS

  dist-upgrade

  Normal boot is expected - after entering encryption password for hard
  disk get black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 30 20:45:30 2019
  InstallationDate: Installed on 2016-11-10 (811 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-05-17 (258 days ago)
  VarLogDistupgradeTermlog:

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

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

[Kernel-packages] [Bug 1813179] Re: Bionic (4.15.0-43.46), x86: mprotect(..., PROT_NONE) failure for VM_PFNMAP VMAs (fixed in mainline)

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1799237
   mprotect fails on ext4 with dax

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

Title:
  Bionic (4.15.0-43.46), x86: mprotect(..., PROT_NONE) failure for
  VM_PFNMAP VMAs (fixed in mainline)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Version:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

  Ubuntu 4.15.0-43.46-generic 4.15.18

  This is a bug that has been fixed in mainline. When calling
  'mprotect(..., PROT_NONE)' on a virtual memory area with VM_PFNMAP set
  it fails with a EACCESS (Permission denied) error even though it is a
  valid call. In my particular case this happens when calling
  mprotect(..., PROT_NONE) on a set of pages within the range of an
  Intel SGX enclave.

  The bug is fully described on the Linux kernel mailing list here:
  https://lkml.org/lkml/2018/8/16/697

  The bug has been fixed in mainline in August, see
  
https://github.com/torvalds/linux/commit/f19f5c49bbc3ffcc9126cc245fc1b24cc29f4a37

  According to https://launchpad.net/ubuntu/+source/linux/+changelog the
  patch has been backported to Xenial and Cosmic, but not yet to Bionic.

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

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

[Kernel-packages] [Bug 1814628] Re: divide error: 0000 with Ubuntu 18.04

[Terry Rudd]

Tony, Thank you for reporting this issue.  
1) Can you please provide any information related to the kernel that you are 
using and conditions prior to this crash?
   a) what kernel are you running?  What has changed in the last week?
   b) do you have updated Dell System firmware?
   c) do you have any hardware errors logged?
2) Have you rebooted the system?
   a) does it cleanly pass selftest?
   b) does it boot single user mode?
   c) when you let it boot without interruption, which init stage do you see 
failure (if repeatable) occur?
   d) if it passes init stage 4 and is the virtualized environment comes up is 
it stable?

Please note: It is difficult to successfully determine root cause
without logs, dmesg. etc. or knowing the conditions of this system prior
to this crash.

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

Title:
  divide error:  with Ubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Got a host running lots of virtual machines crashing today with the
  following terminal output (if that's to any help):

  [3430458.298979] divide error:  [#1] SMP PTI
  [3430458.304484] Modules linked in: cpuid vhost_net vhost tap 
nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink 
kvm_intel kvm irqbypass rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace 
sunrpc cachefiles fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge ebtable_filter ebtables ip6table_filter ip6_tables devlink 
iptable_filter 8021q garp mrp stp llc bonding ipmi_ssif intel_rapl sb_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp dcdbas intel_cstate 
intel_rapl_perf ipmi_si mei_me ipmi_devintf lpc_ich mei shpchp ipmi_msghandler 
acpi_power_meter mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi
  [3430458.389747]  scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul mgag200 
crc32_pclmul i2c_algo_bit ghash_clmulni_intel ttm pcbc mxm_wmi drm_kms_helper 
bnx2x aesni_intel syscopyarea sysfillrect aes_x86_64 sysimgblt fb_sys_fops 
crypto_simd glue_helper ptp cryptd drm pps_core ahci mdio libahci libcrc32c wmi 
[last unloaded: irqbypass]
  [3430458.440756] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.15.0-43-generic 
#46-Ubuntu
  [3430458.450411] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 
01/26/2018
  [3430458.460008] RIP: 0010:update_group_capacity+0x19d/0x1f0
  [3430458.467098] RSP: 0018:91043ec03bd8 EFLAGS: 00010247
  [3430458.474207] RAX: 006314d6 RBX: 0001 RCX: 
024d
  [3430458.483490] RDX:  RSI:  RDI: 
00022880
  [3430458.492769] RBP: 91043ec03c00 R08: 9104376dc940 R09: 
1dcd6500
  [3430458.502071] R10: 91043ec0 R11: 0001 R12: 
910437625000
  [3430458.511391] R13: 9104376dc940 R14:  R15: 
91043ec03c30
  [3430458.520724] FS:  () GS:91043ec0() 
knlGS:
  [3430458.531161] CS:  0010 DS:  ES:  CR0: 80050033
  [3430458.538994] CR2: 00010960b008 CR3: 003f8300a002 CR4: 
003626e0
  [3430458.548416] DR0:  DR1:  DR2: 

  [3430458.557858] DR3:  DR6: fffe0ff0 DR7: 
0400
  [3430458.567298] Call Trace:
  [3430458.571507]  
  [3430458.575253]  find_busiest_group+0xff/0x9c0
  [3430458.581327]  load_balance+0x164/0x9c0
  [3430458.586928]  ? sched_clock+0x9/0x10
  [3430458.592347]  ? sched_clock_cpu+0x11/0xb0
  [3430458.598249]  rebalance_domains+0x245/0x2d0
  [3430458.604372]  run_rebalance_domains+0x139/0x1f0
  [3430458.610901]  __do_softirq+0xe4/0x2bb
  [3430458.616459]  irq_exit+0xb8/0xc0
  [3430458.621538]  scheduler_ipi+0xea/0x130
  [3430458.627201]  smp_reschedule_interrupt+0x39/0xe0
  [3430458.633860]  reschedule_interrupt+0x84/0x90
  [3430458.640138]  
  [3430458.644096] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0
  [3430458.651289] RSP: 0018:a90100107e68 EFLAGS: 0246 ORIG_RAX: 
ff02
  [3430458.661431] RAX: 91043ec22880 RBX: 000c2ffbd05252a7 RCX: 
001f
  [3430458.671114] RDX: 000c2ffbd05252a7 RSI: ff1e5f04e459 RDI: 

  [3430458.680819] RBP: a90100107ea8 R08:  R09: 
0d17
  [3430458.690557] R10: a90100107e38 R11: 0eca R12: 
c900ff401f58
  [3430458.700303] R13: 0004 R14: 9bb71d18 R15: 

  [3430458.710075]  ? cpuidle_enter_state+0x97/0x2f0
  [3430458.716723]  cpuidle_enter+

[Kernel-packages] [Bug 1814805] Re: System fails to boot

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1813657
   4.18.0-14 doesn't boot past grub

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

Title:
  System fails to boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When attempting to boot the machine, it freezes before it reaches the
  disk decryption password prompt. I don't get this issue with linux-
  image-4.18.0-13-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-14-generic 4.18.0-14.15
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sjm2291 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  5 17:46:07 2019
  InstallationDate: Installed on 2018-11-13 (83 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 6474E63
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET94WW (3.24 )
  dmi.board.name: 6474E63
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474E63:pvrThinkPadT400:rvnLENOVO:rn6474E63:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T400
  dmi.product.name: 6474E63
  dmi.product.version: ThinkPad T400
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1814068] Re: Crash/black screen when suspend

[Terry Rudd]

Does the 4.15.0-45 kernel resolve this issues?

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

Title:
  Crash/black screen when suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Suspend does not fully work: The screen goes to black and then
  crashes. Ctrl+Alt+Del does not work, neither switching to any other
  tty.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cobolt 2522 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Jan 31 11:23:51 2019
  HibernationDevice: RESUME=/dev/mapper/wisepad--vg-swap_1
  MachineType: LENOVO 20HES0FX00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-44-generic 
root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-06-15 (229 days ago)
  dmi.bios.date: 07/04/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET77W (1.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HES0FX00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1QET77W(1.52):bd07/04/2018:svnLENOVO:pn20HES0FX00:pvrThinkPadT470:rvnLENOVO:rn20HES0FX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470
  dmi.product.name: 20HES0FX00
  dmi.product.version: ThinkPad T470
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1814084] Re: The screen went black - had to restart. Have happened several times today..

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1813663
   External monitors does not work anymore 4.15.0-44

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

Title:
  The screen went black - had to restart. Have happened several times
  today..

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The screen went black - had to restart. Have happened several times
  today..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  llk1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 12:35:03 2019
  HibernationDevice: RESUME=UUID=42fc63eb-406d-4733-b480-1ad65586
  InstallationDate: Installed on 2018-10-25 (98 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP EliteBook 850 G5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=beba2df7-1067-4875-bc5e-ae2e91661d24 ro quiet splash acpi_osi= 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q78 Ver. 01.03.00
  dmi.board.name: 83B2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 04.53.00
  dmi.chassis.asset.tag: 5CG8398P9Y
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.03.00:bd07/18/2018:svnHP:pnHPEliteBook850G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.53.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 850 G5
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://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 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

[Terry Rudd]

On 02/11/2019 05:18 PM, Marcelo Cerri wrote:
> Does the problem happen in a gen1 or gen2 VM?
> 
Will ask
Terry

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

Title:
  kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu stuck on booting on HyperV Server 2008R2.
  I saw kernel messages, seems to load ram image the boot is stuck.
  Seems to be a problem with hyperv drivers propably harddrive.
  Reverted back to the previous kernel.

  Description:Ubuntu 18.04.1 LTS
  Release:18.04Description:Ubuntu 18.04.1 LTS
  Release:18.04
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 31 08:52 seq
   crw-rw 1 root audio 116, 33 Jan 31 08:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  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
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090004
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1815808] Re: Thunderbolt Ethernet high-traffic exception

[Terry Rudd]

Gene, this bug appears to be a duplicate of one you filed on 1/30/2019.
I will duplicate this one over to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813999

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

Title:
  Thunderbolt Ethernet high-traffic exception

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running iperf3 on Dell XP-15 with TB-10 Thunderbolt dock causes a
  kernel exception and ethernet failure after about 30 seconds.

  Easy to reproduce.  Connect to another machine via Gig-E and run
  iperf3 in either direction until the problem occurs.  Should run 900+
  Mb in either direction.  On one occasion I also lost the USB ports.
  However the display continues to work.

  
  # uname -a
  Linux hauser 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  # apt install iperf3
  # iperf3 -s

  
  # apt install iperf3
  # iperf3 -c my-machine -t 1000 # send to my machine
  # iperf3 -c my-machine -t 1000 -R  # receive data from my machine

  When the bitrate drops to zero, look in syslog for the exception.

  Note: Until recently the TB-10 Ethernet would not receive full speed.
  (prior to -43 kernel) Did not see this problem before the Ethernet
  performance increased.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1994 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 13 13:54:28 2019
  HibernationDevice: RESUME=UUID=d15ecb23-8691-42a1-9909-a56f934b536c
  InstallationDate: Installed on 2018-11-19 (86 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=a73e2d3e-5ce3-4130-917d-d116c1316153 ro net.ifnames=0 
mem_sleep_default=deep
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 02MJVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1815808] Re: Thunderbolt Ethernet high-traffic exception

[Terry Rudd]

Gene, upon further investigation, I made a mistake suggesting this bug
is a duplicate of your earlier bug.  We will investigate this bug stand-
alone.

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

Title:
  Thunderbolt Ethernet high-traffic exception

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running iperf3 on Dell XP-15 with TB-10 Thunderbolt dock causes a
  kernel exception and ethernet failure after about 30 seconds.

  Easy to reproduce.  Connect to another machine via Gig-E and run
  iperf3 in either direction until the problem occurs.  Should run 900+
  Mb in either direction.  On one occasion I also lost the USB ports.
  However the display continues to work.

  
  # uname -a
  Linux hauser 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  # apt install iperf3
  # iperf3 -s

  
  # apt install iperf3
  # iperf3 -c my-machine -t 1000 # send to my machine
  # iperf3 -c my-machine -t 1000 -R  # receive data from my machine

  When the bitrate drops to zero, look in syslog for the exception.

  Note: Until recently the TB-10 Ethernet would not receive full speed.
  (prior to -43 kernel) Did not see this problem before the Ethernet
  performance increased.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1994 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 13 13:54:28 2019
  HibernationDevice: RESUME=UUID=d15ecb23-8691-42a1-9909-a56f934b536c
  InstallationDate: Installed on 2018-11-19 (86 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=a73e2d3e-5ce3-4130-917d-d116c1316153 ro net.ifnames=0 
mem_sleep_default=deep
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 02MJVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1815831] Re: [ALSA] [PATCH] System76 darp5 and oryp5 fixups

[Terry Rudd]

Jeremy, I am working this into our SRU process.. thanks for the commits

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

Title:
  [ALSA] [PATCH] System76 darp5 and oryp5 fixups

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Two fixups are needed to support the headset microphone on the
  System76 darp5 and oryp5. The darp5 patch is attached here, the oryp5
  patch will be attached on the next comment.

  On the System76 Darter Pro (darp5), there is a headset microphone
  input attached to 0x1a that does not have a jack detect. In order to
  get it working, the pin configuration needs to be set correctly, and
  the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied.
  This is similar to the MIC_NO_PRESENCE fixups for some Dell laptops,
  except we have a separate microphone jack that is already configured
  correctly.

  On the System76 Oryx Pro (oryp5), there is a headset microphone input
  attached to 0x19 that does not have a jack detect. In order to get it
  working, the pin configuration needs to be set correctly, and the
  ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied. This is
  similar to the MIC_NO_PRESENCE fixups for some Dell laptops, except we
  have a separate microphone jack that is already configured correctly.
  Since the ALC1220 does not have a fixup similar to
  ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC, I have exposed the fixup from the
  ALC269 in a way that it can be accessed from the
  alc1220_fixup_system76_oryp5 function. In addition, the
  alc1220_fixup_clevo_p950 needs to be applied to gain speaker output.

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

-- 
Mailing list: https://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 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

[Terry Rudd]

On 02/15/2019 10:46 AM, Thadeu Lima de Souza Cascardo wrote:
> So, we will get a package into bionic-proposed with only the necessary
> fix for the ipcs command. It's already in the SRU queue and waiting for
> approval, which we already asked for. So, just waiting for a review and
> this should be on -proposed by next week, when we will ask for
> verification.
> 
> Thanks.
> Cascardo.
> 
Perfect!

Thank you and have a good flight to Malta!
See you soon

Terry

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

Title:
  Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid
  structure member offset" in crash prompt.

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Won't Fix
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Confirmed
Status in crash source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  ipcs command could not be used with the bionic GA kernel on ppc64le.

  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on live 
amd64, ppc64el and s390x system. In fact, the new upload introduces a test to 
verify this bug does not happen again.

  [Regression Potential]
  We have only introduced the fix for this specific bug, also adding a test for 
it. It's less likely to be more broken than the current version on the release 
as an entire new upstream version could be.

  -

  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---

  Ubuntu 18.04: "ipcs" command fails with error "invalid structure
  member offset" in crash prompt.

  ---Environment--

  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to reproduce--

  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump

  ---Logs

  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#

  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.

  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: c03

Re: [Kernel-packages] [Bug 1784659] Re: P9 PMU Events Update #5

[Terry Rudd]

On 12/03/2018 12:42 PM, Joseph Salisbury wrote:
> Is this pull request for our development release(Disco/19.04)?  If so,
> not a big issue.  However, these amount of changes would require a
> justification to get into a stable release.
> 
Thanks Joe,

Will follow up on this with Andy Cloke and confirm expectations

Terry

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

Title:
  P9 PMU Events Update #5

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

Bug description:
  == Comment: #0 - Sukadev Bhattiprolu - 2018-03-13 18:08:25 ==

  ---Problem Description---
  There has been some updates to the P9 PMU events list (some events dropped,
  some events changed linux category). We need to make corresponding updates
  to the PMU event JSON files in the Linux perf.

  Submitted a pull request

  https://lkml.org/lkml/2018/3/13/1428

  with Subject line

  [GIT PULL] Please pull JSON files for POWR9 PMU events

   
  Userspace tool common name: perf 

  Userspace rpm: linux-tools 
   
  The userspace tool has the following bit modes: 64-bit

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

-- 
Mailing list: https://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 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

[Terry Rudd]

On 12/18/2018 06:35 AM, Thadeu Lima de Souza Cascardo wrote:
> Can someone from the SRU team approve this package in the queue?
> 
> Cascardo.
> 
Thank you Thadeu!

Terry

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

Title:
  Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid
  structure member offset" in crash prompt.

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Won't Fix
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Confirmed
Status in crash source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Some analysis won't be possible on new kernels. In this case, ipcs command 
could not be used with the bionic GA kernel on ppc64le.

  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on a live 
amd64 system, with success.
  More tests have been done on amd64 and ppc64el, including memory commands, bt.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.

  In case of regressions, analysis of kernel dumps will require that the
  crash file be moved to a system where crash doesn't have the
  regression. But live analysis won't be possible in that case.

  -

  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---

  Ubuntu 18.04: "ipcs" command fails with error "invalid structure
  member offset" in crash prompt.

  ---Environment--

  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to reproduce--

  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump

  ---Logs

  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#

  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.

  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: c03e56c7c600  [THREAD_INFO: c03e56cb]
   CPU: 41
     STATE: TASK_RUNNING (

Re: [Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Terry Rudd]

On 12/18/2018 06:36 AM, Thadeu Lima de Souza Cascardo wrote:
> Subscribed SRU team for their visibility, will ping them on IRC.
> 
So is this planned for SRU 19.04 or just fixed and enabled to be pulled
in for SRU?

Terry

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Released
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  In Progress

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

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

-- 
Mailing list: https://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 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

[Terry Rudd]

On 12/21/2018 10:40 AM, Thadeu Lima de Souza Cascardo wrote:
> So, the SRU team asked for more detail on the tests. I will post it
> after January 15th.
> 

Thank you Thadeu! Have a great holiday break!

Terry

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

Title:
  Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid
  structure member offset" in crash prompt.

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Won't Fix
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Confirmed
Status in crash source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Some analysis won't be possible on new kernels. In this case, ipcs command 
could not be used with the bionic GA kernel on ppc64le.

  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on a live 
amd64 system, with success.
  More tests will be done with the version of the package from -proposed on 
amd64 and ppc64el, including memory commands, and bt.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing is desirable.

  In case of regressions, analysis of kernel dumps will require that the
  crash file be moved to a system where crash doesn't have the
  regression. But live analysis won't be possible in that case.

  -

  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---

  Ubuntu 18.04: "ipcs" command fails with error "invalid structure
  member offset" in crash prompt.

  ---Environment--

  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to reproduce--

  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump

  ---Logs

  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#

  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.

  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: c03e56c7c6

Re: [Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Terry Rudd]

Hi Thadeu,

So it feels like we're "done" on this bug; fix released on the kernels
that make sense and not doing anything on the kernels that don't.  Is
that correct?

Thanks in advance,

Terry


On 12/21/2018 10:43 AM, Thadeu Lima de Souza Cascardo wrote:
> I have just marked this as Invalid for Bionic, as the crash version on
> Bionic is capable of analyzing 4.15 kernels (and older 4.13 kernels,
> even though no one should be using such kernels on Bionic).
> 
> If there are any bugs about specific functionalities on that Bionic
> crash version, please report it as a different bug. See, for example,
> https://bugs.launchpad.net/ubuntu-power-systems/+bug/1765660.
> 
> Cascardo.
> 
> ** Changed in: crash (Ubuntu Bionic)
>Status: In Progress => Invalid
>

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Released
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Invalid

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.

Re: [Kernel-packages] [Bug 1787405] Re: [19.04 FEAT] Guest-dedicated Crypto Adapters

[Terry Rudd]

Hi Joe,

If IBM does not do the backport, just how much work do you think there
is on that whole effort?  That list of patches was pretty impressive in
my eyes.

Terry
On 11/02/2018 10:43 AM, Joseph Salisbury wrote:
> I tried to apply the first two commits listed in comment #23.  Neither
> apply cleanly and need to be backported.  Would it be possible for IBM
> to provide a backport of any commits that don't apply cleanly?
>
> This bug will be discussed on Monday in the kernel teams work items
> meeting, due to the number of commits needed in Bionic(4.15), which is a
> stable release.
>
> ** Tags added: kernel-key
>


** Attachment added: "pEpkey.asc"
   https://bugs.launchpad.net/bugs/1787405/+attachment/5208447/+files/pEpkey.asc

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

Title:
  [19.04 FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  Triaged
Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
  37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
  112c24d ("KVM: s390: CPU model support for AP virtualization")
  492a6be ("s390: doc: detailed specifications for AP virtualization")

  <-- till here in 'kvm/next'
  (https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->

  8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
  0e237e4 ("KVM: s390: Tracing APCB changes")
  76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")

  <-- till here in 'kvms390/next'
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
  -->

  <-- In addition to that some prereqs for the 'ap/crypto' driver are
  necessary -->

  ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
  df80c03 ("s390/zcrypt: Review inline assembler constraints.")
  f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
  2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
  7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
  fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")

  <--
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
  -->

  == PATCH ==

  Above git commits are all from 4.19.
  The git commands for 4.18 would be:

  $ git cherry-pick 

  (112c24d "KVM: s390: CPU model support for AP virtualization" may have
  a trivial merge conflict with the etoken patch)

  $ git cherry-pick 

  $ git cherry-pick 

  == Regression Potential ==

  Low to mid:

  - mid because in summary there are a lot of changes, but low
  - they are all limited to the s390x architecture
  - and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
  - Test kernel was built for testting.

  == Test Case ==

  Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka 
crypto-) adapters installed.
  Verify that the AP bus created a sysfs device for each APQN, like:
  /sys/devices

[Kernel-packages] [Bug 1815258] Re: 4.18.0-14-generic unbootable on Toshiba

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1814555
   Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

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

Title:
  4.18.0-14-generic unbootable on Toshiba

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the update for the 4.18.0-14-generic kernel the machine freezes
  on booting. Machine still books under the 0-13 kernel. Booting in
  Recovery Mode seems go normally to the Recovery Menu. At that point it
  reports "Starting Avahi mDNS-SD Stack" and gets an OK response. That
  is repeated with another OK. Then it says "Starting Daily apt upgrade
  and clean activities" followed by an OK. Next is a second attempt for
  the same "apt upgrade" and it appears to be frozen. No OK ever
  received and no further progress towards booting.

  Not sure how additional details can be acquired.

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

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

[Kernel-packages] [Bug 1778854] Re: kvm_pr on power9 not loadable

[Terry Rudd]

** Also affects: qemu (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Cosmic)
   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/1778854

Title:
  kvm_pr on power9 not loadable

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in qemu source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  New
Status in qemu source package in Cosmic:
  New

Bug description:
  Hi,
  this might be the worst bug report ever, but there just isn't a lot more info 
available when the issue occurs.

  I tried to set up 2nd level KVM on a P9 machine with kvm_pr but I run into 
(this is the series on commands I used on P8 btw):
$ sudo modprobe kvm_pr
modprobe: ERROR: could not insert 'kvm_pr': Input/output error

  Unfortunately there is no dmesg message (not even with level set to
  debug) or anything like it, so I'm stuck asking if P9 does not work
  with kvm_pr at all or if there are other constraints one should know?

  Note: while no more a problem for kvm_hv on P9 I disabled SMT but the
  issue persists.

  Modinfo LGTM and matches the kernel:
  ubuntu@bionic-kvm:~$ modinfo kvm_pr
  filename:   
/lib/modules/4.15.0-23-generic/kernel/arch/powerpc/kvm/kvm-pr.ko
  alias:  devname:kvm
  alias:  char-major-10-232
  license:GPL
  srcversion: CE18B50FD03CB9D9C432700
  depends:kvm
  intree: Y
  name:   kvm_pr
  vermagic:   4.15.0-23-generic SMP mod_unload mprofile-kernel
  signat: PKCS#7
  signer: 
  sig_key:
  sig_hashalgo:   md4
  ubuntu@bionic-kvm:~$ uname -a
  Linux bionic-kvm 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  It feels more that I'm missing something than a bug, but in that case
  I have to ask what it is.

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

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

[Kernel-packages] [Bug 1814095] Re: bnxt_en_po: TX timed out triggering Netdev Watchdog Timer

[Terry Rudd]

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

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

Title:
  bnxt_en_po: TX timed out triggering Netdev Watchdog Timer

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New

Bug description:
  [Impact]

  The bnxt_en_bpo driver experienced tx timeouts causing the system to
  experience network stalls and fail to send data and heartbeat packets.

  The following 25Gb Broadcom NIC error was seen on Xenial
  running the 4.4.0-141-generic kernel on an amd64 host
  seeing moderate-heavy network traffic (just once):

  * The bnxt_en_po driver froze on a "TX timed out" error
    and triggered the Netdev Watchdog timer under load.

  * From kernel log:
    "NETDEV WATCHDOG: eno2d1 (bnxt_en_bpo): transmit queue 0 timed out"
    See attached kern.log excerpt file for full excerpt of error log.

  * Release = Xenial
    Kernel = 4.4.0-141-generic #167
    eno2d1 = Product Name: Broadcom Adv. Dual 25Gb Ethernet

  * This caused the driver to reset in order to recover:

    "bnxt_en_bpo :19:00.1 eno2d1: TX timeout detected, starting
  reset task!"

    driver: bnxt_en_bpo
    version: 1.8.1
    source: ubuntu/bnxt/bnxt.c: bnxt_tx_timeout()

  * The loss of connectivity and softirq stall caused other failures
    on the system.

  * The bnxt_en_po driver is the imported Broadcom driver
    pulled in to support newer Broadcom HW (specific boards)
    while the bnx_en module continues to support the older
    HW. The current Linux upstream driver does not compile
    easily with the 4.4 kernel (too many changes).

  * This upstream and bnxt_en driver fix is a likely solution:
     "bnxt_en: Fix TX timeout during netpoll"
     commit: 73f21c653f930f438d53eed29b5e4c65c8a0f906

    This fix has not been applied to the bnxt_en_po driver
    version, but review of the code indicates that it is
    susceptible to the bug, and the fix would be reasonable.

  [Test Case]

  * Unfortunately, this is not easy to reproduce. Also, it is only seen
  on 4.4 kernels with newer Broadcom NICs supported by the bnxt_en_bpo
  driver.

  [Regression Potential]

  * The patch is restricted to the bpo driver, with very constrained
  scope - just the newest Broadcom NICs being used by the Xenial 4.4
  kernel (as opposed to the hwe 4.15 etc. kernels, which would have the
  in-tree fixed driver).

  * The patch is very small and backport is fairly minimal and simple.

  * The fix has been running on the in-tree driver in upstream mainline
  as well as the Ubuntu Linux in-tree driver, although the Broadcom
  driver has a lot of lower level code that is different, this piece is
  still the same.

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

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

[Kernel-packages] [Bug 1814095] Re: bnxt_en_po: TX timed out triggering Netdev Watchdog Timer

[Terry Rudd]

Nivedita, per the request to test this patch, determining the correct FW
version seems an open issue.  There is also the issue of having hardware
available to properly test.

Have you been able to determine a reproducer for this bug?  
Do you know if anyone has been able to test the backport?  
Can you confirm if the request is to actually get the patch merged to xenial at 
this time?

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

Title:
  bnxt_en_po: TX timed out triggering Netdev Watchdog Timer

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

Bug description:
  [Impact]

  The bnxt_en_bpo driver experienced tx timeouts causing the system to
  experience network stalls and fail to send data and heartbeat packets.

  The following 25Gb Broadcom NIC error was seen on Xenial
  running the 4.4.0-141-generic kernel on an amd64 host
  seeing moderate-heavy network traffic (just once):

  * The bnxt_en_po driver froze on a "TX timed out" error
    and triggered the Netdev Watchdog timer under load.

  * From kernel log:
    "NETDEV WATCHDOG: eno2d1 (bnxt_en_bpo): transmit queue 0 timed out"
    See attached kern.log excerpt file for full excerpt of error log.

  * Release = Xenial
    Kernel = 4.4.0-141-generic #167
    eno2d1 = Product Name: Broadcom Adv. Dual 25Gb Ethernet

  * This caused the driver to reset in order to recover:

    "bnxt_en_bpo :19:00.1 eno2d1: TX timeout detected, starting
  reset task!"

    driver: bnxt_en_bpo
    version: 1.8.1
    source: ubuntu/bnxt/bnxt.c: bnxt_tx_timeout()

  * The loss of connectivity and softirq stall caused other failures
    on the system.

  * The bnxt_en_po driver is the imported Broadcom driver
    pulled in to support newer Broadcom HW (specific boards)
    while the bnx_en module continues to support the older
    HW. The current Linux upstream driver does not compile
    easily with the 4.4 kernel (too many changes).

  * This upstream and bnxt_en driver fix is a likely solution:
     "bnxt_en: Fix TX timeout during netpoll"
     commit: 73f21c653f930f438d53eed29b5e4c65c8a0f906

    This fix has not been applied to the bnxt_en_po driver
    version, but review of the code indicates that it is
    susceptible to the bug, and the fix would be reasonable.

  [Test Case]

  * Unfortunately, this is not easy to reproduce. Also, it is only seen
  on 4.4 kernels with newer Broadcom NICs supported by the bnxt_en_bpo
  driver.

  [Regression Potential]

  * The patch is restricted to the bpo driver, with very constrained
  scope - just the newest Broadcom NICs being used by the Xenial 4.4
  kernel (as opposed to the hwe 4.15 etc. kernels, which would have the
  in-tree fixed driver).

  * The patch is very small and backport is fairly minimal and simple.

  * The fix has been running on the in-tree driver in upstream mainline
  as well as the Ubuntu Linux in-tree driver, although the Broadcom
  driver has a lot of lower level code that is different, this piece is
  still the same.

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

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