[Kernel-packages] [Bug 1897853] Re: [regression] gnome-shell stutters noticeably with kernel 5.8.0-19, but not 5.8.0-18

[Daniel van Vugt]

** Description changed:

  gnome-shell stutters noticeably with kernel 5.8.0-19
  
- I've now tested three recent kernels:
+ I've now tested four recent kernels:
  
+ 5.8.0-20: stutters
  5.8.0-19: stutters
  5.8.0-18: smooth
  5.8.0-16: smooth
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-19-generic 5.8.0-19.20
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 13:52:38 2020
  InstallationDate: Installed on 2020-07-16 (76 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint
-  Bus 001 Device 003: ID 045e:0823 Microsoft Corp. Classic IntelliMouse
-  Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
-  Bus 001 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 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint
+  Bus 001 Device 003: ID 045e:0823 Microsoft Corp. Classic IntelliMouse
+  Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 10M7CTO1WW
  ProcEnviron:
-  LANGUAGE=en_AU:en
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_AU.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_AU:en
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_AU.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-19-generic 
root=UUID=21e70a66-4d0f-49fc-b42c-668fc1594d91 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.8.0-19-generic N/A
-  linux-backports-modules-5.8.0-19-generic  N/A
-  linux-firmware1.190
+  linux-restricted-modules-5.8.0-19-generic N/A
+  linux-backports-modules-5.8.0-19-generic  N/A
+  linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.release: 0.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:br0.47:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO

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

Title:
  [regression] gnome-shell stutters noticeably with kernel 5.8.0-19, but
  not 5.8.0-18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell stutters noticeably with kernel 5.8.0-19

  I've now tested four recent kernels:

  5.8.0-20: stutters
  5.8.0-19: stutters
  5.8.0-18: smooth
  5.8.0-16: smooth

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-19-generic 5.8.0-19.20
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 13:52:38 2020
  InstallationDate: Installed on 2020-07-16 (76 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint
   Bus 001 Device 003: ID 045e:0823 Microsoft Corp. Classic IntelliMouse
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 10M7CTO1WW
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-19-generic 
root=UUID=21e70a66-4d0f-49fc-b42c-668fc1594d91 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1805806] Re: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64

[Kelsey Margarete Skunberg]

This error is populating on Focal 'aws : 5.4.0-1026.26 : amd64' on
c5.large and ' aws : 5.4.0-1026.26 : arm64' on a1.2xlarge

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

Title:
  test_maps in ubuntu_bpf failed with "Failed sockmap unexpected
  timeout" on D ARM64

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix

Bug description:
  This issue can be found on 2 different ARM64 node, TunderX Cavium node
  "starmie" and Moonshot "ms10-34-mcdivittB0-kernel"

  Running test_maps bpf test..
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Failed sockmap unexpected timeout

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  package linux-image-5.4.0-47-generic (not installed) failed to
  install/upgrade: installed linux-image-5.4.0-47-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i keep getting this error after updating the kernel
  using 
  sudo apt-get dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-47-generic (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shashikanth   1945 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 10:12:31 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32
  ErrorMessage: installed linux-image-5.4.0-47-generic package pre-removal 
script subprocess returned error exit status 1
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:5301 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 3480
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=1cde599c-4502-4a38-9400-2802117f7ca7 ro mem_sleep_default=deep 
usbcore.quirks=2386:3119:k quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.2, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-5.4.0-47-generic (not installed) failed to 
install/upgrade: installed linux-image-5.4.0-47-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0H40C6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd05/30/2019:svnDellInc.:pnVostro3480:pvr:rvnDellInc.:rn0H40C6:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3480
  dmi.product.sku: 08C8
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1898001] [NEW] package linux-image-5.4.0-47-generic (not installed) failed to install/upgrade: installed linux-image-5.4.0-47-generic package pre-removal script subprocess retur

[shashikanth]

Public bug reported:

i keep getting this error after updating the kernel
using 
sudo apt-get dist-upgrade

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-47-generic (not installed)
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  shashikanth   1945 F pulseaudio
CasperMD5CheckResult: skip
Date: Wed Sep 30 10:12:31 2020
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32
ErrorMessage: installed linux-image-5.4.0-47-generic package pre-removal script 
subprocess returned error exit status 1
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 002: ID 27c6:5301 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 3480
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=1cde599c-4502-4a38-9400-2802117f7ca7 ro mem_sleep_default=deep 
usbcore.quirks=2386:3119:k quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.2, python-is-python2, 2.7.17-4
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-image-5.4.0-47-generic (not installed) failed to 
install/upgrade: installed linux-image-5.4.0-47-generic package pre-removal 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.name: 0H40C6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd05/30/2019:svnDellInc.:pnVostro3480:pvr:rvnDellInc.:rn0H40C6:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 3480
dmi.product.sku: 08C8
dmi.sys.vendor: Dell Inc.

** Affects: 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 linux in Ubuntu.
https://bugs.launchpad.net/bugs/1898001

Title:
  package linux-image-5.4.0-47-generic (not installed) failed to
  install/upgrade: installed linux-image-5.4.0-47-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  i keep getting this error after updating the kernel
  using 
  sudo apt-get dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-47-generic (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shashikanth   1945 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 10:12:31 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32
  ErrorMessage: installed linux-image-5.4.0-47-generic package pre-removal 
script subprocess returned error exit status 1
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:5301 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 3480
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=1cde599c-4502-4a38-9400-2802117f7ca7 ro mem_sleep_default=deep 
usbcore.quirks=2386:3119:k quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.2, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc N/A
  

[Kernel-packages] [Bug 1897983] Re: cpuset_inherit in controllers from ubuntu_ltp failed on B-AWS-4.15

[Kelsey Margarete Skunberg]

Spotted this on 4.15.0-1083.87, though the current version is
4.15.0-1084.88. All LTP tests failed on the current version and I'm re-
running the tests. Will report back verifying if this is still failing
on 4.15.0-1084.88.

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

Title:
   cpuset_inherit in controllers from ubuntu_ltp failed on B-AWS-4.15

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Bionic:
  New

Bug description:
  99224.09/10 19:12:56 DEBUG| utils:0153| [stdout] startup='Thu Sep 10 
19:09:04 2020'
  99225.09/10 19:12:56 DEBUG| utils:0153| [stdout] 
/opt/ltp/testcases/bin/cpuset_inherit_testset.sh: 109: 
/opt/ltp/testcases/bin/cpuset_inherit_testset.sh: let: not found
  99226.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 1 
TPASS: cpus: Inherited information is right!
  99227.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 3 
TPASS: cpus: Inherited information is right!
  99228.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 5 
TPASS: cpus: Inherited information is right!
  99229.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 7 
TPASS: cpus: Inherited information is right!
  99230.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 9 
TPASS: cpus: Inherited information is right!
  99231.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 11 
TFAIL: cpus: Test result - 0-7 Expected string - "0-"
  99232.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 13 
TPASS: mems: Inherited information is right!
  99233.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 15 
TPASS: mems: Inherited information is right!
  99234.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 17 
TPASS: mems: Inherited information is right!
  99235.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 19 
TPASS: mems: Inherited information is right!
  99236.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 21 
TPASS: mems: Inherited information is right!
  99237.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 23 
TPASS: mems: Inherited information is right!
  99238.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 25 
TPASS: cpu_exclusive: Inherited information is right!
  99239.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 27 
TPASS: cpu_exclusive: Inherited information is right!
  99240.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 29 
TPASS: mem_exclusive: Inherited information is right!
  99241.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 31 
TPASS: mem_exclusive: Inherited information is right!
  99242.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 33 
TPASS: mem_hardwall: Inherited information is right!
  99243.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 35 
TPASS: mem_hardwall: Inherited information is right!
  99244.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 37 
TPASS: memory_migrate: Inherited information is right!
  99245.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 39 
TPASS: memory_migrate: Inherited information is right!
  99246.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 41 
TPASS: memory_spread_page: Inherited information is right!
  99247.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 43 
TPASS: memory_spread_page: Inherited information is right!
  99248.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 45 
TPASS: memory_spread_slab: Inherited information is right!
  99249.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 47 
TPASS: memory_spread_slab: Inherited information is right!
  99250.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 49 
TPASS: sched_load_balance: Inherited information is right!
  99251.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 51 
TPASS: sched_load_balance: Inherited information is right!
  99252.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 53 
TPASS: sched_relax_domain_level: Inherited information is right!
  99253.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 55 
TPASS: sched_relax_domain_level: Inherited information is right!
  99254.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 57 
TPASS: sched_relax_domain_level: Inherited information is right!
  99255.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 59 
TPASS: sched_relax_domain_level: Inherited information is right!
  99256.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 61 
TPASS: sched_relax_domain_level: Inherited information is right!
  99257.09/10 

[Kernel-packages] [Bug 1868519] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite()

[Daniel van Vugt]

This bug is closed so please open new bugs from now on.

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

Title:
  [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from
  xf86MoveCursor() from miPointerMoveNoEvent() from
  miPointerSetPosition() from positionSprite()

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nvidia-graphics-drivers.  This problem was most recently seen with package 
version 2:1.20.7-2ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5a9ed7ea32a1d20e4222dbe8712aa9640b42a73c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Kernel-packages] [Bug 1871306] Re: No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3

[Hui Wang]

@Gabirele,

Looks there is no difference between Debian 1.2.3 and testing 1.2.2, so
should I submit the testing 1.2.2 to ubuntu package?

And for the problem you met, maybe it is a kernel issue or a pulseaudio
issue, you could file bugs against to linux kernel and pulseaudio.
Because we don't have hardware, we couldn't reproduce the issue you
mentioned.

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

Title:
  No sound from internal card chtmax98090 - missing UCM2 files in alsa-
  ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3

Status in alsa-ucm-conf package in Ubuntu:
  Confirmed

Bug description:
  Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script)  - 
Kubuntu Focal minimal fresh installation.
  The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in 
alsamixer and it's not muted.
  I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case 
config files: no success.
  I tried and unmute speakers left and right in alsamixer: no success.

  I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the
  same issue.

  I'm running on the same rig Debian Bullseye, kernel 5.4: sound card
  output and input are both working perfectly - I noticed that in
  Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH
  (the HDMI card), while in Debian I find Pulseaudio.

  
  I attach the alsa-info.sh output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.17
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Tue Apr  7 08:55:46 2020
  InstallationDate: Installed on 2020-04-04 (2 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gabriel3937 F pulseaudio
   /dev/snd/controlC0:  gabriel3937 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-04 (3 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam
   Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Quawks
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/17/2020
  dmi.bios.vendor: coreboot
  dmi.bios.version: MrChromebox-4.11.2
  dmi.board.name: Quawks
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr:
  dmi.product.name: Quawks
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions

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

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

[Diego González]

Still happening on 2020-10-01 (since at least 2019-10-01) on multiple
computers.

Quoting what bug description says:

"Kernel should be fixed to correctly parse lz4 compressed initrds, or at
least lower the warning, to not be user visible as an error."

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

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

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

[Kernel-packages] [Bug 1897983] [NEW] cpuset_inherit in controllers from ubuntu_ltp failed on B-AWS-4.15

[Kelsey Margarete Skunberg]

Public bug reported:

99224.  09/10 19:12:56 DEBUG| utils:0153| [stdout] startup='Thu Sep 10 19:09:04 
2020'
99225.  09/10 19:12:56 DEBUG| utils:0153| [stdout] 
/opt/ltp/testcases/bin/cpuset_inherit_testset.sh: 109: 
/opt/ltp/testcases/bin/cpuset_inherit_testset.sh: let: not found
99226.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 1 TPASS: 
cpus: Inherited information is right!
99227.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 3 TPASS: 
cpus: Inherited information is right!
99228.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 5 TPASS: 
cpus: Inherited information is right!
99229.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 7 TPASS: 
cpus: Inherited information is right!
99230.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 9 TPASS: 
cpus: Inherited information is right!
99231.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 11 TFAIL: 
cpus: Test result - 0-7 Expected string - "0-"
99232.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 13 TPASS: 
mems: Inherited information is right!
99233.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 15 TPASS: 
mems: Inherited information is right!
99234.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 17 TPASS: 
mems: Inherited information is right!
99235.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 19 TPASS: 
mems: Inherited information is right!
99236.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 21 TPASS: 
mems: Inherited information is right!
99237.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 23 TPASS: 
mems: Inherited information is right!
99238.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 25 TPASS: 
cpu_exclusive: Inherited information is right!
99239.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 27 TPASS: 
cpu_exclusive: Inherited information is right!
99240.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 29 TPASS: 
mem_exclusive: Inherited information is right!
99241.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 31 TPASS: 
mem_exclusive: Inherited information is right!
99242.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 33 TPASS: 
mem_hardwall: Inherited information is right!
99243.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 35 TPASS: 
mem_hardwall: Inherited information is right!
99244.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 37 TPASS: 
memory_migrate: Inherited information is right!
99245.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 39 TPASS: 
memory_migrate: Inherited information is right!
99246.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 41 TPASS: 
memory_spread_page: Inherited information is right!
99247.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 43 TPASS: 
memory_spread_page: Inherited information is right!
99248.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 45 TPASS: 
memory_spread_slab: Inherited information is right!
99249.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 47 TPASS: 
memory_spread_slab: Inherited information is right!
99250.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 49 TPASS: 
sched_load_balance: Inherited information is right!
99251.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 51 TPASS: 
sched_load_balance: Inherited information is right!
99252.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 53 TPASS: 
sched_relax_domain_level: Inherited information is right!
99253.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 55 TPASS: 
sched_relax_domain_level: Inherited information is right!
99254.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 57 TPASS: 
sched_relax_domain_level: Inherited information is right!
99255.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 59 TPASS: 
sched_relax_domain_level: Inherited information is right!
99256.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 61 TPASS: 
sched_relax_domain_level: Inherited information is right!
99257.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 63 TPASS: 
sched_relax_domain_level: Inherited information is right!
99258.  09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 65 TPASS: 
sched_relax_domain_level: Inherited information is right!
99259.  09/10 19:12:56 DEBUG| utils:0153| [stdout] tag=cpuset_inherit 
stime=1599764944 dur=2 exit=exited stat=1 core=no cu=68 cs=45

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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

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


** Tags: 4.15 amd64 bionic cpuset-inherit kqa-blocker sru-20200921

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

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

[Kernel-packages] [Bug 1897977] [NEW] Bionic update: upstream stable patchset 2020-09-30

[Kamal Mostafa]

Public bug reported:

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

Ported from the following upstream stable releases:
v4.14.199, v4.19.146
   v4.19.147,

   from git://git.kernel.org/

ARM: dts: socfpga: fix register entry for timer3 on Arria10
RDMA/rxe: Fix memleak in rxe_mem_init_user
RDMA/rxe: Drop pointless checks in rxe_init_ports
scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA
RDMA/core: Fix reported speed and width
mmc: sdhci-msm: Add retries when all tuning phases are found valid
ARM: dts: BCM5301X: Fixed QSPI compatible string
arm64: dts: ns2: Fixed QSPI compatible string
ARC: HSDK: wireup perf irq
dmaengine: acpi: Put the CSRT table after using it
drivers/net/wan/lapbether: Added needed_tailroom
NFC: st95hf: Fix memleak in st95hf_in_send_cmd
firestream: Fix memleak in fs_open
ALSA: hda: Fix 2 channel swapping for Tegra
drivers/net/wan/lapbether: Set network_header before transmitting
xfs: initialize the shortform attr header padding entry
irqchip/eznps: Fix build error for !ARC700 builds
drivers/net/wan/hdlc_cisco: Add hard_header_len
ARC: [plat-hsdk]: Switch ethernet phy-mode to rgmii-id
cpufreq: intel_pstate: Refuse to turn off with HWP enabled
ALSA: hda: fix a runtime pm issue in SOF when integrated GPU is disabled
gcov: Disable gcov build with GCC 10
iio: adc: mcp3422: fix locking scope
iio: adc: mcp3422: fix locking on error path
iio: adc: ti-ads1015: fix conversion when CONFIG_PM is not set
iio:light:ltr501 Fix timestamp alignment issue.
iio:accel:bmc150-accel: Fix timestamp alignment and prevent data leak.
iio:adc:ti-adc084s021 Fix alignment and data leak issues.
iio:adc:ina2xx Fix timestamp alignment issue.
iio:adc:max1118 Fix alignment of timestamp and data leak issues
iio:adc:ti-adc081c Fix alignment and data leak issues
iio:magnetometer:ak8975 Fix alignment and data leak issues.
iio:light:max44000 Fix timestamp alignment and prevent data leak.
iio:chemical:ccs811: Fix timestamp alignment and prevent data leak.
iio: accel: kxsd9: Fix alignment of local buffer.
iio:accel:mma7455: Fix timestamp alignment and prevent data leak.
iio:accel:mma8452: Fix timestamp alignment and prevent data leak.
staging: wlan-ng: fix out of bounds read in prism2sta_probe_usb()
btrfs: require only sector size alignment for parent eb bytenr
btrfs: fix lockdep splat in add_missing_dev
btrfs: fix wrong address when faulting in pages in the search ioctl
regulator: push allocation in set_consumer_device_supply() out of lock
scsi: target: iscsi: Fix data digest calculation
scsi: target: iscsi: Fix hang in iscsit_access_np() when getting 
tpg->np_login_sem
rbd: require global CAP_SYS_ADMIN for mapping and unmapping
RDMA/rxe: Fix the parent sysfs read when the interface has 15 chars
fbcon: remove soft scrollback code
fbcon: remove now unusued 'softback_lines' cursor() argument
vgacon: remove software scrollback support
UBUNTU: [Config] updateconfigs for VGACON_SOFT_SCROLLBACK
KVM: VMX: Don't freeze guest when event delivery causes an APIC-access exit
ARM: dts: vfxxx: Add syscon compatible with OCOTP
video: fbdev: fix OOB read in vga_8planes_imageblit()
staging: greybus: audio: fix uninitialized value issue
usb: core: fix slab-out-of-bounds Read in read_descriptors
USB: serial: ftdi_sio: add IDs for Xsens Mti USB converter
USB: serial: option: support dynamic Quectel USB compositions
USB: serial: option: add support for SIM7070/SIM7080/SIM7090 modules
usb: Fix out of sync data toggle if a configured device is reconfigured
usb: typec: ucsi: acpi: Check the _DEP dependencies
gcov: add support for GCC 10.1
gfs2: initialize transaction tr_ailX_lists earlier
net: handle the return value of pskb_carve_frag_list() correctly
hv_netvsc: Remove "unlikely" from netvsc_select_queue
NFSv4.1 handle ERR_DELAY error reclaiming locking state on delegation recall
scsi: pm8001: Fix memleak in pm8001_exec_internal_task_abort
scsi: libfc: Fix for double free()
scsi: lpfc: Fix FLOGI/PLOGI receive race condition in pt2pt discovery
spi: spi-loopback-test: Fix out-of-bounds read
SUNRPC: stop printk reading past end of string
rapidio: Replace 'select' DMAENGINES 'with depends on'
nvme-fc: cancel async events before freeing event struct
f2fs: fix indefinite loop scanning for free nid
i2c: algo: pca: Reapply i2c bus settings after reset
spi: Fix memory leak on splited transfers
KVM: MIPS: Change the definition of kvm type
clk: rockchip: Fix initialization of mux_pll_src_4plls_p
Drivers: hv: vmbus: Add timeout to 

[Kernel-packages] [Bug 1897975] Re: package linux-oracle-tools-5.4.0-1025 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.4.0-1025', which is also in package

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-oracle-tools-5.4.0-1025 (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/lib/libcpupower.so.5.4.0-1025', which is also in package linux-
  aws-tools-5.4.0-1025 5.4.0-1025.25

Status in linux-oracle package in Ubuntu:
  New

Bug description:
  I don't know any more sorry. John

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-oracle-tools-5.4.0-1025 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Sep 29 11:19:45 2020
  DuplicateSignature:
   package:linux-oracle-tools-5.4.0-1025:(not installed)
   Unpacking linux-gcp-tools-5.4.0-1025 (5.4.0-1025.25) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-kLnVNn/04-linux-gcp-tools-5.4.0-1025_5.4.0-1025.25_amd64.deb
 (--unpack):
trying to overwrite '/usr/lib/libcpupower.so.5.4.0-1025', which is also in 
package linux-aws-tools-5.4.0-1025 5.4.0-1025.25
  ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.5.4.0-1025', which 
is also in package linux-aws-tools-5.4.0-1025 5.4.0-1025.25
  InstallationDate: Installed on 2020-09-21 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: linux-oracle
  Title: package linux-oracle-tools-5.4.0-1025 (not installed) failed to 
install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.4.0-1025', 
which is also in package linux-aws-tools-5.4.0-1025 5.4.0-1025.25
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1897975] [NEW] package linux-oracle-tools-5.4.0-1025 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.4.0-1025', which is also in packag

[John Oliver Clarke]

Public bug reported:

I don't know any more sorry. John

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-oracle-tools-5.4.0-1025 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Sep 29 11:19:45 2020
DuplicateSignature:
 package:linux-oracle-tools-5.4.0-1025:(not installed)
 Unpacking linux-gcp-tools-5.4.0-1025 (5.4.0-1025.25) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-kLnVNn/04-linux-gcp-tools-5.4.0-1025_5.4.0-1025.25_amd64.deb
 (--unpack):
  trying to overwrite '/usr/lib/libcpupower.so.5.4.0-1025', which is also in 
package linux-aws-tools-5.4.0-1025 5.4.0-1025.25
ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.5.4.0-1025', which 
is also in package linux-aws-tools-5.4.0-1025 5.4.0-1025.25
InstallationDate: Installed on 2020-09-21 (9 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: linux-oracle
Title: package linux-oracle-tools-5.4.0-1025 (not installed) failed to 
install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.4.0-1025', 
which is also in package linux-aws-tools-5.4.0-1025 5.4.0-1025.25
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal package-conflict

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

Title:
  package linux-oracle-tools-5.4.0-1025 (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/lib/libcpupower.so.5.4.0-1025', which is also in package linux-
  aws-tools-5.4.0-1025 5.4.0-1025.25

Status in linux-oracle package in Ubuntu:
  New

Bug description:
  I don't know any more sorry. John

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-oracle-tools-5.4.0-1025 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Sep 29 11:19:45 2020
  DuplicateSignature:
   package:linux-oracle-tools-5.4.0-1025:(not installed)
   Unpacking linux-gcp-tools-5.4.0-1025 (5.4.0-1025.25) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-kLnVNn/04-linux-gcp-tools-5.4.0-1025_5.4.0-1025.25_amd64.deb
 (--unpack):
trying to overwrite '/usr/lib/libcpupower.so.5.4.0-1025', which is also in 
package linux-aws-tools-5.4.0-1025 5.4.0-1025.25
  ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.5.4.0-1025', which 
is also in package linux-aws-tools-5.4.0-1025 5.4.0-1025.25
  InstallationDate: Installed on 2020-09-21 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: linux-oracle
  Title: package linux-oracle-tools-5.4.0-1025 (not installed) failed to 
install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.4.0-1025', 
which is also in package linux-aws-tools-5.4.0-1025 5.4.0-1025.25
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1897963] Re: Kernel null pointer dereference - Lenovo Thinkpad USB-C Dock Gen2

[Igor Campos]

the kernel crashes, I am unable to capture the event, only the dmesg
running is able to show what happens. there is already a fix.

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

Title:
  Kernel null pointer dereference - Lenovo Thinkpad USB-C Dock Gen2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Basically a null pointer dereference was happening while using a
  lenovo usb-c dock. The issue has been addressed upstream with commit:
  
https://github.com/torvalds/linux/commit/386e15a650447f53de3d2d8819ce9393f31650a4

  Apparently the dock kept sending altmode information repeatedly, and
  the kernel did not expect this to happen, a check was added to make
  sure it only observes the amount of altmodes limited by the standard.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 30 15:40:24 2020
  InstallationDate: Installed on 2020-09-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1892546] Re: Novalink (mkvterm command failure)

[Patricia Domingues]

Thierry, thanks. Did you check it on Bionic ? (comment #15)

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

Title:
  Novalink (mkvterm command failure)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  SRU Justification:

  [Impact]
  * drmgr command is failing while trying to open console for IBMi on PowerVM 
LPAR

  [Fix]
  * 63ffcbdad738 "tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()"

  [Test Case]
  * Create a VM from PowerVC on a Novalink managed host. 
  * Unmanage and manage the VM, this problem gets reproduced.
  * grep the logs for "drmgr"

  
  [Regression Potential]
  The regression can be considered as very low, since:
  * limited to the IBM Hypervisor Virtual Console Server.
  * patched kernel where shared and successfully tested by IBM.
  * the worse case, if the cleanup is broken a new opened connection might 
break.

  [Other]
  * The patch got upstream accepted.

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

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

[Kernel-packages] [Bug 1897955] Re: [5.8] broadcom driver binaries do not contain a driver string

[Jeff Lane]

Talked to upstream and discovered this is by design on their end:

This is not a bug. The versions of all network drivers in the kernel
tree were removed around March 2020. The arbitrary version of each
driver was considered too arbitrary and not meaningful, so they were all
removed:

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/ethernet/broadcom/bnxt?id=e3c0a635103d6a0a49ca6b5ddf945a11693e45b2

Each driver is part of the kernel and so the kernel version should be
relied on instead.

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

Title:
  [5.8] broadcom driver binaries do not contain a driver string

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Brodcom network drivers in 5.8 do not have a version string (even
  though it is present in the source code) modinfo cannot return a
  driver version.

  In a vm I installed 20.04.1 and then installed 
linux-image-generic-hwe-20.04-edge from the Groovy archive to get the 20.04.2 
HWE image (5.8) since you said 20.10 fails.
  So this gives me the 20.04 userspace with a working modinfo, and a 5.8 kernel 
which you've noted has failed drivers.

  I am able to easily recreate this issue:
  bladernr@vm1:$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu 20.04.1 LTS
  Release:        20.04
  Codename:       focal
  bladernr@vm1:/$ uname -r
  5.4.0-47-generic
  bladernr@vm1:$ for x in b44 bnx2 bnx2x bnxt_en cnic genet tg3; do echo "$x: 
`modinfo -F version $x`"; done
  b44: 2.0
  bnx2: 2.2.6
  bnx2x: 1.713.36-0
  bnxt_en: 1.10.0
  cnic: 2.5.22
  genet:
  tg3: 3.137

  Next, I installed the 5.8 kernel on 20.04.1 and tried the same
  experiment (did it this way to ensure I was using the same userspace
  and version of kmod that does work with 5.4):

  bladernr@vm1:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu 20.04.1 LTS
  Release:        20.04
  Codename:       focal
  bladernr@vm1:~$ uname -r
  5.8.0-20-generic
  bladernr@vm1:~$ for x in b44 bnx2 bnx2x bnxt_en cnic genet tg3; do echo "$x: 
`modinfo -F version $x`"; done
  b44:
  bnx2:
  bnx2x:
  bnxt_en:
  cnic: 2.5.22
  genet:
  tg3:

  Note that now none of the driver versions are returned when probing
  with modinfo.

  Just grabbing one at random, bnxt_en, notice that the test strings in the 
compiled driver for 5.4 include a version string, which is absent in the 5.8 
version:
  bladernr@vm1:/lib/modules$ strings 
5.4.0-47-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko |grep 
version
  Unable to allocate memory for pkg version, length = %u
  version=1.10.0
  srcversion=D3F4FDC7C50D2098ACBC3DC
  __UNIQUE_ID_srcversion98
  version_printed.93504
  version
  __UNIQUE_ID_version368
  bladernr@vm1:/lib/modules$ strings 
5.8.0-20-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko |grep 
version
  Unable to allocate memory for pkg version, length = %u
  srcversion=CC39AC9960F1BCF24B4FB48
  __UNIQUE_ID_srcversion148
  devlink_info_version_fixed_put
  devlink_info_version_running_put

  And looking at the source for bnxt_hst.h in both Focal (5.4) and
  Groovy (5.8), the version strings appear to exist:

  bladernr@galactica:~/development/kernels/ubuntu$ grep VERSION 
focal/drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h
  #define HWRM_VERSION_MAJOR 1
  #define HWRM_VERSION_MINOR 10
  #define HWRM_VERSION_UPDATE 0
  #define HWRM_VERSION_RSVD 100
  #define HWRM_VERSION_STR "1.10.0.100"
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_MASK      0xf0UL
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_SFT       4
  bladernr@galactica:~/development/kernels/ubuntu$ grep VERSION 
groovy/drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h

          #define HWRM_TF_VERSION_GET                       0x2bdUL
  #define HWRM_VERSION_MAJOR 1
  #define HWRM_VERSION_MINOR 10
  #define HWRM_VERSION_UPDATE 1
  #define HWRM_VERSION_RSVD 33
  #define HWRM_VERSION_STR "1.10.1.33"
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_MASK      0xf0UL
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_SFT       4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-20-generic 5.8.0-20.21
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-20-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  

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

[Ubuntu Kernel Bot]

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

apport-collect 1897963

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

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

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

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

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

Title:
  Kernel null pointer dereference - Lenovo Thinkpad USB-C Dock Gen2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Basically a null pointer dereference was happening while using a
  lenovo usb-c dock. The issue has been addressed upstream with commit:
  
https://github.com/torvalds/linux/commit/386e15a650447f53de3d2d8819ce9393f31650a4

  Apparently the dock kept sending altmode information repeatedly, and
  the kernel did not expect this to happen, a check was added to make
  sure it only observes the amount of altmodes limited by the standard.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 30 15:40:24 2020
  InstallationDate: Installed on 2020-09-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1769792] Re: Keyboard and Touchpad do not work after suspend/resume

[voku]

Smme here. FUJITSU Notebook LIFEBOOK E Serie running Ubuntu 18.04.5
LTS

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

Title:
  Keyboard and Touchpad do not work after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop is a Toshiba Satellite C850D with updated 18.04 installed.
  When resuming from suspend, I have no keyboard and touchpad.
  dmesg shows "i8042: Can't reactivate KBD port"

  This looks like a recurring problem, and is just like these:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1142118

  Here's the dmesg output from before and after suspending.
  https://paste.ubuntu.com/p/rsFX9Yw7Xh/

  This post also talks about this bit failing for a lot of people!
  http://lightrush.ndoytchev.com/random-1/i8042quirkoptions

  Some of the function keys work, such as changing the screen
  brightness, but the key (fn+F5) does not turn the touchpad back on. I
  have not yet tried any of the suggested options, as results have been
  mixed, but I will.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  7 22:01:26 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1897963] Re: Kernel null pointer dereference - Lenovo Thinkpad USB-C Dock Gen2

[Ubuntu Foundations Team Bug Bot]

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

Title:
  Kernel null pointer dereference - Lenovo Thinkpad USB-C Dock Gen2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Basically a null pointer dereference was happening while using a
  lenovo usb-c dock. The issue has been addressed upstream with commit:
  
https://github.com/torvalds/linux/commit/386e15a650447f53de3d2d8819ce9393f31650a4

  Apparently the dock kept sending altmode information repeatedly, and
  the kernel did not expect this to happen, a check was added to make
  sure it only observes the amount of altmodes limited by the standard.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 30 15:40:24 2020
  InstallationDate: Installed on 2020-09-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1897963] Re: Kernel null pointer dereference - Lenovo Thinkpad USB-C Dock Gen2

[Igor Campos]

** Package changed: linux-signed-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/1897963

Title:
  Kernel null pointer dereference - Lenovo Thinkpad USB-C Dock Gen2

Status in linux package in Ubuntu:
  New

Bug description:
  Basically a null pointer dereference was happening while using a
  lenovo usb-c dock. The issue has been addressed upstream with commit:
  
https://github.com/torvalds/linux/commit/386e15a650447f53de3d2d8819ce9393f31650a4

  Apparently the dock kept sending altmode information repeatedly, and
  the kernel did not expect this to happen, a check was added to make
  sure it only observes the amount of altmodes limited by the standard.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 30 15:40:24 2020
  InstallationDate: Installed on 2020-09-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1897963] [NEW] Kernel null pointer dereference - Lenovo Thinkpad USB-C Dock Gen2

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Basically a null pointer dereference was happening while using a lenovo
usb-c dock. The issue has been addressed upstream with commit:
https://github.com/torvalds/linux/commit/386e15a650447f53de3d2d8819ce9393f31650a4

