[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + journal_checksum + mmap

[Terry Rudd]

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

Title:
  ext4 journal recovery fails w/ data=journal + journal_checksum + mmap

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  New

Bug description:
  [Impact]
  In the event of a loss of power, ext4 filesystems mounted w/ 
data=journal,journal_checksum are subject to a corruption issue that requires a 
fsck to recover. This is exacerbated by installations by curtin that set 
passno=0 in /etc/fstab, preventing fsck from running automatically and thus 
requiring a manual recovery. And *that* is further exacerbated because 
initramfs-tools is smart enough to not include fsck.ext4 when passno=0 is 
detected in /etc/fstab, requiring the user to boot from recovery media.

  [Test Case]
  Forcibly power cycle a system running 'stress-ng --dir 0'. I've created a 
package to automate the reproduction:
  https://git.launchpad.net/~dannf/+git/dgx2-ext4-csum-repro?h=master

  [Fix]
  [Regression Risk]

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


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

[Kernel-packages] [Bug 1940564] Re: bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure Standard_D48_v3

[Terry Rudd]

** Summary changed:

- linux
+ bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure Standard_D48_v3

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

Title:
  bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure
  Standard_D48_v3

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

Bug description:
  [Impact]

  bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure
  Standard_D48_v3

  [Fix]

  revert 10b9a1068ba301b6458a308c749eb0b93951010c ("scsi: core: Cap
  scsi_host cmd_per_lun at can_queue") from "UBUNTU: upstream stable to
  v4.14.240, v4.19.198"

  This commit originates from an unreleased kernel (5.14-rc1). According
  to the commit log it purports to head off possible future problems. It
  does not appear to address a specific bug. It has been backported to
  4.14.y and 4.19.y.

  [Test Plan]

  Install and boot on an Azure Standard_D48_v3 instance.

  [Where problems could occur]

  iscsi requests could hang

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


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

[Kernel-packages] [Bug 1938221] Re: Fail to resume after hibernate. Image mismatch: architecture specific data

[Terry Rudd]

does this behavior persist using the 5.11.0-26.28 in proposed?   And can
you confirm you didn't see this problem on 5.11.0-24?   Thanks - 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/1938221

Title:
  Fail to resume after hibernate. Image mismatch: architecture specific
  data

Status in linux package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 21.04 on a laptop and have been using hibernate flawlessly 
for a couple of months.
  More recently, resuming from hibernation stopped working and now falls back 
to complete restart. 

  This is what I get from dmesg:

  [   17.407048] kernel: PM: hibernation: resume from hibernation
  [   17.409714] kernel: PM: hibernation: Marking nosave pages: [mem 
0x-0x0fff]
  [   17.409717] kernel: PM: hibernation: Marking nosave pages: [mem 
0x0004f000-0x0004]
  [   17.409718] kernel: PM: hibernation: Marking nosave pages: [mem 
0x0009e000-0x000f]
  [   17.409721] kernel: PM: hibernation: Marking nosave pages: [mem 
0xae6e9000-0xae6e]
  [   17.409723] kernel: PM: hibernation: Marking nosave pages: [mem 
0xaf0cd000-0xaf5abfff]
  [   17.409744] kernel: PM: hibernation: Marking nosave pages: [mem 
0xb1e4c000-0xb1ed3fff]
  [   17.409747] kernel: PM: hibernation: Marking nosave pages: [mem 
0xb2698000-0xb2698fff]
  [   17.409748] kernel: PM: hibernation: Marking nosave pages: [mem 
0xb54af000-0xb54a]
  [   17.409749] kernel: PM: hibernation: Marking nosave pages: [mem 
0xb54d8000-0xb54d8fff]
  [   17.409751] kernel: PM: hibernation: Marking nosave pages: [mem 
0xb7db3000-0xb7ff]
  [   17.409761] kernel: PM: hibernation: Marking nosave pages: [mem 
0xb8759000-0xb87f]
  [   17.409765] kernel: PM: hibernation: Marking nosave pages: [mem 
0xb8f9d000-0xb8ff]
  [   17.409767] kernel: PM: hibernation: Marking nosave pages: [mem 
0xba6f5000-0xba7f]
  [   17.409773] kernel: PM: hibernation: Marking nosave pages: [mem 
0xbbcec000-0x]
  [   17.410626] kernel: PM: hibernation: Basic memory bitmaps created
  [   17.481616] kernel: PM: Using 3 thread(s) for decompression
  [   17.481620] kernel: PM: Loading and decompressing image data (835177 
pages)...
  [   17.481626] kernel: PM: hibernation: Image mismatch: architecture specific 
data
  [   17.481627] kernel: PM: hibernation: Read 3340708 kbytes in 0.01 seconds 
(334070.80 MB/s)
  [   17.482589] kernel: PM: Error -1 resuming
  [   17.482594] kernel: PM: hibernation: Failed to load image, recovering.
  [   17.482992] kernel: PM: hibernation: Basic memory bitmaps freed
  [   17.483572] kernel: PM: hibernation: resume failed (-1)

  Here is some system information:

  $ cat /proc/version_signature
  Ubuntu 5.11.0-25.27-generic 5.11.22
  $ cat /sys/power/state
  freeze mem disk
  $ cat /sys/power/disk
  [platform] shutdown reboot suspend test_resume
  $ cat /proc/cmdline 
  BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet 
splash resume=UUID=a2be2098-* mem_sleep_default=deep
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giacof 2186 F pulseaudio
   /dev/snd/controlC2:  giacof 2186 F pulseaudio
   /dev/snd/controlC0:  giacof 2186 F pulseaudio
  CasperMD5json:
   {
 "result": "skip"
   }
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-05-17 (71 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision M4800
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash 
resume=UUID=a2be2098-8e7d-4460-845d-c2b3b22def13 mem_sleep_default=deep
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  StagingDrivers: ashmem_linux
  Tags:  hirsute staging
  Uname: Linux 5.11.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 10/08/2018
  dmi.bios.release: 65.25
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A25
  dmi.board.name: 0T3YTY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr:
  

[Kernel-packages] [Bug 1935855] Re: dbgsym contains no debug symbols

[Terry Rudd]

Thanks for bringing this up @dann.   This needs to be corrected.

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

Title:
  dbgsym contains no debug symbols

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  linux-image-unsigned-5.4.0-77-generic-dbgsym provides a
  /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm, but it does not contain
  any debug symbols. Compare:

  
  $ file /usr/lib/debug/boot/vmlinux-*
  /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm:   ELF 64-bit LSB executable, 
x86-64, version 1 (SYSV), statically linked, 
BuildID[sha1]=514891d64a7d18db4fa58aa5cfea213e0951ca9d, not stripped
  /usr/lib/debug/boot/vmlinux-5.4.0-77-generic: ELF 64-bit LSB executable, 
x86-64, version 1 (SYSV), statically linked, 
BuildID[sha1]=773d8ee85333fe092635f65d2b6850909085c11d, with debug_info, not 
stripped

  This is apparently because linux-kvm has CONFIG_DEBUG_INFO disabled.
  Is there a good reason for that? Does it have some adverse impact even
  when stripped?

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


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

[Kernel-packages] [Bug 1934099] Re: 4.15.0-149-generic: lxc-attach lsm/lsm.c: lsm_process_label_set_at: 174 Operation not permitted - Failed to set AppArmor label "lxc-container-default-cgns"

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1934187
   lxd exec fails

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

Title:
  4.15.0-149-generic: lxc-attach lsm/lsm.c: lsm_process_label_set_at:
  174 Operation not permitted - Failed to set AppArmor label "lxc-
  container-default-cgns"

Status in linux package in Ubuntu:
  New

Bug description:
  Hello.

  When testing with the bionic-proposed repository, we found that the
  4.15.0-149-generic break the lxc-attach command with the following
  error:

lxc-attach: bidule: lsm/lsm.c: lsm_process_label_set_at: 174
  Operation not permitted - Failed to set AppArmor label "lxc-container-
  default-cgns"

  We don't have this issue with the current 4.15.0-147.

  There is no issue using the --elevated-privileges option of lxc-
  attach.

  I join the debug log of “lxc-attach -n bidule -l debug”.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-149-generic 4.15.0-149.153
  ProcVersionSignature: Ubuntu 4.15.0-149.153-generic 4.15.18
  Uname: Linux 4.15.0-149-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 juin  30 10:15 seq
   crw-rw 1 root audio 116, 33 juin  30 10:15 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.24
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Jun 30 10:21:54 2021
  HibernationDevice: RESUME=/dev/mapper/bionic--vg-swap_1
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  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)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-149-generic 
root=/dev/mapper/hostname--vg-root ro console=tty1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-149-generic N/A
   linux-backports-modules-4.15.0-149-generic  N/A
   linux-firmware  1.173.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-3.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-3.1
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1932585] [NEW] Please block application of hirsute linux/bits.h: fix compilation error with GENMASK for this cycle

[Terry Rudd]

Public bug reported:

The following upstream changes in 5.13-rc3 [1] broke Mellanox OFED 
compatibility:
https://patches.linaro.org/patch/451093/

Mellanox has confirmed that OFED5.3 installation fails with this patch
and they are working to check older versions. They have asked us to keep
them informed on when this patch set will come into which kernel series,
which we've agreed to do.  The intent of this bug is to block
application of the patch set until we get confirmation of Mellanox's
awareness.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Terry Rudd (terrykrudd)
 Status: New

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

Title:
  Please block application of hirsute  linux/bits.h: fix compilation
  error with GENMASK for this cycle

Status in linux package in Ubuntu:
  New

Bug description:
  The following upstream changes in 5.13-rc3 [1] broke Mellanox OFED 
compatibility:
  https://patches.linaro.org/patch/451093/

  Mellanox has confirmed that OFED5.3 installation fails with this patch
  and they are working to check older versions. They have asked us to
  keep them informed on when this patch set will come into which kernel
  series, which we've agreed to do.  The intent of this bug is to block
  application of the patch set until we get confirmation of Mellanox's
  awareness.

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

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

[Kernel-packages] [Bug 1930794] Re: Ubuntu 20.04 LTS does not start after kernel update

[Terry Rudd]

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

** This bug is no longer a duplicate of bug 1930976
   5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
** This bug has been marked a duplicate of bug 1930733
   Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with 
HDMI

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

Title:
  Ubuntu 20.04 LTS does not start after kernel update

Status in linux package in Ubuntu:
  New

Bug description:
  Hi
  I got a notification to update my kernel to 5.8.0-55 and when I update and 
reboot my PC. The desktop does not start and when I downgrade my kernel 
5.8.0-53. Again, it does not work either. Finally, I have to reimage my PC from 
the scratch and I lose all of my local data in this situation. I Hope you can 
solve this critical problem soon.

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

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

[Kernel-packages] [Bug 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1930733
   Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with 
HDMI

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

Title:
  5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers

Status in linux-hwe-5.8 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Incomplete

Bug description:
  Kernel: 5.8.0-55
  The last kernel destroyed my Ubuntu 20.04.02 installation, something went 
wrong with some kernel packages. It seems like Ubuntu is unable to find my 
video card correctly and the device drivers from Nvidia don't seem to work 
anymore. I had to do a clean installation, but even that doesn't solve the 
problem. I think this is a serious issue that needs to be looked into.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jun  5 16:50:38 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation Device [10de:2206] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:403f]
  InstallationDate: Installed on 2021-06-05 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=4984fe2f-d45f-4734-884c-2426bcf10ca4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F33j
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33j:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1930794] Re: Ubuntu 20.04 LTS does not start after kernel update

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1930976
   5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers

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

