date:20200720

This change was made by a bot.

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

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

Title:
  [amdgpu] Xorg freeze

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I have Radeon Pro WX 7100. It hangs twice a day.

  I narrow-downed this issue to the fan speed lock. After reboot, it
  always runs on 18%, no matter of the load. If I install Radeon Profile
  and force fan to 100% and then turn auto fan configuration, then fan
  reacts on the load.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 09:15:03 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100] 
[1002:67c4] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 
7100] [1002:0b0d]
  InstallationDate: Installed on 2020-06-29 (20 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=2b68d049-e85f-47ab-97d9-5632f225b71b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7803
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7803:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Kernel-packages] [Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel

The test has passed with 5.4.0-42.46 on all different arches.

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3
  / 5.4 kernel

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Failure to run ip_defrag deterministically.

  [Fix]
  Use smaller packets and ignore EPERM.

  [Test case]
  Run the test multiple times without observing failures.

  [Regression potential]
  If the test fix is incorrect, it will cause us to miss real kernel bugs. But 
as it is now, we are already ignoring its results.

  
  ==

  Test failed becuase:
     ./ip_defrag: sendto overlap: 1400: Operation not permitted

   selftests: net: ip_defrag.sh
   
   ipv6 tx:17 gso:1 (fail)
   OK
   ipv4 defrag
   PASS
   seed = 1556203721
   ipv4 defrag with overlaps
   PASS
   seed = 1556203722
   ipv6 defrag
   seed = 1556203756
   PASS
   ipv6 defrag with overlaps
   seed = 1556203756
   ./ip_defrag: sendto overlap: 1400: Operation not permitted
   not ok 1..17 selftests: net: ip_defrag.sh [FAIL]

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

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

[Kernel-packages] [Bug 1881137] Re: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers

2020-07-20 Thread Alberto Milone

The results look good to me. The only case that looks like a failure
doesn't really have the nvidia modules loaded, so it's ok.

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal
** Tags added: verification-done verification-done-bionic 
verification-done-focal

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

Title:
  Introduce the new NVIDIA 418-server and 440-server series, and update
  the current NVIDIA drivers

Status in linux package in Ubuntu:
  Incomplete
Status in linux-restricted-modules package in Ubuntu:
  New
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-440-server source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-440-server source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  440.82:
    * New upstream release:
  - Added a workaround for Steam Play title DOOM Eternal, which
    overrides application requested memory locations, to ensure
    performance-critical resources be placed in video memory.
  - Allow presenting from queue families which only expose
    VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib
    surfaces.
  - Fixed a bug that caused render-offloaded applications to crash
    on exit.
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'timespec_to_ns'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'getrawmonotonic'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'timespec_to_ns'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'getrawmonotonic'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'getnstimeofday'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "dereferencing pointer to incomplete type 'struct
    timeval'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'jiffies_to_timespec'".
  - Fixed driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "passing argument 4 of 'proc_create_data' from
    incompatible pointer type".

  440.64.00:
    * Init

Re: [Kernel-packages] [Bug 1888193] Re: Xorg freeze

2020-07-20 Thread Maksym Wezdecki

Issues in dmesg in kernel are my fault - I'm developing app, which faults
GPU.

Have you read my description of the narrowed down issue?

pon., 20 lip 2020 o 09:50 Daniel van Vugt <1888...@bugs.launchpad.net>
napisał(a):

> This looks like a hardware or driver problem with the Radeon Pro WX
> 7100. Your logs show two issues:
>
> 1. Xorg logs that the monitor is being repeatedly redetected. So it
> sounds like the monitor is not plugged in properly. Maybe try a new
> monitor cable.
>
> 2. The kernel is logging more serious issues:
>
> [  107.569355] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38480c for
> process mksReplay pid 2764 thread main-mks pid 2772
> [  107.569358] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR
>  0x0030C387
> [  107.569359] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x0804800C
> [  107.569360] amdgpu :0a:00.0: VM fault (0x0c, vmid 4, pasid 32785)
> at page 3195783, read from 'TC4' (0x54433400) (72)
> [  107.569365] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38880c for
> process mksReplay pid 2764 thread main-mks pid 2772
> [  107.569366] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR
>  0x0030C38E
> [  107.569367] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x0808400C
> [  107.569368] amdgpu :0a:00.0: VM fault (0x0c, vmid 4, pasid 32785)
> at page 3195790, read from 'TC7' (0x54433700) (132)
> [  107.597584] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38480c for
> process mksReplay pid 2764 thread main-mks pid 2772
> [  107.597587] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR
>  0x0030C387
> [  107.597588] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x0E04800C
> [  107.597590] amdgpu :0a:00.0: VM fault (0x0c, vmid 7, pasid 32785)
> at page 3195783, read from 'TC4' (0x54433400) (72)
> [  107.597595] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38880c for
> process mksReplay pid 2764 thread main-mks pid 2772
> [  107.597596] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR
>  0x0030C38D
> [  107.597597] amdgpu :0a:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x0E04400C
> [  107.597598] amdgpu :0a:00.0: VM fault (0x0c, vmid 7, pasid 32785)
> at page 3195789, read from 'TC5' (0x54433500) (68)
> [
>
> ** Tags added: amdgpu
>
> ** Summary changed:
>
> - Xorg freeze
> + [amdgpu] Xorg freeze
>
> ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)
>
> ** Also affects: linux (Ubuntu)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1888193
>
> Title:
>   [amdgpu] Xorg freeze
>
> Status in linux package in Ubuntu:
>   New
> Status in xserver-xorg-video-amdgpu package in Ubuntu:
>   New
>
> Bug description:
>   I have Radeon Pro WX 7100. It hangs twice a day.
>
>   I narrow-downed this issue to the fan speed lock. After reboot, it
>   always runs on 18%, no matter of the load. If I install Radeon Profile
>   and force fan to 100% and then turn auto fan configuration, then fan
>   reacts on the load.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
>   Uname: Linux 5.3.0-62-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.15
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Jul 20 09:15:03 2020
>   DistUpgraded: Fresh install
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GpuHangFrequency: Very infrequently
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100]
> [1002:67c4] (prog-if 00 [VGA controller])
>  Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon
> Pro WX 7100] [1002:0b0d]
>   InstallationDate: Installed on 2020-06-29 (20 days ago)
>   InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
> (20190805)
>   MachineType: System manufacturer System Product Name
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic
> root=UUID=2b68d049-e85f-47ab-97d9-5632f225b71b ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 06/17/2020
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 7803
>   dmi.board.asset.tag: Default string
>   dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: Rev 1.xx
>   dmi.chassis.asset.tag: Default string
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Default string
>   dmi.chassis.version: Default string
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr7803:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnAS

[Kernel-packages] [Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel

The test has passed with 5.3.0-64.58 on all different arches.

** Tags removed: verification-needed-eoan
** Tags added: verification-done-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/1826848

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3
  / 5.4 kernel

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Failure to run ip_defrag deterministically.

  [Fix]
  Use smaller packets and ignore EPERM.

  [Test case]
  Run the test multiple times without observing failures.

  [Regression potential]
  If the test fix is incorrect, it will cause us to miss real kernel bugs. But 
as it is now, we are already ignoring its results.

  
  ==

  Test failed becuase:
     ./ip_defrag: sendto overlap: 1400: Operation not permitted

   selftests: net: ip_defrag.sh
   
   ipv6 tx:17 gso:1 (fail)
   OK
   ipv4 defrag
   PASS
   seed = 1556203721
   ipv4 defrag with overlaps
   PASS
   seed = 1556203722
   ipv6 defrag
   seed = 1556203756
   PASS
   ipv6 defrag with overlaps
   seed = 1556203756
   ./ip_defrag: sendto overlap: 1400: Operation not permitted
   not ok 1..17 selftests: net: ip_defrag.sh [FAIL]

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

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

[Kernel-packages] [Bug 1878421] Re: Using two GPUs with one monitor each, one is always black

2020-07-20 Thread frank

https://gitlab.gnome.org/GNOME/mutter/-/issues/1351

but currently it looks related to nvidia/nouveau driver

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1351
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1351

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

Title:
  Using two GPUs with one monitor each, one is always black

Status in Mutter:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi,

  i try to use external monitor on my dell G5 2019 (5590). works on
  ubuntu 18.4 (after reboot) using prime-select nvidia.

  did this on 20.4 (prime-select + reboot because logoff/login again
  still don't work) and it hang on boot while showing ubuntu bootscreen
  with animation (not stopped, but also response to esc-key to show
  terminal-output) on the monitor (need to switch off). booted again
  where monitor is configured to other input, boot works, i see it in
  preferences dialog as second monitor, but if i configure input on
  monitor i have no signal..

  
  anything i can try?

  regards Frank

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 13 15:21:08 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea]
  InstallationDate: Installed on 2020-04-27 (16 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 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. G5 5590
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0KW84T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  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.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/mutter/+bug/1878421/+subscriptions

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

[Kernel-packages] [Bug 1888202] [NEW] package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit statu

2020-07-20 Thread Ate Siemensma

Public bug reported:

the upgrade process assumes ZFS-utils is not configured and has exit
code 1

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: zfsutils-linux 0.8.3-1ubuntu12.1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.3
AptOrdering:
 gir1.2-webkit2-4.0:amd64: Install
 gir1.2-javascriptcoregtk-4.0:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Jul 20 10:22:00 2020
ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2016-05-15 (1526 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: zfs-linux
Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2020-05-24 (56 days ago)

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


** Tags: amd64 apport-package focal

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

Title:
  package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade:
  installed zfsutils-linux package post-installation script subprocess
  returned error exit status 1

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  the upgrade process assumes ZFS-utils is not configured and has exit
  code 1

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: zfsutils-linux 0.8.3-1ubuntu12.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  AptOrdering:
   gir1.2-webkit2-4.0:amd64: Install
   gir1.2-javascriptcoregtk-4.0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jul 20 10:22:00 2020
  ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-05-15 (1526 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-24 (56 days ago)

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

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

[Kernel-packages] [Bug 1888202] Re: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status

2020-07-20 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade:
  installed zfsutils-linux package post-installation script subprocess
  returned error exit status 1

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  the upgrade process assumes ZFS-utils is not configured and has exit
  code 1

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: zfsutils-linux 0.8.3-1ubuntu12.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  AptOrdering:
   gir1.2-webkit2-4.0:amd64: Install
   gir1.2-javascriptcoregtk-4.0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jul 20 10:22:00 2020
  ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-05-15 (1526 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-24 (56 days ago)

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

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

[Kernel-packages] [Bug 1879470] Re: stress-ng on gcov enabled focal kernel triggers OOPS

2020-07-20 Thread Colin Ian King

** Description changed:

- Running stress-ng coverage testss on an ARM64 VM gcov 5.4.0-26-generic
- focal kernel trips the following oops:
+ == SRU Justification Focal RISC-V ==
+ 
+ Running stress-ng coverage tests on an ARM64 VM gcov 5.4.0-26-generic
+ focal kernel trips an oops because the kernel stack is too small.
+ 
+ == Fix ==
+ 
+ Clean Upstream commit:
+ 
+ commit 0cac21b02ba5f3095fd2dcc77c26a25a0b2432ed
+ Author: Andreas Schwab 
+ Date:   Mon Jul 6 14:32:26 2020 +0200
+ 
+ riscv: use 16KB kernel stack on 64-bit
+ 
+ == Test ==
+ 
+ Without the fix, we hit stack overflows. Run stress-ng kernel-
+ coverage.sh script with gcov enabled and the issue occurs. With the fix
+ the issue does not occur.
+ 
+ == Regression Potential ==
+ 
+ This fix just affects 64 bit RISC-V and doubles the stack size. In
+ systems that run thousands of processes will see more memory being
+ consumed, but this most probably won't bite anyone because RISC-V
+ systems are generally not used in this manner.
+ 
+ 
+ 
+ 
+ 
+ Running stress-ng coverage tests on an ARM64 VM gcov 5.4.0-26-generic focal 
kernel trips the following oops:
  
  cd stress-ng
  ./kernel-coverage.sh
  
  [  894.205097] swapper pgtable: 4k pages, 48-bit VAs, pgdp=bf608000
  [  894.209645] [abd0c7eba050] pgd=0001b6fff003, pud=0001b6ffe003, 
pmd=00019b19d003, pte=00611f517f93
  [  894.217586] Internal error: Oops: 964f [#1] SMP
  [  894.220753] Modules linked in: userio(+) aes_arm64 algif_rng aegis128 
algif_aead anubis fcrypt khazad seed sm4_generic tea crc32_generic md4 
michael_mic nhpoly1305_neon nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 
rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic 
algif_hash blowfish_generic blowfish_common cast5_generic des_generic libdes 
salsa20_generic chacha_neon chacha_generic unix_diag camellia_generic 
cast6_generic cast_common sctp serpent_generic twofish_generic twofish_common 
algif_skcipher atm af_alg dccp_ipv4 dccp xfs binfmt_misc zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zlua(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) dm_multipath 
scsi_dh_rdac scsi_dh_emc spl(O) scsi_dh_alua qemu_fw_cfg nfsd auth_rpcgss 
sch_fq_codel nfs_acl lockd grace drm sunrpc virtio_rng ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear crct10dif_ce
  [  894.227087]  ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_net virtio_blk 
net_failover virtio_scsi failover aes_neon_bs aes_neon_blk aes_ce_blk 
crypto_simd cryptd aes_ce_cipher
  [  894.287863] CPU: 5 PID: 24647 Comm: modprobe Tainted: P   O  
5.4.0-26-generic #30
  [  894.292103] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015
  [  894.295900] pstate: 6045 (nZCv daif +PAN -UAO)
  [  894.298999] pc : jump_label_swap+0x2c/0x80
  [  894.301451] lr : jump_label_swap+0x1c/0x80
  [  894.304012] sp : 8000168cba30
  [  894.305734] x29: 8000168cba30 x28: abd0c7eba0b0
  [  894.308535] x27: abd0c7eba050 x26: 0010
  [  894.311432] x25: 0010 x24: abd0da14c3c0
  [  894.315165] x23: 0050 x22: 
  [  894.319411] x21: abd0c7eba000 x20: abd0c7eba050
  [  894.323865] x19: abd0c7eba0b0 x18: 
  [  894.327192] x17: da02346b4a843289 x16: 785f32823a7a414c
  [  894.330232] x15: 2ed60f0f x14: 0004
  [  894.333187] x13: abd0d8a918f0 x12: 0030
  [  894.336289] x11: cc4c3420 x10: 00015cc23828
  [  894.339448] x9 :  x8 : abd0dd503000
  [  894.343242] x7 :  x6 : 
  [  894.348272] x5 : 0001 x4 : d82c
  [  894.351581] x3 : d9bc x2 : e410
  [  894.355001] x1 : abd0d9d3e76c x0 : ffa0
  [  894.358183] Call trace:
  [  894.359991]  jump_label_swap+0x2c/0x80
  [  894.362067]  do_swap+0x40/0x170
  [  894.363886]  sort_r+0x200/0x2f0
  [  894.365400]  sort+0x30/0x48
  [  894.367488]  jump_label_add_module+0x7c/0x458
  [  894.371041]  jump_label_module_notify+0xc8/0x190
  [  894.375615]  notifier_call_chain+0xa4/0x108
  [  894.378428]  __blocking_notifier_call_chain+0xa4/0xe0
  [  894.381374]  blocking_notifier_call_chain+0x54/0x70
  [  894.384374]  load_module+0x1674/0x1d50
  [  894.386229]  __do_sys_finit_module+0x184/0x1d8
  [  894.388569]  __arm64_sys_finit_module+0x40/0x58
  [  894.390935]  el0_svc_common.constprop.0+0x150/0x5e8
  [  894.394000]  el0_svc_handler+0xbc/0x260
  [  894.396581]  el0_svc+0x10/0x14
  [  894.398445] Code: b9400262 cb130280 29400e84 4b42 (b9000282)
  [  894.402792] ---[ end trace 05455454484e1508 ]---
  [  897.757436] loop_set_block_size: loop3 () has still dirty pages (nrpages=1)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is

[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code

2020-07-20 Thread Sebastien Bacher

Alex, did you read comment 7? 'low' isn't responding to what the
regression potential should provide, it's there to describe what impact
the change could have to know on what to focus the testing

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

Title:
  [bionic]blutoothd segfault when you cancel the keyboard pairing during
  the dialog for pairing code

Status in OEM Priority Project:
  In Progress
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  In Progress
Status in bluez source package in Eoan:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * only impact Bionic machines because series after Bionic already
  included this patch.

  [Test Case]

   1. pair bluetooth keyboard
   2. see the dialog asking user input the code for pairing.
   3. press "esc" to cancel it.
   4. the bluetooth should still work to pair another bluetooth device.

  [Regression Potential]

   * low, because the same patch from upstream is already there on
  Groovy, Focal and Eoan.

  [Other Info]

   * NO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions

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

[Kernel-packages] [Bug 1865967] Re: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

@Sean, the failure you have seen here in 5.4 I believe it's for btrfs
instead (bug 1866323), not for xfs.

** Tags removed: 5.4 sru-20200629

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

Title:
  xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

Status in ubuntu-kernel-tests:
  Fix Released
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 Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Released

Bug description:
  == SRU Justification ==
  The fill_fs test for XFS in fallocate06 from ubuntu_ltp_syscalls will fail on 
X/B/D/E:
  tst_test.c:1290: INFO: Testing on xfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop1 with xfs opts='' extra opts=''
  tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
  fallocate06.c:117: INFO: Copy-on-write is not supported
  fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no
  fallocate06.c:157: PASS: write() successful
  fallocate06.c:201: PASS: Misaligned allocation works as expected
  fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) successful
  fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) cleared the correct file range
  fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827
  tst_fill_fs.c:59: INFO: write(): ENOSPC (28)
  fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 
8192)
  fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) successful
  fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) cleared the correct file range

  == Fix ==
  * e093c4be (xfs: Fix tail rounding in xfs_alloc_file_space())

  This patch can be cherry-picked in D/E and needs some minor context
  adjustmest on X/B.

  == Test ==
  Test kernels can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1865967-xfs-fallocate06/

  All patched kernels are working as expected, this issue will no longer
  exist on XFS:
  tst_test.c:1290: INFO: Testing on xfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop5 with xfs opts='' extra opts=''
  tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
  fallocate06.c:117: INFO: Copy-on-write is not supported
  fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no
  fallocate06.c:157: PASS: write() successful
  fallocate06.c:201: PASS: Misaligned allocation works as expected
  fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) successful
  fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) cleared the correct file range
  fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827
  tst_fill_fs.c:59: INFO: write(): ENOSPC (28)
  fallocate06.c:157: PASS: write() successful
  fallocate06.c:201: PASS: Misaligned allocation works as expected
  fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) successful
  fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) cleared the correct file range

  == Regression Potential ==
  Low, this ensure