Apparently the dock kept sending altmode information repeatedly, and the
kernel did not expect this to happen, a check was added to make sure it
only observes the amount of altmodes limited by the standard.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52~18.04.1
ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 30 15:40:24 2020
InstallationDate: Installed on 2020-09-30 (0 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
SourcePackage: linux-signed-hwe-5.4
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic kernel-bug
-- 
Kernel null pointer dereference - Lenovo Thinkpad USB-C Dock Gen2
https://bugs.launchpad.net/bugs/1897963
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 1897955] Re: [5.8] broadcom driver binaries do not contain a driver string

[Jeff Lane]

What bugs could this possibly be missing?  I filed this using apport in
the first place, and apport collected all the logs the hooks told it to,
didn't it?


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

Title:
  [5.8] broadcom driver binaries do not contain a driver string

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Brodcom network drivers in 5.8 do not have a version string (even
  though it is present in the source code) modinfo cannot return a
  driver version.

  In a vm I installed 20.04.1 and then installed 
linux-image-generic-hwe-20.04-edge from the Groovy archive to get the 20.04.2 
HWE image (5.8) since you said 20.10 fails.
  So this gives me the 20.04 userspace with a working modinfo, and a 5.8 kernel 
which you've noted has failed drivers.

  I am able to easily recreate this issue:
  bladernr@vm1:$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu 20.04.1 LTS
  Release:        20.04
  Codename:       focal
  bladernr@vm1:/$ uname -r
  5.4.0-47-generic
  bladernr@vm1:$ for x in b44 bnx2 bnx2x bnxt_en cnic genet tg3; do echo "$x: 
`modinfo -F version $x`"; done
  b44: 2.0
  bnx2: 2.2.6
  bnx2x: 1.713.36-0
  bnxt_en: 1.10.0
  cnic: 2.5.22
  genet:
  tg3: 3.137

  Next, I installed the 5.8 kernel on 20.04.1 and tried the same
  experiment (did it this way to ensure I was using the same userspace
  and version of kmod that does work with 5.4):

  bladernr@vm1:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu 20.04.1 LTS
  Release:        20.04
  Codename:       focal
  bladernr@vm1:~$ uname -r
  5.8.0-20-generic
  bladernr@vm1:~$ for x in b44 bnx2 bnx2x bnxt_en cnic genet tg3; do echo "$x: 
`modinfo -F version $x`"; done
  b44:
  bnx2:
  bnx2x:
  bnxt_en:
  cnic: 2.5.22
  genet:
  tg3:

  Note that now none of the driver versions are returned when probing
  with modinfo.

  Just grabbing one at random, bnxt_en, notice that the test strings in the 
compiled driver for 5.4 include a version string, which is absent in the 5.8 
version:
  bladernr@vm1:/lib/modules$ strings 
5.4.0-47-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko |grep 
version
  Unable to allocate memory for pkg version, length = %u
  version=1.10.0
  srcversion=D3F4FDC7C50D2098ACBC3DC
  __UNIQUE_ID_srcversion98
  version_printed.93504
  version
  __UNIQUE_ID_version368
  bladernr@vm1:/lib/modules$ strings 
5.8.0-20-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko |grep 
version
  Unable to allocate memory for pkg version, length = %u
  srcversion=CC39AC9960F1BCF24B4FB48
  __UNIQUE_ID_srcversion148
  devlink_info_version_fixed_put
  devlink_info_version_running_put

  And looking at the source for bnxt_hst.h in both Focal (5.4) and
  Groovy (5.8), the version strings appear to exist:

  bladernr@galactica:~/development/kernels/ubuntu$ grep VERSION 
focal/drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h
  #define HWRM_VERSION_MAJOR 1
  #define HWRM_VERSION_MINOR 10
  #define HWRM_VERSION_UPDATE 0
  #define HWRM_VERSION_RSVD 100
  #define HWRM_VERSION_STR "1.10.0.100"
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_MASK      0xf0UL
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_SFT       4
  bladernr@galactica:~/development/kernels/ubuntu$ grep VERSION 
groovy/drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h

          #define HWRM_TF_VERSION_GET                       0x2bdUL
  #define HWRM_VERSION_MAJOR 1
  #define HWRM_VERSION_MINOR 10
  #define HWRM_VERSION_UPDATE 1
  #define HWRM_VERSION_RSVD 33
  #define HWRM_VERSION_STR "1.10.1.33"
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_MASK      0xf0UL
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_SFT       4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-20-generic 5.8.0-20.21
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-20-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: pass
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Wed Sep 30 18:42:14 2020
  InstallationDate: 

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

[bugproxy]

--- Comment From thierry.fa...@fr.ibm.com 2020-09-30 15:03 EDT---
I loaded the kernel on both focal and groovy and connecting/disconnecting from 
the console seems to work. Is there anything I can do to validate it is working 
? thanks

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

Title:
  Novalink (mkvterm command failure)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  SRU Justification:

  [Impact]
  * drmgr command is failing while trying to open console for IBMi on PowerVM 
LPAR

  [Fix]
  * 63ffcbdad738 "tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()"

  [Test Case]
  * Create a VM from PowerVC on a Novalink managed host. 
  * Unmanage and manage the VM, this problem gets reproduced.
  * grep the logs for "drmgr"

  
  [Regression Potential]
  The regression can be considered as very low, since:
  * limited to the IBM Hypervisor Virtual Console Server.
  * patched kernel where shared and successfully tested by IBM.
  * the worse case, if the cleanup is broken a new opened connection might 
break.

  [Other]
  * The patch got upstream accepted.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1897955

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

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

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

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

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

Title:
  [5.8] broadcom driver binaries do not contain a driver string

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brodcom network drivers in 5.8 do not have a version string (even
  though it is present in the source code) modinfo cannot return a
  driver version.

  In a vm I installed 20.04.1 and then installed 
linux-image-generic-hwe-20.04-edge from the Groovy archive to get the 20.04.2 
HWE image (5.8) since you said 20.10 fails.
  So this gives me the 20.04 userspace with a working modinfo, and a 5.8 kernel 
which you've noted has failed drivers.

  I am able to easily recreate this issue:
  bladernr@vm1:$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu 20.04.1 LTS
  Release:        20.04
  Codename:       focal
  bladernr@vm1:/$ uname -r
  5.4.0-47-generic
  bladernr@vm1:$ for x in b44 bnx2 bnx2x bnxt_en cnic genet tg3; do echo "$x: 
`modinfo -F version $x`"; done
  b44: 2.0
  bnx2: 2.2.6
  bnx2x: 1.713.36-0
  bnxt_en: 1.10.0
  cnic: 2.5.22
  genet:
  tg3: 3.137

  Next, I installed the 5.8 kernel on 20.04.1 and tried the same
  experiment (did it this way to ensure I was using the same userspace
  and version of kmod that does work with 5.4):

  bladernr@vm1:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu 20.04.1 LTS
  Release:        20.04
  Codename:       focal
  bladernr@vm1:~$ uname -r
  5.8.0-20-generic
  bladernr@vm1:~$ for x in b44 bnx2 bnx2x bnxt_en cnic genet tg3; do echo "$x: 
`modinfo -F version $x`"; done
  b44:
  bnx2:
  bnx2x:
  bnxt_en:
  cnic: 2.5.22
  genet:
  tg3:

  Note that now none of the driver versions are returned when probing
  with modinfo.

  Just grabbing one at random, bnxt_en, notice that the test strings in the 
compiled driver for 5.4 include a version string, which is absent in the 5.8 
version:
  bladernr@vm1:/lib/modules$ strings 
5.4.0-47-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko |grep 
version
  Unable to allocate memory for pkg version, length = %u
  version=1.10.0
  srcversion=D3F4FDC7C50D2098ACBC3DC
  __UNIQUE_ID_srcversion98
  version_printed.93504
  version
  __UNIQUE_ID_version368
  bladernr@vm1:/lib/modules$ strings 
5.8.0-20-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko |grep 
version
  Unable to allocate memory for pkg version, length = %u
  srcversion=CC39AC9960F1BCF24B4FB48
  __UNIQUE_ID_srcversion148
  devlink_info_version_fixed_put
  devlink_info_version_running_put

  And looking at the source for bnxt_hst.h in both Focal (5.4) and
  Groovy (5.8), the version strings appear to exist:

  bladernr@galactica:~/development/kernels/ubuntu$ grep VERSION 
focal/drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h
  #define HWRM_VERSION_MAJOR 1
  #define HWRM_VERSION_MINOR 10
  #define HWRM_VERSION_UPDATE 0
  #define HWRM_VERSION_RSVD 100
  #define HWRM_VERSION_STR "1.10.0.100"
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_MASK      0xf0UL
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_SFT       4
  bladernr@galactica:~/development/kernels/ubuntu$ grep VERSION 
groovy/drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h

          #define HWRM_TF_VERSION_GET                       0x2bdUL
  #define HWRM_VERSION_MAJOR 1
  #define HWRM_VERSION_MINOR 10
  #define HWRM_VERSION_UPDATE 1
  #define HWRM_VERSION_RSVD 33
  #define HWRM_VERSION_STR "1.10.1.33"
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_MASK      0xf0UL
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_SFT       4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-20-generic 5.8.0-20.21
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-20-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed 

[Kernel-packages] [Bug 1897955] Re: [5.8] broadcom driver binaries do not contain a driver string

[Jeff Lane]

for comparison, I checked drivers from Intel and they work:
bladernr@vm1:~$ uname -a
Linux vm1 5.8.0-20-generic #21-Ubuntu SMP Wed Sep 23 00:39:43 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux
bladernr@vm1:~$ for x in e1000 e1000e e100 fm10k i40e iavf ice igb igbvf igc 
ixgb; do echo "$x: `modinfo -F version $x`"; done
e1000: 7.3.21-k8-NAPI
e1000e: 3.2.6-k
e100: 3.5.24-k2-NAPI
fm10k: 0.27.1-k
i40e: 2.8.20-k
iavf: 3.2.3-k
ice: 0.8.2-k
igb: 5.6.0-k
igbvf: 2.4.0-k
igc: 0.0.1-k
ixgb: 1.0.135-k2-NAPI

Additionally, I also checked broadcom storage drivers and they DO return
version strings with the 5.8:

bladernr@vm1:~$ for x in be2iscsi bnx2fc bnx2i; do
> echo "$x: `modinfo -F version $x`"; done
be2iscsi: 11.4.0.1
bnx2fc: 2.12.13
bnx2i: 2.7.10.1

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

Title:
  [5.8] broadcom driver binaries do not contain a driver string

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brodcom network drivers in 5.8 do not have a version string (even
  though it is present in the source code) modinfo cannot return a
  driver version.

  In a vm I installed 20.04.1 and then installed 
linux-image-generic-hwe-20.04-edge from the Groovy archive to get the 20.04.2 
HWE image (5.8) since you said 20.10 fails.
  So this gives me the 20.04 userspace with a working modinfo, and a 5.8 kernel 
which you've noted has failed drivers.

  I am able to easily recreate this issue:
  bladernr@vm1:$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu 20.04.1 LTS
  Release:        20.04
  Codename:       focal
  bladernr@vm1:/$ uname -r
  5.4.0-47-generic
  bladernr@vm1:$ for x in b44 bnx2 bnx2x bnxt_en cnic genet tg3; do echo "$x: 