Title:
  Ubuntu 20.04 LTS does not start after kernel update

Status in linux package in Ubuntu:
  New

Bug description:
  Hi
  I got a notification to update my kernel to 5.8.0-55 and when I update and 
reboot my PC. The desktop does not start and when I downgrade my kernel 
5.8.0-53. Again, it does not work either. Finally, I have to reimage my PC from 
the scratch and I lose all of my local data in this situation. I Hope you can 
solve this critical problem soon.

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

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

[Kernel-packages] [Bug 1915699] Re: Bluetooth adapter not found

[Terry Rudd]

Hi Mukesh,

4.4.0-83 is a very old kernel.  Have you tried the latest proposed
kernel for 16.04, which is 4.4.0-203.235?

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

Title:
  Bluetooth adapter not found

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No Bluetooth adapters were found

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-83-generic 4.4.0-83.106
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mukesh-pt3266   2720 F pulseaudio
  Date: Mon Feb 15 15:54:01 2021
  InstallationDate: Installed on 2017-07-10 (1316 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:301a Dell Computer Corp. 
   Bus 001 Device 002: ID 1bcf:28b8 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=UUID=9c344e13-42e5-43bd-a49c-0495a0065cde ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-83-generic N/A
   linux-backports-modules-4.4.0-83-generic  N/A
   linux-firmware1.157.23
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2019-12-16 (427 days ago)
  dmi.bios.date: 12/11/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.3
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.3:bd12/11/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1912708] Re: CONFIG_RANDOMIZE_BASE on ppc64el

[Terry Rudd]

Steve,  I am adding this to our workflow to address

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

Title:
  CONFIG_RANDOMIZE_BASE on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, it looks like CONFIG_RANDOMIZE_BASE is not set in our ppc64el
  kernel configurations, based on running this in an rsync clone of
  kernel.ubuntu.com::kernel-ppa-config/ :

  grep CONFIG_RANDOMIZE_BASE $(find . -iname '*ppc*' | grep /linux/)

  This returns no hits -- not even for a disabled feature -- which
  surprised me a bit.

  This webpage suggests power should have this kernel configuration
  available after 5.5: https://cateee.net/lkddb/web-
  lkddb/RANDOMIZE_BASE.html

  Thanks

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

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

[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8

[Terry Rudd]

It seems that in at least 1 case, this condition arises with linux-
modules-extra installed so my suggestion above may not help

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

Title:
  Black screen on boot after 20.04 upgraded to kernel 5.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday Ubuntu asked me to reboot after automatic updates, and when
  I rebooted it doesn't start up. Sometimes it stays on the Dell logo,
  sometimes it goes to a black screen and doesn't get past that (not
  sure what causes each variation -- perhaps for reboot it does the Dell
  logo, cold start up it does the black screen?).

  After the updates it's trying to boot the 5.8.0 kernel. In the boot
  menu, if I manually select the 5.4.0 kernel everything works fine. So
  presumably it's something about the 5.8 kernel on this hardware.

  When this occurred I was running the Nouveau open source graphics
  driver. I switched to the NVIDIA driver (460) to see if that would
  help, but it didn't change anything. So it may or may not be graphics
  related.

  I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday
  -- Jan 12, I think it would be around 13:30 that I first rebooted
  after the upgrade (and a bunch of times after that). I ran the logs
  through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the
  lines were this (presumably irrelevant):

  Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400
  audit(1610431795.003:29126): apparmor="DENIED" operation="open"
  namespace="root//lxd-juju-804318-0_"
  profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906
  comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100

  For reference:

  * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I 
think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB 
RAM.
  * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on 
"Ubuntu 20.04.1 LTS".
  * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78
  * "sudo lspci -vnvn" output is included in the attached logs.zip
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ben4518 F pulseaudio
   /dev/snd/pcmC0D0p:   ben4518 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-27 (138 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. XPS 15 9550
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-59-generic N/A
   linux-backports-modules-5.4.0-59-generic  N/A
   linux-firmware1.187.7
  Tags:  focal
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8

[Terry Rudd]

If anyone affected by this bug can still reproduce it in their
environments, I would like them to try installing linux-modules-extra
and rebooting to see if the issue clears.  You will need to do this with
your 5.4 kernel.

Thanks in advance,
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/1911352

Title:
  Black screen on boot after 20.04 upgraded to kernel 5.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Yesterday Ubuntu asked me to reboot after automatic updates, and when
  I rebooted it doesn't start up. Sometimes it stays on the Dell logo,
  sometimes it goes to a black screen and doesn't get past that (not
  sure what causes each variation -- perhaps for reboot it does the Dell
  logo, cold start up it does the black screen?).

  After the updates it's trying to boot the 5.8.0 kernel. In the boot
  menu, if I manually select the 5.4.0 kernel everything works fine. So
  presumably it's something about the 5.8 kernel on this hardware.

  When this occurred I was running the Nouveau open source graphics
  driver. I switched to the NVIDIA driver (460) to see if that would
  help, but it didn't change anything. So it may or may not be graphics
  related.

  I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday
  -- Jan 12, I think it would be around 13:30 that I first rebooted
  after the upgrade (and a bunch of times after that). I ran the logs
  through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the
  lines were this (presumably irrelevant):

  Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400
  audit(1610431795.003:29126): apparmor="DENIED" operation="open"
  namespace="root//lxd-juju-804318-0_"
  profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906
  comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100

  For reference:

  * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I 
think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB 
RAM.
  * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on 
"Ubuntu 20.04.1 LTS".
  * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78
  * "sudo lspci -vnvn" output is included in the attached logs.zip
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ben4518 F pulseaudio
   /dev/snd/pcmC0D0p:   ben4518 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-27 (138 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. XPS 15 9550
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-59-generic N/A
   linux-backports-modules-5.4.0-59-generic  N/A
   linux-firmware1.187.7
  Tags:  focal
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1912188] Re: Load growing continously

[Terry Rudd]

Thank you Tamas.   You are likely aware we don't plan to support 5.8.*
in 21.04 user space but we've very interested to make sure this issue is
not present in 20.10 (groovy).  Have you tested with that user space?
Also, have you tried the 5.10 kernel in -proposed for 21.04?  If you see
the same or similar issue with that kernel, please let us know.

I would be very interested in results from both if you have time/ability
test both. Thanks in advance.

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

Title:
  Load growing continously

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently load started growing with no end. After a while random
  processes become zombies.

   11:32:22 up 26 min,  1 user,  load average: 196.16, 186.30, 138.60

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-generic 5.8.0.36.40+21.04.38
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tompos 2361 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Jan 18 11:30:11 2021
  InstallationDate: Installed on 2020-12-31 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic 
root=UUID=086c6507-b389-4208-a8bc-d0b99071b5cd ro rootflags=subvol=@
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-01-02 (15 days ago)
  dmi.bios.date: 10/22/2020
  dmi.bios.release: 14.1
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.14.01
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.4E.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 20.78
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.14.01:bd10/22/2020:br14.1:efr20.78:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.4E.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 5DT80EC#BH4
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1912188] Re: Load growing continously

[Terry Rudd]

Yes Tamas.  In other words, I believe you are confirming the only think
changing back and forth is the kernel version you are running. Thank you
for that.

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

Title:
  Load growing continously

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently load started growing with no end. After a while random
  processes become zombies.

   11:32:22 up 26 min,  1 user,  load average: 196.16, 186.30, 138.60

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-generic 5.8.0.36.40+21.04.38
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tompos 2361 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Jan 18 11:30:11 2021
  InstallationDate: Installed on 2020-12-31 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic 