[Kernel-packages] [Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

** Tags added: 5.4 sru-20200629

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

Title:
  btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Test failure in fallocate06 was composed by two issues, one is xfs
  fill_fs test issue addressed in bug 1865967.

  Another is this one, this is the case 2 of btrfs (fill_fs):

  tst_test.c:1290: INFO: Testing on btrfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts=''
  tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
  fallocate06.c:117: INFO: Copy-on-write is supported
  fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no
  fallocate06.c:157: PASS: write() successful
  fallocate06.c:201: PASS: Misaligned allocation works as expected
  fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) successful
  fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) cleared the correct file range
  fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821
  tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962
  tst_fill_fs.c:59: INFO: write(): ENOSPC (28)
  fallocate06.c:157: PASS: write() successful
  fallocate06.c:201: PASS: Misaligned allocation works as expected
  fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (2

  This issue can be found from X to F
  X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/
  B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/
  D - https://pastebin.ubuntu.com/p/cryTnnn5wF/
  E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/
  F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/

  Note that the hint printed in the test:
HINT: You _MAY_ be missing kernel fixes, see:
   
   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e093c4be760e

  It something that will get printed after the test, as it's for XFS so
  it has nothing to do with this issue here.

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

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

[Kernel-packages] [Bug 1882093] Re: CVE-2020-{5963|5967} NVIDIA

2020-07-20 Thread Alberto Milone

The results look good to me. The only case that looks like a failure
doesn't really have the nvidia modules loaded, so it's ok.

** Also affects: nvidia-graphics-drivers-440-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Bionic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** No longer affects: nvidia-graphics-drivers-440-server (Ubuntu Eoan)

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  CVE-2020-{5963|5967} NVIDIA

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-440 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-440-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-440 source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-440-server source package in Focal:
  Fix Committed

Bug description:
  Security update for CVE-2020-5963 CVE-2020-5967

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1882093/+subscriptions

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

[Kernel-packages] [Bug 1888070] Re: latest update freezes system on boot

2020-07-20 Thread Linux User

Neither 111 nor 109 kernel nor any older would work with a full boot
into system.

So I was advised to get rid of the amdgpu drivers and make sure the open
source AMD drivers are installed.

https://amdgpu-install.readthedocs.io/en/latest/install-installing.html
#uninstalling-the-amdgpu-graphics-stack

amdgpu-uninstall

https://linuxconfig.org/how-to-install-the-latest-amd-radeon-drivers-on-
ubuntu-18-04-bionic-beaver-linux

sudo add-apt-repository ppa:oibaf/graphics-drivers

sudo apt-get update

sudo apt update && sudo apt -y upgrade

Additionally I installed
https://wiki.ubuntu.com/Kernel/LTSEnablementStack though I am not sure
if I had to also use that.

Possibly simply uninstalling the amdgpu drivers that are not compatible
with the latest kernel and switching to the open source Mesa release
drivers would also have been an option, though this is speculation.

Regardless with the open source AMD drivers I do not have any AER issues
(could also not get rid of those with pcie="noaer") and can enjoy a full
boot into the system with latest kernel and all updates.

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

Title:
  latest update freezes system on boot

Status in linux-meta package in Ubuntu:
  New

Bug description:
  Getting a lot of pcie errors when trying to do these updates.

  sudo apt update
  Get:1 file:/var/opt/amdgpu-pro-local ./ InRelease
  Ign:1 file:/var/opt/amdgpu-pro-local ./ InRelease
  Get:2 file:/var/opt/amdgpu-pro-local ./ Release [816 B]
  Get:2 file:/var/opt/amdgpu-pro-local ./ Release [816 B]
  Get:3 file:/var/opt/amdgpu-pro-local ./ Release.gpg   
  
  Ign:3 file:/var/opt/amdgpu-pro-local ./ Release.gpg   
  
  Hit:4 http://linux.teamviewer.com/deb stable InRelease
  
  Hit:5 http://ch.archive.ubuntu.com/ubuntu bionic InRelease
  
  Hit:6 http://ppa.launchpad.net/obsproject/obs-studio/ubuntu bionic InRelease  
  
  Hit:7 http://ch.archive.ubuntu.com/ubuntu bionic-updates InRelease
  
  Hit:8 http://dl.google.com/linux/chrome/deb stable InRelease  
  
  Hit:9 http://security.ubuntu.com/ubuntu bionic-security InRelease 
  
  Hit:10 http://ch.archive.ubuntu.com/ubuntu bionic-backports InRelease 
  
  Hit:11 https://download.docker.com/linux/ubuntu bionic InRelease  
  
  Hit:12 https://deb.nodesource.com/node_11.x bionic InRelease  
  
  Hit:13 https://packages.microsoft.com/repos/ms-teams stable InRelease 
  
  Hit:14 https://packages.microsoft.com/repos/vscode stable InRelease   
  
  Hit:15 https://packagecloud.io/slacktechnologies/slack/debian jessie 
InRelease
  Reading package lists... Done 
  Building dependency tree   
  Reading state information... Done
  16 packages can be upgraded. Run 'apt list --upgradable' to see them.

  sudo apt list -u
  Listing... Done
  code/stable 1.47.1-1594686231 amd64 [upgradable from: 1.47.0-1594283939]
  google-chrome-stable/stable 84.0.4147.89-1 amd64 [upgradable from: 
83.0.4103.116-1]
  libegl-mesa0/bionic-updates 20.0.8-0ubuntu1~18.04.1 amd64 [upgradable from: 
19.2.8-0ubuntu0~18.04.3]
  libegl1-mesa/bionic-updates 20.0.8-0ubuntu1~18.04.1 amd64 [upgradable from: 
19.2.8-0ubuntu0~18.04.3]
  libgbm1/bionic-updates 20.0.8-0ubuntu1~18.04.1 amd64 [upgradable from: 
19.2.8-0ubuntu0~18.04.3]
  libgl1-mesa-dri/bionic-updates 20.0.8-0ubuntu1~18.04.1 amd64 [upgradable 
from: 19.2.8-0ubuntu0~18.04.3]
  libgl1-mesa-glx/bionic-updates 20.0.8-0ubuntu1~18.04.1 amd64 [upgradable 
from: 19.2.8-0ubuntu0~18.04.3]
  libglapi-mesa/bionic-updates 20.0.8-0ubuntu1~18.04.1 amd64 [upgradable from: 
19.2.8-0ubuntu0~18.04.3]

  One of these updates leads to this screen with more and more errors
  coming up and the boot process never finishing.

  https://i.stack.imgur.com/jiVhU.jpg

  I also found out that when booting with kernel

  Linux version 4.15.0-109-generic (buildd@lgw01-amd64-010) (gcc version
  7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #110-Ubuntu SMP Tue Jun 23
  02:39:32 UTC 2020

  the problem is gone. But when I use the 111 kernel the pcie errors
  come up again and the system boot hangs on it.

  This is my graphics card, it was suggested that the pcie errors might
  have to do with that, not sure about this.

  sudo lshw -class display
*-display 
 description: VGA compatible controller
 product: UHD Graphics 620
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 07
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm vga_controller bus_master cap_list rom

[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO

2020-07-20 Thread JPT

Probably fucked up installation was the cause of this. sorry for
bothering.

I recently reinstalled Kubuntu because I was frustrated with the stability of
my system. It still hadn't really improved since switch to kernel 5.4
And, magically, all the crashes are gone. So, no idea why but something in my
old system seems to have caused most of the crashes.

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

Title:
KDE GUI freeze on high disk IO

Status in linux package in Ubuntu:
Confirmed

Bug description:
I've got massive problems with GUI on my PC.

The attached logs are from the following setting:
- high disk load (f3write)
- kernel 4.15.0-1050-oem (the only 4x kernel available in eoan)
- no swap available

These are the parameters (disk load, kernel, swap) I am fiddling with
to find out the cause, see below.

In general
- the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo
- more likely to happen with high disk or CPU load, but not necessarily.
- less likely with the 4.x kernel mentioned above.

I just installed the following kernels from kernel-ppa:
5.3.10-050310-generic
5.4.0-050400rc6-generic
5.4.0-997-generic (drm-intel-next)
Now I am waiting for the freeze to occur again.

The problem started about half a year ago.
There have been three changes that happened at the time and could be the cause
- switch to kernel 5.x
- update to Ubuntu 19.4
- swapped motherboard, CPU and RAM.

The hassle started with the following scenario, repeated often:
- high disk load
- PC becomes laggy
- soon dies/freezes

The longer I waited, the deeper the lockdown went. but I don't know the exact
details.
The first cause I found was kswapd running amok and take the system with it.
Workaround: add swap space.

Now the problem shifted: Whenever I got high disk load (eg dd 100 GB
of data) the kernel swaps likle crazy and makes the GUI first lag soon
freeze. but no excessive CPU load any more, as kswapd does not go
crazy.

Again I found a workaround:
the above mentioned 4.x kernel. In this case the GUI lags as expected from a
heavily swapping system. nothing more.
but still sometimes the GUI simply freezes (the error reported at the top)

Another workaround is to completely remove swap. Let's see what
happens, if kswapd goes amok again.

I am not sure as how these problems are related.

I did extensive hardware check like
- memtest86 newest version, no "may be vulnerable to high frequency row
hammering"
- smart

do you suggest any burn in test suites?

thanks

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18
Uname: Linux 4.15.0-1050-oem x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
Date: Sun Nov 10 15:55:14 2019
DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb
http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled
on upgrade to eoan' was disabled (unknown mirror)
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if
00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630
(Desktop 9 Series) [1462:7b16]
InstallationDate: Installed on 2017-12-16 (693 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64
(20171017.1)
MachineType: Micro-Star International Co., Ltd. MS-7B16
ProcEnviron:
LANGUAGE=en_US:en
TERM=linux
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem
root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago)
dmi.bios.date: 08/13/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.80
dmi.board.asset.tag: Default string
dmi.board.name: B360 GAMING PRO CARBON (MS-7B16)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7B16
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.com

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-07-20 Thread Nicolas Rogues

Hello Didi,

The issue we face could be different : on the Lenovo Legion-5 15ARH05
(which is the object of this bug report) there is no working trick to
boot on Windows then Ubuntu : it just never worked under Linux on the
two BIOS tested (factory I think EUCN16WW and June update EUCN19WW), in
UEFI mode, no matters if Windows was used before reboot and grub to
Ubuntu (I have a dual-boot setup).

As a remark, the touchpad does work in the UEFI BIOS, before any OS is
loaded.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion

[Kernel-packages] [Bug 1888223] [NEW] Touchpad not listed in /proc/bus/input/devices

2020-07-20 Thread Jekyll

Public bug reported:

Hello Ubuntu engineer. Thankyou for supporting me in your own time.

Laptop: lenovo Thinkbook 15-IIL
kernal: Linux 5.4.0-40-generic


happy to provide any more info. afraid couldn't find my touchpad manufacturer.


Thank you very much for your help.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jekyllz 859 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 20 13:04:58 2020
InstallationDate: Installed on 2020-07-19 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 20SM
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=6a6a18ad-d6af-4396-9d9e-2bf710f1a388 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-40-generic N/A
 linux-backports-modules-5.4.0-40-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/24/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: DJCN16WW
dmi.board.name: LVAC/LVAD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ThinkBook 15-IIL
dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN16WW:bd03/24/2020:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:
dmi.product.family: Thinkbook 15-IIL
dmi.product.name: 20SM
dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
dmi.product.version: Lenovo ThinkBook 15-IIL
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  Touchpad not listed in /proc/bus/input/devices

Status in linux package in Ubuntu:
  New

Bug description:
  Hello Ubuntu engineer. Thankyou for supporting me in your own time.

  Laptop: lenovo Thinkbook 15-IIL
  kernal: Linux 5.4.0-40-generic

  
  happy to provide any more info. afraid couldn't find my touchpad manufacturer.

  
  Thank you very much for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jekyllz 859 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 13:04:58 2020
  InstallationDate: Installed on 2020-07-19 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20SM
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=6a6a18ad-d6af-4396-9d9e-2bf710f1a388 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN16WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN16WW:bd03/24/2020:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:
  dmi.product.family: Thinkbook 15-IIL
  dmi.product.name: 20SM
  dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
  dmi.product.version: Lenovo ThinkBook 15-IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code

2020-07-20 Thread Alex Tu

** Description changed:

  [Impact]
  
-  * only impact Bionic machines because series after Bionic already
- included this patch.
+ This patch is for this issue:
+ steps: 
+ 1. pair bluetooth keyboard 
+ 2. see the dialog asking user input the code for pairing. 
+ 3. press "esc" to cancel it. 
+ 4. blutoothd segfault shows in dmesg after a while. 
+ 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 
978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 
7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000]
+ 
  
  [Test Case]
  
   1. pair bluetooth keyboard
   2. see the dialog asking user input the code for pairing.
   3. press "esc" to cancel it.
   4. the bluetooth should still work to pair another bluetooth device.
  
  [Regression Potential]
  
-  * low, because the same patch from upstream is already there on Groovy,
- Focal and Eoan.
+  * This patch workaround the case that a queue node was created but not
+ yet assigned function before user input pairing keycode. If the user
+ cancel the paring before inputting pairing keycode then assign the
+ function pointer a dummy 'direct_match'.
+ 
+ * Bluetoothd responses to Bluetooth functions and "queue" is a shared
+ common data structure, so in case of regression happens then blutoothd
+ systemd service would be crashed.
+ 
+  * We can verify this by operating add/remove BT devices to trigger
+ queue operations.
+ 
+  * I verified on target machine BIOS ID:0983 on BT mouse, keyboard,
+ headset on pairing, remove and functionality checking.
  
  [Other Info]
  
   * NO.

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

Title:
  [bionic]blutoothd segfault when you cancel the keyboard pairing during
  the dialog for pairing code

Status in OEM Priority Project:
  In Progress
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  In Progress
Status in bluez source package in Eoan:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This patch is for this issue:
  steps: 
  1. pair bluetooth keyboard 
  2. see the dialog asking user input the code for pairing. 
  3. press "esc" to cancel it. 
  4. blutoothd segfault shows in dmesg after a while. 
  5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 
978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 
7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000]

  
  [Test Case]

   1. pair bluetooth keyboard
   2. see the dialog asking user input the code for pairing.
   3. press "esc" to cancel it.
   4. the bluetooth should still work to pair another bluetooth device.

  [Regression Potential]

   * This patch workaround the case that a queue node was created but
  not yet assigned function before user input pairing keycode. If the
  user cancel the paring before inputting pairing keycode then assign
  the function pointer a dummy 'direct_match'.

  * Bluetoothd responses to Bluetooth functions and "queue" is a shared
  common data structure, so in case of regression happens then blutoothd
  systemd service would be crashed.

   * We can verify this by operating add/remove BT devices to trigger
  queue operations.

   * I verified on target machine BIOS ID:0983 on BT mouse, keyboard,
  headset on pairing, remove and functionality checking.

  [Other Info]

   * NO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions

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

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

This change was made by a bot.

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

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

Title:
  Touchpad not listed in /proc/bus/input/devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello Ubuntu engineer. Thankyou for supporting me in your own time.

  Laptop: lenovo Thinkbook 15-IIL
  kernal: Linux 5.4.0-40-generic

  
  happy to provide any more info. afraid couldn't find my touchpad manufacturer.

  
  Thank you very much for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jekyllz 859 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 13:04:58 2020
  InstallationDate: Installed on 2020-07-19 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20SM
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=6a6a18ad-d6af-4396-9d9e-2bf710f1a388 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN16WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN16WW:bd03/24/2020:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:
  dmi.product.family: Thinkbook 15-IIL
  dmi.product.name: 20SM
  dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
  dmi.product.version: Lenovo ThinkBook 15-IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code

2020-07-20 Thread Alex Tu

sorry for bad habit that I miss-understanded before.
I revised it and put detail information there.

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

Title:
  [bionic]blutoothd segfault when you cancel the keyboard pairing during
  the dialog for pairing code

Status in OEM Priority Project:
  In Progress
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  In Progress
Status in bluez source package in Eoan:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This patch is for this issue:
  steps: 
  1. pair bluetooth keyboard 
  2. see the dialog asking user input the code for pairing. 
  3. press "esc" to cancel it. 
  4. blutoothd segfault shows in dmesg after a while. 
  5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 
978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 
7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000]

  
  [Test Case]

   1. pair bluetooth keyboard
   2. see the dialog asking user input the code for pairing.
   3. press "esc" to cancel it.
   4. the bluetooth should still work to pair another bluetooth device.

  [Regression Potential]

   * This patch workaround the case that a queue node was created but
  not yet assigned function before user input pairing keycode. If the
  user cancel the paring before inputting pairing keycode then assign
  the function pointer a dummy 'direct_match'.

  * Bluetoothd responses to Bluetooth functions and "queue" is a shared
  common data structure, so in case of regression happens then blutoothd
  systemd service would be crashed.

   * We can verify this by operating add/remove BT devices to trigger
  queue operations.

   * I verified on target machine BIOS ID:0983 on BT mouse, keyboard,
  headset on pairing, remove and functionality checking.

  [Other Info]

   * NO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions

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

[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working

2020-07-20 Thread David Rosenstrauch

Why the status update to invalid?  Several people have confirmed this
issue.

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

Title:
  HP 1030 G3 fn-keys not working

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn 
key combinations are only working partially. 
  What works: Volume up/down/mute, Airplane mode
  What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator 
lights

  I already tried solutions regarding editing the Kernel Parameter
  acpi_osi in the grub config but can not get the keys to work. In case
  of screen brightness changing it using the desktop slider works.

  But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
  Running showkey -k results in a keycode 465 pressed and released event for 
all three key combinations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.10
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Apr  1 14:22:47 2019
  InstallationDate: Installed on 2019-03-30 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.06.00
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.38.00
  dmi.chassis.asset.tag: 5CD8427YK5
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 4QZ13ES#ABD
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1888231] [NEW] [UBUNTU 20.04] zipl: Fix KVM IPL without bootindex

You have been subscribed to a public bug:

Description:   zipl: Fix KVM IPL without bootindex
Symptom:   Failed IPL on KVM when no bootindex is specified.
Problem:   Without bootindex specified there is no IPL parmblock
   on KVM which can be read by the stage3 loader.
Solution:  In case diag308 gives a response code 0x102 the stage3
   loader can safely assume that no secure IPL is required
   since no IPL report block exists.
Reproduction:  IPL on KVM without 'bootindex=' attached.
Upstream-ID:   c9066bf5497300db5e0ba11bf111683ea225d8c8
   b7f1977d3f9332f82e7f388fb18076b89b83944e

Component: s390-tools 2.14

Should also be integrated into 20.04, where secure boot is enabled.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-186967 severity-high 
targetmilestone-inin2010
-- 
[UBUNTU 20.04] zipl: Fix KVM IPL without bootindex
https://bugs.launchpad.net/bugs/1888231
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1879401] Re: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound rarely works

2020-07-20 Thread Nathan Bryant

Last night I built a kernel from drm-tip. CONFIG_BPFILTER is disabled
because of regressions, otherwise config is the same as used in
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

I was eventually able to reproduce the problem but it seemed like I need
to reboot in order to do so. The first boot worked OK across many
attempts. Attaching success and failed dmesg.

** Attachment added: "success-dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879401/+attachment/5394329/+files/success-dmesg.txt

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

Title:
  [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound
  rarely works

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ice Lake laptop (Dell 7390 2-in-one) which I am connecting
  to a TV over HDMI via a Novoo USB-C multiport adapter. This is not a
  Thunderbolt device, it is just USB-C.

  It seemed like things used to work fine before I upgraded this system
  from Ubuntu 19.10 to 20.04, although I couldn't say for certain at
  this point. But I'm having a ton of difficulty getting audio output
  over HDMI. Getting it to work requires a lot of retries to
  reinitialize the device (either by suspending/resuming the laptop, or
  plugging/unplugging the HDMI cable and/or the multiport adapter). It
  does work sometimes, but my success rate is very low at this point.

  Even when it does work, it's brittle: any change to the output port
  (to speaker and back to HDMI, or from stereo to surround and back)
  will often break the audio. This fact seems to suggest that the
  problem doesn't have anything to do with the low-level initialization
  of the HDMI port; I'd be looking at some mid-layer code.

  To be clear, there doesn't seem to be any particular symptom, or
  anything of interest in the logs, other than an absence of sound
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Uname: Linux 5.6.0-1010-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nbryant1510 F pulseaudio
   /dev/snd/pcmC0D9p:   nbryant1510 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 17:32:11 2020
  InstallationDate: Installed on 2020-01-31 (108 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulseAudioLog:
   May 18 16:36:42 atlantis dbus-daemon[633]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.41' (uid=124 pid=1116 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   May 18 16:36:53 atlantis systemd[1109]: pulseaudio.service: Succeeded.
   May 18 16:37:03 atlantis systemd[1109]: pulseaudio.socket: Succeeded.
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] fails 
after a while
  UpgradeStatus: Upgraded to focal on 2020-04-21 (27 days ago)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.1
  dmi.board.name: 06CDVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd03/02/2020:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nbryant1510 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-31 (108 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 003: ID 8087:0026 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  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 i

[Kernel-packages] [Bug 1879401] Re: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound rarely works

2020-07-20 Thread Nathan Bryant

Now attaching failed dmesg.

** Attachment added: "failed-sound-dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879401/+attachment/5394330/+files/failed-sound-dmesg.txt

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

Title:
  [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound
  rarely works

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ice Lake laptop (Dell 7390 2-in-one) which I am connecting
  to a TV over HDMI via a Novoo USB-C multiport adapter. This is not a
  Thunderbolt device, it is just USB-C.

  It seemed like things used to work fine before I upgraded this system
  from Ubuntu 19.10 to 20.04, although I couldn't say for certain at
  this point. But I'm having a ton of difficulty getting audio output
  over HDMI. Getting it to work requires a lot of retries to
  reinitialize the device (either by suspending/resuming the laptop, or
  plugging/unplugging the HDMI cable and/or the multiport adapter). It
  does work sometimes, but my success rate is very low at this point.

  Even when it does work, it's brittle: any change to the output port
  (to speaker and back to HDMI, or from stereo to surround and back)
  will often break the audio. This fact seems to suggest that the
  problem doesn't have anything to do with the low-level initialization
  of the HDMI port; I'd be looking at some mid-layer code.

  To be clear, there doesn't seem to be any particular symptom, or
  anything of interest in the logs, other than an absence of sound
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Uname: Linux 5.6.0-1010-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nbryant1510 F pulseaudio
   /dev/snd/pcmC0D9p:   nbryant1510 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 17:32:11 2020
  InstallationDate: Installed on 2020-01-31 (108 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulseAudioLog:
   May 18 16:36:42 atlantis dbus-daemon[633]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.41' (uid=124 pid=1116 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   May 18 16:36:53 atlantis systemd[1109]: pulseaudio.service: Succeeded.
   May 18 16:37:03 atlantis systemd[1109]: pulseaudio.socket: Succeeded.
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] fails 
after a while
  UpgradeStatus: Upgraded to focal on 2020-04-21 (27 days ago)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.1
  dmi.board.name: 06CDVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd03/02/2020:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nbryant1510 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-31 (108 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 003: ID 8087:0026 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  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=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=caffa21a-82f2-4555-a416-67926241525a ro cma=64M 
pcie_aspm.policy=powersupersave drm.vblankoffdelay=1 video=1600x1200 
mem_sleep_default=deep
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1010-oem

[Kernel-packages] [Bug 1888231] [NEW] [UBUNTU 20.04] zipl: Fix KVM IPL without bootindex

Public bug reported:

Description:   zipl: Fix KVM IPL without bootindex
Symptom:   Failed IPL on KVM when no bootindex is specified.
Problem:   Without bootindex specified there is no IPL parmblock
   on KVM which can be read by the stage3 loader.
Solution:  In case diag308 gives a response code 0x102 the stage3
   loader can safely assume that no secure IPL is required
   since no IPL report block exists.
Reproduction:  IPL on KVM without 'bootindex=' attached.
Upstream-ID:   c9066bf5497300db5e0ba11bf111683ea225d8c8
   b7f1977d3f9332f82e7f388fb18076b89b83944e

Component: s390-tools 2.14

Should also be integrated into 20.04, where secure boot is enabled.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-186967 severity-high 
targetmilestone-inin2010

** Tags added: architecture-s39064 bugnameltc-186967 severity-high
targetmilestone-inin2010

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  [UBUNTU 20.04] zipl: Fix KVM IPL without bootindex

Status in linux package in Ubuntu:
  New

Bug description:
  Description:   zipl: Fix KVM IPL without bootindex
  Symptom:   Failed IPL on KVM when no bootindex is specified.
  Problem:   Without bootindex specified there is no IPL parmblock
 on KVM which can be read by the stage3 loader.
  Solution:  In case diag308 gives a response code 0x102 the stage3
 loader can safely assume that no secure IPL is required
 since no IPL report block exists.
  Reproduction:  IPL on KVM without 'bootindex=' attached.
  Upstream-ID:   c9066bf5497300db5e0ba11bf111683ea225d8c8
 b7f1977d3f9332f82e7f388fb18076b89b83944e

  Component: s390-tools 2.14

  Should also be integrated into 20.04, where secure boot is enabled.

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

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

[Kernel-packages] [Bug 1888229] [NEW] Touchpad doesn't work

2020-07-20 Thread sara

Public bug reported:

I'm using a computer Lenovo IdeaPad s145 and I've installed Ubuntu 20.04 LTS 
and my touchpad doesn't work at all. xinput gives:
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Logitech Optical USB Mouseid=12   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Power Button  id=8[slave  keyboard (3)]
↳ Integrated Camera: Integrated C   id=9[slave  keyboard (3)]
↳ Ideapad extra buttons id=10   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)]

Moreover, if I execute cat /proc/bus/input/devices it gives me only the
mouse device and not the touchpad. What can I do?

Thank you for your help

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  s  1002 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 20 15:46:40 2020
InstallationDate: Installed on 2020-07-16 (4 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 005: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
 Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera
 Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81W8
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=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=ee02290d-f214-4067-8ce8-c44b9e0ca2a0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-40-generic N/A
 linux-backports-modules-5.4.0-40-generic  N/A
 linux-firmware1.187.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: DKCN24WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S145-15IIL
dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN24WW:bd11/26/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL:
dmi.product.family: IdeaPad S145-15IIL
dmi.product.name: 81W8
dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL
dmi.product.version: Lenovo IdeaPad S145-15IIL
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  Touchpad doesn't work

Status in linux package in Ubuntu:
  New

Bug description:
  I'm using a computer Lenovo IdeaPad s145 and I've installed Ubuntu 20.04 LTS 
and my touchpad doesn't work at all. xinput gives:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech Optical USB Mouse  id=12   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=9[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=11   [slave  
keyboard (3)]

  Moreover, if I execute cat /proc/bus/input/devices it gives me only
  the mouse device and not the touchpad. What can I do?

  Thank you for your help

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersio

[Kernel-packages] [Bug 1888231] Re: [UBUNTU 20.04] zipl: Fix KVM IPL without bootindex

2020-07-20 Thread Heinz-Werner Seeck

** Package changed: linux (Ubuntu) => s390-tools (Ubuntu)

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

Title:
  [UBUNTU 20.04] zipl: Fix KVM IPL without bootindex

Status in s390-tools package in Ubuntu:
  New

Bug description:
  Description:   zipl: Fix KVM IPL without bootindex
  Symptom:   Failed IPL on KVM when no bootindex is specified.
  Problem:   Without bootindex specified there is no IPL parmblock
 on KVM which can be read by the stage3 loader.
  Solution:  In case diag308 gives a response code 0x102 the stage3
 loader can safely assume that no secure IPL is required
 since no IPL report block exists.
  Reproduction:  IPL on KVM without 'bootindex=' attached.
  Upstream-ID:   c9066bf5497300db5e0ba11bf111683ea225d8c8
 b7f1977d3f9332f82e7f388fb18076b89b83944e

  Component: s390-tools 2.14

  Should also be integrated into 20.04, where secure boot is enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1888231/+subscriptions

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

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

This change was made by a bot.

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

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

Title:
  Touchpad doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using a computer Lenovo IdeaPad s145 and I've installed Ubuntu 20.04 LTS 
and my touchpad doesn't work at all. xinput gives:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech Optical USB Mouse  id=12   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=9[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=11   [slave  
keyboard (3)]

  Moreover, if I execute cat /proc/bus/input/devices it gives me only
  the mouse device and not the touchpad. What can I do?

  Thank you for your help

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  s  1002 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 15:46:40 2020
  InstallationDate: Installed on 2020-07-16 (4 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 005: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81W8
  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=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=ee02290d-f214-4067-8ce8-c44b9e0ca2a0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN24WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN24WW:bd11/26/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL:
  dmi.product.family: IdeaPad S145-15IIL
  dmi.product.name: 81W8
  dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL
  dmi.product.version: Lenovo IdeaPad S145-15IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1879707] 0001-s390-dasd-Fix-zero-write-for-EDEVICEs.patch

--- Comment on attachment From jan.hoepp...@de.ibm.com 2020-07-20 11:15 
EDT---


This is a patch that potentially fixes the issue. Can you please apply the 
patch and run your tests with it? Please let me know if this fixes the issues 
for you.

Please note that this patch is for testing _only_ and not a final or
even upstream patch.

** Attachment added: "0001-s390-dasd-Fix-zero-write-for-EDEVICEs.patch"
   
https://bugs.launchpad.net/bugs/1879707/+attachment/5394376/+files/0001-s390-dasd-Fix-zero-write-for-EDEVICEs.patch

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

Title:
  [UBUNTU 20.04] mke2fs dasd(fba),Failing CCW,default ERP has run out of
  retries and failed

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

Bug description:
  mke2fs,dasd(fba) guest edevices FBA,default ERP has run out of retries and 
failed,Failing CCW
   
  ---uname output---
  xx -  5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:27:18 UTC 2020 s390x 
s390x s390x GNU/Linux
   
  Machine Type = IBM 3906 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   mke2fs to dasd(fba) devices
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  dasd(fba),Failing CCW,default ERP has run out of retries and failed between 
the following syslog events,
  mke2fs running, before mounting and starting IO to dasd(fba) devices

  May 14 14:33:32 ilabg13 root: ILAB_IO_FROM_MSDI_START
  May 14 14:48:34 ilabg13 root: ILAB_IO_FROM_MSDI_RUNNING

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

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

[Kernel-packages] [Bug 1888116] [NEW] kernel 5.4.0-42-generic looping amdgpu errors

You have been subscribed to a public bug:

After updating to package "linux-image-5.4.0-42-generic" (5.4.0.42.45)
several hundred system-log similar entires per minute are thrown at log:

kernel  amdgpu :09:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:169 
vmid:0 pasid:0, for process  pid 0 thread  pid 0)
kernel  amdgpu :09:00.0: amdgpu:   in page starting at address 
0xfffba000 from client 18
kernel  amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00041F52
kernel  amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: 0xf
kernel  amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0
kernel  amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x1
kernel  amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x5
kernel  amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x1
kernel  amdgpu :09:00.0: amdgpu: RW: 0x1

System is a 20.04.1 Kubtuntu, with AMD Ryzen 5 and RX 5700 GPU, amdgpu
with opencl installed (via amdgpu-pro-20.20-1089974-ubuntu-20.04.tar.xz
from amd.com)

Nevertheless no system freezes or graphic bugs happened

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


** Tags: bot-comment
-- 
kernel 5.4.0-42-generic looping amdgpu errors
https://bugs.launchpad.net/bugs/1888116
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1888116] Re: kernel 5.4.0-42-generic looping amdgpu errors

2020-07-20 Thread Brian Murray

** Package changed: linux-hwe-5.4 (Ubuntu) => linux (Ubuntu)

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

Title:
  kernel 5.4.0-42-generic looping amdgpu errors

Status in linux package in Ubuntu:
  New

