[Kernel-packages] [Bug 2077159] Re: i40e interfaces renamed after upgrade from hwe-6.5

[Lukas Märdian]

** Changed in: netplan.io (Ubuntu)
   Status: New => Invalid

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

Title:
  i40e interfaces renamed after upgrade from hwe-6.5

Status in linux package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Server running Ubuntu 22.04.4 LTS

  Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:

  3: eno1:  mtu 9100 qdisc mq state DOWN 
mode DEFAULT group default qlen 1000
  altname enp102s0f0
  4: eno5:  mtu 1500 qdisc mq state DOWN 
mode DEFAULT group default qlen 1000
  altname enp183s0f0
  6: eno2:  mtu 1500 qdisc mq master mgmt 
state UP mode DEFAULT group default qlen 1000
  altname enp102s0f1
  7: eno6:  mtu 1500 qdisc mq master mgmt 
state DOWN mode DEFAULT group default qlen 1000
  altname enp183s0f1
  8: eno3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp102s0f2
  9: eno7:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp183s0f2
  10: eno4:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp102s0f3
  11: eno8:  mtu 1500 qdisc mq state DOWN 
mode DEFAULT group default qlen 1000
  altname enp183s0f3

  Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:

  3: eno5np0:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000 
  altname enp183s0f0np0 

 
  4: eno1:  mtu 9100 qdisc mq state DOWN 
mode DEFAULT group default qlen 1000
 
  altname enp102s0f0

 
  5: enp101s0f1np1:  mtu 9100 qdisc mq state 
DOWN mode DEFAULT group default qlen 1000
  6: eno2:  mtu 1500 qdisc mq master mgmt 
state UP mode DEFAULT group default qlen 1000
  altname enp102s0f1

 
  7: eno6np1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp183s0f1np1 

 
  8: eno3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp102s0f2
 
  9: eno7np2:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp183s0f2np2 
 
  10: eno4:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp102s0f3
 
  11: eno8np3:  mtu 1500 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
  altname enp183s0f3np3

  Expected result: Static network configuration via netplan keeps
  working after the upgrade.

  Actual result: Static network configuration is no longer applied for the 
interface that changed their name.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 16 09:40 seq
   crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  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:
  CRDA: N/A
  CasperMD5json:
   {
 "result": "skip"
   }
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-12-04 (260 days ago)
  InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64 (20230217.1)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Supermicro SYS-5019D-FN8TP
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic 
root=/dev/mapper/system-root ro
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedP

[Kernel-packages] [Bug 2080489] Re: Network Manager stops functioning on Ubuntu 24.04

[Lukas Märdian]

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

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

Title:
  Network Manager stops functioning on Ubuntu 24.04

Status in linux package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 24.04 about a month ago on a Asus Vivobook. Soon
  after the NetworkManager started misbehaving, with all connections to
  the internet becoming idle now and then. When this event happens the
  only way to restore internet access is to reboot the system. If
  initially these events were occasional, they now take place 3 or 4
  times per day, often after signing in from the lock screen.

  So far I was not able to verify whether NetworkManager is actually
  crashing, the Settings programme reports "NetworkManager not running"
  (see attached image). However, in the command line `systemctl` reports
  an active service:

  ```
  $ systemctl status NetworkManager
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled>
   Active: active (running) since Sun 2024-08-27 18:21:44 WEST; 2h 18min a>
     Docs: man:NetworkManager(8)
     Main PID: 1149 (NetworkManager)
    Tasks: 4 (limit: 18646)
   Memory: 12.2M (peak: 28.6M)
  CPU: 836ms
   CGroup: /system.slice/NetworkManager.service
   └─1149 /usr/sbin/NetworkManager --no-daemon

  ago 27 19:34:08 Symbolic NetworkManager[1149]:   [1724006048.8961] man>
  ago 27 19:34:08 Symbolic NetworkManager[1149]:   [1724006048.8965] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1482] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1484] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1488] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1488] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1489] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.2049] dev>
  ago 27 20:33:50 Symbolic NetworkManager[1149]:   [1724009630.5340] man>
  ago 27 20:33:50 Symbolic NetworkManager[1149]:   [1724009630.5344] dev>
  ```

  But if I try to restart the service, the command line just hangs up:

  ```
  $ ping 1.1.1.1
  ping: connect: Network is unreachable

  $ sudo systemctl restart NetworkManager

  ```

  Also from `ifconfig` there is no response:

  ```
  $ ifconfig -a

  ```

  Please let me know if there is further useful information I can
  report.

  Thank you.

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


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

[Kernel-packages] [Bug 1988018] Re: [mlx5] Intermittent VF-LAG activation failure

[Lukas Märdian]

** Tags added: sru-next

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

Title:
  [mlx5] Intermittent VF-LAG activation failure

Status in linux package in Ubuntu:
  Fix Committed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  New
Status in netplan.io source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Won't Fix
Status in netplan.io source package in Kinetic:
  Won't Fix
Status in linux source package in Mantic:
  Won't Fix
Status in netplan.io source package in Mantic:
  Won't Fix
Status in linux source package in Noble:
  Fix Committed
Status in netplan.io source package in Noble:
  Fix Released

Bug description:
  During system initialization there is a specific sequence that must be
  followed to enable the use of hardware offload and VF-LAG.

  Intermittently one may see that VF-LAG initialization fails:
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 
shared_fdb:1
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 
9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome 
(0x7d49cb)
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 
9): Failed to create LAG (-22)
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 
9): Failed to activate VF LAG
 Make sure all VFs are unbound prior to VF LAG 
activation or deactivation

  This is caused by rebinding the driver prior to the VF lag being
  ready.

  A sysfs knob has recently been added to the driver [0] and we should
  monitor it before attempting to rebind the driver:

  $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state

  The kernel feature is available in the upcoming Kinetic 5.19 kernel
  and we should probably backport it to the Jammy 5.15 kernel.

  0:
  
https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900

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


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

[Kernel-packages] [Bug 2077260] Re: freeze after updating to newest kernel on log in sreen or just after log in (6.8.0-45 ?). Had to use Grub to restero to 6.5.0-45

[Lukas Märdian]

I can see this behavior on a ThinkPad T410 with Intel graphics.

Rolling back to kernel 6.5 or 5.15 solves the issue.

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

Title:
  freeze after updating to newest kernel on log in sreen or just after
  log in (6.8.0-45 ?). Had to use Grub to restero to 6.5.0-45

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

Bug description:
  freeze after updating to newest kernel on log in sreen or just after
  log in (6.8.0-45 ?). Had to use Grub to rester to 6.5.0-45

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-45-generic 6.5.0-45.45~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 18 15:53:56 2024
  SourcePackage: linux-signed-hwe-6.5
  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-6.8/+bug/2077260/+subscriptions


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

[Kernel-packages] [Bug 2072643] Re: Embedded camera using camera sensors ov02e10 and ov08a10 doesn't work: missing kernel driver

[Lukas Märdian]

Both debdiffs have landed, so I'm unsubscribing ~ubuntu-sponsors. Please
re-subscribe should you need further sponsorship.

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

Title:
  Embedded camera using camera sensors ov02e10 and ov08a10 doesn't work:
  missing kernel driver

Status in OEM Priority Project:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in linux-signed-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in linux-signed-oem-6.5 source package in Jammy:
  New
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in linux-signed-oem-6.5 source package in Noble:
  Invalid
Status in ipu6-drivers source package in Oracular:
  Fix Released
Status in linux-signed-oem-6.5 source package in Oracular:
  Invalid

Bug description:
  [SRU Justfication]

  [Impact]

  Device camera won't work.

  [Fix]

  The current version in -proposed pocket may skip installation of built
  kernel module ov02e10 and ov08a10. The fix is to use fixed index
  numbers in dkms.conf.

  [Test Case]

  Install the dkms and check if ov02e10.ko and ov08a10.ko have been
  installed to /lib/modules//updates/dkms.

  [Where problems could occur]

  Minimal, as this is restoring driver modules that were previously
  installed prior to the regression.

  [Other Info]

  While this happens to ipu6-drivers/{oracualr,noble} only, proposed
  fixes are therefore nominated accordingly.

  == original bug report =

  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04
  linux-oem-22.04d 6.5.0.1026.28

  com.canonical.certification::camera/camera-quality_video0 test fails:

  [ WARN:0] global ./modules/videoio/src/cap_gstreamer.cpp (1100) open OpenCV | 
GStreamer warning: Cannot query video position: status=0, value=-1, duration=-1
  /bin/sh: 1: kill: Illegal number: -
  Traceback (most recent call last):
    File 
"/tmp/nest-oh_l6kjy.e6eacba27b81ed7929f808c3af9ceaf803facf6256ab97b917f65943c394f09d/camera_quality_test.py",
 line 178, in 
  sys.exit(main(sys.argv[1:]))
    File "/usr/lib/python3/dist-packages/checkbox_support/helpers/timeout.py", 
line 93, in _f
  return run_with_timeout(f, timeout_s, *args, **kwargs)
    File "/usr/lib/python3/dist-packages/checkbox_support/helpers/timeout.py", 
line 78, in run_with_timeout
  raise TimeoutError("Task unable to finish in {}s".format(timeout_s))
  TimeoutError: Task unable to finish in 120s

  It passed on 6.5.1024.25 on the same device.

  It fails on all Dell Oasis MTL machines
  202312-33186 (usbio, ov02e10)
  202312-33187 (usbio, ov02e10)
  202312-33214 (usbio, hi556, checkbox test pass)
  202312-33215 (usbio, hi556, checkbox test pass)
  202312-32371 (usbio, hi556, checkbox test pass)
  202312-32372 (usbio, ov02e10)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-1026-oem 6.5.0-1026.27
  ProcVersionSignature: Ubuntu 6.5.0-1026.27-oem 6.5.13
  Uname: Linux 6.5.0-1026-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jul 10 06:38:38 2024
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-oddish13+X120
  InstallationDate: Installed on 2024-02-27 (134 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  SourcePackage: linux-signed-oem-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2077872] [NEW] Kernel 5.15.0-118, 119 causes suspend to fail, works fine with 5.15.0-117

[Lukas Fichtner]

Public bug reported:

System:
Env: Desktop
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Kernel: 5.15.0-118(119)-generic
secure boot enabled

Log files:
kern.log -> https://pastebin.ubuntu.com/p/KGN9QcQV9F/
lspci-vnvn.log -> https://pastebin.ubuntu.com/p/fXQYDTPVvr/
version.log -> https://pastebin.ubuntu.com/p/TZzhRshmVJ/

Description:
After updating to Kernel version 5.15.0-118(and 119), the system fails to 
suspend correctly. The system remains turned on and continues to throw errors.
The issue is evident in the logs, which show repeated failures related to task 
freezing during the suspend process. This problem does not occur with Kernel 
version 5.15.0-117, where the system suspends and resumes as expected.

visable Errors:
Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Freezing remaining freezable tasks ...
Freezing of tasks failed after 20.007 seconds (9 tasks refusing to freeze, 
wq_busy=0):
task:lockd   state:I stack:0 pid: 2511 ppid: 2 flags:0x4000
Call Trace:

__schedule+0x24e/0x590
schedule+0x69/0x110
schedule_timeout+0x105/0x140
? srso_return_thunk+0x5/0x10
? srso_return_thunk+0x5/0x10
svc_get_next_xprt+0xf1/0x190 [sunrpc]
svc_recv+0x1a9/0x330 [sunrpc]
lockd+0xa9/0x1c0 [lockd]
? set_grace_period+0xa0/0xa0 [lockd]
kthread+0x12a/0x150
? set_kthread_struct+0x50/0x50
ret_from_fork+0x22/0x30

task:nfsdstate:I stack:0 pid: 2653 ppid: 2 flags:0x4000

Solution/Workaround:
systemctl stop rpcbind nfs-server.service

Package versions:
nfs-kernel-server 1:2.6.1-1ubuntu1.2
rpcbind 1.2.6-2build1

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

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

Title:
  Kernel 5.15.0-118,119 causes suspend to fail, works fine with
  5.15.0-117

Status in linux package in Ubuntu:
  New

Bug description:
  System:
  Env: Desktop
  Description: Ubuntu 22.04.4 LTS
  Release: 22.04
  Kernel: 5.15.0-118(119)-generic
  secure boot enabled

  Log files:
  kern.log -> https://pastebin.ubuntu.com/p/KGN9QcQV9F/
  lspci-vnvn.log -> https://pastebin.ubuntu.com/p/fXQYDTPVvr/
  version.log -> https://pastebin.ubuntu.com/p/TZzhRshmVJ/

  Description:
  After updating to Kernel version 5.15.0-118(and 119), the system fails to 
suspend correctly. The system remains turned on and continues to throw errors.
  The issue is evident in the logs, which show repeated failures related to 
task freezing during the suspend process. This problem does not occur with 
Kernel version 5.15.0-117, where the system suspends and resumes as expected.

  visable Errors:
  Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
  Freezing remaining freezable tasks ...
  Freezing of tasks failed after 20.007 seconds (9 tasks refusing to freeze, 
wq_busy=0):
  task:lockd   state:I stack:0 pid: 2511 ppid: 2 
flags:0x4000
  Call Trace:
  
  __schedule+0x24e/0x590
  schedule+0x69/0x110
  schedule_timeout+0x105/0x140
  ? srso_return_thunk+0x5/0x10
  ? srso_return_thunk+0x5/0x10
  svc_get_next_xprt+0xf1/0x190 [sunrpc]
  svc_recv+0x1a9/0x330 [sunrpc]
  lockd+0xa9/0x1c0 [lockd]
  ? set_grace_period+0xa0/0xa0 [lockd]
  kthread+0x12a/0x150
  ? set_kthread_struct+0x50/0x50
  ret_from_fork+0x22/0x30
  
  task:nfsdstate:I stack:0 pid: 2653 ppid: 2 
flags:0x4000

  Solution/Workaround:
  systemctl stop rpcbind nfs-server.service

  Package versions:
  nfs-kernel-server 1:2.6.1-1ubuntu1.2
  rpcbind 1.2.6-2build1

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


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

[Kernel-packages] [Bug 1988018] Re: [mlx5] Intermittent VF-LAG activation failure

[Lukas Märdian]

This should be fixed as of Netplan v1.0:
https://github.com/canonical/netplan/pull/439

Please re-open if you think this is still an issue.

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: Fix Committed

** Also affects: netplan.io (Ubuntu Noble)
   Importance: Medium
   Status: Triaged

** Changed in: netplan.io (Ubuntu Noble)
   Status: Triaged => Fix Released

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

** Also affects: netplan.io (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

Title:
  [mlx5] Intermittent VF-LAG activation failure

Status in linux package in Ubuntu:
  Fix Committed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  New
Status in netplan.io source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Fix Committed
Status in netplan.io source package in Kinetic:
  Won't Fix
Status in linux source package in Mantic:
  New
Status in netplan.io source package in Mantic:
  New
Status in linux source package in Noble:
  Fix Committed
Status in netplan.io source package in Noble:
  Fix Released

Bug description:
  During system initialization there is a specific sequence that must be
  followed to enable the use of hardware offload and VF-LAG.

  Intermittently one may see that VF-LAG initialization fails:
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 
shared_fdb:1
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 
9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome 
(0x7d49cb)
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 
9): Failed to create LAG (-22)
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 
9): Failed to activate VF LAG
 Make sure all VFs are unbound prior to VF LAG 
activation or deactivation

  This is caused by rebinding the driver prior to the VF lag being
  ready.

  A sysfs knob has recently been added to the driver [0] and we should
  monitor it before attempting to rebind the driver:

  $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state

  The kernel feature is available in the upcoming Kinetic 5.19 kernel
  and we should probably backport it to the Jammy 5.15 kernel.

  0:
  