`modinfo -F version $x`"; done
  b44: 2.0
  bnx2: 2.2.6
  bnx2x: 1.713.36-0
  bnxt_en: 1.10.0
  cnic: 2.5.22
  genet:
  tg3: 3.137

  Next, I installed the 5.8 kernel on 20.04.1 and tried the same
  experiment (did it this way to ensure I was using the same userspace
  and version of kmod that does work with 5.4):

  bladernr@vm1:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu 20.04.1 LTS
  Release:        20.04
  Codename:       focal
  bladernr@vm1:~$ uname -r
  5.8.0-20-generic
  bladernr@vm1:~$ for x in b44 bnx2 bnx2x bnxt_en cnic genet tg3; do echo "$x: 
`modinfo -F version $x`"; done
  b44:
  bnx2:
  bnx2x:
  bnxt_en:
  cnic: 2.5.22
  genet:
  tg3:

  Note that now none of the driver versions are returned when probing
  with modinfo.

  Just grabbing one at random, bnxt_en, notice that the test strings in the 
compiled driver for 5.4 include a version string, which is absent in the 5.8 
version:
  bladernr@vm1:/lib/modules$ strings 
5.4.0-47-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko |grep 
version
  Unable to allocate memory for pkg version, length = %u
  version=1.10.0
  srcversion=D3F4FDC7C50D2098ACBC3DC
  __UNIQUE_ID_srcversion98
  version_printed.93504
  version
  __UNIQUE_ID_version368
  bladernr@vm1:/lib/modules$ strings 
5.8.0-20-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko |grep 
version
  Unable to allocate memory for pkg version, length = %u
  srcversion=CC39AC9960F1BCF24B4FB48
  __UNIQUE_ID_srcversion148
  devlink_info_version_fixed_put
  devlink_info_version_running_put

  And looking at the source for bnxt_hst.h in both Focal (5.4) and
  Groovy (5.8), the version strings appear to exist:

  bladernr@galactica:~/development/kernels/ubuntu$ grep VERSION 
focal/drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h
  #define HWRM_VERSION_MAJOR 1
  #define HWRM_VERSION_MINOR 10
  #define HWRM_VERSION_UPDATE 0
  #define HWRM_VERSION_RSVD 100
  #define HWRM_VERSION_STR "1.10.0.100"
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_MASK      0xf0UL
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_SFT       4
  bladernr@galactica:~/development/kernels/ubuntu$ grep VERSION 
groovy/drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h

          #define HWRM_TF_VERSION_GET                       0x2bdUL
  #define HWRM_VERSION_MAJOR 1
  #define HWRM_VERSION_MINOR 10
  #define HWRM_VERSION_UPDATE 1
  #define HWRM_VERSION_RSVD 33
  #define HWRM_VERSION_STR "1.10.1.33"
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_MASK      0xf0UL
          #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_SFT       4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-20-generic 5.8.0-20.21
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.8.0-20-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', 

[Kernel-packages] [Bug 1897955] [NEW] [5.8] broadcom driver binaries do not contain a driver string

[Jeff Lane]

Public bug reported:

Brodcom network drivers in 5.8 do not have a version string (even though
it is present in the source code) modinfo cannot return a driver
version.

In a vm I installed 20.04.1 and then installed 
linux-image-generic-hwe-20.04-edge from the Groovy archive to get the 20.04.2 
HWE image (5.8) since you said 20.10 fails.
So this gives me the 20.04 userspace with a working modinfo, and a 5.8 kernel 
which you've noted has failed drivers.

I am able to easily recreate this issue:
bladernr@vm1:$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.1 LTS
Release:        20.04
Codename:       focal
bladernr@vm1:/$ uname -r
5.4.0-47-generic
bladernr@vm1:$ for x in b44 bnx2 bnx2x bnxt_en cnic genet tg3; do echo "$x: 
`modinfo -F version $x`"; done
b44: 2.0
bnx2: 2.2.6
bnx2x: 1.713.36-0
bnxt_en: 1.10.0
cnic: 2.5.22
genet:
tg3: 3.137

Next, I installed the 5.8 kernel on 20.04.1 and tried the same
experiment (did it this way to ensure I was using the same userspace and
version of kmod that does work with 5.4):

bladernr@vm1:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.1 LTS
Release:        20.04
Codename:       focal
bladernr@vm1:~$ uname -r
5.8.0-20-generic
bladernr@vm1:~$ for x in b44 bnx2 bnx2x bnxt_en cnic genet tg3; do echo "$x: 
`modinfo -F version $x`"; done
b44:
bnx2:
bnx2x:
bnxt_en:
cnic: 2.5.22
genet:
tg3:

Note that now none of the driver versions are returned when probing with
modinfo.

Just grabbing one at random, bnxt_en, notice that the test strings in the 
compiled driver for 5.4 include a version string, which is absent in the 5.8 
version:
bladernr@vm1:/lib/modules$ strings 
5.4.0-47-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko |grep 
version
Unable to allocate memory for pkg version, length = %u
version=1.10.0
srcversion=D3F4FDC7C50D2098ACBC3DC
__UNIQUE_ID_srcversion98
version_printed.93504
version
__UNIQUE_ID_version368
bladernr@vm1:/lib/modules$ strings 
5.8.0-20-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko |grep 
version
Unable to allocate memory for pkg version, length = %u
srcversion=CC39AC9960F1BCF24B4FB48
__UNIQUE_ID_srcversion148
devlink_info_version_fixed_put
devlink_info_version_running_put

And looking at the source for bnxt_hst.h in both Focal (5.4) and Groovy
(5.8), the version strings appear to exist:

bladernr@galactica:~/development/kernels/ubuntu$ grep VERSION 
focal/drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h
#define HWRM_VERSION_MAJOR 1
#define HWRM_VERSION_MINOR 10
#define HWRM_VERSION_UPDATE 0
#define HWRM_VERSION_RSVD 100
#define HWRM_VERSION_STR "1.10.0.100"
        #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_MASK      0xf0UL
        #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_SFT       4
bladernr@galactica:~/development/kernels/ubuntu$ grep VERSION 
groovy/drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h

        #define HWRM_TF_VERSION_GET                       0x2bdUL
#define HWRM_VERSION_MAJOR 1
#define HWRM_VERSION_MINOR 10
#define HWRM_VERSION_UPDATE 1
#define HWRM_VERSION_RSVD 33
#define HWRM_VERSION_STR "1.10.1.33"
        #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_MASK      0xf0UL
        #define VXLAN_IPV4_HDR_VER_HLEN_VERSION_SFT       4

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-20-generic 5.8.0-20.21
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.8.0-20-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Wed Sep 30 18:42:14 2020
InstallationDate: Installed on 2020-09-15 (15 days ago)
InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
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, 

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

[bugproxy]

--- Comment From thierry.fa...@fr.ibm.com 2020-09-30 13:13 EDT---
I loaded the kernel on both focal and groovy and connecting/disconnecting from 
the console seems to work. Is there anything I can do to validate it is working 
? thanks

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

Title:
  Novalink (mkvterm command failure)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  SRU Justification:

  [Impact]
  * drmgr command is failing while trying to open console for IBMi on PowerVM 
LPAR

  [Fix]
  * 63ffcbdad738 "tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()"

  [Test Case]
  * Create a VM from PowerVC on a Novalink managed host. 
  * Unmanage and manage the VM, this problem gets reproduced.
  * grep the logs for "drmgr"

  
  [Regression Potential]
  The regression can be considered as very low, since:
  * limited to the IBM Hypervisor Virtual Console Server.
  * patched kernel where shared and successfully tested by IBM.
  * the worse case, if the cleanup is broken a new opened connection might 
break.

  [Other]
  * The patch got upstream accepted.

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

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

[Kernel-packages] [Bug 1848771] Re: Reboot after resume from suspend (deep)

[php4fan]

Now not only does my laptop reboot on resuming from suspend: it suddenly
RANDOMLY SHUTS DOWN while I'm using it.

Ubuntu people, please, give us an older non-broken version of the kernel
while this gets fixed upstream, because that is obviously going to take
a while.

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

Title:
  Reboot after resume from suspend (deep)

Status in linux package in Ubuntu:
  Incomplete
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes
  after resume from suspending. This is regardless the way of suspending
  (closing lid, selecting suspend from sddm, systemctl suspend).

  The journal shows:
  ferry@chromium:~$ journalctl -b -1 -e
  ..
  sddm[1106]: Message received from greeter: Suspend
  NetworkManager[836]:   manager: sleep: sleep requested (sleeping: no  
enabled: yes)
  NetworkManager[836]:   device (60:73:BC:BA:B8:68): state change: 