Bug description:
  After updating to package "linux-image-5.4.0-42-generic" (5.4.0.42.45)
  several hundred system-log similar entires per minute are thrown at
  log:

  kernelamdgpu :09:00.0: amdgpu: [mmhub] page fault (src_id:0 
ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
  kernelamdgpu :09:00.0: amdgpu:   in page starting at address 
0xfffba000 from client 18
  kernelamdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00041F52
  kernelamdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: 0xf
  kernelamdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0
  kernelamdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x1
  kernelamdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x5
  kernelamdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x1
  kernelamdgpu :09:00.0: amdgpu: RW: 0x1

  System is a 20.04.1 Kubtuntu, with AMD Ryzen 5 and RX 5700 GPU, amdgpu
  with opencl installed (via amdgpu-
  pro-20.20-1089974-ubuntu-20.04.tar.xz from amd.com)

  Nevertheless no system freezes or graphic bugs happened

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

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

[Kernel-packages] [Bug 1887724] Re: [amdgpu] Xorg freeze

2020-07-20 Thread Blaise Mariner

Funny you say that there has been a problem with the Wifi on this
machine since it was solely running Windows 10. Best Buy could not fix
it and did not want to cheaply replace it. Sometimes (unable to
reproduce) the wifi loses the ability to detect networks and I would
have to reboot in order to reset the wifi connection. No freeze or
anything would occur. I have a USB-antennae that works well and works
around the problem, so most of the time now I am unaware if the internal
wifi connection stops. Thank you for the different kernel version link,
I will explore 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/1887724

Title:
  [amdgpu] Xorg freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random freezing-- different freezing every time. I switched GUIs from
  Gnome to Cinnamon and it seems to freeze less, but still averaging
  about once a day. I cannot reproduce, is random.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Wed Jul 15 15:44:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Dell Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [1028:0884]
  InstallationDate: Installed on 2020-06-04 (40 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 7375
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=0ed970bf-fd17-4242-8a3e-5c1224ed5b72 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 02YPPF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.5.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd07/09/2018:svnDellInc.:pnInspiron7375:pvr1.5.0:rvnDellInc.:rn02YPPF:rvrA00:cvnDellInc.:ct10:cvr1.5.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7375
  dmi.product.sku: 0884
  dmi.product.version: 1.5.0
  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 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/1887724/+subscriptions

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

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

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

apport-collect 1888116

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

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

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

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

** Tags added: focal

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

Title:
  kernel 5.4.0-42-generic looping amdgpu errors

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to package "linux-image-5.4.0-42-generic" (5.4.0.42.45)
  several hundred system-log similar entires per minute are thrown at
  log:

  kernelamdgpu :09:00.0: amdgpu: [mmhub] page fault (src_id:0 
ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
  kernelamdgpu :09:00.0: amdgpu:   in page starting at address 
0xfffba000 from client 18
  kernelamdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00041F52
  kernelamdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: 0xf
  kernelamdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0
  kernelamdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x1
  kernelamdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x5
  kernelamdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x1
  kernelamdgpu :09:00.0: amdgpu: RW: 0x1

  System is a 20.04.1 Kubtuntu, with AMD Ryzen 5 and RX 5700 GPU, amdgpu
  with opencl installed (via amdgpu-
  pro-20.20-1089974-ubuntu-20.04.tar.xz from amd.com)

  Nevertheless no system freezes or graphic bugs happened

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

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

[Kernel-packages] [Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108

This bug was fixed in the package linux - 5.4.0-42.46

---
linux (5.4.0-42.46) focal; urgency=medium

  * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)

  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

linux (5.4.0-41.45) focal; urgency=medium

  * focal/linux: 5.4.0-41.45 -proposed tracker (LP: #1885855)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * CVE-2019-19642
- kernel/relay.c: handle alloc_percpu returning NULL in relay_open

  * CVE-2019-16089
- SAUCE: nbd_genl_status: null check for nla_nest_start

  * CVE-2020-11935
- aufs: do not call i_readcount_inc()

  * ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4
kernel (LP: #1826848)
- selftests: net: ip_defrag: ignore EPERM

  * Update lockdown patches (LP: #1884159)
- SAUCE: acpi: disallow loading configfs acpi tables when locked down

  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc

  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

 -- Khalid Elmously   Thu, 09 Jul 2020
19:50:26 -0400

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-16089

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19642

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-11935

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

Title:
  linux 4.15.0-109-generic network DoS regression vs -108

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  On systems using cgroups and sockets extensively, like docker, kubernetes, 
lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic.

  [Fix]
  Revert the patch that disables sk_alloc cgroup refcounting when tasks are 
added to net_prio cgroup.

  [Test case]
  Test that such environments where the issue is reproduced survive some hours 
of uptime. A different bug was reproduced with a work-in-progress code and was 
not reproduced with the culprit reverted.

  [Regression potential]
  The reverted commit fix a memory leak on similar scenarios. But a leak is 
better than a crash. Two other bugs have been opened to track a real fix for 
this issue and the leak.

  --

  Reported from a user:

  Several of our infrastructure VMs recently started crashing (oops
  attached), after they upgraded to -109.  -108 appears to be stable.

  Analysing the crash, it appears to be a wild pointer access in a BPF
  filter, which makes this (probably) a network-traffic triggered crash.

  [  696.396831] general protection fault:  [#1] SMP PTI
  [  696.396843] Modules linked in: iscsi_target_mod target_core_mod 
ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac 
arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc 
overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid 
sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs 
sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse 
i2c_piix4 pata_acpi floppy
  [  696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic 
#110-Ubuntu
  [  696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018
  [  696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0
  [  696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292
  [  696.397015] RAX: 6d69546e6f697469 RBX:  RCX: 
0014
  [  696.397028] RDX:  RSI: 893fd036 RDI: 
893fb5154800
  [  696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: 

  [  696.397058] R10:  R11: 0003 R12: 
0014
  [  696.397075] R13: 893fb5154800 R14: 0020 R15: 
893fc6ba4d00
  [  696.397091] FS:  () GS:893fdcb8() 
knlGS:
  [  696.397107] CS:  0010 DS:  ES:  CR0: 0

[Kernel-packages] [Bug 1881137] Re: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers

This bug was fixed in the package linux - 5.4.0-42.46

---
linux (5.4.0-42.46) focal; urgency=medium

  * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)

  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

linux (5.4.0-41.45) focal; urgency=medium

  * focal/linux: 5.4.0-41.45 -proposed tracker (LP: #1885855)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * CVE-2019-19642
- kernel/relay.c: handle alloc_percpu returning NULL in relay_open

  * CVE-2019-16089
- SAUCE: nbd_genl_status: null check for nla_nest_start

  * CVE-2020-11935
- aufs: do not call i_readcount_inc()

  * ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4
kernel (LP: #1826848)
- selftests: net: ip_defrag: ignore EPERM

  * Update lockdown patches (LP: #1884159)
- SAUCE: acpi: disallow loading configfs acpi tables when locked down

  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc

  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

 -- Khalid Elmously   Thu, 09 Jul 2020
19:50:26 -0400

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-16089

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19642

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-11935

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

Title:
  Introduce the new NVIDIA 418-server and 440-server series, and update
  the current NVIDIA drivers

Status in linux package in Ubuntu:
  Incomplete
Status in linux-restricted-modules package in Ubuntu:
  New
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-440-server source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-440-server source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  440.82:
    * New upstream release:
  - Added a workaround for Steam Play title DOOM Eternal, which
    overrides application requested memory locations, to ensure
    performance-critical resources be placed in video memory.
  - Allow presenting from queue families which only expose
    VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib
    surfaces.
  - Fixed a bug that caused render-offloaded applications to crash
    on exit.
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'timespec_to_ns'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit

[Kernel-packages] [Bug 1884159] Re: Update lockdown patches

This bug was fixed in the package linux - 5.4.0-42.46

---
linux (5.4.0-42.46) focal; urgency=medium

  * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)

  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

linux (5.4.0-41.45) focal; urgency=medium

  * focal/linux: 5.4.0-41.45 -proposed tracker (LP: #1885855)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * CVE-2019-19642
- kernel/relay.c: handle alloc_percpu returning NULL in relay_open

  * CVE-2019-16089
- SAUCE: nbd_genl_status: null check for nla_nest_start

  * CVE-2020-11935
- aufs: do not call i_readcount_inc()

  * ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4
kernel (LP: #1826848)
- selftests: net: ip_defrag: ignore EPERM

  * Update lockdown patches (LP: #1884159)
- SAUCE: acpi: disallow loading configfs acpi tables when locked down

  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc

  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

 -- Khalid Elmously   Thu, 09 Jul 2020
19:50:26 -0400

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-16089

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19642

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-11935

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

Title:
  Update lockdown patches

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  Impact: The lockdown patches have evolved over time, and part of this
  was restricting more areas of the kernel. Not all of these additions
  were backported, and some can lead to lockdown bypasses, see [1] and
  [2].

  Fix: Backport newer lockdown restrictions to older releases.

  Test Case: Test cases for most of the backports can be found at [3],
  and [4] is another test case. Some which need e.g. specific hardware
  to test have not been tested.

  Regression Potential: Most of these are small, simple fixes with low
  potential for regression. Users may also lose access to some
  functionality previously accissible under secure boot. Some changes
  are more substantial, especially the hw_param and debugfs changes for
  xenial, but they are based on well-tested upstream code. The xmon
  backports also carry a more moderate risk of regression.

  [1] https://lists.ubuntu.com/archives/kernel-team/2020-June/111050.html
  [2] https://lore.kernel.org/lkml/20200615104332.901519-1-ja...@zx2c4.com/
  [3] https://git.launchpad.net/~sforshee/+git/lockdown-tests
  [4] 
https://git.zx2c4.com/american-unsigned-language/tree/american-unsigned-language.sh

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

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

[Kernel-packages] [Bug 1885757] Re: seccomp_bpf fails on powerpc

This bug was fixed in the package linux - 5.4.0-42.46

---
linux (5.4.0-42.46) focal; urgency=medium

  * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)

  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

linux (5.4.0-41.45) focal; urgency=medium

  * focal/linux: 5.4.0-41.45 -proposed tracker (LP: #1885855)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * CVE-2019-19642
- kernel/relay.c: handle alloc_percpu returning NULL in relay_open

  * CVE-2019-16089
- SAUCE: nbd_genl_status: null check for nla_nest_start

  * CVE-2020-11935
- aufs: do not call i_readcount_inc()

  * ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4
kernel (LP: #1826848)
- selftests: net: ip_defrag: ignore EPERM

  * Update lockdown patches (LP: #1884159)
- SAUCE: acpi: disallow loading configfs acpi tables when locked down

  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc

  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

 -- Khalid Elmously   Thu, 09 Jul 2020
19:50:26 -0400

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-16089

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19642

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-11935

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

Title:
  seccomp_bpf fails on powerpc

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  seccomp_bpf test fails on powerpc and ends up being disabled on some series, 
or causing engineers to waste their time verifying the same failures are the 
only ones we see every kernel release.

  [Test case]
  Run the test and notice there are no more failures.

  [Regression potential]
  We may break the test on different architectures. That doesn't break users, 
though, as the changes are only on tests. It has been tested at least on 
ppc64el and amd64.

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

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

[Kernel-packages] [Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel

This bug was fixed in the package linux - 5.4.0-42.46

---
linux (5.4.0-42.46) focal; urgency=medium

  * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)

  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

linux (5.4.0-41.45) focal; urgency=medium

  * focal/linux: 5.4.0-41.45 -proposed tracker (LP: #1885855)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * CVE-2019-19642
- kernel/relay.c: handle alloc_percpu returning NULL in relay_open

  * CVE-2019-16089
- SAUCE: nbd_genl_status: null check for nla_nest_start

  * CVE-2020-11935
- aufs: do not call i_readcount_inc()

  * ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4
kernel (LP: #1826848)
- selftests: net: ip_defrag: ignore EPERM

  * Update lockdown patches (LP: #1884159)
- SAUCE: acpi: disallow loading configfs acpi tables when locked down

  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc

  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

 -- Khalid Elmously   Thu, 09 Jul 2020
19:50:26 -0400

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-16089

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19642

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-11935

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

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3
  / 5.4 kernel

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Failure to run ip_defrag deterministically.

  [Fix]
  Use smaller packets and ignore EPERM.

  [Test case]
  Run the test multiple times without observing failures.

  [Regression potential]
  If the test fix is incorrect, it will cause us to miss real kernel bugs. But 
as it is now, we are already ignoring its results.

  
  ==

  Test failed becuase:
     ./ip_defrag: sendto overlap: 1400: Operation not permitted

   selftests: net: ip_defrag.sh
   
   ipv6 tx:17 gso:1 (fail)
   OK
   ipv4 defrag
   PASS
   seed = 1556203721
   ipv4 defrag with overlaps
   PASS
   seed = 1556203722
   ipv6 defrag
   seed = 1556203756
   PASS
   ipv6 defrag with overlaps
   seed = 1556203756
   ./ip_defrag: sendto overlap: 1400: Operation not permitted
   not ok 1..17 selftests: net: ip_defrag.sh [FAIL]

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

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

[Kernel-packages] [Bug 1881137] Re: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers

This bug was fixed in the package linux-restricted-modules - 5.4.0-42.46

---
linux-restricted-modules (5.4.0-42.46) focal; urgency=medium

  * Master version: 5.4.0-42.46

linux-restricted-modules (5.4.0-41.45) focal; urgency=medium

  * Master version: 5.4.0-41.45

  * Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family

  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] drop nvidia-kernel-common dependency from the ABI metas
- [packaging] add nvidia 418-server and 440-server drivers

  * Miscellaneous Ubuntu changes
- debian/dkms-versions -- update from master

 -- Khalid Elmously   Thu, 09 Jul 2020
20:05:22 -0400

** Changed in: linux-restricted-modules (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Introduce the new NVIDIA 418-server and 440-server series, and update
  the current NVIDIA drivers

Status in linux package in Ubuntu:
  Incomplete
Status in linux-restricted-modules package in Ubuntu:
  New
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-440-server source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-440-server source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  440.82:
    * New upstream release:
  - Added a workaround for Steam Play title DOOM Eternal, which
    overrides application requested memory locations, to ensure
    performance-critical resources be placed in video memory.
  - Allow presenting from queue families which only expose
    VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib
    surfaces.
  - Fixed a bug that caused render-offloaded applications to crash
    on exit.
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'timespec_to_ns'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'getrawmonotonic'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'timespec_to_ns'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'getrawmonotonic'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'getnstimeofday'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with

[Kernel-packages] [Bug 1887011] Re: Xenial update: v4.4.230 upstream stable release

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

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

Title:
  Xenial update: v4.4.230 upstream stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v4.4.230 upstream stable release
     from git://git.kernel.org/

  btrfs: cow_file_range() num_bytes and disk_num_bytes are same
  btrfs: fix data block group relocation failure due to concurrent scrub
  mm: fix swap cache node allocation mask
  EDAC/amd64: Read back the scrub rate PCI register on F15h
  mm/slub: fix stack overruns with SLUB_STATS
  usb: usbtest: fix missing kfree(dev->buf) in usbtest_disconnect
  kgdb: Avoid suspicious RCU usage warning
  crypto: af_alg - fix use-after-free in af_alg_accept() due to bh_lock_sock()
  sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice tuning knob in 
milliseconds
  hwmon: (max6697) Make sure the OVERT mask is set correctly
  hwmon: (acpi_power_meter) Fix potential memory leak in acpi_power_meter_add()
  virtio-blk: free vblk-vqs in error path of virtblk_probe()
  i2c: algo-pca: Add 0x78 as SCL stuck low status for PCA9665
  Revert "ALSA: usb-audio: Improve frames size computation"
  SMB3: Honor 'seal' flag for multiuser mounts
  SMB3: Honor persistent/resilient handle flags for multiuser mounts
  cifs: Fix the target file was deleted when rename failed.
  MIPS: Add missing EHB in mtc0 -> mfc0 sequence for DSPen
  netfilter: nf_conntrack_h323: lost .data_len definition for Q.931/ipv6
  Linux 4.4.230
  UBUNTU: upstream stable to v4.4.230

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

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

[Kernel-packages] [Bug 1885932] Re: Xenial update: v4.4.229 upstream stable release

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

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

Title:
  Xenial update: v4.4.229 upstream stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v4.4.229 upstream stable release
     from git://git.kernel.org/

  s390: fix syscall_get_error for compat processes
  clk: sunxi: Fix incorrect usage of round_down()
  i2c: piix4: Detect secondary SMBus controller on AMD AM4 chipsets
  clk: qcom: msm8916: Fix the address location of pll->config_reg
  ALSA: isa/wavefront: prevent out of bounds write in ioctl
  scsi: qla2xxx: Fix issue with adapter's stopping state
  i2c: pxa: clear all master action bits in i2c_pxa_stop_message()
  usblp: poison URBs upon disconnect
  ps3disk: use the default segment boundary
  vfio/pci: fix memory leaks in alloc_perm_bits()
  mfd: wm8994: Fix driver operation if loaded as modules
  scsi: lpfc: Fix lpfc_nodelist leak when processing unsolicited event
  nfsd: Fix svc_xprt refcnt leak when setup callback client failed
  powerpc/crashkernel: Take "mem=" option into account
  yam: fix possible memory leak in yam_init_driver
  mksysmap: Fix the mismatch of '.L' symbols in System.map
  scsi: sr: Fix sr_probe() missing deallocate of device minor
  scsi: ibmvscsi: Don't send host info in adapter info MAD after LPM
  ALSA: usb-audio: Improve frames size computation
  s390/qdio: put thinint indicator after early error
  tty: hvc: Fix data abort due to race in hvc_open
  staging: sm750fb: add missing case while setting FB_VISUAL
  i2c: pxa: fix i2c_pxa_scream_blue_murder() debug output
  serial: amba-pl011: Make sure we initialize the port.lock spinlock
  drivers: base: Fix NULL pointer exception in __platform_driver_probe() if a 
driver developer is foolish
  PCI/ASPM: Allow ASPM on links to PCIe-to-PCI/PCI-X Bridges
  power: supply: smb347-charger: IRQSTAT_D is volatile
  scsi: mpt3sas: Fix double free warnings
  dlm: remove BUG() before panic()
  clk: ti: composite: fix memory leak
  tty: n_gsm: Fix SOF skipping
  tty: n_gsm: Fix waking up upper tty layer when room available
  powerpc/pseries/ras: Fix FWNMI_VALID off by one
  powerpc/ps3: Fix kexec shutdown hang
  vfio-pci: Mask cap zero
  usb/ohci-platform: Fix a warning when hibernating
  USB: host: ehci-mxc: Add error handling in ehci_mxc_drv_probe()
  tty: n_gsm: Fix bogus i++ in gsm_data_kick
  clk: samsung: exynos5433: Add IGNORE_UNUSED flag to sclk_i2s1
  watchdog: da9062: No need to ping manually before setting timeout
  usb: dwc2: gadget: move gadget resume after the core is in L0 state
  USB: gadget: udc: s3c2410_udc: Remove pointless NULL check in s3c2410_udc_nuke
  usb: gadget: lpc32xx_udc: don't dereference ep pointer before null check
  usb: gadget: fix potential double-free in m66592_probe.
  net: sunrpc: Fix off-by-one issues in 'rpc_ntop6'
  ASoC: fsl_asrc_dma: Fix dma_chan leak when config DMA channel failed
  openrisc: Fix issue with argument clobbering for clone/fork
  gfs2: Allow lock_nolock mount to specify jid=X
  scsi: iscsi: Fix reference count leak in iscsi_boot_create_kobj
  lib/zlib: remove outdated and incorrect pre-increment optimization
  include/linux/bitops.h: avoid clang shift-count-overflow warnings
  elfnote: mark all .note sections SHF_ALLOC
  selftests/net: in timestamping, strncpy needs to preserve null byte
  scsi: acornscsi: Fix an error handling path in acornscsi_probe()
  usb/xhci-plat: Set PM runtime as active on resume
  usb/ehci-platform: Set PM runtime as active on resume
  perf report: Fix NULL pointer dereference in hists__fprintf_nr_sample_events()
  bcache: fix potential deadlock problem in btree_gc_coalesce
  block: Fix use-after-free in blkdev_get()
  libata: Use per port sync for detach
  drm: encoder_slave: fix refcouting error for modules
  drm/dp_mst: Reformat drm_dp_check_act_status() a bit
  drm/qxl: Use correct notify port address when creating cursor ring
  selinux: fix double free
  ext4: fix partial cluster initialization when splitting extent
  drm/dp_mst: Increase ACT retry timeout to 3s
  sparc64: fix misuses of access_process_vm() in genregs32_[sg]et()
  block: nr_sects_write(): Disable preemption on seqcount write
  crypto: algboss - don't wait during notifier callback
  kprobes: Fix to protect kick_kprobe_optimizer() by kprobe

[Kernel-packages] [Bug 1887838] Re: Eoan update: upstream stable patchset 2020-07-16

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

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

Title:
  Eoan update: upstream stable patchset 2020-07-16

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2020-07-16

  Ported from the following upstream stable releases:
  v4.19.132, v.5.4.51

     from git://git.kernel.org/

  btrfs: fix a block group ref counter leak after failure to remove block group
  mm: fix swap cache node allocation mask
  EDAC/amd64: Read back the scrub rate PCI register on F15h
  usbnet: smsc95xx: Fix use-after-free after removal
  mm/slub.c: fix corrupted freechain in deactivate_slab()
  mm/slub: fix stack overruns with SLUB_STATS
  usb: usbtest: fix missing kfree(dev->buf) in usbtest_disconnect
  s390/debug: avoid kernel warning on too large number of pages
  nvme-multipath: set bdi capabilities once
  nvme-multipath: fix deadlock between ana_work and scan_work
  kgdb: Avoid suspicious RCU usage warning
  crypto: af_alg - fix use-after-free in af_alg_accept() due to bh_lock_sock()
  drm/msm/dpu: fix error return code in dpu_encoder_init
  cxgb4: use unaligned conversion for fetching timestamp
  cxgb4: parse TC-U32 key values and masks natively
  cxgb4: use correct type for all-mask IP address comparison
  cxgb4: fix SGE queue dump destination buffer context
  hwmon: (max6697) Make sure the OVERT mask is set correctly
  hwmon: (acpi_power_meter) Fix potential memory leak in acpi_power_meter_add()
  drm: sun4i: hdmi: Remove extra HPD polling
  virtio-blk: free vblk-vqs in error path of virtblk_probe()
  SMB3: Honor 'posix' flag for multiuser mounts
  nvme: fix a crash in nvme_mpath_add_disk
  i2c: algo-pca: Add 0x78 as SCL stuck low status for PCA9665
  i2c: mlxcpld: check correct size of maximum RECV_LEN packet
  nfsd: apply umask on fs without ACL support
  Revert "ALSA: usb-audio: Improve frames size computation"
  SMB3: Honor 'seal' flag for multiuser mounts
  SMB3: Honor persistent/resilient handle flags for multiuser mounts
  SMB3: Honor lease disabling for multiuser mounts
  cifs: Fix the target file was deleted when rename failed.
  MIPS: Add missing EHB in mtc0 -> mfc0 sequence for DSPen
  irqchip/gic: Atomically update affinity
  dm zoned: assign max_io_len correctly
  UBUNTU: [Config] updateconfigs for EFI_CUSTOM_SSDT_OVERLAYS
  efi: Make it possible to disable efivar_ssdt entirely
  sched/debug: Make sd->flags sysctl read-only
  rxrpc: Fix race between incoming ACK parser and retransmitter
  tools lib traceevent: Add append() function helper for appending strings
  tools lib traceevent: Handle __attribute__((user)) in field names
  nvme-multipath: fix deadlock due to head->lock
  nvme-multipath: fix bogus request queue reference put
  selftests: tpm: Use /bin/sh instead of /bin/bash
  tpm: Fix TIS locality timeout problems
  rxrpc: Fix afs large storage transmission performance drop
  RDMA/counter: Query a counter before release
  cxgb4: fix endian conversions for L4 ports in filters
  thermal/drivers/mediatek: Fix bank number settings on mt8183
  thermal/drivers/rcar_gen3: Fix undefined temperature if negative
  nfsd4: fix nfsdfs reference count loop
  nfsd: fix nfsdfs inode reference count leak
  samples/vfs: avoid warning in statx override
  spi: spi-fsl-dspi: Fix external abort on interrupt in resume or exit paths
  SMB3: Honor 'handletimeout' flag for multiuser mounts
  MIPS: lantiq: xway: sysctrl: fix the GPHY clock alias names
  drm/amd/display: Only revalidate bandwidth on medium and fast updates
  drm/amdgpu: use %u rather than %d for sclk/mclk
  drm/amdgpu/atomfirmware: fix vram_info fetching for renoir
  dma-buf: Move dma_buf_release() from fops to dentry_ops
  mm, compaction: fully assume capture is not NULL in compact_zone_order()
  mm, compaction: make capture control handling safe wrt interrupts
  x86/resctrl: Fix memory bandwidth counter width for AMD
  UBUNTU: upstream stable to v4.19.132, v5.4.51

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

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

[Kernel-packages] [Bug 1887573] Re: Eoan update: upstream stable patchset 2020-07-14

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

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

Title:
  Eoan update: upstream stable patchset 2020-07-14

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2020-07-14

  Ported from the following upstream stable releases:
  v4.19.131, v.5.4.50

     from git://git.kernel.org/

  block/bio-integrity: don't free 'buf' if bio_integrity_add_page() failed
  mtd: rawnand: marvell: Fix the condition on a return code
  net: sched: export __netdev_watchdog_up()
  fix a braino in "sparc32: fix register window handling in genregs32_[gs]et()"
  ALSA: hda/realtek - Enable micmute LED on and HP system
  ibmveth: Fix max MTU limit
  mld: fix memory leak in ipv6_mc_destroy_dev()
  net: bridge: enfore alignment for ethernet address
  net: fix memleak in register_netdevice()
  net: increment xmit_recursion level in dev_direct_xmit()
  net: usb: ax88179_178a: fix packet alignment padding
  rocker: fix incorrect error handling in dma_rings_init
  rxrpc: Fix notification call on completion of discarded calls
  sctp: Don't advertise IPv4 addresses if ipv6only is set on the socket
  tcp: don't ignore ECN CWR on pure ACK
  tcp: grow window for OOO packets only for SACK flows
  tg3: driver sleeps indefinitely when EEH errors exceed eeh_max_freezes
  ip6_gre: fix use-after-free in ip6gre_tunnel_lookup()
  net: phy: Check harder for errors in get_phy_id()
  ip_tunnel: fix use-after-free in ip_tunnel_lookup()
  sch_cake: don't try to reallocate or unshare skb unconditionally
  sch_cake: fix a few style nits
  tcp_cubic: fix spurious HYSTART_DELAY exit upon drop in min RTT
  sch_cake: don't call diffserv parsing code when it is not needed
  net: Fix the arp error in some cases
  net: Do not clear the sock TX queue in sk_set_socket()
  net: core: reduce recursion limit value
  USB: ohci-sm501: Add missed iounmap() in remove
  usb: dwc2: Postponed gadget registration to the udc class driver
  usb: add USB_QUIRK_DELAY_INIT for Logitech C922
  USB: ehci: reopen solution for Synopsys HC bug
  usb: host: xhci-mtk: avoid runtime suspend when removing hcd
  xhci: Poll for U0 after disabling USB2 LPM
  usb: host: ehci-exynos: Fix error check in exynos_ehci_probe()
  usb: typec: tcpci_rt1711h: avoid screaming irq causing boot hangs
  ALSA: usb-audio: add quirk for Denon DCD-1500RE
  ALSA: usb-audio: add quirk for Samsung USBC Headset (AKG)
  ALSA: usb-audio: Fix OOB access of mixer element list
  scsi: zfcp: Fix panic on ERP timeout for previously dismissed ERP action
  xhci: Fix incorrect EP_STATE_MASK
  xhci: Fix enumeration issue when setting max packet size for FS devices.
  xhci: Return if xHCI doesn't support LPM
  cdc-acm: Add DISABLE_ECHO quirk for Microchip/SMSC chip
  loop: replace kill_bdev with invalidate_bdev
  IB/mad: Fix use after free when destroying MAD agent
  cifs/smb3: Fix data inconsistent when punch hole
  cifs/smb3: Fix data inconsistent when zero file range
  xfrm: Fix double ESP trailer insertion in IPsec crypto offload.
  ASoC: q6asm: handle EOS correctly
  efi/esrt: Fix reference count leak in esre_create_sysfs_entry.
  regualtor: pfuze100: correct sw1a/sw2 on pfuze3000
  ASoC: fsl_ssi: Fix bclk calculation for mono channel
  ARM: dts: Fix duovero smsc interrupt for suspend
  x86/resctrl: Fix a NULL vs IS_ERR() static checker warning in 
rdt_cdp_peer_get()
  regmap: Fix memory leak from regmap_register_patch
  ARM: dts: NSP: Correct FA2 mailbox node
  rxrpc: Fix handling of rwind from an ACK packet
  RDMA/qedr: Fix KASAN: use-after-free in ucma_event_handler+0x532
  RDMA/cma: Protect bind_list and listen_list while finding matching cm id
  ASoC: rockchip: Fix a reference count leak.
  RDMA/mad: Fix possible memory leak in ib_mad_post_receive_mads()
  net: qed: fix left elements count calculation
  net: qed: fix NVMe login fails over VFs
  net: qed: fix excessive QM ILT lines consumption
  cxgb4: move handling L2T ARP failures to caller
  ARM: imx5: add missing put_device() call in imx_suspend_alloc_ocram()
  usb: gadget: udc: Potential Oops in error handling code
  netfilter: ipset: fix unaligned atomic access
  net: bcmgenet: use hardware padding of runt frames
  i2c: fsi: Fix the port number field in status register
  i2c

[Kernel-packages] [Bug 1887188] Re: Eoan update: upstream stable patchset 2020-07-10

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

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

Title:
  Eoan update: upstream stable patchset 2020-07-10

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2020-07-10

  Ported from the following upstream stable releases:
 v.5.4.49

     from git://git.kernel.org/

  ARM: dts: renesas: Fix IOMMU device node names
  ARM: dts: stm32: Add missing ethernet PHY reset on AV96
  scsi: core: free sgtables in case command setup fails
  arm64: dts: meson: fixup SCP sram nodes
  Input: edt-ft5x06 - fix get_default register write access
  powerpc/kasan: Fix stack overflow by increasing THREAD_SHIFT
  rtc: mc13xxx: fix a double-unlock issue
  remoteproc: qcom_q6v5_mss: map/unmap mpss segments before/after use
  misc: fastrpc: fix potential fastrpc_invoke_ctx leak
  arm64: dts: juno: Fix GIC child nodes
  pinctrl: ocelot: Fix GPIO interrupt decoding on Jaguar2
  clk: renesas: cpg-mssr: Fix STBCR suspend/resume handling
  ASoC: SOF: Do nothing when DSP PM callbacks are not set
  arm64: dts: fvp: Fix GIC child nodes
  arm64: dts: fvp/juno: Fix node address fields
  coresight: tmc: Fix TMC mode read in tmc_read_prepare_etb()
  scsi: hisi_sas: Do not reset phy timer to wait for stray phy up
  PCI: pci-bridge-emul: Fix PCIe bit conflicts
  usb: gadget: core: sync interrupt before unbind the udc
  powerpc/ptdump: Add _PAGE_COHERENT flag
  scsi: cxgb3i: Fix some leaks in init_act_open()
  clk: zynqmp: fix memory leak in zynqmp_register_clocks
  scsi: vhost: Notify TCM about the maximum sg entries supported per command
  IB/mlx5: Fix DEVX support for MLX5_CMD_OP_INIT2INIT_QP command
  RDMA/core: Fix several reference count leaks.
  cifs: set up next DFS target before generic_ip_connect()
  ASoC: qcom: q6asm-dai: kCFI fix
  sparc32: mm: Don't try to free page-table pages if ctor() fails
  net: dsa: lantiq_gswip: fix and improve the unsupported interface error
  f2fs: handle readonly filesystem in f2fs_ioc_shutdown()
  bpf, sockhash: Fix memory leak when unlinking sockets in sock_hash_free
  arm64: dts: qcom: msm8916: remove unit name for thermal trip points
  RDMA/mlx5: Fix udata response upon SRQ creation
  clk: meson: meson8b: Fix the polarity of the RESET_N lines
  clk: meson: meson8b: Fix the vclk_div{1, 2, 4, 6, 12}_en gate bits
  gpio: pca953x: fix handling of automatic address incrementing
  clk: meson: meson8b: Don't rely on u-boot to init all GP_PLL registers
  ASoC: max98373: reorder max98373_reset() in resume
  HID: intel-ish-hid: avoid bogus uninitialized-variable warning
  usb: dwc3: gadget: Properly handle ClearFeature(halt)
  staging: wilc1000: Increase the size of wid_list array
  ALSA: firewire-lib: fix invalid assignment to union data for directional 
parameter
  ASoC: SOF: core: fix error return code in sof_probe_continue()
  arm64: dts: msm8996: Fix CSI IRQ types
  scsi: target: loopback: Fix READ with data and sensebytes
  SoC: rsnd: add interrupt support for SSI BUSIF buffer
  ASoC: ux500: mop500: Fix some refcounted resources issues
  ASoC: ti: omap-mcbsp: Fix an error handling path in 'asoc_mcbsp_probe()'
  USB: ohci-sm501: fix error return code in ohci_hcd_sm501_drv_probe()
  ALSA: usb-audio: Add duplex sound support for USB devices using implicit 
feedback
  habanalabs: increase timeout during reset
  powerpc/64s/exception: Fix machine check no-loss idle wakeup
  drivers: phy: sr-usb: do not use internal fsm for USB2 phy init
  RDMA/hns: Fix cmdq parameter of querying pf timer resource
  firmware: imx: scu: Fix possible memory leak in imx_scu_probe()
  fuse: fix copy_file_range cache issues
  fuse: copy_file_range should truncate cache
  arm64: tegra: Fix flag for 64-bit resources in 'ranges' property
  PCI: amlogic: meson: Don't use FAST_LINK_MODE to set up link
  mfd: stmfx: Reset chip on resume as supply was disabled
  mfd: stmfx: Fix stmfx_irq_init error path
  mfd: stmfx: Disable IRQ in suspend to avoid spurious interrupt
  powerpc/32s: Don't warn when mapping RO data ROX.
  KVM: PPC: Book3S: Fix some RCU-list locks
  input: i8042 - Remove special PowerPC handling
  rtc: rv3028: Add missed check for devm_regmap_init_i2c()
  mailbox: zynqmp-ipi: Fix NULL vs IS_ERR() check in zynqmp_ipi_mbox_pr

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

--- Comment From niklas.schne...@ibm.com 2020-07-20 12:57 EDT---
(In reply to comment #19)
> On Fri, 26 Jun 2020 at 15:01, bugproxy <1877...@bugs.launchpad.net> wrote:
> >
> > (In reply to comment #17)
> > > Eoan and later d-i, new installer, curtin do not install
> > > /etc/kernel-img.conf.
> > > Upgraded systems keep having it (ie. installed with bionic or xenial, and
> > > upgraded).
> > >
> > > Can you please let me know if _removing_ /etc/kernel-img.conf breaks $ 
> > > sudo
> > > make install, and if adding /etc/kernel-img.conf back fixes $ sudo make
> > > install?
> > >
> > > Cause the expectation is that `/etc/kernel-img.conf` should not be there,
> > > yet everything should still work correctly.
> > >
> > > I think somewhere something is reading "link_in_boot=yes" and was not
> > > updated with the new implicit default to always assume that on recent 
> > > ubuntu.
> >
> > For me the installkernel script (including in the current case "sudo
> > make install" from a mainline Linux tree) doesn't update the
> > /boot/initrd.img symlink.
> >
> > Interestingly a package upgrade for linux-generic does overwrite this
> > symlink.
>
> .deb package uses very different maintainer scripts / codepath, and is
> not the same operation as "sudo make install".
>
> I personally always build my kernels as debs, and install debs, rather
> than doing "sudo make install". But I am a distribution developer, and
> I care for .debs to work right. Kernel developers, I guess, are
> inverse, and care for "upstream" $ sudo make install to work.
>
> >
> > Not with the /etc/kernel-img.conf[0] and not without it either.
> > As before the /boot/vmlinuz link is always updated.
> >
>
> That is slightly concerning, as to how $ sudo make install, ever
> worked before. Or what has changed since.
>
> Normally, $ sudo make install, should lookup if /sbin/installkernel is
> available, and call that to "do what it has to do, on a given
> distribution", and that script is shipped by the debianutils package
> which is required and must be installed always. And it hasn't been
> touched in ages.
>
> I wonder which arguments are passed to /sbin/installkernel by $ sudo
> make install. And whether the 4th argument is passed, and if it is
> empty, /, or /boot. It should be either empty, or /boot.
>
> --
> Regards,
>
> Dimitri.
So when I built on a beefy development server I usually copy a tar of the 
modules + bzImage + System.map and e.g.:

# sudo tar -xavf 5.8.0-rc6-06703-g93c67d794cfc.tar -C /usr/
# sudo installkernel 5.8.0-rc6-06703-g93c67d794cfc bzImage System.map /boot

that works well on RHEL, Fedora, SUSE and I'm pretty sure it worked on Ubuntu 
only a week prior to me opening this Bugzilla. I also looked in the history
and didn't find anything so yeah I'm pretty confused how that
used to work on Ubuntu but I've even bisected like that (on Ubuntu) so have 
used that approach dozens of times.

Of course for us working with multiple distros there's a lot of value in
this working the same on all of them and I think that's the main point
of the installkernel script.

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

Title:
  [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img
  which is required with the default zipl.conf

Status in Ubuntu on IBM z Systems:
  Triaged
Status in debianutils package in Ubuntu:
  New
Status in linux-base package in Ubuntu:
  New

Bug description:
  When testing development kernels I usually rely on the installkernel
  script either through the "make install" target of the Kernel source
  or manually. This used to work great on Ubuntu on Z.

  On Ubuntu 20.04 (freshly installed up to date) this fails however because
  /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the
  wrong kernel/initrd combination rendering the system unbootable.

  (with the correct modules already copied to 
/usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/)
  # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (3844).
  Done.
  run-parts: executing /etc/kernel/postinst.d/zz-zipl 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL secti

[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()

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

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

Title:
  use-after-free in af_alg_accept() due to bh_lock_sock()

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

   * Users of the Linux kernel's crypto userspace API
     reported BUG() / kernel NULL pointer dereference
     errors after kernel upgrades.

   * The stack trace signature is an accept() syscall
     going through af_alg_accept() and hitting errors
     usually in one of:
     - apparmor_sk_clone_security()
     - apparmor_sock_graft()
     - release_sock()

  [Fix]

   * This is a regression introduced by upstream commit
     37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
     in sk_destruct") which made its way through stable.

   * The offending patch allows the critical regions
     of af_alg_accept() and af_alg_release_parent() to
     run concurrently; now with the "right" events on 2
     CPUs it might drop the non-atomic reference counter
     of the alg_sock then the sock, thus release a sock
     that is still in use.

   * The fix is upstream commit 34c86f4c4a7b ("crypto:
     af_alg - fix use-after-free in af_alg_accept() due
     to bh_lock_sock()") [1]. It changes alg_sock's ref
     counter to atomic, which addresses the root cause.

  [Test Case]

   * There is a synthetic test case available, which
     uses a kprobes kernel module to synchronize the
     concurrent CPUs on the instructions responsible
     for the problem; and a userspace part to run it.

   * The organic reproducer is the Varnish Cache Plus
     software with the Crypto vmod (which uses kernel
     crypto userspace API) under long, very high load.

   * The patch has been verified on both reproducers
     with the 4.15 and 5.7 kernels.

   * More tests performed with 'stress-ng --af-alg'
     with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
     (all on same version of stress-ng, V0.11.14)

     No regressions observed from original kernel.
     (the af-alg stressor can exercise almost all
     kernel crypto modules shipped with the kernel;
     so it checks more paths/crypto alg interfaces.)

  [Regression Potential]

   * The fix patch does a fundamental change in how
     alg_sock reference counters work, plus another
     change to the 'nokey' counting. This of course
     *has* a risk of regression.

   * Regressions theoretically could manifest as use
     after free errors (in case of undercounting) in
     the af_alg functions or silent memory leaks (in
     case of overcounting), but also other behaviors
     since reference counting is key to many things.

   * FWIW, this patch has been written by the crypto
     subsystem maintainer, who certainly knows a lot
     of the normal and corner cases, thus giving the
     patch more credit.

   * Testing with the organic reproducer ran as long
     as 5 days, without issues, so it does look good.

  [Other Info]

   * Not sending for Groovy (should get via Unstable).

   * [1] Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d

  [Stack Trace Examples]

  Examples:

  BUG: unable to handle kernel NULL pointer dereference at 
  ...
  RIP: 0010:apparmor_sk_clone_security+0x26/0x70
  ...
  Call Trace:
   security_sk_clone+0x33/0x50
   af_alg_accept+0x81/0x1c0 [af_alg]
   alg_accept+0x15/0x20 [af_alg]
   SYSC_accept4+0xff/0x210
   SyS_accept+0x10/0x20
   do_syscall_64+0x73/0x130
   entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  general protection fault:  [#1] SMP PTI
  ...
  RIP: 0010:__release_sock+0x54/0xe0
  ...
  Call Trace:
   release_sock+0x30/0xa0
   af_alg_accept+0x122/0x1c0 [af_alg]
   alg_accept+0x15/0x20 [af_alg]
   SYSC_accept4+0xff/0x210
   SyS_accept+0x10/0x20
   do_syscall_64+0x73/0x130
   entry_SYSCALL_64_after_hwframe+0x3d/0xa2

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

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

[Kernel-packages] [Bug 1886105] Re: Disco update: upstream stable patchset 2020-07-02

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

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

Title:
  Disco update: upstream stable patchset 2020-07-02

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2020-07-02

  Ported from the following upstream stable releases:
  v4.19.130, v.5.4.48

     from git://git.kernel.org/

  power: supply: bq24257_charger: Replace depends on REGMAP_I2C with select
  clk: sunxi: Fix incorrect usage of round_down()
  ASoC: tegra: tegra_wm8903: Support nvidia, headset property
  i2c: piix4: Detect secondary SMBus controller on AMD AM4 chipsets
  iio: pressure: bmp280: Tolerate IRQ before registering
  remoteproc: Fix IDR initialisation in rproc_alloc()
  clk: qcom: msm8916: Fix the address location of pll->config_reg
  backlight: lp855x: Ensure regulators are disabled on probe failure
  ASoC: davinci-mcasp: Fix dma_chan refcnt leak when getting dma type
  ARM: integrator: Add some Kconfig selections
  scsi: qedi: Check for buffer overflow in qedi_set_path()
  ALSA: hda/realtek - Introduce polarity for micmute LED GPIO
  ALSA: isa/wavefront: prevent out of bounds write in ioctl
  PCI: Allow pci_resize_resource() for devices on root bus
  scsi: qla2xxx: Fix issue with adapter's stopping state
  iio: bmp280: fix compensation of humidity
  f2fs: report delalloc reserve as non-free in statfs for project quota
  i2c: pxa: clear all master action bits in i2c_pxa_stop_message()
  clk: samsung: Mark top ISP and CAM clocks on Exynos542x as critical
  usblp: poison URBs upon disconnect
  serial: 8250: Fix max baud limit in generic 8250 port
  dm mpath: switch paths in dm_blk_ioctl() code path
  PCI: aardvark: Don't blindly enable ASPM L0s and don't write to read-only 
register
  ps3disk: use the default segment boundary
  vfio/pci: fix memory leaks in alloc_perm_bits()
  RDMA/mlx5: Add init2init as a modify command
  m68k/PCI: Fix a memory leak in an error handling path
  gpio: dwapb: Call acpi_gpiochip_free_interrupts() on GPIO chip de-registration
  mfd: wm8994: Fix driver operation if loaded as modules
  scsi: lpfc: Fix lpfc_nodelist leak when processing unsolicited event
  clk: clk-flexgen: fix clock-critical handling
  powerpc/perf/hv-24x7: Fix inconsistent output values incase multiple hv-24x7 
events run
  nfsd: Fix svc_xprt refcnt leak when setup callback client failed
  PCI: vmd: Filter resource type bits from shadow register
  powerpc/crashkernel: Take "mem=" option into account
  pwm: img: Call pm_runtime_put() in pm_runtime_get_sync() failed case
  yam: fix possible memory leak in yam_init_driver
  NTB: ntb_pingpong: Choose doorbells based on port number
  NTB: Fix the default port and peer numbers for legacy drivers
  mksysmap: Fix the mismatch of '.L' symbols in System.map
  apparmor: fix introspection of of task mode for unconfined tasks
  ASoC: meson: add missing free_irq() in error path
  scsi: sr: Fix sr_probe() missing deallocate of device minor
  scsi: ibmvscsi: Don't send host info in adapter info MAD after LPM
  x86/purgatory: Disable various profiling and sanitizing options
  staging: greybus: fix a missing-check bug in gb_lights_light_config()
  arm64: dts: mt8173: fix unit name warnings
  scsi: qedi: Do not flush offload work if ARP not resolved
  ARM: dts: sun8i-h2-plus-bananapi-m2-zero: Fix led polarity
  gpio: dwapb: Append MODULE_ALIAS for platform driver
  scsi: qedf: Fix crash when MFW calls for protocol stats while function is 
still probing
  pinctrl: rza1: Fix wrong array assignment of rza1l_swio_entries
  firmware: qcom_scm: fix bogous abuse of dma-direct internals
  staging: gasket: Fix mapping refcnt leak when put attribute fails
  staging: gasket: Fix mapping refcnt leak when register/store fails
  ALSA: usb-audio: Improve frames size computation
  ALSA: usb-audio: Fix racy list management in output queue
  s390/qdio: put thinint indicator after early error
  slimbus: ngd: get drvdata from correct device
  thermal/drivers/ti-soc-thermal: Avoid dereferencing ERR_PTR
  usb: dwc3: gadget: Properly handle failed kick_transfer
  staging: sm750fb: add missing case while setting FB_VISUAL
  PCI: v3-semi: Fix a memory leak in v3_pci_probe() error handling paths
  i2c: pxa: fix i2c_pxa_scream_blue_murder() debug output
  serial: amba-pl011: Make sure we initialize

[Kernel-packages] [Bug 1886876] Re: Disco update: upstream stable patchset 2020-07-08

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

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

Title:
  Disco update: upstream stable patchset 2020-07-08

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2020-07-08

  Ported from the following upstream stable releases:
 v.5.4.49

     from git://git.kernel.org/

  ARM: dts: renesas: Fix IOMMU device node names
  scsi: core: free sgtables in case command setup fails
  arm64: dts: meson: fixup SCP sram nodes
  powerpc/kasan: Fix stack overflow by increasing THREAD_SHIFT
  pinctrl: ocelot: Fix GPIO interrupt decoding on Jaguar2
  clk: renesas: cpg-mssr: Fix STBCR suspend/resume handling
  coresight: tmc: Fix TMC mode read in tmc_read_prepare_etb()
  scsi: hisi_sas: Do not reset phy timer to wait for stray phy up
  PCI: pci-bridge-emul: Fix PCIe bit conflicts
  usb: gadget: core: sync interrupt before unbind the udc
  clk: zynqmp: fix memory leak in zynqmp_register_clocks
  scsi: vhost: Notify TCM about the maximum sg entries supported per command
  IB/mlx5: Fix DEVX support for MLX5_CMD_OP_INIT2INIT_QP command
  cifs: set up next DFS target before generic_ip_connect()
  ASoC: qcom: q6asm-dai: kCFI fix
  sparc32: mm: Don't try to free page-table pages if ctor() fails
  net: dsa: lantiq_gswip: fix and improve the unsupported interface error
  bpf, sockhash: Fix memory leak when unlinking sockets in sock_hash_free
  RDMA/mlx5: Fix udata response upon SRQ creation
  clk: meson: meson8b: Fix the polarity of the RESET_N lines
  clk: meson: meson8b: Fix the vclk_div{1, 2, 4, 6, 12}_en gate bits
  gpio: pca953x: fix handling of automatic address incrementing
  ASoC: max98373: reorder max98373_reset() in resume
  soundwire: slave: don't init debugfs on device registration error
  arm64: dts: msm8996: Fix CSI IRQ types
  scsi: target: loopback: Fix READ with data and sensebytes
  SoC: rsnd: add interrupt support for SSI BUSIF buffer
  ASoC: ux500: mop500: Fix some refcounted resources issues
  ASoC: ti: omap-mcbsp: Fix an error handling path in 'asoc_mcbsp_probe()'
  ALSA: usb-audio: Add duplex sound support for USB devices using implicit 
feedback
  RDMA/hns: Fix cmdq parameter of querying pf timer resource
  firmware: imx: scu: Fix possible memory leak in imx_scu_probe()
  PCI: amlogic: meson: Don't use FAST_LINK_MODE to set up link
  KVM: PPC: Book3S: Fix some RCU-list locks
  input: i8042 - Remove special PowerPC handling
  drm/nouveau/disp/gm200-: fix NV_PDISP_SOR_HDMI2_CTRL(n) selection
  net: marvell: Fix OF_MDIO config check
  bpf/sockmap: Fix kernel panic at __tcp_bpf_recvmsg
  bpf, sockhash: Synchronize delete from bucket list on map free
  nfs: set invalid blocks after NFSv4 writes
  powerpc: Fix kernel crash in show_instructions() w/DEBUG_VIRTUAL
  bnxt_en: Return from timer if interface is not in open state.
  scsi: ufs-bsg: Fix runtime PM imbalance on error
  jbd2: clean __jbd2_journal_abort_hard() and __journal_abort_soft()
  drm/amd/display: Use swap() where appropriate
  drm/msm: Check for powered down HW in the devfreq callbacks
  drm/connector: notify userspace on hotplug after register complete
  UBUNTU: upstream stable to v5.4.49

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

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

[Kernel-packages] [Bug 1886568] Re: Eoan update: upstream stable patchset 2020-07-06

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

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

Title:
  Eoan update: upstream stable patchset 2020-07-06

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2020-07-06

  Ported from the following upstream stable releases:
  v4.19.130, v.5.4.48

     from git://git.kernel.org/

  power: supply: bq24257_charger: Replace depends on REGMAP_I2C with select
  clk: sunxi: Fix incorrect usage of round_down()
  ASoC: tegra: tegra_wm8903: Support nvidia, headset property
  i2c: piix4: Detect secondary SMBus controller on AMD AM4 chipsets
  iio: pressure: bmp280: Tolerate IRQ before registering
  remoteproc: Fix IDR initialisation in rproc_alloc()
  clk: qcom: msm8916: Fix the address location of pll->config_reg
  backlight: lp855x: Ensure regulators are disabled on probe failure
  ASoC: davinci-mcasp: Fix dma_chan refcnt leak when getting dma type
  ARM: integrator: Add some Kconfig selections
  scsi: qedi: Check for buffer overflow in qedi_set_path()
  ALSA: hda/realtek - Introduce polarity for micmute LED GPIO
  ALSA: isa/wavefront: prevent out of bounds write in ioctl
  PCI: Allow pci_resize_resource() for devices on root bus
  scsi: qla2xxx: Fix issue with adapter's stopping state
  iio: bmp280: fix compensation of humidity
  f2fs: report delalloc reserve as non-free in statfs for project quota
  i2c: pxa: clear all master action bits in i2c_pxa_stop_message()
  clk: samsung: Mark top ISP and CAM clocks on Exynos542x as critical
  usblp: poison URBs upon disconnect
  serial: 8250: Fix max baud limit in generic 8250 port
  dm mpath: switch paths in dm_blk_ioctl() code path
  PCI: aardvark: Don't blindly enable ASPM L0s and don't write to read-only 
register
  ps3disk: use the default segment boundary
  vfio/pci: fix memory leaks in alloc_perm_bits()
  RDMA/mlx5: Add init2init as a modify command
  m68k/PCI: Fix a memory leak in an error handling path
  gpio: dwapb: Call acpi_gpiochip_free_interrupts() on GPIO chip de-registration
  mfd: wm8994: Fix driver operation if loaded as modules
  scsi: lpfc: Fix lpfc_nodelist leak when processing unsolicited event
  clk: clk-flexgen: fix clock-critical handling
  powerpc/perf/hv-24x7: Fix inconsistent output values incase multiple hv-24x7 
events run
  nfsd: Fix svc_xprt refcnt leak when setup callback client failed
  PCI: vmd: Filter resource type bits from shadow register
  powerpc/crashkernel: Take "mem=" option into account
  pwm: img: Call pm_runtime_put() in pm_runtime_get_sync() failed case
  yam: fix possible memory leak in yam_init_driver
  NTB: ntb_pingpong: Choose doorbells based on port number
  NTB: Fix the default port and peer numbers for legacy drivers
  mksysmap: Fix the mismatch of '.L' symbols in System.map
  apparmor: fix introspection of of task mode for unconfined tasks
  ASoC: meson: add missing free_irq() in error path
  scsi: sr: Fix sr_probe() missing deallocate of device minor
  scsi: ibmvscsi: Don't send host info in adapter info MAD after LPM
  x86/purgatory: Disable various profiling and sanitizing options
  staging: greybus: fix a missing-check bug in gb_lights_light_config()
  arm64: dts: mt8173: fix unit name warnings
  scsi: qedi: Do not flush offload work if ARP not resolved
  ARM: dts: sun8i-h2-plus-bananapi-m2-zero: Fix led polarity
  gpio: dwapb: Append MODULE_ALIAS for platform driver
  scsi: qedf: Fix crash when MFW calls for protocol stats while function is 
still probing
  pinctrl: rza1: Fix wrong array assignment of rza1l_swio_entries
  firmware: qcom_scm: fix bogous abuse of dma-direct internals
  staging: gasket: Fix mapping refcnt leak when put attribute fails
  staging: gasket: Fix mapping refcnt leak when register/store fails
  ALSA: usb-audio: Improve frames size computation
  ALSA: usb-audio: Fix racy list management in output queue
  s390/qdio: put thinint indicator after early error
  slimbus: ngd: get drvdata from correct device
  thermal/drivers/ti-soc-thermal: Avoid dereferencing ERR_PTR
  usb: dwc3: gadget: Properly handle failed kick_transfer
  staging: sm750fb: add missing case while setting FB_VISUAL
  PCI: v3-semi: Fix a memory leak in v3_pci_probe() error handling paths
  i2c: pxa: fix i2c_pxa_scream_blue_murder() deb

[Kernel-packages] [Bug 1887156] Re: USB ports not working on the Pi 4 rev 1.4 board

** Changed in: linux-raspi2 (Ubuntu Eoan)
   Status: Confirmed => Fix Committed

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

Title:
  USB ports not working on the Pi 4 rev 1.4 board

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Bionic:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  USB on the Pi 4B rev 1.4 running the raspi 5.3 kernel is non-
  functional.

  [Test Case]

  See original description below.

  [Regression Potential]

  Low. The changes are isolated to the PCIe driver used for the
  Raspberry Pi. The commit is a clean cherry-pick from the raspi 5.4
  kernel.

  [Original Description]

  On the Pi 4 board revision 1.4 (of which the 8Gb model is currently
  the main example), the VL805 USB controller doesn't appear to be
  recognized by the 5.3 kernel. To reproduce:

  * Flash a current bionic image (e.g. 
http://cdimage.ubuntu.com/releases/bionic/release/ubuntu-18.04.4-preinstalled-server-arm64+raspi4.img.xz)
  * Boot the card on an older Pi model (3, 4 rev 1.2, etc.)
  * sudo add-apt-repository ppa:waveform/firmware
  * sudo apt install linux-firmware-raspi2 (the rev 1.4 requires a newer 
firmware package to boot; this PPA contains a test package with a back-ported 
firmware)
  * Boot the card on a Pi 4 rev 1.4
  * Observe USB2 and USB3 ports do not work
  * Boot the card on an older Pi 4 rev 1.2
  * Observe USB2 and USB3 ports do work

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

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

[Kernel-packages] [Bug 1879707] Re: [UBUNTU 20.04] mke2fs dasd(fba), Failing CCW, default ERP has run out of retries and failed

2020-07-20 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: New => In Progress

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

Title:
  [UBUNTU 20.04] mke2fs dasd(fba),Failing CCW,default ERP has run out of
  retries and failed

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  New

Bug description:
  mke2fs,dasd(fba) guest edevices FBA,default ERP has run out of retries and 
failed,Failing CCW
   
  ---uname output---
  xx -  5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:27:18 UTC 2020 s390x 
s390x s390x GNU/Linux
   
  Machine Type = IBM 3906 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   mke2fs to dasd(fba) devices
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  dasd(fba),Failing CCW,default ERP has run out of retries and failed between 
the following syslog events,
  mke2fs running, before mounting and starting IO to dasd(fba) devices

  May 14 14:33:32 ilabg13 root: ILAB_IO_FROM_MSDI_START
  May 14 14:48:34 ilabg13 root: ILAB_IO_FROM_MSDI_RUNNING

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

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

[Kernel-packages] [Bug 1864669] Re: overlayfs regression - internal getxattr operations without sepolicy checking

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  overlayfs regression - internal getxattr operations without sepolicy
  checking

Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-4.15 package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-4.15 source package in Xenial:
  Invalid
Status in linux-aws source package in Bionic:
  In Progress
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-azure-4.15 source package in Bionic:
  Fix Released
Status in linux-aws source package in Eoan:
  In Progress
Status in linux-azure source package in Eoan:
  Fix Released
Status in linux-azure-4.15 source package in Eoan:
  Invalid
Status in linux-aws source package in Focal:
  In Progress
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-azure-4.15 source package in Focal:
  Invalid

Bug description:
  Bug description and repro:

  Run the following commands on host instances:

  Prepare the overlayfs directories:
  $ cd /tmp
  $ mkdir -p base/dir1/dir2 upper olwork merged
  $ touch base/dir1/dir2/file
  $ chown -R 10:10 base upper olwork merged

  Verify that the directory is owned by user 10:
  $ ls -al merged/ 
  total 8
  drwxr-xr-x  2 10 10 4096 Nov  1 07:08 .
  drwxrwxrwt 16 root   root   4096 Nov  1 07:08 ..

  We use lxc-usernsexec to start a new shell as user 10.
  $ lxc-usernsexec -m b:0:10:1 -- /bin/bash
  $$ ls -al merged/
  total 8
  drwxr-xr-x  2 root   root4096 Nov  1 07:08 .
  drwxrwxrwt 16 nobody nogroup 4096 Nov  1 07:08 ..

  Notice that the ownership of . and .. has changed because the new shell is 
running as the remapped user.
  Now, mount the overlayfs as an unprivileged user in the new shell. This is 
the key to trigger the bug.
  $$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
  $$ ls -al merged/dir1/dir2/file 
  -rw-r--r-- 1 root root 0 Nov  1 07:09 merged/dir1/dir2/file

  We can see the file in the base layer from the mount directory. Now trigger 
the bug:
  $$ rm -rf merged/dir1/dir2/
  $$ mkdir merged/dir1/dir2
  $$ ls -al merged/dir1/dir2
  total 12
  drwxr-xr-x 2 root root 4096 Nov  1 07:10 .
  drwxr-xr-x 1 root root 4096 Nov  1 07:10 ..

  File does not show up in the newly created dir2 as expected. But it will 
reappear after we remount the filesystem (or any other means that might evict 
the cached dentry, such as attempt to delete the parent directory):
  $$ umount merged
  $$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
  $$ ls -al merged/dir1/dir2
  total 12
  drwxr-xr-x 1 root root 4096 Nov  1 07:10 .
  drwxr-xr-x 1 root root 4096 Nov  1 07:10 ..
  -rw-r--r-- 1 root root0 Nov  1 07:09 file
  $$ exit
  $

  This is a recent kernel regression. I tried the above step on an old
  kernel (4.4.0-1072-aws) but cannot reproduce.


  I looked up linux source code and figured out where the "regression" is 
coming from. The issue lies in how overlayfs checks the "opaque" flag from the 
underlying upper-level filesystem. It checks the "trusted.overlay.opaque" 
extended attribute to decide whether to hide the directory content from the 
lower level. The logic are different in 4.4 and 4.15 kernel.
  In 4.4: https://elixir.bootlin.com/linux/v4.4/source/fs/overlayfs/super.c#L255
  static bool ovl_is_opaquedir(struct dentry *dentry)
  {
int res;
char val;
struct inode *inode = dentry->d_inode;

if (!S_ISDIR(inode->i_mode) || !inode->i_op->getxattr)
return false;

res = inode->i_op->getxattr(dentry, OVL_XATTR_OPAQUE, &val, 1);
if (res == 1 && val == 'y')
return true;

return false;
  }

  In 4.15: 
https://elixir.bootlin.com/linux/v4.15/source/fs/overlayfs/util.c#L349
  static bool ovl_is_opaquedir(struct dentry *dentry)
  {
return ovl_check_dir_xattr(dentry, OVL_XATTR_OPAQUE);
  }

  bool ovl_check_dir_xattr(struct dentry *dentry, const char *name)
  {
int res;
char val;

if (!d_is_dir(dentry))
return false;

res = vfs_getxattr(dentry, name, &val, 1);
if (res == 1 && val == 'y')
return true;

return false;
  }

  The 4.4 version simply uses the internal i_node callback 
inode->i_op->getxattr from the host filesystem, which doesn't perform any 
permission check. While the 4.15 version calls the VFS interface vfs_getxattr 
that performs bunch of permission checks before the calling the internal 
insecure callback __vfs_getxa

[Kernel-packages] [Bug 1878421] Re: Using two GPUs with one monitor each, one is always black

2020-07-20 Thread frank

is maybe this also handled by gnome-flashback directly?

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

Title:
  Using two GPUs with one monitor each, one is always black

Status in Mutter:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi,

  i try to use external monitor on my dell G5 2019 (5590). works on
  ubuntu 18.4 (after reboot) using prime-select nvidia.

  did this on 20.4 (prime-select + reboot because logoff/login again
  still don't work) and it hang on boot while showing ubuntu bootscreen
  with animation (not stopped, but also response to esc-key to show
  terminal-output) on the monitor (need to switch off). booted again
  where monitor is configured to other input, boot works, i see it in
  preferences dialog as second monitor, but if i configure input on
  monitor i have no signal..

  
  anything i can try?

  regards Frank

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 13 15:21:08 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea]
  InstallationDate: Installed on 2020-04-27 (16 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 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. G5 5590
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0KW84T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  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.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/mutter/+bug/1878421/+subscriptions

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

[Kernel-packages] [Bug 1878421] Re: Using two GPUs with one monitor each, one is always black

2020-07-20 Thread frank

mhm, ubuntu-session is same...i see cursor but no background/window
while dragging, this time it looks stable, after loggin out (from
ubuntu-session), i see login-form on laptop-screen and purple background
on external monitor. after logging into flashback it's same as in
ubuntu-session with black screen, cursor visible but no windows

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

Title:
  Using two GPUs with one monitor each, one is always black

Status in Mutter:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi,

  i try to use external monitor on my dell G5 2019 (5590). works on
  ubuntu 18.4 (after reboot) using prime-select nvidia.

  did this on 20.4 (prime-select + reboot because logoff/login again
  still don't work) and it hang on boot while showing ubuntu bootscreen
  with animation (not stopped, but also response to esc-key to show
  terminal-output) on the monitor (need to switch off). booted again
  where monitor is configured to other input, boot works, i see it in
  preferences dialog as second monitor, but if i configure input on
  monitor i have no signal..

  
  anything i can try?

  regards Frank

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 13 15:21:08 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea]
  InstallationDate: Installed on 2020-04-27 (16 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 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. G5 5590
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0KW84T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  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.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/mutter/+bug/1878421/+subscriptions

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

[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00

It shouldn't be long that Ubuntu 20.04 kernel gets it from upstream.

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

Title:
  int3403 thermal INT3403:00

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   10.121722] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   12.165233] int3403 thermal INT3403:00: Unsupported event [0x91]

  Is constantly flooding my dmesg. I believe this is also due to missing
  audio drivers as well. Which is another issue that I am facing.

  Realtek ALC1220

  Ubuntu 20.04

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

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

[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00

The patch was meraged to 5.4 stable 5 hours ago - 
=
This is a note to let you know that I've just added the patch titled

thermal: int3403_thermal: Downgrade error message

to the 5.4-stable tree which can be found at:

http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
 thermal-int3403_thermal-downgrade-error-message.patch
and it can be found in the queue-5.4 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let  know about it.
=

details @ https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-
queue.git/commit/?id=0d0f826a596961721326485e02a37c9b49aafb7a

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

Title:
  int3403 thermal INT3403:00

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   10.121722] int3403 thermal INT3403:00: Unsupported event [0x91]
  [   12.165233] int3403 thermal INT3403:00: Unsupported event [0x91]

  Is constantly flooding my dmesg. I believe this is also due to missing
  audio drivers as well. Which is another issue that I am facing.

  Realtek ALC1220

  Ubuntu 20.04

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

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

[Kernel-packages] [Bug 1711283] Re: few kernel selftest failed on Ubuntu 17.10

2020-07-20 Thread Desnes A. Nunes do Rosario

The cycle_test failure does not reproduce on everyrun. In order to
validate you'll have to run the test a few times. Moreover, seems that
ZZ lpars are easier to reproduce this.

Last, this patch fixes this bug:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=3337bf41e0dd70b4064cdf60acdfcdc2d050066c

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

Title:
  few kernel selftest failed on Ubuntu 17.10

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

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-01 05:11:09 ==
  Problem Description
  
  Few kernel selftest failed on Ubuntu 17.10

  Environment
  --
  Kernel Build:  4.11.0-10-generic
  System Name : ltc-test-ci2
  Model  : 8247-22L
  Platform:  PowerNV ( P8 )

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

  Steps to reproduce:
  
  1. Get kernel source using apt source
  2. Start powerpc specific tests

  The following FAILS are observed.
  selftests:  cycles_test [FAIL]
  selftests:  cycles_with_freeze_test [FAIL]
  selftests:  pmc56_overflow_test [FAIL]
  selftests:  ebb_vs_cpu_event_test [FAIL]
  selftests:  cpu_event_vs_ebb_test [FAIL]
  selftests:  task_event_vs_ebb_test [FAIL]
  selftests:  multi_ebb_procs_test [FAIL]
  selftests:  multi_counter_test [FAIL]
  selftests:  pmae_handling_test [FAIL]
  selftests:  close_clears_pmcc_test [FAIL]
  selftests:  instruction_count_test [FAIL]
  selftests:  ebb_on_willing_child_test [FAIL]
  selftests:  back_to_back_ebbs_test [FAIL]
  selftests:  lost_exception_test [FAIL]
  selftests:  cycles_with_mmcr2_test [FAIL]
  selftests:  tm-vmxcopy [FAIL]

  Full run log is attached.

  == Comment: #5 - Harish Sriram  - 2017-08-08 03:33:36 ==
  With the latest ubuntu mainline kernel 4.13-rc4 from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/, I see following 
additional failures

  selftests:  ptrace-gpr [FAIL]
  selftests:  ptrace-tm-gpr [FAIL]
  selftests:  ptrace-tm-spd-gpr [FAIL]

  # uname -a
  Linux ltc-test-ci2 4.13.0-041300rc4-generic #201708062231 SMP Mon Aug 7 
03:29:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Thanks,
  Harish

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

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

[Kernel-packages] [Bug 1830151] Re: ebb: cycles_test in powerpc from ubuntu_kernel_selftests failed on B-hwe P9

2020-07-20 Thread Desnes A. Nunes do Rosario

Actually, this bug does not reproduce on everyrun. In order to validate
you'll have to run the test a few times. Moreover, seems that ZZ lpars
are easier to reproduce this.

Last, this patch fixes this bug:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=3337bf41e0dd70b4064cdf60acdfcdc2d050066c

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

Title:
  ebb: cycles_test in powerpc from ubuntu_kernel_selftests failed on
  B-hwe P9

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  This test has passed with Cosmic kernel on the same node ("baltar"),
  but not with the 4.18 kernel on Bionic.

   selftests: ebb: cycles_test
   
   test: cycles
   tags: git_version:unknown
   EBB Handler is at 0x10004170
   ebb_state:
   ebb_count = 10
   spurious = 0
   negative = 0
   no_overflow = 0
   pmc[1] count = 0x2843f
   pmc[2] count = 0x0
   pmc[3] count = 0x0
   pmc[4] count = 0x0
   pmc[5] count = 0x0
   pmc[6] count = 0x0
   HW state:
   MMCR0 0x8400 FC PMAE
   MMCR2 0x
   EBBHR 0x10004170
   BESCR 0x8000 GE
   PMC1 0x4000
   PMC2 0x
   PMC3 0x
   PMC4 0x
   PMC5 0x00028b3f
   PMC6 0x0002ac80
   SIAR 0x100035d4
   Trace buffer dump:
   address 0x71a628a2
   tail 0x71a628a201f6
   size 1048576
   overflow false
   Content:
   [0]: counter = 1
   [1]: register SPRN_MMCR0 = 0x8080
   [2]: register SPRN_PMC1 = 0x8004
   [3]: counter = 2
   [4]: register SPRN_MMCR0 = 0x8080
   [5]: register SPRN_PMC1 = 0x8004
   [6]: counter = 3
   [7]: register SPRN_MMCR0 = 0x8080
   [8]: register SPRN_PMC1 = 0x8004
   [FAIL] Test FAILED on line 52
   [9]: counter = 4
   [10]: register SPRN_MMCR0 = 0x8080
   [11]: register SPRN_PMC1 = 0x8004
   [12]: counter = 5
   [13]: register SPRN_MMCR0 = 0x8080
   [14]: register SPRN_PMC1 = 0x8004
   [15]: counter = 6
   [16]: register SPRN_MMCR0 = 0x8080
   [17]: register SPRN_PMC1 = 0x8004
   [18]: counter = 7
   [19]: register SPRN_MMCR0 = 0x8080
   [20]: register SPRN_PMC1 = 0x8004
   [21]: counter = 8
   [22]: register SPRN_MMCR0 = 0x8080
   [23]: register SPRN_PMC1 = 0x8004
   [24]: counter = 9
   [25]: register SPRN_MMCR0 = 0x8080
   [26]: register SPRN_PMC1 = 0x8004
   [27]: counter = 10
   [28]: register SPRN_MMCR0 = 0x8080
   [29]: register SPRN_PMC1 = 0x8004
   [30]: register SPRN_PMC1 = 0x4417
   PMC1 count (0x2843f) above upper limit 0x283e8 (+0x57)
   failure: cycles
   not ok 1..3 selftests: ebb: cycles_test [FAIL]

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

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

[Kernel-packages] [Bug 1881813] Re: [qxl] Desktop freezes 20.04

I did experience a complete lock of my system on the latest kernel and
it was worse then before, in a way that I was not able even to ssh to my
VM at all :(

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

Title:
  [qxl] Desktop freezes 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Not too much info yet, will add apport report, but see it very often on 20.04 
(upgraded from 18.04)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (759 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (759 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yuriw  1143 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (764 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   ens8  no wireless extensions.
   
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  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 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=2b5969aa-16c5-43c7-9a83-1c75e5e19363 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (46 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _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-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

2020-07-20 Thread Joshua Powers

Thanks for the review, it turns out that this failure has always been
present.

Going back to the Bionic 20180705 and Xenial 20180705, which were the
first releases of minimal, also showed that the system "Failed to find
module 'ib_iser'".

Is this something that could be fixed in order to prevent us from
shipping with failed systemd units?

** Description changed:

  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. 
- 
+ It appears the Bionic and Xenial minimal images have always shipped with a 
failing systemd unit: "systemd-modules-load.service" with the error "Failed to 
find module 'ib_iser'"
  
  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
- --- 
+ $ wget 
https://cloud-images.ubuntu.com/daily/server/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img
+ $ multipass launch file:///$(pwd)/ubuntu-18.04-minimal-cloudimg-amd64.img 
--name=bionic-minimal
+ $ multipass exec bionic-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': '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
+  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
+  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

-- 
You 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
  ---
  It appears the Bionic and Xenial minimal images have always shipped with a 
failing systemd unit: "systemd-modules-load.service" with the error "Failed to 
find module 'ib_iser'"

  Expected results
  ---
  $ sudo sy

[Kernel-packages] [Bug 1881813] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1881813/+attachment/5394404/+files/ProcCpuinfoMinimal.txt

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

Title:
  [qxl] Desktop freezes 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Not too much info yet, will add apport report, but see it very often on 20.04 
(upgraded from 18.04)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (759 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (759 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yuriw  1143 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (764 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   ens8  no wireless extensions.
   
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  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 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=2b5969aa-16c5-43c7-9a83-1c75e5e19363 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (46 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _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-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (805 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/ba

[Kernel-packages] [Bug 1881813] Re: [qxl] Desktop freezes 20.04

Correction I was able to shh it took very long time.

Attaching log files

** Attachment added: "journal1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881813/+attachment/5394402/+files/journal1.txt

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

Title:
  [qxl] Desktop freezes 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Not too much info yet, will add apport report, but see it very often on 20.04 
(upgraded from 18.04)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (759 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (759 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yuriw  1143 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (764 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   ens8  no wireless extensions.
   
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  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 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=2b5969aa-16c5-43c7-9a83-1c75e5e19363 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (46 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _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-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (805 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)

[Kernel-packages] [Bug 1881813] Re: [qxl] Desktop freezes 20.04

** Attachment added: "prevjournal1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881813/+attachment/5394403/+files/prevjournal1.txt

** Description changed:

  Not too much info yet, will add apport report, but see it very often on 20.04 
(upgraded from 18.04)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (759 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (759 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yuriw  1143 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-05-07 (764 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   ens8  no wireless extensions.
   
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  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 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=2b5969aa-16c5-43c7-9a83-1c75e5e19363 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (46 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _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-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.4
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2018-05-07 (805 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ Tags:  focal
+ Uname: Linux 5.8.0-050800rc5-lowlatency x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare su

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

2020-07-20 Thread Joshua Powers

Similar to bug 1888000, it appears this failure has also always been
present. I verified this against the focal 20200423 (oldest release with
5.4.0-1009-kvm) and 20200703 (newest release with 5.4.0-1018-kvm)
serials.

While this is no longer blocking image publication, is this something
that could be fixed in order to prevent us from shipping with failed
systemd units?

Both images produce a failure similar to:

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

Jul 20 12:15:30 ubuntu systemd-sysctl[134]: Couldn't write '4194304' to
'kernel/pid_max': Invalid argument


** Description changed:

  Overview
  ---
- This is *blocking* new minimal image promotion. Starting on or around 
20200714, the Focal minimal cloud images reported they failed to apply kernel 
variables during boot. 
- 
+ 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-modules-load.service loaded failed failed Load Kernel Modules 
+ systemd-sysctl.service loaded failed failed Apply Kernel Variables
+ 
  
  From the journal:
- Jul 17 10:30:12 ubuntu systemd[1]: systemd-sysctl.service: Main process 
exited, code=exited, status=1/FAILURE
- Jul 17 10:30:12 ubuntu systemd[1]: systemd-sysctl.service: Failed with result 
'exit-code'.
- Jul 17 10:30:12 ubuntu systemd[1]: Failed to start Apply Kernel Variables.
- Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Couldn't write '176' to 
'kernel/sysrq', ignoring: No such file or directory
- Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Not setting 
net/ipv4/conf/all/promote_secondaries (explicit setting exists).
- Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Not setting 
net/ipv4/conf/default/promote_secondaries (explicit setting exists).
- Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Couldn't write 'fq_codel' to 
'net/core/default_qdisc', ignoring: No such file or directory
- Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Couldn't write '4194304' to 
'kernel/pid_max': Invalid argument
+ 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
  ---
- 1. Download image from: 
https://private-fileshare.canonical.com/~powersj/minimal-focal/
- 2. multipass launch file:///
- 3. multipass exec  -- sudo systemctl list-units --failed --no-legend
- --- 
+ $ 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
+  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

[Kernel-packages] [Bug 1887218] Re: Ryzen 5 3500U - laptop won't boot when on battery power

Since the workaround involves amd's iommu and kernel 5.5, we may be able
to find a patch that fixes this by cherry-pikcy: git log --pretty=short
v5.4..v5.5 -- drivers/iommu/amd_iommu.c

commit 1daa56bcfd8b329447e0c1b1e91c3925d08489b7
Merge: a5255bc31673 9b3a713feef8
Author: Linus Torvalds 

Merge tag 'iommu-updates-v5.5' of
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu

commit 995e2ef08280dab8de6c517acd836613678fe2a3
Merge: 1fca7e0e6fe6 ae5e6c6439c3 cb0701acfa7e b5b42b24d783 2e127203d116
Author: Rafael J. Wysocki 

Merge branches 'acpi-utils', 'acpi-platform', 'acpi-video' and
'acpi-doc'

commit 9b3a713feef8db41d4bcccb3b97e86ee906690c8
Merge: 4e7120d79edb da6b05dce2a9 1289f7f15001 5b47748ecf2e c90ae4a63541 
96d3ab802e49 34d1b0895dbd 3c124435e8dd 6c3a44ed3c55 c1c8058dfb98 808be0aae53a
Author: Joerg Roedel 

Merge branches 'iommu/fixes', 'arm/qcom', 'arm/renesas',
'arm/rockchip', 'arm/mediatek', 'arm/tegra', 'arm/smmu', 'x86/amd',
'x86/vt-d', 'virtio' and 'core' into next


commit 3c124435e8dd516df4b2fc983f4415386fd6edae
Author: Logan Gunthorpe 

iommu/amd: Support multiple PCI DMA aliases in IRQ Remapping

commit 3332364e4ebc0581d133a334645a20fd13b580f1
Author: Logan Gunthorpe 

iommu/amd: Support multiple PCI DMA aliases in device table

commit a5bbbf37c6f8522a1afd46c37b5a0d1ce63232b7
Author: Denys Vlasenko 

iommu/amd: Do not re-fetch iommu->cmd_buf_tail

commit 3057fb9377eb5e73386dd0d8804bf72bdd23e391
Author: Joerg Roedel 

iommu/amd: Pass gfp flags to iommu_map_page() in amd_iommu_map()

commit 470eb3b31134ada545dcb41e94a0c97b42c95803
Author: Suthikulpanit, Suravee 

iommu/amd: Simpify decoding logic for INVALID_PPR_REQUEST event

commit ae5e6c6439c3d0ac8e9c71523790ba1ff6887894
Author: Andy Shevchenko 

iommu/amd: Switch to use acpi_dev_hid_uid_match()

commit be62dbf554c5b50718a54a359372c148cd9975c7
Author: Tom Murphy 

iommu/amd: Convert AMD iommu driver to the dma-iommu api

commit 781ca2de89bae1b1d2c96df9ef33e9a324415995
Author: Tom Murphy 

iommu: Add gfp parameter to iommu_ops::map

commit 37ec8eb851c1876580a963f283fe7496592b9f72
Author: Tom Murphy 

iommu/amd: Remove unnecessary locking from AMD iommu driver

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

Title:
  Ryzen 5 3500U - laptop won't boot when on battery power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ryzen 5 3500U (release in 2019) won't boot when laptop is on battery power. 
It affects different brands of laptops. Laptop boots normally with charger in 
and you can unplug the charger and then use battery. 
  For some a work around is possible on kernel 5.4. For others kernel should be 
5.5 or better yet 5.6.

  issue described in more detail in Ubuntu forums:
  https://ubuntuforums.org/showthread.php?t=2446942

  dmesg: https://paste.ubuntu.com/p/C2xNzpBKq5/

  iommu=soft boot options provides the work arround on some laptops,
  while on others USB ports stop working.

  OS: Kubuntu 20.04 LTS

  CPU: Ryzen 5 3500U
  GPU: AMD Vega 8
  RAM: 8 GB DDR4 2400 Mhz
  disk: 256 GB nvme

  
  I patched kernel (now tainted) to get driver for rtl8821ce (wi-fi).

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

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

[Kernel-packages] [Bug 1867559] Re: Qualcomm Atheros QCA9377 wifi 802.11ac very unstable and low speed

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Qualcomm Atheros QCA9377 wifi 802.11ac very unstable and low speed

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  rafa@acer:~$ sudo lshw -C network
  [sudo] senha para rafa: 
*-network 
 descrição: Ethernet interface
 produto: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 fabricante: Realtek Semiconductor Co., Ltd.
 ID físico: 0.1
 informações do barramento: pci@:01:00.1
 nome lógico: enp1s0f1
 versão: 12
 serial: 08:97:98:63:7d:2e
 capacidade: 1Gbit/s
 largura: 64 bits
 clock: 33MHz
 capacidades: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuração: autonegotiation=on broadcast=yes driver=r8169 
firmware=rtl8411-2_0.0.1 07/08/13 latency=0 link=no multicast=yes port=MII
 recursos: irq:16 porta de E/S:3000(tamanho=256) 
memória:b1204000-b1204fff memória:b120-b1203fff
*-network
 descrição: Interface sem fio
 produto: QCA9377 802.11ac Wireless Network Adapter
 fabricante: Qualcomm Atheros
 ID físico: 0
 informações do barramento: pci@:02:00.0
 nome lógico: wlp2s0
 versão: 31
 serial: a4:63:a1:0e:bc:42
 largura: 64 bits
 clock: 33MHz
 capacidades: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuração: broadcast=yes driver=ath10k_pci 
driverversion=5.3.0-40-generic firmware=WLAN.TF.2.1-00021-QCARMSWP-1 
ip=192.168.1.3 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 recursos: irq:132 memória:b100-b11f


  Download speed around 100-600Kb/s on 5GHz connection using WPA/WPA2.

  Notebook ACER ASPIRE 3 A315-53-343Y

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

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

[Kernel-packages] [Bug 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
  laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
  to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.

  I've been unsuccessful to pair with 2 different bluetooth mice.
  However bluetooth seems to work with other devices. I'm under the
  impression that this problem only happens with Bluetooth LE devices.

  Trying to pair using bluetoothctl fails with the
  org.bluez.Error.AuthenticationCanceled error:

  [bluetooth]# pair E5:5B:67:2A:09:76
  Attempting to pair with E5:5B:67:2A:09:76
  [CHG] Device E5:5B:67:2A:09:76 Connected: yes
  [CHG] Device E5:5B:67:2A:09:76 Connected: no
  Failed to pair: org.bluez.Error.AuthenticationCanceled

  A quick google search for org.bluez.Error.AuthenticationCanceled
  reported nothing relevant.

  Running btmon while trying to pair with the device gives me the
  following:

  Bluetooth monitor ver 5.53
  = Note: Linux version 5.4.0-40-generic (x86_64)   
0.998188
  = Note: Bluetooth subsystem version 2.22  
0.998193
  = New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0) 
 [hci0] 0.998194
  = Open Index: E8:6F:38:9C:2B:3C   
 [hci0] 0.998195
  = Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)   
 [hci0] 0.998197
  @ MGMT Open: bluetoothd (privileged) version 1.14 
   {0x0001} 0.998198
  @ MGMT Open: btmon (privileged) version 1.14  
   {0x0002} 0.998310
  @ MGMT Command: Pair Device (0x0019) plen 8   
{0x0001} [hci0] 8.162442
  LE Address: E5:5B:67:2A:09:76 (Static)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8   
  #1 [hci0] 8.162527
  Own address type: Public (0x00)
  Filter policy: Ignore not in white list (0x01)
  PHYs: 0x01
  Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
  > HCI Event: Command Complete (0x0e) plen 4   
  #2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
  Status: Success (0x00)
  < HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6   
  #3 [hci0] 8.284654
  Extended scan: Enabled (0x01)
  Filter duplicates: Enabled (0x01)
  Duration: 0 msec (0x)
  Period: 0.00 sec (0x)
  > HCI Event: Command Complete (0x0e) plen 4   
  #4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
  Status: Success (0x00)
  > HCI Event: LE Meta Event (0x3e) plen 52 
  #5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
  Num reports: 1
  Entry 0
Event type: 0x0013
  Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
  Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
  03 19 c2 03 02 01 05 03

[Kernel-packages] [Bug 1888116] Re: kernel 5.4.0-42-generic looping amdgpu errors

2020-07-20 Thread Günter Haus

apport-collect tells me that this bug is not open anymore (or not started by 
me) so i attach all relevant information, configurations and log files as 
tar.gz archive
Pls advice if any other information is reqired

** Attachment added: "all relevant log files"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888116/+attachment/5394454/+files/amdgpu-error-logs.tar.gz

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

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

Title:
  kernel 5.4.0-42-generic looping amdgpu errors

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to package "linux-image-5.4.0-42-generic" (5.4.0.42.45)
  several hundred system-log similar entires per minute are thrown at
  log:

  kernelamdgpu :09:00.0: amdgpu: [mmhub] page fault (src_id:0 
ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
  kernelamdgpu :09:00.0: amdgpu:   in page starting at address 
0xfffba000 from client 18
  kernelamdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00041F52
  kernelamdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: 0xf
  kernelamdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0
  kernelamdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x1
  kernelamdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x5
  kernelamdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x1
  kernelamdgpu :09:00.0: amdgpu: RW: 0x1

  System is a 20.04.1 Kubtuntu, with AMD Ryzen 5 and RX 5700 GPU, amdgpu
  with opencl installed (via amdgpu-
  pro-20.20-1089974-ubuntu-20.04.tar.xz from amd.com)

  Nevertheless no system freezes or graphic bugs happened

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

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

[Kernel-packages] [Bug 1887218] Re: Ryzen 5 3500U - laptop won't boot when on battery power

A test kernel, based on UBUNTU: Ubuntu-5.4.0-42.46, is available @
https://people.canonical.com/~alexhung/LP1887218/ver1/

If this solves this bug, we can keep bisecting. If not, we can try other
patches.

The following commits are excluded:

== merges ==
1daa56bcfd8b329447e0c1b1e91c3925d08489b7
995e2ef08280dab8de6c517acd836613678fe2a3
9b3a713feef8db41d4bcccb3b97e86ee906690c8

== cannot clean picked ==
3c124435e8dd516df4b2fc983f4415386fd6edae
3332364e4ebc0581d133a334645a20fd13b580f1

We can come back to these if the test kernel fails.


== fail to compile ==
ae5e6c6439c3d0ac8e9c71523790ba1ff6887894
This requires additional patch(es) but this is to replace an existing function 
with acpi_dev_hid_uid_match and should not have any effects

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

Title:
  Ryzen 5 3500U - laptop won't boot when on battery power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ryzen 5 3500U (release in 2019) won't boot when laptop is on battery power. 
It affects different brands of laptops. Laptop boots normally with charger in 
and you can unplug the charger and then use battery. 
  For some a work around is possible on kernel 5.4. For others kernel should be 
5.5 or better yet 5.6.

  issue described in more detail in Ubuntu forums:
  https://ubuntuforums.org/showthread.php?t=2446942

  dmesg: https://paste.ubuntu.com/p/C2xNzpBKq5/

  iommu=soft boot options provides the work arround on some laptops,
  while on others USB ports stop working.

  OS: Kubuntu 20.04 LTS

  CPU: Ryzen 5 3500U
  GPU: AMD Vega 8
  RAM: 8 GB DDR4 2400 Mhz
  disk: 256 GB nvme

  
  I patched kernel (now tainted) to get driver for rtl8821ce (wi-fi).

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

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

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

--- Comment From z...@us.ibm.com 2020-07-20 17:09 EDT---
I download iproute2-4.19.0.tar.gz from this upstream url:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git

Build and tested on my existing ppc64 Genesis OS (4.15.0-1039-ibm-gt),
I do see it now reports correct tcp_flags mask.

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

Title:
  tc filter show tcp_flags wrong mask value

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

Bug description:
  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

   
  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r
   
  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 22   /* <--- Wrong */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen
   
  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r
   
  After that, using "tc filter show dev p0v2_r root" to verify, we still see 
the same output (tcp_flags 22) as shown in 2) above, which is wrong.
   
  Userspace tool common name: tc 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */
   
  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.
   
  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 0x2/7   /* <--- Correct */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

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

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

[Kernel-packages] [Bug 1885757] Re: seccomp_bpf fails on powerpc

This bug was fixed in the package linux - 4.15.0-112.113

---
linux (4.15.0-112.113) bionic; urgency=medium

  * bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * CVE-2020-11935
- SAUCE: aufs: do not call i_readcount_inc()
- SAUCE: aufs: bugfix, IMA i_readcount

  * CVE-2020-10757
- mm: Fix mremap not considering huge pmd devmap

  * Update lockdown patches (LP: #1884159)
- efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN
- efi: Restrict efivar_ssdt_load when the kernel is locked down
- powerpc/xmon: add read-only mode
- powerpc/xmon: Restrict when kernel is locked down
- [Config] CONFIG_XMON_DEFAULT_RO_MODE=y
- SAUCE: acpi: disallow loading configfs acpi tables when locked down

  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc

  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

 -- Khalid Elmously   Thu, 09 Jul 2020
19:13:37 -0400

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10757

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

Title:
  seccomp_bpf fails on powerpc

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  seccomp_bpf test fails on powerpc and ends up being disabled on some series, 
or causing engineers to waste their time verifying the same failures are the 
only ones we see every kernel release.

  [Test case]
  Run the test and notice there are no more failures.

  [Regression potential]
  We may break the test on different architectures. That doesn't break users, 
though, as the changes are only on tests. It has been tested at least on 
ppc64el and amd64.

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

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

[Kernel-packages] [Bug 1882955] Re: LXD 4.2 broken on linux-kvm due to missing VLAN filtering

This bug was fixed in the package linux-kvm - 4.15.0-1071.72

---
linux-kvm (4.15.0-1071.72) bionic; urgency=medium

  * bionic/linux-kvm: 4.15.0-1071.72 -proposed tracker (LP: #1887041)

  [ Ubuntu: 4.15.0-112.113 ]

  * bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * CVE-2020-11935
- SAUCE: aufs: do not call i_readcount_inc()
- SAUCE: aufs: bugfix, IMA i_readcount
  * CVE-2020-10757
- mm: Fix mremap not considering huge pmd devmap
  * Update lockdown patches (LP: #1884159)
- efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN
- efi: Restrict efivar_ssdt_load when the kernel is locked down
- powerpc/xmon: add read-only mode
- powerpc/xmon: Restrict when kernel is locked down
- [Config] CONFIG_XMON_DEFAULT_RO_MODE=y
- SAUCE: acpi: disallow loading configfs acpi tables when locked down
  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc
  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

  [ Ubuntu: 4.15.0-111.112 ]

  * bionic/linux: 4.15.0-111.112 -proposed tracker (LP: #1886999)
  * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461)
- SAUCE: mlxsw: Add missmerged ERR_PTR hunk
  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

linux-kvm (4.15.0-1070.71) bionic; urgency=medium

  * bionic/linux-kvm: 4.15.0-1070.71 -proposed tracker (LP: #1885807)

  * Build and ship a signed wireguard.ko (LP: #1861284)
- [Config] kvm: wireguard -- enable on all architectures

  * LXD 4.2 broken on linux-kvm due to missing VLAN filtering (LP: #1882955)
- [Config] VLAN_8021Q=m && BRIDGE_VLAN_FILTERING=y

  [ Ubuntu: 4.15.0-110.111 ]

  * bionic/linux: 4.15.0-110.111 -proposed tracker (LP: #1885814)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * CVE-2020-11935
- SAUCE: aufs: do not call i_readcount_inc()
- SAUCE: aufs: bugfix, IMA i_readcount
  * CVE-2020-10757
- mm: Fix mremap not considering huge pmd devmap
  * Update lockdown patches (LP: #1884159)
- efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN
- efi: Restrict efivar_ssdt_load when the kernel is locked down
- powerpc/xmon: add read-only mode
- powerpc/xmon: Restrict when kernel is locked down
- [Config] CONFIG_XMON_DEFAULT_RO_MODE=y
- SAUCE: acpi: disallow loading configfs acpi tables when locked down
  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc
  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

 -- Khalid Elmously   Thu, 09 Jul 2020
22:13:34 -0400

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10757

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-11935

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

Title:
  LXD 4.2 broken on linux-kvm due to missing VLAN filtering

Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Fix Released
Status in linux-kvm source package in Bionic:
  Fix Released
Status in linux-kvm source package in Eoan:
  Fix Committed
Status in linux-kvm source package in Focal:
  Fix Released

Bug description:
  [Description]

  Some VLAN options (BRIDGE_VLAN_FILTERING, and its dependencies
  VLAN_8021Q*) were in a different state in Focal/kvm compared to
  Focal/generic: LXD now depends on BRIDGE_VLAN_FILTERING and due to
  this discrepancy it fails to work on the Focal/kvm kernel: fix it by
  aligning the config with Focal/generic

  [Fix]

  Apply the attached config patch

  [Regression potential]

  Low, just some config changes already present in generic.

  ---
  This is another case of linux-kvm having unexplained differences compared to 
linux-generic in areas that aren't related to hardware drivers (see other bug 
we filed for missing nft).

  This time, CPC is reporting that LXD no longer works on linux-kvm as
  we now set vlan filtering on our bridges to prevent containers from
  escaping firewalling through custom vlan tags.

  This relies on CONFIG_BRIDGE_VLAN_FILTERING which is a built-in on the
  generic kernel but is apparently missing on linux-kvm (I don't have
  any system running that kernel to confirm its config, but the behavior
  certainly matches that).

  We ne

[Kernel-packages] [Bug 1881137] Re: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers

This bug was fixed in the package linux - 4.15.0-112.113

---
linux (4.15.0-112.113) bionic; urgency=medium

  * bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * CVE-2020-11935
- SAUCE: aufs: do not call i_readcount_inc()
- SAUCE: aufs: bugfix, IMA i_readcount

  * CVE-2020-10757
- mm: Fix mremap not considering huge pmd devmap

  * Update lockdown patches (LP: #1884159)
- efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN
- efi: Restrict efivar_ssdt_load when the kernel is locked down
- powerpc/xmon: add read-only mode
- powerpc/xmon: Restrict when kernel is locked down
- [Config] CONFIG_XMON_DEFAULT_RO_MODE=y
- SAUCE: acpi: disallow loading configfs acpi tables when locked down

  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc

  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

 -- Khalid Elmously   Thu, 09 Jul 2020
19:13:37 -0400

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10757

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

Title:
  Introduce the new NVIDIA 418-server and 440-server series, and update
  the current NVIDIA drivers

Status in linux package in Ubuntu:
  Incomplete
Status in linux-restricted-modules package in Ubuntu:
  New
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-440-server source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-440-server source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  440.82:
    * New upstream release:
  - Added a workaround for Steam Play title DOOM Eternal, which
    overrides application requested memory locations, to ensure
    performance-critical resources be placed in video memory.
  - Allow presenting from queue families which only expose
    VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib
    surfaces.
  - Fixed a bug that caused render-offloaded applications to crash
    on exit.
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'timespec_to_ns'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'getrawmonotonic'".
  - Fixed a driver installation failure on Linux kernel 5.6 release
    candidates, where the NVIDIA kernel module failed to build with
    error "implicit declaration of function 'timespec_to_ns'".
  - Fixed a driver installation failure on Linux kernel 5.6

[Kernel-packages] [Bug 1884159] Re: Update lockdown patches

This bug was fixed in the package linux - 4.15.0-112.113

---
linux (4.15.0-112.113) bionic; urgency=medium

  * bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * CVE-2020-11935
- SAUCE: aufs: do not call i_readcount_inc()
- SAUCE: aufs: bugfix, IMA i_readcount

  * CVE-2020-10757
- mm: Fix mremap not considering huge pmd devmap

  * Update lockdown patches (LP: #1884159)
- efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN
- efi: Restrict efivar_ssdt_load when the kernel is locked down
- powerpc/xmon: add read-only mode
- powerpc/xmon: Restrict when kernel is locked down
- [Config] CONFIG_XMON_DEFAULT_RO_MODE=y
- SAUCE: acpi: disallow loading configfs acpi tables when locked down

  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc

  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

 -- Khalid Elmously   Thu, 09 Jul 2020
19:13:37 -0400

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10757

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

Title:
  Update lockdown patches

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  Impact: The lockdown patches have evolved over time, and part of this
  was restricting more areas of the kernel. Not all of these additions
  were backported, and some can lead to lockdown bypasses, see [1] and
  [2].

  Fix: Backport newer lockdown restrictions to older releases.

  Test Case: Test cases for most of the backports can be found at [3],
  and [4] is another test case. Some which need e.g. specific hardware
  to test have not been tested.

  Regression Potential: Most of these are small, simple fixes with low
  potential for regression. Users may also lose access to some
  functionality previously accissible under secure boot. Some changes
  are more substantial, especially the hw_param and debugfs changes for
  xenial, but they are based on well-tested upstream code. The xmon
  backports also carry a more moderate risk of regression.

  [1] https://lists.ubuntu.com/archives/kernel-team/2020-June/111050.html
  [2] https://lore.kernel.org/lkml/20200615104332.901519-1-ja...@zx2c4.com/
  [3] https://git.launchpad.net/~sforshee/+git/lockdown-tests
  [4] 
https://git.zx2c4.com/american-unsigned-language/tree/american-unsigned-language.sh

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

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

[Kernel-packages] [Bug 1884159] Re: Update lockdown patches

This bug was fixed in the package linux - 4.4.0-186.216

---
linux (4.4.0-186.216) xenial; urgency=medium

  * xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514)

  * Xenial update: v4.4.228 upstream stable release (LP: #1884564)
- ipv6: fix IPV6_ADDRFORM operation logic
- vxlan: Avoid infinite loop when suppressing NS messages with invalid 
options
- scsi: return correct blkprep status code in case scsi_init_io() fails.
- net: phy: marvell: Limit 88m1101 autoneg errata to 88E1145 as well.
- pwm: fsl-ftm: Use flat regmap cache
- ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
- sched/fair: Don't NUMA balance for kthreads
- ath9k_htc: Silence undersized packet warnings
- x86_64: Fix jiffies ODR violation
- x86/speculation: Prevent rogue cross-process SSBD shutdown
- x86/reboot/quirks: Add MacBook6,1 reboot quirk
- efi/efivars: Add missing kobject_put() in sysfs entry creation error path
- ALSA: es1688: Add the missed snd_card_free()
- ALSA: usb-audio: Fix inconsistent card PM state after resume
- ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile()
- ACPI: PM: Avoid using power resources if there are none for D0
- cgroup, blkcg: Prepare some symbols for module and !CONFIG_CGROUP usages
- nilfs2: fix null pointer dereference at nilfs_segctor_do_construct()
- spi: bcm2835aux: Fix controller unregister order
- ALSA: pcm: disallow linking stream to itself
- x86/speculation: Change misspelled STIPB to STIBP
- x86/speculation: Add support for STIBP always-on preferred mode
- x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced
  IBRS.
- x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
- spi: dw: fix possible race condition
- spi: dw: Fix controller unregister order
- spi: No need to assign dummy value in spi_unregister_controller()
- spi: Fix controller unregister order
- spi: pxa2xx: Fix controller unregister order
- spi: bcm2835: Fix controller unregister order
- ovl: initialize error in ovl_copy_xattr
- proc: Use new_inode not new_inode_pseudo
- video: fbdev: w100fb: Fix a potential double free.
- KVM: nSVM: leave ASID aside in copy_vmcb_control_area
- KVM: nVMX: Consult only the "basic" exit reason when routing nested exit
- KVM: arm64: Make vcpu_cp1x() work on Big Endian hosts
- ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx
- ath9k: Fix use-after-free Write in ath9k_htc_rx_msg
- ath9x: Fix stack-out-of-bounds Write in ath9k_hif_usb_rx_cb
- ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb
- Smack: slab-out-of-bounds in vsscanf
- mm/slub: fix a memory leak in sysfs_slab_add()
- fat: don't allow to mount if the FAT length == 0
- can: kvaser_usb: kvaser_usb_leaf: Fix some info-leaks to USB devices
- spi: dw: Zero DMA Tx and Rx configurations on stack
- Bluetooth: Add SCO fallback for invalid LMP parameters error
- kgdb: Prevent infinite recursive entries to the debugger
- spi: dw: Enable interrupts in accordance with DMA xfer mode
- clocksource: dw_apb_timer_of: Fix missing clockevent timers
- btrfs: do not ignore error from btrfs_next_leaf() when inserting checksums
- ARM: 8978/1: mm: make act_mm() respect THREAD_SIZE
- net: vmxnet3: fix possible buffer overflow caused by bad DMA value in
  vmxnet3_get_rss()
- staging: android: ion: use vmap instead of vm_map_ram
- e1000: Distribute switch variables for initialization
- media: dvb: return -EREMOTEIO on i2c transfer failure.
- MIPS: Make sparse_init() using top-down allocation
- netfilter: nft_nat: return EOPNOTSUPP if type or flags are not supported
- lib/mpi: Fix 64-bit MIPS build with Clang
- net: lpc-enet: fix error return code in lpc_mii_init()
- net: allwinner: Fix use correct return type for ndo_start_xmit()
- powerpc/spufs: fix copy_to_user while atomic
- mips: cm: Fix an invalid error code of INTVN_*_ERR
- kgdb: Fix spurious true from in_dbg_master()
- md: don't flush workqueue unconditionally in md_open
- mwifiex: Fix memory corruption in dump_station
- mips: Add udelay lpj numbers adjustment
- x86/mm: Stop printing BRK addresses
- m68k: mac: Don't call via_flush_cache() on Mac IIfx
- macvlan: Skip loopback packets in RX handler
- PCI: Don't disable decoding when mmio_always_on is set
- MIPS: Fix IRQ tracing when call handle_fpe() and handle_msa_fpe()
- ixgbe: fix signed-integer-overflow warning
- spi: dw: Return any value retrieved from the dma_transfer callback
- cpuidle: Fix three reference count leaks
- ima: Fix ima digest hash table key calculation
- ext4: fix EXT_MAX_EXTENT/INDEX to check for zeroed eh_max
- Btrfs: fix unreplayable log after snapshot delete + parent dir fsync
- btrfs: send: emit file capabilities after chow

[Kernel-packages] [Bug 1883918] Re: Xenial update: v4.4.227 upstream stable release

This bug was fixed in the package linux - 4.4.0-186.216

---
linux (4.4.0-186.216) xenial; urgency=medium

  * xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514)

  * Xenial update: v4.4.228 upstream stable release (LP: #1884564)
- ipv6: fix IPV6_ADDRFORM operation logic
- vxlan: Avoid infinite loop when suppressing NS messages with invalid 
options
- scsi: return correct blkprep status code in case scsi_init_io() fails.
- net: phy: marvell: Limit 88m1101 autoneg errata to 88E1145 as well.
- pwm: fsl-ftm: Use flat regmap cache
- ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
- sched/fair: Don't NUMA balance for kthreads
- ath9k_htc: Silence undersized packet warnings
- x86_64: Fix jiffies ODR violation
- x86/speculation: Prevent rogue cross-process SSBD shutdown
- x86/reboot/quirks: Add MacBook6,1 reboot quirk
- efi/efivars: Add missing kobject_put() in sysfs entry creation error path
- ALSA: es1688: Add the missed snd_card_free()
- ALSA: usb-audio: Fix inconsistent card PM state after resume
- ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile()
- ACPI: PM: Avoid using power resources if there are none for D0
- cgroup, blkcg: Prepare some symbols for module and !CONFIG_CGROUP usages
- nilfs2: fix null pointer dereference at nilfs_segctor_do_construct()
- spi: bcm2835aux: Fix controller unregister order
- ALSA: pcm: disallow linking stream to itself
- x86/speculation: Change misspelled STIPB to STIBP
- x86/speculation: Add support for STIBP always-on preferred mode
- x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced
  IBRS.
- x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
- spi: dw: fix possible race condition
- spi: dw: Fix controller unregister order
- spi: No need to assign dummy value in spi_unregister_controller()
- spi: Fix controller unregister order
- spi: pxa2xx: Fix controller unregister order
- spi: bcm2835: Fix controller unregister order
- ovl: initialize error in ovl_copy_xattr
- proc: Use new_inode not new_inode_pseudo
- video: fbdev: w100fb: Fix a potential double free.
- KVM: nSVM: leave ASID aside in copy_vmcb_control_area
- KVM: nVMX: Consult only the "basic" exit reason when routing nested exit
- KVM: arm64: Make vcpu_cp1x() work on Big Endian hosts
- ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx
- ath9k: Fix use-after-free Write in ath9k_htc_rx_msg
- ath9x: Fix stack-out-of-bounds Write in ath9k_hif_usb_rx_cb
- ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb
- Smack: slab-out-of-bounds in vsscanf
- mm/slub: fix a memory leak in sysfs_slab_add()
- fat: don't allow to mount if the FAT length == 0
- can: kvaser_usb: kvaser_usb_leaf: Fix some info-leaks to USB devices
- spi: dw: Zero DMA Tx and Rx configurations on stack
- Bluetooth: Add SCO fallback for invalid LMP parameters error
- kgdb: Prevent infinite recursive entries to the debugger
- spi: dw: Enable interrupts in accordance with DMA xfer mode
- clocksource: dw_apb_timer_of: Fix missing clockevent timers
- btrfs: do not ignore error from btrfs_next_leaf() when inserting checksums
- ARM: 8978/1: mm: make act_mm() respect THREAD_SIZE
- net: vmxnet3: fix possible buffer overflow caused by bad DMA value in
  vmxnet3_get_rss()
- staging: android: ion: use vmap instead of vm_map_ram
- e1000: Distribute switch variables for initialization
- media: dvb: return -EREMOTEIO on i2c transfer failure.
- MIPS: Make sparse_init() using top-down allocation
- netfilter: nft_nat: return EOPNOTSUPP if type or flags are not supported
- lib/mpi: Fix 64-bit MIPS build with Clang
- net: lpc-enet: fix error return code in lpc_mii_init()
- net: allwinner: Fix use correct return type for ndo_start_xmit()
- powerpc/spufs: fix copy_to_user while atomic
- mips: cm: Fix an invalid error code of INTVN_*_ERR
- kgdb: Fix spurious true from in_dbg_master()
- md: don't flush workqueue unconditionally in md_open
- mwifiex: Fix memory corruption in dump_station
- mips: Add udelay lpj numbers adjustment
- x86/mm: Stop printing BRK addresses
- m68k: mac: Don't call via_flush_cache() on Mac IIfx
- macvlan: Skip loopback packets in RX handler
- PCI: Don't disable decoding when mmio_always_on is set
- MIPS: Fix IRQ tracing when call handle_fpe() and handle_msa_fpe()
- ixgbe: fix signed-integer-overflow warning
- spi: dw: Return any value retrieved from the dma_transfer callback
- cpuidle: Fix three reference count leaks
- ima: Fix ima digest hash table key calculation
- ext4: fix EXT_MAX_EXTENT/INDEX to check for zeroed eh_max
- Btrfs: fix unreplayable log after snapshot delete + parent dir fsync
- btrfs: send: emit file capabilities after chow

[Kernel-packages] [Bug 1884564] Re: Xenial update: v4.4.228 upstream stable release

This bug was fixed in the package linux - 4.4.0-186.216

---
linux (4.4.0-186.216) xenial; urgency=medium

  * xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514)

  * Xenial update: v4.4.228 upstream stable release (LP: #1884564)
- ipv6: fix IPV6_ADDRFORM operation logic
- vxlan: Avoid infinite loop when suppressing NS messages with invalid 
options
- scsi: return correct blkprep status code in case scsi_init_io() fails.
- net: phy: marvell: Limit 88m1101 autoneg errata to 88E1145 as well.
- pwm: fsl-ftm: Use flat regmap cache
- ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
- sched/fair: Don't NUMA balance for kthreads
- ath9k_htc: Silence undersized packet warnings
- x86_64: Fix jiffies ODR violation
- x86/speculation: Prevent rogue cross-process SSBD shutdown
- x86/reboot/quirks: Add MacBook6,1 reboot quirk
- efi/efivars: Add missing kobject_put() in sysfs entry creation error path
- ALSA: es1688: Add the missed snd_card_free()
- ALSA: usb-audio: Fix inconsistent card PM state after resume
- ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile()
- ACPI: PM: Avoid using power resources if there are none for D0
- cgroup, blkcg: Prepare some symbols for module and !CONFIG_CGROUP usages
- nilfs2: fix null pointer dereference at nilfs_segctor_do_construct()
- spi: bcm2835aux: Fix controller unregister order
- ALSA: pcm: disallow linking stream to itself
- x86/speculation: Change misspelled STIPB to STIBP
- x86/speculation: Add support for STIBP always-on preferred mode
- x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced
  IBRS.
- x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
- spi: dw: fix possible race condition
- spi: dw: Fix controller unregister order
- spi: No need to assign dummy value in spi_unregister_controller()
- spi: Fix controller unregister order
- spi: pxa2xx: Fix controller unregister order
- spi: bcm2835: Fix controller unregister order
- ovl: initialize error in ovl_copy_xattr
- proc: Use new_inode not new_inode_pseudo
- video: fbdev: w100fb: Fix a potential double free.
- KVM: nSVM: leave ASID aside in copy_vmcb_control_area
- KVM: nVMX: Consult only the "basic" exit reason when routing nested exit
- KVM: arm64: Make vcpu_cp1x() work on Big Endian hosts
- ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx
- ath9k: Fix use-after-free Write in ath9k_htc_rx_msg
- ath9x: Fix stack-out-of-bounds Write in ath9k_hif_usb_rx_cb
- ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb
- Smack: slab-out-of-bounds in vsscanf
- mm/slub: fix a memory leak in sysfs_slab_add()
- fat: don't allow to mount if the FAT length == 0
- can: kvaser_usb: kvaser_usb_leaf: Fix some info-leaks to USB devices
- spi: dw: Zero DMA Tx and Rx configurations on stack
- Bluetooth: Add SCO fallback for invalid LMP parameters error
- kgdb: Prevent infinite recursive entries to the debugger
- spi: dw: Enable interrupts in accordance with DMA xfer mode
- clocksource: dw_apb_timer_of: Fix missing clockevent timers
- btrfs: do not ignore error from btrfs_next_leaf() when inserting checksums
- ARM: 8978/1: mm: make act_mm() respect THREAD_SIZE
- net: vmxnet3: fix possible buffer overflow caused by bad DMA value in
  vmxnet3_get_rss()
- staging: android: ion: use vmap instead of vm_map_ram
- e1000: Distribute switch variables for initialization
- media: dvb: return -EREMOTEIO on i2c transfer failure.
- MIPS: Make sparse_init() using top-down allocation
- netfilter: nft_nat: return EOPNOTSUPP if type or flags are not supported
- lib/mpi: Fix 64-bit MIPS build with Clang
- net: lpc-enet: fix error return code in lpc_mii_init()
- net: allwinner: Fix use correct return type for ndo_start_xmit()
- powerpc/spufs: fix copy_to_user while atomic
- mips: cm: Fix an invalid error code of INTVN_*_ERR
- kgdb: Fix spurious true from in_dbg_master()
- md: don't flush workqueue unconditionally in md_open
- mwifiex: Fix memory corruption in dump_station
- mips: Add udelay lpj numbers adjustment
- x86/mm: Stop printing BRK addresses
- m68k: mac: Don't call via_flush_cache() on Mac IIfx
- macvlan: Skip loopback packets in RX handler
- PCI: Don't disable decoding when mmio_always_on is set
- MIPS: Fix IRQ tracing when call handle_fpe() and handle_msa_fpe()
- ixgbe: fix signed-integer-overflow warning
- spi: dw: Return any value retrieved from the dma_transfer callback
- cpuidle: Fix three reference count leaks
- ima: Fix ima digest hash table key calculation
- ext4: fix EXT_MAX_EXTENT/INDEX to check for zeroed eh_max
- Btrfs: fix unreplayable log after snapshot delete + parent dir fsync
- btrfs: send: emit file capabilities after chow

[Kernel-packages] [Bug 1883917] Re: Xenial update: v4.4.226 upstream stable release

This bug was fixed in the package linux - 4.4.0-186.216

---
linux (4.4.0-186.216) xenial; urgency=medium

  * xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514)

  * Xenial update: v4.4.228 upstream stable release (LP: #1884564)
- ipv6: fix IPV6_ADDRFORM operation logic
- vxlan: Avoid infinite loop when suppressing NS messages with invalid 
options
- scsi: return correct blkprep status code in case scsi_init_io() fails.
- net: phy: marvell: Limit 88m1101 autoneg errata to 88E1145 as well.
- pwm: fsl-ftm: Use flat regmap cache
- ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
- sched/fair: Don't NUMA balance for kthreads
- ath9k_htc: Silence undersized packet warnings
- x86_64: Fix jiffies ODR violation
- x86/speculation: Prevent rogue cross-process SSBD shutdown
- x86/reboot/quirks: Add MacBook6,1 reboot quirk
- efi/efivars: Add missing kobject_put() in sysfs entry creation error path
- ALSA: es1688: Add the missed snd_card_free()
- ALSA: usb-audio: Fix inconsistent card PM state after resume
- ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile()
- ACPI: PM: Avoid using power resources if there are none for D0
- cgroup, blkcg: Prepare some symbols for module and !CONFIG_CGROUP usages
- nilfs2: fix null pointer dereference at nilfs_segctor_do_construct()
- spi: bcm2835aux: Fix controller unregister order
- ALSA: pcm: disallow linking stream to itself
- x86/speculation: Change misspelled STIPB to STIBP
- x86/speculation: Add support for STIBP always-on preferred mode
- x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced
  IBRS.
- x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
- spi: dw: fix possible race condition
- spi: dw: Fix controller unregister order
- spi: No need to assign dummy value in spi_unregister_controller()
- spi: Fix controller unregister order
- spi: pxa2xx: Fix controller unregister order
- spi: bcm2835: Fix controller unregister order
- ovl: initialize error in ovl_copy_xattr
- proc: Use new_inode not new_inode_pseudo
- video: fbdev: w100fb: Fix a potential double free.
- KVM: nSVM: leave ASID aside in copy_vmcb_control_area
- KVM: nVMX: Consult only the "basic" exit reason when routing nested exit
- KVM: arm64: Make vcpu_cp1x() work on Big Endian hosts
- ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx
- ath9k: Fix use-after-free Write in ath9k_htc_rx_msg
- ath9x: Fix stack-out-of-bounds Write in ath9k_hif_usb_rx_cb
- ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb
- Smack: slab-out-of-bounds in vsscanf
- mm/slub: fix a memory leak in sysfs_slab_add()
- fat: don't allow to mount if the FAT length == 0
- can: kvaser_usb: kvaser_usb_leaf: Fix some info-leaks to USB devices
- spi: dw: Zero DMA Tx and Rx configurations on stack
- Bluetooth: Add SCO fallback for invalid LMP parameters error
- kgdb: Prevent infinite recursive entries to the debugger
- spi: dw: Enable interrupts in accordance with DMA xfer mode
- clocksource: dw_apb_timer_of: Fix missing clockevent timers
- btrfs: do not ignore error from btrfs_next_leaf() when inserting checksums
- ARM: 8978/1: mm: make act_mm() respect THREAD_SIZE
- net: vmxnet3: fix possible buffer overflow caused by bad DMA value in
  vmxnet3_get_rss()
- staging: android: ion: use vmap instead of vm_map_ram
- e1000: Distribute switch variables for initialization
- media: dvb: return -EREMOTEIO on i2c transfer failure.
- MIPS: Make sparse_init() using top-down allocation
- netfilter: nft_nat: return EOPNOTSUPP if type or flags are not supported
- lib/mpi: Fix 64-bit MIPS build with Clang
- net: lpc-enet: fix error return code in lpc_mii_init()
- net: allwinner: Fix use correct return type for ndo_start_xmit()
- powerpc/spufs: fix copy_to_user while atomic
- mips: cm: Fix an invalid error code of INTVN_*_ERR
- kgdb: Fix spurious true from in_dbg_master()
- md: don't flush workqueue unconditionally in md_open
- mwifiex: Fix memory corruption in dump_station
- mips: Add udelay lpj numbers adjustment
- x86/mm: Stop printing BRK addresses
- m68k: mac: Don't call via_flush_cache() on Mac IIfx
- macvlan: Skip loopback packets in RX handler
- PCI: Don't disable decoding when mmio_always_on is set
- MIPS: Fix IRQ tracing when call handle_fpe() and handle_msa_fpe()
- ixgbe: fix signed-integer-overflow warning
- spi: dw: Return any value retrieved from the dma_transfer callback
- cpuidle: Fix three reference count leaks
- ima: Fix ima digest hash table key calculation
- ext4: fix EXT_MAX_EXTENT/INDEX to check for zeroed eh_max
- Btrfs: fix unreplayable log after snapshot delete + parent dir fsync
- btrfs: send: emit file capabilities after chow

[Kernel-packages] [Bug 1883916] Re: Xenial update: v4.4.225 upstream stable release

This bug was fixed in the package linux - 4.4.0-186.216

---
linux (4.4.0-186.216) xenial; urgency=medium

  * xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514)

  * Xenial update: v4.4.228 upstream stable release (LP: #1884564)
- ipv6: fix IPV6_ADDRFORM operation logic
- vxlan: Avoid infinite loop when suppressing NS messages with invalid 
options
- scsi: return correct blkprep status code in case scsi_init_io() fails.
- net: phy: marvell: Limit 88m1101 autoneg errata to 88E1145 as well.
- pwm: fsl-ftm: Use flat regmap cache
- ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
- sched/fair: Don't NUMA balance for kthreads
- ath9k_htc: Silence undersized packet warnings
- x86_64: Fix jiffies ODR violation
- x86/speculation: Prevent rogue cross-process SSBD shutdown
- x86/reboot/quirks: Add MacBook6,1 reboot quirk
- efi/efivars: Add missing kobject_put() in sysfs entry creation error path
- ALSA: es1688: Add the missed snd_card_free()
- ALSA: usb-audio: Fix inconsistent card PM state after resume
- ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile()
- ACPI: PM: Avoid using power resources if there are none for D0
- cgroup, blkcg: Prepare some symbols for module and !CONFIG_CGROUP usages
- nilfs2: fix null pointer dereference at nilfs_segctor_do_construct()
- spi: bcm2835aux: Fix controller unregister order
- ALSA: pcm: disallow linking stream to itself
- x86/speculation: Change misspelled STIPB to STIBP
- x86/speculation: Add support for STIBP always-on preferred mode
- x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced
  IBRS.
- x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
- spi: dw: fix possible race condition
- spi: dw: Fix controller unregister order
- spi: No need to assign dummy value in spi_unregister_controller()
- spi: Fix controller unregister order
- spi: pxa2xx: Fix controller unregister order
- spi: bcm2835: Fix controller unregister order
- ovl: initialize error in ovl_copy_xattr
- proc: Use new_inode not new_inode_pseudo
- video: fbdev: w100fb: Fix a potential double free.
- KVM: nSVM: leave ASID aside in copy_vmcb_control_area
- KVM: nVMX: Consult only the "basic" exit reason when routing nested exit
- KVM: arm64: Make vcpu_cp1x() work on Big Endian hosts
- ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx
- ath9k: Fix use-after-free Write in ath9k_htc_rx_msg
- ath9x: Fix stack-out-of-bounds Write in ath9k_hif_usb_rx_cb
- ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb
- Smack: slab-out-of-bounds in vsscanf
- mm/slub: fix a memory leak in sysfs_slab_add()
- fat: don't allow to mount if the FAT length == 0
- can: kvaser_usb: kvaser_usb_leaf: Fix some info-leaks to USB devices
- spi: dw: Zero DMA Tx and Rx configurations on stack
- Bluetooth: Add SCO fallback for invalid LMP parameters error
- kgdb: Prevent infinite recursive entries to the debugger
- spi: dw: Enable interrupts in accordance with DMA xfer mode
- clocksource: dw_apb_timer_of: Fix missing clockevent timers
- btrfs: do not ignore error from btrfs_next_leaf() when inserting checksums
- ARM: 8978/1: mm: make act_mm() respect THREAD_SIZE
- net: vmxnet3: fix possible buffer overflow caused by bad DMA value in
  vmxnet3_get_rss()
- staging: android: ion: use vmap instead of vm_map_ram
- e1000: Distribute switch variables for initialization
- media: dvb: return -EREMOTEIO on i2c transfer failure.
- MIPS: Make sparse_init() using top-down allocation
- netfilter: nft_nat: return EOPNOTSUPP if type or flags are not supported
- lib/mpi: Fix 64-bit MIPS build with Clang
- net: lpc-enet: fix error return code in lpc_mii_init()
- net: allwinner: Fix use correct return type for ndo_start_xmit()
- powerpc/spufs: fix copy_to_user while atomic
- mips: cm: Fix an invalid error code of INTVN_*_ERR
- kgdb: Fix spurious true from in_dbg_master()
- md: don't flush workqueue unconditionally in md_open
- mwifiex: Fix memory corruption in dump_station
- mips: Add udelay lpj numbers adjustment
- x86/mm: Stop printing BRK addresses
- m68k: mac: Don't call via_flush_cache() on Mac IIfx
- macvlan: Skip loopback packets in RX handler
- PCI: Don't disable decoding when mmio_always_on is set
- MIPS: Fix IRQ tracing when call handle_fpe() and handle_msa_fpe()
- ixgbe: fix signed-integer-overflow warning
- spi: dw: Return any value retrieved from the dma_transfer callback
- cpuidle: Fix three reference count leaks
- ima: Fix ima digest hash table key calculation
- ext4: fix EXT_MAX_EXTENT/INDEX to check for zeroed eh_max
- Btrfs: fix unreplayable log after snapshot delete + parent dir fsync
- btrfs: send: emit file capabilities after chow

[Kernel-packages] [Bug 1882955] Re: LXD 4.2 broken on linux-kvm due to missing VLAN filtering

This bug was fixed in the package linux-kvm - 4.4.0-1077.84

---
linux-kvm (4.4.0-1077.84) xenial; urgency=medium

  * xenial/linux-kvm: 4.4.0-1077.84 -proposed tracker (LP: #1885506)

  * LXD 4.2 broken on linux-kvm due to missing VLAN filtering (LP: #1882955)
- [Config] VLAN_8021Q=m && BRIDGE_VLAN_FILTERING=y

  [ Ubuntu: 4.4.0-186.216 ]

  * xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514)
  * Xenial update: v4.4.228 upstream stable release (LP: #1884564)
- ipv6: fix IPV6_ADDRFORM operation logic
- vxlan: Avoid infinite loop when suppressing NS messages with invalid 
options
- scsi: return correct blkprep status code in case scsi_init_io() fails.
- net: phy: marvell: Limit 88m1101 autoneg errata to 88E1145 as well.
- pwm: fsl-ftm: Use flat regmap cache
- ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
- sched/fair: Don't NUMA balance for kthreads
- ath9k_htc: Silence undersized packet warnings
- x86_64: Fix jiffies ODR violation
- x86/speculation: Prevent rogue cross-process SSBD shutdown
- x86/reboot/quirks: Add MacBook6,1 reboot quirk
- efi/efivars: Add missing kobject_put() in sysfs entry creation error path
- ALSA: es1688: Add the missed snd_card_free()
- ALSA: usb-audio: Fix inconsistent card PM state after resume
- ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile()
- ACPI: PM: Avoid using power resources if there are none for D0
- cgroup, blkcg: Prepare some symbols for module and !CONFIG_CGROUP usages
- nilfs2: fix null pointer dereference at nilfs_segctor_do_construct()
- spi: bcm2835aux: Fix controller unregister order
- ALSA: pcm: disallow linking stream to itself
- x86/speculation: Change misspelled STIPB to STIBP
- x86/speculation: Add support for STIBP always-on preferred mode
- x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced
  IBRS.
- x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
- spi: dw: fix possible race condition
- spi: dw: Fix controller unregister order
- spi: No need to assign dummy value in spi_unregister_controller()
- spi: Fix controller unregister order
- spi: pxa2xx: Fix controller unregister order
- spi: bcm2835: Fix controller unregister order
- ovl: initialize error in ovl_copy_xattr
- proc: Use new_inode not new_inode_pseudo
- video: fbdev: w100fb: Fix a potential double free.
- KVM: nSVM: leave ASID aside in copy_vmcb_control_area
- KVM: nVMX: Consult only the "basic" exit reason when routing nested exit
- KVM: arm64: Make vcpu_cp1x() work on Big Endian hosts
- ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx
- ath9k: Fix use-after-free Write in ath9k_htc_rx_msg
- ath9x: Fix stack-out-of-bounds Write in ath9k_hif_usb_rx_cb
- ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb
- Smack: slab-out-of-bounds in vsscanf
- mm/slub: fix a memory leak in sysfs_slab_add()
- fat: don't allow to mount if the FAT length == 0
- can: kvaser_usb: kvaser_usb_leaf: Fix some info-leaks to USB devices
- spi: dw: Zero DMA Tx and Rx configurations on stack
- Bluetooth: Add SCO fallback for invalid LMP parameters error
- kgdb: Prevent infinite recursive entries to the debugger
- spi: dw: Enable interrupts in accordance with DMA xfer mode
- clocksource: dw_apb_timer_of: Fix missing clockevent timers
- btrfs: do not ignore error from btrfs_next_leaf() when inserting checksums
- ARM: 8978/1: mm: make act_mm() respect THREAD_SIZE
- net: vmxnet3: fix possible buffer overflow caused by bad DMA value in
  vmxnet3_get_rss()
- staging: android: ion: use vmap instead of vm_map_ram
- e1000: Distribute switch variables for initialization
- media: dvb: return -EREMOTEIO on i2c transfer failure.
- MIPS: Make sparse_init() using top-down allocation
- netfilter: nft_nat: return EOPNOTSUPP if type or flags are not supported
- lib/mpi: Fix 64-bit MIPS build with Clang
- net: lpc-enet: fix error return code in lpc_mii_init()
- net: allwinner: Fix use correct return type for ndo_start_xmit()
- powerpc/spufs: fix copy_to_user while atomic
- mips: cm: Fix an invalid error code of INTVN_*_ERR
- kgdb: Fix spurious true from in_dbg_master()
- md: don't flush workqueue unconditionally in md_open
- mwifiex: Fix memory corruption in dump_station
- mips: Add udelay lpj numbers adjustment
- x86/mm: Stop printing BRK addresses
- m68k: mac: Don't call via_flush_cache() on Mac IIfx
- macvlan: Skip loopback packets in RX handler
- PCI: Don't disable decoding when mmio_always_on is set
- MIPS: Fix IRQ tracing when call handle_fpe() and handle_msa_fpe()
- ixgbe: fix signed-integer-overflow warning
- spi: dw: Return any value retrieved from the dma_transfer callback
- cpuidle: Fix three reference count leaks
-

[Kernel-packages] [Bug 1882478] Re: smpboot: don't call topology_sane() when Sub-NUMA-Clustering is enabled

This bug was fixed in the package linux - 4.4.0-186.216

---
linux (4.4.0-186.216) xenial; urgency=medium

  * xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514)

  * Xenial update: v4.4.228 upstream stable release (LP: #1884564)
- ipv6: fix IPV6_ADDRFORM operation logic
- vxlan: Avoid infinite loop when suppressing NS messages with invalid 
options
- scsi: return correct blkprep status code in case scsi_init_io() fails.
- net: phy: marvell: Limit 88m1101 autoneg errata to 88E1145 as well.
- pwm: fsl-ftm: Use flat regmap cache
- ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
- sched/fair: Don't NUMA balance for kthreads
- ath9k_htc: Silence undersized packet warnings
- x86_64: Fix jiffies ODR violation
- x86/speculation: Prevent rogue cross-process SSBD shutdown
- x86/reboot/quirks: Add MacBook6,1 reboot quirk
- efi/efivars: Add missing kobject_put() in sysfs entry creation error path
- ALSA: es1688: Add the missed snd_card_free()
- ALSA: usb-audio: Fix inconsistent card PM state after resume
- ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile()
- ACPI: PM: Avoid using power resources if there are none for D0
- cgroup, blkcg: Prepare some symbols for module and !CONFIG_CGROUP usages
- nilfs2: fix null pointer dereference at nilfs_segctor_do_construct()
- spi: bcm2835aux: Fix controller unregister order
- ALSA: pcm: disallow linking stream to itself
- x86/speculation: Change misspelled STIPB to STIBP
- x86/speculation: Add support for STIBP always-on preferred mode
- x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced
  IBRS.
- x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
- spi: dw: fix possible race condition
- spi: dw: Fix controller unregister order
- spi: No need to assign dummy value in spi_unregister_controller()
- spi: Fix controller unregister order
- spi: pxa2xx: Fix controller unregister order
- spi: bcm2835: Fix controller unregister order
- ovl: initialize error in ovl_copy_xattr
- proc: Use new_inode not new_inode_pseudo
- video: fbdev: w100fb: Fix a potential double free.
- KVM: nSVM: leave ASID aside in copy_vmcb_control_area
- KVM: nVMX: Consult only the "basic" exit reason when routing nested exit
- KVM: arm64: Make vcpu_cp1x() work on Big Endian hosts
- ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx
- ath9k: Fix use-after-free Write in ath9k_htc_rx_msg
- ath9x: Fix stack-out-of-bounds Write in ath9k_hif_usb_rx_cb
- ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb
- Smack: slab-out-of-bounds in vsscanf
- mm/slub: fix a memory leak in sysfs_slab_add()
- fat: don't allow to mount if the FAT length == 0
- can: kvaser_usb: kvaser_usb_leaf: Fix some info-leaks to USB devices
- spi: dw: Zero DMA Tx and Rx configurations on stack
- Bluetooth: Add SCO fallback for invalid LMP parameters error
- kgdb: Prevent infinite recursive entries to the debugger
- spi: dw: Enable interrupts in accordance with DMA xfer mode
- clocksource: dw_apb_timer_of: Fix missing clockevent timers
- btrfs: do not ignore error from btrfs_next_leaf() when inserting checksums
- ARM: 8978/1: mm: make act_mm() respect THREAD_SIZE
- net: vmxnet3: fix possible buffer overflow caused by bad DMA value in
  vmxnet3_get_rss()
- staging: android: ion: use vmap instead of vm_map_ram
- e1000: Distribute switch variables for initialization
- media: dvb: return -EREMOTEIO on i2c transfer failure.
- MIPS: Make sparse_init() using top-down allocation
- netfilter: nft_nat: return EOPNOTSUPP if type or flags are not supported
- lib/mpi: Fix 64-bit MIPS build with Clang
- net: lpc-enet: fix error return code in lpc_mii_init()
- net: allwinner: Fix use correct return type for ndo_start_xmit()
- powerpc/spufs: fix copy_to_user while atomic
- mips: cm: Fix an invalid error code of INTVN_*_ERR
- kgdb: Fix spurious true from in_dbg_master()
- md: don't flush workqueue unconditionally in md_open
- mwifiex: Fix memory corruption in dump_station
- mips: Add udelay lpj numbers adjustment
- x86/mm: Stop printing BRK addresses
- m68k: mac: Don't call via_flush_cache() on Mac IIfx
- macvlan: Skip loopback packets in RX handler
- PCI: Don't disable decoding when mmio_always_on is set
- MIPS: Fix IRQ tracing when call handle_fpe() and handle_msa_fpe()
- ixgbe: fix signed-integer-overflow warning
- spi: dw: Return any value retrieved from the dma_transfer callback
- cpuidle: Fix three reference count leaks
- ima: Fix ima digest hash table key calculation
- ext4: fix EXT_MAX_EXTENT/INDEX to check for zeroed eh_max
- Btrfs: fix unreplayable log after snapshot delete + parent dir fsync
- btrfs: send: emit file capabilities after chow

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

** Description changed:

Description:

When the speed of data with a usb disk device is too high, the probes
that check if the disk still exists is missed. This makes the disk to be
unmounted and is remounted with an other drive letter (/dev/sdX). If
this disk is the root ("/"), the computer hangs.

A usb SSD-disk (4 TB) connected to a USB port reproduce this bug easily.
This has never happened with a mechanical USB-drive.

Symptoms and how to reproduce:

1) (Disk mounted as root) Computer hangs. Only way to get started again
is a hard reset.

2) (Erasing disk, not mounted as root) If you erase a disk with dd ("dd
if=/dev/zero of=/dev/sdX"), the disk disappears from the mounted list
and reappears as an other drive letter. In my case the data is
redirected to /dev/null and the fans speed up. The apparent data
transfer speed is also increased. Usually this happens after about 45 to
60 minutes.

3) Fill RAM with programs and make sure the swap to this disk is used.

Bug found in:

$ uname -a
Linux pb-189b1884 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux

$ cat /proc/version_signature
Ubuntu 5.4.0-40.44-generic 5.4.44

- Bug not found in:
-
- Linux v4.15 (Ubuntu Bionic)
-
Hardware:

Tested with slower and faster computers. Tested directly connected to a
computer and via a hub. They all reproduce this bug.

Workaround:

None found.
- ---
+ ---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: user 6813 F pulseaudio
- /dev/snd/controlC0: user 6813 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: user 6813 F pulseaudio
+ /dev/snd/controlC0: user 6813 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
MachineType: ASUSTeK COMPUTER INC. GL503VM
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic
root=UUID=74545cc2-bc7e-11ea-9c1b-6b408850adf5 ro fsck.repair=yes
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
RelatedPackageVersions:
- linux-restricted-modules-5.4.0-40-generic N/A
- linux-backports-modules-5.4.0-40-generic N/A
- linux-firmware1.187.1
+ linux-restricted-modules-5.4.0-40-generic N/A
+ linux-backports-modules-5.4.0-40-generic N/A
+ linux-firmware1.187.1
Tags: focal
Uname: Linux 5.4.0-40-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: sudo vboxusers wireshark
WifiSyslog:
-
+
_MarkForUpload: False
dmi.bios.date: 04/29/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL503VM.314
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL503VM
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrGL503VM.314:bd04/29/2019:svnASUSTeKCOMPUTERINC.:pnGL503VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG
dmi.product.name: GL503VM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
high speed data to usb disk makes the kernel think that is has been
unmounted

Status in linux package in Ubuntu:
Confirmed

Bug description:
Description:

When the speed of data with a usb disk device is too high, the probes
that check if the disk still exists is missed. This makes the disk to
be unmounted and is remounted with an other drive letter (/dev/sdX).
If this disk is the root ("/"), the computer hangs.

A usb SSD-disk (4 TB) connected to a USB port reproduce this bug
easily. This has never happened with a mechanical USB-drive.

Symptoms and how to reproduce:

1) (Disk mounted as root) Computer hangs. Only way to get started
again is a hard reset.

2) (Erasing disk, not mounted as root) If you erase a disk with dd
("dd if=/dev/zero of=/dev/sdX"), the disk disappears from the mounted
list and reappears as an other drive letter. In my case the data is
redirected to /dev/null and the fans speed up. The apparent data
transfer speed is also increased. Usually this happens after about 45
to 60 minutes.

3) Fill RAM with programs and make sure the swap to this disk is used.

Bug found in:

$ uname -a
Linux pb-189b1884 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

This bug is present in all kernels tested from 4.15. Tested kernels are
at the end of this comment. The bug appears to depend heavily on the
speed of data. For example it works erasing a disk with all kernels with
dd if=/dev/urandom, but not with faster if=/dev/zero or if="openssl"
(exact syntax in attached test-script).


Linux 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux
Linux 5.0.1-050001-generic #201903100732 SMP Sun Mar 10 07:33:53 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
Linux 4.17.0-041700-generic #201806041953 SMP Mon Jun 4 19:55:25 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
Linux 4.16.18-041618-generic #201806252030 SMP Tue Jun 26 00:33:13 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
Linux 4.16.1-041601-generic #201804081334 SMP Sun Apr 8 13:35:48 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
Linux 4.15.18-041518-generic #201804190330 SMP Thu Apr 19 07:34:21 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
Linux 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux


** Attachment added: "test script"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886172/+attachment/5394463/+files/test.sh

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

Title:
  high speed data to usb disk makes the kernel think that is has been
  unmounted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:

  When the speed of data with a usb disk device is too high, the probes
  that check if the disk still exists is missed. This makes the disk to
  be unmounted and is remounted with an other drive letter (/dev/sdX).
  If this disk is the root ("/"), the computer hangs.

  A usb SSD-disk (4 TB) connected to a USB port reproduce this bug
  easily. This has never happened with a mechanical USB-drive.

  Symptoms and how to reproduce:

  1) (Disk mounted as root) Computer hangs. Only way to get started
  again is a hard reset.

  2) (Erasing disk, not mounted as root) If you erase a disk with dd
  ("dd if=/dev/zero of=/dev/sdX"), the disk disappears from the mounted
  list and reappears as an other drive letter. In my case the data is
  redirected to /dev/null and the fans speed up. The apparent data
  transfer speed is also increased. Usually this happens after about 45
  to 60 minutes.

  3) Fill RAM with programs and make sure the swap to this disk is used.

  Bug found in:

  $ uname -a
  Linux pb-189b1884 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  $ cat /proc/version_signature
  Ubuntu 5.4.0-40.44-generic 5.4.44

  Hardware:

  Tested with slower and faster computers. Tested directly connected to
  a computer and via a hub. They all reproduce this bug.

  Workaround:

  None found.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   6813 F pulseaudio
   /dev/snd/controlC0:  user   6813 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  MachineType: ASUSTeK COMPUTER INC. GL503VM
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=74545cc2-bc7e-11ea-9c1b-6b408850adf5 ro fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  Tags:  focal
  Uname: Linux 5.4.0-40-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:

  _MarkForUpload: False
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VM.314
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VM.314:bd04/29/2019:svnASUSTeKCOMPUTERINC.:pnGL503VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL503VM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

Log of udev event, when the bug happens.

# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[4837.212964] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0
 (bsg)
KERNEL[4837.218270] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg3
 (scsi_generic)
UDEV  [4837.218305] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0
 (scsi_disk)
KERNEL[4837.218325] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0
 (scsi_device)
UDEV  [4837.218349] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0
 (bsg)
KERNEL[4837.218364] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0
 (scsi_disk)
UDEV  [4837.218382] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0
 (scsi_device)
UDEV  [4837.219394] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg3
 (scsi_generic)
KERNEL[4846.579833] remove   /devices/virtual/bdi/8:48 (bdi)
KERNEL[4846.579956] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/block/sdd
 (block)
UDEV  [4846.580945] remove   /devices/virtual/bdi/8:48 (bdi)
UDEV  [4846.582743] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/block/sdd
 (block)
KERNEL[4846.824123] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0
 (scsi)
KERNEL[4846.824157] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0
 (scsi)
UDEV  [4846.826395] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0
 (scsi)
UDEV  [4846.827776] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0
 (scsi)
KERNEL[4846.848222] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0
 (scsi)
KERNEL[4846.848254] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/scsi_host/host5
 (scsi_host)
KERNEL[4846.848271] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5 (scsi)
KERNEL[4846.849427] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0 (usb)
KERNEL[4846.849470] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0 (usb)
UDEV  [4846.849777] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0
 (scsi)
KERNEL[4846.850038] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3 (usb)
KERNEL[4846.850071] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3 (usb)
UDEV  [4846.850475] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/scsi_host/host5
 (scsi_host)
UDEV  [4846.851513] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5 (scsi)
UDEV  [4846.852747] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0 (usb)
UDEV  [4846.854079] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0 (usb)
UDEV  [4846.855663] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3 (usb)
UDEV  [4846.863974] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3 (usb)
KERNEL[4849.780952] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3 (usb)
KERNEL[4849.781689] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0 (usb)
KERNEL[4849.783493] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host6 (scsi)
KERNEL[4849.783529] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host6/scsi_host/host6
 (scsi_host)
KERNEL[4849.783568] bind 
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0 (usb)
KERNEL[4849.783607] bind 
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3 (usb)
KERNEL[4849.786356] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host6/target6:0:0
 (scsi)
KERNEL[4849.786442] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host6/target6:0:0/6:0:0:0
 (scsi)
KERNEL[4849.786462] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host6/target6:0:0/6:0:0:0/scsi_disk/6:0:0:0
 (scsi_disk)
KERNEL[4849.786482] bind 
/devices/pci:00/000

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

Log of udev event, when the bug happens.

# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[25.226057] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
 (bsg)
KERNEL[25.232094] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
 (scsi_generic)
UDEV  [25.232131] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
 (scsi_generic)
KERNEL[25.232148] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
 (scsi_device)
UDEV  [25.232163] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
 (scsi_disk)
KERNEL[25.232176] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
 (scsi_disk)
UDEV  [25.234471] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
 (scsi_device)
UDEV  [25.237032] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
 (bsg)
KERNEL[257785.993301] remove   /devices/virtual/bdi/8:32 (bdi)
KERNEL[257785.994189] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
UDEV  [257785.994536] remove   /devices/virtual/bdi/8:32 (bdi)
UDEV  [257785.996938] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
KERNEL[257786.236165] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0
 (scsi)
KERNEL[257786.236196] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0
 (scsi)
UDEV  [257786.238169] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0
 (scsi)
UDEV  [257786.239825] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0
 (scsi)
KERNEL[257786.268117] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0
 (scsi)
KERNEL[257786.268147] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/scsi_host/host4
 (scsi_host)
KERNEL[257786.268166] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4
 (scsi)
KERNEL[257786.269320] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0
 (usb)
KERNEL[257786.269363] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0
 (usb)
KERNEL[257786.269829] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2 
(usb)
KERNEL[257786.269869] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2 
(usb)
UDEV  [257786.270012] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0
 (scsi)
UDEV  [257786.270648] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/scsi_host/host4
 (scsi_host)
UDEV  [257786.271546] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4
 (scsi)
UDEV  [257786.272602] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0
 (usb)
UDEV  [257786.273926] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0
 (usb)
UDEV  [257786.275670] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2 
(usb)
UDEV  [257786.284734] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2 
(usb)
KERNEL[257790.500838] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2 
(usb)
KERNEL[257790.501540] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0
 (usb)
KERNEL[257790.503117] add  
/devices/pci:00/:00:14.0/usb

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

Log of udev event, when the bug happens.

# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[255114.318220] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
 (bsg)
KERNEL[255114.320177] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
 (scsi_generic)
KERNEL[255114.320198] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
 (scsi_device)
KERNEL[255114.320209] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
 (scsi_disk)
UDEV  [255114.320619] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
 (scsi_generic)
UDEV  [255114.321338] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
 (bsg)
UDEV  [255114.321948] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
 (scsi_disk)
UDEV  [255114.325400] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
 (scsi_device)
KERNEL[255123.206586] remove   /devices/virtual/bdi/8:32 (bdi)
KERNEL[255123.206734] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
UDEV  [255123.207599] remove   /devices/virtual/bdi/8:32 (bdi)
UDEV  [255123.209019] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
KERNEL[255123.452120] unbind   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 
(scsi)
KERNEL[255123.452156] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 
(scsi)
UDEV  [255123.454017] unbind   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 
(scsi)
UDEV  [255123.455196] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 
(scsi)
KERNEL[255123.484123] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0 (scsi)
KERNEL[255123.484149] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/scsi_host/host4 
(scsi_host)
KERNEL[255123.484174] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4 (scsi)
KERNEL[255123.485174] unbind   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
KERNEL[255123.485215] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
UDEV  [255123.485449] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0 (scsi)
KERNEL[255123.485698] unbind   /devices/pci:00/:00:14.0/usb2/2-2 (usb)
KERNEL[255123.485730] remove   /devices/pci:00/:00:14.0/usb2/2-2 (usb)
UDEV  [255123.485994] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/scsi_host/host4 
(scsi_host)
UDEV  [255123.486906] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4 (scsi)
UDEV  [255123.487940] unbind   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
UDEV  [255123.489062] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
UDEV  [255123.490615] unbind   /devices/pci:00/:00:14.0/usb2/2-2 (usb)
UDEV  [255123.499129] remove   /devices/pci:00/:00:14.0/usb2/2-2 (usb)
KERNEL[255126.952713] add  /devices/pci:00/:00:14.0/usb2/2-2 (usb)
KERNEL[255126.953377] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
KERNEL[255126.955007] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5 (scsi)
KERNEL[255126.955119] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/scsi_host/host5 
(scsi_host)
KERNEL[255126.955164] bind 
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
KERNEL[255126.955209] bind /devices/pci:00/:00:14.0/usb2/2-2 (usb)
KERNEL[255126.958067] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0 (scsi)
KERNEL[255126.958155] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0 
(scsi)
KERNEL[255126.958177] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0
 (scsi_disk)
KERNEL[255126.958199] bind 
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0 
(scsi)
KERNEL[255126.958216] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0
 (scsi_device)
KERNEL[255126.958288] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg2
 (scsi_generic)
KERNEL[255126.958361] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0
 (bsg)
KERNEL[255126.959138] add  /devices/virtual/bdi/8:48 (bdi)
UDEV  [255126.960879] add  /devi

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

Log of udev event, when the bug happens.

# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[10316.148582] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
 (bsg)
KERNEL[10316.148718] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
 (scsi_generic)
KERNEL[10316.148737] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
 (scsi_device)
KERNEL[10316.148810] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
 (scsi_disk)
UDEV  [10316.150795] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
 (scsi_generic)
UDEV  [10316.151259] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
 (bsg)
UDEV  [10316.153358] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
 (scsi_disk)
UDEV  [10316.153443] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
 (scsi_device)
KERNEL[10325.527284] remove   /devices/virtual/bdi/8:32 (bdi)
KERNEL[10325.527425] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
UDEV  [10325.528344] remove   /devices/virtual/bdi/8:32 (bdi)
UDEV  [10325.529371] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
KERNEL[10325.772119] unbind   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 
(scsi)
KERNEL[10325.772152] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 
(scsi)
UDEV  [10325.774112] unbind   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 
(scsi)
UDEV  [10325.775045] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 
(scsi)
KERNEL[10325.796104] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0 (scsi)
KERNEL[10325.796133] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/scsi_host/host4 
(scsi_host)
KERNEL[10325.796152] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4 (scsi)
KERNEL[10325.796751] unbind   /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 
(usb)
KERNEL[10325.796785] remove   /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 
(usb)
KERNEL[10325.797247] unbind   /devices/pci:00/:00:14.0/usb2/2-2 (usb)
KERNEL[10325.797286] remove   /devices/pci:00/:00:14.0/usb2/2-2 (usb)
UDEV  [10325.797543] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0 (scsi)
UDEV  [10325.798531] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/scsi_host/host4 
(scsi_host)
UDEV  [10325.799470] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4 (scsi)
UDEV  [10325.800764] unbind   /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 
(usb)
UDEV  [10325.801790] remove   /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 
(usb)
UDEV  [10325.803192] unbind   /devices/pci:00/:00:14.0/usb2/2-2 (usb)
UDEV  [10325.822894] remove   /devices/pci:00/:00:14.0/usb2/2-2 (usb)
KERNEL[10328.672752] add  /devices/pci:00/:00:14.0/usb2/2-2 (usb)
KERNEL[10328.674111] add  /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 
(usb)
KERNEL[10328.675645] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5 (scsi)
KERNEL[10328.675684] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/scsi_host/host5 
(scsi_host)
KERNEL[10328.675725] bind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 
(usb)
KERNEL[10328.675770] bind /devices/pci:00/:00:14.0/usb2/2-2 (usb)
KERNEL[10328.676723] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0 (scsi)
KERNEL[10328.677293] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0 
(scsi)
KERNEL[10328.677315] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0
 (scsi_disk)
KERNEL[10328.677338] bind 
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0 
(scsi)
KERNEL[10328.677357] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0
 (scsi_device)
KERNEL[10328.677379] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg2
 (scsi_generic)
KERNEL[10328.677400] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0
 (bsg)
KERNEL[10328.677975] add  /devices/virtual/bdi/8:48 (bdi)
UDEV  [10328.679302] add  /devices/virtual/bdi/8:48 (bdi)
UDEV  [10328.70207

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

Log of udev event, when the bug happens.

# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[255114.318220] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
 (bsg)
KERNEL[255114.320177] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
 (scsi_generic)
KERNEL[255114.320198] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
 (scsi_device)
KERNEL[255114.320209] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
 (scsi_disk)
UDEV  [255114.320619] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
 (scsi_generic)
UDEV  [255114.321338] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
 (bsg)
UDEV  [255114.321948] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
 (scsi_disk)
UDEV  [255114.325400] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
 (scsi_device)
KERNEL[255123.206586] remove   /devices/virtual/bdi/8:32 (bdi)
KERNEL[255123.206734] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
UDEV  [255123.207599] remove   /devices/virtual/bdi/8:32 (bdi)
UDEV  [255123.209019] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
KERNEL[255123.452120] unbind   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 
(scsi)
KERNEL[255123.452156] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 
(scsi)
UDEV  [255123.454017] unbind   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 
(scsi)
UDEV  [255123.455196] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 
(scsi)
KERNEL[255123.484123] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0 (scsi)
KERNEL[255123.484149] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/scsi_host/host4 
(scsi_host)
KERNEL[255123.484174] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4 (scsi)
KERNEL[255123.485174] unbind   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
KERNEL[255123.485215] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
UDEV  [255123.485449] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0 (scsi)
KERNEL[255123.485698] unbind   /devices/pci:00/:00:14.0/usb2/2-2 (usb)
KERNEL[255123.485730] remove   /devices/pci:00/:00:14.0/usb2/2-2 (usb)
UDEV  [255123.485994] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/scsi_host/host4 
(scsi_host)
UDEV  [255123.486906] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4 (scsi)
UDEV  [255123.487940] unbind   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
UDEV  [255123.489062] remove   
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
UDEV  [255123.490615] unbind   /devices/pci:00/:00:14.0/usb2/2-2 (usb)
UDEV  [255123.499129] remove   /devices/pci:00/:00:14.0/usb2/2-2 (usb)
KERNEL[255126.952713] add  /devices/pci:00/:00:14.0/usb2/2-2 (usb)
KERNEL[255126.953377] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
KERNEL[255126.955007] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5 (scsi)
KERNEL[255126.955119] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/scsi_host/host5 
(scsi_host)
KERNEL[255126.955164] bind 
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
KERNEL[255126.955209] bind /devices/pci:00/:00:14.0/usb2/2-2 (usb)
KERNEL[255126.958067] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0 (scsi)
KERNEL[255126.958155] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0 
(scsi)
KERNEL[255126.958177] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0
 (scsi_disk)
KERNEL[255126.958199] bind 
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0 
(scsi)
KERNEL[255126.958216] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0
 (scsi_device)
KERNEL[255126.958288] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg2
 (scsi_generic)
KERNEL[255126.958361] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0
 (bsg)
KERNEL[255126.959138] add  /devices/virtual/bdi/8:48 (bdi)
UDEV  [255126.960879] add  /devi

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

Log of udev event, when the bug happens.

# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[259892.454355] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
 (bsg)
KERNEL[259892.454422] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
 (scsi_generic)
KERNEL[259892.454441] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
 (scsi_device)
KERNEL[259892.454539] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
 (scsi_disk)
UDEV  [259892.457118] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
 (bsg)
UDEV  [259892.458521] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
 (scsi_generic)
UDEV  [259892.458829] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
 (scsi_disk)
UDEV  [259892.460499] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
 (scsi_device)
KERNEL[259900.048051] remove   /devices/virtual/bdi/8:32 (bdi)
KERNEL[259900.048161] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
UDEV  [259900.049035] remove   /devices/virtual/bdi/8:32 (bdi)
UDEV  [259900.050572] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
KERNEL[259900.304129] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0
 (scsi)
KERNEL[259900.304164] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0
 (scsi)
UDEV  [259900.307449] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0
 (scsi)
UDEV  [259900.308340] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0
 (scsi)
KERNEL[259900.328191] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0
 (scsi)
KERNEL[259900.328218] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/scsi_host/host4
 (scsi_host)
KERNEL[259900.328236] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4
 (scsi)
UDEV  [259900.329867] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0
 (scsi)
UDEV  [259900.330569] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/scsi_host/host4
 (scsi_host)
UDEV  [259900.332031] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4
 (scsi)
KERNEL[259900.347337] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0
 (usb)
UDEV  [259900.349761] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0
 (usb)
KERNEL[259900.468456] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5
 (scsi)
KERNEL[259900.468492] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/scsi_host/host5
 (scsi_host)
KERNEL[259900.468523] bind 
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0
 (usb)
KERNEL[259900.469340] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0
 (scsi)
KERNEL[259900.469396] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0
 (scsi)
KERNEL[259900.469435] add  
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0
 (scsi_disk)
KERNEL[259900.469457] bind 
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

Log of udev event, when the bug happens.

# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[258304.180050] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd1
 (block)
KERNEL[258304.180140] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd2
 (block)
KERNEL[258304.180259] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd3
 (block)
KERNEL[258304.180306] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd4
 (block)
KERNEL[258304.185959] change   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd
 (block)
UDEV  [258304.194320] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd1
 (block)
UDEV  [258304.197464] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd2
 (block)
UDEV  [258304.201738] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd3
 (block)
UDEV  [258304.206277] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd4
 (block)
UDEV  [258304.231082] change   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd
 (block)
KERNEL[258909.512337] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0
 (bsg)
KERNEL[258909.512751] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg2
 (scsi_generic)
KERNEL[258909.512770] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0
 (scsi_device)
KERNEL[258909.512849] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0
 (scsi_disk)
UDEV  [258909.514595] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0
 (bsg)
UDEV  [258909.523015] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg2
 (scsi_generic)
UDEV  [258909.523043] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0
 (scsi_device)
UDEV  [258909.525664] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0
 (scsi_disk)
KERNEL[258916.896444] remove   /devices/virtual/bdi/8:48 (bdi)
KERNEL[258916.896543] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd
 (block)
UDEV  [258916.898043] remove   /devices/virtual/bdi/8:48 (bdi)
UDEV  [258916.899241] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd
 (block)
KERNEL[258917.140120] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0
 (scsi)
KERNEL[258917.140157] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0
 (scsi)
UDEV  [258917.142078] unbind   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0
 (scsi)
UDEV  [258917.143694] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0
 (scsi)
KERNEL[258917.168225] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0
 (scsi)
KERNEL[258917.168252] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/scsi_host/host5
 (scsi_host)
KERNEL[258917.168270] remove   
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5
 (scsi)
KERNEL[258917.168796]

[Kernel-packages] [Bug 1888326] [NEW] Bluetooth device not found QCA9565

2020-07-20 Thread Frédéric Annequin

Public bug reported:

Hello,
I run Ubuntu 20.04 LTS on my Acer Aspire E5-573G and Ubuntu can't found my 
bluetooth device.

I have a QCNFA335 (QCA9565) which can normally support both wifi and
bluetooth

I can use both wifi and bluetooth on windows 10.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 20 20:24:58 2020
InstallationDate: Installed on 2020-07-17 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: bnep btusb bluetooth
MachineType: Acer Aspire E5-573G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=eec36b7b-bbf9-463c-80a6-6ec698a4d655 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/16/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.37
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: ZORO_BH
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: BDW
dmi.product.name: Aspire E5-573G
dmi.product.sku: Aspire E5-573G_098A_1_37
dmi.product.version: V3.72
dmi.sys.vendor: Acer
hciconfig:

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


** Tags: amd64 apport-bug focal

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

Title:
  Bluetooth device not found QCA9565

Status in bluez package in Ubuntu:
  New

Bug description:
  Hello,
  I run Ubuntu 20.04 LTS on my Acer Aspire E5-573G and Ubuntu can't found my 
bluetooth device.

  I have a QCNFA335 (QCA9565) which can normally support both wifi and
  bluetooth

  I can use both wifi and bluetooth on windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 20:24:58 2020
  InstallationDate: Installed on 2020-07-17 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: bnep btusb bluetooth
  MachineType: Acer Aspire E5-573G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=eec36b7b-bbf9-463c-80a6-6ec698a4d655 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-573G
  dmi.product.sku: Aspire E5-573G_098A_1_37
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer
  hciconfig:

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

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

[Kernel-packages] [Bug 1886247] Re: Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found

2020-07-20 Thread AaronMa

For 20.04 focal 5.4 kernel. it should be in this SRU cycle released on
10 Aug.

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

Title:
  Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  SRU justification:
  [Impact]
  New realtek wifi card ID found on ThinkCentre.
  No driver is loaded to support it.

  [Fix]
  This wifi card is very similar as 0xc822 in rtw88.

  [Test]
  Verified on hardware, link status is OK, iperf test result is good.

  [Regression Potential]
  Low.
  Add new ID to supported driver.
  Test on hw, double confirmed by LP bugs.
  This patch is backported from original link due to the 5.8-rc1 driver
  file path changed, no function changed.

  Maintainer had merged:
  
https://github.com/lwfinger/rtlwifi_new/commit/b76b895a90f1168c5223849562fd6e1196b2c351
  This git repo is moving by maintainer, not availible by now.
  
=

  
  01:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device c82f

  Looking for a working solution on a fresh install (USB BOOT) of
  Ubuntu. A work-around helped, for a while, but I would really like to
  disconnect my Wifi Dongel and use my brand new laptop!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1277 F pulseaudio
   /dev/snd/pcmC0D0c:   christian   1277 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  4 07:58:06 2020
  InstallationDate: Installed on 2020-06-28 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81W8
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=f610713f-73ad-468c-8a69-9a47b385acab ro quiet splash i8042.nopnp=1 
pci=nocrs vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  StagingDrivers: r8712u
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32866 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL:
  dmi.product.family: IdeaPad S145-15IIL
  dmi.product.name: 81W8
  dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL
  dmi.product.version: Lenovo IdeaPad S145-15IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1879334] Re: Desktop Activities - first key typed is repeated 21 times

2020-07-20 Thread buchs

Nice! You don’t do anything on this and then expire it. Good job! So
much for stating that you want people to report bugs. What a waste of
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/1879334

Title:
  Desktop Activities - first key typed is repeated 21 times

Status in linux package in Ubuntu:
  Expired

Bug description:
  Pretty simple scenario. I often press the Super key and then start
  typing a command name. Within the last two weeks (I stay up to date on
  any updates to 18.04), when I press the first key it gets repeated a
  total of 21 times. It is only the first key. If I press backspace or
  Ctl-u to erase the entries, then there is no problem. It seems that
  this problem went from being intermittent to being constant now.

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

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

[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO

2020-07-20 Thread Daniel van Vugt

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

Title:
KDE GUI freeze on high disk IO

Status in linux package in Ubuntu:
Invalid

Bug description:
I've got massive problems with GUI on my PC.

The attached logs are from the following setting:
- high disk load (f3write)
- kernel 4.15.0-1050-oem (the only 4x kernel available in eoan)
- no swap available

These are the parameters (disk load, kernel, swap) I am fiddling with
to find out the cause, see below.

I just installed the following kernels from kernel-ppa:
5.3.10-050310-generic
5.4.0-050400rc6-generic
5.4.0-997-generic (drm-intel-next)
Now I am waiting for the freeze to occur again.

The hassle started with the following scenario, repeated often:
- high disk load
- PC becomes laggy
- soon dies/freezes

The longer I waited, the deeper the lockdown went. but I don't know the exact
details.
The first cause I found was kswapd running amok and take the system with it.
Workaround: add swap space.

Another workaround is to completely remove swap. Let's see what
happens, if kswapd goes amok again.

I am not sure as how these problems are related.

I did extensive hardware check like
- memtest86 newest version, no "may be vulnerable to high frequency row
hammering"
- smart

do you suggest any burn in test suites?

thanks

[Kernel-packages] [Bug 1887724] Re: [amdgpu] Xorg freeze

2020-07-20 Thread Daniel van Vugt

It might help to disable the built-in wifi. Try doing it in the BIOS. If
that doesn't work then you can disable the kernel driver of the built-in
wifi by adding a line:

  blacklist ath10k_pci

to /etc/modprobe.d/blacklist.conf and then reboot.

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

Title:
  [amdgpu] Xorg freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random freezing-- different freezing every time. I switched GUIs from
  Gnome to Cinnamon and it seems to freeze less, but still averaging
  about once a day. I cannot reproduce, is random.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Wed Jul 15 15:44:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Dell Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [1028:0884]
  InstallationDate: Installed on 2020-06-04 (40 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 7375
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=0ed970bf-fd17-4242-8a3e-5c1224ed5b72 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 02YPPF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.5.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd07/09/2018:svnDellInc.:pnInspiron7375:pvr1.5.0:rvnDellInc.:rn02YPPF:rvrA00:cvnDellInc.:ct10:cvr1.5.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7375
  dmi.product.sku: 0884
  dmi.product.version: 1.5.0
  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 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/1887724/+subscriptions

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

[Kernel-packages] [Bug 1879299] Re: enable disable fan test in ubuntu_fan_smoke_test failed on E/F s390x LPAR / zVM ( docker still configured, unable to disable fan)