https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900

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


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

[Kernel-packages] [Bug 2049924] Re: WireGuard broken on Noble ppc64el

[Lukas Märdian]

** Changed in: netplan.io (Ubuntu Noble)
   Status: New => Invalid

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

Title:
  WireGuard broken on Noble ppc64el

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  New
Status in netplan.io source package in Noble:
  Invalid

Bug description:
  Netplan autopkgtests related to Wireguard are currently failing (see
  below) on Noble ppc64el. Trying it manually on a ppc64el system, I
  can't load the kernel module:

  ~# modprobe wireguard
  modprobe: ERROR: could not insert 'wireguard': No such device

  
  And because of that the interface can't be created:

  Jan 19 15:47:59 mantic-bos01-ppc64el NetworkManager[2414]:   
[1705679279.5797] platform-linux: do-add-link[wg0/wireguard]: failure 95 
(Operation not supported - Unknown device type)
  Jan 19 15:47:59 mantic-bos01-ppc64el NetworkManager[2414]:  
[1705679279.5797] manager: (netplan-wg0) couldn't create the device: Failed to 
create WireGuard interface 'wg0' for 'netplan-wg0': Operation not supported

  
  Jan 19 15:45:08 mantic-bos01-ppc64el systemd-networkd[731]: 
/run/systemd/network/10-netplan-wg0.netdev has 0644 mode that is too 
permissive, please adjust the ownership and access mode.
  Jan 19 15:45:08 mantic-bos01-ppc64el systemd-networkd[731]: wg0: netdev could 
not be created: Operation not supported

  
  Autopkgtest error:

  2690s .Interface "wg0" not found.
  2691s .Interface "wg0" not found.
  2692s .Interface "wg0" not found.
  2693s ..Interface "wg0" not found.
  2694s Interface "wg0" not found.
  2695s .Interface "wg0" not found.
  2696s .Interface "wg0" not found.
  2697s .Interface "wg0" not found.
  2697s FAIL
  2697s 
  2697s ==
  2697s FAIL: test_tunnel_wireguard 
(__main__.TestNetworkManager.test_tunnel_wireguard)
  2697s --
  2697s Traceback (most recent call last):
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/tunnels.py", line 126, 
in test_tunnel_wireguard
  2697s self.generate_and_settle(['wg0', 'wg1'])
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 363, in 
generate_and_settle
  2697s self.nm_wait_connected(iface, 60)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 419, in 
nm_wait_connected
  2697s self.wait_output(['nmcli', 'dev', 'show', iface], '(connected', 
timeout)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 416, in 
wait_output
  2697s self.fail('timed out waiting for "{}" to appear in 
{}'.format(expected_output, cmd))
  2697s AssertionError: timed out waiting for "(connected" to appear in 
['nmcli', 'dev', 'show', 'wg0']
  2697s 
  2697s ==
  2697s FAIL: test_tunnel_wireguard 
(__main__.TestNetworkd.test_tunnel_wireguard)
  2697s --
  2697s Traceback (most recent call last):
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/tunnels.py", line 126, 
in test_tunnel_wireguard
  2697s self.generate_and_settle(['wg0', 'wg1'])
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 365, in 
generate_and_settle
  2697s self.networkd_wait_connected(iface, 60)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 423, in 
networkd_wait_connected
  2697s self.wait_output(['networkctl', 'status', iface], '(configured', 
timeout)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 416, in 
wait_output
  2697s self.fail('timed out waiting for "{}" to appear in 
{}'.format(expected_output, cmd))
  2697s AssertionError: timed out waiting for "(configured" to appear in 
['networkctl', 'status', 'wg0']
  2697s 
  2697s --
  2697s Ran 26 tests in 294.247s

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


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

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Lukas Märdian]

Actually, we can further reduce the patch to the removal of
`.generate_mac = true`. This already fixes the issue we observe here.

** Patch added: "lp2037667.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+attachment/5741632/+files/lp2037667.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/2037667

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Lukas Märdian]

This seems to do the trick using the following Netplan config as a
testcase.

All 3 interfaces (tun[0-2]) are correctly created with their local &
remote properties set:

root@jj-abi:~/systemd# ip link show dev tun0
19: tun0@NONE:  mtu 1448 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/gre6 fe80::1 brd 2001:dead:beef::2 permaddr e262:75ae:2aa0::
root@jj-abi:~/systemd# ip link show dev tun1
20: tun1@NONE:  mtu 1332 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/tunnel6 fe80::2 brd 2001:dead:beef::3 permaddr c2aa:7446:cc29::
root@jj-abi:~/systemd# ip link show dev tun2
21: tun2@NONE:  mtu 1444 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/gre6 fe80::3 brd 2001:dead:beef::4 permaddr 3ef2:274c:a921::


Netplan test config:
```
network:
  version: 2
  tunnels:
tun0:
  mode: ip6gre
  local: fe80::1
  remote: 2001:dead:beef::2
tun1:
  mode: vti6
  local: fe80::2
  remote: 2001:dead:beef::3
tun2:
  mode: ip6gre
  key: 1234
  local: fe80::3
  remote: 2001:dead:beef::4
```

** Patch added: "network-netdev-introduce-.iftype-to-netdev-vtable.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+attachment/5741625/+files/network-netdev-introduce-.iftype-to-netdev-vtable.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/2037667

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chas

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Lukas Märdian]

So after bisecting systemd (v249..v251) on Jammy, this seems to be the
commit that changed behavior for the better:

https://github.com/systemd/systemd/commit/9f0cf80dd007491698978dbfe38158d74c1c9526

It probably needs some backporting for v249.11.

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Lukas Märdian]

We talked to our systemd maintainer inside foundations and also reached
out to upstream system [1], which didn't lead anywhere. We shouldn't
need to bisect systemd-networkd and do a high impact systemd SRU to fix
a regression in a kernel update, where we can pinpoint the exact (small)
git commit.

We'd like to ask to have the kernel commit b0ad3c179059 reverted in the
Jammy kernels, to mitigate this regression.


[1] 
https://lists.freedesktop.org/archives/systemd-devel/2023-November/049693.html

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 2049924] Re: WireGuard broken on Noble ppc64el

[Lukas Märdian]

** Tags added: update-excuse

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

Title:
  WireGuard broken on Noble ppc64el

Status in linux package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in linux source package in Noble:
  New
Status in netplan.io source package in Noble:
  New

Bug description:
  Netplan autopkgtests related to Wireguard are currently failing (see
  below) on Noble ppc64el. Trying it manually on a ppc64el system, I
  can't load the kernel module:

  ~# modprobe wireguard
  modprobe: ERROR: could not insert 'wireguard': No such device

  
  And because of that the interface can't be created:

  Jan 19 15:47:59 mantic-bos01-ppc64el NetworkManager[2414]:   
[1705679279.5797] platform-linux: do-add-link[wg0/wireguard]: failure 95 
(Operation not supported - Unknown device type)
  Jan 19 15:47:59 mantic-bos01-ppc64el NetworkManager[2414]:  
[1705679279.5797] manager: (netplan-wg0) couldn't create the device: Failed to 
create WireGuard interface 'wg0' for 'netplan-wg0': Operation not supported

  
  Jan 19 15:45:08 mantic-bos01-ppc64el systemd-networkd[731]: 
/run/systemd/network/10-netplan-wg0.netdev has 0644 mode that is too 
permissive, please adjust the ownership and access mode.
  Jan 19 15:45:08 mantic-bos01-ppc64el systemd-networkd[731]: wg0: netdev could 
not be created: Operation not supported

  
  Autopkgtest error:

  2690s .Interface "wg0" not found.
  2691s .Interface "wg0" not found.
  2692s .Interface "wg0" not found.
  2693s ..Interface "wg0" not found.
  2694s Interface "wg0" not found.
  2695s .Interface "wg0" not found.
  2696s .Interface "wg0" not found.
  2697s .Interface "wg0" not found.
  2697s FAIL
  2697s 
  2697s ==
  2697s FAIL: test_tunnel_wireguard 
(__main__.TestNetworkManager.test_tunnel_wireguard)
  2697s --
  2697s Traceback (most recent call last):
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/tunnels.py", line 126, 
in test_tunnel_wireguard
  2697s self.generate_and_settle(['wg0', 'wg1'])
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 363, in 
generate_and_settle
  2697s self.nm_wait_connected(iface, 60)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 419, in 
nm_wait_connected
  2697s self.wait_output(['nmcli', 'dev', 'show', iface], '(connected', 
timeout)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 416, in 
wait_output
  2697s self.fail('timed out waiting for "{}" to appear in 
{}'.format(expected_output, cmd))
  2697s AssertionError: timed out waiting for "(connected" to appear in 
['nmcli', 'dev', 'show', 'wg0']
  2697s 
  2697s ==
  2697s FAIL: test_tunnel_wireguard 
(__main__.TestNetworkd.test_tunnel_wireguard)
  2697s --
  2697s Traceback (most recent call last):
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/tunnels.py", line 126, 
in test_tunnel_wireguard
  2697s self.generate_and_settle(['wg0', 'wg1'])
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 365, in 
generate_and_settle
  2697s self.networkd_wait_connected(iface, 60)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 423, in 
networkd_wait_connected
  2697s self.wait_output(['networkctl', 'status', iface], '(configured', 
timeout)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 416, in 
wait_output
  2697s self.fail('timed out waiting for "{}" to appear in 
{}'.format(expected_output, cmd))
  2697s AssertionError: timed out waiting for "(configured" to appear in 
['networkctl', 'status', 'wg0']
  2697s 
  2697s --
  2697s Ran 26 tests in 294.247s

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


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

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Lukas Märdian]

** Changed in: systemd (Ubuntu)
   Status: Invalid => 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/2037667

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 2039280] Re: Support IP address protocol

[Lukas Märdian]

Thank you! I confirmed that the added distro-patches match the upstream
patches. The feature looks useful, but it's not very common to backport
new features as part of an SRU... So I'll leave that decision to the SRU
team.

In either way, this should probably first be fixed in the current
"devel" series, i.e. by merging iproute2 v6.4+ from Debian unstable.
Once that is accomplished, we can consider this patch for SRU. Would you
be interested in working on that merge?

Nitpick: When aiming for SRU, you should consider updating the SRU
template in the bug description to the latest version (although, the one
you used might also be accepted as-is) and also change the version
number according to
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging,
e.g.: 6.1.0-1ubuntu2.1

https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

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

Title:
  Support IP address protocol

Status in iproute2 package in Ubuntu:
  Confirmed
Status in iproute2 source package in Mantic:
  Confirmed

Bug description:
  [Impact]

  IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
  provenance of the IP address. The attribute is modeled after ip route
  protocols, and essentially allows the administrator or userspace stack to
  tag addresses in some way that makes sense to the actor in question.
  Support for this feature was merged with commit 47f0bd503210 ("net: Add new
  protocol attribute to IP addresses"), for kernel 5.18.

  In this patch, add support for setting the protocol attribute at IP address
  addition, replacement, and listing requests.

  [Fix]

  Apply the attached patch

  [How to test]

  $ cat << EOF > test.sh
  #!/bin/sh

  addr=192.0.2.1/28
  addr2=${addr%/*}2/${addr#*/}
  ifr=test-dummy123

  sudo ip link add name "$ifr" type dummy
  sudo ip link set "$ifr" up

  sudo ip address add dev "$ifr" "$addr2" proto 0x99

  sudo ip link del "$ifr"
  EOF

  $chmod +x test.sh
  $test.sh
  $ echo $?
  0

  if you get an error instead, like:
  Error: either "local" is duplicate, or "proto" is a garbage.

  your iproute2 is not patched.
  Alternativerly, you could download Linux v6.5 source code and run:

  $ cd linux
  $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto

  [Regression potential]

  Two clean upstream cherry-picks, regression potential should be low.

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


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

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Lukas Märdian]

** Tags added: rls-jj-incoming

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 2038942] Re: [MIR] protection-domain-mapper & qrtr

[Lukas Märdian]

r libgoa-*
- not part of the UI for extra checks
- no translation present, but none needed for this case (user visible)?

 Problems: None

** Changed in: protection-domain-mapper (Ubuntu)
   Status: New => Confirmed

** Changed in: protection-domain-mapper (Ubuntu)
 Assignee: Lukas Märdian (slyon) => Ubuntu Security Team (ubuntu-security)

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

Title:
  [MIR] protection-domain-mapper & qrtr

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed

Bug description:
  [Availability]
  The package protection-domain-mapper is already in Ubuntu universe.
  The package protection-domain-mapper build for the architectures it is 
designed to work on.
  It currently builds and works for architectures: any, verified as working on 
arm64
  Link to package https://launchpad.net/ubuntu/+source/protection-domain-mapper

  [Rationale]

  - The package protection-domain-mapper is required in Ubuntu main for
    ubuntu-desktop on ARM64, as it enables power-indicator (among other
    things) on most Windows on Arm laptops (qcom based laptops ~7 SKUs
    and more coming). There is no other way to implement this.

  - protection-domain-mapper depends on qrtr for library and a systemd
    service it provides.

  - There is no other/better way to solve this that is already in main
    or should go universe->main instead of this. As this is the only
    implementation of talking to the qcom hardware.

  - The package protection-domain-mapper is required in Ubuntu main no
    later than today due to Mantic release, if we want to have the best
    impression of Ubuntu Desktop in the live session on x13s.

  - If that fails, having it fixed as SRU is the next best option.

  [Security]

  - No CVEs/security issues in this software in the past. This is a
    reference open source implementation of these tools, which otherwise
    are used on qcom Android devices

  - no `suid` or `sgid` binaries no executables in `/sbin` and
    `/usr/sbin`

  - Package does install services: pd-mapper.service & qrtr-ns.service
    which allow runtime access to the qcom hardware which are run as
    root

  - Security has been kept in mind and common isolation/risk-mitigation
  patterns are in place utilizing the following features:

  - Packages does not open privileged ports (ports < 1024).

  - Package does not expose any external endpoints

  - Packages does not contain extensions to security-sensitive software
    (filters, scanners, plugins, UI skins, ...)

  [Quality assurance - function/usage]

  - The package works well right after install, i.e. power indicator
    straight away starts to show accurate battery information

  [Quality assurance - maintenance]
  - The package is maintained well in Debian/Ubuntu/Upstream and does
    not have too many, long-term & critical, open bugs
    - Ubuntu 
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug
    https://bugs.launchpad.net/ubuntu/+source/qrtr/+bug
    - Debian 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=protection-domain-mapper 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=qrtr
    - Upstream's bug tracker, e.g., GitHub Issues

  - The package has important open bugs, listing them:
    
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2038944
    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045729 upstream fix at 
https://github.com/andersson/qrtr/pull/24/files

  - The package does deal with exotic hardware, it is present at Lenovo
    X13s to be able to test, fix and verify bugs as many users at
    Canonical and Community have it. And it is available for purchase.

  [Quality assurance - testing]

  - The package does not run a test at build time because adequate
    testing requires exotic hardware & specifically kernel driver loaded

  - The package does not run an autopkgtest because testing requires
    exotic hardware & specifically kernel driver loaded.

  - The package does have not failing autopkgtests right now

  - The package can not be well tested at build or autopkgtest time
    because it requires exotic hardware to test. To make up for that:
     - We have access to such hardware in the team (foundations & kernel)

     - We will add a run-once manual test case to iso tracker to ensure
   that "power indicator shows battery indicator %")

     - We will execute this test case on every upload of
   protection-domain-mapper qrtr and the underlying kernel, as well
   as image milestone testing

     - qrtr package is minimal and will be tested in a more wide
   reaching solution context protection-device-mapper, that is
   causing battery indicator to work.

  [Quality assurance - packaging]

  - debian/watch is present and w