disconnected -> unmanaged (reason '
  NetworkManager[836]:   device (60:73:BC:23:8F:3E): state change: 
disconnected -> unmanaged (reason '
  NetworkManager[836]:   device (p2p-dev-wlp1s0): state change: 
disconnected -> unmanaged (reason 'sle
  NetworkManager[836]:   manager: NetworkManager state is now ASLEEP
  systemd[1]: Reached target Sleep.
  systemd[1]: Starting Suspend...
  systemd-sleep[1238]: Suspending system...
  kernel: PM: suspend entry (deep)

  On resume (keypress, open lid) resume starts but immediately crashes
  and reboots.

  The laptop is an Acer 720p Chromebook with Chromium replaced and
  working fine with Kubuntu since 5 years or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Oct 18 18:45:53 2019
  InstallationDate: Installed on 2017-07-13 (826 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1878045

** Tags added: iso-testing

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

Title:
  doing dist-upgrade got error related do Broadcom

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  I had a working 20.04 installation running, including the Broadcom Wifi. 
After upgrade to 20.10 the Broadcom Wifi is not working. I tried several 
suggestions and always end to an error similiar to this one: 
  ...
  Building initial module for 5.4.0-30-generic
  ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not 
supported
  Error! Application of patch 0028-add-support-for-linux-5.6.patch failed.
  Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information.
  dpkg: error processing package bcmwl-kernel-source (--configure):
   installed bcmwl-kernel-source package post-installation script subprocess 
returned error exit status 6
  Errors were encountered while processing:
   bcmwl-kernel-source
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.1
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  Date: Mon May 11 17:16:43 2020
  InstallationDate: Installed on 2020-02-22 (78 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  mtime.conffile..etc.update-manager.release-upgrades: 
2020-05-07T09:26:37.178586

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

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

[Kernel-packages] [Bug 1896726] Re: [UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic page table folding issue

[Frank Heimes]

For the reason of completeness this is the link to the patch request for groovy:
https://lists.ubuntu.com/archives/kernel-team/2020-September/thread.html#113731
and it got already applied to groovy master-next.

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

Title:
  [UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic
  page table folding issue

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  Justification:
  ==

  Secure KVM guest (using secure execution on Ubuntu Server 20.04 for s390x)
  crashes happen from time to time during boot.
  Such crashed guests ("reason=crashed" in the libvirt log) end up in hutoff 
state instead of crashed state ( preserve is set).
  The crash points to a kernel memory management problem, addressed by the 
following patch/fix.
  The modifications touch common memory management code,
  but it will have no effect to architectures other than s390x.
  This is ensured by the fact that only s390 provides / implements the new 
helper functions.
  And for s390x, this is actually a critical (and carefully tested) fix for a 
(previous) regression, so it can hardly get any more regressive.
  The patch landed upstream in linux-next, is in depth discussed
  at LKML https://lkml.kernel.org/r/20190418100218.0a4afd51@mschwideX1
  and here 
https://lore.kernel.org/linux-arch/patch.git-943f1e5dcff2.your-ad-here.call-01599856292-ext-8676@work.hours/
  and will soon land via the regular upstream stable release update for kernel 
5.4 in focal, too.
  The process already started:
  
https://lore.kernel.org/stable/patch-1.thread-41918b.git-41918be365c0.your-ad-here.call-01600439945-ext-8991@work.hours/

  Hence this cherry-pick from the upstream patch should be added to groovy
  to avoid any potential regression in case the patch landed in focal via the 
upstream release update process,
  but is not in groovy and someones upgrades from focal to groovy.

  __

  Secure Execution with Ubuntu 20.04, secure guest crash during boot
  from time to time, crashed guest went into Shufoff state instead of
  Crashed state (preserve is set), so I can't get a dump.

  libvirt log file:
  2020-04-21T16:35:39.382999Z qemu-system-s390x: Guest says index 19608 is 
available
  2020-04-21 16:35:44.831+: shutting down, reason=crashed

  ---uname output---
  Linux ubu204uclg1002 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:05:32 UTC 
2020 s390x s390x s390x GNU/Linux

  Machine Type = z15 8561

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

  ---Steps to Reproduce---
   I have a setup with 72 KVM guests which I can start in secure or non-secure 
mode. Starting all of them in secure mode back to back results in a number of 
guests (4..8) in Shutoff state and reason=crashed in the libvirt log. I can 
manually start the guest again no problem. Different guests are failing.
  Host and guests are on latest Ubuntu 20.04.

  The supposed fix (kernel memory management) has landed in Andrew Mortons mm
  tree
  
https://lore.kernel.org/mm-commits/20200916003608.ib4ln%25a...@linux-foundation.org/T/#u

  Please note: while this was found with secure execution, the bug is
  actually present for non-KVM workloads as well.

  The complete patch is this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a338e69ba37286c0fc300ab7e6fa0227e6ca68b1

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

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

[Kernel-packages] [Bug 1897942] [NEW] crash on brcmfmac

[lesar]

Public bug reported:

I have Ubuntu 20.04 64bit, ubuntu desktop, network-manager on RPI4 8GB  
wifi work well for some time but then all gone very slow and system is 
unusable.  

to me it seames a brcmfmac module problem.

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


** Tags: desktop rpi4 wifi

** Attachment added: "a bit of kernel log"
   
https://bugs.launchpad.net/bugs/1897942/+attachment/5415756/+files/mini-kernel.log

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

Title:
  crash on brcmfmac

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  I have Ubuntu 20.04 64bit, ubuntu desktop, network-manager on RPI4 8GB  
  wifi work well for some time but then all gone very slow and system is 
unusable.  

  to me it seames a brcmfmac module problem.

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

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

[Kernel-packages] [Bug 1896884] Re: Kernel 4.15.0-118 doen't get active after 4.15.0-112 updating

[Volodymyr Honcharov]

Solved! Problem was in Grub2 I used one from newer version of LM19.3
Cinnamon. I deleted Grub-customizer in my good old LM19.1, installed
Grub2 there, deleted old Vmlinuz. To see other OSs installed os-prober,
modified boot-menu's view via /etc/default/grub. There is only problem
now - doubled entries in boot menu, both second Linux and Wins. But it's
an oldest bug of Grub2. Maximum is possible - correcting manually
/boot/grub/grub.cfg, but it's working till next update-grub only. I am
shocked - the Grub2's bug - doubled entries in boot menu is from very
beginning! And boot menu of newest version of Grub2 in LM19.1 looks
great in resolution 640x480(!), I'm really shocked. Even in 2012 it
looked junk! Nevertheless, I can update my kernel now, boot in any OS.
Problem is solved.

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

Title:
  Kernel 4.15.0-118 doen't get active after 4.15.0-112 updating

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In Mint Cinnamon 19.1-64 kernel 4.15.0-118 doesn't get active after 
4.15.0-112 updating (intermediary kernel updates were skipped). Kernel 
4.15.0-112 stays active, 4.15.0-118 is only installed. Even after several 
restarting and removing 4.15.0-118 with second kernel update.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  waldi  1268 F pulseaudio
   /dev/snd/controlC0:  waldi  1268 F pulseaudio
   /dev/snd/controlC1:  waldi  1268 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2
  InstallationDate: Installed on 2019-02-27 (574 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217
  IwConfig:
   enp5s0no wireless extensions.
   
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-112-generic N/A
   linux-backports-modules-4.15.0-112-generic  N/A
   linux-firmware  1.173.19
  RfKill:
   
  Tags:  tessa
  Uname: Linux 4.15.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Thiago Marcello]

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

@dgoosens

I updated my kernel to 5.6.10-050610-generic but still not working.

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Kernel-packages] [Bug 1895947] Re: backport tls-rx to ubuntu 5.8

[Francis Ginther]

Patches have been committed to the 5.8 master-next branch. Expected in
the next 5.8 groovy kernel.

** Changed in: linux (Ubuntu Groovy)
   Status: Confirmed => 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/1895947

Title:
  backport tls-rx to ubuntu 5.8

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

Bug description:
  Hi,

  [Impact]
  The request here is to backport support for ktls-rx from upstream 5.9 to 
Ubuntu 20.10/20.04-HWE 5.8 kernel.

  [Other Info]
  list of required patches:

  (1 patch)
  from 
https://patchwork.ozlabs.org/project/netdev/patch/20200626055943.99943-3-sae...@mellanox.com/
  2d1b69ed65ee net/mlx5: kTLS, Improve TLS params layout structures
  (needed to apply ‘net/mlx5e: kTLS, Improve TLS feature modularity’ below 
cleanly)

  (15 patches )
  https://patchwork.ozlabs.org/project/netdev/list/?series=186181=*
  a29074367b34 net/mlx5e: kTLS, Improve rx handler function call
  ed9a7c53b878 net/mlx5e: kTLS, Cleanup redundant capability check
  c5607360ec4e net/mlx5e: Increase Async ICO SQ size
  76c1e1ac2aae net/mlx5e: kTLS, Add kTLS RX stats
  0419d8c9d8f8 net/mlx5e: kTLS, Add kTLS RX resync support
  ed9b7646b06a net/tls: Add asynchronous resync
  acb5a07aaf27 Revert "net/tls: Add force_resync for driver resync"
  1182f3659357 net/mlx5e: kTLS, Add kTLS RX HW offload support
  df8d866770f9 net/mlx5e: kTLS, Use kernel API to extract private offload 
context
  7d0d0d86ec6c net/mlx5e: kTLS, Improve TLS feature modularity
  5229a96e59ec net/mlx5e: Accel, Expose flow steering API for rules add/del
  c062d52ac24c net/mlx5e: Receive flow steering framework for accelerated TCP 
flows
  b8922a73ec3e net/mlx5e: API to manipulate TTC rules destinations
  c293ac927fbb net/mlx5e: Refactor build channel params
  8d94b590f1e4 net/mlx5e: Turn XSK ICOSQ into a general asynchronous one

  (3 bug fixes patches, also attached)
  6e8de0b6b469 net/mlx5e: kTLS, Fix napi sync and possible use-after-free
  9c25a22dfb00 net/mlx5e: Use synchronize_rcu to sync with NAPI
  fe45386a2082 net/mlx5e: Use RCU to protect rq->xdp_prog

  all patches are applied cleanly beside
  1182f3659357 net/mlx5e: kTLS, Add kTLS RX HW offload support
  that has one hunk rejected in
  file: drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  function: mlx5e_init_nic_rx
  the rejection is caused by and extra #ifdef statement
  inserted by commit f4aebbfb56ed0c186adbeb2799df836da50f78e3
  here we just need to add manually the needed lines.

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

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

[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

[max]

+1

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

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

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are supposed to be turned on 
by a button on the touchpad. This works well in Windows but doesn't work in 
Ubuntu. 
  I have tried to search for any related problems/solutions online but I 
haven't been able to.
  I will appreciate any suggestion or help.
  Thanks,
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.19.11-041911-generic 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 sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.18.10-041810-generic 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 sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1897904] Re: Computer sometimes boot with snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus:

[Marcos Diaz]

** Description changed:

  *sometimes* (not always) when booting I notice the system slow,
- when running dmesg I see a lot of this logs: snd_hda_intel :00:1f.3: No 
response from codec, resetting bus:...
+ when running dmesg I see a lot of these logs: 
+ snd_hda_intel :00:1f.3: No response from codec, resetting bus:...
  
  I reproduced sometimes:
  5.4.0-48-generic
  
  still couldn't reproduce in
  5.4.0-42-generic
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  cecilia1897 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  cecilia1897 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 10:18:54 2020
  InstallationDate: Installed on 2020-09-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 13d3:56b2 IMC Networks Integrated Camera
-  Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
-  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
-  Bus 001 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 003: ID 13d3:56b2 IMC Networks Integrated Camera
+  Bus 001 Device 004: ID 8087:0aaa Intel Corp.
+  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81VW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=/dev/mapper/vgcherries-lvcherriesroot ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-48-generic N/A
-  linux-backports-modules-5.4.0-48-generic  N/A
-  linux-firmware1.187.3
+  linux-restricted-modules-5.4.0-48-generic N/A
+  linux-backports-modules-5.4.0-48-generic  N/A
+  linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CUCN13WW(V1.02)
  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 S340-15IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrCUCN13WW(V1.02):bd09/03/2019:svnLENOVO:pn81VW:pvrLenovoIdeaPadS340-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-15IIL:
  dmi.product.family: IdeaPad S340-15IIL
  dmi.product.name: 81VW
  dmi.product.sku: LENOVO_MT_81VW_BU_idea_FM_IdeaPad S340-15IIL
  dmi.product.version: Lenovo IdeaPad S340-15IIL
  dmi.sys.vendor: LENOVO

** Description changed:

  *sometimes* (not always) when booting I notice the system slow,
- when running dmesg I see a lot of these logs: 
+ when running dmesg I see a lot of these logs:
  snd_hda_intel :00:1f.3: No response from codec, resetting bus:...
  
- I reproduced sometimes:
+ I reproduced sometimes in:
  5.4.0-48-generic
  
  still couldn't reproduce in
  5.4.0-42-generic
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cecilia1897 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 10:18:54 2020
  InstallationDate: Installed on 2020-09-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81VW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=/dev/mapper/vgcherries-lvcherriesroot ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Computer sometimes boot with snd_hda_intel :00:1f.3: No response
  from codec, resetting bus:

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  *sometimes* (not always) when booting I notice the system slow,
  when running dmesg I see a lot of these logs: snd_hda_intel :00:1f.3: No 
response from codec, resetting bus:...
  When I see the logs, the system is unstable: it takes a while to open file 
explorer/ terminal or whatever I try to open

  I reproduced sometimes in:
  5.4.0-48-generic

  still couldn't reproduce in
  5.4.0-42-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cecilia1897 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 10:18:54 2020
  InstallationDate: Installed on 2020-09-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81VW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=/dev/mapper/vgcherries-lvcherriesroot ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CUCN13WW(V1.02)
  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 S340-15IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrCUCN13WW(V1.02):bd09/03/2019:svnLENOVO:pn81VW:pvrLenovoIdeaPadS340-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-15IIL:
  dmi.product.family: IdeaPad S340-15IIL
  dmi.product.name: 81VW
  dmi.product.sku: LENOVO_MT_81VW_BU_idea_FM_IdeaPad S340-15IIL
  dmi.product.version: Lenovo IdeaPad S340-15IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1897904] [NEW] Computer sometimes boot with snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus:

[Marcos Diaz]

Public bug reported:

*sometimes* (not always) when booting I notice the system slow,
when running dmesg I see a lot of these logs:
snd_hda_intel :00:1f.3: No response from codec, resetting bus:...

I reproduced sometimes in:
5.4.0-48-generic

still couldn't reproduce in
5.4.0-42-generic

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  cecilia1897 F pulseaudio
CasperMD5CheckResult: skip
Date: Wed Sep 30 10:18:54 2020
InstallationDate: Installed on 2020-09-29 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:56b2 IMC Networks Integrated Camera
 Bus 001 Device 004: ID 8087:0aaa Intel Corp.
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81VW
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=/dev/mapper/vgcherries-lvcherriesroot ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-48-generic N/A
 linux-backports-modules-5.4.0-48-generic  N/A
 linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/03/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: CUCN13WW(V1.02)
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 S340-15IIL
dmi.modalias: 
dmi:bvnLENOVO:bvrCUCN13WW(V1.02):bd09/03/2019:svnLENOVO:pn81VW:pvrLenovoIdeaPadS340-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-15IIL:
dmi.product.family: IdeaPad S340-15IIL
dmi.product.name: 81VW
dmi.product.sku: LENOVO_MT_81VW_BU_idea_FM_IdeaPad S340-15IIL
dmi.product.version: Lenovo IdeaPad S340-15IIL
dmi.sys.vendor: LENOVO

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


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

Title:
  Computer sometimes boot with snd_hda_intel :00:1f.3: No response
  from codec, resetting bus:

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  *sometimes* (not always) when booting I notice the system slow,
  when running dmesg I see a lot of these logs:
  snd_hda_intel :00:1f.3: No response from codec, resetting bus:...

  I reproduced sometimes in:
  5.4.0-48-generic

  still couldn't reproduce in
  5.4.0-42-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cecilia1897 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 10:18:54 2020
  InstallationDate: Installed on 2020-09-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81VW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic 
root=/dev/mapper/vgcherries-lvcherriesroot ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CUCN13WW(V1.02)
  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 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  bind04 from ubuntu_ltp_syscalls caused kernel NULL pointer dereference
  on B-5.4 i386

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

Bug description:
  Issue found on 5.4.0-49.53~18.04.1 i386 node pepe (this issue does not
  exist on other arhces)

  bind04 test will cause kernel NULL pointer dereference and taints the
  kernel, making other tests to fail.

  Test output:
  <<>>
  incrementing stop
  tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
  bind04.c:117: TINFO: Testing AF_UNIX pathname stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX pathname seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop SCTP
  bind04.c:150: TPASS: Communication successful
  tst_test.c:1295: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1296: TBROK: Test killed! (timeout?)

  Summary:
  passed   13
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=2 corefile=no
  cutime=40 cstime=324
  <<>>

  syslog output:
   pepe kernel: [  456.420474] LTP: starting bind04
   pepe kernel: [  456.451023] sctp: Hash tables configured (bind 512/512)
   pepe kernel: [  456.452997] BUG: kernel NULL pointer dereference, address: 
0008
   pepe kernel: [  456.528037] #PF: supervisor read access in kernel mode
   pepe kernel: [  456.589500] #PF: error_code(0x) - not-present page
   pepe kernel: [  456.651172] *pdpt = 220e0001 *pde = 
   pepe kernel: [  456.720122] Oops:  [#1] SMP PTI
   pepe kernel: [  456.761828] CPU: 1 PID: 9783 Comm: bind04 Not tainted 
5.4.0-48-generic #52~18.04.1-Ubuntu
   pepe kernel: [  456.859798] Hardware name: Dell Inc. PowerEdge R310/05XKKK, 
BIOS 1.8.2 08/17/2011
   pepe kernel: [  456.949345] EIP: sctp_ulpevent_free+0x24/0x70 [sctp]
   pepe kernel: [  457.008824] Code: 52 67 71 e3 66 90 66 66 66 66 90 55 89 e5 
57 56 53 66 83 78 20 00 89 c3 78 3b 8b 78 3c 8b 40 40 85 c0 74 20 8b 83 88 00 
00 00 <8b> 70 08 85 f6 74 13 90 8d 74 26 00 8d 46 18 e8 48 ec ff ff 8b 36
   pepe kernel: [  457.233564] EAX:  EBX: e239aa20 ECX: 0246 EDX: 
e239aa08
   pepe kernel: [  457.308755] ESI: e1c02a08 EDI:  EBP: e5661eac ESP: 
e5661ea0
   pepe kernel: [  457.383798] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010202
   pepe kernel: [  457.465170] CR0: 80050033 CR2: 0008 CR3: 25602000 CR4: 
06f0
   pepe kernel: [  457.540361] Call Trace:
   pepe kernel: [  457.569594]  sctp_queue_purge_ulpevents+0x22/0x40 [sctp]
   pepe kernel: [  457.633241]  sctp_close+0x69/0x270 [sctp]
   pepe kernel: [  457.681179]  ? tty_write_unlock+0x2a/0x30
   pepe kernel: [  457.729224]  ? tty_ldisc_deref+0x13/0x20
   pepe kernel: [  457.776127]  inet_release+0x2f/0x60
   pepe kernel: [  457.818040]  inet6_release+0x28/0x40
   pepe kernel: [  457.860783]  __sock_release+0x32/0xb0
   pepe kernel: [  457.904565]  sock_close+0x12/0x20
   pepe kernel: [  457.944190]  __fput+0xb3/0x240
   pepe kernel: [  457.980694]  fput+0xd/0x10
   pepe kernel: [  458.017302]  task_work_run+0x82/0xa0
   pepe kernel: [  458.060044]  exit_to_usermode_loop+0xed/0x110
   pepe kernel: [  458.112251]  do_fast_syscall_32+0x1c7/0x240
   pepe kernel: [  458.162275]  entry_SYSENTER_32+0xac/0xff
   pepe kernel: [  458.209176] EIP: 0xb7ef5bb5
   pepe kernel: [  458.242666] Code: d3 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 b8 
00 09 3d 00 eb b5 8b 04 24 c3 8b 1c 24 c3 8b 34 24 c3 90 51 52 55 89 e5 0f 34 
cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76
   pepe kernel: [ 

[Kernel-packages] [Bug 1868519] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite()

[Sergey]

My desktop is still being re-logged randomly. How do I know if this is a
problem or not?

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

Title:
  [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from
  xf86MoveCursor() from miPointerMoveNoEvent() from
  miPointerSetPosition() from positionSprite()

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nvidia-graphics-drivers.  This problem was most recently seen with package 
version 2:1.20.7-2ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5a9ed7ea32a1d20e4222dbe8712aa9640b42a73c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Kernel-packages] [Bug 1897894] Re: bind04 from ubuntu_ltp_syscalls caused kernel NULL pointer dereference on B-5.4 i386

[Po-Hsu Lin]

** Description changed:

  Issue found on 5.4.0-49.53~18.04.1 i386 node pepe (this issue does not
  exist on other arhces)
  
  bind04 test will cause kernel NULL pointer dereference and taints the
  kernel, making other tests to fail.
  
  Test output:
  <<>>
  incrementing stop
  tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
  bind04.c:117: TINFO: Testing AF_UNIX pathname stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX pathname seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop SCTP
  bind04.c:150: TPASS: Communication successful
  tst_test.c:1295: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1296: TBROK: Test killed! (timeout?)
  
  Summary:
  passed   13
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=2 corefile=no
  cutime=40 cstime=324
  <<>>
  
  syslog output:
   pepe kernel: [  456.420474] LTP: starting bind04
   pepe kernel: [  456.451023] sctp: Hash tables configured (bind 512/512)
   pepe kernel: [  456.452997] BUG: kernel NULL pointer dereference, address: 
0008
   pepe kernel: [  456.528037] #PF: supervisor read access in kernel mode
   pepe kernel: [  456.589500] #PF: error_code(0x) - not-present page
   pepe kernel: [  456.651172] *pdpt = 220e0001 *pde = 
   pepe kernel: [  456.720122] Oops:  [#1] SMP PTI
   pepe kernel: [  456.761828] CPU: 1 PID: 9783 Comm: bind04 Not tainted 
5.4.0-48-generic #52~18.04.1-Ubuntu
   pepe kernel: [  456.859798] Hardware name: Dell Inc. PowerEdge R310/05XKKK, 
BIOS 1.8.2 08/17/2011
   pepe kernel: [  456.949345] EIP: sctp_ulpevent_free+0x24/0x70 [sctp]
   pepe kernel: [  457.008824] Code: 52 67 71 e3 66 90 66 66 66 66 90 55 89 e5 
57 56 53 66 83 78 20 00 89 c3 78 3b 8b 78 3c 8b 40 40 85 c0 74 20 8b 83 88 00 
00 00 <8b> 70 08 85 f6 74 13 90 8d 74 26 00 8d 46 18 e8 48 ec ff ff 8b 36
   pepe kernel: [  457.233564] EAX:  EBX: e239aa20 ECX: 0246 EDX: 
e239aa08
   pepe kernel: [  457.308755] ESI: e1c02a08 EDI:  EBP: e5661eac ESP: 
e5661ea0
   pepe kernel: [  457.383798] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010202
   pepe kernel: [  457.465170] CR0: 80050033 CR2: 0008 CR3: 25602000 CR4: 
06f0
   pepe kernel: [  457.540361] Call Trace:
   pepe kernel: [  457.569594]  sctp_queue_purge_ulpevents+0x22/0x40 [sctp]
   pepe kernel: [  457.633241]  sctp_close+0x69/0x270 [sctp]
   pepe kernel: [  457.681179]  ? tty_write_unlock+0x2a/0x30
   pepe kernel: [  457.729224]  ? tty_ldisc_deref+0x13/0x20
   pepe kernel: [  457.776127]  inet_release+0x2f/0x60
   pepe kernel: [  457.818040]  inet6_release+0x28/0x40
   pepe kernel: [  457.860783]  __sock_release+0x32/0xb0
   pepe kernel: [  457.904565]  sock_close+0x12/0x20
   pepe kernel: [  457.944190]  __fput+0xb3/0x240
   pepe kernel: [  457.980694]  fput+0xd/0x10
   pepe kernel: [  458.017302]  task_work_run+0x82/0xa0
   pepe kernel: [  458.060044]  exit_to_usermode_loop+0xed/0x110
   pepe kernel: [  458.112251]  do_fast_syscall_32+0x1c7/0x240
   pepe kernel: [  458.162275]  entry_SYSENTER_32+0xac/0xff
   pepe kernel: [  458.209176] EIP: 0xb7ef5bb5
   pepe kernel: [  458.242666] Code: d3 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 b8 
00 09 3d 00 eb b5 8b 04 24 c3 8b 1c 24 c3 8b 34 24 c3 90 51 52 55 89 e5 0f 34 
cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76
   pepe kernel: [  458.467405] EAX:  EBX: 0007 ECX: 0002 EDX: 

   pepe kernel: [  458.542597] ESI: b7ee4000 EDI: 0006 EBP: 004b1210 ESP: 
bfebe150
   pepe kernel: [  458.617789] DS: 007b ES: 007b FS:  GS: 0033 SS: 007b 
EFLAGS: 0293
   pepe kernel: [  458.699012] Modules linked in: sctp nfsd auth_rpcgss nfs_acl 
lockd grace sunrpc intel_powerclamp coretemp kvm_intel kvm irqbypass ipmi_ssif 
gpio_ich intel_cstate lpc_ich 

[Kernel-packages] [Bug 1897894] WifiSyslog.txt

[Po-Hsu Lin]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1897894/+attachment/5415653/+files/WifiSyslog.txt

** Description changed:

- Issue found on 5.4.0-49.53~18.04.1 i386 node pepe
+ Issue found on 5.4.0-49.53~18.04.1 i386 node pepe (this issue does not
+ exist on other arhces)
  
  bind04 test will cause kernel NULL pointer dereference and taints the
  kernel, making other tests to fail.
  
  Test output:
  <<>>
  incrementing stop
  tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
  bind04.c:117: TINFO: Testing AF_UNIX pathname stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX pathname seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop SCTP
  bind04.c:150: TPASS: Communication successful
  tst_test.c:1295: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1296: TBROK: Test killed! (timeout?)
  
  Summary:
  passed   13
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=2 corefile=no
  cutime=40 cstime=324
  <<>>
  
  syslog output:
   pepe kernel: [  456.420474] LTP: starting bind04
   pepe kernel: [  456.451023] sctp: Hash tables configured (bind 512/512)
   pepe kernel: [  456.452997] BUG: kernel NULL pointer dereference, address: 
0008
   pepe kernel: [  456.528037] #PF: supervisor read access in kernel mode
   pepe kernel: [  456.589500] #PF: error_code(0x) - not-present page
   pepe kernel: [  456.651172] *pdpt = 220e0001 *pde = 
   pepe kernel: [  456.720122] Oops:  [#1] SMP PTI
   pepe kernel: [  456.761828] CPU: 1 PID: 9783 Comm: bind04 Not tainted 
5.4.0-48-generic #52~18.04.1-Ubuntu
   pepe kernel: [  456.859798] Hardware name: Dell Inc. PowerEdge R310/05XKKK, 
BIOS 1.8.2 08/17/2011
   pepe kernel: [  456.949345] EIP: sctp_ulpevent_free+0x24/0x70 [sctp]
   pepe kernel: [  457.008824] Code: 52 67 71 e3 66 90 66 66 66 66 90 55 89 e5 
57 56 53 66 83 78 20 00 89 c3 78 3b 8b 78 3c 8b 40 40 85 c0 74 20 8b 83 88 00 
00 00 <8b> 70 08 85 f6 74 13 90 8d 74 26 00 8d 46 18 e8 48 ec ff ff 8b 36
   pepe kernel: [  457.233564] EAX:  EBX: e239aa20 ECX: 0246 EDX: 
e239aa08
   pepe kernel: [  457.308755] ESI: e1c02a08 EDI:  EBP: e5661eac ESP: 
e5661ea0
   pepe kernel: [  457.383798] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010202
   pepe kernel: [  457.465170] CR0: 80050033 CR2: 0008 CR3: 25602000 CR4: 
06f0
   pepe kernel: [  457.540361] Call Trace:
   pepe kernel: [  457.569594]  sctp_queue_purge_ulpevents+0x22/0x40 [sctp]
   pepe kernel: [  457.633241]  sctp_close+0x69/0x270 [sctp]
   pepe kernel: [  457.681179]  ? tty_write_unlock+0x2a/0x30
   pepe kernel: [  457.729224]  ? tty_ldisc_deref+0x13/0x20
   pepe kernel: [  457.776127]  inet_release+0x2f/0x60
   pepe kernel: [  457.818040]  inet6_release+0x28/0x40
   pepe kernel: [  457.860783]  __sock_release+0x32/0xb0
   pepe kernel: [  457.904565]  sock_close+0x12/0x20
   pepe kernel: [  457.944190]  __fput+0xb3/0x240
   pepe kernel: [  457.980694]  fput+0xd/0x10
   pepe kernel: [  458.017302]  task_work_run+0x82/0xa0
   pepe kernel: [  458.060044]  exit_to_usermode_loop+0xed/0x110
   pepe kernel: [  458.112251]  do_fast_syscall_32+0x1c7/0x240
   pepe kernel: [  458.162275]  entry_SYSENTER_32+0xac/0xff
   pepe kernel: [  458.209176] EIP: 0xb7ef5bb5
   pepe kernel: [  458.242666] Code: d3 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 b8 
00 09 3d 00 eb b5 8b 04 24 c3 8b 1c 24 c3 8b 34 24 c3 90 51 52 55 89 e5 0f 34 
cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76
   pepe kernel: [  458.467405] EAX:  EBX: 0007 ECX: 0002 EDX: 

   pepe kernel: [  458.542597] ESI: b7ee4000 EDI: 0006 EBP: 004b1210 ESP: 
bfebe150
   pepe kernel: [  458.617789] DS: 007b ES: 007b FS:  GS: 0033 SS: 007b 
EFLAGS: 

[Kernel-packages] [Bug 1897894] ProcModules.txt

[Po-Hsu Lin]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1897894/+attachment/5415651/+files/ProcModules.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/1897894

Title:
  bind04 from ubuntu_ltp_syscalls caused kernel NULL pointer dereference
  on B-5.4 i386

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

Bug description:
  Issue found on 5.4.0-49.53~18.04.1 i386 node pepe (this issue does not
  exist on other arhces)

  bind04 test will cause kernel NULL pointer dereference and taints the
  kernel, making other tests to fail.

  Test output:
  <<>>
  incrementing stop
  tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
  bind04.c:117: TINFO: Testing AF_UNIX pathname stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX pathname seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop SCTP
  bind04.c:150: TPASS: Communication successful
  tst_test.c:1295: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1296: TBROK: Test killed! (timeout?)

  Summary:
  passed   13
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=2 corefile=no
  cutime=40 cstime=324
  <<>>

  syslog output:
   pepe kernel: [  456.420474] LTP: starting bind04
   pepe kernel: [  456.451023] sctp: Hash tables configured (bind 512/512)
   pepe kernel: [  456.452997] BUG: kernel NULL pointer dereference, address: 
0008
   pepe kernel: [  456.528037] #PF: supervisor read access in kernel mode
   pepe kernel: [  456.589500] #PF: error_code(0x) - not-present page
   pepe kernel: [  456.651172] *pdpt = 220e0001 *pde = 
   pepe kernel: [  456.720122] Oops:  [#1] SMP PTI
   pepe kernel: [  456.761828] CPU: 1 PID: 9783 Comm: bind04 Not tainted 
5.4.0-48-generic #52~18.04.1-Ubuntu
   pepe kernel: [  456.859798] Hardware name: Dell Inc. PowerEdge R310/05XKKK, 
BIOS 1.8.2 08/17/2011
   pepe kernel: [  456.949345] EIP: sctp_ulpevent_free+0x24/0x70 [sctp]
   pepe kernel: [  457.008824] Code: 52 67 71 e3 66 90 66 66 66 66 90 55 89 e5 
57 56 53 66 83 78 20 00 89 c3 78 3b 8b 78 3c 8b 40 40 85 c0 74 20 8b 83 88 00 
00 00 <8b> 70 08 85 f6 74 13 90 8d 74 26 00 8d 46 18 e8 48 ec ff ff 8b 36
   pepe kernel: [  457.233564] EAX:  EBX: e239aa20 ECX: 0246 EDX: 
e239aa08
   pepe kernel: [  457.308755] ESI: e1c02a08 EDI:  EBP: e5661eac ESP: 
e5661ea0
   pepe kernel: [  457.383798] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010202
   pepe kernel: [  457.465170] CR0: 80050033 CR2: 0008 CR3: 25602000 CR4: 
06f0
   pepe kernel: [  457.540361] Call Trace:
   pepe kernel: [  457.569594]  sctp_queue_purge_ulpevents+0x22/0x40 [sctp]
   pepe kernel: [  457.633241]  sctp_close+0x69/0x270 [sctp]
   pepe kernel: [  457.681179]  ? tty_write_unlock+0x2a/0x30
   pepe kernel: [  457.729224]  ? tty_ldisc_deref+0x13/0x20
   pepe kernel: [  457.776127]  inet_release+0x2f/0x60
   pepe kernel: [  457.818040]  inet6_release+0x28/0x40
   pepe kernel: [  457.860783]  __sock_release+0x32/0xb0
   pepe kernel: [  457.904565]  sock_close+0x12/0x20
   pepe kernel: [  457.944190]  __fput+0xb3/0x240
   pepe kernel: [  457.980694]  fput+0xd/0x10
   pepe kernel: [  458.017302]  task_work_run+0x82/0xa0
   pepe kernel: [  458.060044]  exit_to_usermode_loop+0xed/0x110
   pepe kernel: [  458.112251]  do_fast_syscall_32+0x1c7/0x240
   pepe kernel: [  458.162275]  entry_SYSENTER_32+0xac/0xff
   pepe kernel: [  458.209176] EIP: 0xb7ef5bb5
   pepe kernel: [  458.242666] Code: d3 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 b8 
00 09 3d 00 eb b5 8b 04 24 c3 8b 1c 24 c3 8b 34 24 c3 90 51 52 55 89 e5 0f 34 
cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 

[Kernel-packages] [Bug 1897894] UdevDb.txt

[Po-Hsu Lin]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1897894/+attachment/5415652/+files/UdevDb.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/1897894

Title:
  bind04 from ubuntu_ltp_syscalls caused kernel NULL pointer dereference
  on B-5.4 i386

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

Bug description:
  Issue found on 5.4.0-49.53~18.04.1 i386 node pepe (this issue does not
  exist on other arhces)

  bind04 test will cause kernel NULL pointer dereference and taints the
  kernel, making other tests to fail.

  Test output:
  <<>>
  incrementing stop
  tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
  bind04.c:117: TINFO: Testing AF_UNIX pathname stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX pathname seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop SCTP
  bind04.c:150: TPASS: Communication successful
  tst_test.c:1295: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1296: TBROK: Test killed! (timeout?)

  Summary:
  passed   13
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=2 corefile=no
  cutime=40 cstime=324
  <<>>

  syslog output:
   pepe kernel: [  456.420474] LTP: starting bind04
   pepe kernel: [  456.451023] sctp: Hash tables configured (bind 512/512)
   pepe kernel: [  456.452997] BUG: kernel NULL pointer dereference, address: 
0008
   pepe kernel: [  456.528037] #PF: supervisor read access in kernel mode
   pepe kernel: [  456.589500] #PF: error_code(0x) - not-present page
   pepe kernel: [  456.651172] *pdpt = 220e0001 *pde = 
   pepe kernel: [  456.720122] Oops:  [#1] SMP PTI
   pepe kernel: [  456.761828] CPU: 1 PID: 9783 Comm: bind04 Not tainted 
5.4.0-48-generic #52~18.04.1-Ubuntu
   pepe kernel: [  456.859798] Hardware name: Dell Inc. PowerEdge R310/05XKKK, 
BIOS 1.8.2 08/17/2011
   pepe kernel: [  456.949345] EIP: sctp_ulpevent_free+0x24/0x70 [sctp]
   pepe kernel: [  457.008824] Code: 52 67 71 e3 66 90 66 66 66 66 90 55 89 e5 
57 56 53 66 83 78 20 00 89 c3 78 3b 8b 78 3c 8b 40 40 85 c0 74 20 8b 83 88 00 
00 00 <8b> 70 08 85 f6 74 13 90 8d 74 26 00 8d 46 18 e8 48 ec ff ff 8b 36
   pepe kernel: [  457.233564] EAX:  EBX: e239aa20 ECX: 0246 EDX: 
e239aa08
   pepe kernel: [  457.308755] ESI: e1c02a08 EDI:  EBP: e5661eac ESP: 
e5661ea0
   pepe kernel: [  457.383798] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010202
   pepe kernel: [  457.465170] CR0: 80050033 CR2: 0008 CR3: 25602000 CR4: 
06f0
   pepe kernel: [  457.540361] Call Trace:
   pepe kernel: [  457.569594]  sctp_queue_purge_ulpevents+0x22/0x40 [sctp]
   pepe kernel: [  457.633241]  sctp_close+0x69/0x270 [sctp]
   pepe kernel: [  457.681179]  ? tty_write_unlock+0x2a/0x30
   pepe kernel: [  457.729224]  ? tty_ldisc_deref+0x13/0x20
   pepe kernel: [  457.776127]  inet_release+0x2f/0x60
   pepe kernel: [  457.818040]  inet6_release+0x28/0x40
   pepe kernel: [  457.860783]  __sock_release+0x32/0xb0
   pepe kernel: [  457.904565]  sock_close+0x12/0x20
   pepe kernel: [  457.944190]  __fput+0xb3/0x240
   pepe kernel: [  457.980694]  fput+0xd/0x10
   pepe kernel: [  458.017302]  task_work_run+0x82/0xa0
   pepe kernel: [  458.060044]  exit_to_usermode_loop+0xed/0x110
   pepe kernel: [  458.112251]  do_fast_syscall_32+0x1c7/0x240
   pepe kernel: [  458.162275]  entry_SYSENTER_32+0xac/0xff
   pepe kernel: [  458.209176] EIP: 0xb7ef5bb5
   pepe kernel: [  458.242666] Code: d3 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 b8 
00 09 3d 00 eb b5 8b 04 24 c3 8b 1c 24 c3 8b 34 24 c3 90 51 52 55 89 e5 0f 34 
cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76
   

[Kernel-packages] [Bug 1897894] ProcEnviron.txt

[Po-Hsu Lin]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1897894/+attachment/5415649/+files/ProcEnviron.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/1897894

Title:
  bind04 from ubuntu_ltp_syscalls caused kernel NULL pointer dereference
  on B-5.4 i386

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

Bug description:
  Issue found on 5.4.0-49.53~18.04.1 i386 node pepe (this issue does not
  exist on other arhces)

  bind04 test will cause kernel NULL pointer dereference and taints the
  kernel, making other tests to fail.

  Test output:
  <<>>
  incrementing stop
  tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
  bind04.c:117: TINFO: Testing AF_UNIX pathname stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX pathname seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop SCTP
  bind04.c:150: TPASS: Communication successful
  tst_test.c:1295: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1296: TBROK: Test killed! (timeout?)

  Summary:
  passed   13
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=2 corefile=no
  cutime=40 cstime=324
  <<>>

  syslog output:
   pepe kernel: [  456.420474] LTP: starting bind04
   pepe kernel: [  456.451023] sctp: Hash tables configured (bind 512/512)
   pepe kernel: [  456.452997] BUG: kernel NULL pointer dereference, address: 
0008
   pepe kernel: [  456.528037] #PF: supervisor read access in kernel mode
   pepe kernel: [  456.589500] #PF: error_code(0x) - not-present page
   pepe kernel: [  456.651172] *pdpt = 220e0001 *pde = 
   pepe kernel: [  456.720122] Oops:  [#1] SMP PTI
   pepe kernel: [  456.761828] CPU: 1 PID: 9783 Comm: bind04 Not tainted 
5.4.0-48-generic #52~18.04.1-Ubuntu
   pepe kernel: [  456.859798] Hardware name: Dell Inc. PowerEdge R310/05XKKK, 
BIOS 1.8.2 08/17/2011
   pepe kernel: [  456.949345] EIP: sctp_ulpevent_free+0x24/0x70 [sctp]
   pepe kernel: [  457.008824] Code: 52 67 71 e3 66 90 66 66 66 66 90 55 89 e5 
57 56 53 66 83 78 20 00 89 c3 78 3b 8b 78 3c 8b 40 40 85 c0 74 20 8b 83 88 00 
00 00 <8b> 70 08 85 f6 74 13 90 8d 74 26 00 8d 46 18 e8 48 ec ff ff 8b 36
   pepe kernel: [  457.233564] EAX:  EBX: e239aa20 ECX: 0246 EDX: 
e239aa08
   pepe kernel: [  457.308755] ESI: e1c02a08 EDI:  EBP: e5661eac ESP: 
e5661ea0
   pepe kernel: [  457.383798] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010202
   pepe kernel: [  457.465170] CR0: 80050033 CR2: 0008 CR3: 25602000 CR4: 
06f0
   pepe kernel: [  457.540361] Call Trace:
   pepe kernel: [  457.569594]  sctp_queue_purge_ulpevents+0x22/0x40 [sctp]
   pepe kernel: [  457.633241]  sctp_close+0x69/0x270 [sctp]
   pepe kernel: [  457.681179]  ? tty_write_unlock+0x2a/0x30
   pepe kernel: [  457.729224]  ? tty_ldisc_deref+0x13/0x20
   pepe kernel: [  457.776127]  inet_release+0x2f/0x60
   pepe kernel: [  457.818040]  inet6_release+0x28/0x40
   pepe kernel: [  457.860783]  __sock_release+0x32/0xb0
   pepe kernel: [  457.904565]  sock_close+0x12/0x20
   pepe kernel: [  457.944190]  __fput+0xb3/0x240
   pepe kernel: [  457.980694]  fput+0xd/0x10
   pepe kernel: [  458.017302]  task_work_run+0x82/0xa0
   pepe kernel: [  458.060044]  exit_to_usermode_loop+0xed/0x110
   pepe kernel: [  458.112251]  do_fast_syscall_32+0x1c7/0x240
   pepe kernel: [  458.162275]  entry_SYSENTER_32+0xac/0xff
   pepe kernel: [  458.209176] EIP: 0xb7ef5bb5
   pepe kernel: [  458.242666] Code: d3 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 b8 
00 09 3d 00 eb b5 8b 04 24 c3 8b 1c 24 c3 8b 34 24 c3 90 51 52 55 89 e5 0f 34 
cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 

[Kernel-packages] [Bug 1897894] ProcCpuinfo.txt

[Po-Hsu Lin]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1897894/+attachment/5415647/+files/ProcCpuinfo.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/1897894

Title:
  bind04 from ubuntu_ltp_syscalls caused kernel NULL pointer dereference
  on B-5.4 i386

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

Bug description:
  Issue found on 5.4.0-49.53~18.04.1 i386 node pepe (this issue does not
  exist on other arhces)

  bind04 test will cause kernel NULL pointer dereference and taints the
  kernel, making other tests to fail.

  Test output:
  <<>>
  incrementing stop
  tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
  bind04.c:117: TINFO: Testing AF_UNIX pathname stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX pathname seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop SCTP
  bind04.c:150: TPASS: Communication successful
  tst_test.c:1295: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1296: TBROK: Test killed! (timeout?)

  Summary:
  passed   13
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=2 corefile=no
  cutime=40 cstime=324
  <<>>

  syslog output:
   pepe kernel: [  456.420474] LTP: starting bind04
   pepe kernel: [  456.451023] sctp: Hash tables configured (bind 512/512)
   pepe kernel: [  456.452997] BUG: kernel NULL pointer dereference, address: 
0008
   pepe kernel: [  456.528037] #PF: supervisor read access in kernel mode
   pepe kernel: [  456.589500] #PF: error_code(0x) - not-present page
   pepe kernel: [  456.651172] *pdpt = 220e0001 *pde = 
   pepe kernel: [  456.720122] Oops:  [#1] SMP PTI
   pepe kernel: [  456.761828] CPU: 1 PID: 9783 Comm: bind04 Not tainted 
5.4.0-48-generic #52~18.04.1-Ubuntu
   pepe kernel: [  456.859798] Hardware name: Dell Inc. PowerEdge R310/05XKKK, 
BIOS 1.8.2 08/17/2011
   pepe kernel: [  456.949345] EIP: sctp_ulpevent_free+0x24/0x70 [sctp]
   pepe kernel: [  457.008824] Code: 52 67 71 e3 66 90 66 66 66 66 90 55 89 e5 
57 56 53 66 83 78 20 00 89 c3 78 3b 8b 78 3c 8b 40 40 85 c0 74 20 8b 83 88 00 
00 00 <8b> 70 08 85 f6 74 13 90 8d 74 26 00 8d 46 18 e8 48 ec ff ff 8b 36
   pepe kernel: [  457.233564] EAX:  EBX: e239aa20 ECX: 0246 EDX: 
e239aa08
   pepe kernel: [  457.308755] ESI: e1c02a08 EDI:  EBP: e5661eac ESP: 
e5661ea0
   pepe kernel: [  457.383798] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010202
   pepe kernel: [  457.465170] CR0: 80050033 CR2: 0008 CR3: 25602000 CR4: 
06f0
   pepe kernel: [  457.540361] Call Trace:
   pepe kernel: [  457.569594]  sctp_queue_purge_ulpevents+0x22/0x40 [sctp]
   pepe kernel: [  457.633241]  sctp_close+0x69/0x270 [sctp]
   pepe kernel: [  457.681179]  ? tty_write_unlock+0x2a/0x30
   pepe kernel: [  457.729224]  ? tty_ldisc_deref+0x13/0x20
   pepe kernel: [  457.776127]  inet_release+0x2f/0x60
   pepe kernel: [  457.818040]  inet6_release+0x28/0x40
   pepe kernel: [  457.860783]  __sock_release+0x32/0xb0
   pepe kernel: [  457.904565]  sock_close+0x12/0x20
   pepe kernel: [  457.944190]  __fput+0xb3/0x240
   pepe kernel: [  457.980694]  fput+0xd/0x10
   pepe kernel: [  458.017302]  task_work_run+0x82/0xa0
   pepe kernel: [  458.060044]  exit_to_usermode_loop+0xed/0x110
   pepe kernel: [  458.112251]  do_fast_syscall_32+0x1c7/0x240
   pepe kernel: [  458.162275]  entry_SYSENTER_32+0xac/0xff
   pepe kernel: [  458.209176] EIP: 0xb7ef5bb5
   pepe kernel: [  458.242666] Code: d3 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 b8 
00 09 3d 00 eb b5 8b 04 24 c3 8b 1c 24 c3 8b 34 24 c3 90 51 52 55 89 e5 0f 34 
cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 

[Kernel-packages] [Bug 1897894] CurrentDmesg.txt

[Po-Hsu Lin]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1897894/+attachment/5415645/+files/CurrentDmesg.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/1897894

Title:
  bind04 from ubuntu_ltp_syscalls caused kernel NULL pointer dereference
  on B-5.4 i386

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

Bug description:
  Issue found on 5.4.0-49.53~18.04.1 i386 node pepe (this issue does not
  exist on other arhces)

  bind04 test will cause kernel NULL pointer dereference and taints the
  kernel, making other tests to fail.

  Test output:
  <<>>
  incrementing stop
  tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
  bind04.c:117: TINFO: Testing AF_UNIX pathname stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX pathname seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop SCTP
  bind04.c:150: TPASS: Communication successful
  tst_test.c:1295: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1296: TBROK: Test killed! (timeout?)

  Summary:
  passed   13
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=2 corefile=no
  cutime=40 cstime=324
  <<>>

  syslog output:
   pepe kernel: [  456.420474] LTP: starting bind04
   pepe kernel: [  456.451023] sctp: Hash tables configured (bind 512/512)
   pepe kernel: [  456.452997] BUG: kernel NULL pointer dereference, address: 
0008
   pepe kernel: [  456.528037] #PF: supervisor read access in kernel mode
   pepe kernel: [  456.589500] #PF: error_code(0x) - not-present page
   pepe kernel: [  456.651172] *pdpt = 220e0001 *pde = 
   pepe kernel: [  456.720122] Oops:  [#1] SMP PTI
   pepe kernel: [  456.761828] CPU: 1 PID: 9783 Comm: bind04 Not tainted 
5.4.0-48-generic #52~18.04.1-Ubuntu
   pepe kernel: [  456.859798] Hardware name: Dell Inc. PowerEdge R310/05XKKK, 
BIOS 1.8.2 08/17/2011
   pepe kernel: [  456.949345] EIP: sctp_ulpevent_free+0x24/0x70 [sctp]
   pepe kernel: [  457.008824] Code: 52 67 71 e3 66 90 66 66 66 66 90 55 89 e5 
57 56 53 66 83 78 20 00 89 c3 78 3b 8b 78 3c 8b 40 40 85 c0 74 20 8b 83 88 00 
00 00 <8b> 70 08 85 f6 74 13 90 8d 74 26 00 8d 46 18 e8 48 ec ff ff 8b 36
   pepe kernel: [  457.233564] EAX:  EBX: e239aa20 ECX: 0246 EDX: 
e239aa08
   pepe kernel: [  457.308755] ESI: e1c02a08 EDI:  EBP: e5661eac ESP: 
e5661ea0
   pepe kernel: [  457.383798] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010202
   pepe kernel: [  457.465170] CR0: 80050033 CR2: 0008 CR3: 25602000 CR4: 
06f0
   pepe kernel: [  457.540361] Call Trace:
   pepe kernel: [  457.569594]  sctp_queue_purge_ulpevents+0x22/0x40 [sctp]
   pepe kernel: [  457.633241]  sctp_close+0x69/0x270 [sctp]
   pepe kernel: [  457.681179]  ? tty_write_unlock+0x2a/0x30
   pepe kernel: [  457.729224]  ? tty_ldisc_deref+0x13/0x20
   pepe kernel: [  457.776127]  inet_release+0x2f/0x60
   pepe kernel: [  457.818040]  inet6_release+0x28/0x40
   pepe kernel: [  457.860783]  __sock_release+0x32/0xb0
   pepe kernel: [  457.904565]  sock_close+0x12/0x20
   pepe kernel: [  457.944190]  __fput+0xb3/0x240
   pepe kernel: [  457.980694]  fput+0xd/0x10
   pepe kernel: [  458.017302]  task_work_run+0x82/0xa0
   pepe kernel: [  458.060044]  exit_to_usermode_loop+0xed/0x110
   pepe kernel: [  458.112251]  do_fast_syscall_32+0x1c7/0x240
   pepe kernel: [  458.162275]  entry_SYSENTER_32+0xac/0xff
   pepe kernel: [  458.209176] EIP: 0xb7ef5bb5
   pepe kernel: [  458.242666] Code: d3 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 b8 
00 09 3d 00 eb b5 8b 04 24 c3 8b 1c 24 c3 8b 34 24 c3 90 51 52 55 89 e5 0f 34 
cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 

[Kernel-packages] [Bug 1897894] Lspci.txt

[Po-Hsu Lin]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1897894/+attachment/5415646/+files/Lspci.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/1897894

Title:
  bind04 from ubuntu_ltp_syscalls caused kernel NULL pointer dereference
  on B-5.4 i386

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

Bug description:
  Issue found on 5.4.0-49.53~18.04.1 i386 node pepe (this issue does not
  exist on other arhces)

  bind04 test will cause kernel NULL pointer dereference and taints the
  kernel, making other tests to fail.

  Test output:
  <<>>
  incrementing stop
  tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
  bind04.c:117: TINFO: Testing AF_UNIX pathname stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX pathname seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop SCTP
  bind04.c:150: TPASS: Communication successful
  tst_test.c:1295: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1296: TBROK: Test killed! (timeout?)

  Summary:
  passed   13
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=2 corefile=no
  cutime=40 cstime=324
  <<>>

  syslog output:
   pepe kernel: [  456.420474] LTP: starting bind04
   pepe kernel: [  456.451023] sctp: Hash tables configured (bind 512/512)
   pepe kernel: [  456.452997] BUG: kernel NULL pointer dereference, address: 
0008
   pepe kernel: [  456.528037] #PF: supervisor read access in kernel mode
   pepe kernel: [  456.589500] #PF: error_code(0x) - not-present page
   pepe kernel: [  456.651172] *pdpt = 220e0001 *pde = 
   pepe kernel: [  456.720122] Oops:  [#1] SMP PTI
   pepe kernel: [  456.761828] CPU: 1 PID: 9783 Comm: bind04 Not tainted 
5.4.0-48-generic #52~18.04.1-Ubuntu
   pepe kernel: [  456.859798] Hardware name: Dell Inc. PowerEdge R310/05XKKK, 
BIOS 1.8.2 08/17/2011
   pepe kernel: [  456.949345] EIP: sctp_ulpevent_free+0x24/0x70 [sctp]
   pepe kernel: [  457.008824] Code: 52 67 71 e3 66 90 66 66 66 66 90 55 89 e5 
57 56 53 66 83 78 20 00 89 c3 78 3b 8b 78 3c 8b 40 40 85 c0 74 20 8b 83 88 00 
00 00 <8b> 70 08 85 f6 74 13 90 8d 74 26 00 8d 46 18 e8 48 ec ff ff 8b 36
   pepe kernel: [  457.233564] EAX:  EBX: e239aa20 ECX: 0246 EDX: 
e239aa08
   pepe kernel: [  457.308755] ESI: e1c02a08 EDI:  EBP: e5661eac ESP: 
e5661ea0
   pepe kernel: [  457.383798] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010202
   pepe kernel: [  457.465170] CR0: 80050033 CR2: 0008 CR3: 25602000 CR4: 
06f0
   pepe kernel: [  457.540361] Call Trace:
   pepe kernel: [  457.569594]  sctp_queue_purge_ulpevents+0x22/0x40 [sctp]
   pepe kernel: [  457.633241]  sctp_close+0x69/0x270 [sctp]
   pepe kernel: [  457.681179]  ? tty_write_unlock+0x2a/0x30
   pepe kernel: [  457.729224]  ? tty_ldisc_deref+0x13/0x20
   pepe kernel: [  457.776127]  inet_release+0x2f/0x60
   pepe kernel: [  457.818040]  inet6_release+0x28/0x40
   pepe kernel: [  457.860783]  __sock_release+0x32/0xb0
   pepe kernel: [  457.904565]  sock_close+0x12/0x20
   pepe kernel: [  457.944190]  __fput+0xb3/0x240
   pepe kernel: [  457.980694]  fput+0xd/0x10
   pepe kernel: [  458.017302]  task_work_run+0x82/0xa0
   pepe kernel: [  458.060044]  exit_to_usermode_loop+0xed/0x110
   pepe kernel: [  458.112251]  do_fast_syscall_32+0x1c7/0x240
   pepe kernel: [  458.162275]  entry_SYSENTER_32+0xac/0xff
   pepe kernel: [  458.209176] EIP: 0xb7ef5bb5
   pepe kernel: [  458.242666] Code: d3 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 b8 
00 09 3d 00 eb b5 8b 04 24 c3 8b 1c 24 c3 8b 34 24 c3 90 51 52 55 89 e5 0f 34 
cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76
   

[Kernel-packages] [Bug 1897894] ProcInterrupts.txt

[Po-Hsu Lin]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1897894/+attachment/5415650/+files/ProcInterrupts.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/1897894

Title:
  bind04 from ubuntu_ltp_syscalls caused kernel NULL pointer dereference
  on B-5.4 i386

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

Bug description:
  Issue found on 5.4.0-49.53~18.04.1 i386 node pepe (this issue does not
  exist on other arhces)

  bind04 test will cause kernel NULL pointer dereference and taints the
  kernel, making other tests to fail.

  Test output:
  <<>>
  incrementing stop
  tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
  bind04.c:117: TINFO: Testing AF_UNIX pathname stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX pathname seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop SCTP
  bind04.c:150: TPASS: Communication successful
  tst_test.c:1295: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1296: TBROK: Test killed! (timeout?)

  Summary:
  passed   13
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=2 corefile=no
  cutime=40 cstime=324
  <<>>

  syslog output:
   pepe kernel: [  456.420474] LTP: starting bind04
   pepe kernel: [  456.451023] sctp: Hash tables configured (bind 512/512)
   pepe kernel: [  456.452997] BUG: kernel NULL pointer dereference, address: 
0008
   pepe kernel: [  456.528037] #PF: supervisor read access in kernel mode
   pepe kernel: [  456.589500] #PF: error_code(0x) - not-present page
   pepe kernel: [  456.651172] *pdpt = 220e0001 *pde = 
   pepe kernel: [  456.720122] Oops:  [#1] SMP PTI
   pepe kernel: [  456.761828] CPU: 1 PID: 9783 Comm: bind04 Not tainted 
5.4.0-48-generic #52~18.04.1-Ubuntu
   pepe kernel: [  456.859798] Hardware name: Dell Inc. PowerEdge R310/05XKKK, 
BIOS 1.8.2 08/17/2011
   pepe kernel: [  456.949345] EIP: sctp_ulpevent_free+0x24/0x70 [sctp]
   pepe kernel: [  457.008824] Code: 52 67 71 e3 66 90 66 66 66 66 90 55 89 e5 
57 56 53 66 83 78 20 00 89 c3 78 3b 8b 78 3c 8b 40 40 85 c0 74 20 8b 83 88 00 
00 00 <8b> 70 08 85 f6 74 13 90 8d 74 26 00 8d 46 18 e8 48 ec ff ff 8b 36
   pepe kernel: [  457.233564] EAX:  EBX: e239aa20 ECX: 0246 EDX: 
e239aa08
   pepe kernel: [  457.308755] ESI: e1c02a08 EDI:  EBP: e5661eac ESP: 
e5661ea0
   pepe kernel: [  457.383798] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010202
   pepe kernel: [  457.465170] CR0: 80050033 CR2: 0008 CR3: 25602000 CR4: 
06f0
   pepe kernel: [  457.540361] Call Trace:
   pepe kernel: [  457.569594]  sctp_queue_purge_ulpevents+0x22/0x40 [sctp]
   pepe kernel: [  457.633241]  sctp_close+0x69/0x270 [sctp]
   pepe kernel: [  457.681179]  ? tty_write_unlock+0x2a/0x30
   pepe kernel: [  457.729224]  ? tty_ldisc_deref+0x13/0x20
   pepe kernel: [  457.776127]  inet_release+0x2f/0x60
   pepe kernel: [  457.818040]  inet6_release+0x28/0x40
   pepe kernel: [  457.860783]  __sock_release+0x32/0xb0
   pepe kernel: [  457.904565]  sock_close+0x12/0x20
   pepe kernel: [  457.944190]  __fput+0xb3/0x240
   pepe kernel: [  457.980694]  fput+0xd/0x10
   pepe kernel: [  458.017302]  task_work_run+0x82/0xa0
   pepe kernel: [  458.060044]  exit_to_usermode_loop+0xed/0x110
   pepe kernel: [  458.112251]  do_fast_syscall_32+0x1c7/0x240
   pepe kernel: [  458.162275]  entry_SYSENTER_32+0xac/0xff
   pepe kernel: [  458.209176] EIP: 0xb7ef5bb5
   pepe kernel: [  458.242666] Code: d3 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 b8 
00 09 3d 00 eb b5 8b 04 24 c3 8b 1c 24 c3 8b 34 24 c3 90 51 52 55 89 e5 0f 34 
cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 

[Kernel-packages] [Bug 1897894] CRDA.txt

[Po-Hsu Lin]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1897894/+attachment/5415644/+files/CRDA.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/1897894

Title:
  bind04 from ubuntu_ltp_syscalls caused kernel NULL pointer dereference
  on B-5.4 i386

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

Bug description:
  Issue found on 5.4.0-49.53~18.04.1 i386 node pepe (this issue does not
  exist on other arhces)

  bind04 test will cause kernel NULL pointer dereference and taints the
  kernel, making other tests to fail.

  Test output:
  <<>>
  incrementing stop
  tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
  bind04.c:117: TINFO: Testing AF_UNIX pathname stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX pathname seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop SCTP
  bind04.c:150: TPASS: Communication successful
  tst_test.c:1295: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1296: TBROK: Test killed! (timeout?)

  Summary:
  passed   13
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=2 corefile=no
  cutime=40 cstime=324
  <<>>

  syslog output:
   pepe kernel: [  456.420474] LTP: starting bind04
   pepe kernel: [  456.451023] sctp: Hash tables configured (bind 512/512)
   pepe kernel: [  456.452997] BUG: kernel NULL pointer dereference, address: 
0008
   pepe kernel: [  456.528037] #PF: supervisor read access in kernel mode
   pepe kernel: [  456.589500] #PF: error_code(0x) - not-present page
   pepe kernel: [  456.651172] *pdpt = 220e0001 *pde = 
   pepe kernel: [  456.720122] Oops:  [#1] SMP PTI
   pepe kernel: [  456.761828] CPU: 1 PID: 9783 Comm: bind04 Not tainted 
5.4.0-48-generic #52~18.04.1-Ubuntu
   pepe kernel: [  456.859798] Hardware name: Dell Inc. PowerEdge R310/05XKKK, 
BIOS 1.8.2 08/17/2011
   pepe kernel: [  456.949345] EIP: sctp_ulpevent_free+0x24/0x70 [sctp]
   pepe kernel: [  457.008824] Code: 52 67 71 e3 66 90 66 66 66 66 90 55 89 e5 
57 56 53 66 83 78 20 00 89 c3 78 3b 8b 78 3c 8b 40 40 85 c0 74 20 8b 83 88 00 
00 00 <8b> 70 08 85 f6 74 13 90 8d 74 26 00 8d 46 18 e8 48 ec ff ff 8b 36
   pepe kernel: [  457.233564] EAX:  EBX: e239aa20 ECX: 0246 EDX: 
e239aa08
   pepe kernel: [  457.308755] ESI: e1c02a08 EDI:  EBP: e5661eac ESP: 
e5661ea0
   pepe kernel: [  457.383798] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010202
   pepe kernel: [  457.465170] CR0: 80050033 CR2: 0008 CR3: 25602000 CR4: 
06f0
   pepe kernel: [  457.540361] Call Trace:
   pepe kernel: [  457.569594]  sctp_queue_purge_ulpevents+0x22/0x40 [sctp]
   pepe kernel: [  457.633241]  sctp_close+0x69/0x270 [sctp]
   pepe kernel: [  457.681179]  ? tty_write_unlock+0x2a/0x30
   pepe kernel: [  457.729224]  ? tty_ldisc_deref+0x13/0x20
   pepe kernel: [  457.776127]  inet_release+0x2f/0x60
   pepe kernel: [  457.818040]  inet6_release+0x28/0x40
   pepe kernel: [  457.860783]  __sock_release+0x32/0xb0
   pepe kernel: [  457.904565]  sock_close+0x12/0x20
   pepe kernel: [  457.944190]  __fput+0xb3/0x240
   pepe kernel: [  457.980694]  fput+0xd/0x10
   pepe kernel: [  458.017302]  task_work_run+0x82/0xa0
   pepe kernel: [  458.060044]  exit_to_usermode_loop+0xed/0x110
   pepe kernel: [  458.112251]  do_fast_syscall_32+0x1c7/0x240
   pepe kernel: [  458.162275]  entry_SYSENTER_32+0xac/0xff
   pepe kernel: [  458.209176] EIP: 0xb7ef5bb5
   pepe kernel: [  458.242666] Code: d3 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 b8 
00 09 3d 00 eb b5 8b 04 24 c3 8b 1c 24 c3 8b 34 24 c3 90 51 52 55 89 e5 0f 34 
cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76
   pepe 

[Kernel-packages] [Bug 1897894] [NEW] bind04 from ubuntu_ltp_syscalls caused kernel NULL pointer dereference on B-5.4 i386

[Po-Hsu Lin]

Public bug reported:

Issue found on 5.4.0-49.53~18.04.1 i386 node pepe (this issue does not
exist on other arhces)

bind04 test will cause kernel NULL pointer dereference and taints the
kernel, making other tests to fail.

Test output:
<<>>
incrementing stop
tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
bind04.c:117: TINFO: Testing AF_UNIX pathname stream
bind04.c:150: TPASS: Communication successful
bind04.c:117: TINFO: Testing AF_UNIX pathname seqpacket
bind04.c:150: TPASS: Communication successful
bind04.c:117: TINFO: Testing AF_UNIX abstract stream
bind04.c:150: TPASS: Communication successful
bind04.c:117: TINFO: Testing AF_UNIX abstract seqpacket
bind04.c:150: TPASS: Communication successful
bind04.c:117: TINFO: Testing IPv4 loop TCP variant 1
bind04.c:150: TPASS: Communication successful
bind04.c:117: TINFO: Testing IPv4 loop TCP variant 2
bind04.c:150: TPASS: Communication successful
bind04.c:117: TINFO: Testing IPv4 loop SCTP
bind04.c:150: TPASS: Communication successful
bind04.c:117: TINFO: Testing IPv4 any TCP variant 1
bind04.c:150: TPASS: Communication successful
bind04.c:117: TINFO: Testing IPv4 any TCP variant 2
bind04.c:150: TPASS: Communication successful
bind04.c:117: TINFO: Testing IPv4 any SCTP
bind04.c:150: TPASS: Communication successful
bind04.c:117: TINFO: Testing IPv6 loop TCP variant 1
bind04.c:150: TPASS: Communication successful
bind04.c:117: TINFO: Testing IPv6 loop TCP variant 2
bind04.c:150: TPASS: Communication successful
bind04.c:117: TINFO: Testing IPv6 loop SCTP
bind04.c:150: TPASS: Communication successful
tst_test.c:1295: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
tst_test.c:1296: TBROK: Test killed! (timeout?)

Summary:
passed   13
failed   0
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=3 termination_type=exited termination_id=2 corefile=no
cutime=40 cstime=324
<<>>

syslog output:
 pepe kernel: [  456.420474] LTP: starting bind04
 pepe kernel: [  456.451023] sctp: Hash tables configured (bind 512/512)
 pepe kernel: [  456.452997] BUG: kernel NULL pointer dereference, address: 
0008
 pepe kernel: [  456.528037] #PF: supervisor read access in kernel mode
 pepe kernel: [  456.589500] #PF: error_code(0x) - not-present page
 pepe kernel: [  456.651172] *pdpt = 220e0001 *pde = 
 pepe kernel: [  456.720122] Oops:  [#1] SMP PTI
 pepe kernel: [  456.761828] CPU: 1 PID: 9783 Comm: bind04 Not tainted 
5.4.0-48-generic #52~18.04.1-Ubuntu
 pepe kernel: [  456.859798] Hardware name: Dell Inc. PowerEdge R310/05XKKK, 
BIOS 1.8.2 08/17/2011
 pepe kernel: [  456.949345] EIP: sctp_ulpevent_free+0x24/0x70 [sctp]
 pepe kernel: [  457.008824] Code: 52 67 71 e3 66 90 66 66 66 66 90 55 89 e5 57 
56 53 66 83 78 20 00 89 c3 78 3b 8b 78 3c 8b 40 40 85 c0 74 20 8b 83 88 00 00 
00 <8b> 70 08 85 f6 74 13 90 8d 74 26 00 8d 46 18 e8 48 ec ff ff 8b 36
 pepe kernel: [  457.233564] EAX:  EBX: e239aa20 ECX: 0246 EDX: 
e239aa08
 pepe kernel: [  457.308755] ESI: e1c02a08 EDI:  EBP: e5661eac ESP: 
e5661ea0
 pepe kernel: [  457.383798] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010202
 pepe kernel: [  457.465170] CR0: 80050033 CR2: 0008 CR3: 25602000 CR4: 
06f0
 pepe kernel: [  457.540361] Call Trace:
 pepe kernel: [  457.569594]  sctp_queue_purge_ulpevents+0x22/0x40 [sctp]
 pepe kernel: [  457.633241]  sctp_close+0x69/0x270 [sctp]
 pepe kernel: [  457.681179]  ? tty_write_unlock+0x2a/0x30
 pepe kernel: [  457.729224]  ? tty_ldisc_deref+0x13/0x20
 pepe kernel: [  457.776127]  inet_release+0x2f/0x60
 pepe kernel: [  457.818040]  inet6_release+0x28/0x40
 pepe kernel: [  457.860783]  __sock_release+0x32/0xb0
 pepe kernel: [  457.904565]  sock_close+0x12/0x20
 pepe kernel: [  457.944190]  __fput+0xb3/0x240
 pepe kernel: [  457.980694]  fput+0xd/0x10
 pepe kernel: [  458.017302]  task_work_run+0x82/0xa0
 pepe kernel: [  458.060044]  exit_to_usermode_loop+0xed/0x110
 pepe kernel: [  458.112251]  do_fast_syscall_32+0x1c7/0x240
 pepe kernel: [  458.162275]  entry_SYSENTER_32+0xac/0xff
 pepe kernel: [  458.209176] EIP: 0xb7ef5bb5
 pepe kernel: [  458.242666] Code: d3 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 b8 00 
09 3d 00 eb b5 8b 04 24 c3 8b 1c 24 c3 8b 34 24 c3 90 51 52 55 89 e5 0f 34 cd 
80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76
 pepe kernel: [  458.467405] EAX:  EBX: 0007 ECX: 0002 EDX: 

 pepe kernel: [  458.542597] ESI: b7ee4000 EDI: 0006 EBP: 004b1210 ESP: 
bfebe150
 pepe kernel: [  458.617789] DS: 007b ES: 007b FS:  GS: 0033 SS: 007b 
EFLAGS: 0293
 pepe kernel: [  458.699012] Modules linked in: sctp nfsd auth_rpcgss nfs_acl 
lockd grace sunrpc intel_powerclamp coretemp kvm_intel kvm irqbypass ipmi_ssif 
gpio_ich intel_cstate lpc_ich dcdbas i7core_edac acpi_power_meter mac_hid 
ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi 

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

[Po-Hsu Lin]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1897894/+attachment/5415648/+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/1897894

Title:
  bind04 from ubuntu_ltp_syscalls caused kernel NULL pointer dereference
  on B-5.4 i386

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

Bug description:
  Issue found on 5.4.0-49.53~18.04.1 i386 node pepe (this issue does not
  exist on other arhces)

  bind04 test will cause kernel NULL pointer dereference and taints the
  kernel, making other tests to fail.

  Test output:
  <<>>
  incrementing stop
  tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s
  bind04.c:117: TINFO: Testing AF_UNIX pathname stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX pathname seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract stream
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing AF_UNIX abstract seqpacket
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 loop SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv4 any SCTP
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 1
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop TCP variant 2
  bind04.c:150: TPASS: Communication successful
  bind04.c:117: TINFO: Testing IPv6 loop SCTP
  bind04.c:150: TPASS: Communication successful
  tst_test.c:1295: TINFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1296: TBROK: Test killed! (timeout?)

  Summary:
  passed   13
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=3 termination_type=exited termination_id=2 corefile=no
  cutime=40 cstime=324
  <<>>

  syslog output:
   pepe kernel: [  456.420474] LTP: starting bind04
   pepe kernel: [  456.451023] sctp: Hash tables configured (bind 512/512)
   pepe kernel: [  456.452997] BUG: kernel NULL pointer dereference, address: 
0008
   pepe kernel: [  456.528037] #PF: supervisor read access in kernel mode
   pepe kernel: [  456.589500] #PF: error_code(0x) - not-present page
   pepe kernel: [  456.651172] *pdpt = 220e0001 *pde = 
   pepe kernel: [  456.720122] Oops:  [#1] SMP PTI
   pepe kernel: [  456.761828] CPU: 1 PID: 9783 Comm: bind04 Not tainted 
5.4.0-48-generic #52~18.04.1-Ubuntu
   pepe kernel: [  456.859798] Hardware name: Dell Inc. PowerEdge R310/05XKKK, 
BIOS 1.8.2 08/17/2011
   pepe kernel: [  456.949345] EIP: sctp_ulpevent_free+0x24/0x70 [sctp]
   pepe kernel: [  457.008824] Code: 52 67 71 e3 66 90 66 66 66 66 90 55 89 e5 
57 56 53 66 83 78 20 00 89 c3 78 3b 8b 78 3c 8b 40 40 85 c0 74 20 8b 83 88 00 
00 00 <8b> 70 08 85 f6 74 13 90 8d 74 26 00 8d 46 18 e8 48 ec ff ff 8b 36
   pepe kernel: [  457.233564] EAX:  EBX: e239aa20 ECX: 0246 EDX: 
e239aa08
   pepe kernel: [  457.308755] ESI: e1c02a08 EDI:  EBP: e5661eac ESP: 
e5661ea0
   pepe kernel: [  457.383798] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
EFLAGS: 00010202
   pepe kernel: [  457.465170] CR0: 80050033 CR2: 0008 CR3: 25602000 CR4: 
06f0
   pepe kernel: [  457.540361] Call Trace:
   pepe kernel: [  457.569594]  sctp_queue_purge_ulpevents+0x22/0x40 [sctp]
   pepe kernel: [  457.633241]  sctp_close+0x69/0x270 [sctp]
   pepe kernel: [  457.681179]  ? tty_write_unlock+0x2a/0x30
   pepe kernel: [  457.729224]  ? tty_ldisc_deref+0x13/0x20
   pepe kernel: [  457.776127]  inet_release+0x2f/0x60
   pepe kernel: [  457.818040]  inet6_release+0x28/0x40
   pepe kernel: [  457.860783]  __sock_release+0x32/0xb0
   pepe kernel: [  457.904565]  sock_close+0x12/0x20
   pepe kernel: [  457.944190]  __fput+0xb3/0x240
   pepe kernel: [  457.980694]  fput+0xd/0x10
   pepe kernel: [  458.017302]  task_work_run+0x82/0xa0
   pepe kernel: [  458.060044]  exit_to_usermode_loop+0xed/0x110
   pepe kernel: [  458.112251]  do_fast_syscall_32+0x1c7/0x240
   pepe kernel: [  458.162275]  entry_SYSENTER_32+0xac/0xff
   pepe kernel: [  458.209176] EIP: 0xb7ef5bb5
   pepe kernel: [  458.242666] Code: d3 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 b8 
00 09 3d 00 eb b5 8b 04 24 c3 8b 1c 24 c3 8b 34 24 c3 90 51 52 55 89 e5 0f 34 
cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 

[Kernel-packages] [Bug 1886769] Re: [ 0.000000] Initramfs unpacking failed: Decoding failed

[Norbert]

Still happens on Ubuntu MATE 20200930 beta iso. Using virtualbox 6.0.24
with EFI.

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

Title:
  [ 0.00] Initramfs unpacking failed: Decoding failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download MATE Groovy daily (sha256sum = 
7d2fdad36b8fcf0409aa0a484755e5fc5ef3798fd256eeebbde905a71ad474b7 )
  2. Insert ISO into VirtualBox with EFI enabled
  3. Boot VM

  Expected results:
  * VM boots normally

  Actual results:
  * VM hangs during early boot with message

    [ 0.00] Initramfs unpacking failed: Decoding failed

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

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

[Kernel-packages] [Bug 1837005] Re: cve-2015-3290 in cve from ubuntu_ltp failed with B/D-i386

[Po-Hsu Lin]

Still affecting B-5.4 i386

** Tags added: sru-20200921

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

Title:
  cve-2015-3290 in cve from ubuntu_ltp failed with B/D-i386

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New
Status in linux source package in Disco:
  Won't Fix

Bug description:
  This issue was only spotted on an i386 node "pepe" with Disco kernel,
  passed with other arch with Disco.

  On B/C i386, the CVE test was not successfully executed, failed with Resource 
temporarily unavailable.
  Will need to verify this manually.
   
  Test report:
  <<>>
  tag=cve-2015-3290 stime=1563431630
  cmdline="cve-2015-3290"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 03m 00s
  cve-2015-3290.c:407: INFO: attempting to corrupt nested NMI stack state
  cve-2015-3290.c:460: FAIL: corrupted NMI stack

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0

  syslog output:
   06:33:50 pepe kernel: [ 6042.144077] LTP: starting cve-2015-3290
   06:33:50 pepe kernel: [ 6042.159521] perf: interrupt took too long (2518 > 
2500), lowering kernel.perf_event_max_sample_rate to 79250
   06:33:50 pepe kernel: [ 6042.159531] show_signal: 16 callbacks suppressed
   06:33:50 pepe kernel: [ 6042.159532] traps: cve-2015-3290[7761] general 
protection fault ip:46c0ef sp:b7d43280 error:800
   06:33:50 pepe AutotestCrashHandler: Application cve-2015-3290, PID 7760 
crashed
   06:33:50 pepe AutotestCrashHandler: Writing core files to 
['/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760']
   06:33:50 pepe AutotestCrashHandler: Could not determine from which 
application core file 
/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760/core
 is from

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-20-generic 5.0.0-20.21
  ProcVersionSignature: User Name 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 18 04:53 seq
   crw-rw 1 root audio 116, 33 Jul 18 04:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [ 6042.144077] LTP: starting cve-2015-3290
   [ 6042.159521] perf: interrupt took too long (2518 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79250
   [ 6042.159531] show_signal: 16 callbacks suppressed
   [ 6042.159532] traps: cve-2015-3290[7761] general protection fault ip:46c0ef 
sp:b7d43280 error:800
  Date: Thu Jul 18 06:36:51 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R310
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-20-generic N/A
   linux-backports-modules-5.0.0-20-generic  N/A
   linux-firmware1.178.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1837035] Re: memcg_stat_rss from controllers in ubuntu_ltp failed

[Po-Hsu Lin]

Spotted on B-5.4 ARM64

 memcg_stat_rss 4 TINFO: Starting test 4
 sh: echo: I/O error
 memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
 memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 
135168
 memcg_stat_rss 4 TINFO: Warming up pid: 50880
 memcg_process: shmget() failed: Invalid argument
 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process
 
 memcg_stat_rss 4 TFAIL: Process 50880 exited with 1 after warm up


** Tags added: arm64

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

Title:
  memcg_stat_rss from controllers in ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New

Bug description:
  This issue was spotted on an i386 node "pepe" with Disco kernel,
  it failed with:

  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

  memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up

  
  <<>>
  tag=memcg_stat_rss stime=1563448062
  cmdline="memcg_stat_rss.sh"
  contacts=""
  analysis=exit
  <<>>
  memcg_stat_rss 1 TINFO: Starting test 1
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 1 TINFO: Running memcg_process --mmap-anon -s 135168
  memcg_stat_rss 1 TINFO: Warming up pid: 1784
  memcg_stat_rss 1 TINFO: Process is still here after warm up: 1784
  memcg_stat_rss 1 TPASS: rss is 135168 as expected
  memcg_stat_rss 2 TINFO: Starting test 2
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 2 TINFO: Running memcg_process --mmap-file -s 4096
  memcg_stat_rss 2 TINFO: Warming up pid: 1804
  memcg_stat_rss 2 TINFO: Process is still here after warm up: 1804
  memcg_stat_rss 2 TPASS: rss is 0 as expected
  memcg_stat_rss 3 TINFO: Starting test 3
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 3 TINFO: Running memcg_process --shm -k 3 -s 4096
  memcg_stat_rss 3 TINFO: Warming up pid: 1825
  memcg_stat_rss 3 TINFO: Process is still here after warm up: 1825
  memcg_stat_rss 3 TPASS: rss is 0 as expected
  memcg_stat_rss 4 TINFO: Starting test 4
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm 
-s 135168
  memcg_stat_rss 4 TINFO: Warming up pid: 1845
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

  memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up
  memcg_stat_rss 5 TINFO: Starting test 5
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 5 TINFO: Running memcg_process --mmap-lock1 -s 135168
  memcg_stat_rss 5 TINFO: Warming up pid: 1858
  memcg_stat_rss 5 TINFO: Process is still here after warm up: 1858
  memcg_stat_rss 5 TPASS: rss is 135168 as expected
  memcg_stat_rss 6 TINFO: Starting test 6
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 6 TINFO: Running memcg_process --mmap-anon -s 135168
  memcg_stat_rss 6 TINFO: Warming up pid: 1878
  memcg_stat_rss 6 TINFO: Process is still here after warm up: 1878
  memcg_stat_rss 6 TPASS: rss is 135168 as expected
  memcg_stat_rss 7 TPASS: rss is 0 as expected
  memcg_stat_rss 8 TINFO: Starting test 7
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 8 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 8 TINFO: Running memcg_process --mmap-file -s 4096
  memcg_stat_rss 8 TINFO: Warming up pid: 1901
  memcg_stat_rss 8 TINFO: Process is still here after warm up: 1901
  memcg_stat_rss 8 TPASS: rss is 0 as expected
  memcg_stat_rss 9 TPASS: rss is 0 as expected
  memcg_stat_rss 10 TINFO: Starting test 8
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 10 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 10 TINFO: Running memcg_process --shm -k 8 -s 4096
  memcg_stat_rss 10 TINFO: Warming up pid: 1925
  memcg_stat_rss 10 TINFO: Process is still here after warm up: 1925
  memcg_stat_rss 10 TPASS: rss is 0 as expected
  memcg_stat_rss 11 TPASS: rss is 0 as expected
  memcg_stat_rss 12 TINFO: Starting test 9
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  

[Kernel-packages] [Bug 1847982] Re: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E

[Po-Hsu Lin]

Spotted on B-5.4 ARM64
 memcg_subgroup_charge 1 TINFO: Starting test 1
 sh: echo: I/O error
 memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
 memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 135168
 memcg_subgroup_charge 1 TINFO: Warming up pid: 51116
 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 51116
 memcg_subgroup_charge 1 TFAIL: rss is 0, 135168 expected

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

Title:
  memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  Won't Fix
Status in linux-kvm source package in Disco:
  Won't Fix
Status in linux-oracle source package in Disco:
  Won't Fix

Bug description:
  Issue found on Azure Disco kernel 5.0.0-1023.24

  Failed on instance:
* Standard_GS2
* Standard_D16s_v3

  Passed on instance:
* Standard_F32s_v2
* Standard_L8s_v2
* Standard_L4s
* Standard_L8s_v2

  (Although it has passed on these instances, but they all have the same
  test output, just the pids are different)

  
  Test failed with:
    /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error

   tag=memcg_subgroup_charge stime=1570239843 dur=3 exit=exited stat=1 core=no 
cu=7 cs=11
   startup='Sat Oct 5 01:44:03 2019'
   memcg_subgroup_charge 1 TINFO: Starting test 1
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 1 TINFO: Warming up pid: 119041
   memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 119041
   memcg_subgroup_charge 1 TPASS: rss is 135168 as expected
   memcg_subgroup_charge 2 TPASS: rss is 0 as expected
   memcg_subgroup_charge 3 TINFO: Starting test 2
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 3 TINFO: Warming up pid: 119071
   memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 119071
   memcg_subgroup_charge 3 TFAIL: rss is 0, 135168 expected
   memcg_subgroup_charge 4 TPASS: rss is 0 as expected
   memcg_subgroup_charge 5 TINFO: Starting test 3
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 5 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 5 TINFO: Warming up pid: 119094
   memcg_subgroup_charge 5 TINFO: Process is still here after warm up: 119094
   memcg_subgroup_charge 5 TPASS: rss is 135168 as expected
   memcg_subgroup_charge 6 TPASS: rss is 0 as expected

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

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

[Kernel-packages] [Bug 1897299] Re: mwifiex stops working after kernel upgrade

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  mwifiex stops working after kernel upgrade

Status in HWE Next:
  Fix Released
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 Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress

Bug description:
  == Impact ==
  Marvell WiFi cards supported by the mwifiex driver may fail to connect to 
some access points after kernel upgrade.
  This is caused by the commit

  commit e18696786548244914f36ec3c46ac99c53df99c3
  Author: Dan Carpenter 
  Date:   Wed Jul 8 14:58:57 2020 +0300

  mwifiex: Prevent memory corruption handling keys
  
  The length of the key comes from the network and it's a 16 bit number.  It
  needs to be capped to prevent a buffer overflow.
  
  Fixes: 5e6e3a92b9a4 ("wireless: mwifiex: initial commit for Marvell 
mwifiex driver")
  Signed-off-by: Dan Carpenter 
  Acked-by: Ganapathi Bhat 
  Signed-off-by: Kalle Valo 
  Link: https://lore.kernel.org/r/20200708115857.GA13729@mwanda

  The commit added a check to mwifiex_ret_802_11_key_material_v2() to
  make sure the key length doesn't larger than the key buffer size
  before copying it. The allocated key buffer is 16-byte long. In some
  cases the key would be 32-byte long and hence the check fails. One
  thing to note is that this commit is not the cause of the problem,
  instead it just makes the issue visible.

  The commit is included in Ubuntu-4.4.0-190.220, Ubuntu-4.15.0-119.120,
  Ubuntu-5.4.0-48.52, and Ubuntu-5.8.0-18.19.

  == Fix ==
  There's already a fix in the mainline which increase the key buffer size to 
32 bytes:

  commit 4afc850e2e9e781976fb2c7852ce7bac374af938
  Author: Maximilian Luz 
  Date:   Tue Aug 25 17:38:29 2020 +0200

  mwifiex: Increase AES key storage size to 256 bits
  
  Following commit e18696786548 ("mwifiex: Prevent memory corruption
  handling keys") the mwifiex driver fails to authenticate with certain
  networks, specifically networks with 256 bit keys, and repeatedly asks
  for the password. The kernel log repeats the following lines (id and
  bssid redacted):
  
  mwifiex_pcie :01:00.0: info: trying to associate to '' bssid 

  mwifiex_pcie :01:00.0: info: associated to bssid  
successfully
  mwifiex_pcie :01:00.0: crypto keys added
  mwifiex_pcie :01:00.0: info: successfully disconnected from 
: reason code 3
  
  Tracking down this problem lead to the overflow check introduced by the
  aforementioned commit into mwifiex_ret_802_11_key_material_v2(). This
  check fails on networks with 256 bit keys due to the current storage
  size for AES keys in struct mwifiex_aes_param being only 128 bit.
  
  To fix this issue, increase the storage size for AES keys to 256 bit.
  
  Fixes: e18696786548 ("mwifiex: Prevent memory corruption handling keys")
  Signed-off-by: Maximilian Luz 
  Reported-by: Kaloyan Nikolov 
  Tested-by: Kaloyan Nikolov 
  Reviewed-by: Dan Carpenter 
  Reviewed-by: Brian Norris 
  Tested-by: Brian Norris 
  Signed-off-by: Kalle Valo 
  Link: 
https://lore.kernel.org/r/20200825153829.38043-1-luzmaximil...@gmail.com

  == Regression Potential ==
  Low. While the fix increases the buffer size, it still checks and make sure 
data to be copy can fit into the buffer. Also the commit does fix the issue we 
saw in the Cert lab.

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

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

[Kernel-packages] [Bug 1896725] Re: xenial 4.4.0-191-generic in -proposed has a regression

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  xenial 4.4.0-191-generic in -proposed has a regression

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  The new xenial kernel in -proposed, 4.4.0-191-generic, and its
  derivatives, such as 4.4.0-1115-aws suffer a kernel panic on boot on
  AWS.

  I tested t2.micro and t2.medium, it happens every time. Simply install
  the kernel from -proposed and reboot, we get the following oops:

  [0.549557] BUG: unable to handle kernel paging request at ff5f3000
  [0.552000] IP: [] mp_irqdomain_activate+0x5f/0xa0
  [0.552000] PGD 1e0f067 PUD 1e11067 PMD 1e12067 PTE 0
  [0.552000] Oops: 0002 [#1] SMP 
  [0.552000] Modules linked in:
  [0.552000] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-191-generic 
#221-Ubuntu
  [0.552000] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [0.552000] task: 88010a0f ti: 88010a0f8000 task.ti: 
88010a0f8000
  [0.552000] RIP: 0010:[]  [] 
mp_irqdomain_activate+0x5f/0xa0
  [0.552000] RSP: :88010a0fbc48  EFLAGS: 00010086
  [0.552000] RAX: 0086 RBX: 88010a1df480 RCX: 

  [0.552000] RDX: ff5f3000 RSI: 0001 RDI: 
0020c000
  [0.552000] RBP: 88010a0fbc50 R08: 81ebdfd0 R09: 

  [0.552000] R10: 0011 R11: 0009 R12: 
88010ad95400
  [0.552000] R13: 0001 R14: 0009 R15: 
88010a1fc480
  [0.552000] FS:  () GS:88010b24() 
knlGS:
  [0.552000] CS:  0010 DS:  ES:  CR0: 80050033
  [0.552000] CR2: ff5f3000 CR3: 01e0a000 CR4: 
00160670
  [0.552000] DR0:  DR1:  DR2: 

  [0.552000] DR3:  DR6: fffe0ff0 DR7: 
0400
  [0.552000] Stack:
  [0.552000]  88010ac0ba58 88010a0fbc70 810ea644 
88010ac0ba00
  [0.552000]  88010ac0ba58 88010a0fbca0 810e6d88 
810e1009
  [0.552000]  88010ac0ba00 88010ac0baa0 88010a1fc480 
88010a0fbd38
  [0.552000] Call Trace:
  [0.552000]  [] irq_domain_activate_irq+0x44/0x50
  [0.552000]  [] irq_startup+0x38/0x90
  [0.552000]  [] ? vprintk_default+0x29/0x40
  [0.552000]  [] __setup_irq+0x5a2/0x650
  [0.552000]  [] ? kmem_cache_alloc_trace+0x1d4/0x1f0
  [0.552000]  [] ? acpi_osi_handler+0xb0/0xb0
  [0.552000]  [] request_threaded_irq+0xfb/0x1a0
  [0.552000]  [] ? acpi_osi_handler+0xb0/0xb0
  [0.552000]  [] ? acpi_ev_sci_dispatch+0x64/0x64
  [0.552000]  [] 
acpi_os_install_interrupt_handler+0xaa/0x100
  [0.552000]  [] ? acpi_sleep_proc_init+0x28/0x28
  [0.552000]  [] acpi_ev_install_sci_handler+0x23/0x25
  [0.552000]  [] acpi_ev_install_xrupt_handlers+0x1c/0x6c
  [0.552000]  [] acpi_enable_subsystem+0x8f/0x93
  [0.552000]  [] acpi_init+0x8b/0x2c4
  [0.552000]  [] ? kasprintf+0x4e/0x70
  [0.552000]  [] ? acpi_sleep_proc_init+0x28/0x28
  [0.552000]  [] do_one_initcall+0xb5/0x200
  [0.552000]  [] ? parse_args+0x29a/0x4a0
  [0.552000]  [] kernel_init_freeable+0x177/0x218
  [0.552000]  [] ? rest_init+0x80/0x80
  [0.552000]  [] kernel_init+0xe/0xe0
  [0.552000]  [] ret_from_fork+0x55/0x80
  [0.552000]  [] ? rest_init+0x80/0x80
  [0.552000] Code: 8d 1c d2 8d ba 0b 02 00 00 44 8d 51 11 42 8b 14 dd 74 ec 
10 82 c1 e7 0c 48 63 ff 81 e2 ff 0f 00 00 48 81 ea 00 10 80 00 48 29 fa <44> 89 
12 89 72 10 42 8b 14 dd 74 ec 10 82 83 c1 10 81 e2 ff 0f 
  [0.552000] RIP  [] mp_irqdomain_activate+0x5f/0xa0
  [0.996006]  RSP 
  [0.996006] CR2: ff5f3000
  [0.996006] ---[ end trace 1d0c3bd610d641a0 ]---
  [1.012018] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1892855] Re: [Potential Regression] hyperv_connections / hyperv_stimer / hyperv_synic failed on B-i386

[Po-Hsu Lin]

Affecting B-5.4 i386 as well

** Tags added: 5.4 sru-20200921

** Summary changed:

- [Potential Regression] hyperv_connections / hyperv_stimer / hyperv_synic 
failed on B-i386
+ [Potential Regression] hyperv_connections / hyperv_stimer / hyperv_synic 
failed on B-i386 / B-5.4 i386

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

Title:
  [Potential Regression] hyperv_connections / hyperv_stimer /
  hyperv_synic failed on B-i386 / B-5.4 i386

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

Bug description:
  Issue found on 4.15.0-114.115, with i386 generic /lowlatency on node
  fozzie.

  All 3 tests failed with timeout issue:
  * hyperv_connections
   timeout -k 1s --foreground 90s /usr/bin/qemu-system-i386 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.UwdQ0PZort -smp 2 
-cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd 
/tmp/tmp.GNmO7BfE7a
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   enabling apic
   enabling apic
   paging enabled
   cr0 = 80010011
   cr3 = 453000
   cr4 = 10
   EAX=00459001 EBX=0040aae0 ECX=4083 EDX=
   ESI= EDI= EBP=0044b158 ESP=0044b130
   EIP=004006b9 EFL=0202 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
   ES =0010   00c09300 DPL=0 DS [-WA]
   CS =0008   00c09b00 DPL=0 CS32 [-RA]
   SS =0010   00c09300 DPL=0 DS [-WA]
   DS =0010   00c09300 DPL=0 DS [-WA]
   FS =0010   00c09300 DPL=0 DS [-WA]
   GS =0010 0044a1f0  00c09300 DPL=0 DS [-WA]
   LDT=   8200 DPL=0 LDT
   TR =0080 00406280  8b00 DPL=0 TSS32-busy
   GDT= 00406000 027f
   IDT=  0fff
   CR0=80010011 CR2= CR3=00453000 CR4=0010
   DR0= DR1= DR2=664fb17c DR3=
   DR6=0ff0 DR7=0400
   EFER=
   Code=87 e0 aa 40 00 83 c8 01 ba 00 00 00 00 b9 83 00 00 40 0f 30 <8b> 43 04 
83 c8 01 b9 82 00 00 40 0f 30 b8 01 00 00 00 b9 80 00 00 40 0f 30 83 c4 0c 0f b6
   qemu-system-i386: terminating on signal 15 from pid 12753 (timeout)
   FAIL hyperv_connections (timeout; duration=90s)

  * hyperv_stimer
   timeout -k 1s --foreground 90s /usr/bin/qemu-system-i386 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.P9Uky1nZUD -smp 2 
-cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # 
-initrd /tmp/tmp.uulivUIlYy
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   enabling apic
   enabling apic
   paging enabled
   cr0 = 80010011
   cr3 = 453000
   cr4 = 10
   enabling apic
   cpus = 2
   EAX=00458001 EBX=0040aa9c ECX=4083 EDX=
   ESI= EDI=0004 EBP=0044aab8 ESP=0044aaa0
   EIP=0040070c EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
   ES =0010   00c09300 DPL=0 DS [-WA]
   CS =0008   00c09b00 DPL=0 CS32 [-RA]
   SS =0010   00c09300 DPL=0 DS [-WA]
   DS =0010   00c09300 DPL=0 DS [-WA]
   FS =0010   00c09300 DPL=0 DS [-WA]
   GS =0010 00449b60  00c09300 DPL=0 DS [-WA]
   LDT=   8200 DPL=0 LDT
   TR =0080 00406280  8b00 DPL=0 TSS32-busy
   GDT= 00406000 027f
   IDT=  0fff
   CR0=80010011 CR2= CR3=00453000 CR4=0010
   DR0= DR1= DR2=4036d141 DR3=
   DR6=0ff0 DR7=0400
   EFER=
   Code=86 64 aa 40 00 83 c8 01 ba 00 00 00 00 b9 83 00 00 40 0f 30 01 00 00 00 
b9 80 00 00 40 0f 30 83 ec 04 6a 00 68 f1 00 00 00 6a 02 e8 ac 02 00 00 83
   EAX=00459001 EBX=0040aad8 ECX=4083 EDX=
   ESI=003c EDI=0004 EBP=0009ffbc ESP=0009ffa4
   EIP=0040070c EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
   ES =0010   00c09300 DPL=0 DS [-WA]
   CS =0008   00c09b00 DPL=0 CS32 [-RA]
   SS =0010   00c09300 DPL=0 DS [-WA]
   

[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting

[Christian Ehrhardt ]

On a system affected by the issue I was upgrading to focal-proposed:

The time on ZFS got down from >20sec to ~<2sec now and in ps I can catch
it is back on metadata as intended:

$ ps axlf | grep -e qemu-img | grep -v grep
0 0   48981   11928  20   0 164860  5020 ?  Sl   ?  0:00  \_ 
/usr/bin/qemu-img create -f qcow2 -o 
preallocation=metadata,compat=1.1,lazy_refcounts 
/var/lib/libvirt/images/ubuntu20.04.qcow2 15728640K

Setting verified

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

Title:
  very slow disk creation, snapshotting

Status in virt-manager:
  Fix Released
Status in Native ZFS for Linux:
  New
Status in libvirt package in Ubuntu:
  Triaged
Status in virt-manager package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  New
Status in libvirt source package in Bionic:
  Invalid
Status in virt-manager source package in Bionic:
  Invalid
Status in zfs-linux source package in Bionic:
  Won't Fix
Status in libvirt source package in Disco:
  Won't Fix
Status in virt-manager source package in Disco:
  Won't Fix
Status in zfs-linux source package in Disco:
  Won't Fix
Status in libvirt source package in Focal:
  Triaged
Status in virt-manager source package in Focal:
  Fix Committed
Status in libvirt source package in Groovy:
  Triaged

Bug description:
  [Impact]

   * The defaults of virt-manager for disk allocation always worked fine
     when qcow2 had nothing but sparse support. So sparse=True vs
     sparse=False made no difference. So it always set sparse=False.
     Then qcow2 grows non-sparse support, and virt-manager is suddenly
     defaulting to it, which is not the intention.

   * For upgraders from pre-Focal this was a regression in two ways:
  a) allocation of qcow changed to non-sparse (fallocate based)
     potentially consuming more space
  b) depending on the underlying FS this made the allocation much
     slower

   * Fix by applying the upstream change that Defaults to sparse when
     requested format isn't raw (for raw the assumption ill stay that
     users do that for runtime performance, so non-sparse on those stays
     as-is)

  [Test Case]

   * open virt-manager and create a new guest which includes creating a
     new image for it
     * when clicking "finish" the image will be created (which e.g. on ZFS
   will take quite some time)
     * In the background grep ps output if the qemu-img call for qcow (the
   default) is using "preallocation=fallocate" (wrong) or
   "preallocation=metadata" (correct)

  [Regression Potential]

   * For upgraders from pre-focal it actually ensures behavior stays as is
     (no change/regression there)
   * For users of ZFS where the allocation was slow it fixes this
     slowness.
   * But for people using Focal all the time and on non-ZFS there will be
     a behavior change in no more doing falloc pre-allocating the qemu
     image. To be cleear there are four modes:
     1. no allocation
     2. metadata allocation - is initially larger but can improve
    performance when the image needs to grow
     3. falloc - preallocates space for image by calling posix_fallocate
     4. full - writes data to the underlying storage
     The fix changes the default from 3->2 which it always was and should
     be. As the patch says: "If users want to override it, they can
     do it via custom created storage."
     (To be clear, upstream changed this as we fixed it here, so on
  further upgrades what we apply here will be the behavior anyway, it
  seems wrong to keep Focal the only one in between kept different)
   * [racb] The code path being added special cases the 'raw' format and in 
handling of the default sparse setting. Areas of potential regression are 
therefore in the handling of the default and override of the default in the 
cases of both 'raw' and not 'raw'.

  [Other Info]

   * The slowness effect might be further mitigated by ZFS implementing
     more falloc options (thanks Richard for that hint) but that won't be
     in Focal.

  

  This is a regression in eoan for me. I use virt-manager to create vms,
  and I noticed that creating one now takes more than a minute.

  Looking at the process listing while the backing disk is being created, I see 
this qemu-img command line:
  15658 ?Ssl0:00 /usr/sbin/libvirtd
  23726 ?Sl 0:04  \_ /usr/bin/qemu-img create -f qcow2 -o 
preallocation=falloc,compat=1.1,lazy_refcounts 
/var/lib/libvirt/images/live-server.qcow2 41943040K

  If I run qemu-img with that preallocation parameter set, even on
  bionic, then it also takes a very long time.

  On eoan, for comparison:
  andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G
  

[Kernel-packages] [Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Christian Ehrhardt ]

Before:
qemu-system-x86_64 -cpu ? | grep EPYC
x86 EPYC  (alias configured by machine type)  
x86 EPYC-IBPB (alias of EPYC-v2)  
x86 EPYC-v1   AMD EPYC Processor  
x86 EPYC-v2   AMD EPYC Processor (with IBPB)

Upgrade:
...
Setting up qemu-system-data (1:4.2-3ubuntu6.7) ...
Setting up libgfortran5:amd64 (10.2.0-5ubuntu1~20.04) ...
Setting up libubsan1:amd64 (10.2.0-5ubuntu1~20.04) ...
Setting up python3.8-minimal (3.8.5-1~20.04) ...
Setting up gdbserver (9.2-0ubuntu1~20.04) ...
Setting up language-selector-common (0.204.2) ...
Setting up build-essential (12.8ubuntu1.1) ...
Setting up libpython3.8-stdlib:amd64 (3.8.5-1~20.04) ...
Setting up python3.8 (3.8.5-1~20.04) ...
Setting up python3-lib2to3 (3.8.5-1~20.04.1) ...
find: ‘/usr/lib/python3.7/lib2to3’: No such file or directory
find: ‘/usr/lib/python3.7/lib2to3’: No such file or directory
find: ‘/usr/lib/python3.7’: No such file or directory
Setting up qemu-block-extra:amd64 (1:4.2-3ubuntu6.7) ...
Setting up libcc1-0:amd64 (10.2.0-5ubuntu1~20.04) ...
Setting up liblsan0:amd64 (10.2.0-5ubuntu1~20.04) ...
Setting up mdadm (4.1-5ubuntu1.2) ...
update-initramfs: deferring update (trigger activated)
Created symlink 
/etc/systemd/system/mdmonitor.service.wants/mdcheck_continue.timer → 
/lib/systemd/system/mdcheck_continue.timer.
Setting up libitm1:amd64 (10.2.0-5ubuntu1~20.04) ...
Setting up bolt (0.8-4ubuntu1) ...
Setting up gcc-9-base:amd64 (9.3.0-17ubuntu1~20.04) ...
Setting up libgcc-s1-arm64-cross (10.2.0-5ubuntu1~20.04cross1) ...
Setting up libtsan0:amd64 (10.2.0-5ubuntu1~20.04) ...
Setting up libatomic1-arm64-cross (10.2.0-5ubuntu1~20.04cross1) ...
Setting up python3-distutils (3.8.5-1~20.04.1) ...
find: ‘/usr/lib/python3.7/distutils’: No such file or directory
find: ‘/usr/lib/python3.7/distutils’: No such file or directory
find: ‘/usr/lib/python3.7’: No such file or directory
Setting up libgomp1-armhf-cross (10.2.0-5ubuntu1~20.04cross1) ...
Setting up liblsan0-arm64-cross (10.2.0-5ubuntu1~20.04cross1) ...
Setting up libgomp1-arm64-cross (10.2.0-5ubuntu1~20.04cross1) ...
Setting up qemu-system-common (1:4.2-3ubuntu6.7) ...
Setting up cpp-9-arm-linux-gnueabihf (9.3.0-17ubuntu1~20.04cross2) ...
Setting up libgcc-s1-armhf-cross (10.2.0-5ubuntu1~20.04cross1) ...
Setting up qemu-system-mips (1:4.2-3ubuntu6.7) ...
Setting up libpython3.8-dbg:amd64 (3.8.5-1~20.04) ...
Setting up libtsan0-arm64-cross (10.2.0-5ubuntu1~20.04cross1) ...
Setting up qemu-system-x86 (1:4.2-3ubuntu6.7) ...
...

After:
qemu-system-x86_64 -cpu ? | grep EPYC
x86 EPYC  (alias configured by machine type)  
x86 EPYC-IBPB (alias of EPYC-v2)  
x86 EPYC-Rome (alias configured by machine type)  
x86 EPYC-Rome-v1  AMD EPYC-Rome Processor 
x86 EPYC-v1   AMD EPYC Processor  
x86 EPYC-v2   AMD EPYC Processor (with IBPB)  
x86 EPYC-v3   AMD EPYC Processor

Marking as verified.

@Markus - if you could give this a better test on your systems with the
respective HW as well that would be awesome.

P.S. as expected libvirt can make use of EPYC-v3 but not Rome yet.
$ virsh domcapabilities | grep EPYC
  EPYC-IBPB
  EPYC

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

Title:
  Add/Backport EPYC-v3 and EPYC-Rome CPU model

Status in libvirt package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Fix Released
Status in libvirt source package in Focal:
  Incomplete
Status in linux source package in Focal:
  Fix Committed
Status in qemu source package in Focal:
  Fix Committed

Bug description:
  ## Qemu SRU ##

  [Impact]

   * CPU definitions are added to qemu as these CPUs are known.
 And due to that over time are missing in former releases.

   * To really benefit from the new features of these chips
 they have to be known, therefore new type additions done by
 upstream should be backported if they generally apply and do
 not depend on SRU-critical changes.

   * This backports two upstream fixes that just add definitions (no
 control flow changes)

  [Test Case]

   * Probe qemu for the known CPU types (works on all HW)
 $ qemu-system-x86_64 -cpu ? | grep EPYC
 Focal without fix:
 x86 EPYC  (alias configured by machine type)  
 x86 EPYC-IBPB (alias of EPYC-v2)  
 x86 EPYC-v1   AMD EPYC Processor  
 x86 EPYC-v2   AMD EPYC Processor 

[Kernel-packages] [Bug 1894017] Re: Keyboard not working

[Carlos]

Following a tip from [1] (the user there suspects their laptop is
erroneously entering tablet mode) I blacklisted the kernel module
intel_vbtn and it seems to do the trick, my laptop keyboard works again
on kernel 5.4.0-48.

I found a few other bug reports which may be related or duplicates. One
([2]) suggests some kernel parameters as a partial fix, the others ([3],
[4], [5]) have no solution

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=208525#c9
[2]: https://bugzilla.kernel.org/show_bug.cgi?id=208945
[3]: https://bugzilla.kernel.org/show_bug.cgi?id=208853
[4]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012
[5]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894125

** Bug watch added: Linux Kernel Bug Tracker #208525
   https://bugzilla.kernel.org/show_bug.cgi?id=208525

** Bug watch added: Linux Kernel Bug Tracker #208945
   https://bugzilla.kernel.org/show_bug.cgi?id=208945

** Bug watch added: Linux Kernel Bug Tracker #208853
   https://bugzilla.kernel.org/show_bug.cgi?id=208853

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

Title:
  Keyboard not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The laptop keyboard doesn't work at login or in the de. If I
  ctrl+alt+F3 from an external usb keyboard to a terminal the laptop
  keyboard works. An external usb keyboard works everywhere. The
  laptop's keyboard does work everywhere with the previous kernel
  5.4.0.42.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49
  ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55
  Uname: Linux 5.4.0-45-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Sep  3 03:09:49 2020
  InstallationDate: Installed on 2019-08-07 (392 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency 
root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-45-lowlatency N/A
   linux-backports-modules-5.4.0-45-lowlatency  N/A
   linux-firmware   1.187.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago)
  dmi.bios.date: 03/13/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2209
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.57
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
  dmi.product.name: HP Pavilion 11 x360 PC
  dmi.product.sku: M0B61EA#ACQ
  dmi.product.version: 097710405F00010420180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1897853] Re: [regression] gnome-shell stutters noticeably with kernel 5.8.0-19, but not 5.8.0-18

[Daniel van Vugt]

When finished, this will also solve it:

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441

but that probably won't be this cycle.

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

Title:
  [regression] gnome-shell stutters noticeably with kernel 5.8.0-19, but
  not 5.8.0-18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell stutters noticeably with kernel 5.8.0-19

  I've now tested three recent kernels:

  5.8.0-19: stutters
  5.8.0-18: smooth
  5.8.0-16: smooth

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-19-generic 5.8.0-19.20
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 13:52:38 2020
  InstallationDate: Installed on 2020-07-16 (76 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint
   Bus 001 Device 003: ID 045e:0823 Microsoft Corp. Classic IntelliMouse
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 10M7CTO1WW
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-19-generic 
root=UUID=21e70a66-4d0f-49fc-b42c-668fc1594d91 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.release: 0.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:br0.47:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888779] Re: Can't boot with Linux 5.4.0.*

[You-Sheng Yang]

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

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

Title:
  Can't boot with Linux 5.4.0.*

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked
  5.4.0.42 and two uncertain previous versions, something like 5.4.0.40
  and 5.4.0.38).

  The laptop stays at a black screen with the following printed
  (disclaimer: typed manually from a low quality photo of the screen---
  typos and mistakes expected):

  [   69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
t
  ype=Physical Layer, (Receiver ID)
  [   69.258377] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mas
  k=0001/2000
  [   69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [   69.254733] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mask=0001/2000
  [   69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP

  
  See attachments for good quality photo of the screen.

  Notes
  -
  Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text 
as above is shown for a brief moment.

  Minimum attachment
  --
  Output of "sudo lspci -vnvn" is attached.

  $ cat /proc/version_signature
  Ubuntu 5.3.0-51.44-generic 5.3.18
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrei 2258 F pulseaudio
   /dev/snd/controlC1:  andrei 2258 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: KDE neon 20.04
  HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab
  InstallationDate: Installed on 2017-12-26 (940 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.187.1
  Tags:  focal
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.4
  dmi.board.name: 0DRPKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Markus Schade]

Thanks. It does not look like the "regression" preventing proposed
migration is caused by the qemu changes.

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

Title:
  Add/Backport EPYC-v3 and EPYC-Rome CPU model

Status in libvirt package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Fix Released
Status in libvirt source package in Focal:
  Incomplete
Status in linux source package in Focal:
  Fix Committed
Status in qemu source package in Focal:
  Fix Committed

Bug description:
  ## Qemu SRU ##

  [Impact]

   * CPU definitions are added to qemu as these CPUs are known.
 And due to that over time are missing in former releases.

   * To really benefit from the new features of these chips
 they have to be known, therefore new type additions done by
 upstream should be backported if they generally apply and do
 not depend on SRU-critical changes.

   * This backports two upstream fixes that just add definitions (no
 control flow changes)

  [Test Case]

   * Probe qemu for the known CPU types (works on all HW)
 $ qemu-system-x86_64 -cpu ? | grep EPYC
 Focal without fix:
 x86 EPYC  (alias configured by machine type)  
 x86 EPYC-IBPB (alias of EPYC-v2)  
 x86 EPYC-v1   AMD EPYC Processor  
 x86 EPYC-v2   AMD EPYC Processor (with IBPB)
 Focal with fix also adds:
 x86 EPYC-Rome (alias configured by machine type)   
 
 x86 EPYC-Rome-v1  AMD EPYC-Rome Processor  
 
 x86 EPYC-v3   AMD EPYC Processor 

   * Given such HW is available start a KVM guest using those new types
 Since we don't have libvirt support (yet) do so directly in qemu 
 commandline like (bootloader is enough)
 $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm 
-nographic
 $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm 
-nographic

  [Regression Potential]

   * This adds new CPU types to the list of known CPUs defining their name
 and features. Generally the changes are contained to those new types
 and only active when selected - and usually only selectable on such new 
 machines. Therefore not a lot should change for other users.
 One thing thou, if a user selected an unversioned type (which in this 
 case only can be "EPYC") by default it will pick the latest subversion
 that applies. In this case the behavior will change and pick EPYC-v3 
 after the fix. But this is the whole purpose of versioned (stay as is) 
 and unversioned (move with updates) CPU types - so that should be ok.
 The EPYC-Rome type didn't exist in Focal before, so it can't "change" 
 for users.

  
  [Other Info]
   
   * Depends on the new kernel 5.4.0-49 or later (Currently in
 focal-proposed)

  ---

  Qemu in focal has already support for most (except amd-stibp) flags of
  this model.

  Please backport the following patches:

  https://github.com/qemu/qemu/commit/a16e8dbc043720abcb37fc7dca313e720b4e0f0c

  https://github.com/qemu/qemu/commit/143c30d4d346831a09e59e9af45afdca0331e819

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

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

[Kernel-packages] [Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Christian Ehrhardt ]

FYI: Autopkgtest issues resolved

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

Title:
  Add/Backport EPYC-v3 and EPYC-Rome CPU model

Status in libvirt package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Fix Released
Status in libvirt source package in Focal:
  Incomplete
Status in linux source package in Focal:
  Fix Committed
Status in qemu source package in Focal:
  Fix Committed

Bug description:
  ## Qemu SRU ##

  [Impact]

   * CPU definitions are added to qemu as these CPUs are known.
 And due to that over time are missing in former releases.

   * To really benefit from the new features of these chips
 they have to be known, therefore new type additions done by
 upstream should be backported if they generally apply and do
 not depend on SRU-critical changes.

   * This backports two upstream fixes that just add definitions (no
 control flow changes)

  [Test Case]

   * Probe qemu for the known CPU types (works on all HW)
 $ qemu-system-x86_64 -cpu ? | grep EPYC
 Focal without fix:
 x86 EPYC  (alias configured by machine type)  
 x86 EPYC-IBPB (alias of EPYC-v2)  
 x86 EPYC-v1   AMD EPYC Processor  
 x86 EPYC-v2   AMD EPYC Processor (with IBPB)
 Focal with fix also adds:
 x86 EPYC-Rome (alias configured by machine type)   
 
 x86 EPYC-Rome-v1  AMD EPYC-Rome Processor  
 
 x86 EPYC-v3   AMD EPYC Processor 

   * Given such HW is available start a KVM guest using those new types
 Since we don't have libvirt support (yet) do so directly in qemu 
 commandline like (bootloader is enough)
 $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm 
-nographic
 $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm 
-nographic

  [Regression Potential]

   * This adds new CPU types to the list of known CPUs defining their name
 and features. Generally the changes are contained to those new types
 and only active when selected - and usually only selectable on such new 
 machines. Therefore not a lot should change for other users.
 One thing thou, if a user selected an unversioned type (which in this 
 case only can be "EPYC") by default it will pick the latest subversion
 that applies. In this case the behavior will change and pick EPYC-v3 
 after the fix. But this is the whole purpose of versioned (stay as is) 
 and unversioned (move with updates) CPU types - so that should be ok.
 The EPYC-Rome type didn't exist in Focal before, so it can't "change" 
 for users.

  
  [Other Info]
   
   * Depends on the new kernel 5.4.0-49 or later (Currently in
 focal-proposed)

  ---

  Qemu in focal has already support for most (except amd-stibp) flags of
  this model.

  Please backport the following patches:

  https://github.com/qemu/qemu/commit/a16e8dbc043720abcb37fc7dca313e720b4e0f0c

  https://github.com/qemu/qemu/commit/143c30d4d346831a09e59e9af45afdca0331e819

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

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

[Kernel-packages] [Bug 1871306] Re: No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3

[Gabriele Tettamanzi]

@Hui

There's no sound recording difference within Debian  1.2.3 and yours
testing 1.2.2

I narrowed down the issue: it's coming along when plugging / unplugging
the headset jack while I'm running the recording piece of software.

I'm able to reproduce the issue on Audacity.

This issue makes web Skype unusable, the installed version of Zoom seems
to work of I plug the jack in before launching it.

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

Title:
  No sound from internal card chtmax98090 - missing UCM2 files in alsa-
  ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3

Status in alsa-ucm-conf package in Ubuntu:
  Confirmed

Bug description:
  Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script)  - 
Kubuntu Focal minimal fresh installation.
  The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in 
alsamixer and it's not muted.
  I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case 
config files: no success.
  I tried and unmute speakers left and right in alsamixer: no success.

  I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the
  same issue.

  I'm running on the same rig Debian Bullseye, kernel 5.4: sound card
  output and input are both working perfectly - I noticed that in
  Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH
  (the HDMI card), while in Debian I find Pulseaudio.

  
  I attach the alsa-info.sh output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.17
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Tue Apr  7 08:55:46 2020
  InstallationDate: Installed on 2020-04-04 (2 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gabriel3937 F pulseaudio
   /dev/snd/controlC0:  gabriel3937 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-04 (3 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam
   Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Quawks
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/17/2020
  dmi.bios.vendor: coreboot
  dmi.bios.version: MrChromebox-4.11.2
  dmi.board.name: Quawks
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr:
  dmi.product.name: Quawks
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions

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

[Kernel-packages] [Bug 1897853] [NEW] [regression] gnome-shell stutters noticeably with kernel 5.8.0-19, but not 5.8.0-18

[Daniel van Vugt]

Public bug reported:

gnome-shell stutters noticeably with kernel 5.8.0-19

I've now tested three recent kernels:

5.8.0-19: stutters
5.8.0-18: smooth
5.8.0-16: smooth

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-19-generic 5.8.0-19.20
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Sep 30 13:52:38 2020
InstallationDate: Installed on 2020-07-16 (76 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint
 Bus 001 Device 003: ID 045e:0823 Microsoft Corp. Classic IntelliMouse
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 10M7CTO1WW
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-19-generic 
root=UUID=21e70a66-4d0f-49fc-b42c-668fc1594d91 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-19-generic N/A
 linux-backports-modules-5.8.0-19-generic  N/A
 linux-firmware1.190
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2018
dmi.bios.release: 0.47
dmi.bios.vendor: LENOVO
dmi.bios.version: M16KT47A
dmi.board.name: 3102
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN 3259627060530
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:br0.47:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
dmi.product.family: ThinkCentre M710s
dmi.product.name: 10M7CTO1WW
dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
dmi.product.version: ThinkCentre M710s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug groovy performance regression

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

Title:
  [regression] gnome-shell stutters noticeably with kernel 5.8.0-19, but
  not 5.8.0-18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell stutters noticeably with kernel 5.8.0-19

  I've now tested three recent kernels:

  5.8.0-19: stutters
  5.8.0-18: smooth
  5.8.0-16: smooth

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-19-generic 5.8.0-19.20
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 13:52:38 2020
  InstallationDate: Installed on 2020-07-16 (76 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint
   Bus 001 Device 003: ID 045e:0823 Microsoft Corp. Classic IntelliMouse
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 10M7CTO1WW
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-19-generic 
root=UUID=21e70a66-4d0f-49fc-b42c-668fc1594d91 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.release: 0.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:br0.47:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [regression] gnome-shell stutters noticeably with kernel 5.8.0-19, but
  not 5.8.0-18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell stutters noticeably with kernel 5.8.0-19

  I've now tested three recent kernels:

  5.8.0-19: stutters
  5.8.0-18: smooth
  5.8.0-16: smooth

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-19-generic 5.8.0-19.20
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 13:52:38 2020
  InstallationDate: Installed on 2020-07-16 (76 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint
   Bus 001 Device 003: ID 045e:0823 Microsoft Corp. Classic IntelliMouse
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 10M7CTO1WW
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-19-generic 
root=UUID=21e70a66-4d0f-49fc-b42c-668fc1594d91 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.release: 0.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:br0.47:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888779] Re: Can't boot with Linux 5.4.0.*

[You-Sheng Yang]

Didn't find any screenshot attachment. But could you try booting with
following kernel parameters?

  debug initcall_debug earlycon=efifb

The screen may scroll much slower than usual but it's normal. Take a
picture and attach here if any last word of the kernel dumped.

For detailed steps, please see
https://wiki.ubuntu.com/Kernel/KernelBootParameters#Temporarily_Add_a_Kernel_Boot_Parameter_for_Testing
.

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

Title:
  Can't boot with Linux 5.4.0.*

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked
  5.4.0.42 and two uncertain previous versions, something like 5.4.0.40
  and 5.4.0.38).

  The laptop stays at a black screen with the following printed
  (disclaimer: typed manually from a low quality photo of the screen---
  typos and mistakes expected):

  [   69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
t
  ype=Physical Layer, (Receiver ID)
  [   69.258377] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mas
  k=0001/2000
  [   69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [   69.254733] pcieport 000:00:1c.5: AER:   device [B086:9d15] error 
status/mask=0001/2000
  [   69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr
  [   69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP

  
  See attachments for good quality photo of the screen.

  Notes
  -
  Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text 
as above is shown for a brief moment.

  Minimum attachment
  --
  Output of "sudo lspci -vnvn" is attached.

  $ cat /proc/version_signature
  Ubuntu 5.3.0-51.44-generic 5.3.18
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrei 2258 F pulseaudio
   /dev/snd/controlC1:  andrei 2258 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: KDE neon 20.04
  HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab
  InstallationDate: Installed on 2017-12-26 (940 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.187.1
  Tags:  focal
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.4
  dmi.board.name: 0DRPKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

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

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