root=UUID=086c6507-b389-4208-a8bc-d0b99071b5cd ro rootflags=subvol=@
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-01-02 (15 days ago)
  dmi.bios.date: 10/22/2020
  dmi.bios.release: 14.1
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.14.01
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.4E.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 20.78
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.14.01:bd10/22/2020:br14.1:efr20.78:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.4E.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 5DT80EC#BH4
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1909017] Re: bug when suspending the system does not wake up and freezes on black screen

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1909005
   Ubuntu does not resume (wake up) from suspend

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

Title:
  bug when suspending the system does not wake up and freezes on black
  screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bug when suspending the system does not wake up and freezes on black
  screen.

  If I lower the screen or suspend, when trying to turn on the computer
  the screen is frozen on a black screen and does not obey any command
  that I try, it is stuck on a black screen, and I am forced to turn off
  the forced computer by holding the power until it turns off .

  version.log: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17

  lspci-vnvn.log: https://del.dog/menitofyfy.txt

  
  more info:
  togofire@togofire:~$ cat /etc/*-release
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  NAME="Linux Mint"
  VERSION="20 (Ulyana)"
  ID=linuxmint
  ID_LIKE=ubuntu
  PRETTY_NAME="Linux Mint 20"
  VERSION_ID="20"
  HOME_URL="https://www.linuxmint.com/;
  SUPPORT_URL="https://forums.linuxmint.com/;
  
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/;
  PRIVACY_POLICY_URL="https://www.linuxmint.com/;
  VERSION_CODENAME=ulyana
  UBUNTU_CODENAME=focal
  cat: /etc/upstream-release: É um diretório
  togofire@togofire:~$ cat /etc/*-release | grep PRETTY
  cat: /etc/upstream-release: É um diretório
  PRETTY_NAME="Linux Mint 20"
  togofire@togofire:~$ lsb_release -a
  LSB Version:  core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Linuxmint
  Description:  Linux Mint 20
  Release:  20
  Codename: ulyana
  togofire@togofire:~$ uname -a
  Linux togofire 5.8.0-33-generic #36~20.04.1-Ubuntu SMP Wed Dec 9 17:01:13 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
  togofire@togofire:~$ cat /proc/version
  Linux version 5.8.0-33-generic (buildd@lgw01-amd64-010) (gcc (Ubuntu 
9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) 
#36~20.04.1-Ubuntu SMP Wed Dec 9 17:01:13 UTC 2020
  togofire@togofire:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  togofire   4520 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-07-04 (171 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:2113 Acer, Inc Integrated Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81GT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=90612144-f123-47e5-b09e-9c2870210dfb ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-33-generic N/A
   linux-backports-modules-5.8.0-33-generic  N/A
   linux-firmware1.187.6
  Tags:  ulyana
  Uname: Linux 5.8.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2020
  dmi.bios.release: 1.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8JCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion Y530-15ICH
  dmi.ec.firmware.release: 1.54
  dmi.modalias: 
dmi:bvnLENOVO:bvr8JCN54WW:bd06/15/2020:br1.54:efr1.54:svnLENOVO:pn81GT:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH:
  dmi.product.family: Legion Y530-15ICH
  dmi.product.name: 81GT
  dmi.product.sku: LENOVO_MT_81GT_BU_idea_FM_Legion Y530-15ICH
  dmi.product.version: Lenovo Legion Y530-15ICH
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  togofire   4218 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-07-04 (187 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux 

[Kernel-packages] [Bug 1912188] Re: Load growing continously

[Terry Rudd]

Are you running the 5.8.0-33 kernel in the same 21.04 user space?

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

Title:
  Load growing continously

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently load started growing with no end. After a while random
  processes become zombies.

   11:32:22 up 26 min,  1 user,  load average: 196.16, 186.30, 138.60

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-generic 5.8.0.36.40+21.04.38
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tompos 2361 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Jan 18 11:30:11 2021
  InstallationDate: Installed on 2020-12-31 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic 
root=UUID=086c6507-b389-4208-a8bc-d0b99071b5cd ro rootflags=subvol=@
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-01-02 (15 days ago)
  dmi.bios.date: 10/22/2020
  dmi.bios.release: 14.1
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.14.01
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.4E.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 20.78
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.14.01:bd10/22/2020:br14.1:efr20.78:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.4E.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 5DT80EC#BH4
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1909017] Re: bug when suspending the system does not wake up and freezes on black screen

[Terry Rudd]

@Italo, have you had time to test Kai-Heng's suggestion?

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

Title:
  bug when suspending the system does not wake up and freezes on black
  screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bug when suspending the system does not wake up and freezes on black
  screen.

  If I lower the screen or suspend, when trying to turn on the computer
  the screen is frozen on a black screen and does not obey any command
  that I try, it is stuck on a black screen, and I am forced to turn off
  the forced computer by holding the power until it turns off .

  version.log: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17

  lspci-vnvn.log: https://del.dog/menitofyfy.txt

  
  more info:
  togofire@togofire:~$ cat /etc/*-release
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=20
  DISTRIB_CODENAME=ulyana
  DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
  NAME="Linux Mint"
  VERSION="20 (Ulyana)"
  ID=linuxmint
  ID_LIKE=ubuntu
  PRETTY_NAME="Linux Mint 20"
  VERSION_ID="20"
  HOME_URL="https://www.linuxmint.com/;
  SUPPORT_URL="https://forums.linuxmint.com/;
  
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/;
  PRIVACY_POLICY_URL="https://www.linuxmint.com/;
  VERSION_CODENAME=ulyana
  UBUNTU_CODENAME=focal
  cat: /etc/upstream-release: É um diretório
  togofire@togofire:~$ cat /etc/*-release | grep PRETTY
  cat: /etc/upstream-release: É um diretório
  PRETTY_NAME="Linux Mint 20"
  togofire@togofire:~$ lsb_release -a
  LSB Version:  core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Linuxmint
  Description:  Linux Mint 20
  Release:  20
  Codename: ulyana
  togofire@togofire:~$ uname -a
  Linux togofire 5.8.0-33-generic #36~20.04.1-Ubuntu SMP Wed Dec 9 17:01:13 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
  togofire@togofire:~$ cat /proc/version
  Linux version 5.8.0-33-generic (buildd@lgw01-amd64-010) (gcc (Ubuntu 
9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) 
#36~20.04.1-Ubuntu SMP Wed Dec 9 17:01:13 UTC 2020
  togofire@togofire:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  togofire   4520 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-07-04 (171 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:2113 Acer, Inc Integrated Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81GT
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=90612144-f123-47e5-b09e-9c2870210dfb ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-33-generic N/A
   linux-backports-modules-5.8.0-33-generic  N/A
   linux-firmware1.187.6
  Tags:  ulyana
  Uname: Linux 5.8.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2020
  dmi.bios.release: 1.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8JCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion Y530-15ICH
  dmi.ec.firmware.release: 1.54
  dmi.modalias: 
dmi:bvnLENOVO:bvr8JCN54WW:bd06/15/2020:br1.54:efr1.54:svnLENOVO:pn81GT:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH:
  dmi.product.family: Legion Y530-15ICH
  dmi.product.name: 81GT
  dmi.product.sku: LENOVO_MT_81GT_BU_idea_FM_Legion Y530-15ICH
  dmi.product.version: Lenovo Legion Y530-15ICH
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  togofire   4218 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-07-04 (187 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:2113 Acer, Inc Integrated Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 

[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time

[Terry Rudd]

Andrew, we plan to address this in the Focal 5.8 hwe kernel and we're
going to be building a test kernel.  We would really appreciate you
testing it since you have a reliable reproducer.

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

Title:
  nvme drive fails after some time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sorry for the vague title. I thought this was a hardware issue until
  someone else online mentioned their nvme drive goes "read only" after
  some time. I tend not to reboot my system much, so have a large
  journal. Either way this happens once in a while. The / drive is fine,
  but /home is on nvme which just disappears. I reboot and everything is
  fine. But leave it long enough and it'll fail again.

  Here's the most recent snippet about the nvme drive before I restarted
  the system.

  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting 

   
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset 
controller
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset 
controller
  Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure 
status: -19
  Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more 
than 120 seconds.
  Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0   731  2 0x4000
  Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123967, lost async page write
  Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): 
__ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading 
directory lblock 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123917, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123909, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 0, lost sync page write
  Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing 
superblock

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan  9 11:56:28 2021
  InstallationDate: Installed on 2020-08-15 (146 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel Corporation NUC8i7HVK
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic 
root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7
  RebootRequiredPkgs:
   linux-image-5.8.0-36-generic
   linux-base
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1911814] Re: Cannot install Ubuntu 18.04 LTS Alongside Pre-Installed Windows 10

[Terry Rudd]

Daniel,

This isn't actually a kernel bug.  I will watch these for a few days but
will mark them invalid if the 18.04 dual boot install worked.  I just
don't want to erase information for 16.04 until the installer team has
some time to consider this.

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

Title:
  Cannot install Ubuntu 18.04 LTS Alongside Pre-Installed Windows 10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Also reported for Ubuntu 16.04.4 LTS:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911578

  Hello.

  I am trying to install Ubuntu 18.04.5 LTS from newly written USB
  alongside pre-installed Windows 10 on a new Acer Aspire TC-895-EB11
  desktop.

  I expected that the install process would recognize the free partition
  created on the GPT disk, but it did not.

  I had previously reviewed and followed the steps in this guide
  (https://askubuntu.com/questions/221835/how-do-i-install-ubuntu-
  alongside-a-pre-installed-windows-with-uefi).

  Secure Boot was disabled in the BIOS on the first failed attempt.  I
  tried again with Secure Boot enabled - no change. The drive &
  partitions do not appear to be recognized by Ubuntu.

  As recommended in the guide, I am submitting this bug report. Any
  assistance would be much appreciated! I only purchased this desktop to
  run Ubuntu, but would prefer to keep the Windows 10 partition usable
  in case I ever want to use it.

  Thanks!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1788 F pulseaudio
  CasperVersion: 1.394.3
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: Acer Aspire TC-895
  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 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper only-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/19/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A0
  dmi.board.name: Aspire TC-895
  dmi.board.vendor: Acer
  dmi.board.version: V:1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A0:bd05/19/2020:svnAcer:pnAspireTC-895:pvr:rvnAcer:rnAspireTC-895:rvrV1.0:cvnAcer:ct3:cvr:
  dmi.product.family: Aspire T
  dmi.product.name: Aspire TC-895
  dmi.product.sku: 
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1910503] Re: latest kernel breaks display full sizing in virtualbox

[Terry Rudd]

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

** This bug has been marked a duplicate of bug 1901904
   [SRU] virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ADT test failure with 
linux-hwe-5.8 5.8.0-25.26~20.04.1

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

Title:
  latest kernel breaks display full sizing in virtualbox

Status in linux package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in virtualbox source package in Focal:
  New

Bug description:
  kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1
  going back to kernel 5.4.0-59 makes full size display working again

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  Uname: Linux 5.4.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 09:12:44 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox-guest, 6.1.10, 5.4.0-58-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
   virtualbox-guest, 6.1.10, 5.4.0-59-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2020-05-01 (250 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=71747bce-f255-4284-aefc-caee0698739c ro quiet splash noibrs noibpb 
nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable 
no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1910806] Re: System hang - kernel 5.8.0-36

[Terry Rudd]

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

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

Title:
  System hang - kernel 5.8.0-36

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I reported what I believe to be the same problem yesterday with kernel
  -34 but running the rsync command to create a backup.

  I can cause the system to hang with the following commands:

  dd if=Win10_20H2_v2_English_x64.iso of=/dev/null bs=8192k
  cp Win10_20H2_v2_English_x64.iso /var/tmp

  The source file resides on a zfs filesystem in a raidz1 pool (4 x 4TB
  Seagate drives)

  These commands and the rsync work with kernel 5.8.0-33

  The filename describes the contents.

  zpool scrub runs without errors...

  cw0624@cascade:~/Documents/Computing/Windows$ ls -l *.iso
  -rw-r--r-- 1 jcw0624 staff 6221846528 Dec 20 12:18 
Win10_20H2_v2_English_x64.iso
  jcw0624@cascade:~/Documents/Computing/Windows$ zpool status
pool: data
   state: ONLINE
scan: scrub repaired 0B in 0 days 00:22:28 with 0 errors on Fri Jan  8 
11:48:13 2021
  config:

NAMESTATE READ WRITE CKSUM
dataONLINE   0 0 0
  raidz1-0  ONLINE   0 0 0
sda ONLINE   0 0 0
sdb ONLINE   0 0 0
sdc ONLINE   0 0 0
sdd ONLINE   0 0 0

  errors: No known data errors
  jcw0624@cascade:~/Documents/Computing/Windows$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-36-generic 5.8.0-36.40
  ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jcw06245470 F pulseaudio
   /dev/snd/controlC1:  jcw06245470 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Jan  8 11:56:46 2021
  InstallationDate: Installed on 2020-10-03 (97 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=89ed8b12-0ade-4a0f-91c3-8f9f4b3a8a81 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.190.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-11-09 (60 days ago)
  dmi.bios.date: 10/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1604
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  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.:bvr1604:bd10/16/2012:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX: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.sku: 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/1910806/+subscriptions

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

[Kernel-packages] [Bug 1910588] Re: rsync backup hang

[Terry Rudd]

Thanks Jack,

I will go ahead then and mark this invalid

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

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

Title:
  rsync backup hang

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I'm using rsync to backup directories. With kernel 5.8.0.34 it hangs
  requiring machine reset; no response from mouse or keyboard. No
  response to ping from a windows machine. All drive activity stops. The
  hang occurs with the backup drive connected via sata and via usb3
  (adapter)

  The source directories are ext4 (boot drive ssd) and zfs (raidz1 four
  x 4TB drives). The destination is a single 3TB drive formatted with
  zfs (drive is about 20% full).

  The hang occurred about 6 times before I decided to go back to kernel
  5.8.0-33 (hangs ocurred with -34). The backup worked fine with kernel
  -33 (sata and usb3 connect). The install is 20.10. Please let me know
  if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jcw06245100 F pulseaudio
   /dev/snd/pcmC0D0p:   jcw06245100 F...m pulseaudio
   /dev/snd/controlC1:  jcw06245100 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 12:07:11 2021
  InstallationDate: Installed on 2020-10-03 (96 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic 
root=UUID=89ed8b12-0ade-4a0f-91c3-8f9f4b3a8a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-34-generic N/A
   linux-backports-modules-5.8.0-34-generic  N/A
   linux-firmware1.190.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-11-09 (59 days ago)
  dmi.bios.date: 10/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1604
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  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.:bvr1604:bd10/16/2012:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX: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.sku: 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/1910588/+subscriptions

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

[Kernel-packages] [Bug 1910588] Re: rsync backup hang

[Terry Rudd]

Hi Jack.

I discussed this with other kernel engineers this morning and we also
felt this was looking more like a FW or hardware issue.  I am anxious to
hear your results.   Thanks for the detailed response.

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

Title:
  rsync backup hang

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using rsync to backup directories. With kernel 5.8.0.34 it hangs
  requiring machine reset; no response from mouse or keyboard. No
  response to ping from a windows machine. All drive activity stops. The
  hang occurs with the backup drive connected via sata and via usb3
  (adapter)

  The source directories are ext4 (boot drive ssd) and zfs (raidz1 four
  x 4TB drives). The destination is a single 3TB drive formatted with
  zfs (drive is about 20% full).

  The hang occurred about 6 times before I decided to go back to kernel
  5.8.0-33 (hangs ocurred with -34). The backup worked fine with kernel
  -33 (sata and usb3 connect). The install is 20.10. Please let me know
  if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jcw06245100 F pulseaudio
   /dev/snd/pcmC0D0p:   jcw06245100 F...m pulseaudio
   /dev/snd/controlC1:  jcw06245100 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 12:07:11 2021
  InstallationDate: Installed on 2020-10-03 (96 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic 
root=UUID=89ed8b12-0ade-4a0f-91c3-8f9f4b3a8a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-34-generic N/A
   linux-backports-modules-5.8.0-34-generic  N/A
   linux-firmware1.190.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-11-09 (59 days ago)
  dmi.bios.date: 10/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1604
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  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.:bvr1604:bd10/16/2012:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX: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.sku: 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/1910588/+subscriptions

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

[Kernel-packages] [Bug 1910588] Re: rsync backup hang

[Terry Rudd]

Jack, I just saw your message in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910806

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

Title:
  rsync backup hang

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using rsync to backup directories. With kernel 5.8.0.34 it hangs
  requiring machine reset; no response from mouse or keyboard. No
  response to ping from a windows machine. All drive activity stops. The
  hang occurs with the backup drive connected via sata and via usb3
  (adapter)

  The source directories are ext4 (boot drive ssd) and zfs (raidz1 four
  x 4TB drives). The destination is a single 3TB drive formatted with
  zfs (drive is about 20% full).

  The hang occurred about 6 times before I decided to go back to kernel
  5.8.0-33 (hangs ocurred with -34). The backup worked fine with kernel
  -33 (sata and usb3 connect). The install is 20.10. Please let me know
  if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jcw06245100 F pulseaudio
   /dev/snd/pcmC0D0p:   jcw06245100 F...m pulseaudio
   /dev/snd/controlC1:  jcw06245100 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 12:07:11 2021
  InstallationDate: Installed on 2020-10-03 (96 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic 
root=UUID=89ed8b12-0ade-4a0f-91c3-8f9f4b3a8a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-34-generic N/A
   linux-backports-modules-5.8.0-34-generic  N/A
   linux-firmware1.190.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-11-09 (59 days ago)
  dmi.bios.date: 10/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1604
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  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.:bvr1604:bd10/16/2012:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX: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.sku: 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/1910588/+subscriptions

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

[Kernel-packages] [Bug 1910588] Re: rsync backup hang

[Terry Rudd]

Have  you tested with 5.8.0-36?

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

Title:
  rsync backup hang

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using rsync to backup directories. With kernel 5.8.0.34 it hangs
  requiring machine reset; no response from mouse or keyboard. No
  response to ping from a windows machine. All drive activity stops. The
  hang occurs with the backup drive connected via sata and via usb3
  (adapter)

  The source directories are ext4 (boot drive ssd) and zfs (raidz1 four
  x 4TB drives). The destination is a single 3TB drive formatted with
  zfs (drive is about 20% full).

  The hang occurred about 6 times before I decided to go back to kernel
  5.8.0-33 (hangs ocurred with -34). The backup worked fine with kernel
  -33 (sata and usb3 connect). The install is 20.10. Please let me know
  if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jcw06245100 F pulseaudio
   /dev/snd/pcmC0D0p:   jcw06245100 F...m pulseaudio
   /dev/snd/controlC1:  jcw06245100 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 12:07:11 2021
  InstallationDate: Installed on 2020-10-03 (96 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic 
root=UUID=89ed8b12-0ade-4a0f-91c3-8f9f4b3a8a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-34-generic N/A
   linux-backports-modules-5.8.0-34-generic  N/A
   linux-firmware1.190.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-11-09 (59 days ago)
  dmi.bios.date: 10/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1604
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  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.:bvr1604:bd10/16/2012:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX: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.sku: 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/1910588/+subscriptions

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

[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8

[Terry Rudd]

Ben, can you tell us if it was 5.8.0-34 kernel or later?

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

Title:
  Black screen on boot after 20.04 upgraded to kernel 5.8

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Yesterday Ubuntu asked me to reboot after automatic updates, and when
  I rebooted it doesn't start up. Sometimes it stays on the Dell logo,
  sometimes it goes to a black screen and doesn't get past that (not
  sure what causes each variation -- perhaps for reboot it does the Dell
  logo, cold start up it does the black screen?).

  After the updates it's trying to boot the 5.8.0 kernel. In the boot
  menu, if I manually select the 5.4.0 kernel everything works fine. So
  presumably it's something about the 5.8 kernel on this hardware.

  When this occurred I was running the Nouveau open source graphics
  driver. I switched to the NVIDIA driver (460) to see if that would
  help, but it didn't change anything. So it may or may not be graphics
  related.

  I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday
  -- Jan 12, I think it would be around 13:30 that I first rebooted
  after the upgrade (and a bunch of times after that). I ran the logs
  through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the
  lines were this (presumably irrelevant):

  Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400
  audit(1610431795.003:29126): apparmor="DENIED" operation="open"
  namespace="root//lxd-juju-804318-0_"
  profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906
  comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100

  For reference:

  * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I 
think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB 
RAM.
  * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on 
"Ubuntu 20.04.1 LTS".
  * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78
  * "sudo lspci -vnvn" output is included in the attached logs.zip

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

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

[Kernel-packages] [Bug 1910483] Re: dkms and initramfs-tools dependent issue

[Terry Rudd]

Zhang, can you please include more detail and logs?

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

Title:
  dkms  and initramfs-tools dependent issue

Status in linux-restricted-modules package in Ubuntu:
  New

Bug description:
  for a complete new installed distribution, 
apt-get install linux-modules-nvidia-455-generic 
  will fail because it depends on dkms and initramfs-tools, 
  but seems not list on deb content. after initramfs-tools and dkms installed, 
apt-get install linux-modules-nvidia-455-generic 
  command ok.

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

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

[Kernel-packages] [Bug 1909496] Re: [i915] Blinking unlock screen

[Terry Rudd]

Rohit or anyone affected by this bug, can you please see comment #3?

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

Title:
  [i915] Blinking unlock screen

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I am facing this issue since the upgrade of Ubuntu to Ubuntu 20.04.1 LTS. The 
issue still persists even after re-installing Ubuntu 20.04.1 LTS.

  Due to inactivity the system goes to the Suspend mode. On restoring from the 
suspend mode the login screen appears but it starts to blink continuously 
making it impossible to use the system.
  The only option is to force restart the system.

  Please let me know if this is an already known issue/bug and if there
  is a solution available for the same.

  Thank You

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 28 19:21:12 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793]
  InstallationDate: Installed on 2020-12-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Vostro 15-3568
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=44a1973f-ce3f-46bb-ab72-156c1d047556 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 05HRPP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0793
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1907984] Re: Wifi and ethernet not working anymore since 5.4.0-54

[Terry Rudd]

There are a few bugs that seem related to this one.  The Canonical
kernel team will be investigating this further.  Thanks for the work on
this lotuspsychje.

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

Title:
  Wifi and ethernet not working anymore since 5.4.0-54

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04.1 all up to date to latest @ 13/12/2020 (LTS upgraded
  from 18.04 recently)

  Since kernel 5.4.0-54 both wifi and ethernet are not working anymore

  lower kernels -53 and -42 still work

  i attached dmesg with networking not working on 5.4.0-58

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-53-generic 5.4.0-53.59
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johan  2964 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 13 19:54:57 2020
  MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic 
root=UUID=5b035efe-03db-41c4-b44b-a415de3a0d59 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-53-generic N/A
   linux-backports-modules-5.4.0-53-generic  N/A
   linux-firmware1.187.6
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1842
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr08831138591620100:rvnHewlett-Packard:rn1842:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g7 Notebook PC
  dmi.product.sku: C6H53EA#UUG
  dmi.product.version: 08831138591620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1904848] Re: Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib module

[Terry Rudd]

thanks Amir, I believe you were on vacation so really appreciate it

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

Title:
  Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib
  module

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  unloading ib_ipoib causes a call trace to be logged in kernel buffer.

  bisecting the bionic kernel reveals that this issue was discovered by
  616e695435e3 workqueue: Try to catch flush_work() without INIT_WORK()
  in version 4.15.0-59.66

  [test case]

  # modprobe ib_ipoib
  # modprobe ib_ipoib -r
  # dmesg
  [  306.277717] [ cut here ]
  [  306.277738] WARNING: CPU: 10 PID: 2148 at 
/build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 
__flush_work+0x1f8/0x210
  [  306.277739] Modules linked in: nfsv3 nfs 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 libcrc32c 
ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter bridge stp llc binfmt_misc intel_rapl sb_edac 
x86_pkg_temp_thermal intel_powerclamp rpcrdma rdma_ucm ib_umad ib_uverbs 
coretemp ib_iser rdma_cm kvm_intel kvm iw_cm irqbypass ib_ipoib(-) libiscsi 
scsi_transport_iscsi ib_cm joydev input_leds crct10dif_pclmul crc32_pclmul 
mgag200 ttm drm_kms_helper drm hpilo ghash_clmulni_intel pcbc i2c_algo_bit 
ipmi_ssif fb_sys_fops syscopyarea sysfillrect sysimgblt aesni_intel aes_x86_64 
crypto_simd ioatdma glue_helper shpchp cryptd dca intel_cstate intel_rapl_perf
  [  306.277790]  serio_raw acpi_power_meter lpc_ich mac_hid ipmi_si 
ipmi_devintf ipmi_msghandler nfsd auth_rpcgss nfs_acl lockd grace sunrpc 
sch_fq_codel ip_tables x_tables autofs4 mlx5_ib mlx4_ib mlx4_en ib_core 
hid_generic psmouse mlx5_core usbhid hid pata_acpi hpsa tg3 mlxfw mlx4_core 
scsi_transport_sas ptp pps_core devlink
  [  306.277817] CPU: 10 PID: 2148 Comm: modprobe Not tainted 
4.15.0-124-generic #127-Ubuntu
  [  306.277818] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015
  [  306.277823] RIP: 0010:__flush_work+0x1f8/0x210
  [  306.277825] RSP: 0018:bdeb47ecfcd8 EFLAGS: 00010286
  [  306.277827] RAX: 0024 RBX: 993a5c3d8ec8 RCX: 
0006
  [  306.277829] RDX:  RSI: 99429ef16498 RDI: 
99429ef16490
  [  306.277830] RBP: bdeb47ecfd48 R08: 050d R09: 
0004
  [  306.277832] R10: e263a058c1c0 R11: 0001 R12: 
993a5c3d8ec8
  [  306.277833] R13: 0001 R14: bdeb47ecfd78 R15: 
b00a9800
  [  306.277835] FS:  7fa1124a9540() GS:99429ef0() 
knlGS:
  [  306.277837] CS:  0010 DS:  ES:  CR0: 80050033
  [  306.277839] CR2: 55b1c5007bb0 CR3: 000fcf36c002 CR4: 
001606e0
  [  306.277840] Call Trace:
  [  306.277850]  __cancel_work_timer+0x136/0x1b0
  [  306.277881]  ? mlx5_core_destroy_qp+0x99/0xd0 [mlx5_core]
  [  306.277886]  cancel_delayed_work_sync+0x13/0x20
  [  306.277909]  mlx5e_detach_netdev+0x83/0x90 [mlx5_core]
  [  306.277931]  mlx5_rdma_netdev_free+0x30/0x80 [mlx5_core]
  [  306.277941]  mlx5_ib_free_rdma_netdev+0xe/0x10 [mlx5_ib]
  [  306.277948]  ipoib_remove_one+0xe4/0x180 [ib_ipoib]
  [  306.277965]  ib_unregister_client+0x171/0x1e0 [ib_core]
  [  306.277972]  ipoib_cleanup_module+0x15/0x2f [ib_ipoib]
  [  306.277978]  SyS_delete_module+0x1ab/0x2d0
  [  306.277983]  do_syscall_64+0x73/0x130
  [  306.277989]  entry_SYSCALL_64_after_hwframe+0x41/0xa6
  [  306.277992] RIP: 0033:0x7fa111fc1047
  [  306.277993] RSP: 002b:7ffc0db32298 EFLAGS: 0206 ORIG_RAX: 
00b0
  [  306.277996] RAX: ffda RBX: 5614be46cca0 RCX: 
7fa111fc1047
  [  306.277997] RDX:  RSI: 0800 RDI: 
5614be46cd08
  [  306.277999] RBP: 5614be46cca0 R08: 7ffc0db31241 R09: 

  [  306.278000] R10: 7fa11203dc40 R11: 0206 R12: 
5614be46cd08
  [  306.278002] R13: 0001 R14: 5614be46cd08 R15: 
7ffc0db33680
  [  306.278004] Code: 24 03 80 c9 f0 e9 5b ff ff ff 48 c7 c7 18 50 0b b1 e8 ed 
66 04 00 0f 0b 31 c0 e9 75 ff ff ff 48 c7 c7 18 50 0b b1 e8 d8 66 04 00 <0f> 0b 
31 c0 e9 60 ff ff ff e8 5a 35 fe ff 66 2e 0f 1f 84 00 00
  [  306.278035] ---[ end trace 652f7759937172a2 ]---
  [  306.646061] [ cut here ]
  [  306.646077] WARNING: CPU: 6 PID: 2148 at 
/build/linux-RJNBJC/linux-4.15.0/kernel/workqueue.c:2906 
__flush_work+0x1f8/0x210
  [  306.646078] Modules linked in: nfsv3 nfs 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 

[Kernel-packages] [Bug 1907156] [NEW] Unable to run 4.14 stable kernel in 20.04 user space

[Terry Rudd]

Public bug reported:

Shuah Khan reported in IRC that she starting having problems with 4.14
only of the stable kernel after her upgrade to 20.04.  4.4 and 4.9 work
just fine.  She followed up with 4.19, 5.4 and 5.9 kernel, with no
issue.

She suspects the issue is related to compress/decompress initramfs
image.   She tried all LZO, F2FS config options.

She reports that she made sure to have CONFIG_DECOMPRESS_LZ4 and
CONFIG_F2FS_FS_LZ4 enabled. She has run into this once when she upgraded
to 20.04, which she solved by enabling CONFIG_DECOMPRESS_LZ4 at that
time.  She is very willing to help debug.

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

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

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

Title:
  Unable to run 4.14 stable kernel in 20.04 user space

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

Bug description:
  Shuah Khan reported in IRC that she starting having problems with 4.14
  only of the stable kernel after her upgrade to 20.04.  4.4 and 4.9
  work just fine.  She followed up with 4.19, 5.4 and 5.9 kernel, with
  no issue.

  She suspects the issue is related to compress/decompress initramfs
  image.   She tried all LZO, F2FS config options.

  She reports that she made sure to have CONFIG_DECOMPRESS_LZ4 and
  CONFIG_F2FS_FS_LZ4 enabled. She has run into this once when she
  upgraded to 20.04, which she solved by enabling CONFIG_DECOMPRESS_LZ4
  at that time.  She is very willing to help debug.

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

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

[Kernel-packages] [Bug 1894977] Re: IBM-iobrick patches for Ubuntu 20.04

[Terry Rudd]

Amir and Heinz-werner, it would be helpful to get some test results on
this functionality in the Ubuntu 5.8 kernel in 20.10.  Thanks in
advance.

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

Title:
   IBM-iobrick patches for Ubuntu 20.04

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

Bug description:
  Hi,

  The request is to backport 
  09689703d29a RDMA/mlx5: Do not race with mlx5_ib_invalidate_range during 
create and destroy
  with it the below list (divided to four sets) is required.

  most of the patches applied cleanly above focal tree four exceptions.

  1. 806b101b2bfa RDMA/mlx5: Use a dedicated mkey xarray for ODP
  2. b91e1751fbce RDMA/mlx5: Simplify how the MR cache bucket is located
  3. 1769c4c57548 RDMA/mlx5: Always remove MRs from the cache before destroying 
them
  4. b9358bdbc713 RDMA/mlx5: Fix locking in MR cache work queue
  the rejected hunks need to be manually applied.
  The rejected hunks are due to true<-->1 false<-->0 exchange added support for 
wc (b9358bdbc713) and other minor reasons.  

   set 0: Unrelated code cleanups (needed for applying  cleanly the mr cache 
set)
   https://patchwork.kernel.org/cover/11170991/
   909624d8db5b IB/cm: Use container_of() instead of typecast
   6f26b2ac699c IB/mlx5: Remove unnecessary else statement
   2d67c0798821 IB/mlx5: Remove unnecessary return statement
   4b2a67362e78 RDMA/mlx5: Group boolean parameters to take less space

   set 1: Rework the locking and datastructures for mlx5 implicit ODP
   https://patchwork.kernel.org/cover/11181509/
   46870b2391d5 RDMA/odp: Remove broken debugging call to invalidate_range
   09689703d29a RDMA/mlx5: Do not race with mlx5_ib_invalidate_range during 
create and destroy
   d561987f34f2 RDMA/mlx5: Do not store implicit children in the odp_mkeys 
xarray
   5256edcb98a1 RDMA/mlx5: Rework implicit ODP destroy
   b70d785d237c RDMA/mlx5: Avoid double lookups on the pagefault path
   3389baa831b6 RDMA/mlx5: Reduce locking in implicit_mr_get_data()
   423f52d65005 RDMA/mlx5: Use an xarray for the children of an implicit ODP
   54375e738295 RDMA/mlx5: Split implicit handling from pagefault_mr
   9162420dde49 RDMA/mlx5: Set the HW IOVA of the child MRs to their place in 
the tree
   c2edcd69351f RDMA/mlx5: Lift implicit_mr_alloc() into the two routines that 
call it
   3d5f3c54e7bc RDMA/mlx5: Rework implicit_mr_get_data
   74bddb3682f6 RDMA/mlx5: Delete struct mlx5_priv->mkey_table
   806b101b2bfa RDMA/mlx5: Use a dedicated mkey xarray for ODP
   50211ec9443f RDMA/mlx5: Split sig_err MR data into its own xarray
   fb985e278a30 RDMA/mlx5: Use SRCU properly in ODP prefetch

  
   set 2: Consolidate the mmu notifier interval_tree and locking (only first 
two patches from this set)
   https://patchwork.kernel.org/cover/11240081/
   99cb252f5e68 mm/mmu_notifier: add an interval tree notifier
   56f434f40f05 mm/mmu_notifier: define the header pre-processor parts even if 
disabled

  
   also needed for applying  mr cache set cleanly.
   03232cc43cff IB/mlx5: Introduce and use mkey context setting helper routine

   set 3: MR cache fixes and refactoring
   https://www.spinics.net/lists/linux-rdma/msg89706.html
   aad719dcf379 RDMA/mlx5: Allow MRs to be created in the cache synchronously
   1c78a21a0c6f RDMA/mlx5: Revise how the hysteresis scheme works for cache 
filling
   b9358bdbc713 RDMA/mlx5: Fix locking in MR cache work queue
   ad2d3ef46d2a RDMA/mlx5: Lock access to ent->available_mrs/limit when doing 
queue_work
   a1d8854aae4e RDMA/mlx5: Fix MR cache size and limit debugfs
   1769c4c57548 RDMA/mlx5: Always remove MRs from the cache before destroying 
them
   b91e1751fbce RDMA/mlx5: Simplify how the MR cache bucket is located
   7c8691a396bd RDMA/mlx5: Rename the tracking variables for the MR cache
   f743ff3b37df RDMA/mlx5: Replace spinlock protected write with atomic var
   a3cfdd392811 {IB,net}/mlx5: Move asynchronous mkey creation to mlx5_ib
   fc6a9f86f08a {IB,net}/mlx5: Assign mkey variant in mlx5_ib only
   54c62e13ad76 {IB,net}/mlx5: Setup mkey variant before mr create command 
invocation

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

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

[Kernel-packages] [Bug 1855809] Re: vclib from ubuntu_k8s_unit_tests fail on Focal-5.4-GCP

[Terry Rudd]

** Summary changed:

- vclib from ubuntu_k8s_unit_tests fail on Eoan 5.3 GCP / F-5.4-GCP
+ vclib from ubuntu_k8s_unit_tests fail on Focal-5.4-GCP

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

Title:
  vclib from ubuntu_k8s_unit_tests fail on Focal-5.4-GCP

Status in ubuntu-kernel-tests:
  New
Status in linux-gcp package in Ubuntu:
  New

Bug description:
  Issue found on 5.3.0-1010 Eoan GCP

   E1207 09:14:34.779687 29118 datacenter.go:45] Failed to find the datacenter: 
enoent. err: datacenter 'enoent' not found
   E1207 09:14:34.783331 29118 datacenter.go:78] Unable to find VM by UUID. VM 
UUID: enoent
   E1207 09:14:34.785587 29118 datacenter.go:106] Failed to find VM by Path. VM 
Path: enoent, err: vm 'enoent' not found
   E1207 09:14:34.787217 29118 datacenter.go:153] Failed to parse vmDiskPath: 
enoent
   E1207 09:14:34.788754 29118 datacenter.go:165] Failed while searching for 
datastore: enoent. err: datastore 'enoent' not found
   E1207 09:14:34.792557 29118 datacenter.go:165] Failed while searching for 
datastore: enoent. err: datastore 'enoent' not found
   E1207 09:14:34.801865 29118 datacenter.go:191] Failed to get the folder 
reference for enoent. err: folder 'enoent' not found
   E1207 09:14:34.804569 29118 datacenter.go:203] VirtualMachine Object list is 
empty
   E1207 09:14:34.805548 29118 datacenter.go:213] Failed to get VM managed 
objects from VM objects. vmObjList: [VirtualMachine:vm-54 @ 
/DC0/vm/DC0_H0_VM1], properties: [enoent], err: InvalidProperty
   E1207 09:14:34.806781 29118 datacenter.go:241] Datastore Object list is empty
   E1207 09:14:34.807159 29118 datacenter.go:251] Failed to get Datastore 
managed objects from datastore objects. dsObjList: 
[Datastore:/tmp/govcsim-DC0-LocalDS_0-314024335@folder-5 @ 
/DC0/datastore/LocalDS_0], properties: [enoent], err: InvalidProperty
   E1207 09:14:34.968117 29118 connection.go:180] Failed to create new client. 
err: EOF
   2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:58028: remote 
error: tls: bad certificate
   E1207 09:14:35.039988 29118 connection.go:180] Failed to create new client. 
err: Post https://127.0.0.1:35147/sdk: Host "127.0.0.1:35147" thumbprint does 
not match "obviously wrong"
   E1207 09:14:35.052610 29118 connection.go:180] Failed to create new client. 
err: Post https://127.0.0.1:40591/sdk: x509: certificate signed by unknown 
authority
   2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:37506: remote 
error: tls: bad certificate
   2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:33050: remote 
error: tls: bad certificate
   E1207 09:14:35.081393 29118 connection.go:180] Failed to create new client. 
err: EOF
   E1207 09:14:35.081489 29118 connection.go:163] Failed to parse URL: . err: 
parse https://should-not-matter:should-not-matter: invalid port 
":should-not-matter" after host
   --- FAIL: TestWithInvalidCaCertPath (0.00s)
   connection_test.go:168: Expected an os.PathError, got: 'parse 
https://should-not-matter:should-not-matter: invalid port ":should-not-matter" 
after host' ({Op:"parse", 
URL:"https://should-not-matter:should-not-matter;, 
Err:(*errors.errorString)(0xc0004fcd70)})
   E1207 09:14:35.081626 29118 connection.go:163] Failed to parse URL: . err: 
parse https://should-not-matter:should-not-matter: invalid port 
":should-not-matter" after host
   --- FAIL: TestInvalidCaCert (0.00s)
   connection_test.go:182: Expected invalid certificate error, got 'parse 
https://should-not-matter:should-not-matter: invalid port ":should-not-matter" 
after host'
   FAIL
   FAIL   k8s.io/kubernetes/pkg/cloudprovider/providers/vsphere/vclib 0.319s

  This is not a regression as this failure can be found in
  5.3.0-1009.10-gcp as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855809/+subscriptions

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

[Kernel-packages] [Bug 1855808] Re: cmd from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP

[Terry Rudd]

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

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

Title:
  cmd from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP

Status in ubuntu-kernel-tests:
  New
Status in linux-gcp package in Ubuntu:
  Won't Fix

Bug description:
  Issue found on 5.3.0-1010 Eoan GCP

   [preflight] running pre-flight checks
   [preflight] running pre-flight checks
   [reset] deleting contents of config directories: 
[/tmp/kubeadm-reset-test690031695/manifests 
/tmp/kubeadm-reset-test690031695/pki]
   [reset] deleting files: [/tmp/kubeadm-reset-test690031695/admin.conf 
/tmp/kubeadm-reset-test690031695/kubelet.conf 
/tmp/kubeadm-reset-test690031695/bootstrap-kubelet.conf 
/tmp/kubeadm-reset-test690031695/controller-manager.conf 
/tmp/kubeadm-reset-test690031695/scheduler.conf]
   [reset] deleting contents of config directories: 
[/tmp/kubeadm-reset-test190360418/manifests 
/tmp/kubeadm-reset-test190360418/pki]
   [reset] deleting files: [/tmp/kubeadm-reset-test190360418/admin.conf 
/tmp/kubeadm-reset-test190360418/kubelet.conf 
/tmp/kubeadm-reset-test190360418/bootstrap-kubelet.conf 
/tmp/kubeadm-reset-test190360418/controller-manager.conf 
/tmp/kubeadm-reset-test190360418/scheduler.conf]
   [reset] deleting contents of config directories: 
[/tmp/kubeadm-reset-test519448409/manifests 
/tmp/kubeadm-reset-test519448409/pki]
   [reset] deleting files: [/tmp/kubeadm-reset-test519448409/admin.conf 
/tmp/kubeadm-reset-test519448409/kubelet.conf 
/tmp/kubeadm-reset-test519448409/bootstrap-kubelet.conf 
/tmp/kubeadm-reset-test519448409/controller-manager.conf 
/tmp/kubeadm-reset-test519448409/scheduler.conf]
   [reset] deleting contents of config directories: 
[/tmp/kubeadm-reset-test499669220/manifests 
/tmp/kubeadm-reset-test499669220/pki]
   [reset] deleting files: [/tmp/kubeadm-reset-test499669220/admin.conf 
/tmp/kubeadm-reset-test499669220/kubelet.conf 
/tmp/kubeadm-reset-test499669220/bootstrap-kubelet.conf 
/tmp/kubeadm-reset-test499669220/controller-manager.conf 
/tmp/kubeadm-reset-test499669220/scheduler.conf]
   [reset] deleting contents of config directories: 
[/tmp/kubeadm-reset-test469422835/manifests 
/tmp/kubeadm-reset-test469422835/test-path]
   E1207 09:05:16.966842 26490 reset.go:227] [reset] failed to remove 
directory: "/tmp/kubeadm-reset-test469422835/test-path" [readdirent: not a 
directory]
   [reset] deleting files: [/tmp/kubeadm-reset-test469422835/admin.conf 
/tmp/kubeadm-reset-test469422835/kubelet.conf 
/tmp/kubeadm-reset-test469422835/bootstrap-kubelet.conf 
/tmp/kubeadm-reset-test469422835/controller-manager.conf 
/tmp/kubeadm-reset-test469422835/scheduler.conf]
   [reset] deleting contents of config directories: 
[/tmp/kubeadm-reset-test838040502/manifests 
/tmp/kubeadm-reset-test838040502/pki]
   [reset] deleting files: [/tmp/kubeadm-reset-test838040502/admin.conf 
/tmp/kubeadm-reset-test838040502/kubelet.conf 
/tmp/kubeadm-reset-test838040502/bootstrap-kubelet.conf 
/tmp/kubeadm-reset-test838040502/controller-manager.conf 
/tmp/kubeadm-reset-test838040502/scheduler.conf]
   [dryrun] Would perform action DELETE on resource "secrets" in API group 
"core/v1"
   [dryrun] Resource name: "bootstrap-token-abcdef"
   [dryrun] Would perform action DELETE on resource "secrets" in API group 
"core/v1"
   [dryrun] Resource name: "bootstrap-token-abcdef"
   [dryrun] Would perform action DELETE on resource "secrets" in API group 
"core/v1"
   [dryrun] Resource name: "bootstrap-token-abcdef"
   [dryrun] Would perform action LIST on resource "secrets" in API group 
"core/v1"
   dummy API server listening on localhost:9008
   Running HTTP test case (0) "token-id not defined"
   [dryrun] Would perform action LIST on resource "secrets" in API group 
"core/v1"
   panic: test timed out after 2m0s

   goroutine 41 [running]:
   testing.(*M).startAlarm.func1()
   /usr/lib/go-1.12/src/testing/testing.go:1334 +0xdf
   created by time.goFunc
   /usr/lib/go-1.12/src/time/sleep.go:169 +0x44

   goroutine 1 [chan receive, 1 minutes]:
   testing.(*T).Run(0xc00043c400, 0x1711494, 0x11, 0x17ab5f8, 0x481e01)
   /usr/lib/go-1.12/src/testing/testing.go:917 +0x381
   testing.runTests.func1(0xcd9d00)
   /usr/lib/go-1.12/src/testing/testing.go:1157 +0x78
   testing.tRunner(0xcd9d00, 0xc0005f7e30)
   /usr/lib/go-1.12/src/testing/testing.go:865 +0xc0
   testing.runTests(0xc0001ea320, 0x2781c20, 0x14, 0x14, 0x0)
   /usr/lib/go-1.12/src/testing/testing.go:1155 +0x2a9
   testing.(*M).Run(0xc000324e00, 0x0)
   /usr/lib/go-1.12/src/testing/testing.go:1072 +0x162
   main.main()
   _testmain.go:82 +0x13e

   goroutine 5 [chan receive]:
   
k8s.io/kubernetes/vendor/github.com/golang/glog.(*loggingT).flushDaemon(0x2790e60)
   
/tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/github.com/golang/glog/glog.go:879
 +0x8b
   created by 

[Kernel-packages] [Bug 1894977] Re: IBM-iobrick patches for Ubuntu 20.04

[Terry Rudd]

The Canonical Stable kernel team continues to evaluate this rather large
and quite intrusive patch set.  Put simply, this does not belong on a
stable kernel directly.  That said, we continue to evaluate inclusion by
way of potentially including it via an HWE kernel and porting back over
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/1894977

Title:
   IBM-iobrick patches for Ubuntu 20.04

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

Bug description:
  Hi,

  The request is to backport 
  09689703d29a RDMA/mlx5: Do not race with mlx5_ib_invalidate_range during 
create and destroy
  with it the below list (divided to four sets) is required.

  most of the patches applied cleanly above focal tree four exceptions.

  1. 806b101b2bfa RDMA/mlx5: Use a dedicated mkey xarray for ODP
  2. b91e1751fbce RDMA/mlx5: Simplify how the MR cache bucket is located
  3. 1769c4c57548 RDMA/mlx5: Always remove MRs from the cache before destroying 
them
  4. b9358bdbc713 RDMA/mlx5: Fix locking in MR cache work queue
  the rejected hunks need to be manually applied.
  The rejected hunks are due to true<-->1 false<-->0 exchange added support for 
wc (b9358bdbc713) and other minor reasons.  

   set 0: Unrelated code cleanups (needed for applying  cleanly the mr cache 
set)
   https://patchwork.kernel.org/cover/11170991/
   909624d8db5b IB/cm: Use container_of() instead of typecast
   6f26b2ac699c IB/mlx5: Remove unnecessary else statement
   2d67c0798821 IB/mlx5: Remove unnecessary return statement
   4b2a67362e78 RDMA/mlx5: Group boolean parameters to take less space

   set 1: Rework the locking and datastructures for mlx5 implicit ODP
   https://patchwork.kernel.org/cover/11181509/
   46870b2391d5 RDMA/odp: Remove broken debugging call to invalidate_range
   09689703d29a RDMA/mlx5: Do not race with mlx5_ib_invalidate_range during 
create and destroy
   d561987f34f2 RDMA/mlx5: Do not store implicit children in the odp_mkeys 
xarray
   5256edcb98a1 RDMA/mlx5: Rework implicit ODP destroy
   b70d785d237c RDMA/mlx5: Avoid double lookups on the pagefault path
   3389baa831b6 RDMA/mlx5: Reduce locking in implicit_mr_get_data()
   423f52d65005 RDMA/mlx5: Use an xarray for the children of an implicit ODP
   54375e738295 RDMA/mlx5: Split implicit handling from pagefault_mr
   9162420dde49 RDMA/mlx5: Set the HW IOVA of the child MRs to their place in 
the tree
   c2edcd69351f RDMA/mlx5: Lift implicit_mr_alloc() into the two routines that 
call it
   3d5f3c54e7bc RDMA/mlx5: Rework implicit_mr_get_data
   74bddb3682f6 RDMA/mlx5: Delete struct mlx5_priv->mkey_table
   806b101b2bfa RDMA/mlx5: Use a dedicated mkey xarray for ODP
   50211ec9443f RDMA/mlx5: Split sig_err MR data into its own xarray
   fb985e278a30 RDMA/mlx5: Use SRCU properly in ODP prefetch

  
   set 2: Consolidate the mmu notifier interval_tree and locking (only first 
two patches from this set)
   https://patchwork.kernel.org/cover/11240081/
   99cb252f5e68 mm/mmu_notifier: add an interval tree notifier
   56f434f40f05 mm/mmu_notifier: define the header pre-processor parts even if 
disabled

  
   also needed for applying  mr cache set cleanly.
   03232cc43cff IB/mlx5: Introduce and use mkey context setting helper routine

   set 3: MR cache fixes and refactoring
   https://www.spinics.net/lists/linux-rdma/msg89706.html
   aad719dcf379 RDMA/mlx5: Allow MRs to be created in the cache synchronously
   1c78a21a0c6f RDMA/mlx5: Revise how the hysteresis scheme works for cache 
filling
   b9358bdbc713 RDMA/mlx5: Fix locking in MR cache work queue
   ad2d3ef46d2a RDMA/mlx5: Lock access to ent->available_mrs/limit when doing 
queue_work
   a1d8854aae4e RDMA/mlx5: Fix MR cache size and limit debugfs
   1769c4c57548 RDMA/mlx5: Always remove MRs from the cache before destroying 
them
   b91e1751fbce RDMA/mlx5: Simplify how the MR cache bucket is located
   7c8691a396bd RDMA/mlx5: Rename the tracking variables for the MR cache
   f743ff3b37df RDMA/mlx5: Replace spinlock protected write with atomic var
   a3cfdd392811 {IB,net}/mlx5: Move asynchronous mkey creation to mlx5_ib
   fc6a9f86f08a {IB,net}/mlx5: Assign mkey variant in mlx5_ib only
   54c62e13ad76 {IB,net}/mlx5: Setup mkey variant before mr create command 
invocation

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

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

[Kernel-packages] [Bug 1888001] Re: Focal minimal cloud image: failed to apply kernel variables

[Terry Rudd]

Josh, did your suggestion above resolve this?

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

Title:
  Focal minimal cloud image: failed to apply kernel variables

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Overview
  ---
  It appears the Focal minimal images have always shipped with a failing 
systemd unit: "systemd-sysctl.service" with the error "Couldn't write '4194304' 
to 'kernel/pid_max': Invalid argument"

  Expected results
  ---
  $ sudo systemctl list-units --failed --no-legend
  # Return no failed units

  Actual results
  ---
  $ sudo systemctl list-units --failed --no-legend
  systemd-sysctl.service loaded failed failed Apply Kernel Variables

  
  From the journal:
  Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Main process exit
  ed, code=exited, status=1/FAILURE
  Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Faile
  d with result 'exit-code'.
  Jul 20 12:18:53 ubuntu systemd[1]: Failed to start Apply Kernel Variables.

  Jul 20 12:18:53 ubuntu systemd-sysctl[135]: Couldn't write '4194304' to 'ker
  nel/pid_max': Invalid argument

  
  Steps to reproduce
  ---
  $ wget 
https://cloud-images.ubuntu.com/daily/server/minimal/releases/focal/release/ubuntu-20.04-minimal-cloudimg-amd64.img
  $ multipass launch file:///$(pwd)/ubuntu-20.04-minimal-cloudimg-amd64.img 
--name=focal-minimal
  $ multipass exec focal-minimal -- sudo systemctl list-units --failed 
--no-legend

  
  ---
  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'
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1018-kvm 
root=PARTUUID=4a94aad5-09c7-46a5-aa33-f2f2e03254e7 ro console=tty1 console=ttyS0
  ProcVersionSignature: User Name 5.4.0-1018.18-kvm 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-1018-kvm N/A
   linux-backports-modules-5.4.0-1018-kvm  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1018-kvm x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1888000] Re: Bionic/Xenial minimal cloud image: failed to apply load kernel module

[Terry Rudd]

We have determined nothing has changed in those kernels from last cycle
or this cycle.  We think something changed in the CPC environment that
might have triggered what we think might be an old bug.  But we need to
CPC help to identify the "last good kernel" and the "first bad kernel".
Once we can isolate, we can have a more useful investigation

We have determined that ib_iser.ko is not in 4.15.0-1069-kvm but it
wasn't there in the previous cycle's kernel and is not in the current
proposed 4.15.0-1071.72 cycle either.  I don't think we should try to
make a change, re-spin, then ask the CPC team to test, especially since
we never made the breaking-change in the first place (as far as we know
at least).   Once we know what changed we can make the right choice.

Hopefully this is a reasonable approach

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

Title:
  Bionic/Xenial minimal cloud image: failed to apply load kernel module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Overview
  ---
  This is *blocking* new minimal image promotion. Starting on or around 
20200714, the Bionic and Xenial minimal cloud images reported they failed to 
load kernel modules. 

  
  Expected results
  ---
  $ sudo systemctl list-units --failed --no-legend
  # Return no failed units

  
  Actual results
  ---
  $ sudo systemctl list-units --failed --no-legend
  systemd-sysctl.service loaded failed failed Apply Kernel Variables
  # cloud-config.service may show up failing to setup the timezone...

  From the journal:
  Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Module 'iscsi_tcp' is builtin
  Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Failed to find module 
'ib_iser'
  Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write '176' to 
'kernel/sysrq', ignoring: No such file or directory
  Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write 'fq_codel' to 
'net/core/default_qdisc', ignoring: No such file or directory

  
  Steps to reproduce
  ---
  1. Download image from: 
https://private-fileshare.canonical.com/~powersj/minimal-bionic/
  2. multipass launch file:///
  3. multipass exec  -- sudo systemctl list-units --failed --no-legend
  --- 
  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.9-0ubuntu7.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 
'fuser'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb'
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1069-kvm 
root=PARTUUID=ffb7214d-c783-45ed-b736-278d4ee0cac0 ro console=tty1 console=ttyS0
  ProcVersionSignature: User Name 4.15.0-1069.70-kvm 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1069-kvm N/A
   linux-backports-modules-4.15.0-1069-kvm  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-1069-kvm x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

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

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

[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 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 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 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 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 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 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 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 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 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 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 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 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 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 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=grep=brauner).

  See https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  
bionic.git/commit/debian.master/config/config.common.ubuntu?h=hwe=a758aeb0bb0f52ccbee99f850709c57711753b33
  and https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  
bionic.git/commit/debian.master/config/config.common.ubuntu?h=hwe=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

Re: [Kernel-packages] [Bug 1741860] Re: Use the kernel default for crashkernel offset

[Terry Rudd]

On 9/30/19 7:47 AM, Andrew Cloke wrote:
> Following f2f discussions, next step is to re-upload new version of
> makedumpfile.
> 

Pushing on this one too.

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

Title:
  Use the kernel default for crashkernel offset

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  Won't Fix
Status in makedumpfile source package in Disco:
  Fix Committed
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The value chosen for ppc64el of 128MB aligns with that of the
  kernel default. That may change some day, so it would be best to let
  the kernel decide what value it should use. If the value does change
  and the kernel is not allowed to choose a value, this may stop the
  kernel from booting on a production system.

  [Test Case]

   Run `cat /etc/default/grub.d/kdump-tools.cfg`

   * Expected result: there is no offset specified at the end of the
  line (.e.g, @128M).

   * Actual result: For Xenial, Bionic, Disco, and Eoan there are
  offsets specified.

  [Regression Potential]

   * Right now, the offset described in the kdump-tools.cfg aligns with
  that of what the kernel would select, so since they are the same we
  would expect no change in operation.

  
  Original bug description follows:
  -

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-08 
01:06:41 ==
  ---Problem Description---
  A default offset of 128MB is enforced for crashkernel by kdump-tools utility
  overriding the kernel default.

  While the kernel default offset for crashkernel is also 128MB, that may change
  and the right thing to do would be to let the kernel decide on the offset of
  crashkernel in the default scenario..

  Get rid of "@128M" in kdump-tools.cfg file

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   # cat /etc/default/grub.d/kdump-tools.cfg
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M"
  ---

  The offset is specified via kdump-tools where as the kernel may be the right 
place to
  set an offset by default..

  Userspace tool common name: kdump-tools

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - MAMATHA INAMDAR  - 2018-01-08 03:05:05 
==
  This bug is opened to follow-up other bug based on the comment 19
  https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical 
Launchpad1676884 )

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

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

[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB

[Terry Rudd]

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

Title:
  Avoid migration issues with aligned 2MB THB

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

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

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

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

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

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

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

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

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

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

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

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

[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 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 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 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]

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

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

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