[Kernel-packages] [Bug 2038942] Re: [MIR] protection-domain-mapper & qrtr

[Lukas Märdian]

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

** Changed in: qrtr (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

** Changed in: protection-domain-mapper (Ubuntu)
 Assignee: (unassigned) => Lukas Märdian (slyon)

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

Title:
  [MIR] protection-domain-mapper & qrtr

Status in protection-domain-mapper package in Ubuntu:
  New
Status in qrtr package in Ubuntu:
  Confirmed

Bug description:
  [Availability]
  The package protection-domain-mapper is already in Ubuntu universe.
  The package protection-domain-mapper build for the architectures it is 
designed to work on.
  It currently builds and works for architectures: any, verified as working on 
arm64
  Link to package https://launchpad.net/ubuntu/+source/protection-domain-mapper

  [Rationale]

  - The package protection-domain-mapper is required in Ubuntu main for
    ubuntu-desktop on ARM64, as it enables power-indicator (among other
    things) on most Windows on Arm laptops (qcom based laptops ~7 SKUs
    and more coming). There is no other way to implement this.

  - protection-domain-mapper depends on qrtr for library and a systemd
    service it provides.

  - There is no other/better way to solve this that is already in main
    or should go universe->main instead of this. As this is the only
    implementation of talking to the qcom hardware.

  - The package protection-domain-mapper is required in Ubuntu main no
    later than today due to Mantic release, if we want to have the best
    impression of Ubuntu Desktop in the live session on x13s.

  - If that fails, having it fixed as SRU is the next best option.

  [Security]

  - No CVEs/security issues in this software in the past. This is a
    reference open source implementation of these tools, which otherwise
    are used on qcom Android devices

  - no `suid` or `sgid` binaries no executables in `/sbin` and
    `/usr/sbin`

  - Package does install services: pd-mapper.service & qrtr-ns.service
    which allow runtime access to the qcom hardware which are run as
    root

  - Security has been kept in mind and common isolation/risk-mitigation
  patterns are in place utilizing the following features:

  - Packages does not open privileged ports (ports < 1024).

  - Package does not expose any external endpoints

  - Packages does not contain extensions to security-sensitive software
    (filters, scanners, plugins, UI skins, ...)

  [Quality assurance - function/usage]

  - The package works well right after install, i.e. power indicator
    straight away starts to show accurate battery information

  [Quality assurance - maintenance]
  - The package is maintained well in Debian/Ubuntu/Upstream and does
    not have too many, long-term & critical, open bugs
    - Ubuntu 
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug
    https://bugs.launchpad.net/ubuntu/+source/qrtr/+bug
    - Debian 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=protection-domain-mapper 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=qrtr
    - Upstream's bug tracker, e.g., GitHub Issues

  - The package has important open bugs, listing them:
    
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2038944
    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045729 upstream fix at 
https://github.com/andersson/qrtr/pull/24/files

  - The package does deal with exotic hardware, it is present at Lenovo
    X13s to be able to test, fix and verify bugs as many users at
    Canonical and Community have it. And it is available for purchase.

  [Quality assurance - testing]

  - The package does not run a test at build time because adequate
    testing requires exotic hardware & specifically kernel driver loaded

  - The package does not run an autopkgtest because testing requires
    exotic hardware & specifically kernel driver loaded.

  - The package does have not failing autopkgtests right now

  - The package can not be well tested at build or autopkgtest time
    because it requires exotic hardware to test. To make up for that:
     - We have access to such hardware in the team (foundations & kernel)

     - We will add a run-once manual test case to iso tracker to ensure
   that "power indicator shows battery indicator %")

     - We will execute this test case on every upload of
   protection-domain-mapper qrtr and the underlying kernel, as well
   as image milestone testing

     - qrtr package is minimal and will be tested in a more wide
   reaching solution context protection-device-mapper, that is
   causing battery indicator to work.

  [Quality assurance - packaging]

  - debian/watch is present and works

  - debian/control defines a correct Maintainer field

  - This package does 

[Kernel-packages] [Bug 2038942] Re: [MIR] protection-domain-mapper & qrtr

[Lukas Märdian]

Review for Source Package: qrtr

[Summary]
qrtr is the userspace part for IPC communication with qualcomm processors. It 
is primarily used on mobile phones, but can also be relevant for ARM based 
laptops, such as the Lenovo X13s.

 MIR team ACK (pending security-team ACK), with some suggested
Recommended TODOs.

This does need a security review, so I'll assign ubuntu-security

List of specific binary packages to be promoted to main: libqrtr1, qrtr-tools
Specific binary packages built, but NOT to be promoted to main: None

Notes:
#0 requesting security review, because it's running a service as root, opening 
controll sockets, parsing protocol packages and having no hardening features 
enabled.
#1 This is needed for hardware enablement, no automatic testing can be 
provided, but the hardware is available and a test case described in the ISO 
tracker.

Required TODOs:
- None

Recommended TODOs:
#2 The package should get a team bug subscriber before being promoted
#3 Enablement of isolation/hardening features should be considered (e.g. as 
part of the systemd service)
#4 Adding (hardware independent) smoke tests during build-/autopkgtests should 
be considered, at least making sure the library can be compiled and loaded 
correctly
#5 Consider helping out uptream with adding documentation/man pages
#6 Consider supporting the Debian maintainer with more timely package updates 
after (rare) upstream releases are cut.

[Rationale, Duplication and Ownership]
There is no other package in main providing the same functionality.
A team is committed to own long term maintenance of this package.
The rationale given in the report seems valid and useful for Ubuntu

[Dependencies]
OK:
- no other Dependencies to MIR due to this
  - src:qrtr checked with `check-mir`
  - all dependencies can be found in `seeded-in-ubuntu` (already in main)
  - none of the (potentially auto-generated) dependencies (Depends
and Recommends) that are present after build are not in main
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
  more tests now.

Problems: None

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have unexpected Built-Using entries
- not a go package, no extra constraints to consider in that regard
- not a rust package, no extra constraints to consider in that regard

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not use webkit1,2
- does not use lib*v8 directly
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)
- does not deal with cryptography (en-/decryption, certificates,
  signing, ...)

Problems:
- does run a daemon as root
- doesn't make appropriate (for its exposure) use of established risk
  mitigation features (dropping permissions, using temporary environments,
  restricted users/groups, seccomp, systemd isolation features,
  apparmor, ...)
- does parse data formats (QIPCRTR network packets, QMI structures, ...) from
  an untrusted source (userland).
- does expose any external endpoint (port/socket/... or similar)

[Common blockers]
OK:
 - does not FTBFS currently
- This does seem to need special HW for build or test so it can't be
  automatic at build or autopkgtest time. But as outlined
  by the requester in [Quality assurance - testing] there:
  - is hardware (Lenovo X13s) and a test plan or code (kernel & foundations, 
http://iso.qa.ubuntu.com/qatracker/milestones/449/builds/288343/testcases)
  - is community support to test this for Ubuntu
- no new python2 dependency
- not a Python package
- not a Go package

Problems:
- does not have a test suite that runs at build time
- does not have a non-trivial test suite that runs as autopkgtest

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking is in place.
- debian/watch is present and looks ok (if needed, e.g. non-native)
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- debian/rules is rather clean
- It is not on the lto-disabled list

Problems:
- Upstream update history is sporadic
- Debian/Ubuntu update history is slow
- some lintian warnings:
W: qrtr-tools: no-manual-page [usr/bin/qrtr-{cfg,lookup,ns}]
X: qrtr-tools: systemd-service-file-missing-hardening-features 
[lib/systemd/system/qrtr-ns.service]

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside tests)
- no use of user nobody
- no use of setuid / setgid
- no dependency on webkit, qtwebkit, seed or libgoa-*
- no important open bugs (crashers, etc

[Kernel-packages] [Bug 1988018] Re: [mlx5] Intermittent VF-LAG activation failure

[Lukas Märdian]

Could this be related to https://bugs.launchpad.net/netplan/+bug/2020409
?

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

Title:
  [mlx5] Intermittent VF-LAG activation failure

Status in linux package in Ubuntu:
  Fix Committed
Status in netplan.io package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  New
Status in netplan.io source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Fix Committed
Status in netplan.io source package in Kinetic:
  Won't Fix

Bug description:
  During system initialization there is a specific sequence that must be
  followed to enable the use of hardware offload and VF-LAG.

  Intermittently one may see that VF-LAG initialization fails:
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 
shared_fdb:1
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 
9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome 
(0x7d49cb)
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 
9): Failed to create LAG (-22)
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 
9): Failed to activate VF LAG
 Make sure all VFs are unbound prior to VF LAG 
activation or deactivation

  This is caused by rebinding the driver prior to the VF lag being
  ready.

  A sysfs knob has recently been added to the driver [0] and we should
  monitor it before attempting to rebind the driver:

  $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state

  The kernel feature is available in the upcoming Kinetic 5.19 kernel
  and we should probably backport it to the Jammy 5.15 kernel.

  0:
  
https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900

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


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

[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

[Lukas W]

linux-hwe-5.19 (5.19.0-32) has also arrived in KDE Neon (22.04) now and
can confirm that this has fixed the issue on my Thinkpad X1. None of the
other grub modifications worked any longer, so this is great news.
Thanks all!

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

Title:
  [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
  intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @
  18/1/2022

  Booting into desktop gets heavy screen flickering and disforming (unusable)
  both booting on xorg and wayland

  on kernel 5.13 it did not occur so heavy (only little glitches once in
  a while see bug 1948778)

  adding the kernel paramater intel_idle.max_cstate=4 fixed this

  i had these same bugs on this machine before:

  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1201 F pipewire-media-
lotuspsychje   1207 F pulseaudio
   /dev/snd/seq:lotuspsychje   1193 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 04:22:00 2022
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash 
intel_idle.max_cstate=4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.release: 7.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.14
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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


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

[Kernel-packages] [Bug 1988018] Re: [mlx5] Intermittent VF-LAG activation failure

[Lukas Märdian]

** Tags removed: foundations-triage-discuss

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

Title:
  [mlx5] Intermittent VF-LAG activation failure

Status in linux package in Ubuntu:
  Fix Committed
Status in netplan.io package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  New
Status in netplan.io source package in Jammy:
  New
Status in linux source package in Kinetic:
  Fix Committed
Status in netplan.io source package in Kinetic:
  Triaged

Bug description:
  During system initialization there is a specific sequence that must be
  followed to enable the use of hardware offload and VF-LAG.

  Intermittently one may see that VF-LAG initialization fails:
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 
shared_fdb:1
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 
9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome 
(0x7d49cb)
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 
9): Failed to create LAG (-22)
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 
9): Failed to activate VF LAG
 Make sure all VFs are unbound prior to VF LAG 
activation or deactivation

  This is caused by rebinding the driver prior to the VF lag being
  ready.

  A sysfs knob has recently been added to the driver [0] and we should
  monitor it before attempting to rebind the driver:

  $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state

  The kernel feature is available in the upcoming Kinetic 5.19 kernel
  and we should probably backport it to the Jammy 5.15 kernel.

  0:
  
https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900

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


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

[Kernel-packages] [Bug 1988018] Re: [mlx5] Intermittent VF-LAG activation failure

[Lukas Märdian]

** Changed in: netplan.io (Ubuntu Kinetic)
   Status: New => Triaged

** Changed in: netplan.io (Ubuntu Kinetic)
   Importance: Undecided => Medium

** Tags added: foundations-triage-discuss

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

Title:
  [mlx5] Intermittent VF-LAG activation failure

Status in linux package in Ubuntu:
  Fix Committed
Status in netplan.io package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  New
Status in netplan.io source package in Jammy:
  New
Status in linux source package in Kinetic:
  Fix Committed
Status in netplan.io source package in Kinetic:
  Triaged

Bug description:
  During system initialization there is a specific sequence that must be
  followed to enable the use of hardware offload and VF-LAG.

  Intermittently one may see that VF-LAG initialization fails:
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 
shared_fdb:1
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 
9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome 
(0x7d49cb)
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 
9): Failed to create LAG (-22)
  [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 
9): Failed to activate VF LAG
 Make sure all VFs are unbound prior to VF LAG 
activation or deactivation

  This is caused by rebinding the driver prior to the VF lag being
  ready.

  A sysfs knob has recently been added to the driver [0] and we should
  monitor it before attempting to rebind the driver:

  $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state

  The kernel feature is available in the upcoming Kinetic 5.19 kernel
  and we should probably backport it to the Jammy 5.15 kernel.

  0:
  
https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900

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


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

