date:20210802

Also spotted on B-oracle-5.4 with arm64 instance VM.Standard.A1.Flex-4c.8m
5.4.0-1053.57~18.04.1

** Tags added: 5.4 bionic

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

Title:
  test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on
  F-oracle-5.11 ARM64

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-oracle package in Ubuntu:
  New

Bug description:
  Issue found on 5.11.0-1015.16~20.04.1 with instance
  VM.Standard.A1.Flex-4c.8m

==
FAIL: test_320_config_arm_pan (__main__.KernelSecurityConfigTest)
Ensure PAN for arm processors is set
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2756, in test_320_config_arm_pan
self.assertKernelConfig(config_name, expected)
  File "./test-kernel-security.py", line 214, in assertKernelConfig
self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 201, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: ARM64_SW_TTBR0_PAN option was expected to be set in the 
kernel config

--
Ran 125 tests in 26.030s

FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1938748/+subscriptions


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

[Kernel-packages] [Bug 1938748] [NEW] test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on F-oracle-5.11 ARM64

Public bug reported:

Issue found on 5.11.0-1015.16~20.04.1 with instance
VM.Standard.A1.Flex-4c.8m

  ==
  FAIL: test_320_config_arm_pan (__main__.KernelSecurityConfigTest)
  Ensure PAN for arm processors is set
  --
  Traceback (most recent call last):
File "./test-kernel-security.py", line 2756, in test_320_config_arm_pan
  self.assertKernelConfig(config_name, expected)
File "./test-kernel-security.py", line 214, in assertKernelConfig
  self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 201, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: ARM64_SW_TTBR0_PAN option was expected to be set in the 
kernel config
  
  --
  Ran 125 tests in 26.030s
  
  FAILED (failures=1)

** Affects: qa-regression-testing
 Importance: Undecided
 Status: New

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

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


** Tags: 5.11 5.4 arm64 bionic focal sru-20210719 ubuntu-qrt-kernel-security

** Tags added: 5.11 focal

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

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

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

Title:
  test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on
  F-oracle-5.11 ARM64

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-oracle package in Ubuntu:
  New

Bug description:
  Issue found on 5.11.0-1015.16~20.04.1 with instance
  VM.Standard.A1.Flex-4c.8m

==
FAIL: test_320_config_arm_pan (__main__.KernelSecurityConfigTest)
Ensure PAN for arm processors is set
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2756, in test_320_config_arm_pan
self.assertKernelConfig(config_name, expected)
  File "./test-kernel-security.py", line 214, in assertKernelConfig
self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 201, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: ARM64_SW_TTBR0_PAN option was expected to be set in the 
kernel config

--
Ran 125 tests in 26.030s

FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1938748/+subscriptions


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

[Kernel-packages] [Bug 1938742] Re: 5.8.0-63 Breaks Wifi on RTL8822BE

2021-08-02 Thread ndst

WifiSysLog

** Attachment removed: "PulseList.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1938742/+attachment/5515434/+files/PulseList.txt

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1938742/+attachment/5515437/+files/WifiSyslog.txt

** Attachment added: "WifiSysLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1938742/+attachment/5515440/+files/WifiSysLog.txt

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

Title:
  5.8.0-63 Breaks Wifi on RTL8822BE

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  After upgrading to 5.8.0-63 the wifi card RTL8822BE can still be seen,
  but wifi networks cannot be found. If the nvidia driver 470.57 is
  installed the wifi card is no longer found.

  lspci | grep -i realtek:
  07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 
802.11a/b/g/n/ac WiFi adapter (rev ff)

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  2 22:37:25 2021
  EcryptfsInUse: Yes
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username  2540 F pulseaudio
   /dev/snd/controlC1:  username  2540 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  EcryptfsInUse: Yes
  MachineType: LENOVO 81LF
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 i915drmfb
   1 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic 
root=UUID=79951aeb-477e-4f92-a571-ce78702269da ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-63-generic N/A
   linux-backports-modules-5.8.0-63-generic  N/A
   linux-firmware1.187.15
  Tags:  wayland-session focal
  Uname: Linux 5.8.0-63-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: 11/30/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9VCN22WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion Y7000P-1060
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvr9VCN22WW:bd11/30/2020:br1.22:efr1.22:svnLENOVO:pn81LF:pvrLenovoLegionY7000P-1060:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegionY7000P-1060:
  dmi.product.family: Legion Y7000P-1060
  dmi.product.name: 81LF
  dmi.product.sku: LENOVO_MT_81LF_BU_idea_FM_Legion Y7000P-1060
  dmi.product.version: Lenovo Legion Y7000P-1060
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1938742] Re: 5.8.0-63 Breaks Wifi on RTL8822BE

2021-08-02 Thread ndst

** Description changed:

  After upgrading to 5.8.0-63 the wifi card RTL8822BE can still be seen,
  but wifi networks cannot be found. If the nvidia driver 470.57 is
  installed the wifi card is no longer found.
  
  lspci | grep -i realtek:
  07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 
802.11a/b/g/n/ac WiFi adapter (rev ff)
  
  Thank you.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  2 22:37:25 2021
  EcryptfsInUse: Yes
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  brian  2540 F pulseaudio
-  /dev/snd/controlC1:  brian  2540 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  username  2540 F pulseaudio
+  /dev/snd/controlC1:  username  2540 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  EcryptfsInUse: Yes
  MachineType: LENOVO 81LF
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB:
-  0 i915drmfb
-  1 nouveaudrmfb
+  0 i915drmfb
+  1 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic 
root=UUID=79951aeb-477e-4f92-a571-ce78702269da ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  RelatedPackageVersions:
-  linux-restricted-modules-5.8.0-63-generic N/A
-  linux-backports-modules-5.8.0-63-generic  N/A
-  linux-firmware1.187.15
+  linux-restricted-modules-5.8.0-63-generic N/A
+  linux-backports-modules-5.8.0-63-generic  N/A
+  linux-firmware1.187.15
  Tags:  wayland-session focal
  Uname: Linux 5.8.0-63-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: 11/30/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9VCN22WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion Y7000P-1060
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvr9VCN22WW:bd11/30/2020:br1.22:efr1.22:svnLENOVO:pn81LF:pvrLenovoLegionY7000P-1060:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegionY7000P-1060:
  dmi.product.family: Legion Y7000P-1060
  dmi.product.name: 81LF
  dmi.product.sku: LENOVO_MT_81LF_BU_idea_FM_Legion Y7000P-1060
  dmi.product.version: Lenovo Legion Y7000P-1060
  dmi.sys.vendor: LENOVO

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

Title:
  5.8.0-63 Breaks Wifi on RTL8822BE

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  After upgrading to 5.8.0-63 the wifi card RTL8822BE can still be seen,
  but wifi networks cannot be found. If the nvidia driver 470.57 is
  installed the wifi card is no longer found.

  lspci | grep -i realtek:
  07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 
802.11a/b/g/n/ac WiFi adapter (rev ff)

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  2 22:37:25 2021
  EcryptfsInUse: Yes
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username  2540 F pulseaudio
   /dev/snd/controlC1:  username  2540 F

[Kernel-packages] [Bug 1938742] Re: 5.8.0-63 Breaks Wifi on RTL8822BE

2021-08-02 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => linux-signed-hwe-5.8 (Ubuntu)

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

Title:
  5.8.0-63 Breaks Wifi on RTL8822BE

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  After upgrading to 5.8.0-63 the wifi card RTL8822BE can still be seen,
  but wifi networks cannot be found. If the nvidia driver 470.57 is
  installed the wifi card is no longer found.

  lspci | grep -i realtek:
  07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 
802.11a/b/g/n/ac WiFi adapter (rev ff)

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  2 22:37:25 2021
  EcryptfsInUse: Yes
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username  2540 F pulseaudio
   /dev/snd/controlC1:  username  2540 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  EcryptfsInUse: Yes
  MachineType: LENOVO 81LF
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 i915drmfb
   1 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic 
root=UUID=79951aeb-477e-4f92-a571-ce78702269da ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-63-generic N/A
   linux-backports-modules-5.8.0-63-generic  N/A
   linux-firmware1.187.15
  Tags:  wayland-session focal
  Uname: Linux 5.8.0-63-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: 11/30/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9VCN22WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion Y7000P-1060
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvr9VCN22WW:bd11/30/2020:br1.22:efr1.22:svnLENOVO:pn81LF:pvrLenovoLegionY7000P-1060:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegionY7000P-1060:
  dmi.product.family: Legion Y7000P-1060
  dmi.product.name: 81LF
  dmi.product.sku: LENOVO_MT_81LF_BU_idea_FM_Legion Y7000P-1060
  dmi.product.version: Lenovo Legion Y7000P-1060
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1938742] [NEW] 5.8.0-63 Breaks Wifi on RTL8822BE

You have been subscribed to a public bug:

After upgrading to 5.8.0-63 the wifi card RTL8822BE can still be seen,
but wifi networks cannot be found. If the nvidia driver 470.57 is
installed the wifi card is no longer found.

lspci | grep -i realtek:
07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 
802.11a/b/g/n/ac WiFi adapter (rev ff)

Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug  2 22:37:25 2021
EcryptfsInUse: Yes
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.8
UpgradeStatus: No upgrade log present (probably fresh install)
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  brian  2540 F pulseaudio
 /dev/snd/controlC1:  brian  2540 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
EcryptfsInUse: Yes
MachineType: LENOVO 81LF
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 i915drmfb
 1 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic 
root=UUID=79951aeb-477e-4f92-a571-ce78702269da ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-63-generic N/A
 linux-backports-modules-5.8.0-63-generic  N/A
 linux-firmware1.187.15
Tags:  wayland-session focal
Uname: Linux 5.8.0-63-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: 11/30/2020
dmi.bios.release: 1.22
dmi.bios.vendor: LENOVO
dmi.bios.version: 9VCN22WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Legion Y7000P-1060
dmi.ec.firmware.release: 1.22
dmi.modalias: 
dmi:bvnLENOVO:bvr9VCN22WW:bd11/30/2020:br1.22:efr1.22:svnLENOVO:pn81LF:pvrLenovoLegionY7000P-1060:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegionY7000P-1060:
dmi.product.family: Legion Y7000P-1060
dmi.product.name: 81LF
dmi.product.sku: LENOVO_MT_81LF_BU_idea_FM_Legion Y7000P-1060
dmi.product.version: Lenovo Legion Y7000P-1060
dmi.sys.vendor: LENOVO

** Affects: linux-signed-hwe-5.8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug apport-collected focal wayland-session
-- 
5.8.0-63 Breaks Wifi on RTL8822BE
https://bugs.launchpad.net/bugs/1938742
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-signed-hwe-5.8 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 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does)

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

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

Title:
  Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but
  18.04 does)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have recently acquired a acquired a desktop running ubuntu 20.04. I
  have several computers and switch between them using this KVM
  
https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1
  The other machines are either running windows or ubuntu 18.04 or
  earlier. They are all fine, but the with 20.04 machine neither the
  keyboard nor the mouse works. On the 18.04 machine I can see

  lsusb
  Bus 002 Device 002: ID 8087:8000 Intel Corp. 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 002: ID 8087:8008 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  and it is the Logitech, Inc. Unifying Receiver which appears when the
  USB from the KVM is connected. On the 20.04 machine only this appears

  lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
  Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  I have tested installation discs from 19.04 onwards. The failure first
  appears in 19.10 and is still present in 21.04

  I can observe a similar problem with a dual boot laptop running
  windows 10 and 20.04. With windows 10 I can use it with the KVM for
  screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and
  mouse do not work. This issue has also been observed here
  https://unix.stackexchange.com/questions/646515/using-logitech-mouse-
  keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed
  it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model).

  I had to report this originally against xorg as this bug reporting
  system seems not to allow reporting of bugs against unknown packages.
  I also had to report it through the ubuntu-bug executable as I've been
  unable to find a way in launchpad of reporting a bug (as opposed to
  getting a guided tour about reporting bugs).

  I am happy to supply more info and test fixes if I am asked but as
  with this type of bug where something fails to happen rather than
  something wrong happens I don't know what to look at.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Fri Jun  4 20:21:15 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-05-14 (21 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
   |__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
   |__ Port 13: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 
12M
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=0c391c11-c570-4e04-a351-4fd128a75369 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/2021
  dmi.bios.release: 8.20
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0820
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME H570M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string

[Kernel-packages] [Bug 1936009] Re: [SRU] The internal mic of Dell Precision 5750 can't record sound

2021-08-02 Thread Hui Wang

for focal:

on the Dell Precision 5760
enabled focal-proposed in the /etc/apt/sources.list
sudo apt-get update
sudo apt install alsa-ucm-conf, now the alsa-ucm-conf-1.1.2-1ubuntu0.9 is 
installed.
rm ~/.config/pulse/*;sudo rm -rf /var/lib/alsa/*; echo b | sudo tee 
/proc/sysrq-trigger

After the system boot up, check the internal mic, could record sound
successfully.

verified done on focal.


** 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 alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1936009

Title:
  [SRU] The internal mic of Dell Precision 5750 can't record sound

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Released

Bug description:
  [Impact]
  After upgrade the linux kernel, the mixer names of rt715 is changed, the 
current alsa-ucm-conf will fail to initialize that codec, then users can't 
record sound from internal mic since the internal mic is routed to the codec 
rt715.

  [Fix]
  Backport 3 upstream commits, after applying these 3 commits, the ucm conf 
file dosn't initialize the codec with hardcoded mixer names anymore, it will 
check the existence of the mixer name first, then conditionally initialize the 
codec.

  [Test]
  run 'alsactl init 1' on the precision 5750 with old and new kernel, there is 
no error logs, use the internal mic to record sound, it could record 
successfully.

  [Where problems will occur]
  The change only affects the rt715 codec, so far, that codec only connects to 
the internal mic on Dell soundwire audio machines, so it could introduce 
regression on the internal mic like users can't record sound via internal mic 
anymore on the Dell soundwire audio machines. But this possibility is very low 
since we already tested these 3 commits on different Dell soundwire audio 
machines (latitude and precision). We tested it with old kernel and new kernel, 
all worked well.

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


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

[Kernel-packages] [Bug 1936009] Re: [SRU] The internal mic of Dell Precision 5750 can't record sound

2021-08-02 Thread Hui Wang

for hirsute:

on the Dell Precision 5760
enabled hirsute-proposed in the /etc/apt/sources.list
sudo apt-get update
sudo apt install alsa-ucm-conf, now the alsa-ucm-conf-1.2.4-2ubuntu1.2 is 
installed.
rm ~/.config/pulse/*;sudo rm -rf /var/lib/alsa/*; echo b | sudo tee 
/proc/sysrq-trigger

After the system boot up, check the internal mic, could record sound
successfully.

verified done on hirsute.


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

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

Title:
  [SRU] The internal mic of Dell Precision 5750 can't record sound

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Released

Bug description:
  [Impact]
  After upgrade the linux kernel, the mixer names of rt715 is changed, the 
current alsa-ucm-conf will fail to initialize that codec, then users can't 
record sound from internal mic since the internal mic is routed to the codec 
rt715.

  [Fix]
  Backport 3 upstream commits, after applying these 3 commits, the ucm conf 
file dosn't initialize the codec with hardcoded mixer names anymore, it will 
check the existence of the mixer name first, then conditionally initialize the 
codec.

  [Test]
  run 'alsactl init 1' on the precision 5750 with old and new kernel, there is 
no error logs, use the internal mic to record sound, it could record 
successfully.

  [Where problems will occur]
  The change only affects the rt715 codec, so far, that codec only connects to 
the internal mic on Dell soundwire audio machines, so it could introduce 
regression on the internal mic like users can't record sound via internal mic 
anymore on the Dell soundwire audio machines. But this possibility is very low 
since we already tested these 3 commits on different Dell soundwire audio 
machines (latitude and precision). We tested it with old kernel and new kernel, 
all worked well.

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


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

[Kernel-packages] [Bug 1938492] Re: cursor disappeared and moved to different co-ordinates

Are you using a laptop? Maybe you touched the touchpad while typing?

** Changed in: linux-signed-hwe-5.8 (Ubuntu)
   Status: New => Incomplete

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

Title:
  cursor disappeared and moved to different co-ordinates

Status in linux-signed-hwe-5.8 package in Ubuntu:
  Incomplete

Bug description:
  when I am typing text, suddenly cursor disappeared and moved to
  different coordinates

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 30 08:29:49 2021
  InstallationDate: Installed on 2021-07-25 (4 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1938477] Re: Screen brightness changing randomly with kernel 5.11.0-25

** Summary changed:

- Screen brightness changing randomly
+ Screen brightness changing randomly with kernel 5.11.0-25

** Package changed: gnome-settings-daemon (Ubuntu) => linux (Ubuntu)

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

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

Title:
Screen brightness changing randomly with kernel 5.11.0-25

Status in linux package in Ubuntu:
New

Bug description:
Hello guys!

The brightness of the screen on my laptop (Dell 7573 with touch ips
1080 panel) slightly changes randomly when using the laptop builtin
display. It feels the same as I changed the brightness one step using
the keyboard keys.

Here is a video:

https://drive.google.com/file/d/1XQLXKLWu2TlOoGP-p8eaUGZR78713ErH/view?usp=sharing

I suffer with this problem since a long time ago. I think since ubuntu
19. I tried everything you can imagine, I will make a list of things
I've tried. I had gave up trying to fix this already but in a
beautiful sunny day suddenly the bug stopped happening. So I decided
to report this bug now because this bug does NOT happen with only this
version of the kernel: Linux 5.11.0-16-generic. So that can probably e
useful to help discovering the bug reason.

I am choosing this version on grub every time I reboot so the bug
doesn't happen. If I boot on 5.11.0-25 the bug is back.

List of things I've tried:
- Changing i915 parameters like enable_psr to false and many others.
- Upgrading BIOS version.
- Installing windows and applying all the patches on dell's website and
installing ubuntu again.
- Disabling "dynamic backlight control" on BIOS.

Some maybe useful info:
- I've tried other distros like Fedora and PopOS and the same bug happens.
- The bug does not happen when using live ubuntu from usb.
- When you fresh install ubuntu (I've tried with 20.04, 20.10 and 21.04) the
bug doesn't happen when you have just installed the os but it starts again
after the first update. The same applies to the other distro's mentioned above.
- When you disable i915 driver with modeset parameter, it does not happen.
- The bug does NOT happen only with this kernel version 5.11.0-16-generic,
BUT it starts happening again if I lock screen and login again. So I am never
locking my screen and holding this kernel version for now.

Thanks guys!

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 29 20:54:14 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed
virtualbox, 6.1.18, 5.11.0-25-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA
controller])
Subsystem: Dell UHD Graphics 620 [1028:07ec]
InstallationDate: Installed on 2021-07-25 (4 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Dell Inc. Inspiron 7573
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic
root=UUID=663d1a67-7acb-428f-a6c8-a9a259a5427c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2021
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.1
dmi.board.name: 023FRC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.18.1:bd05/06/2021:br1.18:svnDellInc.:pnInspiron7573:pvr:rvnDellInc.:rn023FRC:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7573
dmi.product.sku: 07EC
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

--
Mailing list: https://launchpad.net/~kernel-packages
Post to :

[Kernel-packages] [Bug 1938477] [NEW] Screen brightness changing randomly with kernel 5.11.0-25

You have been subscribed to a public bug:

Hello guys!

The brightness of the screen on my laptop (Dell 7573 with touch ips 1080
panel) slightly changes randomly when using the laptop builtin display.
It feels the same as I changed the brightness one step using the
keyboard keys.

Here is a video:
https://drive.google.com/file/d/1XQLXKLWu2TlOoGP-p8eaUGZR78713ErH/view?usp=sharing

I suffer with this problem since a long time ago. I think since ubuntu
19. I tried everything you can imagine, I will make a list of things
I've tried. I had gave up trying to fix this already but in a beautiful
sunny day suddenly the bug stopped happening. So I decided to report
this bug now because this bug does NOT happen with only this version of
the kernel: Linux 5.11.0-16-generic. So that can probably e useful to
help discovering the bug reason.

I am choosing this version on grub every time I reboot so the bug
doesn't happen. If I boot on 5.11.0-25 the bug is back.

List of things I've tried:
- Changing i915 parameters like enable_psr to false and many others.
- Upgrading BIOS version.
- Installing windows and applying all the patches on dell's website and 
installing ubuntu again.
- Disabling "dynamic backlight control" on BIOS.

Some maybe useful info:
- I've tried other distros like Fedora and PopOS and the same bug happens.
- The bug does not happen when using live ubuntu from usb.
- When you fresh install ubuntu (I've tried with 20.04, 20.10 and 21.04) the 
bug doesn't happen when you have just installed the os but it starts again 
after the first update. The same applies to the other distro's mentioned above.
- When you disable i915 driver with modeset parameter, it does not happen.
- The bug does NOT happen only with this kernel version 5.11.0-16-generic, BUT 
it starts happening again if I lock screen and login again. So I am never 
locking my screen and holding this kernel version for now.

Thanks guys!

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 29 20:54:14 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed
 virtualbox, 6.1.18, 5.11.0-25-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:07ec]
InstallationDate: Installed on 2021-07-25 (4 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Dell Inc. Inspiron 7573
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=663d1a67-7acb-428f-a6c8-a9a259a5427c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2021
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.1
dmi.board.name: 023FRC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.1:bd05/06/2021:br1.18:svnDellInc.:pnInspiron7573:pvr:rvnDellInc.:rn023FRC:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7573
dmi.product.sku: 07EC
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute ubuntu
-- 
Screen brightness changing randomly with kernel 5.11.0-25
https://bugs.launchpad.net/bugs/1938477
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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

https://launchpad.net/ubuntu/+source/pulseaudio/1:15.0+dfsg1-1ubuntu1

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

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1938413] Re: Shutdown hangs on EHL board

2021-08-02 Thread SACHIN MOKASHI

Please revert the patch "pinctrl: intel: Add Intel Elkhart Lake pin
controller support" and continue testing

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

Title:
  Shutdown hangs on EHL board

Status in intel:
  New
Status in linux-intel package in Ubuntu:
  In Progress

Bug description:
  [Summary]Go to Power -> Shutdown and the screen goes blank, but the
  system does not shut down.  You cannot recover and have to perform a
  hard reboot.

  [Steps to reproduce]
  1. Boot up Ubuntu
  2. Power -> Shutdown (click ok)

  [Expected result]
  System should cleanly shut down.

  [Actual result]
  Screen blanks with a blinking cursor, the system does not shut down, the fan 
is still on.  System is unresponsive, forcing you to do a hard reset.

  [Failure rate]100%

  [Additional information]
  CID: 20215-29063 
  SKU: 
  system-manufacturer: Intel Corporation
  system-product-name: Elkhart Lake Embedded Platform
  bios-version: EHLSFWI1.R00.2091.A00.2002250754
  CPU: Genuine Intel(R) CPU  @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571]
  kernel-version: 5.11.0-1009-intel

  
  [Stage]
  Device froze, issue reported and logs collected right after a reboot

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


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

[Kernel-packages] [Bug 1931779] Re: kdump just hung out of the box

2021-08-02 Thread Guilherme G. Piccoli

This is a good suggestion Rich! I've looped Dann and Cascardo, both
maintainers of kdump-tools to also discuss this subject.

We could have a more explicit message when installing the package, maybe
in the same screen that asks if we want to enable kdump by default. I'm
against the idea of _not_ setting the default crashkernel though - good
suggestion for intermediate/advanced users, bad suggestion for beginners
I think. Also, I must say: my experience was pretty reciprocal to yours.
The default always worked for me in regular/simple HW or VMs, it fails
in more peculiar setups, like 200 PCI devices, 1 TiB of RAM, etc.

Thanks for bringing-up the discussion =)

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

Title:
  kdump just hung out of the box

Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date
  20.04 system, installed specifically to try reproducing a bug.

  But when I tried, after kdump-config status reported "ready to dump"
  on reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the
  panic to console and then just hung forever.

  After some blind guessing and twiddling both variables, I found that
  crashkernel=512M-:256M works on this particular setup. (MS7850
  motherboard, i5-4670 CPU, 5.4.0-42-generic kernel)

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


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

[Kernel-packages] [Bug 1936009] Re: [SRU] The internal mic of Dell Precision 5750 can't record sound

Hello Hui, or anyone else affected,

Accepted alsa-ucm-conf into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu0.9 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: alsa-ucm-conf (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  [SRU] The internal mic of Dell Precision 5750 can't record sound

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Released

Bug description:
  [Impact]
  After upgrade the linux kernel, the mixer names of rt715 is changed, the 
current alsa-ucm-conf will fail to initialize that codec, then users can't 
record sound from internal mic since the internal mic is routed to the codec 
rt715.

  [Fix]
  Backport 3 upstream commits, after applying these 3 commits, the ucm conf 
file dosn't initialize the codec with hardcoded mixer names anymore, it will 
check the existence of the mixer name first, then conditionally initialize the 
codec.

  [Test]
  run 'alsactl init 1' on the precision 5750 with old and new kernel, there is 
no error logs, use the internal mic to record sound, it could record 
successfully.

  [Where problems will occur]
  The change only affects the rt715 codec, so far, that codec only connects to 
the internal mic on Dell soundwire audio machines, so it could introduce 
regression on the internal mic like users can't record sound via internal mic 
anymore on the Dell soundwire audio machines. But this possibility is very low 
since we already tested these 3 commits on different Dell soundwire audio 
machines (latitude and precision). We tested it with old kernel and new kernel, 
all worked well.

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


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

[Kernel-packages] [Bug 1931779] Re: kdump just hung out of the box

2021-08-02 Thread Rich

My suggestion would be to print a warning unconditionally on first
install that you should test it and not assume it will just work, and/or
to not set crashkernel=... with the default in the first place so people
have to go explicitly set it (and, implicitly, read about the fact that
one size does not fit all when finding out how). (I would even do the
former if your very next commit landed the heuristic estimator to
improve this, until you were confident it worked in the majority of
cases.)

I know it's not readily programmatically possible to tell "will this
work" short of actually doing it, because haha hardware, my lament is
that in my experience, the default has _never_ worked, on my VMs or real
hardware, and I would not expect something to configure itself with
defaults, resulting in e.g. kdump-config status reporting "ready to
kdump" when asked, and then...not.

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

Title:
  kdump just hung out of the box

Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date
  20.04 system, installed specifically to try reproducing a bug.

  But when I tried, after kdump-config status reported "ready to dump"
  on reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the
  panic to console and then just hung forever.

  After some blind guessing and twiddling both variables, I found that
  crashkernel=512M-:256M works on this particular setup. (MS7850
  motherboard, i5-4670 CPU, 5.4.0-42-generic kernel)

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


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

[Kernel-packages] [Bug 1938474] Re: delve golang debugger can't read vvar on arm64

2021-08-02 Thread Bryce Harrington

** Bug watch added: github.com/go-delve/delve/issues #2630
   https://github.com/go-delve/delve/issues/2630

** Also affects: linux via
   https://github.com/go-delve/delve/issues/2630
   Importance: Unknown
   Status: Unknown

** Project changed: linux => delve

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

Title:
  delve golang debugger can't read vvar on arm64

Status in Delve:
  Unknown
Status in delve package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Also documented upstream:
  https://github.com/go-delve/delve/issues/2630

  In version 1.6.1 of the delve golang debugger, a 'dump' feature was added.
  https://github.com/go-delve/delve/pull/2173

  Since that time, arm64 autopkgtest of delve has been failing like so:

  
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/d/delve/20210707_003312_d3699@/log.gz
  === RUN   TestDump
  proc_test.go:5117: testing normal dump
  proc_test.go:5029: bad DumpState 
{Mutex:sync.Mutex{state:0, sema:0x0}, Dumping:false, 
AllDone:true, Canceled:false, DoneChan:(chan struct {})(nil), ThreadsDone:5, 
ThreadsTotal:5, MemDone:0x657b000, MemTotal:0x657d000, Err:error(nil)}
  --- FAIL: TestDump (0.98s)

  The test fails becaue MemDone != MemTotal.
  The decision on what to dump or not is based on smaps.
  The failing item is vvar.
  err when attempting to read is
  error(syscall.Errno) golang.org/x/sys/unix.EIO (5)

  Notably however, this test passes in debian CI. (kernel 4.19)
  Also, running on older series such as bionic/focal does pass.

  vvar section from vm with kernel 5.4 (test pass):
  924a4000-924a5000 r--p  00:00 0  
[vvar]
  Size:  4 kB
  KernelPageSize:4 kB
  MMUPageSize:   4 kB
  Rss:   0 kB
  Pss:   0 kB
  Shared_Clean:  0 kB
  Shared_Dirty:  0 kB
  Private_Clean: 0 kB
  Private_Dirty: 0 kB
  Referenced:0 kB
  Anonymous: 0 kB
  LazyFree:  0 kB
  AnonHugePages: 0 kB
  ShmemPmdMapped:0 kB
  FilePmdMapped:0 kB
  Shared_Hugetlb:0 kB
  Private_Hugetlb:   0 kB
  Swap:  0 kB
  SwapPss:   0 kB
  Locked:0 kB
  THPeligible:0
  VmFlags: rd mr de

  vvar from failing case
  ac144000-ac146000 r--p  00:00 0  
[vvar]
  Size:  8 kB
  KernelPageSize:4 kB
  MMUPageSize:   4 kB
  Rss:   0 kB
  Pss:   0 kB
  Shared_Clean:  0 kB
  Shared_Dirty:  0 kB
  Private_Clean: 0 kB
  Private_Dirty: 0 kB
  Referenced:0 kB
  Anonymous: 0 kB
  LazyFree:  0 kB
  AnonHugePages: 0 kB
  ShmemPmdMapped:0 kB
  FilePmdMapped: 0 kB
  Shared_Hugetlb:0 kB
  Private_Hugetlb:   0 kB
  Swap:  0 kB
  SwapPss:   0 kB
  Locked:0 kB
  THPeligible:0
  VmFlags: rd mr pf de

  Two noticible differences
  1) 4kB vs 8kB size
  2) Failing case adds the "pf" flag ("pure PFN range")

  Open questions:
  1) Would we expect that a debugger could read vvar on arm64?
  2) Any thoughts on why this seems to work on older kernels?
  3) Do we believe this to be a kernel bug,
     or should the delve debugger not expect to read vvar?
  4) Is it sensible for a debugger to attempt to read things with the "pf"
     flag?  Note that the "dd" ("do not include area into core dump")
     flag is not set.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.11.0-20-generic 5.11.0-20.21+21.10.1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 29 21:21 seq
   crw-rw 1 root audio 116, 33 Jul 29 21:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: Thu Jul 29 21:34:34 2021
  InstallationDate: Installed on 2021-07-29 (0 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210729)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle-5.11/5.11.0.1015.16~20.04.7)

2021-08-02 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-oracle-5.11 
(5.11.0.1015.16~20.04.7) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

glibc/2.31-0ubuntu9.2 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-oracle-5.11

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1925421] Autopkgtest regression report (linux-meta-oracle-5.11/5.11.0.1015.16~20.04.7)

2021-08-02 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-oracle-5.11 
(5.11.0.1015.16~20.04.7) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

glibc/2.31-0ubuntu9.2 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-oracle-5.11

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  arm64 support

Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle-5.4 package in Ubuntu:
  New
Status in linux-oracle-5.8 package in Ubuntu:
  New
Status in linux-oracle source package in Bionic:
  Invalid
Status in linux-oracle-5.4 source package in Bionic:
  Fix Released
Status in linux-oracle-5.8 source package in Bionic:
  New
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-oracle-5.4 source package in Focal:
  Invalid
Status in linux-oracle-5.8 source package in Focal:
  Fix Released
Status in linux-oracle source package in Groovy:
  Fix Released
Status in linux-oracle-5.4 source package in Groovy:
  Invalid
Status in linux-oracle-5.8 source package in Groovy:
  Fix Committed

Bug description:
  See
  https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view
  for more info

  
  [Impact]
  No support for arm64 currently

  
  [Fix]
  Add arm64 support, including hardware support patches

  [Test]
  Confirm that it boots on desired arm64 hardware, as well as VMs

  [Regression Potential]
  This was never working on arm64 so there should be no risk of regression.
  The requested changes included some refactorings of early memory 
initialization code (all arches) so this presents a small risk. The changes 
were tested on arm64 as well amd64.

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


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

[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04

2021-08-02 Thread Glyn Normington

I'm on Ubuntu 20.10 and security updates are no longer being provided.
The recommendation is to upgrade to 21.04, but I want to avoid this
issue. I could upgrade the kernel, but I wonder when the kernel fixes
will appear in an Ubuntu release so I can simply upgrade 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/1924685

Title:
  No sound output/input available after installing 21.04

Status in OEM Priority Project:
  Won't Fix
Status in Release Notes for Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Image: Hirsute 21.04 (20210415 daily build)

  Device: Dell Precision 5750

  After installing 21.04, the sound card is unavailable. In Sound
  Settings, there is only one choice: "Dummy Output" .

  The only way to hear sound is to connect a Bluetooth speaker.

  Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel:

  https://certification.ubuntu.com/hardware/202002-27726

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-14-generic 5.11.0-14.15
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1561 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 15:10:05 2021
  InstallationDate: Installed on 2021-04-16 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  MachineType: Dell Inc. Precision 5750
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic 
root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-14-generic N/A
   linux-backports-modules-5.11.0-14-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1938669] Re: Epiphan framegrabbers stream only once then need unbinding/rebinding to uvcvideo to work again

2021-08-02 Thread Philip Spencer

Thanks; I have done so, to the uvcvideo maintainer with copies to the
media input maintainer, LKML and the linux-media mailing list, as
indicated by the get_maintainer.pl script.

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

Title:
  Epiphan framegrabbers stream only once then need unbinding/rebinding
  to uvcvideo to work again

Status in linux package in Ubuntu:
  New

Bug description:
  Video capture devices made by Epiphan Systems (vendor id 0x2b77) work
  once, but as soon as the video device is closed (or even if it is kept
  open but the application issues a VIDIOC_STREAMOFF ioctl) it won't
  work again - subsequent calls to VIDOC_DQBUF simply hang - until the
  device is unbound from and rebound to the uvcvideo module. (modprobe
  -r uvcvideo; modprobe uvcvideo also works).

  For example:

ffplay /dev/video0  -- works fine and shows the captured stream.

ffplay /dev/video0  -- when run a second time: hangs and does not
  capture anything

modprobe -r uvcvideo ; modprobe uvcvideo; ffplay /dev/video  --
  works fine again.

  Experimenting with the device and the uvcvideo module source code
  reveals that problem is the device is expecting SET_INTERFACE(0) to be
  sent to return it to a state where it can accept control requests and
  start streaming again.

  The code in uvc_video.c has several comments stating that some bulk-
  transfer devices require a SET_INTERFACE(0) call to be made before any
  control commands, even though 0 is already the default and only valid
  interface value. And, the function uvc_video_init makes such a call
  (which is why the device starts working again after rebinding to the
  uvcvideo module). But no such call is made when streaming is stopped
  then restarted.

  Furthermore, SET_INTERFACE(0) is the mechanism by which isochronous
  devices are told to stop streaming, and the comments in
  uvc_video_stop_streaming state that the UVC specification is unclear
  on how a bulk-based device should be told to stop streaming, so it is
  reasonable to expect this particular bulk-based device might be
  expecting the same SET_INTERFACE(0) call that an isochronous device
  would get as means of being told to stop streaming.

  The attached patch fixes the problem for these Epiphan devices by
  adding a SET_INTERFACE(0) call in two places. Either one by itself is
  sufficient to resolve the symptoms but I think it is probably safest
  to include both.

  The first hunk adds a SET_INTERFACE(0) call in
  uvc_video_start_streaming, but only in the bulk-based case where 0 is
  the only possible interface value (it won't mess with an isochronous
  device that might be set to a different interface).

  The second hunk modifies the behaviour of uvc_video_stop_streaming to
  call SET_INTERFACE(0) unconditionally instead of only calling it for
  isochronous devices. Since interface 0 should already be set on non-
  isochronous devices, it should be safe to set it again, and this way
  devices that are expecting it as a signal to stop streaming will get
  it.

  The patch is against 5.4.137 in the vanilla kernel.org source tree,
  but also applies cleanly to the 5.8.63 kernel in Ubuntu 20.4 LTS and
  to the 5.14-rc3 release candidate kernel.

  Since this is clearly an upstream issue unrelated to any vendor
  modifications, should I also submit an upstream bug report directly to
  bugzilla.kernel.org?

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


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

[Kernel-packages] [Bug 1936009] Please test proposed package

Hello Hui, or anyone else affected,

Accepted alsa-ucm-conf into hirsute-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.4-2ubuntu1.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [SRU] The internal mic of Dell Precision 5750 can't record sound

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Released

Bug description:
  [Impact]
  After upgrade the linux kernel, the mixer names of rt715 is changed, the 
current alsa-ucm-conf will fail to initialize that codec, then users can't 
record sound from internal mic since the internal mic is routed to the codec 
rt715.

  [Fix]
  Backport 3 upstream commits, after applying these 3 commits, the ucm conf 
file dosn't initialize the codec with hardcoded mixer names anymore, it will 
check the existence of the mixer name first, then conditionally initialize the 
codec.

  [Test]
  run 'alsactl init 1' on the precision 5750 with old and new kernel, there is 
no error logs, use the internal mic to record sound, it could record 
successfully.

  [Where problems will occur]
  The change only affects the rt715 codec, so far, that codec only connects to 
the internal mic on Dell soundwire audio machines, so it could introduce 
regression on the internal mic like users can't record sound via internal mic 
anymore on the Dell soundwire audio machines. But this possibility is very low 
since we already tested these 3 commits on different Dell soundwire audio 
machines (latitude and precision). We tested it with old kernel and new kernel, 
all worked well.

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


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

[Kernel-packages] [Bug 1936009] Re: [SRU] The internal mic of Dell Precision 5750 can't record sound

The status should be Fix Committed only when accepted into -proposed,
reverting statuses for now o/

** Changed in: alsa-ucm-conf (Ubuntu Focal)
   Status: Fix Committed => In Progress

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  [SRU] The internal mic of Dell Precision 5750 can't record sound

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Released

Bug description:
  [Impact]
  After upgrade the linux kernel, the mixer names of rt715 is changed, the 
current alsa-ucm-conf will fail to initialize that codec, then users can't 
record sound from internal mic since the internal mic is routed to the codec 
rt715.

  [Fix]
  Backport 3 upstream commits, after applying these 3 commits, the ucm conf 
file dosn't initialize the codec with hardcoded mixer names anymore, it will 
check the existence of the mixer name first, then conditionally initialize the 
codec.

  [Test]
  run 'alsactl init 1' on the precision 5750 with old and new kernel, there is 
no error logs, use the internal mic to record sound, it could record 
successfully.

  [Where problems will occur]
  The change only affects the rt715 codec, so far, that codec only connects to 
the internal mic on Dell soundwire audio machines, so it could introduce 
regression on the internal mic like users can't record sound via internal mic 
anymore on the Dell soundwire audio machines. But this possibility is very low 
since we already tested these 3 commits on different Dell soundwire audio 
machines (latitude and precision). We tested it with old kernel and new kernel, 
all worked well.

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


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

[Kernel-packages] [Bug 1938723] Re: Impish update: v5.13.7 upstream stable release

** Changed in: linux (Ubuntu Impish)
   Status: Confirmed => Fix Committed

** Description changed:

+ SRU Justification
  
- 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:
  
- 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:
+    v5.13.7 upstream stable release
+    from git://git.kernel.org/
  
-v5.13.7 upstream stable release
-from git://git.kernel.org/
+ af_unix: fix garbage collect vs MSG_PEEK
+ workqueue: fix UAF in pwq_unbound_release_workfn()
+ cgroup1: fix leaked context root causing sporadic NULL deref in LTP
+ net/802/mrp: fix memleak in mrp_request_join()
+ net/802/garp: fix memleak in garp_request_join()
+ net: annotate data race around sk_ll_usec
+ sctp: move 198 addresses from unusable to private scope
+ rcu-tasks: Don't delete holdouts within trc_inspect_reader()
+ rcu-tasks: Don't delete holdouts within trc_wait_for_one_reader()
+ ipv6: allocate enough headroom in ip6_finish_output2()
+ nvme-pci: fix multiple races in nvme_setup_io_queues
+ drm/ttm: add a check against null pointer dereference
+ hfs: add missing clean-up in hfs_fill_super
+ hfs: fix high memory mapping in hfs_bnode_read
+ hfs: add lock nesting notation to hfs_find_init
+ firmware: arm_scmi: Fix possible scmi_linux_errmap buffer overflow
+ firmware: arm_scmi: Fix range check for the maximum number of pending messages
+ cifs: fix the out of range assignment to bit fields in parse_server_interfaces
+ iomap: remove the length variable in iomap_seek_data
+ iomap: remove the length variable in iomap_seek_hole
+ ARM: dts: versatile: Fix up interrupt controller node names
+ ipv6: ip6_finish_output2: set sk into newly allocated nskb
+ Linux 5.13.7
+ UBUNTU: upstream stable to v5.13.7

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

Title:
  Impish update: v5.13.7 upstream stable release

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

Bug description:
  SRU Justification

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

     v5.13.7 upstream stable release
     from git://git.kernel.org/

  af_unix: fix garbage collect vs MSG_PEEK
  workqueue: fix UAF in pwq_unbound_release_workfn()
  cgroup1: fix leaked context root causing sporadic NULL deref in LTP
  net/802/mrp: fix memleak in mrp_request_join()
  net/802/garp: fix memleak in garp_request_join()
  net: annotate data race around sk_ll_usec
  sctp: move 198 addresses from unusable to private scope
  rcu-tasks: Don't delete holdouts within trc_inspect_reader()
  rcu-tasks: Don't delete holdouts within trc_wait_for_one_reader()
  ipv6: allocate enough headroom in ip6_finish_output2()
  nvme-pci: fix multiple races in nvme_setup_io_queues
  drm/ttm: add a check against null pointer dereference
  hfs: add missing clean-up in hfs_fill_super
  hfs: fix high memory mapping in hfs_bnode_read
  hfs: add lock nesting notation to hfs_find_init
  firmware: arm_scmi: Fix possible scmi_linux_errmap buffer overflow
  firmware: arm_scmi: Fix range check for the maximum number of pending messages
  cifs: fix the out of range assignment to bit fields in parse_server_interfaces
  iomap: remove the length variable in iomap_seek_data
  iomap: remove the length variable in iomap_seek_hole
  ARM: dts: versatile: Fix up interrupt controller node names
  ipv6: ip6_finish_output2: set sk into newly allocated nskb
  Linux 5.13.7
  UBUNTU: upstream stable to v5.13.7

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


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

[Kernel-packages] [Bug 1938723] Re: Impish update: v5.13.7 upstream stable release

** Changed in: linux (Ubuntu Impish)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

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

Title:
  Impish update: v5.13.7 upstream stable release

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

Bug description:
  SRU Justification

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

     v5.13.7 upstream stable release
     from git://git.kernel.org/

  af_unix: fix garbage collect vs MSG_PEEK
  workqueue: fix UAF in pwq_unbound_release_workfn()
  cgroup1: fix leaked context root causing sporadic NULL deref in LTP
  net/802/mrp: fix memleak in mrp_request_join()
  net/802/garp: fix memleak in garp_request_join()
  net: annotate data race around sk_ll_usec
  sctp: move 198 addresses from unusable to private scope
  rcu-tasks: Don't delete holdouts within trc_inspect_reader()
  rcu-tasks: Don't delete holdouts within trc_wait_for_one_reader()
  ipv6: allocate enough headroom in ip6_finish_output2()
  nvme-pci: fix multiple races in nvme_setup_io_queues
  drm/ttm: add a check against null pointer dereference
  hfs: add missing clean-up in hfs_fill_super
  hfs: fix high memory mapping in hfs_bnode_read
  hfs: add lock nesting notation to hfs_find_init
  firmware: arm_scmi: Fix possible scmi_linux_errmap buffer overflow
  firmware: arm_scmi: Fix range check for the maximum number of pending messages
  cifs: fix the out of range assignment to bit fields in parse_server_interfaces
  iomap: remove the length variable in iomap_seek_data
  iomap: remove the length variable in iomap_seek_hole
  ARM: dts: versatile: Fix up interrupt controller node names
  ipv6: ip6_finish_output2: set sk into newly allocated nskb
  Linux 5.13.7
  UBUNTU: upstream stable to v5.13.7

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


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

[Kernel-packages] [Bug 1938722] [NEW] watchdog: BUG: soft lockup on Threadripper 2950X

2021-08-02 Thread John Stultz

Public bug reported:

Description:Ubuntu 20.04.2 LTS
Release:20.04

Been suddenly seeing a number of crashes today on my threadripper 2950x
box today after the system being off over the weekend.

Suspect it may be tied to Ubuntu 5.4.0-80.90-generic 5.4.124 kernel, as
I wasn't seeing it last week or previously.


Aug  2 16:52:14 threadripper kernel: [  600.168436] watchdog: BUG: soft lockup 
- CPU#19 stuck for 22s! [kworker/19:0:11301]
Aug  2 16:52:14 threadripper kernel: [  600.168490] Modules linked in: veth 
xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf
_nat br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_hda_codec_realtek 
snd_hda_codec_generic 
ledtrig_audio snd_hda_codec_hdmi eeepc_wmi snd_hda_intel edac_mce_amd 
snd_intel_dspcfg asus_wmi ftdi_sio snd_hda_codec kvm_amd usbserial 
sparse_keymap snd_
hda_core kvm video wmi_bmof snd_hwdep snd_pcm snd_timer snd ccp soundcore 
k10temp mac_hid nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt 
nf_log_ipv4 
nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype 
sch_fq_codel xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
ip6table
_filter ip6_tables iptable_filter bpfilter ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid 
hid uas usb_storage amdgpu
Aug  2 16:52:14 threadripper kernel: [  600.168542]  amd_iommu_v2 gpu_sched 
crct10dif_pclmul ttm crc32_pclmul ghash_clmulni_intel drm_kms_helper syscopyare
a aesni_intel crypto_simd mxm_wmi sysfillrect cryptd sysimgblt glue_helper 
fb_sys_fops igb drm dca i2c_piix4 ahci i2c_algo_bit libahci gpio_amdpt wmi gpio_
generic
Aug  2 16:52:14 threadripper kernel: [  600.168558] CPU: 19 PID: 11301 Comm: 
kworker/19:0 Tainted: G L5.4.0-80-generic #90-Ubuntu
Aug  2 16:52:14 threadripper kernel: [  600.168559] Hardware name: System 
manufacturer System Product Name/ROG STRIX X399-E GAMING, BIOS 1203 10/09/2019
Aug  2 16:52:14 threadripper kernel: [  600.168569] Workqueue: events free_work
Aug  2 16:52:14 threadripper kernel: [  600.168574] RIP: 
0010:smp_call_function_many+0x205/0x270
Aug  2 16:52:14 threadripper kernel: [  600.168576] Code: e8 50 10 92 00 3b 05 
ae cf 70 01 89 c7 0f 83 9b fe ff ff 48 63 c7 48 8b 0b 48 03 0c c5 80 99 64 a
1 8b 41 18 a8 01 74 0a f3 90 <8b> 51 18 83 e2 01 75 f6 eb c8 89 cf 48 c7 c2 a0 
b8 a4 a1 4c 89 fe
Aug  2 16:52:14 threadripper kernel: [  600.168577] RSP: 0018:b66b0aa17d00 
EFLAGS: 0202 ORIG_RAX: ff13
Aug  2 16:52:14 threadripper kernel: [  600.168579] RAX: 0003 RBX: 
8de1fd4ebd40 RCX: 8de1fd0b2540
Aug  2 16:52:14 threadripper kernel: [  600.168580] RDX: 0001 RSI: 
 RDI: 0002
Aug  2 16:52:14 threadripper kernel: [  600.168580] RBP: b66b0aa17d40 R08: 
8de1f6da7190 R09: 0003
Aug  2 16:52:14 threadripper kernel: [  600.168581] R10: 8de1f6da7190 R11: 
0002 R12: a0281930
Aug  2 16:52:14 threadripper kernel: [  600.168581] R13:  R14: 
0001 R15: 0080
Aug  2 16:52:14 threadripper kernel: [  600.168583] FS:  () 
GS:8de1fd4c() knlGS:
Aug  2 16:52:14 threadripper kernel: [  600.168583] CS:  0010 DS:  ES:  
CR0: 80050033
Aug  2 16:52:14 threadripper kernel: [  600.168584] CR2: 55ea29edefd0 CR3: 
0009c500a000 CR4: 003406e0
Aug  2 16:52:14 threadripper kernel: [  600.168585] Call Trace:
Aug  2 16:52:14 threadripper kernel: [  600.168592]  ? load_new_mm_cr3+0xf0/0xf0
Aug  2 16:52:14 threadripper kernel: [  600.168594]  on_each_cpu+0x2d/0x60
Aug  2 16:52:14 threadripper kernel: [  600.168596]  
flush_tlb_kernel_range+0x38/0x90
Aug  2 16:52:14 threadripper kernel: [  600.168597]  
__purge_vmap_area_lazy+0x70/0x6d0
Aug  2 16:52:14 threadripper kernel: [  600.168598]  
free_vmap_area_noflush+0xe1/0xf0
Aug  2 16:52:14 threadripper kernel: [  600.168600]  remove_vm_area+0x9a/0xb0
Aug  2 16:52:14 threadripper kernel: [  600.168602]  __vunmap+0x5f/0x210
Aug  2 16:52:14 threadripper kernel: [  600.168603]  free_work+0x25/0x30
Aug  2 16:52:14 threadripper kernel: [  600.168607]  
process_one_work+0x1eb/0x3b0
Aug  2 16:52:14 threadripper kernel: [  600.168609]  worker_thread+0x4d/0x400
Aug  2 16:52:14 threadripper kernel: [  600.168611]  kthread+0x104/0x140
Aug  2 16:52:14 threadripper kernel: [  600.168612]  ? 
process_one_work+0x3b0/0x3b0
Aug  2 16:52:14 threadripper kernel: [  600.168613]  ? kthread_park+0x90/0x90
Aug  2 16:52:14 threadripper kernel: [  600.168617]  ret_from_fork+0x22/0x40
Aug  2 16:52:40 threadripper kernel: [  606.280524] rcu: INFO: rcu_sched 
detected stalls on CPUs/tasks:
Aug  2 16:52:40 threadripper kernel: [  606.280567] rcu:2-...0: (1 GPs

[Kernel-packages] [Bug 1938723] [NEW] Impish update: v5.13.7 upstream stable release

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:

   v5.13.7 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Impish)
   Importance: Undecided
   Status: 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/1938723

Title:
  Impish update: v5.13.7 upstream stable release

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

Bug description:
  
  SRU Justification

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

 v5.13.7 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2021-08-02 Thread bmaupin

Can someone with administrative permissions mark that this bug also
affects Focal? 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/1808418

Title:
  Thinkpad T430u won't boot without noapic workaround

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

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2021-08-02 Thread bmaupin

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

Title:
  Thinkpad T430u won't boot without noapic workaround

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

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1938720] Re: hirsute:linux-oracle ubuntu_ltp_syscalls fail "ERROR| Exception escaping from test"

2021-08-02 Thread Tim Gardner

** Tags added: amd64 oracle sru-20210719

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

Title:
  hirsute:linux-oracle ubuntu_ltp_syscalls fail "ERROR| Exception
  escaping from test"

Status in linux-oracle package in Ubuntu:
  New
Status in linux-oracle source package in Hirsute:
  New

Bug description:
  23:53:29 ERROR| Exception escaping from test:
  Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
File 
"/home/ubuntu/autotest/client/tests/ubuntu_ltp_syscalls/ubuntu_ltp_syscalls.py",
 line 227, in run_once
  raise error.TestFail()
  TestFail

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


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

[Kernel-packages] [Bug 1938720] Re: hirsute:linux-oracle ubuntu_ltp_syscalls fail "ERROR| Exception escaping from test"

2021-08-02 Thread Tim Gardner

** Attachment added: "Failure log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1938720/+attachment/5515372/+files/ltp_syscalls.txt

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

Title:
  hirsute:linux-oracle ubuntu_ltp_syscalls fail "ERROR| Exception
  escaping from test"

Status in linux-oracle package in Ubuntu:
  New
Status in linux-oracle source package in Hirsute:
  New

Bug description:
  23:53:29 ERROR| Exception escaping from test:
  Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
File 
"/home/ubuntu/autotest/client/tests/ubuntu_ltp_syscalls/ubuntu_ltp_syscalls.py",
 line 227, in run_once
  raise error.TestFail()
  TestFail

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


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

[Kernel-packages] [Bug 1938720] [NEW] hirsute:linux-oracle ubuntu_ltp_syscalls fail "ERROR| Exception escaping from test"

2021-08-02 Thread Tim Gardner

Public bug reported:

23:53:29 ERROR| Exception escaping from test:
Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
return func(*args, **dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
self.run_once(*args, **dargs)
  File 
"/home/ubuntu/autotest/client/tests/ubuntu_ltp_syscalls/ubuntu_ltp_syscalls.py",
 line 227, in run_once
raise error.TestFail()
TestFail

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

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


** Tags: amd64 oracle sru-20210719 ubuntu-ltp-syscalls

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

** Tags added: ubuntu-ltp-syscalls

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

Title:
  hirsute:linux-oracle ubuntu_ltp_syscalls fail "ERROR| Exception
  escaping from test"

Status in linux-oracle package in Ubuntu:
  New
Status in linux-oracle source package in Hirsute:
  New

Bug description:
  23:53:29 ERROR| Exception escaping from test:
  Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
File 
"/home/ubuntu/autotest/client/tests/ubuntu_ltp_syscalls/ubuntu_ltp_syscalls.py",
 line 227, in run_once
  raise error.TestFail()
  TestFail

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


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

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2021-08-02 Thread bmaupin

I just installed a few kernels to see if I could narrow down the latest
regression, and this is what I found:

- 5.7.0-050700 boots fine
- 5.7.5-050705 exhibits the problematic behaviour (does not boot)
- The latest kernel (5.13.7-051307) also does not boot

I doubt this is helpful, but these are the last log lines shown on 5.7.0
on a successful boot right before the GUI kicks in; I'm not sure if
they're meaningful since they're just a few lines from the log as a
whole:

[5.999124] ACPI: \_SB_.PCI0.LPCB.EC__.HKEY: BCTG evaluated but flagged as 
error
[5.999126] thinkpad_acpi: Error probing battery 2
[5.999135] battery: extension failed to load: ThinkPad Battery Extension
[8.097361] Bluetooth: hci0: command 0x1001 tx timeout

I guess at this point I need to do another bisect between 5.7.0 and
5.7.5. Here goes...

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

Title:
  Thinkpad T430u won't boot without noapic workaround

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

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1931779] Re: kdump just hung out of the box

2021-08-02 Thread Guilherme G. Piccoli

Oh yeah, it would be awesome to set such message...but I'm not sure how
we can do it! If we know beforehand that the reserved memory amount
won't work for your system, to show the message..why we don't just fix
it?

The problem is that this is a policy, there is no technical mechanism
(currently) that foresees that a quantity of RAM equals X is required
for your system in order kdump to work. We have the heuristic (aka sets
crashkernel to 192M), which is expected to work on the majority of
machines. Hence, the recommendation for kdump users is to install the
package and perform a dummy kdump, as you did! If it fails, go ahead and
fine tune that.

With the estimator I've pointed you in the last comment, things should improve, 
having a mechanism that will suggest a proper amount, pre-calculated on boot 
time. But until we get that merged, this situation is not ideal and will remain 
like this - I understand it's not the best, if you have a technical suggestion 
on how we could improve it, it's highly appreciated =)
Cheers,


Guilherme

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

Title:
  kdump just hung out of the box

Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date
  20.04 system, installed specifically to try reproducing a bug.

  But when I tried, after kdump-config status reported "ready to dump"
  on reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the
  panic to console and then just hung forever.

  After some blind guessing and twiddling both variables, I found that
  crashkernel=512M-:256M works on this particular setup. (MS7850
  motherboard, i5-4670 CPU, 5.4.0-42-generic kernel)

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


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

[Kernel-packages] [Bug 1875577] Re: Encrypted swap won't load on 20.04 with zfs root

2021-08-02 Thread Heitor Alves de Siqueira

Validated with ZFS from focal-proposed, according to test case from description:
ubuntu@z-rotomvm34:~$ dpkg -l | grep zfsutils
ii  zfsutils-linux   0.8.3-1ubuntu12.12
amd64command-line tools to manage OpenZFS filesystems
ubuntu@z-rotomvm34:~$ zfs list
NAME USED  AVAIL REFER  MOUNTPOINT
rpool   2.50G  25.6G  176K  /
rpool/ROOT  2.50G  25.6G  176K  none
rpool/ROOT/zfsroot  2.50G  25.6G 2.50G  /
ubuntu@z-rotomvm34:~$ sudo journalctl -b | grep -i ordering
ubuntu@z-rotomvm34:~$ lsblk -e 7
NAMEMAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
vda 252:00   30G  0 disk
├─vda1  252:10  512M  0 part  /boot/efi
└─vda2  252:20 29.5G  0 part
nvme0n1 259:00  9.8G  0 disk
└─nvme0n1p1 259:10  9.8G  0 part
  └─swap253:00  9.8G  0 crypt [SWAP]

In addition to the test above, I've also tested the configurations
suggested in the [Test Plan] section. Besides validating the ordering
bug, I've also done basic smoke tests and verified that the ZFS pools
are working as expected.

- Encrypted rootfs on LVM + separate ZFS partitions:
ubuntu@ubuntu-focal:~$ zfs list
NAME   USED  AVAIL REFER  MOUNTPOINT
zfspool492K  4.36G   96K  /mnt/zfspool
zfspool/tank96K  4.36G   96K  /mnt/zfspool/tank
ubuntu@ubuntu-focal:~$ dpkg -l | grep zfsutils
ii  zfsutils-linux   0.8.3-1ubuntu12.12
amd64command-line tools to manage OpenZFS filesystems
ubuntu@ubuntu-focal:~$ zfs list
NAME   USED  AVAIL REFER  MOUNTPOINT
zfspool492K  4.36G   96K  /mnt/zfspool
zfspool/tank96K  4.36G   96K  /mnt/zfspool/tank
ubuntu@ubuntu-focal:~$ sudo journalctl -b | grep -i ordering
ubuntu@ubuntu-focal:~$ lsblk -e7
NAME MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
sr0   11:01 1024M  0 rom
vda  252:00   30G  0 disk
├─vda1   252:10  512M  0 part  /boot/efi
├─vda2   252:201K  0 part
├─vda5   252:50  731M  0 part  /boot
└─vda6   252:60 28.8G  0 part
  └─vda6_crypt   253:00 28.8G  0 crypt
├─vgubuntu--focal-root   253:10 27.8G  0 lvm   /
└─vgubuntu--focal-swap_1 253:20  980M  0 lvm   [SWAP]
vdb  252:16   05G  0 disk
├─vdb1   252:17   05G  0 part
└─vdb9   252:25   08M  0 part

- ZFS on LUKS
ubuntu@z-rotomvm33:~$ dpkg -l | grep zfsutils
ii  zfsutils-linux   0.8.3-1ubuntu12.12
amd64command-line tools to manage OpenZFS filesystems
ubuntu@z-rotomvm33:~$ zfs list
NAME   USED  AVAIL REFER  MOUNTPOINT
zfspool612K  9.20G   96K  /mnt/zfspool
zfspool/tank96K  9.20G   96K  /mnt/zfspool/tank
ubuntu@z-rotomvm33:~$ sudo journalctl -b | grep -i ordering
ubuntu@z-rotomvm33:~$ lsblk -e7
NAMEMAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
vda 252:00   30G  0 disk
├─vda1  252:10  512M  0 part  /boot/efi
└─vda2  252:20 29.5G  0 part  /
nvme0n1 259:00  9.8G  0 disk
└─nvme0n1p1 259:10  9.8G  0 part
  └─zfspool 253:00  9.8G  0 crypt
ubuntu@z-rotomvm33:~$ cat /etc/crypttab
# 
zfspool /dev/nvme0n1p1 /etc/keyfile luks

- ZFS on dm-raid
ubuntu@z-rotomvm33:~$ dpkg -l | grep zfsutils
ii  zfsutils-linux   0.8.3-1ubuntu12.12
amd64command-line tools to manage OpenZFS filesystems
ubuntu@z-rotomvm33:~$ zfs list
NAME   USED  AVAIL REFER  MOUNTPOINT
zfspool612K  9.20G   96K  /mnt/zfspool
zfspool/tank96K  9.20G   96K  /mnt/zfspool/tank
ubuntu@z-rotomvm33:~$ sudo journalctl -b | grep -i ordering
ubuntu@z-rotomvm33:~$ lsblk -e7
NAMEMAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
vda 252:00   30G  0 disk
├─vda1  252:10  512M  0 part  /boot/efi
└─vda2  252:20 29.5G  0 part  /
nvme0n1 259:00  9.8G  0 disk
└─md127   9:127  0  9.8G  0 raid0
  ├─md127p1 259:10  9.8G  0 part
  └─md127p9 259:208M  0 part


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

Title:
  Encrypted swap won't load on 20.04 with zfs root

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Encrypted swap partitions may not load correctly with ZFS root, due to 
ordering cycle on zfs-mount.service.

  [Test Plan]
  1. Install Ubuntu 20.04 using ZFS-on-root
  2. Add encrypted partition to /etc/crypttab:
     swap/dev/nvme0n1p1  /dev/urandom
swap,cipher=aes-xts-plain64,size=256
  3. Add swap

[Kernel-packages] [Bug 1931779] Re: kdump just hung out of the box

2021-08-02 Thread Rich

I suppose I should have made it clear that just changing the amount of
memory reserved was not sufficient.

Perhaps it would be useful to print a message saying "hey, I know we set
something by default, but we don't expect that to actually work, so you
should probably test and adjust it"?

Because it sounds like it's not expected to work out of the box, and
configuring it to "on, but doesn't actually work or warn you" when you
install the package seems worse than not configuring it, similar to how
I wouldn't expect installing ccache to result in it sticking itself in
my PATH, reporting "ccache enabled and working" when asked, but then
defaulting to a max cache size of 4 kilobytes.

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

Title:
  kdump just hung out of the box

Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date
  20.04 system, installed specifically to try reproducing a bug.

  But when I tried, after kdump-config status reported "ready to dump"
  on reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the
  panic to console and then just hung forever.

  After some blind guessing and twiddling both variables, I found that
  crashkernel=512M-:256M works on this particular setup. (MS7850
  motherboard, i5-4670 CPU, 5.4.0-42-generic kernel)

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


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

[Kernel-packages] [Bug 1688716] Re: screen turns black after reopening lid (laptop)

2021-08-02 Thread Norbert

** Changed in: ubuntu-mate
   Status: Incomplete => Won't Fix

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

Title:
  screen turns black after reopening lid (laptop)

Status in Ubuntu MATE:
  Won't Fix
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I close the laptop lid, the laptop hibernates/(suspends?). When I
  reopen the lid, the fans starts again but the screen is completely
  black.

  I'm running Ubuntu MATE 16.04.2 LTS (installed yesterday) on a ASUS TP301U.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vilhelm1852 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=78779645-e369-460f-92fa-fdef01ab1941
  InstallationDate: Installed on 2017-05-12 (112 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b568 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. TP301UJ
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=200c5644-817b-4c85-a997-011c9c0cfe6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP301UJ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP301UJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP301UJ.300:bd06/01/2016:svnASUSTeKCOMPUTERINC.:pnTP301UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP301UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: TP301UJ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vilhelm1852 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=78779645-e369-460f-92fa-fdef01ab1941
  InstallationDate: Installed on 2017-05-12 (112 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b568 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. TP301UJ
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=200c5644-817b-4c85-a997-011c9c0cfe6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP301UJ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP301UJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP301UJ.300:bd06/01/2016:svnASUSTeKCOMPUTERINC.:pnTP301UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP301UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: TP301UJ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1931779] Re: kdump just hung out of the box

2021-08-02 Thread Guilherme G. Piccoli

Thank you for the report! I think the problem was memory then, you
nailed it - by reserving more memory, you were able to make it work.
This is a policy and currently, the default is a bit conservative in
order to not waste memory. It works in most of the systems...

We have a memory estimator project [0] that (hopefully) will help users to 
determine the proper amount of reserved memory for their systems. For now, I 
guess we can consider this bug fixed (by the reporter!).
Cheers,


Guilherme


[0] https://salsa.debian.org/debian/kdump-tools/-/merge_requests/13

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

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

Title:
  kdump just hung out of the box

Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date
  20.04 system, installed specifically to try reproducing a bug.

  But when I tried, after kdump-config status reported "ready to dump"
  on reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the
  panic to console and then just hung forever.

  After some blind guessing and twiddling both variables, I found that
  crashkernel=512M-:256M works on this particular setup. (MS7850
  motherboard, i5-4670 CPU, 5.4.0-42-generic kernel)

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


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

[Kernel-packages] [Bug 1938669] Re: Epiphan framegrabbers stream only once then need unbinding/rebinding to uvcvideo to work again

2021-08-02 Thread Kai-Heng Feng

If possible, please send the patch to mailing list directly, that's the
quickest way to get the patch merged.

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

Title:
  Epiphan framegrabbers stream only once then need unbinding/rebinding
  to uvcvideo to work again

Status in linux package in Ubuntu:
  New

Bug description:
  Video capture devices made by Epiphan Systems (vendor id 0x2b77) work
  once, but as soon as the video device is closed (or even if it is kept
  open but the application issues a VIDIOC_STREAMOFF ioctl) it won't
  work again - subsequent calls to VIDOC_DQBUF simply hang - until the
  device is unbound from and rebound to the uvcvideo module. (modprobe
  -r uvcvideo; modprobe uvcvideo also works).

  For example:

ffplay /dev/video0  -- works fine and shows the captured stream.

ffplay /dev/video0  -- when run a second time: hangs and does not
  capture anything

modprobe -r uvcvideo ; modprobe uvcvideo; ffplay /dev/video  --
  works fine again.

  Experimenting with the device and the uvcvideo module source code
  reveals that problem is the device is expecting SET_INTERFACE(0) to be
  sent to return it to a state where it can accept control requests and
  start streaming again.

  The code in uvc_video.c has several comments stating that some bulk-
  transfer devices require a SET_INTERFACE(0) call to be made before any
  control commands, even though 0 is already the default and only valid
  interface value. And, the function uvc_video_init makes such a call
  (which is why the device starts working again after rebinding to the
  uvcvideo module). But no such call is made when streaming is stopped
  then restarted.

  Furthermore, SET_INTERFACE(0) is the mechanism by which isochronous
  devices are told to stop streaming, and the comments in
  uvc_video_stop_streaming state that the UVC specification is unclear
  on how a bulk-based device should be told to stop streaming, so it is
  reasonable to expect this particular bulk-based device might be
  expecting the same SET_INTERFACE(0) call that an isochronous device
  would get as means of being told to stop streaming.

  The attached patch fixes the problem for these Epiphan devices by
  adding a SET_INTERFACE(0) call in two places. Either one by itself is
  sufficient to resolve the symptoms but I think it is probably safest
  to include both.

  The first hunk adds a SET_INTERFACE(0) call in
  uvc_video_start_streaming, but only in the bulk-based case where 0 is
  the only possible interface value (it won't mess with an isochronous
  device that might be set to a different interface).

  The second hunk modifies the behaviour of uvc_video_stop_streaming to
  call SET_INTERFACE(0) unconditionally instead of only calling it for
  isochronous devices. Since interface 0 should already be set on non-
  isochronous devices, it should be safe to set it again, and this way
  devices that are expecting it as a signal to stop streaming will get
  it.

  The patch is against 5.4.137 in the vanilla kernel.org source tree,
  but also applies cleanly to the 5.8.63 kernel in Ubuntu 20.4 LTS and
  to the 5.14-rc3 release candidate kernel.

  Since this is clearly an upstream issue unrelated to any vendor
  modifications, should I also submit an upstream bug report directly to
  bugzilla.kernel.org?

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


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

[Kernel-packages] [Bug 1938713] Re: Focal update: v5.4.133 upstream stable release

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

** Description changed:

+ SRU Justification
  
- 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:
  
- 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:
+    v5.4.133 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.133 upstream stable release
-from git://git.kernel.org/
+ drm/mxsfb: Don't select DRM_KMS_FB_HELPER
+ drm/zte: Don't select DRM_KMS_FB_HELPER
+ drm/amd/amdgpu/sriov disable all ip hw status by default
+ drm/vc4: fix argument ordering in vc4_crtc_get_margins()
+ net: pch_gbe: Use proper accessors to BE data in pch_ptp_match()
+ drm/amd/display: fix use_max_lb flag for 420 pixel formats
+ hugetlb: clear huge pte during flush function on mips platform
+ atm: iphase: fix possible use-after-free in ia_module_exit()
+ mISDN: fix possible use-after-free in HFC_cleanup()
+ atm: nicstar: Fix possible use-after-free in nicstar_cleanup()
+ net: Treat __napi_schedule_irqoff() as __napi_schedule() on PREEMPT_RT
+ drm/mediatek: Fix PM reference leak in mtk_crtc_ddp_hw_init()
+ reiserfs: add check for invalid 1st journal block
+ drm/virtio: Fix double free on probe failure
+ drm/sched: Avoid data corruptions
+ udf: Fix NULL pointer dereference in udf_symlink function
+ e100: handle eeprom as little endian
+ igb: handle vlan types with checker enabled
+ drm/bridge: cdns: Fix PM reference leak in cdns_dsi_transfer()
+ clk: renesas: r8a77995: Add ZA2 clock
+ clk: tegra: Ensure that PLLU configuration is applied properly
+ ipv6: use prandom_u32() for ID generation
+ RDMA/cxgb4: Fix missing error code in create_qp()
+ dm space maps: don't reset space map allocation cursor when committing
+ pinctrl: mcp23s08: fix race condition in irq handler
+ ice: set the value of global config lock timeout longer
+ virtio_net: Remove BUG() to avoid machine dead
+ net: bcmgenet: check return value after calling platform_get_resource()
+ net: mvpp2: check return value after calling platform_get_resource()
+ net: micrel: check return value after calling platform_get_resource()
+ drm/amd/display: Update scaling settings on modeset
+ drm/amd/display: Release MST resources on switch from MST to SST
+ drm/amd/display: Set DISPCLK_MAX_ERRDET_CYCLES to 7
+ drm/amdkfd: use allowed domain for vmbo validation
+ fjes: check return value after calling platform_get_resource()
+ selinux: use __GFP_NOWARN with GFP_NOWAIT in the AVC
+ r8169: avoid link-up interrupt issue on RTL8106e if user enables ASPM
+ drm/amd/display: Verify Gamma & Degamma LUT sizes in amdgpu_dm_atomic_check
+ xfrm: Fix error reporting in xfrm_state_construct.
+ wlcore/wl12xx: Fix wl12xx get_mac error if device is in ELP
+ wl1251: Fix possible buffer overflow in wl1251_cmd_scan
+ cw1200: add missing MODULE_DEVICE_TABLE
+ bpf: Fix up register-based shifts in interpreter to silence KUBSAN
+ mt76: mt7615: fix fixed-rate tx status reporting
+ net: fix mistake path for netdev_features_strings
+ net: sched: fix error return code in tcf_del_walker()
+ drm/amdkfd: Walk through list with dqm lock hold
+ rtl8xxxu: Fix device info for RTL8192EU devices
+ atm: nicstar: use 'dma_free_coherent' instead of 'kfree'
+ atm: nicstar: register the interrupt handler in the right place
+ vsock: notify server to shutdown when client has pending signal
+ RDMA/rxe: Don't overwrite errno from ib_umem_get()
+ iwlwifi: mvm: don't change band on bound PHY contexts
+ iwlwifi: pcie: free IML DMA memory allocation
+ iwlwifi: pcie: fix context info freeing
+ sfc: avoid double pci_remove of VFs
+ sfc: error code if SRIOV cannot be disabled
+ wireless: wext-spy: Fix out-of-bounds warning
+ media, bpf: Do not copy more entries than user space requested
+ net: ip: avoid OOM kills with large UDP sends over loopback
+ RDMA/cma: Fix rdma_resolve_route() memory leak
+ Bluetooth: btusb: Fixed too many in-token issue for Mediatek Chip.
+ Bluetooth: Fix the HCI to MGMT status conversion

[Kernel-packages] [Bug 1938713] [NEW] Focal update: v5.4.133 upstream stable release

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:

   v5.4.133 upstream stable release
   from git://git.kernel.org/

drm/mxsfb: Don't select DRM_KMS_FB_HELPER
drm/zte: Don't select DRM_KMS_FB_HELPER
drm/amd/amdgpu/sriov disable all ip hw status by default
drm/vc4: fix argument ordering in vc4_crtc_get_margins()
net: pch_gbe: Use proper accessors to BE data in pch_ptp_match()
drm/amd/display: fix use_max_lb flag for 420 pixel formats
hugetlb: clear huge pte during flush function on mips platform
atm: iphase: fix possible use-after-free in ia_module_exit()
mISDN: fix possible use-after-free in HFC_cleanup()
atm: nicstar: Fix possible use-after-free in nicstar_cleanup()
net: Treat __napi_schedule_irqoff() as __napi_schedule() on PREEMPT_RT
drm/mediatek: Fix PM reference leak in mtk_crtc_ddp_hw_init()
reiserfs: add check for invalid 1st journal block
drm/virtio: Fix double free on probe failure
drm/sched: Avoid data corruptions
udf: Fix NULL pointer dereference in udf_symlink function
e100: handle eeprom as little endian
igb: handle vlan types with checker enabled
drm/bridge: cdns: Fix PM reference leak in cdns_dsi_transfer()
clk: renesas: r8a77995: Add ZA2 clock
clk: tegra: Ensure that PLLU configuration is applied properly
ipv6: use prandom_u32() for ID generation
RDMA/cxgb4: Fix missing error code in create_qp()
dm space maps: don't reset space map allocation cursor when committing
pinctrl: mcp23s08: fix race condition in irq handler
ice: set the value of global config lock timeout longer
virtio_net: Remove BUG() to avoid machine dead
net: bcmgenet: check return value after calling platform_get_resource()
net: mvpp2: check return value after calling platform_get_resource()
net: micrel: check return value after calling platform_get_resource()
drm/amd/display: Update scaling settings on modeset
drm/amd/display: Release MST resources on switch from MST to SST
drm/amd/display: Set DISPCLK_MAX_ERRDET_CYCLES to 7
drm/amdkfd: use allowed domain for vmbo validation
fjes: check return value after calling platform_get_resource()
selinux: use __GFP_NOWARN with GFP_NOWAIT in the AVC
r8169: avoid link-up interrupt issue on RTL8106e if user enables ASPM
drm/amd/display: Verify Gamma & Degamma LUT sizes in amdgpu_dm_atomic_check
xfrm: Fix error reporting in xfrm_state_construct.
wlcore/wl12xx: Fix wl12xx get_mac error if device is in ELP
wl1251: Fix possible buffer overflow in wl1251_cmd_scan
cw1200: add missing MODULE_DEVICE_TABLE
bpf: Fix up register-based shifts in interpreter to silence KUBSAN
mt76: mt7615: fix fixed-rate tx status reporting
net: fix mistake path for netdev_features_strings
net: sched: fix error return code in tcf_del_walker()
drm/amdkfd: Walk through list with dqm lock hold
rtl8xxxu: Fix device info for RTL8192EU devices
atm: nicstar: use 'dma_free_coherent' instead of 'kfree'
atm: nicstar: register the interrupt handler in the right place
vsock: notify server to shutdown when client has pending signal
RDMA/rxe: Don't overwrite errno from ib_umem_get()
iwlwifi: mvm: don't change band on bound PHY contexts
iwlwifi: pcie: free IML DMA memory allocation
iwlwifi: pcie: fix context info freeing
sfc: avoid double pci_remove of VFs
sfc: error code if SRIOV cannot be disabled
wireless: wext-spy: Fix out-of-bounds warning
media, bpf: Do not copy more entries than user space requested
net: ip: avoid OOM kills with large UDP sends over loopback
RDMA/cma: Fix rdma_resolve_route() memory leak
Bluetooth: btusb: Fixed too many in-token issue for Mediatek Chip.
Bluetooth: Fix the HCI to MGMT status conversion table
Bluetooth: Shutdown controller after workqueues are flushed or cancelled
Bluetooth: btusb: fix bt fiwmare downloading failure issue for qca btsoc.
sctp: validate from_addr_param return
sctp: add size validation when walking chunks
MIPS: loongsoon64: Reserve memory below starting pfn to prevent Oops
MIPS: set mips32r5 for virt extensions
fscrypt: don't ignore minor_hash when hash is 0
crypto: ccp - Annotate SEV Firmware file names
perf bench: Fix 2 memory sanitizer warnings
powerpc/mm: Fix lockup on kernel exec fault
powerpc/barrier: Avoid collision with clang's __lwsync macro
drm/amdgpu: Update NV SIMD-per-CU to 2
drm/radeon: Add the missed drm_gem_object_put() in 
radeon_user_framebuffer_create()
drm/rockchip: dsi: remove extra component_del() call
drm/amd/display: fix incorrrect valid irq check
pinctrl/amd: Add device HID for new AMD GPIO controller
drm/tegra: Don't set allow_fb_modifiers explicitly
drm/msm/mdp4: Fix modifier support enabling
drm/arm/malidp: Always list modifiers

[Kernel-packages] [Bug 1938699] Re: cpu-checker: riscv64 build missing

2021-08-02 Thread Julian Andres Klode

cpu-checker (0.7-1.2) experimental; urgency=medium


will be synced shortly with those changes

** Changed in: cpu-checker (Ubuntu)
   Status: New => Fix Committed

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

Title:
  cpu-checker: riscv64 build missing

Status in cpu-checker package in Ubuntu:
  Fix Committed

Bug description:
  cpu-checker builds fine for RISC-V once architecture riscv64 is added to 
debian/control.
  A patch for kvm-ok is needed to add a /dev/kvm check for the RISC-V 
architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpu-checker/+bug/1938699/+subscriptions


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

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

2021-08-02 Thread giacof

Thank you, I have already installed it. The missing one is for
5.11.0-24, as I said before.

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

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

Status in linux package in Ubuntu:
  New

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

  This is what I get from dmesg:

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

  Here is some system information:

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

[Kernel-packages] [Bug 1938705] [NEW] dmidecode: not built on riscv64

2021-08-02 Thread Heinrich Schuchardt

Public bug reported:

riscv64 is missinag in debian/control

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


** Tags: fr-1546

** Tags added: fr-1546

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

Title:
  dmidecode: not built on riscv64

Status in dmidecode package in Ubuntu:
  New

Bug description:
  riscv64 is missinag in debian/control

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


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

[Kernel-packages] [Bug 1938530] Re: arm64: virtio_blk is not included in the initramfs

2021-08-02 Thread Juerg Haefliger

What exactly are you trying to do? virtio_blk is not required to boot
UC20 on real HW...

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

Title:
  arm64: virtio_blk is not included in the initramfs

Status in linux-meta package in Ubuntu:
  New

Bug description:
  The virtio_blk module is not included by default in the initramfs for
  arm64, so UC20 cannot boot as expected.

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


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

[Kernel-packages] [Bug 1938699] Re: cpu-checker: riscv64 build missing

2021-08-02 Thread Heinrich Schuchardt

** Tags added: fr-1545

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

Title:
  cpu-checker: riscv64 build missing

Status in cpu-checker package in Ubuntu:
  New

Bug description:
  cpu-checker builds fine for RISC-V once architecture riscv64 is added to 
debian/control.
  A patch for kvm-ok is needed to add a /dev/kvm check for the RISC-V 
architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpu-checker/+bug/1938699/+subscriptions


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

[Kernel-packages] [Bug 1923638] Re: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11

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

This bug was fixed in the package evdi - 1.9.1-1ubuntu4~20.04.1

---
evdi (1.9.1-1ubuntu4~20.04.1) focal; urgency=medium

  * Support USB-less systems (e.g. s390x). (LP: #1932163)

evdi (1.9.1-1ubuntu4) impish; urgency=medium

  * Support USB-less systems (e.g. s390x). (LP: #1932163)

evdi (1.9.1-1ubuntu3~20.04.1) focal; urgency=medium

  * Backport to focal to add support to 5.11 kernels. (LP: #1932163)

evdi (1.9.1-1ubuntu3) impish; urgency=medium

  * Fix regression with Linux 5.11

evdi (1.9.1-1ubuntu2) impish; urgency=medium

  * Fix build with Linux 5.13

evdi (1.9.1-1ubuntu1) hirsute; urgency=medium

  * New upstream release 1.9.1
  * Fix build with Linux 5.11 (LP: #1923638)
- 
debian/patches/0001-Merge-branch-private-dczerwik-enable-cursor-ioctl-in.patch
- debian/patches/0002-Add-support-for-5.11-and-5.12-kernels.patch

evdi (1.9.0+dfsg-1) unstable; urgency=medium

  * new upstream release 1.9.0
- fixes incompatibility with newer kernels
  (closes: #973837, #975456)
  * Updated d/libevdi0.symbols

 -- Andrea Righi   Tue, 20 Jul 2021 14:32:12
+

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

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

Title:
  [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11

Status in evdi package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in evdi source package in Focal:
  Fix Released

Bug description:
  evdi-dkms in hirsute cannot be used with the 5.11 kernel in hirsute as
  it will fail to build. Upstream updates for 5.11 proved problematic,
  and a working set of updates became available in the upstream project
  only recently. Unfortunately these updates are difficult to backport
  due to upstream changes, and if they are backported the kernel team
  has no access to hardware to confirm that the backports function as
  intended. Therefore the safest course of action seems to be to move
  forward to the latest upstream evdi release plus they fixes for 5.11
  from git, which has been tested by a number of evdi users already.

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


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

[Kernel-packages] [Bug 1938697] Re: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic

2021-08-02 Thread Paul White

** Tags added: focal

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

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

Title:
  Kernel driver support issue between  5.4.0-74-generic and
  5.4.0-80-generic

Status in linux package in Ubuntu:
  New

Bug description:
  I have found an issue after upgrading my Kernel from 5.4.0-74-generic
  to 5.4.0-80-generic on Ubuntu 20.04.

  It appears that support for the second ethernet port on my Lenovo
  m90n-1 has been dropped or isn't working as expected.  After upgrading
  to 5.4.0-80-generic my second ethernet port

  Both ethernet ports use the r8169 driver.  If I switch back to the
  previous kernel 5.4.0-74-generic.  The second ethernet port is usable
  again.

  I did attempt under 5.4.0-80-generic to see if I could get an error
  message.  When the driver attempts to discover the second ethernet
  port the following error is thrown.

 "unknown chip XID fcf"

  Support output below:

  
  --- Before update.

  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64)

  root@lenovo-test-3:~# lshw -c network
*-network DISABLED
 description: Wireless interface
 product: Cannon Point-LP CNVi [Wireless-AC]
 vendor: Intel Corporation
 physical id: 14.3
 bus info: pci@:00:14.3
 logical name: wlo1
 version: 30
 serial: 54:8d:5a:ab:41:77
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
 resources: irq:16 memory:a141c000-a141
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: enp2s0
 version: 15
 serial: 98:fa:9b:c9:eb:c6
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 
link=yes multicast=yes port=MII speed=1Gbit/s
 resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff 
memory:a130-a1303fff
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:04:00.0
 logical name: enp4s0
 version: 1b
 serial: 98:fa:9b:c9:eb:c7
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII
 resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff 
memory:a120-a1203fff

  
  --- After update

  root@lenovo-test-3:~# uname -r
  5.4.0-80-generic

  root@lenovo-test-3:~# lshw -c network
*-network DISABLED
 description: Wireless interface
 product: Cannon Point-LP CNVi [Wireless-AC]
 vendor: Intel Corporation
 physical id: 14.3
 bus info: pci@:00:14.3
 logical name: wlo1
 version: 30
 serial: 54:8d:5a:ab:41:77
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
 resources: irq:16 memory:a141c000-a141
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: enp2s0
 version: 15
 serial: 98:fa:9b:c9:eb:c6
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
duplex=full firmware=rtl8168h-2_0.0.2 02/26/15

[Kernel-packages] [Bug 1938699] [NEW] cpu-checker: riscv64 build missing

2021-08-02 Thread Heinrich Schuchardt

Public bug reported:

cpu-checker builds fine for RISC-V once architecture riscv64 is added to 
debian/control.
A patch for kvm-ok is needed to add a /dev/kvm check for the RISC-V 
architecture.

** Affects: cpu-checker (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: riscv64

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

Title:
  cpu-checker: riscv64 build missing

Status in cpu-checker package in Ubuntu:
  New

Bug description:
  cpu-checker builds fine for RISC-V once architecture riscv64 is added to 
debian/control.
  A patch for kvm-ok is needed to add a /dev/kvm check for the RISC-V 
architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpu-checker/+bug/1938699/+subscriptions


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

[Kernel-packages] [Bug 1938697] [NEW] Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic

You have been subscribed to a public bug:

I have found an issue after upgrading my Kernel from 5.4.0-74-generic to
5.4.0-80-generic on Ubuntu 20.04.

It appears that support for the second ethernet port on my Lenovo m90n-1
has been dropped or isn't working as expected.  After upgrading to
5.4.0-80-generic my second ethernet port

Both ethernet ports use the r8169 driver.  If I switch back to the
previous kernel 5.4.0-74-generic.  The second ethernet port is usable
again.

I did attempt under 5.4.0-80-generic to see if I could get an error
message.  When the driver attempts to discover the second ethernet port
the following error is thrown.

   "unknown chip XID fcf"

Support output below:


--- Before update.

Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64)

root@lenovo-test-3:~# lshw -c network
  *-network DISABLED
   description: Wireless interface
   product: Cannon Point-LP CNVi [Wireless-AC]
   vendor: Intel Corporation
   physical id: 14.3
   bus info: pci@:00:14.3
   logical name: wlo1
   version: 30
   serial: 54:8d:5a:ab:41:77
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
   resources: irq:16 memory:a141c000-a141
  *-network
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:02:00.0
   logical name: enp2s0
   version: 15
   serial: 98:fa:9b:c9:eb:c6
   size: 1Gbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full 
firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes 
multicast=yes port=MII speed=1Gbit/s
   resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff 
memory:a130-a1303fff
  *-network
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:04:00.0
   logical name: enp4s0
   version: 1b
   serial: 98:fa:9b:c9:eb:c7
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII
   resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff 
memory:a120-a1203fff


--- After update

root@lenovo-test-3:~# uname -r
5.4.0-80-generic

root@lenovo-test-3:~# lshw -c network
  *-network DISABLED
   description: Wireless interface
   product: Cannon Point-LP CNVi [Wireless-AC]
   vendor: Intel Corporation
   physical id: 14.3
   bus info: pci@:00:14.3
   logical name: wlo1
   version: 30
   serial: 54:8d:5a:ab:41:77
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
   resources: irq:16 memory:a141c000-a141
  *-network
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:02:00.0
   logical name: enp2s0
   version: 15
   serial: 98:fa:9b:c9:eb:c6
   size: 1Gbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full 
firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes 
multicast=yes port=MII speed=1Gbit/s
   resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff 
memory:a130-a1303fff

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


** Tags: focal
-- 
Kernel driver support issue between  5.4.0-74-generic and  5.4.0-80-generic
https://bugs.launchpad.net/bugs/1938697
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
Mailing list:

[Kernel-packages] [Bug 1936255] Re: New upstream release 2021.07.14

Hey! I have no power over ESM packages - I assume that's something the
security team needs to handle. Well, potentially I *could* get that into
xenial still, but in theory xenial should be closed now.

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

Title:
  New upstream release 2021.07.14

Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in wireless-regdb source package in Trusty:
  In Progress
Status in wireless-regdb source package in Xenial:
  In Progress
Status in wireless-regdb source package in Bionic:
  Fix Committed
Status in wireless-regdb source package in Focal:
  Fix Committed
Status in wireless-regdb source package in Groovy:
  Won't Fix
Status in wireless-regdb source package in Hirsute:
  Fix Committed
Status in wireless-regdb source package in Impish:
  Fix Released

Bug description:
  [Impact]

  New upstream release. This is a database of wireless regulations, and
  should updated in all releases to ensure users have the most up-to-
  date regulatory information.

  [Test Case]

  Following reboot after installing the new database, it should be
  possible to query and change the regulatory domain using 'iw reg get'
  and 'iw reg set'.

  [Where problems could occur]

  If crda or the kernel is unable to use the new database, users may be
  stuck using the default "world" regulatory domain which is quite
  restrictive, therefore they may be unable to use wireless channels
  that they were able to use previously. Regulatory rules may have also
  changed for the user's region, which could also make some channels
  unusable, but this would not be a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+subscriptions


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

[Kernel-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

This bug was fixed in the package gnome-settings-daemon -
3.36.1-0ubuntu1.1

---
gnome-settings-daemon (3.36.1-0ubuntu1.1) focal; urgency=medium

  * d/p/git-rfkill-set-the-g_io_channel-to-unbuffered-mode.patch:
- Set the g_io_channel to unbuffered mode to fix airplane mode with
  newer kernel versions (lp: #1926062)
  * d/p/git-media-keys-Addd-one-second-delay-between-each-rfkill-.patch
- Add one second dely between each rfkill event (lp: #1936303)

 -- Andy Chi   Thu, 08 Jul 2021 17:35:19 +0800

** Changed in: gnome-settings-daemon (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Fix Released
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in gnome-settings-daemon source package in Focal:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in gnome-settings-daemon source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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


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

[Kernel-packages] [Bug 1930754] Re: e1000e extremly slow

2021-08-02 Thread Yuan-Chen Cheng

Hi Sebastian

I test "sudo ethtool -C  rx-usecs 6000", it does work to a
certain degree, but it will decrease the maximum LAN speed per test
using iperf3. Not sure if this is the work around you are using for now?

For your test in #17, is this the command you try:

echo on | sudo tee /sys/bus/pci/devices/\:00\:16.0/power/control

If yes, and it does not work around this issue, can you run beload
command

sudo lspci -nnvv > pci-nnvv

and upload pci-nnvv?

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

Title:
  e1000e extremly slow

Status in OEM Priority Project:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  Confirmed

Bug description:
  We have dell latitude 5420 & 5520 laptops with onboard intel ethernet 
controller.
  Problem is that the ethernet port is extremely slow. about 100kbyte/s 
download throughput while on a gigabit connection. Upload seems to work just 
fine.

  Also when I pxe boot the system it's also painfully slow.

  But here comes the funny part. When I attach a usb memory stick the
  throughput of the networkcontroller is as expected.

  I've used latest ubuntu 20.04.2 kernel 5.8.0-55
  I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem

  Turns out this problem is not showing up when I manually install the
  5.8.18 kernel.

  Also when I create my own iso with the help of Cubic and install the
  5.8.18 kernel in it the pxe boot is working as expected with high
  throughput

  system: Dell latitude 5420 + 5520
  nic: Ethernet Connection (13) I219-LM
  ubuntu 20.04.2
  module: e1000e

  Please assist. Thank you

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


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

[Kernel-packages] [Bug 1840488] Re: Disable Bluetooth in cloud kernels

2021-08-02 Thread 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-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag 'verification-needed-hirsute' to 'verification-failed-
hirsute'.

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

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

Title:
  Disable Bluetooth in cloud kernels

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Triaged
Status in linux-gke-4.15 package in Ubuntu:
  Invalid
Status in linux-gke-5.0 package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Triaged
Status in linux-aws source package in Xenial:
  Invalid
Status in linux-gcp source package in Xenial:
  Triaged
Status in linux-gke-4.15 source package in Xenial:
  Invalid
Status in linux-gke-5.0 source package in Xenial:
  Invalid
Status in linux-oracle source package in Xenial:
  Triaged
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux-gcp source package in Bionic:
  Triaged
Status in linux-gke-4.15 source package in Bionic:
  Triaged
Status in linux-gke-5.0 source package in Bionic:
  Triaged
Status in linux-oracle source package in Bionic:
  Triaged
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-gcp source package in Disco:
  Won't Fix
Status in linux-gke-4.15 source package in Disco:
  Invalid
Status in linux-gke-5.0 source package in Disco:
  Invalid
Status in linux-oracle source package in Disco:
  Won't Fix
Status in linux-aws source package in Eoan:
  Won't Fix
Status in linux-gcp source package in Eoan:
  Won't Fix
Status in linux-gke-5.0 source package in Eoan:
  Invalid
Status in linux-oracle source package in Eoan:
  Won't Fix
Status in linux-aws source package in Focal:
  New
Status in linux-gcp source package in Focal:
  Fix Committed
Status in linux-gke-5.0 source package in Focal:
  New
Status in linux-oracle source package in Focal:
  New
Status in linux-aws source package in Groovy:
  Won't Fix
Status in linux-gcp source package in Groovy:
  Won't Fix
Status in linux-gke-4.15 source package in Groovy:
  Won't Fix
Status in linux-gke-5.0 source package in Groovy:
  Won't Fix
Status in linux-oracle source package in Groovy:
  Won't Fix
Status in linux-aws source package in Hirsute:
  New
Status in linux-gcp source package in Hirsute:
  New
Status in linux-gke-4.15 source package in Hirsute:
  New
Status in linux-gke-5.0 source package in Hirsute:
  New
Status in linux-oracle source package in Hirsute:
  New

Bug description:
  [Impact]

  Some cloud-focused kernels have CONFIG_BT enabled but cloud instances
  shouldn't need bluetooth support. Disabling the bluetooth subsystem
  reduces the amount of security-sensitive code we have to worry about
  in the cloud kernels and also has the nice side effect of minimizing
  build times and kernel sizes.

  The cloud kernels known to have bluetooth enabled include:

  * [B/D/E] linux-aws (arm64 only)
  * [X/B/D/E] linux-gcp
  * [B] linux-gke-4.15
  * [B] linux-gke-5.0
  * [X/B/D/E] linux-oracle

  [Test Case]

  1. Install patched kernel and reboot into it
  2. Ensure that the following command does NOT display any output:
     $ grep CONFIG_BT=[my] /boot/config-$(uname -r)

  [Regression Potential]

  There could be an unexpected dependence on bluetooth within one of the
  clouds but I think it is highly unlikely.

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


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

[Kernel-packages] [Bug 1926062] Update Released

The verification of the Stable Release Update for gnome-settings-daemon
has completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Fix Released
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in gnome-settings-daemon source package in Focal:
  Fix Committed
Status in bluez source package in Hirsute:
  Fix Released
Status in gnome-settings-daemon source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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


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

[Kernel-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

This bug was fixed in the package gnome-settings-daemon -
3.38.1-3ubuntu3.1

---
gnome-settings-daemon (3.38.1-3ubuntu3.1) hirsute; urgency=medium

  * d/p/git-rfkill-set-the-g_io_channel-to-unbuffered-mode.patch:
- Set the g_io_channel to unbuffered mode to fix airplane mode with
  newer kernel versions (lp: #1926062)
  * d/p/git-media-keys-Addd-one-second-delay-between-each-rfkill-.patch
- Add one second dely between each rfkill event (lp: #1936303)

 -- Andy Chi   Thu, 15 Jul 2021 09:57:58 +0200

** Changed in: gnome-settings-daemon (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Fix Released
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in gnome-settings-daemon source package in Focal:
  Fix Committed
Status in bluez source package in Hirsute:
  Fix Released
Status in gnome-settings-daemon source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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


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

[Kernel-packages] [Bug 1936577] Update Released

The verification of the Stable Release Update for libnvidia-nscq-470 has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Introduce the 470-server series

Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Hirsute:
  Triaged
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Committed

Bug description:
  Introduce the 470 NVIDIA ERD (-server) series in Bionic, Focal,
  Hirsute.

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 470.57.02 (470-server) ==

* Initial release (LP: #1936577).

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


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

[Kernel-packages] [Bug 1934873] Re: ubuntu_aufs_smoke_test fails on Focal cloud v5.11

2021-08-02 Thread 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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

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

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

Title:
  ubuntu_aufs_smoke_test fails on Focal cloud v5.11

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-aws-5.11 package in Ubuntu:
  New
Status in linux-azure-5.11 package in Ubuntu:
  New
Status in linux-gcp-5.11 package in Ubuntu:
  New
Status in linux-oracle-5.11 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-aws-5.11 source package in Focal:
  New
Status in linux-azure-5.11 source package in Focal:
  New
Status in linux-gcp-5.11 source package in Focal:
  New
Status in linux-oracle-5.11 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * Several Focal v5.11 edge kernels are missing AUFS.

   * This is a regression against previous Focal kernels (v5.4 and v5.8)
  because it is expected to support same set of features on v5.11.

  [Test Plan]

   * Run ubuntu_aufs_smoke_test autotest.

  [Where problems could occur]

   * Mounting AUFS file system could succeed introducing a variety of
  failures due to bugs in AUFS.

  lp:1925407 disabled the test for Hirsute but now we have v5.11 edge
  kernels on Focal and it fails the same.

  It's not a regression but test should be hinted.

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


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

[Kernel-packages] [Bug 1928686] Re: Some cloud kernels have Android related config options disabled

2021-08-02 Thread 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-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

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

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

Title:
  Some cloud kernels have Android related config options disabled

Status in linux-gcp package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Bionic:
  New
Status in linux-oracle source package in Bionic:
  New
Status in linux-gcp source package in Focal:
  New
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-gcp source package in Groovy:
  New
Status in linux-oracle source package in Groovy:
  Fix Released
Status in linux-gcp source package in Hirsute:
  New
Status in linux-oracle source package in Hirsute:
  Fix Released

Bug description:
  For Anbox Cloud we require certain CONFIG_ANDROID_* options to be
  enabled in the kernel. We do this already for most of our cloud
  kernels (GCE, AWS, Azure) and the generic kernel and should do so for
  the oracle (and possible others too). We have customers looking at
  running Anbox Cloud on OCI instances and having the ashmem and binder
  kernel modules available is a precondition for this to work.

  
  The following options are what we need

  CONFIG_ANDROID=y
  CONFIG_ANDROID_BINDER_IPC=m
  CONFIG_ANDROID_BINDERFS=m
  CONFIG_ANDROID_BINDER_DEVICES=""
  # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set
  CONFIG_ASHMEM=m

  These should be the same across all our kernels where we're going to
  support Anbox Cloud.

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


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

[Kernel-packages] [Bug 1938693] Re: Flameshot doesn't work anymore after linux upgrade to 21.04

2021-08-02 Thread Kaio Pessoni

The bug was fixed after I logged out and change the setting on login
screen (lower right of screen) to Ubuntu on Xorg.

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

Title:
  Flameshot doesn't work anymore after linux upgrade to 21.04

Status in linux package in Ubuntu:
  New

Bug description:
  After the linux upgrade to 21.04, the package flameshot is not working
  anymore. I click to take a screenshot but nothing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kaio   1676 F pulseaudio
   /dev/snd/controlC1:  kaio   1676 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Mon Aug  2 08:59:19 2021
  InstallationDate: Installed on 2020-12-13 (231 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Acer Aspire VX5-591G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=e4a2a124-2896-4512-af5d-204bf0f6096b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-07-31 (1 days ago)
  dmi.bios.date: 07/07/2017
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:br1.6:efr1.3:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

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


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

[Kernel-packages] [Bug 1938693] [NEW] Flameshot doesn't work anymore after linux upgrade to 21.04

2021-08-02 Thread Kaio Pessoni

Public bug reported:

After the linux upgrade to 21.04, the package flameshot is not working
anymore. I click to take a screenshot but nothing happens.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-25-generic 5.11.0-25.27
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kaio   1676 F pulseaudio
 /dev/snd/controlC1:  kaio   1676 F pulseaudio
CasperMD5CheckResult: unknown
Date: Mon Aug  2 08:59:19 2021
InstallationDate: Installed on 2020-12-13 (231 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: Acer Aspire VX5-591G
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=e4a2a124-2896-4512-af5d-204bf0f6096b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-25-generic N/A
 linux-backports-modules-5.11.0-25-generic  N/A
 linux-firmware 1.197.2
SourcePackage: linux
UpgradeStatus: Upgraded to hirsute on 2021-07-31 (1 days ago)
dmi.bios.date: 07/07/2017
dmi.bios.release: 1.6
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.06
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Wish_KLS
dmi.board.vendor: KBL
dmi.board.version: V1.06
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.06
dmi.ec.firmware.release: 1.3
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:br1.6:efr1.3:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
dmi.product.family: Aspire VX 15
dmi.product.name: Aspire VX5-591G
dmi.product.sku: 
dmi.product.version: V1.06
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug hirsute third-party-packages wayland-session

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

Title:
  Flameshot doesn't work anymore after linux upgrade to 21.04

Status in linux package in Ubuntu:
  New

Bug description:
  After the linux upgrade to 21.04, the package flameshot is not working
  anymore. I click to take a screenshot but nothing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kaio   1676 F pulseaudio
   /dev/snd/controlC1:  kaio   1676 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Mon Aug  2 08:59:19 2021
  InstallationDate: Installed on 2020-12-13 (231 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Acer Aspire VX5-591G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=e4a2a124-2896-4512-af5d-204bf0f6096b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-07-31 (1 days ago)
  dmi.bios.date: 07/07/2017
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:br1.6:efr1.3:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

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


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

[Kernel-packages] [Bug 1688716] Re: screen turns black after reopening lid (laptop)

2021-08-02 Thread Vilhelm Prytz

I no longer use this computer and I no longer use Ubuntu MATE, sorry.

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

Title:
  screen turns black after reopening lid (laptop)

Status in Ubuntu MATE:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I close the laptop lid, the laptop hibernates/(suspends?). When I
  reopen the lid, the fans starts again but the screen is completely
  black.

  I'm running Ubuntu MATE 16.04.2 LTS (installed yesterday) on a ASUS TP301U.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vilhelm1852 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=78779645-e369-460f-92fa-fdef01ab1941
  InstallationDate: Installed on 2017-05-12 (112 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b568 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. TP301UJ
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=200c5644-817b-4c85-a997-011c9c0cfe6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP301UJ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP301UJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP301UJ.300:bd06/01/2016:svnASUSTeKCOMPUTERINC.:pnTP301UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP301UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: TP301UJ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vilhelm1852 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=78779645-e369-460f-92fa-fdef01ab1941
  InstallationDate: Installed on 2017-05-12 (112 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b568 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. TP301UJ
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=200c5644-817b-4c85-a997-011c9c0cfe6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP301UJ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP301UJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP301UJ.300:bd06/01/2016:svnASUSTeKCOMPUTERINC.:pnTP301UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP301UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: TP301UJ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1688716] Re: screen turns black after reopening lid (laptop)

2021-08-02 Thread Norbert

Can you reproduce this bug with newer version of Ubuntu MATE?

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

Title:
  screen turns black after reopening lid (laptop)

Status in Ubuntu MATE:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I close the laptop lid, the laptop hibernates/(suspends?). When I
  reopen the lid, the fans starts again but the screen is completely
  black.

  I'm running Ubuntu MATE 16.04.2 LTS (installed yesterday) on a ASUS TP301U.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vilhelm1852 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=78779645-e369-460f-92fa-fdef01ab1941
  InstallationDate: Installed on 2017-05-12 (112 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b568 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. TP301UJ
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=200c5644-817b-4c85-a997-011c9c0cfe6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP301UJ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP301UJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP301UJ.300:bd06/01/2016:svnASUSTeKCOMPUTERINC.:pnTP301UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP301UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: TP301UJ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vilhelm1852 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=78779645-e369-460f-92fa-fdef01ab1941
  InstallationDate: Installed on 2017-05-12 (112 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b568 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. TP301UJ
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=200c5644-817b-4c85-a997-011c9c0cfe6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP301UJ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP301UJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP301UJ.300:bd06/01/2016:svnASUSTeKCOMPUTERINC.:pnTP301UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP301UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: TP301UJ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1938689] [NEW] [SRU][H/OEM-5.10/OEM-5.13/U] Fix system hang after unplug tbt dock

2021-08-02 Thread AaronMa

Public bug reported:

SRU justification:

[Impact]
System hang after unplug thunderbolt dock with Intel igc lan.

[Fix]
igc driver continue reading and writing MMIO address after PCI device is 
unplugged.
This cause system page fault, and system hang.
Add safe check and prevent reading and writing the MMIO.

The patch is in maintainer's tree, but not merged to Linus's tree.
Due to the schedule, send SRU as SAUCE patch.

[Test]
Verified on hardware, after unplug the thunderbolt cable,
system work fine.

[Where problems could occur]
It may break the igc driver.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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

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

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

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

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

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

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


** Tags: oem-priority originate-from-1931982 originate-from-1932115 sutton

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

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

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

** Also affects: linux-oem-5.10 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.13 (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-5.10 (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.13 (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-5.10 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.13 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu Focal)

** No longer affects: linux-oem-5.10 (Ubuntu Hirsute)

** No longer affects: linux-oem-5.10 (Ubuntu Impish)

** No longer affects: linux-oem-5.13 (Ubuntu Hirsute)

** No longer affects: linux-oem-5.13 (Ubuntu Impish)

** Tags added: oem-priority originate-from-1932115 sutton

** Tags added: originate-from-1931982

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

Title:
  [SRU][H/OEM-5.10/OEM-5.13/U] Fix system hang after unplug tbt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.10 source package in Focal:
  New
Status in linux-oem-5.13 source package in Focal:
  New
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  New

Bug description:
  SRU justification:

  [Impact]
  System hang after unplug thunderbolt dock with Intel igc lan.

  [Fix]
  igc driver continue reading and writing MMIO address after PCI device is 
unplugged.
  This cause system page fault, and system hang.
  Add safe check and prevent reading and writing the MMIO.

  The patch is in maintainer's tree, but not merged to Linus's tree.
  Due to the schedule, send SRU as SAUCE patch.

  [Test]
  Verified on hardware, after unplug the thunderbolt cable,
  system work fine.

  [Where problems could occur]
  It may break the igc driver.

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


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

[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)

On Hirsute:
04:34:53 DEBUG| [stdout] # selftests: net: devlink_port_split.py
04:34:53 DEBUG| [stdout] # no devlink device was found, test skipped
04:34:53 DEBUG| [stdout] ok 44 selftests: net: devlink_port_split.py # SKIP

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

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

Title:
  devlink_port_split in net from ubuntu_kernel_selftests linux ADT test
  failure with linux/5.11.0-18.19 ( list index out of range)

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  If there is no devlink device available, the devlink_port_split.py in 
kselftest/net will fail with:
   # selftests: net: devlink_port_split.py
   # Traceback (most recent call last):
   #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
   # main()
   #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 242, in main
   # dev = list(devs.keys())[0]
   # IndexError: list index out of range 
   not ok 43 selftests: net: devlink_port_split.py # exit=1

  [Fix]
  * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no 
devlink device

  This test only exist in our source tree since Hirsute, this patch can
  be cherry-picked into all affected kernels.

  [Test Plan]
  Run this test manually from the patched source tree, the test will be skipped 
when there is no devlink device:
# selftests: net: devlink_port_split.py
# no devlink device was found, test skipped
ok 7 selftests: net: devlink_port_split.py # SKIP

  [Where problems could occur]
  Change limited to testing tool, if this change is incorrect it might cause 
false-negative result in our test report.

  
  [Original Bug Report]
  This is a scripted bug report about ADT failures while running linux tests 
for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of 
the tested source or the kernel has yet to be determined.

  Not a regression. Found to occur previously on hirsute/linux
  5.11.0-14.15

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz

  17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:39:37 DEBUG| [stdout] # Traceback (most recent call last):
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
  17:39:37 DEBUG| [stdout] # main()
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 242, in main
  17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0]
  17:39:37 DEBUG| [stdout] # IndexError: list index out of range
  17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # 
exit=1

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


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

[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)

On F-oem-5.10:
07/29 03:08:04 DEBUG| utils:0153| [stdout] # selftests: net: 
devlink_port_split.py
07/29 03:08:04 DEBUG| utils:0153| [stdout] # no devlink device was found, 
test skipped
07/29 03:08:04 DEBUG| utils:0153| [stdout] ok 44 selftests: net: 
devlink_port_split.py # SKIP

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

Title:
  devlink_port_split in net from ubuntu_kernel_selftests linux ADT test
  failure with linux/5.11.0-18.19 ( list index out of range)

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  If there is no devlink device available, the devlink_port_split.py in 
kselftest/net will fail with:
   # selftests: net: devlink_port_split.py
   # Traceback (most recent call last):
   #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
   # main()
   #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 242, in main
   # dev = list(devs.keys())[0]
   # IndexError: list index out of range 
   not ok 43 selftests: net: devlink_port_split.py # exit=1

  [Fix]
  * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no 
devlink device

  This test only exist in our source tree since Hirsute, this patch can
  be cherry-picked into all affected kernels.

  [Test Plan]
  Run this test manually from the patched source tree, the test will be skipped 
when there is no devlink device:
# selftests: net: devlink_port_split.py
# no devlink device was found, test skipped
ok 7 selftests: net: devlink_port_split.py # SKIP

  [Where problems could occur]
  Change limited to testing tool, if this change is incorrect it might cause 
false-negative result in our test report.

  
  [Original Bug Report]
  This is a scripted bug report about ADT failures while running linux tests 
for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of 
the tested source or the kernel has yet to be determined.

  Not a regression. Found to occur previously on hirsute/linux
  5.11.0-14.15

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz

  17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:39:37 DEBUG| [stdout] # Traceback (most recent call last):
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
  17:39:37 DEBUG| [stdout] # main()
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 242, in main
  17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0]
  17:39:37 DEBUG| [stdout] # IndexError: list index out of range
  17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # 
exit=1

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


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

[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)

And F-oem-5.13
07:13:14 DEBUG| [stdout] # selftests: net: devlink_port_split.py
07:13:14 DEBUG| [stdout] # no devlink device was found, test skipped
07:13:14 DEBUG| [stdout] ok 44 selftests: net: devlink_port_split.py # SKIP

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

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

Title:
  devlink_port_split in net from ubuntu_kernel_selftests linux ADT test
  failure with linux/5.11.0-18.19 ( list index out of range)

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  If there is no devlink device available, the devlink_port_split.py in 
kselftest/net will fail with:
   # selftests: net: devlink_port_split.py
   # Traceback (most recent call last):
   #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
   # main()
   #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 242, in main
   # dev = list(devs.keys())[0]
   # IndexError: list index out of range 
   not ok 43 selftests: net: devlink_port_split.py # exit=1

  [Fix]
  * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no 
devlink device

  This test only exist in our source tree since Hirsute, this patch can
  be cherry-picked into all affected kernels.

  [Test Plan]
  Run this test manually from the patched source tree, the test will be skipped 
when there is no devlink device:
# selftests: net: devlink_port_split.py
# no devlink device was found, test skipped
ok 7 selftests: net: devlink_port_split.py # SKIP

  [Where problems could occur]
  Change limited to testing tool, if this change is incorrect it might cause 
false-negative result in our test report.

  
  [Original Bug Report]
  This is a scripted bug report about ADT failures while running linux tests 
for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of 
the tested source or the kernel has yet to be determined.

  Not a regression. Found to occur previously on hirsute/linux
  5.11.0-14.15

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz

  17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:39:37 DEBUG| [stdout] # Traceback (most recent call last):
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
  17:39:37 DEBUG| [stdout] # main()
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 242, in main
  17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0]
  17:39:37 DEBUG| [stdout] # IndexError: list index out of range
  17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # 
exit=1

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


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

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

2021-08-02 Thread Alberto Milone

You might want to install the linux-modules-nvidia-390-5.11.0-26-generic
package from proposed.

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

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

Status in linux package in Ubuntu:
  New

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

  This is what I get from dmesg:

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

  Here is some system information:

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

[Kernel-packages] [Bug 1929892] Re: [TGL] enable USB-dw3

2021-08-02 Thread Hsuan-Yu Lin

This patch 73203bde3a95a48f27b2454dc6b955280c641afe needs another 2
dependency patches (Please see bug 1929902 comment #3)

I will re-submit the new patch set.

---
Reference:
e492ce9bcaa1 usb: dwc3: pci: Register a software node for the dwc3 platform 
device
e68d0119e328 software node: Introduce device_add_software_node()

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

Title:
  [TGL] enable USB-dw3

Status in intel:
  New
Status in linux package in Ubuntu:
  New
Status in linux-intel package in Ubuntu:
  In Progress

Bug description:
  Description
  Enable USB-dw3 for Tiger Lake

  Hardware: Tiger Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

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


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

[Kernel-packages] [Bug 1929892] Re: [TGL] enable USB-dw3

2021-08-02 Thread Hsuan-Yu Lin

Patches are ready and under review.

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

Title:
  [TGL] enable USB-dw3

Status in intel:
  New
Status in linux package in Ubuntu:
  New
Status in linux-intel package in Ubuntu:
  In Progress

Bug description:
  Description
  Enable USB-dw3 for Tiger Lake

  Hardware: Tiger Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

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


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

[Kernel-packages] [Bug 1909944] Re: Dell XPS 13 9333 Synaptics touch screen does not work after boot but will work after resume from sleep?

Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

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

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

Title:
  Dell XPS 13 9333 Synaptics touch screen does not work after boot but
  will work after resume from sleep?

Status in libinput package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I freshly installed Ubuntu 20.10 and noticed that the touch screen
  does not work. Tried xinput --list and then xinput disable/enable
  [correct-id] but with no avail.

  However, if I close the laptop lid and open it, after the system
  resumes from sleep, the touch screen starts working.

  BUT, another anomaly happens, this could not necessarily be after the
  1st resume from sleep, it could be the 2nd+ ---> the "Windows" key on
  the keyboard stops working? So, I can't start apps by type and search?
  And when this happens, the whole screen sometimes freezes and becomes
  unresponsive ex. moving around the mouse (synaptic touch pad and not
  touchscreen), no matter where I click, no reaction... I tried
  CTRL+ALT+F1 then switch back and somehow it started working again? It
  also happened, that the synaptic touch pad was not moving the mouse
  cursor on the screen (and the mouse cursor just disappeared)? Luckily,
  the keyboard was still reacting for the CTRL+ALT+T and the terminal
  window showed up, from where I used sudo modprobe -r psmouse and then
  sudo modprobe psmouse and also xinput disable/enable [touch-pad-id]
  and it got back to work.

  Many things happen in this one bug it seems?

  NOTE: when running 20.10 from USB (Live CD), then the touchscreen
  works perfectly! Only after install do these anomalies happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  3 22:55:01 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a]
  InstallationDate: Installed on 2021-01-01 (2 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Dell Inc. XPS13 9333
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=fe6e5482-378f-4c13-9039-8b11eba4af45 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/31/2015:br0.1:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to :

[Kernel-packages] [Bug 1938682] [NEW] Flushing is not possible

2021-08-02 Thread Jan Grossmann

Public bug reported:

In the 5.5.0-1ubuntu1 version of Ubuntu 20.04.2 LTS it is not possible to flush 
any ip addresses.
Test command (executed as root):
ip a flush dev lo
EOF on netlink
Flush terminated

Additional version info.
ip -V
ip utility, iproute2-ss200127

>From looking at a strace output it seems to me like the "dev" parameter
is not passed to the correct function.

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

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

Title:
  Flushing is not possible

Status in iproute2 package in Ubuntu:
  New

Bug description:
  In the 5.5.0-1ubuntu1 version of Ubuntu 20.04.2 LTS it is not possible to 
flush any ip addresses.
  Test command (executed as root):
  ip a flush dev lo
  EOF on netlink
  Flush terminated

  Additional version info.
  ip -V
  ip utility, iproute2-ss200127

  From looking at a strace output it seems to me like the "dev"
  parameter is not passed to the correct function.

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


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

[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout

Found on node riccioli with 4.15.0-153.160

** Tags added: sru-20210719

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

Title:
  kvm_unit_tests: emulator test fails on 4.15 kernel, timeout

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  Found this on B/KVM, current cycle (sru-20210531):

  18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
  18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
  18:27:11 DEBUG| [stderr] emulation failure
  18:27:11 DEBUG| [stderr] RAX=000a RBX=e000 
RCX=03fd RDX=03f8
  18:27:11 DEBUG| [stderr] RSI=00419991 RDI=00419991 
RBP=0051b440 RSP=0051b420
  18:27:11 DEBUG| [stderr] R8 =000a R9 =03f8 
R10=000d R11=
  18:27:11 DEBUG| [stderr] R12=e000 R13= 
R14=d000 R15=
  18:27:11 DEBUG| [stderr] RIP=00400a0c RFL=00010006 [-P-] CPL=0 
II=0 A20=1 SMM=0 HLT=0
  18:27:11 DEBUG| [stderr] ES =0010   00c09300 DPL=0 DS 
  [-WA]
  18:27:11 DEBUG| [stderr] CS =0008   00a09b00 DPL=0 
CS64 [-RA]
  18:27:11 DEBUG| [stderr] SS =0010   00c09300 DPL=0 DS 
  [-WA]
  18:27:11 DEBUG| [stderr] DS =0010   00c09300 DPL=0 DS 
  [-WA]
  18:27:11 DEBUG| [stderr] FS =0010   00c09300 DPL=0 DS 
  [-WA]
  18:27:11 DEBUG| [stderr] GS =0010 0051a4d0  00c09300 DPL=0 DS 
  [-WA]
  18:27:11 DEBUG| [stderr] LDT=   8200 DPL=0 LDT
  18:27:11 DEBUG| [stderr] TR =0080 0041207a  8b00 DPL=0 
TSS64-busy
  18:27:11 DEBUG| [stderr] GDT= 0041100a 106f
  18:27:11 DEBUG| [stderr] IDT= 0041 0fff
  18:27:11 DEBUG| [stderr] CR0=80010011 CR2= 
CR3=01007000 CR4=0220
  18:27:11 DEBUG| [stderr] DR0= DR1= 
DR2= DR3= 
  18:27:11 DEBUG| [stderr] DR6=0ff0 DR7=0400
  18:27:11 DEBUG| [stderr] EFER=0500
  18:27:11 DEBUG| [stderr] Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 
0f 6f 45 e0 <0f> 11 03 48 89 de 48 8d 7d e0 e8 f8 f9 ff ff 0f b6 f8 be a1 8f 41 
00 b8 00 00 00 00 e8 05
  18:28:40 DEBUG| [stderr] qemu-system-x86_64: terminating on signal 15 from 
pid 13634 (timeout)
  18:28:40 DEBUG| [stdout] FAIL emulator (timeout; duration=90s)
  [...]
  TestError: Test failed for emulator
  18:28:40 ERROR| child process failed
  18:28:40 DEBUG| Traceback (most recent call last):
  18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/parallel.py", line 25, 
in fork_start
  18:28:40 DEBUG| l()
  18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/job.py", line 505, in 

  18:28:40 DEBUG| l = lambda: test.runtest(self, url, tag, args, dargs)
  18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/test.py", line 125, in 
runtest
  18:28:40 DEBUG| job.sysinfo.log_after_each_iteration)
  18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/shared/test.py", line 
913, in runtest
  18:28:40 DEBUG| mytest._exec(args, dargs)
  18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/shared/test.py", line 
411, in _exec
  18:28:40 DEBUG| _call_test_function(self.execute, *p_args, **p_dargs)
  18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/shared/test.py", line 
823, in _call_test_function
  18:28:40 DEBUG| return func(*args, **dargs)
  18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/shared/test.py", line 
291, in execute
  18:28:40 DEBUG| postprocess_profiled_run, args, dargs)
  18:28:40 DEBUG|   File "/home/ubuntu/autotest/client/shared/test.py", line 
212, in _call_run_once
  18:28:40 DEBUG| self.run_once(*args, **dargs)
  18:28:40 DEBUG|   File 
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
 line 82, in run_once
  18:28:40 DEBUG| raise error.TestError("Test failed for 
{}".format(test_name))
  18:28:40 DEBUG| TestError: Test failed for emulator
  18:28:41 INFO | ERROR   ubuntu_kvm_unit_tests.emulator  
ubuntu_kvm_unit_tests.emulator  timestamp=1624040921localtime=Jun 18 
18:28:41   Test failed for emulator
  18:28:41 INFO | END ERROR   ubuntu_kvm_unit_tests.emulator  
ubuntu_kvm_unit_tests.emulator  timestamp=1624040921localtime=Jun 18 
18:28:41

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


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

[Kernel-packages] [Bug 1938053] Re: [MSI Modern 14 B10MW] HDMI Problem

Thanks for the bug report. Please:

1. Tell us roughly how long ago the problem started.

2. Attach a copy of the three most recent files named
/var/log/apt/history.log*


** Summary changed:

- HDMI Problem
+ [MSI Modern 14 B10MW] HDMI Problem

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

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

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

Title:
  [MSI Modern 14 B10MW] HDMI Problem

Status in linux-hwe-5.8 package in Ubuntu:
  Incomplete

Bug description:
  Cannot connect second monitor with hdmi after update.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 26 17:49:36 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 
[1462:12c1]
  InstallationDate: Installed on 2021-06-05 (50 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Micro-Star International Co., Ltd. Modern 14 B10MW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic 
root=UUID=375930f6-29d7-4278-861a-7bf26f514a10 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E14D1IMS.10B
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-14D1
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE14D1IMS.10B:bd12/22/2020:br1.11:svnMicro-StarInternationalCo.,Ltd.:pnModern14B10MW:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14D1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: Modern
  dmi.product.name: Modern 14 B10MW
  dmi.product.sku: 14D1.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1938669] Re: Epiphan framegrabbers stream only once then need unbinding/rebinding to uvcvideo to work again

2021-08-02 Thread 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/1938669

Title:
  Epiphan framegrabbers stream only once then need unbinding/rebinding
  to uvcvideo to work again

Status in linux package in Ubuntu:
  New

Bug description:
  Video capture devices made by Epiphan Systems (vendor id 0x2b77) work
  once, but as soon as the video device is closed (or even if it is kept
  open but the application issues a VIDIOC_STREAMOFF ioctl) it won't
  work again - subsequent calls to VIDOC_DQBUF simply hang - until the
  device is unbound from and rebound to the uvcvideo module. (modprobe
  -r uvcvideo; modprobe uvcvideo also works).

  For example:

ffplay /dev/video0  -- works fine and shows the captured stream.

ffplay /dev/video0  -- when run a second time: hangs and does not
  capture anything

modprobe -r uvcvideo ; modprobe uvcvideo; ffplay /dev/video  --
  works fine again.

  Experimenting with the device and the uvcvideo module source code
  reveals that problem is the device is expecting SET_INTERFACE(0) to be
  sent to return it to a state where it can accept control requests and
  start streaming again.

  The code in uvc_video.c has several comments stating that some bulk-
  transfer devices require a SET_INTERFACE(0) call to be made before any
  control commands, even though 0 is already the default and only valid
  interface value. And, the function uvc_video_init makes such a call
  (which is why the device starts working again after rebinding to the
  uvcvideo module). But no such call is made when streaming is stopped
  then restarted.

  Furthermore, SET_INTERFACE(0) is the mechanism by which isochronous
  devices are told to stop streaming, and the comments in
  uvc_video_stop_streaming state that the UVC specification is unclear
  on how a bulk-based device should be told to stop streaming, so it is
  reasonable to expect this particular bulk-based device might be
  expecting the same SET_INTERFACE(0) call that an isochronous device
  would get as means of being told to stop streaming.

  The attached patch fixes the problem for these Epiphan devices by
  adding a SET_INTERFACE(0) call in two places. Either one by itself is
  sufficient to resolve the symptoms but I think it is probably safest
  to include both.

  The first hunk adds a SET_INTERFACE(0) call in
  uvc_video_start_streaming, but only in the bulk-based case where 0 is
  the only possible interface value (it won't mess with an isochronous
  device that might be set to a different interface).

  The second hunk modifies the behaviour of uvc_video_stop_streaming to
  call SET_INTERFACE(0) unconditionally instead of only calling it for
  isochronous devices. Since interface 0 should already be set on non-
  isochronous devices, it should be safe to set it again, and this way
  devices that are expecting it as a signal to stop streaming will get
  it.

  The patch is against 5.4.137 in the vanilla kernel.org source tree,
  but also applies cleanly to the 5.8.63 kernel in Ubuntu 20.4 LTS and
  to the 5.14-rc3 release candidate kernel.

  Since this is clearly an upstream issue unrelated to any vendor
  modifications, should I also submit an upstream bug report directly to
  bugzilla.kernel.org?

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


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

[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

2021-08-02 Thread Colin Ian King

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

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

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


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

[Kernel-packages] [Bug 1938616] Re: Lenovo 14 iml Touchpad not working

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

** Summary changed:

- Lenovo 14 iml Touchpad not working
+ Lenovo 14 iml Touchpad not working in 5.11.0-25-generic (but does in 
5.9.0-rc4+-4)

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

Title:
  Lenovo 14 iml Touchpad not working in 5.11.0-25-generic (but does in
  5.9.0-rc4+-4)

Status in linux package in Ubuntu:
  New

Bug description:
  I m having lenovo 14 iml presently running on kernel 5.11.0-25-generic i am 
using kubuntu 
  my touch pad is not working here tried many kernels no luck. The only kernel 
in which it does work was provided by kai-Heng 
linux-image-5.9.0-rc4+_5.9.0-rc4+-4_amd64.deb it is the only kernel where my 
touchpad works but the problem is in this kernel virtual box does not work as 
intended.

  
  Can anyone help me out to figure out how to get this working on any other 
kernel.

  A bit new here if need any new info i will provide.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Jul 31 19:10:48 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics [17aa:382f]
  InstallationDate: Installed on 2021-07-31 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20RV
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.11.0-25-generic 
root=UUID=48f1-f5cd-4f89-b98b-b6b37bec77fd ro rootflags=subvol=@ 
i8042.reset i8042.nomux i8042.nopnp i8042.noloop quiet splash 
psmouse.proto=bare vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2021
  dmi.bios.release: 1.35
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CJCN35WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.ec.firmware.release: 1.34
  dmi.modalias: 
dmi:bvnLENOVO:bvrCJCN35WW:bd05/10/2021:br1.35:efr1.34:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvr:
  dmi.product.family: Lenovo ThinkBook 14-IML
  dmi.product.name: 20RV
  dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML
  dmi.product.version: Lenovo ThinkBook 14-IML
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Kernel-packages] [Bug 1938053] [NEW] [MSI Modern 14 B10MW] HDMI Problem

You have been subscribed to a public bug:

Cannot connect second monitor with hdmi after update.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 26 17:49:36 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics [1462:12c1]
InstallationDate: Installed on 2021-06-05 (50 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Micro-Star International Co., Ltd. Modern 14 B10MW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic 
root=UUID=375930f6-29d7-4278-861a-7bf26f514a10 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/22/2020
dmi.bios.release: 1.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E14D1IMS.10B
dmi.board.asset.tag: Default string
dmi.board.name: MS-14D1
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE14D1IMS.10B:bd12/22/2020:br1.11:svnMicro-StarInternationalCo.,Ltd.:pnModern14B10MW:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14D1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
dmi.product.family: Modern
dmi.product.name: Modern 14 B10MW
dmi.product.sku: 14D1.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: linux-hwe-5.8 (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug focal ubuntu
-- 
[MSI Modern 14 B10MW] HDMI Problem
https://bugs.launchpad.net/bugs/1938053
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-5.8 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 1938616] [NEW] Lenovo 14 iml Touchpad not working

You have been subscribed to a public bug:

I m having lenovo 14 iml presently running on kernel 5.11.0-25-generic i am 
using kubuntu 
my touch pad is not working here tried many kernels no luck. The only kernel in 
which it does work was provided by kai-Heng 
linux-image-5.9.0-rc4+_5.9.0-rc4+-4_amd64.deb it is the only kernel where my 
touchpad works but the problem is in this kernel virtual box does not work as 
intended.


Can anyone help me out to figure out how to get this working on any other 
kernel.

A bit new here if need any new info i will provide.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: KDE
Date: Sat Jul 31 19:10:48 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo UHD Graphics [17aa:382f]
InstallationDate: Installed on 2021-07-31 (0 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20RV
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.11.0-25-generic 
root=UUID=48f1-f5cd-4f89-b98b-b6b37bec77fd ro rootflags=subvol=@ 
i8042.reset i8042.nomux i8042.nopnp i8042.noloop quiet splash 
psmouse.proto=bare vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/10/2021
dmi.bios.release: 1.35
dmi.bios.vendor: LENOVO
dmi.bios.version: CJCN35WW
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.ec.firmware.release: 1.34
dmi.modalias: 
dmi:bvnLENOVO:bvrCJCN35WW:bd05/10/2021:br1.35:efr1.34:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvr:
dmi.product.family: Lenovo ThinkBook 14-IML
dmi.product.name: 20RV
dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML
dmi.product.version: Lenovo ThinkBook 14-IML
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute kubuntu ubuntu
-- 
Lenovo 14 iml Touchpad not working
https://bugs.launchpad.net/bugs/1938616
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 1938647] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1938647/+attachment/5515193/+files/Dependencies.txt

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

Title:
  Suspend in kernel 5.11 causes the whole network to go down

Status in focal package in Ubuntu:
  New
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New

Bug description:
  I am currently reporting on kernel 5.8 (HWE) on KDE Neon Testing
  Edition (Ubuntu 20.04).  I was mainly on 5.11, tried both kernels from
  Ubuntu and Pop!_OS.

  Every time I put the PC on sleep, the whole network will go down after
  waking up.  Only fix I managed is to fully reboot it.

  Operating System: KDE neon Testing Edition
  KDE Plasma Version: 5.22.4
  KDE Frameworks Version: 5.85.0
  Qt Version: 5.15.3
  Kernel Version: 5.8.0-63-generic (64-bit)
  Graphics Platform: X11
  Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
  Memory: 15.6 GiB of RAM
  Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

  Kernels installed:
  * 5.8.0-63-generic
  * 5.11.0.25.27
  * 5.11.0.7620.21
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: KDE neon 20.04
  InstallationDate: Installed on 2020-04-10 (479 days ago)
  InstallationMedia: neon testing "Bionic" - Build amd64 LIVE Binary 
20200324-11:23
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic-hwe-20.04-edge 5.11.0.25.27~20.04.9 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Tags: focal third-party-packages
  Uname: Linux 5.11.0-25-generic x86_64
  UnreportableReason: This is not an official KDE package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip i2c lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1938647] Re: Suspend in kernel 5.11 causes the whole network to go down

Got it to run

apport-collect 1938647 -p linux-generic-hwe-20.04-edge

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

Title:
  Suspend in kernel 5.11 causes the whole network to go down

Status in focal package in Ubuntu:
  New
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New

Bug description:
  I am currently reporting on kernel 5.8 (HWE) on KDE Neon Testing
  Edition (Ubuntu 20.04).  I was mainly on 5.11, tried both kernels from
  Ubuntu and Pop!_OS.

  Every time I put the PC on sleep, the whole network will go down after
  waking up.  Only fix I managed is to fully reboot it.

  Operating System: KDE neon Testing Edition
  KDE Plasma Version: 5.22.4
  KDE Frameworks Version: 5.85.0
  Qt Version: 5.15.3
  Kernel Version: 5.8.0-63-generic (64-bit)
  Graphics Platform: X11
  Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
  Memory: 15.6 GiB of RAM
  Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

  Kernels installed:
  * 5.8.0-63-generic
  * 5.11.0.25.27
  * 5.11.0.7620.21
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: KDE neon 20.04
  InstallationDate: Installed on 2020-04-10 (479 days ago)
  InstallationMedia: neon testing "Bionic" - Build amd64 LIVE Binary 
20200324-11:23
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic-hwe-20.04-edge 5.11.0.25.27~20.04.9 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Tags: focal third-party-packages
  Uname: Linux 5.11.0-25-generic x86_64
  UnreportableReason: This is not an official KDE package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip i2c lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

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


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

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1938647/+attachment/5515195/+files/ProcEnviron.txt

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

Title:
  Suspend in kernel 5.11 causes the whole network to go down

Status in focal package in Ubuntu:
  New
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New

Bug description:
  I am currently reporting on kernel 5.8 (HWE) on KDE Neon Testing
  Edition (Ubuntu 20.04).  I was mainly on 5.11, tried both kernels from
  Ubuntu and Pop!_OS.

  Every time I put the PC on sleep, the whole network will go down after
  waking up.  Only fix I managed is to fully reboot it.

  Operating System: KDE neon Testing Edition
  KDE Plasma Version: 5.22.4
  KDE Frameworks Version: 5.85.0
  Qt Version: 5.15.3
  Kernel Version: 5.8.0-63-generic (64-bit)
  Graphics Platform: X11
  Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
  Memory: 15.6 GiB of RAM
  Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

  Kernels installed:
  * 5.8.0-63-generic
  * 5.11.0.25.27
  * 5.11.0.7620.21
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: KDE neon 20.04
  InstallationDate: Installed on 2020-04-10 (479 days ago)
  InstallationMedia: neon testing "Bionic" - Build amd64 LIVE Binary 
20200324-11:23
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic-hwe-20.04-edge 5.11.0.25.27~20.04.9 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Tags: focal third-party-packages
  Uname: Linux 5.11.0-25-generic x86_64
  UnreportableReason: This is not an official KDE package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip i2c lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

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


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

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

apport information

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

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

Title:
  Suspend in kernel 5.11 causes the whole network to go down

Status in focal package in Ubuntu:
  New
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New

Bug description:
  I am currently reporting on kernel 5.8 (HWE) on KDE Neon Testing
  Edition (Ubuntu 20.04).  I was mainly on 5.11, tried both kernels from
  Ubuntu and Pop!_OS.

  Every time I put the PC on sleep, the whole network will go down after
  waking up.  Only fix I managed is to fully reboot it.

  Operating System: KDE neon Testing Edition
  KDE Plasma Version: 5.22.4
  KDE Frameworks Version: 5.85.0
  Qt Version: 5.15.3
  Kernel Version: 5.8.0-63-generic (64-bit)
  Graphics Platform: X11
  Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
  Memory: 15.6 GiB of RAM
  Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

  Kernels installed:
  * 5.8.0-63-generic
  * 5.11.0.25.27
  * 5.11.0.7620.21
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: KDE neon 20.04
  InstallationDate: Installed on 2020-04-10 (479 days ago)
  InstallationMedia: neon testing "Bionic" - Build amd64 LIVE Binary 
20200324-11:23
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic-hwe-20.04-edge 5.11.0.25.27~20.04.9 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Tags: focal third-party-packages
  Uname: Linux 5.11.0-25-generic x86_64
  UnreportableReason: This is not an official KDE package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip i2c lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1938647] Re: Suspend in kernel 5.11 causes the whole network to go down