[Kernel-packages] [Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing

[Lukas Märdian]

Basic VRF support landed in netplan v0.105:
https://github.com/canonical/netplan/pull/285

** Changed in: netplan.io (Ubuntu)
   Status: Confirmed => 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/1737428

Title:
  VRF support to solve routing problems associated with multi-homing

Status in juju:
  Incomplete
Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in netplan.io package in Ubuntu:
  Fix Released

Bug description:
  Problem description:

  * a host is multi-homed if it has multiple network interfaces with L3
  addresses configured (physical or virtual interfaces, natural to
  OpenStack regardless of IPv4/IPv6 and IPv6 in general);

  (see 3.3.4  Local Multihoming
  https://tools.ietf.org/html/rfc1122#page-60 and 3.3.4.2  Multihoming
  Requirements)

  * if all hosts that need to participate in L3 communication are
  located on the same L2 network there is no need for a routing device
  to be present. ARP/NDP and auto-created directly connected routes are
  enough;

  * multi-homing with hosts located on different L2 networks requires more 
intelligent routing:
    - "directly connected" routes are no longer enough to talk to all relevant 
hosts in the same network space;
    - a default gateway in the main routing table may not be the correct 
routing device that knows where to forward traffic (management network traffic 
goes to a management switch and router, other traffic goes to L3 ToR switch but 
may go via different bonds);
    - even if a default gateway knows where to forward traffic, it may not be 
the intended physical path (storage replication traffic must go through a 
specific outgoing interface, not the same interface as storage access traffic 
although both interfaces are connected to the same ToR);
    - there is no longer a single "default gateway" as applications need either 
per-logical-direction routers or to become routers themselves (if destination 
== X, forward to next-hop Y). Leaf-spine architecture is a good example of how 
multiple L2 networks force you to use spaces that have VLANs in different 
switch fabrics => one or more hops between hosts with interfaces associated 
with the same network space;
    - while network spaces implicitly require L3 reachability between each host 
that has a NIC associated with a network space, the current definition does not 
mention routing infrastructure required for that. For a single L2 this problem 
is hidden by directly connected routes, for multi-L2, no solution is provided 
or discussed;

  * existing solutions to multi-homing require routing table management
  on a given host: complex static routing rules, dynamic routing (e.g.
  running an OSPF or BGP daemon on a host);

  * using static routes is rigid and requires network planning (i.e.
  working with network engineers which may have varying degrees of
  experience, doing VLSM planning etc.);

  * using dynamic routing requires a broader integration into an
  organization's L3 network infrastructure. Routing can be implemented
  differently across different organizations and it is a security and
  operational burden to integrate with a company's routing
  infrastructure.

  Summary: a mechanism is needed to associate an interface with a
  forwarding table (FIB) which has its own default gateway and make an
  application with a listen(2)ing socket(2) return connected sockets
  associated with different FIBs. In other words, applications need to
  implicitly get source/destination-based routing capabilities without
  the need to use static routing schemes or dynamic routing and with
  minimum or no modifications to the applications themselves.

  Goals:

  * avoid turning individual hosts into routers;
  * avoid complex static rules;
  * better support multi-fabric deployments with minimum effort (Juju, charms, 
MAAS, applications, network infrastructure);
  * reduce operational complexity (custom L3 infrastructure integration for 
each deployment);
  * reduce delivery risks (L3 infrastructure, L3 department responsiveness 
varies);
  * avoid any form of L2 stretching at the infrastructure level - this is 
inefficient for various reasons.

  NOTE: https://cumulusnetworks.com/blog/vrf-for-linux/ - I recommend to
  read this post to understand suggestions below.

  How to solve it?

  What does it mean for Juju to support VRF devices?

  * enslave certain devices on provisioning based on network space information 
(physical NICs, VLAN devices, bonds AND bridges created for containers must be 
considered) - VRF devices logically enslave devices similar to bridges but work 
differently (on L3, not L2);
  * the above is per network namespace so it will work equally well in a LXD 
container;

  Conceptually:

  # echo 'net.ipv4.tcp_l3mdev_accept = 1' >> /etc/sysctl.conf
  # echo 'net.ipv4.udp_l3mdev_accept = 1' >> /etc/sysctl.c

[Kernel-packages] [Bug 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

[Lukas Märdian]

Does this also happen when you use the more recent version 2.4.8 from
the jammy-updates pocket?

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

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

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

** Tags added: foundations-triage-discuss

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

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

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


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

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

[Lukas Märdian]

Setting the systemd bug task to "Invalid", as this is being handled in
the kernel.

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

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

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

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Kernel-packages] [Bug 1987620] [NEW] kmod v30 missing new modules.builtin.modinfo file

[Lukas Märdian]

Public bug reported:

depmod: WARNING: could not open modules.builtin.modinfo at
/tmp/autopkgtest.tKMBKb/autopkgtest_tmp/mkinitramfs_uvT4BW/lib/modules/5.15.0-27-generic:
No such file or directory

https://autopkgtest.ubuntu.com/results/autopkgtest-
kinetic/kinetic/amd64/i/initramfs-tools/20220823_075538_8b7f5@/log.gz

We probably need to install the corresponding linux-modules-* package to
get that file.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: update-excuse

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

** Tags added: update-excuse

** Summary changed:

- kmod missing new modules.builtin.modinfo file
+ kmod v30 missing new modules.builtin.modinfo file

** No longer affects: linux (Ubuntu)

** Description changed:

  depmod: WARNING: could not open modules.builtin.modinfo at
  
/tmp/autopkgtest.tKMBKb/autopkgtest_tmp/mkinitramfs_uvT4BW/lib/modules/5.15.0-27-generic:
  No such file or directory
  
- I think this is probably something that needs to be shipped by the
- kernel package.
+ https://autopkgtest.ubuntu.com/results/autopkgtest-
+ kinetic/kinetic/amd64/i/initramfs-tools/20220823_075538_8b7f5@/log.gz
+ 
+ We probably need to install the corresponding linux-modules-* package to
+ get that file.

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

Title:
  kmod v30 missing new modules.builtin.modinfo file

Status in initramfs-tools package in Ubuntu:
  New
Status in kmod package in Ubuntu:
  New

Bug description:
  depmod: WARNING: could not open modules.builtin.modinfo at
  
/tmp/autopkgtest.tKMBKb/autopkgtest_tmp/mkinitramfs_uvT4BW/lib/modules/5.15.0-27-generic:
  No such file or directory

  https://autopkgtest.ubuntu.com/results/autopkgtest-
  kinetic/kinetic/amd64/i/initramfs-tools/20220823_075538_8b7f5@/log.gz

  We probably need to install the corresponding linux-modules-* package
  to get that file.

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


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

[Kernel-packages] [Bug 1973065] Re: Zfsutils-Linux: "zvol_wait" script shows error with encrypted volumes

[Fabian Lichtenegger-Lukas]

Hi,

any updates on this?

thx

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

Title:
  Zfsutils-Linux: "zvol_wait" script shows error with encrypted volumes

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  We are currently encounter an issue in the zfsutils-package with
  encrypted zvols.

  The service zfs-volume-wait throws the following error message:
  "Apr 22 13:08:19 test1 zvol_wait[806]: cannot open 
'rpool/export/vault/block': dataset does not exist"

  How to reproduce the error:
  1. zpool create main /dev/sdb
  2. zfs create -o encryption=on -o keylocation=prompt -o keyformat=passphrase 
-V 500M main/test
  3. reboot
  4. systemctl status zfs-volume-wait
  ● zfs-volume-wait.service - Wait for ZFS Volume (zvol) links in /dev
  Loaded: loaded (/lib/systemd/system/zfs-volume-wait.service; enabled; vendor 
preset: enabled)
  Active: active (exited) since Fri 2022-04-22 13:08:19 UTC; 58s ago
  Process: 758 ExecStart=/sbin/zvol_wait (code=exited, status=0/SUCCESS)
  Main PID: 758 (code=exited, status=0/SUCCESS)

  Apr 22 13:08:19 test1 systemd[1]: Starting Wait for ZFS Volume (zvol) links 
in /dev...
  Apr 22 13:08:19 test1 zvol_wait[758]: Testing 1 zvol links
  Apr 22 13:08:19 test1 zvol_wait[806]: cannot open 'rpool/export/vault/block': 
dataset does not exist
  Apr 22 13:08:19 test1 zvol_wait[758]: All zvol links are now present.
  Apr 22 13:08:19 test1 systemd[1]: Finished Wait for ZFS Volume (zvol) links 
in /dev.

  zfs-volume-wait service calls /sbin/zvol_wait which is part of the package 
"zfsutils-linux".
  Line 29, in script "zvol_wait" seems to be causing this error:
  27 filter_out_locked_zvols() {
  28 while read -r zvol; do
  29 if ! [ "$(zfs list -H -o keystatus rpool/export/vault/block "$zvol")" = 
"unavailable" ]; then
  30 echo "$zvol"
  31 fi
  32 done
  33 }

  It seems that this command does not respect the "zfs list" syntax, which 
should be
  "zfs list [-r|-d depth] [-H] [-o property[,...]] [ -t type[,...]] [ -s 
property ] ... [ -S property ] ... [filesystem|volume|snapshot] ..." 
(https://linux.die.net/man/8/zfs)

  Bug was already reported here:
  # https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969457
  # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997980

  This fix is causing the issue:
  # https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888405

  I created an git patch which fixes the issue:
  --- zvol_wait 2022-04-21 19:09:21.57200 +
  +++ zvol_wait_new 2022-04-22 13:25:26.989422811 +
  @@ -26,7 +26,7 @@

  filter_out_locked_zvols() {
  while read -r zvol; do
  - if ! [ "$(zfs list -H -o keystatus rpool/export/vault/block "$zvol")" = 
"unavailable" ]; then
  + if ! [ "$(zfs list -H -o keystatus "$zvol")" = "unavailable" ]; then
  echo "$zvol"
  fi
  done

  After the patch was applied the command works fine:
  root@test1:/sbin# zvol_wait_new
  Testing 1 zvol links
  All zvol links are now present.

  Did i miss anything or is this really a bug?

  Thank you for your help

  Further information:
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  
  Package: zfsutils-linux
  Version: 0.8.3-1ubuntu12.13
  Priority: extra
  Section: admin
  Source: zfs-linux
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian ZFS on Linux maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 1,297 kB
  Provides: zfsutils
  Depends: libnvpair1linux (= 0.8.3-1ubuntu12.13), libuutil1linux (= 
0.8.3-1ubuntu12.13), libzfs2linux (= 0.8.3-1ubuntu12.13), libzpool2linux (= 
0.8.3-1ubuntu12.13), python3, libblkid1 (>= 2.16), libc6 (>= 2.17), libuuid1 
(>= 2.16)
  Recommends: lsb-base, zfs-zed
  Suggests: nfs-kernel-server, samba-common-bin (>= 3.0.23), zfs-initramfs | 
zfs-dracut
  Conflicts: zfs, zfs-fuse
  Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (<< 
0.7.9-2)
  Replaces: spl (<< 0.7.9-2), spl-dkms
  Homepage: https://zfsonlinux.org/
  Task: ubuntu-live, xubuntu-live, ubuntustudio-dvd-live, ubuntukylin-live, 
ubuntu-mate-live, ubuntu-budgie-live
  Phased-Update-Percentage: 30
  Download-Size: 354 kB
  APT-Manual-Installed: yes
  APT-Sources: http://landscape.test.local/repository/standalone/ubuntu 
focal-updates/main amd64 Packages

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


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

[Kernel-packages] [Bug 1944712] Re: systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1

[Lukas Märdian]

Closing this bug for systemd, as it's not relevant anymore IMO and is a
red herring in proposed-migration.

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

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

Title:
  systemd/237-3ubuntu10.52 ADT test failure with linux-
  aws-5.4/5.4.0-1057.60~18.04.1

Status in linux-aws-5.4 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux-aws-5.4/5.4.0-1057.60~18.04.1 on bionic. Whether this
  is caused by the dep8 tests of the tested source or the kernel has yet
  to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/s/systemd/20210923_022411_52338@/log.gz

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


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

[Kernel-packages] [Bug 1973065] [NEW] Zfsutils-Linux: "zvol_wait" script shows error with encrypted volumes

[Fabian Lichtenegger-Lukas]

Public bug reported:

We are currently encounter an issue in the zfsutils-package with
encrypted zvols.

The service zfs-volume-wait throws the following error message:
"Apr 22 13:08:19 test1 zvol_wait[806]: cannot open 'rpool/export/vault/block': 
dataset does not exist"

How to reproduce the error:
1. zpool create main /dev/sdb
2. zfs create -o encryption=on -o keylocation=prompt -o keyformat=passphrase -V 
500M main/test
3. reboot
4. systemctl status zfs-volume-wait
● zfs-volume-wait.service - Wait for ZFS Volume (zvol) links in /dev
Loaded: loaded (/lib/systemd/system/zfs-volume-wait.service; enabled; vendor 
preset: enabled)
Active: active (exited) since Fri 2022-04-22 13:08:19 UTC; 58s ago
Process: 758 ExecStart=/sbin/zvol_wait (code=exited, status=0/SUCCESS)
Main PID: 758 (code=exited, status=0/SUCCESS)

Apr 22 13:08:19 test1 systemd[1]: Starting Wait for ZFS Volume (zvol) links in 
/dev...
Apr 22 13:08:19 test1 zvol_wait[758]: Testing 1 zvol links
Apr 22 13:08:19 test1 zvol_wait[806]: cannot open 'rpool/export/vault/block': 
dataset does not exist
Apr 22 13:08:19 test1 zvol_wait[758]: All zvol links are now present.
Apr 22 13:08:19 test1 systemd[1]: Finished Wait for ZFS Volume (zvol) links in 
/dev.

zfs-volume-wait service calls /sbin/zvol_wait which is part of the package 
"zfsutils-linux".
Line 29, in script "zvol_wait" seems to be causing this error:
27 filter_out_locked_zvols() {
28 while read -r zvol; do
29 if ! [ "$(zfs list -H -o keystatus rpool/export/vault/block "$zvol")" = 
"unavailable" ]; then
30 echo "$zvol"
31 fi
32 done
33 }

It seems that this command does not respect the "zfs list" syntax, which should 
be
"zfs list [-r|-d depth] [-H] [-o property[,...]] [ -t type[,...]] [ -s property 
] ... [ -S property ] ... [filesystem|volume|snapshot] ..." 
(https://linux.die.net/man/8/zfs)

Bug was already reported here:
# https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969457
# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997980

This fix is causing the issue:
# https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888405

I created an git patch which fixes the issue:
--- zvol_wait 2022-04-21 19:09:21.57200 +
+++ zvol_wait_new 2022-04-22 13:25:26.989422811 +
@@ -26,7 +26,7 @@

filter_out_locked_zvols() {
while read -r zvol; do
- if ! [ "$(zfs list -H -o keystatus rpool/export/vault/block "$zvol")" = 
"unavailable" ]; then
+ if ! [ "$(zfs list -H -o keystatus "$zvol")" = "unavailable" ]; then
echo "$zvol"
fi
done

After the patch was applied the command works fine:
root@test1:/sbin# zvol_wait_new
Testing 1 zvol links
All zvol links are now present.

Did i miss anything or is this really a bug?

Thank you for your help

Further information:
Description:Ubuntu 20.04.4 LTS
Release:20.04


Package: zfsutils-linux
Version: 0.8.3-1ubuntu12.13
Priority: extra
Section: admin
Source: zfs-linux
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian ZFS on Linux maintainers 

Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 1,297 kB
Provides: zfsutils
Depends: libnvpair1linux (= 0.8.3-1ubuntu12.13), libuutil1linux (= 
0.8.3-1ubuntu12.13), libzfs2linux (= 0.8.3-1ubuntu12.13), libzpool2linux (= 
0.8.3-1ubuntu12.13), python3, libblkid1 (>= 2.16), libc6 (>= 2.17), libuuid1 
(>= 2.16)
Recommends: lsb-base, zfs-zed
Suggests: nfs-kernel-server, samba-common-bin (>= 3.0.23), zfs-initramfs | 
zfs-dracut
Conflicts: zfs, zfs-fuse
Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (<< 0.7.9-2)
Replaces: spl (<< 0.7.9-2), spl-dkms
Homepage: https://zfsonlinux.org/
Task: ubuntu-live, xubuntu-live, ubuntustudio-dvd-live, ubuntukylin-live, 
ubuntu-mate-live, ubuntu-budgie-live
Phased-Update-Percentage: 30
Download-Size: 354 kB
APT-Manual-Installed: yes
APT-Sources: http://landscape.test.local/repository/standalone/ubuntu 
focal-updates/main amd64 Packages

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


** Tags: zfs zfsutils-linux

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

Title:
  Zfsutils-Linux: "zvol_wait" script shows error with encrypted volumes

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  We are currently encounter an issue in the zfsutils-package with
  encrypted zvols.

  The service zfs-volume-wait throws the following error message:
  "Apr 22 13:08:19 test1 zvol_wait[806]: cannot open 
'rpool/export/vault/block': dataset does not exist"

  How to reproduce the error:
  1. zpool create main /dev/sdb
  2. zfs create -o encryption=on -o keylocation=prompt -o keyformat=passphrase 
-V 500M main/test
  3. reboot
  4. systemctl status zfs-volume-wait
  ● zfs-volume-wait.service - Wait for ZFS Volume (zvol) links in /dev
  Loaded: loaded (/lib/systemd/system/zfs-volume-wait.service; enabled; vendor 
preset: enabled)
  Active: active (exited) si

[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Lukas Märdian]

Transitioning this bug report to the netplan.io package. "nplan" is no
more. There's also a duplicate at LP: #1664818

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: netplan.io (Ubuntu)
 Assignee: (unassigned) => Lukas Märdian (slyon)

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  Invalid
Status in nss-pam-ldapd package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Fix Released
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~kernel-pa

[Kernel-packages] [Bug 1956422] Re: Linux Kernel 5.13.0-23 Suspend Modus

[Lukas Wiest]

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

Re-added duplicate mark, as on 5.13.0-28(5.13.0.28.31~20.04.15) suspend
is working fine again.

** This bug has been marked a duplicate of bug 1956401
   amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

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

Title:
  Linux Kernel 5.13.0-23 Suspend Modus

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi there,

  after updating to kernel 5.13.0-23 the suspend modus is not working anymore. 
I tried it with a Dell inspiron 5415 with AMD processor and a MacBook with a 
Intel processor. 
  I have to start with Kernel 5.13.0-22 and then it works fine.

  When is suspend modus the computer doesn't wake up again.

  Thanx in advance.
  Dietmar

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-23-generic 5.13.0-23.23
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dietmar1227 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  5 08:06:59 2022
  InstallationDate: Installed on 2021-10-21 (75 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Apple Inc. MacBook5,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=dfd4fa6d-1d92-4d20-b916-8d9ed9588566 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/09
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB51.88Z.007D.B03.0904271443
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:br0.1:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:skuSystemSKU#:
  dmi.product.family: MacBook
  dmi.product.name: MacBook5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

[Lukas Wiest]

Yup, can confirm this on my end as well for
5.13.0-28-generic(5.13.0.28.31~20.04.15) suspend is working fine again.

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

Title:
  amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
  works

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  Impact:

  This does not occur with linux-image-5.13.0-22-generic, but does with 
linux-image-5.13.0-23-generic.
  On startup, I get about a 60 second hang, with the following in the kernel 
dmesg:
  Jan  4 15:26:36 inspiron-3505 kernel: [   34.160572] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:26:56 inspiron-3505 kernel: [   54.189055] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  Jan  4 15:27:16 inspiron-3505 kernel: [   74.329264] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:27:36 inspiron-3505 kernel: [   94.337904] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  I have the following GPU:
  04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Picass
  o (rev c2) (prog-if 00 [VGA controller])
  04:00.0 0300: 1002:15d8 (rev c2)
  (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)

  I get a similar hang if I start firefox (when it's probing OpenGL
  contexts), and even with glxgears and glxinfo. Seems like anything
  that'd kick on a OpenGL context does it.  I had a freeze as well when
  I tried running firefox and glxgears both.  Along with odd BUG:
  messages logged (I have some in the attached log.)

  I was running with "iommu=pt", but did try with this removed, still
  got the errors (I think amdgpu driver uses the IOMMU even when it's
  set to IOMMU=pt though.).  See the attached log for some very odd
  "[Hardware Error]" messages that were logged on one test run.  I think
  this was when I tried to run firestorm (second life viewer) -- that
  had a large pause then opened to a black window.

  Per Google, I see there was a bug like this that turned up in kernel
  5.14.15 but fixed in 5.14.17.  See
  https://gitlab.freedesktop.org/drm/amd/-/issues/1770

  Thanks!
  --Henry

  Fix:
  upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is 
disabled in Picasso.")

  Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
  from an upstream patch set. multiple confirmations the problem is
  resolved with the kernel in -proposed.

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


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

[Kernel-packages] [Bug 1956422] Re: Linux Kernel 5.13.0-23 Suspend Modus

[Lukas Wiest]

/var/log/kern.log after suspend attempt and hard reset after ~2 min
nothing happened

** Attachment added: "kern_log-after-crash-hard-reset-reboot.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956422/+attachment/5558262/+files/kern_log-after-crash-hard-reset-reboot.log

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

Title:
  Linux Kernel 5.13.0-23 Suspend Modus

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi there,

  after updating to kernel 5.13.0-23 the suspend modus is not working anymore. 
I tried it with a Dell inspiron 5415 with AMD processor and a MacBook with a 
Intel processor. 
  I have to start with Kernel 5.13.0-22 and then it works fine.

  When is suspend modus the computer doesn't wake up again.

  Thanx in advance.
  Dietmar

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-23-generic 5.13.0-23.23
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dietmar1227 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  5 08:06:59 2022
  InstallationDate: Installed on 2021-10-21 (75 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Apple Inc. MacBook5,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=dfd4fa6d-1d92-4d20-b916-8d9ed9588566 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/09
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB51.88Z.007D.B03.0904271443
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:br0.1:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:skuSystemSKU#:
  dmi.product.family: MacBook
  dmi.product.name: MacBook5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

[Kernel-packages] [Bug 1956422] Re: Linux Kernel 5.13.0-23 Suspend Modus

[Lukas Wiest]

dmesg before suspend attempt

** Attachment added: "dmesg-after-boot-before-crash.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956422/+attachment/5558261/+files/dmesg-after-boot-before-crash.log

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

Title:
  Linux Kernel 5.13.0-23 Suspend Modus

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi there,

  after updating to kernel 5.13.0-23 the suspend modus is not working anymore. 
I tried it with a Dell inspiron 5415 with AMD processor and a MacBook with a 
Intel processor. 
  I have to start with Kernel 5.13.0-22 and then it works fine.

  When is suspend modus the computer doesn't wake up again.

  Thanx in advance.
  Dietmar

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-23-generic 5.13.0-23.23
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dietmar1227 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  5 08:06:59 2022
  InstallationDate: Installed on 2021-10-21 (75 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Apple Inc. MacBook5,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=dfd4fa6d-1d92-4d20-b916-8d9ed9588566 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/09
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB51.88Z.007D.B03.0904271443
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:br0.1:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:skuSystemSKU#:
  dmi.product.family: MacBook
  dmi.product.name: MacBook5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

[Kernel-packages] [Bug 1956422] Re: Linux Kernel 5.13.0-23 Suspend Modus

[Lukas Wiest]

Ok, I've removed the duplication mark from this now and will continue to
post my comments here, until someone responsible decides differently.

I tried to see something in the dmesg after a suspend attempt checking 
/var/log/kern.log
The only new line I could see compared to before the suspend attempt said:
"[  389.117730] PM: suspend entry (deep)"
wich doesn't sound very suspicious to me, but expected?

Another line I spotted in the dmesg running on 5.13.0-27 on the other hand did:
"[1.238821] BUG: kernel NULL pointer dereference, address: 000c"
Booting with 5.13.0-22 or the current 5.16.3 mainline kernel doesn't have this.

Is there anything else you'd want me to try to capture from my system?
I'm using the tuxinvader mainline kernel ppa (ppa:tuxinvader/lts-mainline) on 
my focal installation in the meantime.

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

Title:
  Linux Kernel 5.13.0-23 Suspend Modus

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi there,

  after updating to kernel 5.13.0-23 the suspend modus is not working anymore. 
I tried it with a Dell inspiron 5415 with AMD processor and a MacBook with a 
Intel processor. 
  I have to start with Kernel 5.13.0-22 and then it works fine.

  When is suspend modus the computer doesn't wake up again.

  Thanx in advance.
  Dietmar

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-23-generic 5.13.0-23.23
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dietmar1227 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  5 08:06:59 2022
  InstallationDate: Installed on 2021-10-21 (75 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Apple Inc. MacBook5,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=dfd4fa6d-1d92-4d20-b916-8d9ed9588566 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/09
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB51.88Z.007D.B03.0904271443
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:br0.1:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:skuSystemSKU#:
  dmi.product.family: MacBook
  dmi.product.name: MacBook5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

[Kernel-packages] [Bug 1956422] Re: Linux Kernel 5.13.0-23 Suspend Modus

[Lukas Wiest]

** This bug is no longer a duplicate of bug 1956401
   amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

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

Title:
  Linux Kernel 5.13.0-23 Suspend Modus

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi there,

  after updating to kernel 5.13.0-23 the suspend modus is not working anymore. 
I tried it with a Dell inspiron 5415 with AMD processor and a MacBook with a 
Intel processor. 
  I have to start with Kernel 5.13.0-22 and then it works fine.

  When is suspend modus the computer doesn't wake up again.

  Thanx in advance.
  Dietmar

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-23-generic 5.13.0-23.23
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dietmar1227 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  5 08:06:59 2022
  InstallationDate: Installed on 2021-10-21 (75 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Apple Inc. MacBook5,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=dfd4fa6d-1d92-4d20-b916-8d9ed9588566 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/09
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB51.88Z.007D.B03.0904271443
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:br0.1:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:skuSystemSKU#:
  dmi.product.family: MacBook
  dmi.product.name: MacBook5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

[Lukas Wiest]

Ok so I've subscribed to this bug, as I was led here from bug 1956422,
which is marked as duplicate of this one. That's why I asked in #47 if
the suspend issue should be kept here, or taken to bug 1956422 and
remove the duplicate mark there.

If I go up in the comment history, I can see in #24 @smiddy67 has this suspend 
issue as well since the 5.13.0-23, where as 5.13.0-22 is just fine.
In #34 we see that suspend seems to work fine with the 3700U, wild guess but, 
maybe there's something up with the Ryzen 4000 series that has changed from 
5.13.0-22 to -23 that's still not fixed.
For me the symptom is the not working/freezing on supsend, but as said, the bug 
I found describing my issue is marked as a duplicate of this as of right now. 
So, where do we go now with this?

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

Title:
  amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
  works

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  Impact:

  This does not occur with linux-image-5.13.0-22-generic, but does with 
linux-image-5.13.0-23-generic.
  On startup, I get about a 60 second hang, with the following in the kernel 
dmesg:
  Jan  4 15:26:36 inspiron-3505 kernel: [   34.160572] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:26:56 inspiron-3505 kernel: [   54.189055] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  Jan  4 15:27:16 inspiron-3505 kernel: [   74.329264] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:27:36 inspiron-3505 kernel: [   94.337904] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  I have the following GPU:
  04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Picass
  o (rev c2) (prog-if 00 [VGA controller])
  04:00.0 0300: 1002:15d8 (rev c2)
  (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)

  I get a similar hang if I start firefox (when it's probing OpenGL
  contexts), and even with glxgears and glxinfo. Seems like anything
  that'd kick on a OpenGL context does it.  I had a freeze as well when
  I tried running firefox and glxgears both.  Along with odd BUG:
  messages logged (I have some in the attached log.)

  I was running with "iommu=pt", but did try with this removed, still
  got the errors (I think amdgpu driver uses the IOMMU even when it's
  set to IOMMU=pt though.).  See the attached log for some very odd
  "[Hardware Error]" messages that were logged on one test run.  I think
  this was when I tried to run firestorm (second life viewer) -- that
  had a large pause then opened to a black window.

  Per Google, I see there was a bug like this that turned up in kernel
  5.14.15 but fixed in 5.14.17.  See
  https://gitlab.freedesktop.org/drm/amd/-/issues/1770

  Thanks!
  --Henry

  Fix:
  upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is 
disabled in Picasso.")

  Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
  from an upstream patch set. multiple confirmations the problem is
  resolved with the kernel in -proposed.

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


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

[Kernel-packages] [Bug 1956422] Re: Linux Kernel 5.13.0-23 Suspend Modus

[Lukas Wiest]

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

Bump this bug. Looking at the latest comments on bug 1956401 it seems
someone should remove the duplicate mark here?

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

Title:
  Linux Kernel 5.13.0-23 Suspend Modus

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi there,

  after updating to kernel 5.13.0-23 the suspend modus is not working anymore. 
I tried it with a Dell inspiron 5415 with AMD processor and a MacBook with a 
Intel processor. 
  I have to start with Kernel 5.13.0-22 and then it works fine.

  When is suspend modus the computer doesn't wake up again.

  Thanx in advance.
  Dietmar

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-23-generic 5.13.0-23.23
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dietmar1227 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  5 08:06:59 2022
  InstallationDate: Installed on 2021-10-21 (75 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Apple Inc. MacBook5,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=dfd4fa6d-1d92-4d20-b916-8d9ed9588566 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/09
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB51.88Z.007D.B03.0904271443
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:br0.1:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:skuSystemSKU#:
  dmi.product.family: MacBook
  dmi.product.name: MacBook5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

[Lukas Wiest]

Tested by installing linux-gcp-edge from the proposed repo which
installed mentioned version 5.13.0-1013.16~20.04.1

This didn't fix the suspend bug on focal with a Ryzen 7 4700U, but this gcp 
kernel seems to lack other drivers needed for my device, as my touch screen 
e.g. didn't work and the lid-close didn't even automatically trigger the 
suspend.
But for the bug we're trying to fix the behavior didn't change with this: 
triggering the suspend ends up in trying to go to suspend but then I'm left 
with a black screen, power led on and no reaction anymore.
Recognized the power led goes off shortly, like it would when entering suspend 
normally to start pulsing, but then instantly goes back to permanent on, like 
as it's immediately woken up again instead of staying asleep. But it never 
comes back to live from there.

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

Title:
  amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
  works

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  Impact:

  This does not occur with linux-image-5.13.0-22-generic, but does with 
linux-image-5.13.0-23-generic.
  On startup, I get about a 60 second hang, with the following in the kernel 
dmesg:
  Jan  4 15:26:36 inspiron-3505 kernel: [   34.160572] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:26:56 inspiron-3505 kernel: [   54.189055] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  Jan  4 15:27:16 inspiron-3505 kernel: [   74.329264] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:27:36 inspiron-3505 kernel: [   94.337904] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  I have the following GPU:
  04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Picass
  o (rev c2) (prog-if 00 [VGA controller])
  04:00.0 0300: 1002:15d8 (rev c2)
  (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)

  I get a similar hang if I start firefox (when it's probing OpenGL
  contexts), and even with glxgears and glxinfo. Seems like anything
  that'd kick on a OpenGL context does it.  I had a freeze as well when
  I tried running firefox and glxgears both.  Along with odd BUG:
  messages logged (I have some in the attached log.)

  I was running with "iommu=pt", but did try with this removed, still
  got the errors (I think amdgpu driver uses the IOMMU even when it's
  set to IOMMU=pt though.).  See the attached log for some very odd
  "[Hardware Error]" messages that were logged on one test run.  I think
  this was when I tried to run firestorm (second life viewer) -- that
  had a large pause then opened to a black window.

  Per Google, I see there was a bug like this that turned up in kernel
  5.14.15 but fixed in 5.14.17.  See
  https://gitlab.freedesktop.org/drm/amd/-/issues/1770

  Thanks!
  --Henry

  Fix:
  upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is 
disabled in Picasso.")

  Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
  from an upstream patch set. multiple confirmations the problem is
  resolved with the kernel in -proposed.

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


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

[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

[Lukas Wiest]

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

Title:
  amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
  works

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  Impact:

  This does not occur with linux-image-5.13.0-22-generic, but does with 
linux-image-5.13.0-23-generic.
  On startup, I get about a 60 second hang, with the following in the kernel 
dmesg:
  Jan  4 15:26:36 inspiron-3505 kernel: [   34.160572] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:26:56 inspiron-3505 kernel: [   54.189055] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  Jan  4 15:27:16 inspiron-3505 kernel: [   74.329264] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:27:36 inspiron-3505 kernel: [   94.337904] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  I have the following GPU:
  04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Picass
  o (rev c2) (prog-if 00 [VGA controller])
  04:00.0 0300: 1002:15d8 (rev c2)
  (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)

  I get a similar hang if I start firefox (when it's probing OpenGL
  contexts), and even with glxgears and glxinfo. Seems like anything
  that'd kick on a OpenGL context does it.  I had a freeze as well when
  I tried running firefox and glxgears both.  Along with odd BUG:
  messages logged (I have some in the attached log.)

  I was running with "iommu=pt", but did try with this removed, still
  got the errors (I think amdgpu driver uses the IOMMU even when it's
  set to IOMMU=pt though.).  See the attached log for some very odd
  "[Hardware Error]" messages that were logged on one test run.  I think
  this was when I tried to run firestorm (second life viewer) -- that
  had a large pause then opened to a black window.

  Per Google, I see there was a bug like this that turned up in kernel
  5.14.15 but fixed in 5.14.17.  See
  https://gitlab.freedesktop.org/drm/amd/-/issues/1770

  Thanks!
  --Henry

  Fix:
  upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is 
disabled in Picasso.")

  Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
  from an upstream patch set. multiple confirmations the problem is
  resolved with the kernel in -proposed.

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


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

[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

[Lukas Wiest]

I'm using a Lenovo Ideapad with a Ryzen 7 4700U on Ubuntu 20.04 focal,
and with the focal kernel 5.13.0-27 I still can't suspend the device.
Last working is 5.13.0-22

The mentioned released fix for impish, is it also included in the focal
version of 5.13.0-27 or do we have to wait longer for an focal fix?

If it's already included, and as my device is working perfectly fine, other 
than it won't get into suspend but hang itself on trying to, should that be 
further discussed here or in the as duplicate marked bug 1956422?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956422

The lts-mainline kernel 5.15 is working fine, 5.16 not yet tested (jfyi)

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

Title:
  amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
  works

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  Impact:

  This does not occur with linux-image-5.13.0-22-generic, but does with 
linux-image-5.13.0-23-generic.
  On startup, I get about a 60 second hang, with the following in the kernel 
dmesg:
  Jan  4 15:26:36 inspiron-3505 kernel: [   34.160572] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:26:56 inspiron-3505 kernel: [   54.189055] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  Jan  4 15:27:16 inspiron-3505 kernel: [   74.329264] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:27:36 inspiron-3505 kernel: [   94.337904] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  I have the following GPU:
  04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Picass
  o (rev c2) (prog-if 00 [VGA controller])
  04:00.0 0300: 1002:15d8 (rev c2)
  (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)

  I get a similar hang if I start firefox (when it's probing OpenGL
  contexts), and even with glxgears and glxinfo. Seems like anything
  that'd kick on a OpenGL context does it.  I had a freeze as well when
  I tried running firefox and glxgears both.  Along with odd BUG:
  messages logged (I have some in the attached log.)

  I was running with "iommu=pt", but did try with this removed, still
  got the errors (I think amdgpu driver uses the IOMMU even when it's
  set to IOMMU=pt though.).  See the attached log for some very odd
  "[Hardware Error]" messages that were logged on one test run.  I think
  this was when I tried to run firestorm (second life viewer) -- that
  had a large pause then opened to a black window.

  Per Google, I see there was a bug like this that turned up in kernel
  5.14.15 but fixed in 5.14.17.  See
  https://gitlab.freedesktop.org/drm/amd/-/issues/1770

  Thanks!
  --Henry

  Fix:
  upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is 
disabled in Picasso.")

  Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
  from an upstream patch set. multiple confirmations the problem is
  resolved with the kernel in -proposed.

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


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

[Kernel-packages] [Bug 1951717] Re: Ubuntu 21.10 not booting with 2 screens attached

[Lukas Graussam]

Hi again,

I was able to narrow the problem down. I noticed that indeed a new
kernel version has been installed today causing the problem. Output of
dpkg.log:

cat /var/log/dpkg.log | grep "^2022-01-.*\ installed\ .*linux-image-generic"
2022-01-05 09:35:21 status installed linux-image-generic-hwe-20.04:amd64 
5.11.0.44.48~20.04.22
2022-01-12 16:42:17 status installed linux-image-generic-hwe-20.04:amd64 
5.11.0.46.51~20.04.23
2022-01-19 13:47:05 status installed linux-image-generic-hwe-20.04:amd64 
5.13.0.27.29~20.04.13

When I boot with the previous kernel version 5.11.0.46, everything works
fine. So the bug is apparently introduced in version 5.13.

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 1951717] Re: Ubuntu 21.10 not booting with 2 screens attached

[Lukas Graussam]

Hi everyone,
I did not look into this forum since when I created this entry. So far the 
problem did not occur on my machine with Ubuntu 20.04.

However, the problem became active again just now (I still have 20.04,
but unfortunately I do not know if any kernel update or something else
happened recently, that causes the problem to be back).

The behavior is exactly the same as initially described. Booting not
working with 2 screens attached.

BR Lukas

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

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

[Lukas Graussam]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1951717/+attachment/527/+files/ProcCpuinfo.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

[Lukas Graussam]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1951717/+attachment/530/+files/ProcInterrupts.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

[Lukas Graussam]

apport information

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

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 1951717] PulseList.txt

[Lukas Graussam]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1951717/+attachment/532/+files/PulseList.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 1951717] Lsusb-v.txt

[Lukas Graussam]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1951717/+attachment/526/+files/Lsusb-v.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

[Lukas Graussam]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1951717/+attachment/533/+files/UdevDb.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

[Lukas Graussam]

apport information

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

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 1951717] acpidump.txt

[Lukas Graussam]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1951717/+attachment/535/+files/acpidump.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

[Lukas Graussam]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1951717/+attachment/531/+files/ProcModules.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

[Lukas Graussam]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1951717/+attachment/529/+files/ProcEnviron.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 1951717] Lsusb.txt

[Lukas Graussam]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1951717/+attachment/524/+files/Lsusb.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 1951717] AudioDevicesInUse.txt

[Lukas Graussam]

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1951717/+attachment/519/+files/AudioDevicesInUse.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

[Lukas Graussam]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1951717/+attachment/522/+files/Lspci.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 1951717] Lspci-vt.txt

[Lukas Graussam]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1951717/+attachment/523/+files/Lspci-vt.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 1951717] Lsusb-t.txt

[Lukas Graussam]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1951717/+attachment/525/+files/Lsusb-t.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

[Lukas Graussam]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1951717/+attachment/521/+files/CurrentDmesg.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

[Lukas Graussam]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1951717/+attachment/520/+files/CRDA.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-11-18 (62 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.24
  RfKill:
   
  Tags:  focal wayland-session
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/16/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.80
  dmi.board.name: B560 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 1951717] Re: Ubuntu 21.10 not booting with 2 screens attached

[Lukas Graussam]

apport information

** Tags added: apport-collected focal wayland-session

** Description changed:

  Hi,
  
  I recently bought a desktop PC with the following hardware:
  
  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)
  
  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).
  
  I should also mention, that connecting 2 screens after the boot process
  works completely fine. It is just a problem when booting.
  
  I am for sure not the only one with the problem, I found this problem in
  another forum (I currently cannot find it anymore, unfortunately), where
  someone had exactly the same problem but with different hardware (I
  remember some Nvidia Graphic Card). They reported that the problem is
  not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.
  
  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.
  
  Best regards
  Lukas
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.21
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2021-11-18 (62 days ago)
+ InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
+ IwConfig:
+  lono wireless extensions.
+  
+  enp0s31f6  no wireless extensions.
+  
+  docker0   no wireless extensions.
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=cbb0140b-aa6c-458e-9070-a714a230896e ro quiet splash
+ ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
+ RelatedPackageVersions:
+  linux-restricted-modules-5.13.0-27-generic N/A
+  linux-backports-modules-5.13.0-27-generic  N/A
+  linux-firmware 1.187.24
+ RfKill:
+  
+ Tags:  focal wayland-session
+ Uname: Linux 5.13.0-27-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
vboxusers
+ _MarkForUpload: True
+ dmi.bios.date: 04/16/2021
+ dmi.bios.release: 5.19
+ dmi.bios.vendor: American Megatrends International, LLC.
+ dmi.bios.version: P1.80
+ dmi.board.name: B560 Pro4
+ dmi.board.vendor: ASRock
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/16/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB560Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
+ dmi.product.family: To Be Filled By O.E.M.
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.sku: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1951717/+attachment/518/+files/AlsaInfo.txt

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

[Kernel-packages] [Bug 1951717] [NEW] Ubuntu 21.10 not booting with 2 screens attached

[Lukas Graussam]

Public bug reported:

Hi,

I recently bought a desktop PC with the following hardware:

Mainboard: ASRock B560 Pro4
Processor: Intel Core i5-11600K
RAM: Corsair Vengeance LPX 16GB (2x8GB)
Storage: WD_Black SN850 1TB WDS100T1X0E
Graphics: Processor Graphic (Intel UHD 750)

I installed Ubuntu 21.10 and noticed the following problem:
It freezes at booting (right after GRUB), if there are 2 screens connected. The 
mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but with 
both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

I should also mention, that connecting 2 screens after the boot process
works completely fine. It is just a problem when booting.

I am for sure not the only one with the problem, I found this problem in
another forum (I currently cannot find it anymore, unfortunately), where
someone had exactly the same problem but with different hardware (I
remember some Nvidia Graphic Card). They reported that the problem is
not there with Ubuntu 21.04.3, so I tried that and it really works
without any problem.

Hope this helps to prevent the error in future Ubuntu versions, I am
sticking to 21.04 for now.

Best regards
Lukas

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

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

Title:
  Ubuntu 21.10 not booting with 2 screens attached

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  I recently bought a desktop PC with the following hardware:

  Mainboard: ASRock B560 Pro4
  Processor: Intel Core i5-11600K
  RAM: Corsair Vengeance LPX 16GB (2x8GB)
  Storage: WD_Black SN850 1TB WDS100T1X0E
  Graphics: Processor Graphic (Intel UHD 750)

  I installed Ubuntu 21.10 and noticed the following problem:
  It freezes at booting (right after GRUB), if there are 2 screens connected. 
The mainboard has 1xHDMI and 1xDP, any of them connected alone works fine, but 
with both, it just freezes. I tried booting 21.10 from a live USB, resulting in 
exactly the same problem (not starting if 2 screens connected).

  I should also mention, that connecting 2 screens after the boot
  process works completely fine. It is just a problem when booting.

  I am for sure not the only one with the problem, I found this problem
  in another forum (I currently cannot find it anymore, unfortunately),
  where someone had exactly the same problem but with different hardware
  (I remember some Nvidia Graphic Card). They reported that the problem
  is not there with Ubuntu 21.04.3, so I tried that and it really works
  without any problem.

  Hope this helps to prevent the error in future Ubuntu versions, I am
  sticking to 21.04 for now.

  Best regards
  Lukas

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


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

[Kernel-packages] [Bug 1944712] Re: systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1

[Lukas Märdian]

In more recent kernels (i.e. linux-meta-aws/azure 5.13) I can see
messages like this: " watchdog: BUG: soft lockup - CPU#3 stuck for
238s!" that seems to indicate the kernel is not giving back control to
the userspace/systemd.

Also a message about a missing autofs4 module, that might be related:
"systemd[1]: Failed to find module 'autofs4'"

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

Title:
  systemd/237-3ubuntu10.52 ADT test failure with linux-
  aws-5.4/5.4.0-1057.60~18.04.1

Status in linux-aws-5.4 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux-aws-5.4/5.4.0-1057.60~18.04.1 on bionic. Whether this
  is caused by the dep8 tests of the tested source or the kernel has yet
  to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/s/systemd/20210923_022411_52338@/log.gz

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


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

[Kernel-packages] [Bug 1938650] Re: iwd on Ubuntu 20.04 stopped working since update to kernel 5.11

[Lukas Märdian]

This seems to be a regression (deprecated AF_ALG RC4 support) in the
linux-hwe-5.11 stack: https://lkml.org/lkml/2020/8/4/512

A workaround exists by either using Linux 5.8 or using a newer iwd
version (e.g. from https://launchpad.net/~slyon/+archive/ubuntu/iwd+nm )

Unfortunately, we cannot easily backport a big version jump of iwd into
the 20.04 stable series, but we would need a small patch that only
backports the required iwd RC4 implementation on top of iwd-1.5.

** Also affects: linux-meta-hwe-5.11 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  iwd on Ubuntu 20.04 stopped working since update to  kernel 5.11

Status in iwd package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-5.11 package in Ubuntu:
  New

Bug description:
  I was using iwd on my Acer aspire v17 nitro with Ubuntu 20.04, and it was 
working great. But after the last update to kernel 5.11 it suddenly had stopped 
working. I’ve tried to reinstall it but that didn’t help. I've tried back with 
kernel 5.8 and iwd was working again. Quick google search showed that this is 
actually a wide spread problem since kernel 5.9.x, so I wish to ask is there 
going to be a solution of any kind?
  Regards!
  I.Ivanov
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-28 (6 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: iwd 1.5-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Tags:  focal
  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
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1860672] Re: Autopkgtest failing badly since linux-5.4/5.4.0-11.14

[Lukas Märdian]

It looks like this error happens when the package is only available in
-proposed, but not the release pocket.

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

Title:
  Autopkgtest failing badly since linux-5.4/5.4.0-11.14

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The autopkgtest on the CI infrastructure is failing consistently now:

  http://autopkgtest.ubuntu.com/packages/l/linux/focal/amd64

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200117_130927_d1ea4@/log.gz
 :
  ...
  autopkgtest [13:09:05]: testbed dpkg architecture: amd64
  autopkgtest [13:09:06]:  apt-source linux
  blame: linux
  badpkg: rules extract failed with exit code 1
  autopkgtest [13:09:16]: ERROR: erroneous package: rules extract failed with 
exit code 1
  Exit request sent.

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


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

[Kernel-packages] [Bug 1932368] Re: boot-smoke systemd/237-3ubuntu10.48 ADT test failure with bionic

[Lukas Märdian]

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

** This bug has been marked a duplicate of bug 1931088
   boot-and-services tests fails in impish on armhf (248.3)

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

Title:
  boot-smoke systemd/237-3ubuntu10.48 ADT test failure with bionic

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

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/4.15.0-145.149 on bionic. Whether this is caused by
  the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Possibly similar to Bug 1931088 (boot-and-services tests fails in
  impish on armhf (248.3)

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/armhf/s/systemd/20210617_212156_99b77@/log.gz

  
  Processing triggers for systemd (237-3ubuntu10.48) ...
  (Reading database ... 83520 files and directories currently installed.)
  Removing autopkgtest-satdep (0) ...
  autopkgtest [21:20:14]: test boot-smoke: [---
  reboot #0
  bash: line 1: 41305 Killed  
/tmp/autopkgtest.gB2khM/build.j7s/src/debian/tests/boot-smoke 2> >(tee -a 
/tmp/autopkgtest.gB2khM/boot-smoke-stderr >&2) > >(tee -a 
/tmp/autopkgtest.gB2khM/boot-smoke-stdout)
  autopkgtest [21:20:18]: test process requested reboot with marker 1
  Unexpected error:
  Traceback (most recent call last):
File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 740, in mainloop
  command()
File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 669, in command
  r = f(c, ce)
File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 364, in cmd_reboot
  caller.hook_wait_reboot(**wait_reboot_args)
File "/home/ubuntu/autopkgtest/virt/autopkgtest-virt-lxd", line 238, in 
hook_wait_reboot
  wait_booted()
File "/home/ubuntu/autopkgtest/virt/autopkgtest-virt-lxd", line 104, in 
wait_booted
  VirtSubproc.check_exec(['lxc', 'exec', container_name, '--', 'sh', '-ec', 
r'if [ -d /run/systemd/system ]; then systemctl start network-online.target; 
else while ps -ef | grep -q "/etc/init\.d/rc"; do sleep 1; done; fi'], 
timeout=60)
File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 182, in check_exec
  (status, out, err) = execute_timeout(None, timeout, real_argv,
File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 144, in 
execute_timeout
  (out, err) = sp.communicate(instr)
File "/usr/lib/python3.8/subprocess.py", line 1014, in communicate
  stderr = self.stderr.read()
File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 64, in 
alarm_handler
  raise Timeout()
  VirtSubproc.Timeout
  autopkgtest [21:21:55]: ERROR: testbed failure: cannot send to testbed: 
[Errno 32] Broken pipe

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

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

[Kernel-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)

[Lukas Märdian]

Thank you! The core problem still is that systemd-networkd does not find
any .link and .network file for the enP53p0s0.171 interface, that's why
it cannot apply any configuration (IP address):

> ? 9: enP53p0s0.171
> Link File: n/a
> Network File: n/a

This might very well be related to the additional 
/etc/systemd/network/10-enP53p0s0.link, which is now gone and apparently not 
needed (good!) – leave that away.
Still the configuration/match of that file might still be loaded into the 
running udev, so we must somehow reset udev to a clean state. I'd like to ask 
you for another test run (and potential reboot of that machine – if that is 
possible?):

# try to reload udev at runtime
udevadm control --reload; udevadm trigger; udevadm settle
# wait a bit
sleep 30
# apply netplan configuration
netplan --debug apply
# wait a bit
sleep 30
# check results
networkctl status enP53p0s0.171 --no-pager
ip a


If the IP is still not set, could you please try to reboot the machine and 
check "networkctl" afterwards?

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

Title:
  [Ubuntu 20.4.2]  vLan not getting static IP assigned (on s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Doing vLAN configuration one of the vLANs is not getting static IP assigned 
when the rest are workin without problems
   
  Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com 
   
  ---uname output---
  Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 
17:29:32 UTC 2021 s390x s390x s390x GNU/Linux
   
  Machine Type = z15 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1)Configure the netplan file as follow:
  root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml

  # This is the network config written by 'subiquity'

  network:

ethernets:

  encdb0:

addresses:

- 11.111.114.213/22

macaddress: 02:76:54:00:00:03

  encdc0:

addresses:

- 11.111.112.213/22

macaddress: 02:76:54:00:00:04

  enP50s3832 :

addresses:

- 11.111.112.214/22

  enP53p0s0:

addresses:

- 11.111.112.215/22

vlans:

  encdb0.160:

id: 160

link: encdb0

mtu: 9000

addresses:

- 192.168.160.53/24

  encdc0.150:

id: 150

link: encdc0

mtu: 9000

addresses:

- 192.168.150.53/24

  enP50s3832.170:

id: 170

link: enP50s3832

mtu: 9000

addresses:

- 192.168.170.53/24

  enP53p0s0.171:

id: 171

link: enP53p0s0

mtu: 9000

addresses:

- 192.168.171.53/24

version: 2

  2)run net plan apply:
  root@ilabg13:~# netplan --debug apply

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/00-installer-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/01-iscsi-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass
  them through a final round of validation

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.047: Genera

[Kernel-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)

[Lukas Märdian]

> Gave some time between netplan apply and check without success, I can leave 
> it for
> hours and the IP never gets assigned

Indeed, I cannot see it being assigned an IPv4 address in your latest
"_delay" run. (Well, there is some assignment of an IP to enP53p0s0.171
at 15:05:29 in the journal logs, but that was before you started the
experiment).

> maybe what you are seeing is the manual assignment that I did with
> ip addr add 192.168.171.53/24 dev enP53p0s0.171

No I don't think so, as the timestamp of your manual "ip addr add"
command (08:13:02++) is after the systemd-networkd assignment in the
logs (08:12:38). Also, your output clearly shows that the IP was already
assigned when you tried to (re-)assign it manually (it shows the
"RTNETLINK answers: File exists" error):

> root@ilabg13:~# ip addr add 192.168.171.53/24 dev enP53p0s0.171
> RTNETLINK answers: File exists

I'm a bit worried about the /etc/systemd/network/10-enP53p0s0.link file (now 
there seems to be another one "10-enP53p0s0.link" as well...) – Is this file 
needed? Why was it created?
It matches on "MACAddress=82:0c:9b:c9:78:f8", which would match enP53p0s0 AND 
enP53p0s0.171 at the same time (they use the same inherited MAC address), 
leading to unspecified behavior, as we cannot rename two interfaces to the same 
"Name=enP53p0s0".

Could you try deleting this file in /etc/systemd/network/10-enP53p0s0.link 
(potentially adopting your netplan YAML config to the name assigned to this 
interface by the kernel/systemd) and check if this makes any difference?
# rm /etc/systemd/network/10-enP53p0s0.link

If for some reason you cannot delete this file, try adding a "Type=!vlan" line 
instead:
# cat /etc/systemd/network/10-enP53p0s0.link
[Match]
MACAddress=82:0c:9b:c9:78:f8
Type=!vlan

[Link]
Name=enP53p0s0

Does this make any difference when running "netplan apply && sleep 30 &&
networkctl status -a --no-pager"?

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

Title:
  [Ubuntu 20.4.2]  vLan not getting static IP assigned (on s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Doing vLAN configuration one of the vLANs is not getting static IP assigned 
when the rest are workin without problems
   
  Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com 
   
  ---uname output---
  Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 
17:29:32 UTC 2021 s390x s390x s390x GNU/Linux
   
  Machine Type = z15 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1)Configure the netplan file as follow:
  root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml

  # This is the network config written by 'subiquity'

  network:

ethernets:

  encdb0:

addresses:

- 11.111.114.213/22

macaddress: 02:76:54:00:00:03

  encdc0:

addresses:

- 11.111.112.213/22

macaddress: 02:76:54:00:00:04

  enP50s3832 :

addresses:

- 11.111.112.214/22

  enP53p0s0:

addresses:

- 11.111.112.215/22

vlans:

  encdb0.160:

id: 160

link: encdb0

mtu: 9000

addresses:

- 192.168.160.53/24

  encdc0.150:

id: 150

link: encdc0

mtu: 9000

addresses:

- 192.168.150.53/24

  enP50s3832.170:

id: 170

link: enP50s3832

mtu: 9000

addresses:

- 192.168.170.53/24

  enP53p0s0.171:

id: 171

link: enP53p0s0

mtu: 9000

addresses:

- 192.168.171.53/24

version: 2

  2)run net plan apply:
  root@ilabg13:~# netplan --debug apply

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/00-installer-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/01-iscsi-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass
  them through a final round of validation

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default
  backend to 1

  ** (genera

[Kernel-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)

[Lukas Märdian]

After crushing the logs a bit more, I found a few interesting things and
also have a few open questions. Thank you very much for your `date`
timestamps in between the different steps, those are very helpful in
linking the order of events!

Open questions:
1) The "udevadm-monitor.txt" log shows that there is a manual 
"/etc/systemd/network/10-enP53p0s0.link" configuration file, while all other 
interfaces make use of "/usr/lib/systemd/network/99-default.link". Can you show 
us what is inside this file?

2) In comment #22 you show the output of "networkctl":
root@ilabg13:~# netplan apply
root@ilabg13:~# networkctl status enP53p0s0.171 --no-pager
? 7: enP53p0s0.171
Link File: n/a
Network File: n/a
Type: vlan
State: degraded (pending)
HW Address: 82:0c:9b:c9:78:f8

=> I wonder why "Link File: n/a" and "Network File: n/a" is set.. The
Link state is still "(pending)", would you mind executing the same steps
again and re-executing the "networkctl status enP53p0s0.171 --no-pager"
a bit later again (like 10sec after and 30sec after)?

3) Does the workaround from
https://github.com/systemd/systemd/issues/15445#issuecomment-776856604
work for you? E.g.:

# netplan apply
- wait 15 sec
# networkctl reload
- wait 15 sec
# networkctl renew enP53p0s0.171
- wait 15 sec  
# networkctl reconfigure enP53p0s0.171
- wait 15 sec
# networkctl reconfigure enP53p0s0.171
- wait 30 sec
# networkctl status enP53p0s0.171 --no-pager
# ip a

=== Findings from comment #33 (journalctl_udev_monitor.txt) ===
You executed "netplan apply" between 08:10:29 - 08:10:59 and it looks like 
systemd-networkd found the correct netplan-*.network configuration and applied 
it (assigned the IP) at 08:10:57. See "***" lines:

Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Link state is 
up-to-date
*** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: found matching 
network '/run/systemd/network/10-netplan-enP53p0s0.171.network'
Jun 15 08:10:57 systemd-networkd[182847]: Setting 
'/proc/sys/net/ipv6/conf/enP53p0s0.171/disable_ipv6' to '0'
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: IPv6 successfully 
enabled
Jun 15 08:10:57 systemd-networkd[182847]: Setting 
'/proc/sys/net/ipv6/conf/enP53p0s0.171/proxy_ndp' to '0'
Jun 15 08:10:57 systemd-networkd[182847]: Setting 
'/proc/sys/net/ipv6/conf/enP53p0s0.171/use_tempaddr' to '0'
Jun 15 08:10:57 systemd-networkd[182847]: Setting 
'/proc/sys/net/ipv6/conf/enP53p0s0.171/accept_ra' to '0'
Jun 15 08:10:57 systemd-networkd[182847]: LLDP: Started LLDP client
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Started LLDP.
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Setting address 
genmode for link
[...]
*** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering 
updated address: 192.168.171.53/24 (valid forever)
Jun 15 08:10:57 systemd-networkd[182847]: Sent message type=signal sender=n/a 
destination=n/a path=/org/freedesktop/network1/link/_37 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=45 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route: 
dst: 192.168.171.53/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: 
host, table: local, proto: kernel, type: local
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route: 
dst: 192.168.171.255/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: 
link, table: local, proto: kernel, type: broadcast
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route: 
dst: 192.168.171.0/24, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: link, 
table: main, proto: kernel, type: unicast
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route: 
dst: 192.168.171.0/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: link, 
table: local, proto: kernel, type: broadcast
*** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Addresses set
*** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: State changed: 
configuring -> configured
[...]
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: Processing device 
(SEQNUM=87120, ACTION=change) 
Jun 15 08:11:28 systemd-udevd[182940]: enP50s3832: 
/usr/lib/udev/rules.d/75-net-description.rules:12 Importing properties from 
results of builtin command 'hwdb --subsystem=pci' 
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: 
/usr/lib/udev/rules.d/75-net-description.rules:6 Importing properties from 
results of builtin command 'net_id' 
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: 
/usr/lib/udev/rules.d/80-net-setup-link.rules:5 Importing properties from 
results of builtin command 'path_id' 
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: 
/usr/lib/udev/rules.d/80-net-setup-link.rules:5 Failed to run builtin 
'path_id': No such file or directory 
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: 
/usr/lib/udev/rules.d/80-net-setup-link.rules:9 Importing properties from 

[Kernel-packages] [Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq

[Lukas Waymann]

We've tested driver versions 460.80 and 465.27 on Bionic, Focal, Groovy,
and Hirsute. The full results are available at
 and
,
respectively.

We found one potential issue.  During some boots, the nvidia-settings
GUI only has the "PRIME Profiles" tab with all other options missing.
This only occurred on Hirsute, primarily on one out of three tested
laptops, and primarily with the 460.80 driver.  I could also reproduce
the same issue with the previous driver version (460.73.01).  All other
tests were successful.

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

Title:
  Introduce the 465 driver series, fabric-manager, and libnvidia-nscq

Status in fabric-manager-450 package in Ubuntu:
  Fix Released
Status in fabric-manager-460 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-460 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  In Progress
Status in fabric-manager-450 source package in Bionic:
  Fix Committed
Status in fabric-manager-460 source package in Bionic:
  Fix Committed
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Committed
Status in libnvidia-nscq-460 source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in fabric-manager-450 source package in Focal:
  Fix Committed
Status in fabric-manager-460 source package in Focal:
  Fix Committed
Status in libnvidia-nscq-450 source package in Focal:
  Fix Committed
Status in libnvidia-nscq-460 source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in fabric-manager-450 source package in Groovy:
  Fix Committed
Status in fabric-manager-460 source package in Groovy:
  Fix Committed
Status in libnvidia-nscq-450 source package in Groovy:
  Fix Committed
Status in libnvidia-nscq-460 source package in Groovy:
  Fix Committed
Status in linux-restricted-modules source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Groovy:
  Fix Committed
Status in nvidia-settings source package in Groovy:
  Fix Committed
Status in fabric-manager-450 source package in Hirsute:
  Fix Committed
Status in fabric-manager-460 source package in Hirsute:
  Fix Committed
Status in libnvidia-nscq-450 source package in Hirsute:
  Fix Committed
Status in libnvidia-nscq-460 source package in Hirsute:
  Fix Committed
Status in linux-restricted-modules source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Hirsute:
  Fix Committed
Status in nvidia-settings source package in Hirsute:
  Fix Committed

Bug description:
  Introduce the new NVIDIA 465 driver series, fabric-manager and
  libnvidia-nscq. Also migrate the UDA 450 series to the 460 series.

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

[Kernel-packages] [Bug 1923062] Re: NVIDIA CVE-2021-1076 CVE-2021-1077

[Lukas Waymann]

We've completed testing the desktop drivers and haven't found any
regressions. Detailed results are available here:

* 390.143: 
https://docs.google.com/spreadsheets/d/1usWROD3m7KWjqsjHHmZLQEQFqPohzxaonSpfBd2qxss
* 450.119.03: 
https://docs.google.com/spreadsheets/d/1WIWwFds85uhYH5nlo7VLDJi7KDJUyA98JyktZp6xZ3E
* 460.73.01: 
https://docs.google.com/spreadsheets/d/1gg_EZy2x4Y8fHGDYVN8ys0bCjOKI25S57p1pfAmhJ2k

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

Title:
  NVIDIA CVE-2021-1076  CVE-2021-1077

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-450 source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  In Progress

Bug description:
  Here is the list of the affected drivers:

  418-server - CVE-2021-1076

  460, 450, 460-server, 450-server - CVE-2021-1076  CVE-2021-1077

  390 - CVE-2021-1076

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

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

[Kernel-packages] [Bug 1923872] PulseList.txt

[Lukas]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1923872/+attachment/5489199/+files/PulseList.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

[Lukas]

apport information

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

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor

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

[Lukas]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1923872/+attachment/5489196/+files/ProcEnviron.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.

[Kernel-packages] [Bug 1923872] acpidump.txt

[Lukas]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1923872/+attachment/5489203/+files/acpidump.txt

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

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.

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

[Lukas]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1923872/+attachment/5489198/+files/ProcModules.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.

[Kernel-packages] [Bug 1923872] RfKill.txt

[Lukas]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1923872/+attachment/5489200/+files/RfKill.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To man

[Kernel-packages] [Bug 1923872] Lsusb-v.txt

[Lukas]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1923872/+attachment/5489193/+files/Lsusb-v.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To 

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

[Lukas]

apport information

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

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

[Lukas]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1923872/+attachment/5489201/+files/UdevDb.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To man

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

[Lukas]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1923872/+attachment/5489194/+files/ProcCpuinfo.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.

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

[Lukas]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1923872/+attachment/5489197/+files/ProcInterrupts.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled

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

[Lukas]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1923872/+attachment/5489187/+files/CurrentDmesg.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.

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

[Lukas]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1923872/+attachment/5489189/+files/Lspci.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage

[Kernel-packages] [Bug 1923872] Lsusb-t.txt

[Lukas]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1923872/+attachment/5489192/+files/Lsusb-t.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To 

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

[Lukas]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1923872/+attachment/5489186/+files/CRDA.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage

[Kernel-packages] [Bug 1923872] Lspci-vt.txt

[Lukas]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1923872/+attachment/5489190/+files/Lspci-vt.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To 

[Kernel-packages] [Bug 1923872] Lsusb.txt

[Lukas]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1923872/+attachment/5489191/+files/Lsusb.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage

[Kernel-packages] [Bug 1923872] Re: Issues with using webcam, system freezes or gets unstable after some time

[Lukas]

apport information

** Tags added: apport-collected

** Description changed:

  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does connect
  properly. I can use it in some applications, like skype, zoom and
  discord. But after some time (around 3 minutes, sometimes way longer)
  the cam won't turn on anymore and the system completely freezes or gets
  very unstable, until I unplug the webcam.
  
  dmesg | grep uvcvideo:
  
  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.16
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC3:  lukas  6667 F pulseaudio
+  /dev/snd/controlC2:  lukas  6667 F pulseaudio
+  /dev/snd/controlC1:  lukas  6667 F pulseaudio
+  /dev/snd/controlC0:  lukas  6667 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-10-06 (192 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ NonfreeKernelModules: nvidia_modeset nvidia wl
+ Package: linux (not installed)
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.8.0-50-generic N/A
+  linux-backports-modules-5.8.0-50-generic  N/A
+  linux-firmware1.187.10
+ Tags:  focal
+ Uname: Linux 5.8.0-50-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/05/2019
+ dmi.bios.release: 5.14
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P3.50
+ dmi.board.name: X470 Gaming K4
+ dmi.board.vendor: ASRock
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To Be Filled By O.E.M.
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.sku: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1923872/+attachment/5489185/+files/AlsaInfo.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

[Kernel-packages] [Bug 1923872] IwConfig.txt

[Lukas]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1923872/+attachment/5489188/+files/IwConfig.txt

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lukas  6667 F pulseaudio
   /dev/snd/controlC2:  lukas  6667 F pulseaudio
   /dev/snd/controlC1:  lukas  6667 F pulseaudio
   /dev/snd/controlC0:  lukas  6667 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-06 (192 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f9858e02-9877-4596-bfd8-5609ee9efe8c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To 

[Kernel-packages] [Bug 1923872] [NEW] Issues with using webcam, system freezes or gets unstable after some time

[Lukas]

Public bug reported:

I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does connect
properly. I can use it in some applications, like skype, zoom and
discord. But after some time (around 3 minutes, sometimes way longer)
the cam won't turn on anymore and the system completely freezes or gets
very unstable, until I unplug the webcam.

dmesg | grep uvcvideo:

[4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
[4.700237] usbcore: registered new interface driver uvcvideo
[14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
[15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
[15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
[15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cheese 3.34.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-49-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 14 18:31:37 2021
InstallationDate: Installed on 2020-10-06 (190 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
RelatedPackageVersions:
 cheese3.34.0-1ubuntu1
 cheese-common 3.34.0-1ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.50
dmi.board.name: X470 Gaming K4
dmi.board.vendor: ASRock
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug focal gstreamer-error webcam

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

Title:
  Issues with using webcam, system freezes or gets unstable after some
  time

Status in linux package in Ubuntu:
  New

Bug description:
  I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does
  connect properly. I can use it in some applications, like skype, zoom
  and discord. But after some time (around 3 minutes, sometimes way
  longer) the cam won't turn on anymore and the system completely
  freezes or gets very unstable, until I unplug the webcam.

  dmesg | grep uvcvideo:

  [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893)
  [4.700237] usbcore: registered new interface driver uvcvideo
  [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: 
-110 (exp. 5).
  [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
  [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 18:31:37 2021
  InstallationDate: Installed on 2020-10-06 (190 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese3.34.0-1ubuntu1
   cheese-common 3.34.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.50
  dmi.board.name: X470 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dm

[Kernel-packages] [Bug 1913809] Re: internal webcams of HP Elite X2 G2 not supported

[Lukas Werner]

I think this does not work, because the camera is not recognised/listed
when i run "sudo cam -l". So libcamera does not seem to know the camera
exists.

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

Title:
  internal webcams of HP Elite X2 G2 not supported

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

Bug description:
  Both internal webcams of my HP Elite X2 G2 work well in Windows, but don't 
work in Ubuntu 20.10 or Manjaro. The driver seems to be missing or 
misconfigured. According to linux-hardware.org, it's a "Xeon E3-1200 v5/E3-1500 
v5/6th Gen Core Processor Imaging Unit". Guvcview recognises the Cameras as 
"Intel IPU3 CIO2", but doesn't show an image.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  elis   6420 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-01-28 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 004: ID 044e:1216 Alps Electric Co., Ltd 
   Bus 001 Device 002: ID 0424:2422 Microchip Technology, Inc. (formerly SMSC) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Elite x2 1012 G2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=8e01b873-3dab-4fbf-86ce-04c4932b3c0a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 10/20/2020
  dmi.bios.release: 1.37
  dmi.bios.vendor: HP
  dmi.bios.version: P87 Ver. 01.37
  dmi.board.name: 82CA
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 50.72
  dmi.chassis.asset.tag: 5CG7272QT5
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 80.114
  dmi.modalias: 
dmi:bvnHP:bvrP87Ver.01.37:bd10/20/2020:br1.37:efr80.114:svnHP:pnHPElitex21012G2:pvr:rvnHP:rn82CA:rvrKBCVersion50.72:cvnHP:ct32:cvr:
  dmi.product.family: 103C_5336AN HP Elite x2
  dmi.product.name: HP Elite x2 1012 G2
  dmi.product.sku: Y5E21AV
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1913809] Re: internal webcams of HP Elite X2 G2 not supported

[Lukas Werner]

Thanks for the suggestion! I installed libcamera already, but no
success. The webcams still don't work.

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

Title:
  internal webcams of HP Elite X2 G2 not supported

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

Bug description:
  Both internal webcams of my HP Elite X2 G2 work well in Windows, but don't 
work in Ubuntu 20.10 or Manjaro. The driver seems to be missing or 
misconfigured. According to linux-hardware.org, it's a "Xeon E3-1200 v5/E3-1500 
v5/6th Gen Core Processor Imaging Unit". Guvcview recognises the Cameras as 
"Intel IPU3 CIO2", but doesn't show an image.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  elis   6420 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-01-28 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 004: ID 044e:1216 Alps Electric Co., Ltd 
   Bus 001 Device 002: ID 0424:2422 Microchip Technology, Inc. (formerly SMSC) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Elite x2 1012 G2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=8e01b873-3dab-4fbf-86ce-04c4932b3c0a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 10/20/2020
  dmi.bios.release: 1.37
  dmi.bios.vendor: HP
  dmi.bios.version: P87 Ver. 01.37
  dmi.board.name: 82CA
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 50.72
  dmi.chassis.asset.tag: 5CG7272QT5
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 80.114
  dmi.modalias: 
dmi:bvnHP:bvrP87Ver.01.37:bd10/20/2020:br1.37:efr80.114:svnHP:pnHPElitex21012G2:pvr:rvnHP:rn82CA:rvrKBCVersion50.72:cvnHP:ct32:cvr:
  dmi.product.family: 103C_5336AN HP Elite x2
  dmi.product.name: HP Elite x2 1012 G2
  dmi.product.sku: Y5E21AV
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

[Lukas Waymann]

** Attachment added: "journalctl-boot.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914374/+attachment/5459318/+files/journalctl-boot.log

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

Title:
  Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

Status in linux package in Ubuntu:
  New

Bug description:
  I've installed the focal-desktop-amd64.iso image with SHA-256 sum
  b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from
  http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook
  15 G7 laptop (CID 202009-28216).

  There are multiple issues:

  * The graphical desktop isn't launched. The screen remains black except for a 
cursor blinking erratically in the top left corner of the screen. If I hammer 
Control+Alt+F[12345] for a while, the graphical desktop starts eventually.
  * The screen resolution is 3840x2160 but there is no scaling, so everything 
is tiny.
  * The touchpad does not work.
  * WLAN does not work.
  * Ethernet does not work. I tried two dongles (a USB A as well as a USB C 
dongle).
  * No sound.

  $ cat /proc/version_signature
  Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18

  $ lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

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

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

[Kernel-packages] [Bug 1914374] [NEW] Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

[Lukas Waymann]

Public bug reported:

I've installed the focal-desktop-amd64.iso image with SHA-256 sum
b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from
http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook
15 G7 laptop (CID 202009-28216).

There are multiple issues:

* The graphical desktop isn't launched. The screen remains black except for a 
cursor blinking erratically in the top left corner of the screen. If I hammer 
Control+Alt+F[12345] for a while, the graphical desktop starts eventually.
* The screen resolution is 3840x2160 but there is no scaling, so everything is 
tiny.
* The touchpad does not work.
* WLAN does not work.
* Ethernet does not work. I tried two dongles (a USB A as well as a USB C 
dongle).
* No sound.

$ cat /proc/version_signature
Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18

$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04

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

** Attachment added: "dmesg.log"
   https://bugs.launchpad.net/bugs/1914374/+attachment/5459317/+files/dmesg.log

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

Title:
  Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

Status in linux package in Ubuntu:
  New

Bug description:
  I've installed the focal-desktop-amd64.iso image with SHA-256 sum
  b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from
  http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook
  15 G7 laptop (CID 202009-28216).

  There are multiple issues:

  * The graphical desktop isn't launched. The screen remains black except for a 
cursor blinking erratically in the top left corner of the screen. If I hammer 
Control+Alt+F[12345] for a while, the graphical desktop starts eventually.
  * The screen resolution is 3840x2160 but there is no scaling, so everything 
is tiny.
  * The touchpad does not work.
  * WLAN does not work.
  * Ethernet does not work. I tried two dongles (a USB A as well as a USB C 
dongle).
  * No sound.

  $ cat /proc/version_signature
  Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18

  $ lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

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

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

[Kernel-packages] [Bug 1913809] acpidump.txt

[Lukas Werner]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1913809/+attachment/5458167/+files/acpidump.txt

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

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

Title:
  internal webcams of HP Elite X2 G2 not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Both internal webcams of my HP Elite X2 G2 work well in Windows, but don't 
work in Ubuntu 20.10 or Manjaro. The driver seems to be missing or 
misconfigured. According to linux-hardware.org, it's a "Xeon E3-1200 v5/E3-1500 
v5/6th Gen Core Processor Imaging Unit". Guvcview recognises the Cameras as 
"Intel IPU3 CIO2", but doesn't show an image.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  elis   6420 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-01-28 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 004: ID 044e:1216 Alps Electric Co., Ltd 
   Bus 001 Device 002: ID 0424:2422 Microchip Technology, Inc. (formerly SMSC) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Elite x2 1012 G2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=8e01b873-3dab-4fbf-86ce-04c4932b3c0a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 10/20/2020
  dmi.bios.release: 1.37
  dmi.bios.vendor: HP
  dmi.bios.version: P87 Ver. 01.37
  dmi.board.name: 82CA
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 50.72
  dmi.chassis.asset.tag: 5CG7272QT5
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 80.114
  dmi.modalias: 
dmi:bvnHP:bvrP87Ver.01.37:bd10/20/2020:br1.37:efr80.114:svnHP:pnHPElitex21012G2:pvr:rvnHP:rn82CA:rvrKBCVersion50.72:cvnHP:ct32:cvr:
  dmi.product.family: 103C_5336AN HP Elite x2
  dmi.product.name: HP Elite x2 1012 G2
  dmi.product.sku: Y5E21AV
  dmi.sys.vendor: HP

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

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

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

[Lukas Werner]

apport information

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

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

Title:
  internal webcams of HP Elite X2 G2 not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Both internal webcams of my HP Elite X2 G2 work well in Windows, but don't 
work in Ubuntu 20.10 or Manjaro. The driver seems to be missing or 
misconfigured. According to linux-hardware.org, it's a "Xeon E3-1200 v5/E3-1500 
v5/6th Gen Core Processor Imaging Unit". Guvcview recognises the Cameras as 
"Intel IPU3 CIO2", but doesn't show an image.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  elis   6420 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-01-28 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 004: ID 044e:1216 Alps Electric Co., Ltd 
   Bus 001 Device 002: ID 0424:2422 Microchip Technology, Inc. (formerly SMSC) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Elite x2 1012 G2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=8e01b873-3dab-4fbf-86ce-04c4932b3c0a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 10/20/2020
  dmi.bios.release: 1.37
  dmi.bios.vendor: HP
  dmi.bios.version: P87 Ver. 01.37
  dmi.board.name: 82CA
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 50.72
  dmi.chassis.asset.tag: 5CG7272QT5
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 80.114
  dmi.modalias: 
dmi:bvnHP:bvrP87Ver.01.37:bd10/20/2020:br1.37:efr80.114:svnHP:pnHPElitex21012G2:pvr:rvnHP:rn82CA:rvrKBCVersion50.72:cvnHP:ct32:cvr:
  dmi.product.family: 103C_5336AN HP Elite x2
  dmi.product.name: HP Elite x2 1012 G2
  dmi.product.sku: Y5E21AV
  dmi.sys.vendor: HP

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

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

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

[Lukas Werner]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1913809/+attachment/5458165/+files/UdevDb.txt

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

Title:
  internal webcams of HP Elite X2 G2 not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Both internal webcams of my HP Elite X2 G2 work well in Windows, but don't 
work in Ubuntu 20.10 or Manjaro. The driver seems to be missing or 
misconfigured. According to linux-hardware.org, it's a "Xeon E3-1200 v5/E3-1500 
v5/6th Gen Core Processor Imaging Unit". Guvcview recognises the Cameras as 
"Intel IPU3 CIO2", but doesn't show an image.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  elis   6420 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-01-28 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 004: ID 044e:1216 Alps Electric Co., Ltd 
   Bus 001 Device 002: ID 0424:2422 Microchip Technology, Inc. (formerly SMSC) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Elite x2 1012 G2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=8e01b873-3dab-4fbf-86ce-04c4932b3c0a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 10/20/2020
  dmi.bios.release: 1.37
  dmi.bios.vendor: HP
  dmi.bios.version: P87 Ver. 01.37
  dmi.board.name: 82CA
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 50.72
  dmi.chassis.asset.tag: 5CG7272QT5
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 80.114
  dmi.modalias: 
dmi:bvnHP:bvrP87Ver.01.37:bd10/20/2020:br1.37:efr80.114:svnHP:pnHPElitex21012G2:pvr:rvnHP:rn82CA:rvrKBCVersion50.72:cvnHP:ct32:cvr:
  dmi.product.family: 103C_5336AN HP Elite x2
  dmi.product.name: HP Elite x2 1012 G2
  dmi.product.sku: Y5E21AV
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1913809] RfKill.txt

[Lukas Werner]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1913809/+attachment/5458164/+files/RfKill.txt

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

Title:
  internal webcams of HP Elite X2 G2 not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Both internal webcams of my HP Elite X2 G2 work well in Windows, but don't 
work in Ubuntu 20.10 or Manjaro. The driver seems to be missing or 
misconfigured. According to linux-hardware.org, it's a "Xeon E3-1200 v5/E3-1500 
v5/6th Gen Core Processor Imaging Unit". Guvcview recognises the Cameras as 
"Intel IPU3 CIO2", but doesn't show an image.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  elis   6420 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-01-28 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 004: ID 044e:1216 Alps Electric Co., Ltd 
   Bus 001 Device 002: ID 0424:2422 Microchip Technology, Inc. (formerly SMSC) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Elite x2 1012 G2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=8e01b873-3dab-4fbf-86ce-04c4932b3c0a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 10/20/2020
  dmi.bios.release: 1.37
  dmi.bios.vendor: HP
  dmi.bios.version: P87 Ver. 01.37
  dmi.board.name: 82CA
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 50.72
  dmi.chassis.asset.tag: 5CG7272QT5
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 80.114
  dmi.modalias: 
dmi:bvnHP:bvrP87Ver.01.37:bd10/20/2020:br1.37:efr80.114:svnHP:pnHPElitex21012G2:pvr:rvnHP:rn82CA:rvrKBCVersion50.72:cvnHP:ct32:cvr:
  dmi.product.family: 103C_5336AN HP Elite x2
  dmi.product.name: HP Elite x2 1012 G2
  dmi.product.sku: Y5E21AV
  dmi.sys.vendor: HP

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

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