[Kernel-packages] [Bug 2061986] Re: Mount CIFS fails with Permission denied

[Robert Malz]

Attaching tcpdump output with patch


** Attachment added: "base_5_15_104_with_patch_filtered.pcap"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+attachment/5766753/+files/base_5_15_104_with_patch_filtered.pcap

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

Title:
  Mount CIFS fails with Permission denied

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

Bug description:
  [ Impact ]

   * Mounting SMB share from server without Key Exchange capability is
  failing with Access Denied error

   * Even though SMB server during Session Setup Response in NTLMSSP_CHALLANGE 
message does not advertise
 Key Exchange capabilities SMB client < 5.16 will forcefully use it leading 
to error response during
 TCON requests.

   * Issue can be reproduced on 5.15 or older Kernels, there is no reproduction 
on 6.5 Kernel
   
   * This scenario was fixed in upstream commit 
9de0737d5ba0425c3154d5d83da12a8fa8595c0f
   
   * An example of server without Key Exchange capability is Oracle Solaris 
11.4 SMB zfs, meaning
 mounting share from that server will result in ACCESS_DENIED error.
   
  [ Test Plan ]

   * So far issue was reported only with Oracle Solaris 11.04 smb server
  and Ubuntu with Kernel <= 5.15

   * To reproduce, setup Oracle Solaris SMB server and try to mount share on 
22.04/20.04 (5.15/5.04)
 Steps to configure SMB server:
  1. Download the ISO for Oracle Solaris Common Build Edition [1]
  2. Create a VM with at least 16 GB of memory - I have experienced 
installation issues with less memory
  3. Install Oracle Solaris using the downloaded ISO
  a. Make sure to create a test user
  4. Log into the VM as the root user
  5. Create a test directory for the share:
  a. mkdir /smbshare && chmod 777 /smbshare 
  6. Disable the normal Samba daemon: [2]
  a. svcadm disable svc:/network/samba
  b. svcadm disable svc:/network/wins
  7 Configure the server to serve Samba shares using ZFS in Workgroup mode [3]
  a. svcadm enable -r smb/server
  b. smbadm join -w workgroup
  8 Update the /etc/pam.d/other file to require authentication by adding the 
following line:
  a. password requiredpam_smb_passwd.so.1nowarn
  9. Reset the password for the test user so that it is updated in the SMB 
password database
  10. Create the pool and share it using Samba: [4]
  a. zfs create -o mountpoint=/smbshare/ rpool/smbshare
  b. zfs share -o share.smb=on rpool/smbshare%share

  [1] 

  [2] 

  [3] 

  [4] 


   * With server configured, mount share using ubuntu SMB client
 Expected result: mount operation should succeed
 Actual result: mount returns following error:
  root@ubuntu20:/mnt# mount -t cifs -o username=rmalz //192.168.50.217/smbshare 
test
  Password for rmalz@//192.168.50.217/smbshare:  
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg) 

  [ Where problems could occur ]

   * Upstream patch is changing smb client behavior based on server 
NTLMSSP_CHALLENGE Negotiate Flags,
 if server does not advertise Key Exchange Capability but requires it from 
client communication might
 be broken. It is unknown if such servers are used, such instance should be 
treated as a server bug.

   * Patch is available in upstream kernel since 5.16, any issues associated 
with it should be already
 detected.

   * Patch adds additional requirement checks on server NTLM flags, although it 
is possible to hit
 these checks, I was not able to find any instances of that occurring.

   * To lower regression potential, upstream patch backported to Ubuntu 5.15 
and 5.04 Kernels have been
 tested in following environments:
 smb server: Oracle Solaris 11.04, Ubuntu 22.04 HWE
 smb client: Ubuntu 22.04, Ubuntu 20.04
 During testing no issues have been detected.

  [ Other Info ]
   
   * Error message coming from SMB client is the same as providing incorrect 
credentials, which might
 confuse users. 
   * Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and 
without patch.

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


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

[Kernel-packages] [Bug 2061986] Re: Mount CIFS fails with Permission denied

[Robert Malz]

Attaching tcpdump output without patch

** Attachment added: "base_5_15_104_filtered.pcap"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+attachment/5766752/+files/base_5_15_104_filtered.pcap

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

Title:
  Mount CIFS fails with Permission denied

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

Bug description:
  [ Impact ]

   * Mounting SMB share from server without Key Exchange capability is
  failing with Access Denied error

   * Even though SMB server during Session Setup Response in NTLMSSP_CHALLANGE 
message does not advertise
 Key Exchange capabilities SMB client < 5.16 will forcefully use it leading 
to error response during
 TCON requests.

   * Issue can be reproduced on 5.15 or older Kernels, there is no reproduction 
on 6.5 Kernel
   
   * This scenario was fixed in upstream commit 
9de0737d5ba0425c3154d5d83da12a8fa8595c0f
   
   * An example of server without Key Exchange capability is Oracle Solaris 
11.4 SMB zfs, meaning
 mounting share from that server will result in ACCESS_DENIED error.
   
  [ Test Plan ]

   * So far issue was reported only with Oracle Solaris 11.04 smb server
  and Ubuntu with Kernel <= 5.15

   * To reproduce, setup Oracle Solaris SMB server and try to mount share on 
22.04/20.04 (5.15/5.04)
 Steps to configure SMB server:
  1. Download the ISO for Oracle Solaris Common Build Edition [1]
  2. Create a VM with at least 16 GB of memory - I have experienced 
installation issues with less memory
  3. Install Oracle Solaris using the downloaded ISO
  a. Make sure to create a test user
  4. Log into the VM as the root user
  5. Create a test directory for the share:
  a. mkdir /smbshare && chmod 777 /smbshare 
  6. Disable the normal Samba daemon: [2]
  a. svcadm disable svc:/network/samba
  b. svcadm disable svc:/network/wins
  7 Configure the server to serve Samba shares using ZFS in Workgroup mode [3]
  a. svcadm enable -r smb/server
  b. smbadm join -w workgroup
  8 Update the /etc/pam.d/other file to require authentication by adding the 
following line:
  a. password requiredpam_smb_passwd.so.1nowarn
  9. Reset the password for the test user so that it is updated in the SMB 
password database
  10. Create the pool and share it using Samba: [4]
  a. zfs create -o mountpoint=/smbshare/ rpool/smbshare
  b. zfs share -o share.smb=on rpool/smbshare%share

  [1] 

  [2] 

  [3] 

  [4] 


   * With server configured, mount share using ubuntu SMB client
 Expected result: mount operation should succeed
 Actual result: mount returns following error:
  root@ubuntu20:/mnt# mount -t cifs -o username=rmalz //192.168.50.217/smbshare 
test
  Password for rmalz@//192.168.50.217/smbshare:  
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg) 

  [ Where problems could occur ]

   * Upstream patch is changing smb client behavior based on server 
NTLMSSP_CHALLENGE Negotiate Flags,
 if server does not advertise Key Exchange Capability but requires it from 
client communication might
 be broken. It is unknown if such servers are used, such instance should be 
treated as a server bug.

   * Patch is available in upstream kernel since 5.16, any issues associated 
with it should be already
 detected.

   * Patch adds additional requirement checks on server NTLM flags, although it 
is possible to hit
 these checks, I was not able to find any instances of that occurring.

   * To lower regression potential, upstream patch backported to Ubuntu 5.15 
and 5.04 Kernels have been
 tested in following environments:
 smb server: Oracle Solaris 11.04, Ubuntu 22.04 HWE
 smb client: Ubuntu 22.04, Ubuntu 20.04
 During testing no issues have been detected.

  [ Other Info ]
   
   * Error message coming from SMB client is the same as providing incorrect 
credentials, which might
 confuse users. 
   * Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and 
without patch.

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


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

[Kernel-packages] [Bug 2061986] [NEW] Mount CIFS fails with Permission denied

[Robert Malz]

Public bug reported:

[ Impact ]

 * Mounting SMB share from server without Key Exchange capability is
failing with Access Denied error

 * Even though SMB server during Session Setup Response in NTLMSSP_CHALLANGE 
message does not advertise
   Key Exchange capabilities SMB client < 5.16 will forcefully use it leading 
to error response during
   TCON requests.

 * Issue can be reproduced on 5.15 or older Kernels, there is no reproduction 
on 6.5 Kernel
 
 * This scenario was fixed in upstream commit 
9de0737d5ba0425c3154d5d83da12a8fa8595c0f
 
 * An example of server without Key Exchange capability is Oracle Solaris 11.4 
SMB zfs, meaning
   mounting share from that server will result in ACCESS_DENIED error.
 
[ Test Plan ]

 * So far issue was reported only with Oracle Solaris 11.04 smb server
and Ubuntu with Kernel <= 5.15

 * To reproduce, setup Oracle Solaris SMB server and try to mount share on 
22.04/20.04 (5.15/5.04)
   Steps to configure SMB server:
1. Download the ISO for Oracle Solaris Common Build Edition [1]
2. Create a VM with at least 16 GB of memory - I have experienced installation 
issues with less memory
3. Install Oracle Solaris using the downloaded ISO
a. Make sure to create a test user
4. Log into the VM as the root user
5. Create a test directory for the share:
a. mkdir /smbshare && chmod 777 /smbshare 
6. Disable the normal Samba daemon: [2]
a. svcadm disable svc:/network/samba
b. svcadm disable svc:/network/wins
7 Configure the server to serve Samba shares using ZFS in Workgroup mode [3]
a. svcadm enable -r smb/server
b. smbadm join -w workgroup
8 Update the /etc/pam.d/other file to require authentication by adding the 
following line:
a. password requiredpam_smb_passwd.so.1nowarn
9. Reset the password for the test user so that it is updated in the SMB 
password database
10. Create the pool and share it using Samba: [4]
a. zfs create -o mountpoint=/smbshare/ rpool/smbshare
b. zfs share -o share.smb=on rpool/smbshare%share

[1] <https://www.oracle.com/solaris/solaris11/downloads/solaris-downloads.html>
[2] 
<https://docs.oracle.com/cd/E26502_01/html/E29004/migratingfromsamba.html#scrolltoc>
[3] 
<https://docs.oracle.com/cd/E26502_01/html/E29004/configuringoperationmodetm.html#configureworkgroupmodetask>
[4] 
<https://docs.oracle.com/cd/E26502_01/html/E29004/managingsmbshares.html#createstaticsmbsharezfstask>

 * With server configured, mount share using ubuntu SMB client
   Expected result: mount operation should succeed
   Actual result: mount returns following error:
root@ubuntu20:/mnt# mount -t cifs -o username=rmalz //192.168.50.217/smbshare 
test
Password for rmalz@//192.168.50.217/smbshare:  
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg) 

[ Where problems could occur ]

 * Upstream patch is changing smb client behavior based on server 
NTLMSSP_CHALLENGE Negotiate Flags,
   if server does not advertise Key Exchange Capability but requires it from 
client communication might
   be broken. It is unknown if such servers are used, such instance should be 
treated as a server bug.

 * Patch is available in upstream kernel since 5.16, any issues associated with 
it should be already
   detected.

 * Patch adds additional requirement checks on server NTLM flags, although it 
is possible to hit
   these checks, I was not able to find any instances of that occurring.

 * To lower regression potential, upstream patch backported to Ubuntu 5.15 and 
5.04 Kernels have been
   tested in following environments:
   smb server: Oracle Solaris 11.04, Ubuntu 22.04 HWE
   smb client: Ubuntu 22.04, Ubuntu 20.04
   During testing no issues have been detected.

[ Other Info ]
 
 * Error message coming from SMB client is the same as providing incorrect 
credentials, which might
   confuse users. 
 * Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and 
without patch.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Robert Malz (rmalz)
 Status: New

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Robert Malz (rmalz)
 Status: New

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Robert Malz (rmalz)
 Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Robert Malz (rmalz)

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Robert Malz (rmalz)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Robert Malz (rmalz)

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

** Changed in: linux (Ubuntu Jammy)

[Kernel-packages] [Bug 2051720]

[robert]

(In reply to Luiz Von Dentz from comment #16)
> Can you guys try with the following change:
> 
> https://patchwork.kernel.org/project/bluetooth/patch/20240401193515.2525201-
> 1-luiz.de...@gmail.com/

I have the same issue and applied this patch to my kernel, but it seems
to have broken the btintel module. I get a null pointer deref on boot
and bluetooth is broken:

[2.317366] BUG: kernel NULL pointer dereference, address: 0070
[2.317699] #PF: supervisor read access in kernel mode
[2.317993] #PF: error_code(0x) - not-present page
[2.318280] PGD 0 P4D 0
[2.318283] Oops:  [#1] PREEMPT SMP NOPTI
[2.318842] CPU: 3 PID: 185 Comm: kworker/u33:0 Not tainted 
6.8.3-gentoo-dist #1
[2.318844] Hardware name: AZW SER/SER, BIOS SER7PRO_P5C8V30 09/15/2023
[2.318845] Workqueue: hci0 hci_alloc_dev_priv [bluetooth]
[2.319426] RIP: 0010:btintel_configure_setup+0x245/0x970 [btintel]
[2.320365] Code: 85 ff 75 a1 f0 41 80 8e 51 06 00 00 02 f0 41 80 8e 51 06 
00 00 04 f0 41 80 8e 51 06 00 00 08 49 c7 86 38 17 00 00 b0 63 66 c1 <83> 7b 70 
0a 75 7b 48 8b 83 d0 00 00 00 80 78 01 37 75 6e 0f 1f 44
[2.320691] RSP: 0018:a215005cfd48 EFLAGS: 00010202
[2.321452] RAX:  RBX:  RCX: 8026
[2.321760] RDX: 8027 RSI: d3238404d700 RDI: 
[2.322437] RBP: 91a940ccc6c8 R08: 8027 R09: 8026
[2.322438] R10: 0001 R11:  R12: 91a940ccc6d0
[2.322439] R13: 91a947f50c00 R14: 91a940ccc000 R15: 91a940ccca88
[2.322441] FS:  () GS:91af820c() 
knlGS:
[2.323737] CS:  0010 DS:  ES:  CR0: 80050033
[2.323739] CR2: 0070 CR3: 00010dfa2000 CR4: 00f50ef0
[2.323740] PKRU: 5554
[2.323740] Call Trace:
[2.323743]  
[2.326248]  ? __die_body+0x68/0xb0
[2.326253]  ? page_fault_oops+0x3a3/0x400
[2.326256]  ? exc_page_fault+0x60/0xf0
[2.326265]  ? asm_exc_page_fault+0x26/0x30
[2.326269]  ? btintel_configure_setup+0x245/0x970 [btintel]
[2.328091]  ? btintel_configure_setup+0x16c/0x970 [btintel]
[2.328093]  ? __ia32_compat_sys_sysinfo+0x230/0x270
[2.329006]  hci_dev_open_sync+0x166/0x1610 [bluetooth]
[2.329013]  ? srso_alias_return_thunk+0x5/0xfbef5
[2.329015]  ? srso_alias_return_thunk+0x5/0xfbef5
[2.329016]  ? srso_alias_return_thunk+0x5/0xfbef5
[2.329018]  hci_alloc_dev_priv+0x164e/0x1bc0 [bluetooth]
[2.329023]  process_scheduled_works+0x24b/0x450
[2.329026]  worker_thread+0x2c3/0x420
[2.329028]  ? __pfx_worker_thread+0x10/0x10
[2.329030]  kthread+0xe8/0x110
[2.329032]  ? __pfx_kthread+0x10/0x10
[2.329033]  ret_from_fork+0x37/0x50
[2.329036]  ? __pfx_kthread+0x10/0x10
[2.329038]  ret_from_fork_asm+0x1b/0x30
[2.329043]  
[2.329043] Modules linked in: amdxcp(+) ac97_bus(+) iwlwifi(+) 
snd_hda_codec(+) btusb snd_pcm_dmaengine gpu_sched vfat btbcm snd_pci_ps 
drm_suballoc_helper btintel i2c_algo_bit fat snd_rpl_pci_acp6x kvm(+) 
drm_ttm_helper snd_hda_core snd_acp_pci btrtl ttm snd_acp_legacy_common btmtk 
snd_pci_acp6x irqbypass drm_exec snd_hwdep snd_pci_acp5x snd_pcm 
drm_display_helper bluetooth snd_rn_pci_acp3x wmi_bmof cfg80211 snd_timer 
snd_acp_config rapl cec snd_soc_acpi snd pcspkr drm_buddy soundcore i2c_piix4 
k10temp snd_pci_acp3x rfkill amd_pmc fuse loop nfnetlink crct10dif_pclmul 
crc32_pclmul crc32c_intel nvme polyval_clmulni polyval_generic 
ghash_clmulni_intel thunderbolt sha512_ssse3 sha256_ssse3 sha1_ssse3 nvme_core 
amd_sfh ccp sp5100_tco r8169 nvme_auth realtek video wmi i2c_hid_acpi i2c_hid 
serio_raw
[2.329083] CR2: 0070
[2.329085] ---[ end trace  ]---
[2.329087] RIP: 0010:btintel_configure_setup+0x245/0x970 [btintel]
[2.329089] Code: 85 ff 75 a1 f0 41 80 8e 51 06 00 00 02 f0 41 80 8e 51 06 
00 00 04 f0 41 80 8e 51 06 00 00 08 49 c7 86 38 17 00 00 b0 63 66 c1 <83> 7b 70 
0a 75 7b 48 8b 83 d0 00 00 00 80 78 01 37 75 6e 0f 1f 44
[2.329090] RSP: 0018:a215005cfd48 EFLAGS: 00010202
[2.329091] RAX:  RBX:  RCX: 8026
[2.329092] RDX: 8027 RSI: d3238404d700 RDI: 
[2.329093] RBP: 91a940ccc6c8 R08: 8027 R09: 8026
[2.329093] R10: 0001 R11:  R12: 91a940ccc6d0
[2.329094] R13: 91a947f50c00 R14: 91a940ccc000 R15: 91a940ccca88
[2.329095] FS:  () GS:91af820c() 
knlGS:
[2.329096] CS:  0010 DS:  ES:  CR0: 80050033
[2.329096] CR2: 0070 CR3: 00010dfa2000 CR4: 00f50ef0
[2.329097] PKRU: 5554
[2.329098] note: kworker/u33:0[185] exited with irqs disabled

-- 
You received this bug notification because you are a member of 

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Robert Malz]

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux

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

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 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: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-22 (24 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy 

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Robert Malz]

LP update:

Mantic update:
Due to lack of reproduction environment I have been performing following 
regression test:
1. Setup:
   nic: 2port E810-C
both interfaces set up in bonding
   kernel: 6.5.0-25-generic
2. Test cases:
   0) verified that code from the change is used during driver init
   a) stress traffic for 12h (multiple streams of iperf (tcp))
   b) if up/down during stress traffic
   c) reload driver during stress traffic
Look for any issues related to traffic processing, look for tx_hangs
3. Result: No issues have been detected during test execution

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

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Robert Malz]

Hi Roxana,
Mantic verification is still not finished.
I did some touch tests without stress traffic.
I'm trying to get my hands on E810 device to finish testing, I'll update ticket 
once it's done.
Wishful ETA EOW 09.

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

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 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: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Robert Malz]

Jammy update:
Due to lack of reproduction environment I have been performing following 
regression test:
1. Setup:
   nic: 2port E810-XXV
both interfaces set up in bonding 
   kernel: 5.15.0-100-generic
2. Test cases:
   0) verified that code from the change is used during driver init
   a) stress traffic for 48h (multiple streams of iperf (tcp))
   b) if up/down during stress traffic
   c) pf reset during stress traffic
Look for any issues related to traffic processing, look for tx_hangs
3. Result: No issues have been detected during test execution

Mantic tests in progress.

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

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Robert Malz]

Switching status for Noble to In Progress.
Target release for Noble is 6.8 (which includes fix) but it's not out yet, 
status will be changed once 6.8 will be introduced.

** Changed in: linux (Ubuntu Noble)
   Status: Invalid => In Progress

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

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 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: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Robert Malz]

Fix already included in 6.8

** Changed in: linux (Ubuntu Noble)
   Status: In Progress => 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/2036239

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  Invalid

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 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: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-22 (24 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy 

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Robert Malz]

Hey Christian, Intel proposed change [1]
which is targeting this problem and based on our testing in fact it solves the 
problem.
This change is currently added to Ubuntu Kernels.

I'm also keeping an eye on [2] but right now I don't yet see "business need" to 
incorporate it to Ubuntu Kernel.
This patch furthers limit problematic part of the code by adding (in addition 
to NVM caps check) verification based on DDP package.

1 - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
2 - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20240122/039100.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/2036239

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Robert Malz]

Hey @Christian,
1a) No need, AQ 0x000A returns NVM capabilities regardless of configuration 
applied (it's done during driver init)
1b) That's the point, I noticed you upgraded to 4.3 which I currently don't 
have access to and I wanted to verify capabilities on 4.3. NVM caps should be 
similar on the same NVM version in single head of family so values I had access 
to would be the same you had on 4.2 (meaning there is no point of collecting 
these)
1c) No, any "recent" kernel/driver version will support enabling debug logs by 
adding dyndbg=+p param to module. We only care for logs which are retrieved 
from NVM and printed with debug flags.

2) The issue based on recent patches from Intel is caused by performing LAG 
related operations without proper support from NVM. Release notes does not 
always tell every feature change so there is a possibility that 4.4 introduced 
sriov_lag capability but I cannot verify it.
Worst case scenario is that NVM 4.4 will introduce sriov_lag capability, 
meaning patches added recently to upstream kernel will have no effect, and also 
issue will still reproduce. In this scenario currently there will be no 
'workaround' for it.
Best case scenario is that NVM 4.4 will introduce sriov_lag capability and 
issue will no longer reproduce.
In this scenario no additional patches to the driver will be required.

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

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything 

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Robert Malz]

@Christian,
Can you verify your device capabilities returned from 0x000A looking for SRIOV 
lag?
I have attached a script "parse_aq_0xA.py" you need to load driver with 
dyndbg=+p and replace a buffer in script.
Note: buffer has to come from CQ CMD: opcode 0x000A
Expected result:
(...)
resp cap: 0x92 -- this capability we are looking for
resp maj_ver: 0x1
resp min_ver: 0x0
resp number: 0x1   -- This is value we want to check.
resp logical_id: 0x0
resp phys_id: 0x0

If it is set to 0x1 patch [1] will disable lag handler and simplify 
initialization logic to something like in comment #40
Buffer available in the script comes from CVL4.20 NVM

[1] - https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-
Mon-20231211/038588.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/2036239

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Robert Malz]

Script to verify AQ 0x000A capabilities

** Attachment added: "parse_aq_0xA.py"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/+attachment/5736421/+files/parse_aq_0xA.py

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

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 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: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-22 (24 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  IwConfig: Error: [Errno 2] No such file or 

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Robert Malz]

** Description changed:

+ [Impact]
+  * Issue is causing transmit hang on E810 ports with bonding enabled.
+  * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
+  * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
+ 
+ [Fix]
+ * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
+   This change has been tested in an environment where reproduction is 
easily achieved.
+   After multiple iterations, no reproduction has been observed.
+ * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
+ 
+ [Test Plan]
+ * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
+ * The issue could appear on a random node, making reproduction hard to 
achieve.
+ * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
+ 
+ [Where problems could occur]
+ * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
+ * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
+   Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.
+   
+ [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
+ [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6
  
- I'm having issues with an Intel E810-XXV card on a Dell server under Ubuntu 
Jammy.
+ [Other Info]
+ * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
+ * Original description of the case below:
+ 
+ 
+ 
+ I'm having issues with an Intel E810-XXV card on a Dell server under
+ Ubuntu Jammy.
  
  Details:
  
  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)
  
  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.
  
  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as the
  problem seems to be in the interface.
  
  - machine installed by maas. No issues during installation, but at that
  time bond is not formed yet, later when linux is booted, the bond is
  formed and works without issues for a while
  
  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered by
  some tests that I run after openstack finishes installing)
  
  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet
  
  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace
  
  - the switch does log that the bond is flapping
- --- 
+ ---
  ProblemType: Bug
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
-  crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
+  crw-rw 1 root audio 116, 33 Sep 12 20:05 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: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-22 (24 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7515
  Package: linux (not installed)
  PciMultimedia:
-  
+ 
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 

Re: [Kernel-packages] [Bug 2039589] Re: Nwidia driver Ubuntu bug

[Robert Polak]

The content of the "Help" application is not displayed. The main 
"Firewall Configuration" (UFW) panel is not fully displayed. Screenshots 
are attached. Regards :)

W dniu 18.10.2023 o 10:17, Daniel van Vugt pisze:
> Thanks for the bug report. Can you explain in more detail where and 
> when you see the error? ** Package changed: xorg (Ubuntu) => ubuntu ** 
> Changed in: ubuntu Status: New => Incomplete ** Summary changed: - 
> Nwidia driver Ubuntu bug + Nvidia driver Ubuntu bug ** Package 
> changed: ubuntu => nvidia-graphics-drivers-470 (Ubuntu)

** Attachment added: "Help.png"
   https://bugs.launchpad.net/bugs/2039589/+attachment/5710938/+files/Help.png

** Attachment added: "UFW.png"
   https://bugs.launchpad.net/bugs/2039589/+attachment/5710939/+files/UFW.png

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

Title:
  Nvidia driver Ubuntu bug

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete

Bug description:
  Nvidia driver error 470: UFW main window not displayed properly and
  Help not displayed. The issue affects Ubuntu 22.04.3 LTS, Ubuntu 23.10
  and Linux Mint.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.199.02  Thu May 11 
11:46:56 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 18:13:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CardExpert Technology GK107 [GeForce GTX 650] [10b0:0fc6]
  InstallationDate: Installed on 2023-10-16 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=7faab2db-29fa-4024-ae67-d6f019c15904 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-S1
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr10b:bd02/25/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2039231] [NEW] UBSAN: array-index-out-of-bounds in /build/linux-oem-6.5-XiW3QL/linux-oem-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12

[Robert Ross]

Public bug reported:

Dmesg is full of UBSAN errors to do with the mpt3sas driver when
initializing an mpt2sas device.

[5.012673] UBSAN: array-index-out-of-bounds in 
/build/linux-oem-6.5-XiW3QL/linux-oem-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12
[5.014521] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY 
[1]'
[5.015606] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 6.5.0-1004-oem 
#4-Ubuntu
[5.015611] Hardware name: Supermicro C7Q67/C7Q67, BIOS 2.1a 11/10/2015
[5.015613] Call Trace:
[5.015617]  
[5.015621]  dump_stack_lvl+0x48/0x70
[5.015632]  dump_stack+0x10/0x20
[5.015637]  __ubsan_handle_out_of_bounds+0xc6/0x110
[5.015646]  _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas]
[5.015698]  mpt3sas_scsih_event_callback+0x21f/0x630 [mpt3sas]
[5.015735]  _base_async_event.isra.0+0x73/0x190 [mpt3sas]
[5.015769]  _base_process_reply_queue+0x3a0/0x720 [mpt3sas]
[5.015799]  _base_interrupt+0x4e/0x70 [mpt3sas]
[5.015829]  __handle_irq_event_percpu+0x4f/0x1c0
[5.015835]  handle_irq_event+0x39/0x80
[5.015839]  handle_edge_irq+0x8c/0x250
[5.015844]  __common_interrupt+0x56/0x110
[5.015850]  common_interrupt+0x9f/0xb0
[5.015854]  
[5.015856]  
[5.015858]  asm_common_interrupt+0x27/0x40
[5.015865] RIP: 0010:cpuidle_enter_state+0xda/0x720
[5.015872] Code: 25 07 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 
31 ff e8 46 d1 05 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 
0f 88 f7 01 00 00 4d 63 ee 49 83 fd 09 0f 87 19 05 00 00
[5.015876] RSP: 0018:ac24c00bbe18 EFLAGS: 0246
[5.015881] RAX:  RBX: a0abc03beb00 RCX: 
[5.015884] RDX: 0003 RSI:  RDI: 
[5.015886] RBP: ac24c00bbe68 R08:  R09: 
[5.015888] R10:  R11:  R12: b64d1ac0
[5.015890] R13: 0004 R14: 0004 R15: 00012ab445e7
[5.015895]  ? cpuidle_enter_state+0xca/0x720
[5.015901]  ? tick_nohz_stop_tick+0x90/0x210
[5.015908]  cpuidle_enter+0x2e/0x50
[5.015912]  call_cpuidle+0x23/0x60
[5.015918]  cpuidle_idle_call+0x11d/0x190
[5.015922]  do_idle+0x82/0xf0
[5.015926]  cpu_startup_entry+0x1d/0x20
[5.015930]  start_secondary+0x129/0x160
[5.015936]  secondary_startup_64_no_verify+0x17e/0x18b
[5.015944]  
[5.015946] 

[5.017993] mpt2sas_cm0: hba_port entry: fd3a54f4, port: 255 is 
added to hba_port list
[5.018324] 

[5.019566] UBSAN: array-index-out-of-bounds in 
/build/linux-oem-6.5-XiW3QL/linux-oem-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36
[5.021429] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'
[5.022478] CPU: 2 PID: 153 Comm: kworker/u8:7 Not tainted 6.5.0-1004-oem 
#4-Ubuntu
[5.022483] Hardware name: Supermicro C7Q67/C7Q67, BIOS 2.1a 11/10/2015
[5.022486] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas]
[5.022533] Call Trace:
[5.022536]  
[5.022539]  dump_stack_lvl+0x48/0x70
[5.022547]  dump_stack+0x10/0x20
[5.022551]  __ubsan_handle_out_of_bounds+0xc6/0x110
[5.022559]  _scsih_sas_host_add+0x669/0x700 [mpt3sas]
[5.022597]  _mpt3sas_fw_work+0x753/0xbc0 [mpt3sas]
[5.022633]  ? raw_spin_rq_unlock+0x10/0x40
[5.022637]  ? finish_task_switch.isra.0+0x85/0x2a0
[5.022642]  ? __schedule+0x2d4/0x750
[5.022648]  _firmware_event_work+0x16/0x20 [mpt3sas]
[5.022681]  process_one_work+0x240/0x450
[5.022688]  worker_thread+0x50/0x3f0
[5.022693]  ? __pfx_worker_thread+0x10/0x10
[5.022698]  kthread+0xf2/0x120
[5.022704]  ? __pfx_kthread+0x10/0x10
[5.022710]  ret_from_fork+0x47/0x70
[5.022717]  ? __pfx_kthread+0x10/0x10
[5.022722]  ret_from_fork_asm+0x1b/0x30
[5.022728]  
[5.022729] 

[5.025642] mpt2sas_cm0: host_add: handle(0x0001), 
sas_addr(0x500062b0002d0050), phys(8)
[5.025919] 

[5.027158] UBSAN: array-index-out-of-bounds in 
/build/linux-oem-6.5-XiW3QL/linux-oem-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6598:38
[5.029016] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'
[5.030064] CPU: 2 PID: 153 Comm: kworker/u8:7 Not tainted 6.5.0-1004-oem 
#4-Ubuntu
[5.030069] Hardware name: Supermicro C7Q67/C7Q67, BIOS 2.1a 11/10/2015
[5.030071] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas]
[5.030108] Call Trace:
[5.030110]  
[5.030113]  dump_stack_lvl+0x48/0x70
[5.030119]  dump_stack+0x10/0x20
[5.030123]  __ubsan_handle_out_of_bounds+0xc6/0x110

[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!

[Robert Ross]

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

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

Title:
  evict_inodes inode xxx, i_count = 1, was skipped!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  during boot the kernel logs the following messages:

  # dmesg | grep evict_inodes
  [   12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
  [   12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
  [   12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
  [   12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
  [   12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!

  Those messages are not displayed when I boot my system with a mainline Linux 
kernel.
  Moreover, in the mainline Linux source code, I do not find the lines where 
such a message could be printed.

  Therefore, those messages are probably caused by an Ubuntu patch.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   4827 F wireplumber
   /dev/snd/seq:bonnaudl   4808 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 14:39:10 2023
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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


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

[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!

[Robert Ross]

** Also affects: linux-oem-6.5 (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/2037214

Title:
  evict_inodes inode xxx, i_count = 1, was skipped!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  during boot the kernel logs the following messages:

  # dmesg | grep evict_inodes
  [   12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
  [   12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
  [   12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
  [   12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
  [   12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!

  Those messages are not displayed when I boot my system with a mainline Linux 
kernel.
  Moreover, in the mainline Linux source code, I do not find the lines where 
such a message could be printed.

  Therefore, those messages are probably caused by an Ubuntu patch.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   4827 F wireplumber
   /dev/snd/seq:bonnaudl   4808 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 14:39:10 2023
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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


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

[Kernel-packages] [Bug 2037014] [NEW] HDMI audio noisy

[Robert Pearson]

Public bug reported:

After updating to the latest kernel ???-33, and setting the audio
hardware to HDMI, playing any YouTube video is filled with noise.
Rebooting to the previous kernel eliminated the noise.

Please fix what the update broke.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Thu Sep 21 16:33:23 2023
InstallationDate: Installed on 2022-03-05 (565 days ago)
InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: Upgraded to jammy on 2023-01-15 (249 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  HDMI audio noisy

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

Bug description:
  After updating to the latest kernel ???-33, and setting the audio
  hardware to HDMI, playing any YouTube video is filled with noise.
  Rebooting to the previous kernel eliminated the noise.

  Please fix what the update broke.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Thu Sep 21 16:33:23 2023
  InstallationDate: Installed on 2022-03-05 (565 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2023-01-15 (249 days ago)

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


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

[Kernel-packages] [Bug 2036262] [NEW] wrong nvidia configuration: suspend/resume issues

[Robert Haschke]

Public bug reported:

When returning from a suspend/resume cycle on an Optimus laptop
(Intel+NVIDIA GPU), the primary laptop screen stays off. The external
screen works as expected. However, when having disconnected the external
monitor after suspend, the laptop screen is off as well. It is possible
to switch to console and restart lightdm, but that's no solution.

The problem seems to be caused by a misconfiguration of the nvidia 
suspend/resume setup as explained here:
https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150/1

suspend/resume for nvidia is triggered twice:
1. via systemd services: nvidia-[suspend|hibernate|resume].service in 
/usr/lib/systemd/system
2. via /lib/systemd/system-sleep/nvidia

Both paths end up calling /usr/bin/nvidia-sleep.sh.
These files are provided by package nvidia-kernel-common-*.

*Solution*: It was sufficient to delete the latter file: `sudo rm
/lib/systemd/system-sleep/nvidia`

systemd documentation states: "Scripts or binaries dropped in 
/usr/lib/systemd/system-sleep/ are intended for local use only and should be 
considered hacks."
https://www.freedesktop.org/software/systemd/man/systemd-suspend.service.html

The problem exists in Ubuntu Focal and Jammy at least. Probably all
versions of package nvidia-kernel-common are affected. I just
successfully fixed the problem on Jammy with NVIDIA driver version 535.

** Affects: nvidia-graphics-drivers-535 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: nvidia suspend-resume

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

Title:
  wrong nvidia configuration: suspend/resume issues

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New

Bug description:
  When returning from a suspend/resume cycle on an Optimus laptop
  (Intel+NVIDIA GPU), the primary laptop screen stays off. The external
  screen works as expected. However, when having disconnected the
  external monitor after suspend, the laptop screen is off as well. It
  is possible to switch to console and restart lightdm, but that's no
  solution.

  The problem seems to be caused by a misconfiguration of the nvidia 
suspend/resume setup as explained here:
  
https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150/1

  suspend/resume for nvidia is triggered twice:
  1. via systemd services: nvidia-[suspend|hibernate|resume].service in 
/usr/lib/systemd/system
  2. via /lib/systemd/system-sleep/nvidia

  Both paths end up calling /usr/bin/nvidia-sleep.sh.
  These files are provided by package nvidia-kernel-common-*.

  *Solution*: It was sufficient to delete the latter file: `sudo rm
  /lib/systemd/system-sleep/nvidia`

  systemd documentation states: "Scripts or binaries dropped in 
/usr/lib/systemd/system-sleep/ are intended for local use only and should be 
considered hacks."
  https://www.freedesktop.org/software/systemd/man/systemd-suspend.service.html

  The problem exists in Ubuntu Focal and Jammy at least. Probably all
  versions of package nvidia-kernel-common are affected. I just
  successfully fixed the problem on Jammy with NVIDIA driver version
  535.

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


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

[Kernel-packages] [Bug 2025538] Re: Unrequested kernel update

[Olivier Robert]

** Also affects: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unrequested kernel update

Status in linux-signed-nvidia-5.19 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was
  informed that new packages are available and I just hit update. This
  caused my system running 5.15.0-76-generic to be switched to
  5.19.0-1010-nvidia-lowlatency.

  I noted this as I was now running into bugs like
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/2017980

  The update was, as stated in history.log:

  Start-Date: 2023-07-01  00:25:40
  Commandline: packagekit role='update-packages'
  Requested-By: cm (1000)
  Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, 
automatic)
  Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), 
modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2)

  => This simple update was changing my kernel from 5.15 to 5.19 without
  a request from my side

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10
  ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17
  Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Jul  1 21:16:09 2023
  InstallationDate: Installed on 2018-10-10 (1724 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: linux-signed-nvidia-5.19
  UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+subscriptions


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

[Kernel-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)

[Olivier Robert]

** Also affects: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)

Status in linux-meta-nvidia-5.19 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I 
experience that google-chrome crashes.
  It shows

  ```shell
  [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap (core dumped)".
  ```

  To be honest I don't think it has anything to do with google-chrome at all.
  When google-chrome starts it (normally) request the system key-manager 
(KWallet in my case) for access to the users keys before it actually shows 
anything from chrome. Not even that part (the KWallet password box) shows up.

  I can only reproduce this problem with this specific kernel. It should
  be possible to take google-chrome out of the equation by using another
  application that starts by request the desktop key manager for access.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-nvidia-5.19 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92
  Uname: Linux 5.15.0-1023-nvidia x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Apr 28 11:23:23 2023
  InstallationDate: Installed on 2016-01-08 (2666 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: linux-meta-nvidia-5.19
  UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago)

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


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

[Kernel-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)

[Olivier Robert]

The problem seems to come from a wrong suggestion of Nvidia proprietary
driver packages, where Ubuntu logic (likely from the “ubuntu-drivers-
common” package) hints towards drivers that depend on a kernel stack
that’s not installed, which triggers those kernel installations as well,
because dependencies.

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

Title:
  FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)

Status in linux-meta-nvidia-5.19 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I 
experience that google-chrome crashes.
  It shows

  ```shell
  [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap (core dumped)".
  ```

  To be honest I don't think it has anything to do with google-chrome at all.
  When google-chrome starts it (normally) request the system key-manager 
(KWallet in my case) for access to the users keys before it actually shows 
anything from chrome. Not even that part (the KWallet password box) shows up.

  I can only reproduce this problem with this specific kernel. It should
  be possible to take google-chrome out of the equation by using another
  application that starts by request the desktop key manager for access.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-nvidia-5.19 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92
  Uname: Linux 5.15.0-1023-nvidia x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Apr 28 11:23:23 2023
  InstallationDate: Installed on 2016-01-08 (2666 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: linux-meta-nvidia-5.19
  UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago)

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


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

[Kernel-packages] [Bug 2025538] Re: Unrequested kernel update

[Olivier Robert]

Same problem on 23.04 just now, I only had generic kernels installed,
hit update, and find update-manager trying to install lowlatency and
oracle kernels.

The difference is that installation failed for me, and I now have two
half-conf packages :

iF  linux-image-6.2.0-1005-oracle  6.2.0-1005.5 
  amd64Signed kernel image oracle
iF  linux-image-6.2.0-1007-lowlatency  6.2.0-1007.7 
  amd64Signed kernel image lowlatency

Our version numbers are different (22.04/23.04), but it can’t be a
coincidence.

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

Title:
  Unrequested kernel update

Status in linux-signed-nvidia-5.19 package in Ubuntu:
  New

Bug description:
  Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was
  informed that new packages are available and I just hit update. This
  caused my system running 5.15.0-76-generic to be switched to
  5.19.0-1010-nvidia-lowlatency.

  I noted this as I was now running into bugs like
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/2017980

  The update was, as stated in history.log:

  Start-Date: 2023-07-01  00:25:40
  Commandline: packagekit role='update-packages'
  Requested-By: cm (1000)
  Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, 
automatic)
  Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), 
modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2)

  => This simple update was changing my kernel from 5.15 to 5.19 without
  a request from my side

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10
  ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17
  Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Jul  1 21:16:09 2023
  InstallationDate: Installed on 2018-10-10 (1724 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: linux-signed-nvidia-5.19
  UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+subscriptions


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

[Kernel-packages] [Bug 2019444] [NEW] StarFive VisionFive 2 v1.2a board: no networking after ISL

[Robert Lipe]

Public bug reported:

I have a StarFive VisionFive 2 v1.2a board and used the
ubuntu-23.04-preinstalled-server-riscv64+visionfive2.img.xz to install.
I'd noticed the end of the release notes at
https://wiki.ubuntu.com/RISC-V/StarFive%20VisionFive%202 and have
performed those steps.

However, networking does not work. (I'm not alone in this observation;
there's another report of this on the rvspace forum.)

The red light near the power connector is lit. Only the orange light on
the network connector (the one near the edge) is flashing.


Henrick advised 'ip -a' but that's not recognized. In my original message, I 
offered:

$ sudo ip addr
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: end0:  mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether XXX39 brd ff:ff:ff:ff:ff:ff
inet6 XXX39/64 scope link
   valid_lft forever preferred_lft forever
3: end1:  mtu 1500 qdisc mq state DOWN group 
default qlen 1000
link/ether XXX:3a brd ff:ff:ff:ff:ff:ff


root@ubuntu:/etc/netplan# ip -a
Usage: ip [ OPTIONS ] OBJECT { COMMAND | help }
   ip [ -force ] -batch filename
where  OBJECT := { address | addrlabel | amt | fou | help | ila | ioam | l2tp |
   link | macsec | maddress | monitor | mptcp | mroute | mrule |
   neighbor | neighbour | netconf | netns | nexthop | ntable |
   ntbl | route | rule | sr | tap | tcpmetrics |
   token | tunnel | tuntap | vrf | xfrm }
   OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -r[esolve] |
-h[uman-readable] | -iec | -j[son] | -p[retty] |
-f[amily] { inet | inet6 | mpls | bridge | link } |
-4 | -6 | -M | -B | -0 |
-l[oops] { maximum-addr-flush-attempts } | -br[ief] |
-o[neline] | -t[imestamp] | -ts[hort] | -b[atch] [filename] 
|
-rc[vbuf] [size] | -n[etns] name | -N[umeric] | -a[ll] |
-c[olor]}


As advised, USB is not working, so the WiFi card isn't recognized, of course. I 
don't know how a normal person would attach a keyboard if not through a 
USB/Serial bridge as I have, but that's not very satisfactory in X due to the 
absence of things like modifier keys. That's a different problem for now.

I think the rare case here is 1.2a - these earlybird boards must be
uncommon. The list isn't being stormed with reports, so the 1.3 boards
must be succeeding. Reports of this issue on rvspace are getting no
answers.

I've swapped network cabling and am sure the cable works and is plugged
into a functional network.

I've re-installed from media twice. There are no actual prompts to mess
up, so I'm a bit baffled.

I suspect DT isn't identifying the hardware correctly somehow, but I
lack the device tree mojo to stare that down.

Troubleshooting advice welcome.

# lsb_release -rd
No LSB modules are available.
Description:Ubuntu Lunar Lobster (development branch)
Release:23.04

Filing it as a bug and not a support question because a fresh install to 
hardware of a relatively known/limited hardware options like this should result 
in at least minimally working networking. That's just table stakes in modern 
times.
Expected: Glorious networking flowing freely over the wires.
Observed: Not even a DHCP grant requested.

Thank you!

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

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

Title:
  StarFive VisionFive 2 v1.2a board: no networking after ISL

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  I have a StarFive VisionFive 2 v1.2a board and used the
  ubuntu-23.04-preinstalled-server-riscv64+visionfive2.img.xz to
  install. I'd noticed the end of the release notes at
  https://wiki.ubuntu.com/RISC-V/StarFive%20VisionFive%202 and have
  performed those steps.

  However, networking does not work. (I'm not alone in this observation;
  there's another report of this on the rvspace forum.)

  The red light near the power connector is lit. Only the orange light
  on the network connector (the one near the edge) is flashing.

  
  Henrick advised 'ip -a' but that's not recognized. In my original message, I 
offered:

  $ sudo ip addr
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: end0:  mtu 1500 qdisc mq state UP group 
default qlen 1000
  

[Kernel-packages] [Bug 2018624] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess

[Robert Waltz]

Public bug reported:

Bug happened during upgrade from 22.10 in a Parallels VM

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17
Uname: Linux 5.19.0-42-generic aarch64
NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg
ApportVersion: 2.26.1-0ubuntu2
Architecture: arm64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rob1346 F wireplumber
 /dev/snd/seq:rob1340 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Fri May  5 12:22:51 2023
ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-04-14 (21 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release arm64 
(20230414)
IwConfig:
 lono wireless extensions.
 
 enp0s5no wireless extensions.
MachineType: Parallels International GmbH. Parallels ARM Virtual Machine
ProcFB: 0 virtio_gpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=b62973b2-9758-4bc2-a648-a373f0c5b21f ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to lunar on 2023-05-05 (0 days ago)
acpidump:
 
dmi.bios.date: Fri, 10 Feb 2023 10:16:42
dmi.bios.release: 0.1
dmi.bios.vendor: Parallels International GmbH.
dmi.bios.version: 18.2.0 (53488)
dmi.board.asset.tag: None
dmi.board.name: Parallels ARM Virtual Platform
dmi.board.vendor: Parallels ARM Virtual Machine
dmi.board.version: 0.1
dmi.chassis.type: 2
dmi.chassis.vendor: Parallels International GmbH.
dmi.modalias: 
dmi:bvnParallelsInternationalGmbH.:bvr18.2.0(53488):bdFri,10Feb2023101642:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM:
dmi.product.family: Parallels VM
dmi.product.name: Parallels ARM Virtual Machine
dmi.product.sku: Parallels_ARM_VM
dmi.product.version: 0.1
dmi.sys.vendor: Parallels International GmbH.
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


** Tags: apport-package arm64 lunar

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bug happened during upgrade from 22.10 in a Parallels VM

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17
  Uname: Linux 5.19.0-42-generic aarch64
  NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1346 F wireplumber
   /dev/snd/seq:rob1340 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri May  5 12:22:51 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-04-14 (21 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release arm64 
(20230414)
  IwConfig:
   lono wireless extensions.
   
   enp0s5no wireless extensions.
  MachineType: Parallels International GmbH. Parallels ARM Virtual Machine
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=b62973b2-9758-4bc2-a648-a373f0c5b21f ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  

[Kernel-packages] [Bug 2017733] [NEW] package linux-image-5.19.0-38-generic 5.19.0-38.39 failed to install/upgrade: triggers looping, abandoned

[Robert Ressl]

Public bug reported:

Upgrade from Ubuntu 22.04 to 22.10 on iMac 5k 2014

ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-38-generic 5.19.0-38.39
ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.23.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rressl 1577 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
Date: Wed Apr 26 08:40:12 2023
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2023-01-24 (91 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Apple Inc. iMac15,1
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic 
root=UUID=a8712370-b862-47d8-a0eb-7f4b6044877e ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu12.1
SourcePackage: linux
Title: package linux-image-5.19.0-38-generic 5.19.0-38.39 failed to 
install/upgrade: triggers looping, abandoned
UpgradeStatus: Upgraded to kinetic on 2023-04-26 (0 days ago)
dmi.bios.date: 10/27/2021
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 432.60.3.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-FA842E06C61E91C5
dmi.board.vendor: Apple Inc.
dmi.board.version: iMac15,1
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-FA842E06C61E91C5
dmi.modalias: 
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pniMac15,1:pvr1.0:rvnAppleInc.:rnMac-FA842E06C61E91C5:rvriMac15,1:cvnAppleInc.:ct13:cvrMac-FA842E06C61E91C5:skuSystemSKU#:
dmi.product.family: iMac
dmi.product.name: iMac15,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-package kinetic

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

Title:
  package linux-image-5.19.0-38-generic 5.19.0-38.39 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  New

Bug description:
  Upgrade from Ubuntu 22.04 to 22.10 on iMac 5k 2014

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-38-generic 5.19.0-38.39
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rressl 1577 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Apr 26 08:40:12 2023
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2023-01-24 (91 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Apple Inc. iMac15,1
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic 
root=UUID=a8712370-b862-47d8-a0eb-7f4b6044877e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu12.1
  SourcePackage: linux
  Title: package linux-image-5.19.0-38-generic 5.19.0-38.39 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to kinetic on 2023-04-26 (0 days ago)
  dmi.bios.date: 10/27/2021
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 432.60.3.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-FA842E06C61E91C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac15,1
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-FA842E06C61E91C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pniMac15,1:pvr1.0:rvnAppleInc.:rnMac-FA842E06C61E91C5:rvriMac15,1:cvnAppleInc.:ct13:cvrMac-FA842E06C61E91C5:skuSystemSKU#:
  dmi.product.family: iMac
  dmi.product.name: iMac15,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/2017733/+subscriptions


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

[Kernel-packages] [Bug 2016349] Re: Firefox Move tab to 2nd monitor Gnome 44.0-1

[Robert weaver]

apport information

** Tags added: apport-collected lunar

** Description changed:

  When using - firefox - 111.0.1 click on a tab and move it to a 2nd
  monitor , the system freezes and logs you out of ubuntu luna desktop
  
  system -
processor   : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 60
  model name: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
  
  RAM 16 Gig
  
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=23.04
  DISTRIB_CODENAME=lunar
  DISTRIB_DESCRIPTION="Ubuntu Lunar Lobster (development branch)"
  
  
  crash report in .
  /var/crash/_usr_bin_gnome-shell.1000.crash
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 15 00:28:00 2023
  Dependencies:
   accountsservice 22.08.8-1ubuntu7
   acl 2.3.1-3
   adduser 3.129ubuntu1
   adwaita-icon-theme 41.0-1ubuntu1
   alsa-topology-conf 1.2.5.1-2
   alsa-ucm-conf 1.2.6.3-1ubuntu8
   apg 2.2.3.dfsg.1-5build2
   apport 2.26.1-0ubuntu2
   apport-symptoms 0.24
   apt 2.6.0
   apt-utils 2.6.0
   aptdaemon 1.1.1+bzr982-0ubuntu43
   aptdaemon-data 1.1.1+bzr982-0ubuntu43
   aspell 0.60.8-4build1
   aspell-en 2018.04.16-0-1
   at-spi2-common 2.48.0-1
   at-spi2-core 2.48.0-1
   avahi-daemon 0.8-6ubuntu1
   avahi-utils 0.8-6ubuntu1
   base-files 12.3ubuntu1
   base-passwd 3.6.1
   bash 5.2.15-2ubuntu1
   bash-completion 1:2.11-6ubuntu1
  
  /var/log/syslog  ## weyland errors
  2023-04-15T00:28:15.837930+01:00 dsk-nix systemd[1]: Started geoclue.service 
- Location Lookup Service.
  2023-04-15T00:28:15.846216+01:00 dsk-nix 
/usr/libexec/gdm-wayland-session[39331]: dbus-daemon[39331]: [session uid=124 
pid=39331] Activating service name='org.freedesktop.portal.IBus' reques
  ted by ':1.25' (uid=124 pid=39527 comm="ibus-daemon --panel disable")
  2023-04-15T00:28:15.879342+01:00 dsk-nix NetworkManager[1565]:   
[1681514895.8790] agent-manager: 
agent[11da8ca1fedb1e01,:1.312/org.gnome.Shell.NetworkAgent/124]: agent 
registered
  2023-04-15T00:28:15.906745+01:00 dsk-nix 
/usr/libexec/gdm-wayland-session[39331]: dbus-daemon[39331]: [session uid=124 
pid=39331] Successfully activated service 'org.freedesktop.portal.IBus'
  2023-04-15T00:28:15.914814+01:00 dsk-nix dbus-daemon[1466]: [system] 
Successfully activated service 'org.freedesktop.hostname1'
  2023-04-15T00:28:15.915537+01:00 dsk-nix systemd[1]: Started 
systemd-hostnamed.service - Hostname Service.
  2023-04-15T00:28:15.922893+01:00 dsk-nix kernel: [32346.634156] rfkill: input 
handler disabled
  2023-04-15T00:28:15.989652+01:00 dsk-nix dbus-daemon[1466]: [system] 
Activating via systemd: service name='net.reactivated.Fprint' 
unit='fprintd.service' requested by ':1.312' (uid=124 pid=3
  9366 comm="/usr/bin/gnome-shell")
  2023-04-15T00:28:16.020563+01:00 dsk-nix 
/usr/libexec/gdm-wayland-session[39331]: dbus-daemon[39331]: [session uid=124 
pid=39331] Successfully activated service 'org.gnome.Shell.Screencast'
  2023-04-15T00:28:16.048117+01:00 dsk-nix systemd[1]: Starting fprintd.service 
- Fingerprint Authentication Daemon...
  2023-04-15T00:28:16.090413+01:00 dsk-nix gnome-shell[39366]: 
meta_kms_update_set_color_space: assertion 
'meta_kms_connector_is_color_space_supported (connector, color_space)' failed
  2023-04-15T00:28:16.150026+01:00 dsk-nix gnome-shell[39366]: 
meta_kms_update_set_color_space: assertion 
'meta_kms_connector_is_color_space_supported (connector, color_space)' failed
  2023-04-15T00:28:16.166478+01:00 dsk-nix dbus-daemon[1466]: [system] 
Successfully activated service 'net.reactivated.Fprint'
  2023-04-15T00:28:16.166620+01:00 dsk-nix systemd[1]: Started fprintd.service 
- Fingerprint Authentication Daemon.
  2023-04-15T00:28:16.171005+01:00 dsk-nix 
/usr/libexec/gdm-wayland-session[39331]: dbus-daemon[39331]: [session uid=124 
pid=39331] Activating service name='org.gnome.ScreenSaver' requested by
   ':1.26' (uid=124 pid=39579 comm="/usr/libexec/gsd-power")
  2023-04-15T00:28:16.176630+01:00 dsk-nix spice-vdagent[39674]: vdagent virtio 
channel /dev/virtio-ports/com.redhat.spice.0 does not exist, exiting
  2023-04-15T00:28:16.180726+01:00 dsk-nix gnome-session-binary[39336]: 
Entering running state
  2023-04-15T00:28:16.185511+01:00 dsk-nix xbrlapi.desktop[39679]: 
openConnection: connect: No such file or directory
  2023-04-15T00:28:16.185608+01:00 dsk-nix xbrlapi.desktop[39679]: cannot 
connect to braille devices daemon brltty at :0
  2023-04-15T00:28:16.196631+01:00 dsk-nix gnome-shell[39366]: JS ERROR: 
Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No 
devices available#012asyncCallback@resource:
  ///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  2023-04-15T00:28:16.201394+01:00 dsk-nix gsd-media-keys[39538]: Failed to 
grab accelerator for keybinding settings:playback-repeat
  2023-04-15T00:28:16.201525+01:00 dsk-nix gsd-media-keys[39538]: Failed to 
grab accelerator for keybinding settings:hibernate
  

[Kernel-packages] [Bug 2016349] Re: Firefox Move tab to 2nd monitor Gnome 44.0-1

[Robert weaver]

error log uploaded

2023-04-15T00:28:16.664400+01:00 dsk-nix whoopsie-upload-all[39220]: 
INFO:root:Collecting info for /var/crash/_usr_bin_gnome-shell.1000.crash...
2023-04-15T00:28:17.536102+01:00 dsk-nix tracker-miner-fs-3[33418]: OK
2023-04-15T00:28:17.542546+01:00 dsk-nix systemd[2895]: 
tracker-miner-fs-3.service: Consumed 18.653s CPU time.
2023-04-15T00:28:20.456593+01:00 dsk-nix systemd[1]: Started whoopsie.service - 
crash report submission.
2023-04-15T00:28:20.459469+01:00 dsk-nix whoopsie-upload-all[39220]: 
INFO:root:Marking /var/crash/_usr_bin_gnome-shell.1000.crash for whoopsie upload
2023-04-15T00:28:20.462411+01:00 dsk-nix whoopsie-upload-all[39220]: 
INFO:root:Waiting for whoopsie to upload reports (timeout: 20 s)
2023-04-15T00:28:20.462479+01:00 dsk-nix whoopsie-upload-all[39220]: INFO:root: 
 missing (remaining: 20 s): /var/crash/_usr_bin_gnome-shell.1000.uploaded
2023-04-15T00:28:20.466053+01:00 dsk-nix whoopsie[40242]: [00:28:20] Using lock 
path: /var/lock/whoopsie/lock
2023-04-15T00:28:20.467214+01:00 dsk-nix whoopsie[40242]: [00:28:20] Parsing 
/var/crash/_usr_bin_gnome-shell.1000.crash.
2023-04-15T00:28:20.523803+01:00 dsk-nix whoopsie[40242]: [00:28:20] Uploading 
/var/crash/_usr_bin_gnome-shell.1000.crash.
2023-04-15T00:28:21.226942+01:00 dsk-nix whoopsie[40242]: [00:28:21] Sent; 
server replied with: No error

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

Title:
  Firefox Move tab to 2nd monitor Gnome 44.0-1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using - firefox - 111.0.1 click on a tab and move it to a 2nd
  monitor , the system freezes and logs you out of ubuntu luna desktop

  system -
processor   : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 60
  model name: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz

  RAM 16 Gig

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=23.04
  DISTRIB_CODENAME=lunar
  DISTRIB_DESCRIPTION="Ubuntu Lunar Lobster (development branch)"

  
  crash report in .
  /var/crash/_usr_bin_gnome-shell.1000.crash
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 15 00:28:00 2023
  Dependencies:
   accountsservice 22.08.8-1ubuntu7
   acl 2.3.1-3
   adduser 3.129ubuntu1
   adwaita-icon-theme 41.0-1ubuntu1
   alsa-topology-conf 1.2.5.1-2
   alsa-ucm-conf 1.2.6.3-1ubuntu8
   apg 2.2.3.dfsg.1-5build2
   apport 2.26.1-0ubuntu2
   apport-symptoms 0.24
   apt 2.6.0
   apt-utils 2.6.0
   aptdaemon 1.1.1+bzr982-0ubuntu43
   aptdaemon-data 1.1.1+bzr982-0ubuntu43
   aspell 0.60.8-4build1
   aspell-en 2018.04.16-0-1
   at-spi2-common 2.48.0-1
   at-spi2-core 2.48.0-1
   avahi-daemon 0.8-6ubuntu1
   avahi-utils 0.8-6ubuntu1
   base-files 12.3ubuntu1
   base-passwd 3.6.1
   bash 5.2.15-2ubuntu1
   bash-completion 1:2.11-6ubuntu1

  /var/log/syslog  ## weyland errors
  2023-04-15T00:28:15.837930+01:00 dsk-nix systemd[1]: Started geoclue.service 
- Location Lookup Service.
  2023-04-15T00:28:15.846216+01:00 dsk-nix 
/usr/libexec/gdm-wayland-session[39331]: dbus-daemon[39331]: [session uid=124 
pid=39331] Activating service name='org.freedesktop.portal.IBus' reques
  ted by ':1.25' (uid=124 pid=39527 comm="ibus-daemon --panel disable")
  2023-04-15T00:28:15.879342+01:00 dsk-nix NetworkManager[1565]:   
[1681514895.8790] agent-manager: 
agent[11da8ca1fedb1e01,:1.312/org.gnome.Shell.NetworkAgent/124]: agent 
registered
  2023-04-15T00:28:15.906745+01:00 dsk-nix 
/usr/libexec/gdm-wayland-session[39331]: dbus-daemon[39331]: [session uid=124 
pid=39331] Successfully activated service 'org.freedesktop.portal.IBus'
  2023-04-15T00:28:15.914814+01:00 dsk-nix dbus-daemon[1466]: [system] 
Successfully activated service 'org.freedesktop.hostname1'
  2023-04-15T00:28:15.915537+01:00 dsk-nix systemd[1]: Started 
systemd-hostnamed.service - Hostname Service.
  2023-04-15T00:28:15.922893+01:00 dsk-nix kernel: [32346.634156] rfkill: input 
handler disabled
  2023-04-15T00:28:15.989652+01:00 dsk-nix dbus-daemon[1466]: [system] 
Activating via systemd: service name='net.reactivated.Fprint' 
unit='fprintd.service' requested by ':1.312' (uid=124 pid=3
  9366 comm="/usr/bin/gnome-shell")
  2023-04-15T00:28:16.020563+01:00 dsk-nix 
/usr/libexec/gdm-wayland-session[39331]: dbus-daemon[39331]: [session uid=124 
pid=39331] Successfully activated service 'org.gnome.Shell.Screencast'
  2023-04-15T00:28:16.048117+01:00 dsk-nix systemd[1]: Starting fprintd.service 
- Fingerprint Authentication Daemon...
  2023-04-15T00:28:16.090413+01:00 dsk-nix gnome-shell[39366]: 
meta_kms_update_set_color_space: assertion 
'meta_kms_connector_is_color_space_supported (connector, color_space)' failed
  2023-04-15T00:28:16.150026+01:00 dsk-nix gnome-shell[39366]: 
meta_kms_update_set_color_space: assertion 
'meta_kms_connector_is_color_space_supported 

[Kernel-packages] [Bug 2016349] [NEW] Firefox Move tab to 2nd monitor Gnome 44.0-1

[Robert weaver]

Public bug reported:

When using - firefox - 111.0.1 click on a tab and move it to a 2nd
monitor , the system freezes and logs you out of ubuntu luna desktop

system -
  processor : 7
vendor_id   : GenuineIntel
cpu family  : 6
model   : 60
model name  : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz

RAM 16 Gig

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=23.04
DISTRIB_CODENAME=lunar
DISTRIB_DESCRIPTION="Ubuntu Lunar Lobster (development branch)"


crash report in .
/var/crash/_usr_bin_gnome-shell.1000.crash
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 15 00:28:00 2023
Dependencies:
 accountsservice 22.08.8-1ubuntu7
 acl 2.3.1-3
 adduser 3.129ubuntu1
 adwaita-icon-theme 41.0-1ubuntu1
 alsa-topology-conf 1.2.5.1-2
 alsa-ucm-conf 1.2.6.3-1ubuntu8
 apg 2.2.3.dfsg.1-5build2
 apport 2.26.1-0ubuntu2
 apport-symptoms 0.24
 apt 2.6.0
 apt-utils 2.6.0
 aptdaemon 1.1.1+bzr982-0ubuntu43
 aptdaemon-data 1.1.1+bzr982-0ubuntu43
 aspell 0.60.8-4build1
 aspell-en 2018.04.16-0-1
 at-spi2-common 2.48.0-1
 at-spi2-core 2.48.0-1
 avahi-daemon 0.8-6ubuntu1
 avahi-utils 0.8-6ubuntu1
 base-files 12.3ubuntu1
 base-passwd 3.6.1
 bash 5.2.15-2ubuntu1
 bash-completion 1:2.11-6ubuntu1

/var/log/syslog  ## weyland errors
2023-04-15T00:28:15.837930+01:00 dsk-nix systemd[1]: Started geoclue.service - 
Location Lookup Service.
2023-04-15T00:28:15.846216+01:00 dsk-nix 
/usr/libexec/gdm-wayland-session[39331]: dbus-daemon[39331]: [session uid=124 
pid=39331] Activating service name='org.freedesktop.portal.IBus' reques
ted by ':1.25' (uid=124 pid=39527 comm="ibus-daemon --panel disable")
2023-04-15T00:28:15.879342+01:00 dsk-nix NetworkManager[1565]:   
[1681514895.8790] agent-manager: 
agent[11da8ca1fedb1e01,:1.312/org.gnome.Shell.NetworkAgent/124]: agent 
registered
2023-04-15T00:28:15.906745+01:00 dsk-nix 
/usr/libexec/gdm-wayland-session[39331]: dbus-daemon[39331]: [session uid=124 
pid=39331] Successfully activated service 'org.freedesktop.portal.IBus'
2023-04-15T00:28:15.914814+01:00 dsk-nix dbus-daemon[1466]: [system] 
Successfully activated service 'org.freedesktop.hostname1'
2023-04-15T00:28:15.915537+01:00 dsk-nix systemd[1]: Started 
systemd-hostnamed.service - Hostname Service.
2023-04-15T00:28:15.922893+01:00 dsk-nix kernel: [32346.634156] rfkill: input 
handler disabled
2023-04-15T00:28:15.989652+01:00 dsk-nix dbus-daemon[1466]: [system] Activating 
via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' 
requested by ':1.312' (uid=124 pid=3
9366 comm="/usr/bin/gnome-shell")
2023-04-15T00:28:16.020563+01:00 dsk-nix 
/usr/libexec/gdm-wayland-session[39331]: dbus-daemon[39331]: [session uid=124 
pid=39331] Successfully activated service 'org.gnome.Shell.Screencast'
2023-04-15T00:28:16.048117+01:00 dsk-nix systemd[1]: Starting fprintd.service - 
Fingerprint Authentication Daemon...
2023-04-15T00:28:16.090413+01:00 dsk-nix gnome-shell[39366]: 
meta_kms_update_set_color_space: assertion 
'meta_kms_connector_is_color_space_supported (connector, color_space)' failed
2023-04-15T00:28:16.150026+01:00 dsk-nix gnome-shell[39366]: 
meta_kms_update_set_color_space: assertion 
'meta_kms_connector_is_color_space_supported (connector, color_space)' failed
2023-04-15T00:28:16.166478+01:00 dsk-nix dbus-daemon[1466]: [system] 
Successfully activated service 'net.reactivated.Fprint'
2023-04-15T00:28:16.166620+01:00 dsk-nix systemd[1]: Started fprintd.service - 
Fingerprint Authentication Daemon.
2023-04-15T00:28:16.171005+01:00 dsk-nix 
/usr/libexec/gdm-wayland-session[39331]: dbus-daemon[39331]: [session uid=124 
pid=39331] Activating service name='org.gnome.ScreenSaver' requested by
 ':1.26' (uid=124 pid=39579 comm="/usr/libexec/gsd-power")
2023-04-15T00:28:16.176630+01:00 dsk-nix spice-vdagent[39674]: vdagent virtio 
channel /dev/virtio-ports/com.redhat.spice.0 does not exist, exiting
2023-04-15T00:28:16.180726+01:00 dsk-nix gnome-session-binary[39336]: Entering 
running state
2023-04-15T00:28:16.185511+01:00 dsk-nix xbrlapi.desktop[39679]: 
openConnection: connect: No such file or directory
2023-04-15T00:28:16.185608+01:00 dsk-nix xbrlapi.desktop[39679]: cannot connect 
to braille devices daemon brltty at :0
2023-04-15T00:28:16.196631+01:00 dsk-nix gnome-shell[39366]: JS ERROR: 
Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No 
devices available#012asyncCallback@resource:
///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
2023-04-15T00:28:16.201394+01:00 dsk-nix gsd-media-keys[39538]: Failed to grab 
accelerator for keybinding settings:playback-repeat
2023-04-15T00:28:16.201525+01:00 dsk-nix gsd-media-keys[39538]: Failed to grab 
accelerator for keybinding settings:hibernate
2023-04-15T00:28:16.211498+01:00 dsk-nix org.gnome.Shell.desktop[39695]: The 
XKEYBOARD keymap compiler (xkbcomp) reports:
2023-04-15T00:28:16.211572+01:00 dsk-nix org.gnome.Shell.desktop[39695]: > 
Warning:  

[Kernel-packages] [Bug 2015165] Re: Update to 22.04 deletes HDMI audio

[Robert Pearson]

The 5.19.0.-32-generic kernel does have working HDMI audio.

My thanks for telling me how to use an older (not broken) kernel.

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

Title:
  Update to 22.04 deletes HDMI audio

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

Bug description:
  The latest update 5.19.0.-38-generic does include the HDMI audio
  output. The only problem is that the audio still does not work.

  I will try rebooting with an earlier kernel.

  Keep trying.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Mon Apr  3 20:41:56 2023
  InstallationDate: Installed on 2022-03-05 (394 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: Upgraded to jammy on 2023-01-15 (78 days ago)

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


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

[Kernel-packages] [Bug 2015165] [NEW] Update to 22.04 deletes HDMI audio

[Robert Pearson]

Public bug reported:

The latest update 5.19.0.-38-generic does include the HDMI audio output.
The only problem is that the audio still does not work.

I will try rebooting with an earlier kernel.

Keep trying.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Mon Apr  3 20:41:56 2023
InstallationDate: Installed on 2022-03-05 (394 days ago)
InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
SourcePackage: linux-signed-hwe-5.19
UpgradeStatus: Upgraded to jammy on 2023-01-15 (78 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Update to 22.04 deletes HDMI audio

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

Bug description:
  The latest update 5.19.0.-38-generic does include the HDMI audio
  output. The only problem is that the audio still does not work.

  I will try rebooting with an earlier kernel.

  Keep trying.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Mon Apr  3 20:41:56 2023
  InstallationDate: Installed on 2022-03-05 (394 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: Upgraded to jammy on 2023-01-15 (78 days ago)

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


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

[Kernel-packages] [Bug 1966159] Re: package linux-libc-dev 5.4.0-105.119 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted

[Robert weaver]

** Changed in: linux (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/1966159

Title:
  package linux-libc-dev 5.4.0-105.119 failed to install/upgrade: unable
  to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation
  not permitted

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  This makes my laptop very slow.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-libc-dev 5.4.0-105.119
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   linux-libc-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kavindu1601 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue Mar 22 23:39:37 2022
  Dependencies:
   
  DpkgTerminalLog:
   Preparing to unpack .../linux-libc-dev_5.4.0-105.119_amd64.deb ...
   Unpacking linux-libc-dev:amd64 (5.4.0-105.119) over (5.4.0-104.118) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_5.4.0-105.119_amd64.deb (--unpack):
unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': 
Operation not permitted
  DuplicateSignature:
   package:linux-libc-dev:5.4.0-105.119
   Unpacking linux-libc-dev:amd64 (5.4.0-105.119) over (5.4.0-104.118) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_5.4.0-105.119_amd64.deb (--unpack):
unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted
  InstallationDate: Installed on 2021-06-20 (276 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20FBA07Y00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=106efafd-9069-4bf9-b738-813dcacd8be7 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  SourcePackage: linux
  Title: package linux-libc-dev 5.4.0-105.119 failed to install/upgrade: unable 
to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not 
permitted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/08/2017
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET49W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBA07Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET49W(1.23):bd02/08/2017:br1.23:efr1.14:svnLENOVO:pn20FBA07Y00:pvrThinkPadX1Carbon4th:skuLENOVO_MT_20FB_BU_Think_FM_ThinkPadX1Carbon4th:rvnLENOVO:rn20FBA07Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FBA07Y00
  dmi.product.sku: LENOVO_MT_20FB_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1966159] Re: package linux-libc-dev 5.4.0-105.119 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted

[Robert weaver]

fix by setting the following permissions
chmod 0775 /usr/share/doc/linux-libc-dev/copyright.dpkg-new

Then Run 
  sudo apt-get upgrade

sudo apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  librest-1.0-0 linux-headers-generic ubuntu-drivers-common
The following packages will be upgraded:
  linux-libc-dev
1 to upgrade, 0 to newly install, 0 to remove and 3 not to upgrade.
9 not fully installed or removed.
Need to get 0 B/1,370 kB of archives.
After this operation, 5,120 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 391913 files and directories currently installed.)
Preparing to unpack .../linux-libc-dev_5.19.0-38.39_amd64.deb ...
Unpacking linux-libc-dev:amd64 (5.19.0-38.39) over (5.19.0-35.36) ...
Setting up qemu-system-common (1:7.0+dfsg-7ubuntu2.2) ...
Setting up libsnmp-base (5.9.3+dfsg-1ubuntu1.4) ...
Setting up linux-libc-dev:amd64 (5.19.0-38.39) ...
Setting up libsnmp40:amd64 (5.9.3+dfsg-1ubuntu1.4) ...
Setting up qemu-system-data (1:7.0+dfsg-7ubuntu2.2) ...
Setting up printer-driver-splix (2.0.0+svn315-7fakesync1ubuntu0.22.10.1) ...
Setting up qemu-utils (1:7.0+dfsg-7ubuntu2.2) ...
Setting up qemu-block-extra (1:7.0+dfsg-7ubuntu2.2) ...
Setting up qemu-system-x86 (1:7.0+dfsg-7ubuntu2.2) ...
Setting up qemu-system-gui (1:7.0+dfsg-7ubuntu2.2) ...
Processing triggers for man-db (2.10.2-2) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for cups (2.4.2-1ubuntu2) ...
Updating PPD files for splix ...
Processing triggers for libc-bin (2.36-0ubuntu4) ...
rob@dsk-nix:/usr/share/doc/linux-libc-dev$ ls -lsa
total 220
  0 drwxr-xr-x2 root root50 Mar 23 12:45 .
140 drwxr-xr-x 2655 root root 98304 Mar 12 16:05 ..
 76 -rw-r--r--1 root root 75903 Mar 17 17:12 changelog.Debian.gz
  4 -rw-r--r--1 root root  1292 Mar 17 17:12 copyright

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

Title:
  package linux-libc-dev 5.4.0-105.119 failed to install/upgrade: unable
  to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation
  not permitted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This makes my laptop very slow.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-libc-dev 5.4.0-105.119
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   linux-libc-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kavindu1601 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue Mar 22 23:39:37 2022
  Dependencies:
   
  DpkgTerminalLog:
   Preparing to unpack .../linux-libc-dev_5.4.0-105.119_amd64.deb ...
   Unpacking linux-libc-dev:amd64 (5.4.0-105.119) over (5.4.0-104.118) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_5.4.0-105.119_amd64.deb (--unpack):
unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': 
Operation not permitted
  DuplicateSignature:
   package:linux-libc-dev:5.4.0-105.119
   Unpacking linux-libc-dev:amd64 (5.4.0-105.119) over (5.4.0-104.118) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_5.4.0-105.119_amd64.deb (--unpack):
unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted
  InstallationDate: Installed on 2021-06-20 (276 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20FBA07Y00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=106efafd-9069-4bf9-b738-813dcacd8be7 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  SourcePackage: linux
  Title: package linux-libc-dev 5.4.0-105.119 failed to install/upgrade: unable 
to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not 
permitted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/08/2017
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET49W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBA07Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: 

[Kernel-packages] [Bug 1966159] Re: package linux-libc-dev 5.4.0-105.119 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted

[Robert weaver]

Having the same issue .
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.10
DISTRIB_CODENAME=kinetic
DISTRIB_DESCRIPTION="Ubuntu 22.10"

uname -a
Linux dsk-nix 6.1.5 #1 SMP PREEMPT_DYNAMIC Fri Jan 13 18:42:07 GMT 2023 x86_64 
x86_64 x86_64 GNU/Linux

sudo apt-get upgrade
sudo apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  librest-1.0-0 linux-headers-generic ubuntu-drivers-common
The following packages will be upgraded:
  libsnmp-base libsnmp40 linux-libc-dev printer-driver-splix qemu-block-extra 
qemu-system-common qemu-system-data
  qemu-system-gui qemu-system-x86 qemu-utils
10 to upgrade, 0 to newly install, 0 to remove and 3 not to upgrade.
Need to get 18.3 MB of archives.
After this operation, 5,120 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://gb.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 
libsnmp-base all 5.9.3+dfsg-1ubuntu1.4 [201 kB]
Get:2 http://gb.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 libsnmp40 
amd64 5.9.3+dfsg-1ubuntu1.4 [1,061 kB]
Get:3 http://gb.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 
linux-libc-dev amd64 5.19.0-38.39 [1,370 kB]
Get:4 http://gb.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 
printer-driver-splix amd64 2.0.0+svn315-7fakesync1ubuntu0.22.10.1 [38.8 kB]
Get:5 http://gb.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 
qemu-system-gui amd64 1:7.0+dfsg-7ubuntu2.2 [217 kB]
Get:6 http://gb.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 
qemu-block-extra amd64 1:7.0+dfsg-7ubuntu2.2 [67.3 kB]
Get:7 http://gb.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 
qemu-system-x86 amd64 1:7.0+dfsg-7ubuntu2.2 [10.3 MB]
Get:8 http://gb.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 
qemu-system-data all 1:7.0+dfsg-7ubuntu2.2 [1,431 kB]
Get:9 http://gb.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 
qemu-system-common amd64 1:7.0+dfsg-7ubuntu2.2 [2,122 kB]
Get:10 http://gb.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 
qemu-utils amd64 1:7.0+dfsg-7ubuntu2.2 [1,486 kB]
Fetched 18.3 MB in 1s (13.8 MB/s)
(Reading database ... 391913 files and directories currently installed.)
Preparing to unpack .../0-libsnmp-base_5.9.3+dfsg-1ubuntu1.4_all.deb ...
Unpacking libsnmp-base (5.9.3+dfsg-1ubuntu1.4) over (5.9.3+dfsg-1ubuntu1.3) ...
Preparing to unpack .../1-libsnmp40_5.9.3+dfsg-1ubuntu1.4_amd64.deb ...
Unpacking libsnmp40:amd64 (5.9.3+dfsg-1ubuntu1.4) over (5.9.3+dfsg-1ubuntu1.3) 
...
Preparing to unpack .../2-linux-libc-dev_5.19.0-38.39_amd64.deb ...
Unpacking linux-libc-dev:amd64 (5.19.0-38.39) over (5.19.0-35.36) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-U8Cyyl/2-linux-libc-dev_5.19.0-38.39_amd64.deb (--unpack):
 unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation 
not permitted
Preparing to unpack 
.../3-printer-driver-splix_2.0.0+svn315-7fakesync1ubuntu0.22.10.1_amd64.deb ...
Unpacking printer-driver-splix (2.0.0+svn315-7fakesync1ubuntu0.22.10.1) over 
(2.0.0+svn315-7fakesync1build3) ...
Preparing to unpack .../4-qemu-system-gui_1%3a7.0+dfsg-7ubuntu2.2_amd64.deb ...
Unpacking qemu-system-gui (1:7.0+dfsg-7ubuntu2.2) over (1:7.0+dfsg-7ubuntu2.1) 
...
Preparing to unpack .../5-qemu-block-extra_1%3a7.0+dfsg-7ubuntu2.2_amd64.deb ...
Unpacking qemu-block-extra (1:7.0+dfsg-7ubuntu2.2) over (1:7.0+dfsg-7ubuntu2.1) 
...
Preparing to unpack .../6-qemu-system-x86_1%3a7.0+dfsg-7ubuntu2.2_amd64.deb ...
Unpacking qemu-system-x86 (1:7.0+dfsg-7ubuntu2.2) over (1:7.0+dfsg-7ubuntu2.1) 
...
Preparing to unpack .../7-qemu-system-data_1%3a7.0+dfsg-7ubuntu2.2_all.deb ...
Unpacking qemu-system-data (1:7.0+dfsg-7ubuntu2.2) over (1:7.0+dfsg-7ubuntu2.1) 
...
Preparing to unpack .../8-qemu-system-common_1%3a7.0+dfsg-7ubuntu2.2_amd64.deb 
...
Unpacking qemu-system-common (1:7.0+dfsg-7ubuntu2.2) over 
(1:7.0+dfsg-7ubuntu2.1) ...
Preparing to unpack .../9-qemu-utils_1%3a7.0+dfsg-7ubuntu2.2_amd64.deb ...
Unpacking qemu-utils (1:7.0+dfsg-7ubuntu2.2) over (1:7.0+dfsg-7ubuntu2.1) ...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-U8Cyyl/2-linux-libc-dev_5.19.0-38.39_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package linux-libc-dev 5.4.0-105.119 failed to install/upgrade: unable
  to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation
  not permitted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This makes my laptop very slow.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-libc-dev 5.4.0-105.119
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   linux-libc-dev:amd64: 

[Kernel-packages] [Bug 2007994] Re: Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering

[Robert Šámal]

I am affected by this as well -- Lenovo X1 Yoga gen. 6, 
Ubuntu 22.04.2, kernel 5.19.0-35-generic.

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

Title:
  Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen
  Flickering

Status in linux-signed-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  Affected machine: Lenovo ThinkPad X13 Yoga Gen 2
  OS: Ubuntu 22.04.2 LTS (64-bit)

  I did a dist-upgrade on Feb. 16th, and every boot after that results
  in screen flickering, I checked the dpkg history and assume that the
  kernel upgrade(5.19.0.32.33~22.04.9) is the one to blame. Then I tried
  to boot the machine with the former kernel(5.15.0.25.27), everything
  works fine again which confirms my assumption.

  The following line repeated to show up before entering the desktop:
  blacklist: Problem blacklisting hash (-13)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity
  Date: Wed Feb 22 00:11:10 2023
  InstallationDate: Installed on 2022-08-29 (176 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2003004] Re: Cannot write X config due to missing u+x permissions on nvidia-polkit

[Robert Hardy]

** Also affects: nvidia-drivers-ubuntu
   Importance: Undecided
   Status: New

** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

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

Title:
  Cannot write X config due to missing u+x permissions on nvidia-polkit

Status in One Hundred Papercuts:
  New
Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  Despite being this similar to an old bug 1625119, which was on a now
  unsupported release, I asked on #ubuntu whether I should go for a new
  bug and was directed to file this as a new bug.

  I have an Asus NVidia RTX 3060. I am running:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  a supported release, and found a solution on that release.

  I am using a fully patched system with nvidia-settings
  510.47.03-0ubuntu1.

  I expected, when running nvidia-settings as root, when I clicked on
  the button to write out the settings I just configured to
  /etc/X11/xorg.conf for that to work. It does not with permission
  denied.

  The tools needs to be able to write /etc/X11/xorg.conf when root
  requests it.

  I tracked this down to a missing permission on /usr/share/screen-
  resolution-extra/nvidia-polkit which had permissions 644 on my system.

  The following change fixed this for me: chmod u+x 
/usr/share/screen-resolution-extra/nvidia-polkit
  I found many users online with similar issues in forums.

  Please update the package to implement the equivalent and close this.

  FYI end user configuration without root has improved significantly
  since 16.04 such that it would be reasonable in my honest opinion to
  also close 1625119 as fixed in 22.04 once this is done. It is fixed as
  well as security allows. It is reasonable from my point of view for
  security reasons to need root to change such a critical file as
  /etc/X11/xorg.conf.

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


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

[Kernel-packages] [Bug 2003004] [NEW] Cannot write X config due to missing u+x permissions on nvidia-polkit

[Robert Hardy]

Public bug reported:

Despite being this similar to an old bug 1625119, which was on a now
unsupported release, I asked on #ubuntu whether I should go for a new
bug and was directed to file this as a new bug.

I have an Asus NVidia RTX 3060. I am running:
Description:Ubuntu 22.04.1 LTS
Release:22.04

a supported release, and found a solution on that release.

I am using a fully patched system with nvidia-settings
510.47.03-0ubuntu1.

I expected, when running nvidia-settings as root, when I clicked on the
button to write out the settings I just configured to /etc/X11/xorg.conf
for that to work. It does not with permission denied.

The tools needs to be able to write /etc/X11/xorg.conf when root
requests it.

I tracked this down to a missing permission on /usr/share/screen-
resolution-extra/nvidia-polkit which had permissions 644 on my system.

The following change fixed this for me: chmod u+x 
/usr/share/screen-resolution-extra/nvidia-polkit
I found many users online with similar issues in forums.

Please update the package to implement the equivalent and close this.

FYI end user configuration without root has improved significantly since
16.04 such that it would be reasonable in my honest opinion to also
close 1625119 as fixed in 22.04 once this is done. It is fixed as well
as security allows. It is reasonable from my point of view for security
reasons to need root to change such a critical file as
/etc/X11/xorg.conf.

** Affects: nvidia-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

- Despite this similar to an old bug 1625119 I asked on #ubuntu whether I
- should go for a new bug and was directed to file this as a new bug.
+ Despite being this similar to an old bug 1625119, which was on a now
+ unsupported release, I asked on #ubuntu whether I should go for a new
+ bug and was directed to file this as a new bug.
  
  I have an Asus NVidia RTX 3060. I am running:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  
  a supported release, and found a solution on that release.
  
  I am using a fully patched system with nvidia-settings
  510.47.03-0ubuntu1.
  
  I expected, when running as root, when I clicked on the button to write
  out the settings I just configured in nvidia-settings to
  /etc/X11/xorg.conf for that to work. It does not with permission denied.
  
  It needs to be able to write /etc/X11/xorg.conf when running as root when the 
user requests it.
  Attempting to run nvidia-settings as root it cannot write to that 
configuration file.
  
  I tracked this down to a missing permission on /usr/share/screen-
  resolution-extra/nvidia-polkit which was 644 on my system.
  
  The following change fixed this for me: chmod u+x 
/usr/share/screen-resolution-extra/nvidia-polkit
  I found many users online with similar issues in forums.
  
  Please update the package to implement the equivalent and close this.
  
  FYI end user configuration without root has improved significantly since
  16.04 such that it would be reasonable in my honest opinion to close
  1625119 as fixed in 22.04 once this is done. It is also reasonable from
  my point of view for security reasons to need root to change such a
  critical file as /etc/X11/xorg.conf.

** Description changed:

  Despite being this similar to an old bug 1625119, which was on a now
  unsupported release, I asked on #ubuntu whether I should go for a new
  bug and was directed to file this as a new bug.
  
  I have an Asus NVidia RTX 3060. I am running:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  
  a supported release, and found a solution on that release.
  
  I am using a fully patched system with nvidia-settings
  510.47.03-0ubuntu1.
  
- I expected, when running as root, when I clicked on the button to write
- out the settings I just configured in nvidia-settings to
- /etc/X11/xorg.conf for that to work. It does not with permission denied.
+ I expected, when running nvidia-settings as root, when I clicked on the
+ button to write out the settings I just configured to /etc/X11/xorg.conf
+ for that to work. It does not with permission denied.
  
- It needs to be able to write /etc/X11/xorg.conf when running as root when the 
user requests it.
- Attempting to run nvidia-settings as root it cannot write to that 
configuration file.
+ The tools needs to be able to write /etc/X11/xorg.conf when root
+ requests it.
  
  I tracked this down to a missing permission on /usr/share/screen-
- resolution-extra/nvidia-polkit which was 644 on my system.
+ resolution-extra/nvidia-polkit which had permissions 644 on my system.
  
  The following change fixed this for me: chmod u+x 
/usr/share/screen-resolution-extra/nvidia-polkit
  I found many users online with similar issues in forums.
  
  Please update the package to implement the equivalent and close this.
  
  FYI end user configuration without root has improved significantly since
- 16.04 such that it would be reasonable in my 

[Kernel-packages] [Bug 1625119] Re: Nvidia settings can't be saved

[Robert Hardy]

16.04 is old at this point. I had a similar problem with Ubuntu 22.04, which 
should be currently supported, and found a solution on that release. I am using 
a fully patched system with nvidia-settings 510.47.03-0ubuntu1. It needs to be 
able to write /etc/X11/xorg.conf when running as root when the user requests 
it. Attempting to run nvidia-settings as root it cannot write to that 
configuration file. The following change fixed this for me: chmod u+x 
/usr/share/screen-resolution-extra/nvidia-polkit
Please update the package to implement the equivalent and close this.

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

Title:
  Nvidia settings can't be saved

Status in nvidia-settings package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 suggest proprietary Nvidia drivers when a Nvidia GPU is
  present. The settings in the nvidia-settings tool cannot be saved,
  however, without starting the tool as root and doing all kinds of
  workarounds which is impossible to do for the average user.

  Do you really expect users to reconfigure their displays after every
  login?

  Unless you can fix this, the Nvidia driver recommendation should
  simply be removed. Delivering such a horrible experience to millions
  of users seems like a bad joke and the persons responsible should feel
  really bad about this.

  Ubuntu has no future anywhere with such usability issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1625119/+subscriptions


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

[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync

[Robert Lippmann]

Turns out my issue was a faulty drive, and the system would lock up when
mdadm hit the bad sectors on resync. The issue seemed like it was lower
in the blockdev code causing a deadlock.

I replaced the drive and the problem went away.

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

Title:
  kernel io hangs during mdcheck/resync

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.11 package in Ubuntu:
  Confirmed

Bug description:
  It seems to always occur during an mdcheck/resync, if I am logged in
  via SSH it is still somewhat responsive and basic utilities like dmesg
  will work.  But it apppears any write I/O will hang the terminal and
  nothing is written to syslog (presumably because it is blocked).

  Below is output of dmesg and cat /proc/mdstat, it appears the data
  check was interrupted and /proc/mdstat still shows progress, and a
  whole slew of hung tasks including md1_resync itself.

  [756484.534293] md: data-check of RAID array md0
  [756484.628039] md: delaying data-check of md1 until md0 has finished (they 
share one or more physical units)
  [756493.808773] md: md0: data-check done.
  [756493.829760] md: data-check of RAID array md1
  [778112.446410] md: md1: data-check interrupted.
  [810654.608102] md: data-check of RAID array md1
  [832291.201064] md: md1: data-check interrupted.
  [899745.389485] md: data-check of RAID array md1
  [921395.835305] md: md1: data-check interrupted.
  [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 
seconds.
  [921588.558846]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.558854] task:systemd-journal state:D stack:0 pid:  376 ppid: 
1 flags:0x0220
  [921588.558859] Call Trace:
  [921588.558864]  __schedule+0x44c/0x8a0
  [921588.558872]  schedule+0x4f/0xc0
  [921588.558876]  md_write_start+0x150/0x240
  [921588.558880]  ? wait_woken+0x80/0x80
  [921588.558886]  raid5_make_request+0x88/0x890 [raid456]
  [921588.558898]  ? wait_woken+0x80/0x80
  [921588.558901]  ? mempool_kmalloc+0x17/0x20
  [921588.558904]  md_handle_request+0x12d/0x1a0
  [921588.558907]  ? __part_start_io_acct+0x51/0xf0
  [921588.558912]  md_submit_bio+0xca/0x100
  [921588.558915]  submit_bio_noacct+0x112/0x4f0
  [921588.558918]  ? ext4_fc_reserve_space+0x110/0x230
  [921588.558922]  submit_bio+0x51/0x1a0
  [921588.558925]  ? _cond_resched+0x19/0x30
  [921588.558928]  ? kmem_cache_alloc+0x38e/0x440
  [921588.558932]  ? ext4_init_io_end+0x1f/0x50
  [921588.558936]  ext4_io_submit+0x4d/0x60
  [921588.558940]  ext4_writepages+0x2c6/0xcd0
  [921588.558944]  do_writepages+0x43/0xd0
  [921588.558948]  ? do_writepages+0x43/0xd0
  [921588.558951]  ? fault_dirty_shared_page+0xa5/0x110
  [921588.558955]  __filemap_fdatawrite_range+0xcc/0x110
  [921588.558960]  file_write_and_wait_range+0x74/0xc0
  [921588.558962]  ext4_sync_file+0xf5/0x350
  [921588.558967]  vfs_fsync_range+0x49/0x80
  [921588.558970]  do_fsync+0x3d/0x70
  [921588.558973]  __x64_sys_fsync+0x14/0x20
  [921588.558976]  do_syscall_64+0x38/0x90
  [921588.558980]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [921588.558984] RIP: 0033:0x7f4c97ee832b
  [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 
004a
  [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 
7f4c97ee832b
  [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 
0021
  [921588.558995] RBP: 0001 R08:  R09: 
7ffdceb29fa8
  [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 
7ffdceb29fa8
  [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 
55ced34bcf90
  [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds.
  [921588.559018]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.559025] task:mysqld  state:D stack:0 pid: 1505 ppid: 
1 flags:0x
  [921588.559030] Call Trace:
  [921588.559032]  __schedule+0x44c/0x8a0
  [921588.559036]  schedule+0x4f/0xc0
  [921588.559040]  md_write_start+0x150/0x240
  [921588.559044]  ? wait_woken+0x80/0x80
  [921588.559047]  raid5_make_request+0x88/0x890 [raid456]
  [921588.559056]  ? wait_woken+0x80/0x80
  [921588.559059]  ? mempool_kmalloc+0x17/0x20
  [921588.559062]  md_handle_request+0x12d/0x1a0
  [921588.559065]  ? __part_start_io_acct+0x51/0xf0
  [921588.559068]  md_submit_bio+0xca/0x100
  [921588.559071]  submit_bio_noacct+0x112/0x4f0
  [921588.559075]  submit_bio+0x51/0x1a0
  [921588.559077]  ? _cond_resched+0x19/0x30
  [921588.559081]  ? kmem_cache_alloc+0x38e/0x440
  [921588.559084]  ? ext4_init_io_end+0x1f/0x50
  [921588.559088]  

[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots

[Robert Jones]

I can confirm this is now fixed by 5.15.0-56-generic on our affected
machine:

Kubuntu 22.04
Ryzen 3 2200G
Using integrated Vega 8 graphics on default driver
Monitor connected via VGA

We previously experienced the same issue as other users on
5.15.0-53-generic.

Thank you!

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

Title:
  5.15.0-53-generic no longer boots

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

Bug description:
  == SRU Justification ==
  [Impact]
  "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp
  displays" caused AMD Navi10 GFX to panic at boot.

  [Fix]
  Backport the revised version of "drm/amd/display: Add helper for
  blanking all dp displays".

  [Test]
  Users confirmed the issue went away with this fix.
  We also verified the original issue we fixed didn't reappear.

  [Where problems could occur]
  We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many
  cases are untested, hence the potential risk is there.

  == Original Bug Report ==

  Running Ubuntu 22.04.1 Jammy.
  After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no 
longer fully boots.
  After the normal splash screen the screen goes black and the computer is not 
reachable on the network. Changing to another TTY does not work.

  New kernel version: 5.15.0-53.59

  I will attach the output of journalctl -b -1, please let me know what other 
info you need.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  johan  2549 F pulseaudio
   /dev/snd/controlC0:  johan  2549 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2020-12-01 (714 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  IwConfig:
   lono wireless extensions.

   enp37s0   no wireless extensions.

   wgnfs no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7C52
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-52-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/23/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 3.G0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M-A PRO MAX (MS-7C52)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C52
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Kernel-packages] [Bug 1994125] Re: [Solved] Gnome desktop freezes after reboot or resume after sleep

[Robert]

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

Title:
  [Solved] Gnome desktop freezes after reboot or resume after sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a reboot or resuming from sleep, the desktop appears and is
  fully functional for about 20 seconds. Then the desktop freezes, the
  fan spins up but the mouse still moves. Now click around, open
  programs, execute  to switch programs does nothing. The
  system stays this way for 60 seconds. Then the desktop becomes
  responsive again and all click and keystrokes executed during this
  time are executed. After that the system stays responsive and normal.
  The system log fills up with the following lines (many of them) during
  this period, pointing at a gnome javascript / message queue issue :

  ```
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
  t likely caused by not destroying a Clutter actor or Gtk+ widget with 
::destroy signals connected, but can also be cau
  sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
  and the JS callback not invoked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
  t likely caused by not destroying a Clutter actor or Gtk+ widget with 
::destroy signals connected, but can also be cau
  sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
  and the JS callback not invoked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-23-generic 5.19.0-23.24
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 2224 F wireplumber
   /dev/snd/controlC1:  robert 2224 F wireplumber
   /dev/snd/seq:    robert 2221 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 25 09:49:23 2022
  InstallationDate: Installed on 2022-10-23 (1 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC
   Bus 001 Device 002: ID 1d57:ad03 Xenta [T3] 2.4GHz and IR Air Mouse Remote 
Control
   Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=0c55150a-14de-418b-b87f-c46b8f0ef3e7 ro acpi_osi=! "acpi_osi=Windows 
2009" quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 202209

[Kernel-packages] [Bug 1994125] Re: [Solved] Gnome desktop freezes after reboot or resume after sleep

[Robert]

** Summary changed:

- Gnome desktop freezes after reboot or resume after sleep
+ [Solved] Gnome desktop freezes after reboot or resume after sleep

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

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

Title:
  [Solved] Gnome desktop freezes after reboot or resume after sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a reboot or resuming from sleep, the desktop appears and is
  fully functional for about 20 seconds. Then the desktop freezes, the
  fan spins up but the mouse still moves. Now click around, open
  programs, execute  to switch programs does nothing. The
  system stays this way for 60 seconds. Then the desktop becomes
  responsive again and all click and keystrokes executed during this
  time are executed. After that the system stays responsive and normal.
  The system log fills up with the following lines (many of them) during
  this period, pointing at a gnome javascript / message queue issue :

  ```
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
  t likely caused by not destroying a Clutter actor or Gtk+ widget with 
::destroy signals connected, but can also be cau
  sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
  and the JS callback not invoked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
  t likely caused by not destroying a Clutter actor or Gtk+ widget with 
::destroy signals connected, but can also be cau
  sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
  and the JS callback not invoked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-23-generic 5.19.0-23.24
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 2224 F wireplumber
   /dev/snd/controlC1:  robert 2224 F wireplumber
   /dev/snd/seq:    robert 2221 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 25 09:49:23 2022
  InstallationDate: Installed on 2022-10-23 (1 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC
   Bus 001 Device 002: ID 1d57:ad03 Xenta [T3] 2.4GHz and IR Air Mouse Remote 
Control
   Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=0c55150a-14de-418b-b87f-c46b8f0ef3e7 ro acpi_osi=! "acpi_osi=Windows 
2009" quiet splash vt.handoff=7
  RelatedPackageVersions:
   l

[Kernel-packages] [Bug 1994125] Re: Gnome desktop freezes after reboot or resume after sleep

[Robert]

The moment the desktop freezes, gnome-shell spins to 100%, the syslog
messages from that moment  start with a stack trace for
`resource:///org/gnome/shell/ui/calendar.js`

This points to the configured google account. Removing this cloud
account fixed the issue (desktop freeze), in a way this bug is now
solved and there should be a new bug created somewhere else. Can anyone
point me in the right direction ?

** Attachment added: "gnome-shell log messages"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994125/+attachment/5627446/+files/syslog.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/1994125

Title:
  [Solved] Gnome desktop freezes after reboot or resume after sleep

Status in linux package in Ubuntu:
  Opinion

Bug description:
  After a reboot or resuming from sleep, the desktop appears and is
  fully functional for about 20 seconds. Then the desktop freezes, the
  fan spins up but the mouse still moves. Now click around, open
  programs, execute  to switch programs does nothing. The
  system stays this way for 60 seconds. Then the desktop becomes
  responsive again and all click and keystrokes executed during this
  time are executed. After that the system stays responsive and normal.
  The system log fills up with the following lines (many of them) during
  this period, pointing at a gnome javascript / message queue issue :

  ```
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
  t likely caused by not destroying a Clutter actor or Gtk+ widget with 
::destroy signals connected, but can also be cau
  sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
  and the JS callback not invoked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
  t likely caused by not destroying a Clutter actor or Gtk+ widget with 
::destroy signals connected, but can also be cau
  sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
  and the JS callback not invoked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-23-generic 5.19.0-23.24
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 2224 F wireplumber
   /dev/snd/controlC1:  robert 2224 F wireplumber
   /dev/snd/seq:robert 2221 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 25 09:49:23 2022
  InstallationDate: Installed on 2022-10-23 (1 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC
   Bus 001 Device 002: ID 1d57:ad03 Xenta [T3] 2.4GHz and IR Air Mouse Remote 
Control
   Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001

[Kernel-packages] [Bug 1994125] [NEW] Gnome desktop freezes after reboot or resume after sleep

[Robert]

Public bug reported:

After a reboot or resuming from sleep, the desktop appears and is fully
functional for about 20 seconds. Then the desktop freezes, the fan spins
up but the mouse still moves. Now click around, open programs, execute
 to switch programs does nothing. The system stays this way
for 60 seconds. Then the desktop becomes responsive again and all click
and keystrokes executed during this time are executed. After that the
system stays responsive and normal. The system log fills up with the
following lines (many of them) during this period, pointing at a gnome
javascript / message queue issue :

```
Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
or remove() vfuncs. Because it would crash the application, it has been blocked.
Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy 
signals connected, but can also be cau
sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
and the JS callback not invoked.
Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
or remove() vfuncs. Because it would crash the application, it has been blocked.
Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy 
signals connected, but can also be cau
sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
and the JS callback not invoked.
Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
or remove() vfuncs. Because it would crash the application, it has been blocked.
Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
```

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-23-generic 5.19.0-23.24
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  robert 2224 F wireplumber
 /dev/snd/controlC1:  robert 2224 F wireplumber
 /dev/snd/seq:robert 2221 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 25 09:49:23 2022
InstallationDate: Installed on 2022-10-23 (1 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC
 Bus 001 Device 002: ID 1d57:ad03 Xenta [T3] 2.4GHz and IR Air Mouse Remote 
Control
 Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=0c55150a-14de-418b-b87f-c46b8f0ef3e7 ro acpi_osi=! "acpi_osi=Windows 
2009" quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-23-generic N/A
 linux-backports-modules-5.19.0-23-generic  N/A
 linux-firmware 20220923.gitf09bebf3-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2018
dmi.bios.release: 1.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16Q2IMS.10E
dmi.board.asset.tag: Default string
dmi.board.name: MS-16Q2
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dm

[Kernel-packages] [Bug 1992212] Re: nouveau pmu: firmware unavailable gp107

[Robert Browne]

As you can see in dmesg cannot enable HDA controller.
Causes no sound when using HDMI video stream.
Is there other firmware for gp107m ?

00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graph
ics 630]
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] (r
ev a1)

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

Title:
  nouveau pmu: firmware unavailable gp107

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

Bug description:
  /lib/firmware/nvidia/gp107
  /lib/firmware/nvidia/gp107/acr
  /lib/firmware/nvidia/gp107/gr
  /lib/firmware/nvidia/gp107/gr/fecs_bl.bin
  /lib/firmware/nvidia/gp107/gr/fecs_data.bin
  /lib/firmware/nvidia/gp107/gr/fecs_inst.bin
  /lib/firmware/nvidia/gp107/gr/fecs_sig.bin
  /lib/firmware/nvidia/gp107/gr/gpccs_bl.bin
  /lib/firmware/nvidia/gp107/gr/gpccs_data.bin
  /lib/firmware/nvidia/gp107/gr/gpccs_inst.bin
  /lib/firmware/nvidia/gp107/gr/gpccs_sig.bin
  /lib/firmware/nvidia/gp107/gr/sw_ctx.bin
  /lib/firmware/nvidia/gp107/gr/sw_nonctx.bin
  /lib/firmware/nvidia/gp107/nvdec
  /lib/firmware/nvidia/gp107/sec2
  /lib/firmware/nvidia/gp107/acr/bl.bin
  /lib/firmware/nvidia/gp107/acr/ucode_load.bin
  /lib/firmware/nvidia/gp107/acr/ucode_unload.bin
  /lib/firmware/nvidia/gp107/acr/unload_bl.bin
  /lib/firmware/nvidia/gp107/gr/sw_bundle_init.bin
  /lib/firmware/nvidia/gp107/gr/sw_method_init.bin
  /lib/firmware/nvidia/gp107/nvdec/scrubber.bin
  /lib/firmware/nvidia/gp107/sec2/desc-1.bin
  /lib/firmware/nvidia/gp107/sec2/desc.bin
  /lib/firmware/nvidia/gp107/sec2/image-1.bin
  /lib/firmware/nvidia/gp107/sec2/image.bin
  /lib/firmware/nvidia/gp107/sec2/sig-1.bin
  /lib/firmware/nvidia/gp107/sec2/sig.bin

  Package: linux-firmware
  Status: install ok installed
  Priority: optional
  Section: misc
  Installed-Size: 846721
  Maintainer: Ubuntu Kernel Team 
  Architecture: all
  Multi-Arch: foreign
  Version: 20220329.git681281e4-0ubuntu3.5
  Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), 
linux-res
  tricted-common
  Provides: atmel-firmware
  Recommends: firmware-sof-signed
  Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), 
linux-firmware-snapdrago
  n (<= 1.2-0ubuntu1)
  Conflicts: atmel-firmware
  Description: Firmware for Linux kernel drivers
   This package provides firmware used by Linux kernel drivers.
  Oct  8 08:49:44 fx504 kernel: [2.659551] MXM: GUID detected in BIOS
  Oct  8 08:49:44 fx504 kernel: [2.660477] ACPI Warning: 
\_SB.PCI0.GFX0._DSM: 
  Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] 
(20210730/ns
  arguments-61)
  Oct  8 08:49:44 fx504 kernel: [2.661646] ACPI Warning: 
\_SB.PCI0.PEG0.PEGP._
  DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] 
(202107
  30/nsarguments-61)
  Oct  8 08:49:44 fx504 kernel: [2.663101] pci :01:00.0: optimus 
capabilit
  ies: enabled, status dynamic power, hda bios codec supported
  Oct  8 08:49:44 fx504 kernel: [2.664016] VGA switcheroo: detected Optimus 
DS
  M method \_SB_.PCI0.PEG0.PEGP handle
  Oct  8 08:49:44 fx504 kernel: [2.664940] nouveau :01:00.0: enabling 
devi
  ce (0006 -> 0007)
  Oct  8 08:49:44 fx504 kernel: [2.665979] checking generic (8000 
7e9000) 
  vs hw (a300 100)
  Oct  8 08:49:44 fx504 kernel: [2.665981] checking generic (8000 
7e9000) 
  vs hw (9000 1000)
  Oct  8 08:49:44 fx504 kernel: [2.665982] checking generic (8000 
7e9000) 
  vs hw (a000 200)
  Oct  8 08:49:44 fx504 kernel: [2.666029] nouveau :01:00.0: NVIDIA 
GP107 
  (137000a1)
  Oct  8 08:49:44 fx504 kernel: [2.680631] checking generic (8000 
7e9000) 
  vs hw (a200 100)
  Oct  8 08:49:44 fx504 kernel: [2.680632] checking generic (8000 
7e9000) 
  vs hw (8000 1000)
  Oct  8 08:49:44 fx504 kernel: [2.746655] nouveau :01:00.0: bios: 
version
   86.07.50.00.59
  Oct  8 08:49:44 fx504 kernel: [2.747754] nouveau :01:00.0: pmu: 
firmware
   unavailable
  Oct  8 08:49:44 fx504 kernel: [2.755349] i915 :00:02.0: [drm] 
[ENCODER:1
  02:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
  Oct  8 08:49:44 fx504 kernel: [2.803611] nouveau :01:00.0: fb: 4096 
MiB 
  GDDR5
  Oct  8 08:49:44 fx504 kernel: [3.132263] [drm] Initialized i915 1.6.0 
202011
  03 for :00:02.0 on minor 0
  Oct  8 08:49:44 fx504 kernel: [3.139712] ACPI: video: Video Device [GFX0] 
(m
  ulti-head: yes  rom: no  post: no)
  Oct  8 08:49:44 fx504 kernel: [3.139759] nouveau :01:00.0: DRM: VRAM: 
40
  96 MiB
  Oct  8 08:49:44 fx504 kernel: [3.139763] nouveau :01:00.0: DRM: GART: 
53
  6870912 MiB
  Oct  8 08:49:44 fx504 kernel: [3.139766] nouveau :01:00.0: DRM: BIT 
tabl
  e 'A' not found
  Oct  8 

[Kernel-packages] [Bug 1992212] [NEW] nouveau pmu: firmware unavailable gp107

[Robert Browne]

Public bug reported:

/lib/firmware/nvidia/gp107
/lib/firmware/nvidia/gp107/acr
/lib/firmware/nvidia/gp107/gr
/lib/firmware/nvidia/gp107/gr/fecs_bl.bin
/lib/firmware/nvidia/gp107/gr/fecs_data.bin
/lib/firmware/nvidia/gp107/gr/fecs_inst.bin
/lib/firmware/nvidia/gp107/gr/fecs_sig.bin
/lib/firmware/nvidia/gp107/gr/gpccs_bl.bin
/lib/firmware/nvidia/gp107/gr/gpccs_data.bin
/lib/firmware/nvidia/gp107/gr/gpccs_inst.bin
/lib/firmware/nvidia/gp107/gr/gpccs_sig.bin
/lib/firmware/nvidia/gp107/gr/sw_ctx.bin
/lib/firmware/nvidia/gp107/gr/sw_nonctx.bin
/lib/firmware/nvidia/gp107/nvdec
/lib/firmware/nvidia/gp107/sec2
/lib/firmware/nvidia/gp107/acr/bl.bin
/lib/firmware/nvidia/gp107/acr/ucode_load.bin
/lib/firmware/nvidia/gp107/acr/ucode_unload.bin
/lib/firmware/nvidia/gp107/acr/unload_bl.bin
/lib/firmware/nvidia/gp107/gr/sw_bundle_init.bin
/lib/firmware/nvidia/gp107/gr/sw_method_init.bin
/lib/firmware/nvidia/gp107/nvdec/scrubber.bin
/lib/firmware/nvidia/gp107/sec2/desc-1.bin
/lib/firmware/nvidia/gp107/sec2/desc.bin
/lib/firmware/nvidia/gp107/sec2/image-1.bin
/lib/firmware/nvidia/gp107/sec2/image.bin
/lib/firmware/nvidia/gp107/sec2/sig-1.bin
/lib/firmware/nvidia/gp107/sec2/sig.bin

Package: linux-firmware
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 846721
Maintainer: Ubuntu Kernel Team 
Architecture: all
Multi-Arch: foreign
Version: 20220329.git681281e4-0ubuntu3.5
Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), linux-res
tricted-common
Provides: atmel-firmware
Recommends: firmware-sof-signed
Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), linux-firmware-snapdrago
n (<= 1.2-0ubuntu1)
Conflicts: atmel-firmware
Description: Firmware for Linux kernel drivers
 This package provides firmware used by Linux kernel drivers.
Oct  8 08:49:44 fx504 kernel: [2.659551] MXM: GUID detected in BIOS
Oct  8 08:49:44 fx504 kernel: [2.660477] ACPI Warning: \_SB.PCI0.GFX0._DSM: 
Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210730/ns
arguments-61)
Oct  8 08:49:44 fx504 kernel: [2.661646] ACPI Warning: \_SB.PCI0.PEG0.PEGP._
DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (202107
30/nsarguments-61)
Oct  8 08:49:44 fx504 kernel: [2.663101] pci :01:00.0: optimus capabilit
ies: enabled, status dynamic power, hda bios codec supported
Oct  8 08:49:44 fx504 kernel: [2.664016] VGA switcheroo: detected Optimus DS
M method \_SB_.PCI0.PEG0.PEGP handle
Oct  8 08:49:44 fx504 kernel: [2.664940] nouveau :01:00.0: enabling devi
ce (0006 -> 0007)
Oct  8 08:49:44 fx504 kernel: [2.665979] checking generic (8000 7e9000) 
vs hw (a300 100)
Oct  8 08:49:44 fx504 kernel: [2.665981] checking generic (8000 7e9000) 
vs hw (9000 1000)
Oct  8 08:49:44 fx504 kernel: [2.665982] checking generic (8000 7e9000) 
vs hw (a000 200)
Oct  8 08:49:44 fx504 kernel: [2.666029] nouveau :01:00.0: NVIDIA GP107 
(137000a1)
Oct  8 08:49:44 fx504 kernel: [2.680631] checking generic (8000 7e9000) 
vs hw (a200 100)
Oct  8 08:49:44 fx504 kernel: [2.680632] checking generic (8000 7e9000) 
vs hw (8000 1000)
Oct  8 08:49:44 fx504 kernel: [2.746655] nouveau :01:00.0: bios: version
 86.07.50.00.59
Oct  8 08:49:44 fx504 kernel: [2.747754] nouveau :01:00.0: pmu: firmware
 unavailable
Oct  8 08:49:44 fx504 kernel: [2.755349] i915 :00:02.0: [drm] [ENCODER:1
02:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
Oct  8 08:49:44 fx504 kernel: [2.803611] nouveau :01:00.0: fb: 4096 MiB 
GDDR5
Oct  8 08:49:44 fx504 kernel: [3.132263] [drm] Initialized i915 1.6.0 202011
03 for :00:02.0 on minor 0
Oct  8 08:49:44 fx504 kernel: [3.139712] ACPI: video: Video Device [GFX0] (m
ulti-head: yes  rom: no  post: no)
Oct  8 08:49:44 fx504 kernel: [3.139759] nouveau :01:00.0: DRM: VRAM: 40
96 MiB
Oct  8 08:49:44 fx504 kernel: [3.139763] nouveau :01:00.0: DRM: GART: 53
6870912 MiB
Oct  8 08:49:44 fx504 kernel: [3.139766] nouveau :01:00.0: DRM: BIT tabl
e 'A' not found
Oct  8 08:49:44 fx504 kernel: [3.139768] nouveau :01:00.0: DRM: BIT tabl
e 'L' not found
Oct  8 08:49:44 fx504 kernel: [3.139770] nouveau :01:00.0: DRM: Pointer 
to TMDS table not found
Oct  8 08:49:44 fx504 kernel: [3.139773] nouveau :01:00.0: DRM: DCB vers
ion 4.1
Oct  8 08:49:44 fx504 kernel: [3.140071] nouveau :01:00.0: DRM: MM: usin
Oct  8 08:49:44 fx504 kernel: [3.140137] input: Video Bus as /devices/LNXSYS
TM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
Oct  8 08:49:44 fx504 kernel: [3.140265] ACPI: video: Video Device [PEGP] (m
ulti-head: no  rom: yes  post: no)
Oct  8 08:49:44 fx504 kernel: [3.140294] input: Video Bus as /devices/LNXSYS
TM:00/LNXSYBUS:00/PNP0A08:00/device:13/LNXVIDEO:01/input/input9
Oct  8 08:49:44 fx504 kernel: [3.140322] [drm] Initialized nouveau 1.3.1 201

[Kernel-packages] [Bug 1982005] [NEW] installkernel directory in arch/x86/bootinstall.sh needs update

[Robert Bast]

Public bug reported:

This is for package linux-source-5.15.0. I could not select that in the
report-a-bug web interface thus selected 'linux'.

During a manual kernel compile's install phase
(make install) the install.sh script told me that it 'Cannot find LILO'.

After some research it turns out that install.sh cannot find the
installkernel program (supplied by debianutils).

This is because installkernel is installed to /usr/sbin but the script
looks in /sbin/ and no symbolic link exists in /sbin that points to
/usr/sbin/installkernel.

After creating the symlink to /usr/sbin/installkernel in /sbin, make
install works as expected and installs the kernel to /boot after which
update-initramfs / update-grub gets called.

It'd be mighty nice if this gets fixed (i.e. auto symlink creation or
adding /usr/sbin to search locations in install.sh)

Thank you for your time and attention.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-source-5.15.0 5.15.0-41.44
ProcVersionSignature: Ubuntu 5.15.0-41.44-lowlatency 5.15.39
Uname: Linux 5.15.0-41-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sam6496 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Mon Jul 18 16:59:40 2022
HibernationDevice: RESUME=UUID=311aea48-e089-4fed-a4ef-21f9212f057a
MachineType: Acer AOD255
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-lowlatency 
root=UUID=7ed89f1f-cf18-49f8-a413-8bd3874b2f2a ro quiet 
resume=UUID=311aea48-e089-4fed-a4ef-21f9212f057a
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-41-lowlatency N/A
 linux-backports-modules-5.15.0-41-lowlatency  N/A
 linux-firmware20220329.git681281e4-0ubuntu3.2
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-07-18 (0 days ago)
dmi.bios.date: 04/22/2011
dmi.bios.release: 16.220
dmi.bios.vendor: Acer
dmi.bios.version: V3.16(DDR3)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE02_PT
dmi.board.vendor: Acer
dmi.board.version: V3.16(DDR3)
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V3.16(DDR3)
dmi.modalias: 
dmi:bvnAcer:bvrV3.16(DDR3):bd04/22/2011:br16.220:svnAcer:pnAOD255:pvrV3.16(DDR3):rvnAcer:rnJE02_PT:rvrV3.16(DDR3):cvnAcer:ct10:cvrV3.16(DDR3):skuNetTopSku:
dmi.product.family: Intel_Mobile
dmi.product.name: AOD255
dmi.product.sku: NetTopSku
dmi.product.version: V3.16(DDR3)
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug jammy

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

Title:
  installkernel directory in arch/x86/bootinstall.sh needs update

Status in linux package in Ubuntu:
  New

Bug description:
  This is for package linux-source-5.15.0. I could not select that in
  the report-a-bug web interface thus selected 'linux'.

  During a manual kernel compile's install phase
  (make install) the install.sh script told me that it 'Cannot find LILO'.

  After some research it turns out that install.sh cannot find the
  installkernel program (supplied by debianutils).

  This is because installkernel is installed to /usr/sbin but the script
  looks in /sbin/ and no symbolic link exists in /sbin that points to
  /usr/sbin/installkernel.

  After creating the symlink to /usr/sbin/installkernel in /sbin, make
  install works as expected and installs the kernel to /boot after which
  update-initramfs / update-grub gets called.

  It'd be mighty nice if this gets fixed (i.e. auto symlink creation or
  adding /usr/sbin to search locations in install.sh)

  Thank you for your time and attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-source-5.15.0 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-lowlatency 5.15.39
  Uname: Linux 5.15.0-41-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam6496 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Mon Jul 18 16:59:40 2022
  HibernationDevice: RESUME=UUID=311aea48-e089-4fed-a4ef-21f9212f057a
  MachineType: Acer AOD255
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-lowlatency 
root=UUID=7ed89f1f-cf18-49f8-a413-8bd3874b2f2a ro quiet 
resume=UUID=311aea48-e089-4fed-a4ef-21f9212f057a
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-lowlatency N/A
   linux-backports-modules-5.15.0-41-lowlatency  N/A
   linux-firmware   

[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync

[Robert Lippmann]

It won’t let me change the state back to active.

Every time I try nothing happens and array_status is always idle.

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

Title:
  kernel io hangs during mdcheck/resync

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.11 package in Ubuntu:
  Confirmed

Bug description:
  It seems to always occur during an mdcheck/resync, if I am logged in
  via SSH it is still somewhat responsive and basic utilities like dmesg
  will work.  But it apppears any write I/O will hang the terminal and
  nothing is written to syslog (presumably because it is blocked).

  Below is output of dmesg and cat /proc/mdstat, it appears the data
  check was interrupted and /proc/mdstat still shows progress, and a
  whole slew of hung tasks including md1_resync itself.

  [756484.534293] md: data-check of RAID array md0
  [756484.628039] md: delaying data-check of md1 until md0 has finished (they 
share one or more physical units)
  [756493.808773] md: md0: data-check done.
  [756493.829760] md: data-check of RAID array md1
  [778112.446410] md: md1: data-check interrupted.
  [810654.608102] md: data-check of RAID array md1
  [832291.201064] md: md1: data-check interrupted.
  [899745.389485] md: data-check of RAID array md1
  [921395.835305] md: md1: data-check interrupted.
  [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 
seconds.
  [921588.558846]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.558854] task:systemd-journal state:D stack:0 pid:  376 ppid: 
1 flags:0x0220
  [921588.558859] Call Trace:
  [921588.558864]  __schedule+0x44c/0x8a0
  [921588.558872]  schedule+0x4f/0xc0
  [921588.558876]  md_write_start+0x150/0x240
  [921588.558880]  ? wait_woken+0x80/0x80
  [921588.558886]  raid5_make_request+0x88/0x890 [raid456]
  [921588.558898]  ? wait_woken+0x80/0x80
  [921588.558901]  ? mempool_kmalloc+0x17/0x20
  [921588.558904]  md_handle_request+0x12d/0x1a0
  [921588.558907]  ? __part_start_io_acct+0x51/0xf0
  [921588.558912]  md_submit_bio+0xca/0x100
  [921588.558915]  submit_bio_noacct+0x112/0x4f0
  [921588.558918]  ? ext4_fc_reserve_space+0x110/0x230
  [921588.558922]  submit_bio+0x51/0x1a0
  [921588.558925]  ? _cond_resched+0x19/0x30
  [921588.558928]  ? kmem_cache_alloc+0x38e/0x440
  [921588.558932]  ? ext4_init_io_end+0x1f/0x50
  [921588.558936]  ext4_io_submit+0x4d/0x60
  [921588.558940]  ext4_writepages+0x2c6/0xcd0
  [921588.558944]  do_writepages+0x43/0xd0
  [921588.558948]  ? do_writepages+0x43/0xd0
  [921588.558951]  ? fault_dirty_shared_page+0xa5/0x110
  [921588.558955]  __filemap_fdatawrite_range+0xcc/0x110
  [921588.558960]  file_write_and_wait_range+0x74/0xc0
  [921588.558962]  ext4_sync_file+0xf5/0x350
  [921588.558967]  vfs_fsync_range+0x49/0x80
  [921588.558970]  do_fsync+0x3d/0x70
  [921588.558973]  __x64_sys_fsync+0x14/0x20
  [921588.558976]  do_syscall_64+0x38/0x90
  [921588.558980]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [921588.558984] RIP: 0033:0x7f4c97ee832b
  [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 
004a
  [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 
7f4c97ee832b
  [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 
0021
  [921588.558995] RBP: 0001 R08:  R09: 
7ffdceb29fa8
  [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 
7ffdceb29fa8
  [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 
55ced34bcf90
  [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds.
  [921588.559018]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.559025] task:mysqld  state:D stack:0 pid: 1505 ppid: 
1 flags:0x
  [921588.559030] Call Trace:
  [921588.559032]  __schedule+0x44c/0x8a0
  [921588.559036]  schedule+0x4f/0xc0
  [921588.559040]  md_write_start+0x150/0x240
  [921588.559044]  ? wait_woken+0x80/0x80
  [921588.559047]  raid5_make_request+0x88/0x890 [raid456]
  [921588.559056]  ? wait_woken+0x80/0x80
  [921588.559059]  ? mempool_kmalloc+0x17/0x20
  [921588.559062]  md_handle_request+0x12d/0x1a0
  [921588.559065]  ? __part_start_io_acct+0x51/0xf0
  [921588.559068]  md_submit_bio+0xca/0x100
  [921588.559071]  submit_bio_noacct+0x112/0x4f0
  [921588.559075]  submit_bio+0x51/0x1a0
  [921588.559077]  ? _cond_resched+0x19/0x30
  [921588.559081]  ? kmem_cache_alloc+0x38e/0x440
  [921588.559084]  ? ext4_init_io_end+0x1f/0x50
  [921588.559088]  ext4_io_submit+0x4d/0x60
  [921588.559091]  ext4_writepages+0x2c6/0xcd0
  [921588.559094]  ? __schedule+0x454/0x8a0
  [921588.559097]  ? 

[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync

[Robert Lippmann]

Digging further, I think I might be running into this bug:

https://lore.kernel.org/linux-raid/5ed54ffc-
ce82-bf66-4eff-390cb23bc...@molgen.mpg.de/T/

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

Title:
  kernel io hangs during mdcheck/resync

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.11 package in Ubuntu:
  Confirmed

Bug description:
  It seems to always occur during an mdcheck/resync, if I am logged in
  via SSH it is still somewhat responsive and basic utilities like dmesg
  will work.  But it apppears any write I/O will hang the terminal and
  nothing is written to syslog (presumably because it is blocked).

  Below is output of dmesg and cat /proc/mdstat, it appears the data
  check was interrupted and /proc/mdstat still shows progress, and a
  whole slew of hung tasks including md1_resync itself.

  [756484.534293] md: data-check of RAID array md0
  [756484.628039] md: delaying data-check of md1 until md0 has finished (they 
share one or more physical units)
  [756493.808773] md: md0: data-check done.
  [756493.829760] md: data-check of RAID array md1
  [778112.446410] md: md1: data-check interrupted.
  [810654.608102] md: data-check of RAID array md1
  [832291.201064] md: md1: data-check interrupted.
  [899745.389485] md: data-check of RAID array md1
  [921395.835305] md: md1: data-check interrupted.
  [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 
seconds.
  [921588.558846]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.558854] task:systemd-journal state:D stack:0 pid:  376 ppid: 
1 flags:0x0220
  [921588.558859] Call Trace:
  [921588.558864]  __schedule+0x44c/0x8a0
  [921588.558872]  schedule+0x4f/0xc0
  [921588.558876]  md_write_start+0x150/0x240
  [921588.558880]  ? wait_woken+0x80/0x80
  [921588.558886]  raid5_make_request+0x88/0x890 [raid456]
  [921588.558898]  ? wait_woken+0x80/0x80
  [921588.558901]  ? mempool_kmalloc+0x17/0x20
  [921588.558904]  md_handle_request+0x12d/0x1a0
  [921588.558907]  ? __part_start_io_acct+0x51/0xf0
  [921588.558912]  md_submit_bio+0xca/0x100
  [921588.558915]  submit_bio_noacct+0x112/0x4f0
  [921588.558918]  ? ext4_fc_reserve_space+0x110/0x230
  [921588.558922]  submit_bio+0x51/0x1a0
  [921588.558925]  ? _cond_resched+0x19/0x30
  [921588.558928]  ? kmem_cache_alloc+0x38e/0x440
  [921588.558932]  ? ext4_init_io_end+0x1f/0x50
  [921588.558936]  ext4_io_submit+0x4d/0x60
  [921588.558940]  ext4_writepages+0x2c6/0xcd0
  [921588.558944]  do_writepages+0x43/0xd0
  [921588.558948]  ? do_writepages+0x43/0xd0
  [921588.558951]  ? fault_dirty_shared_page+0xa5/0x110
  [921588.558955]  __filemap_fdatawrite_range+0xcc/0x110
  [921588.558960]  file_write_and_wait_range+0x74/0xc0
  [921588.558962]  ext4_sync_file+0xf5/0x350
  [921588.558967]  vfs_fsync_range+0x49/0x80
  [921588.558970]  do_fsync+0x3d/0x70
  [921588.558973]  __x64_sys_fsync+0x14/0x20
  [921588.558976]  do_syscall_64+0x38/0x90
  [921588.558980]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [921588.558984] RIP: 0033:0x7f4c97ee832b
  [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 
004a
  [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 
7f4c97ee832b
  [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 
0021
  [921588.558995] RBP: 0001 R08:  R09: 
7ffdceb29fa8
  [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 
7ffdceb29fa8
  [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 
55ced34bcf90
  [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds.
  [921588.559018]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.559025] task:mysqld  state:D stack:0 pid: 1505 ppid: 
1 flags:0x
  [921588.559030] Call Trace:
  [921588.559032]  __schedule+0x44c/0x8a0
  [921588.559036]  schedule+0x4f/0xc0
  [921588.559040]  md_write_start+0x150/0x240
  [921588.559044]  ? wait_woken+0x80/0x80
  [921588.559047]  raid5_make_request+0x88/0x890 [raid456]
  [921588.559056]  ? wait_woken+0x80/0x80
  [921588.559059]  ? mempool_kmalloc+0x17/0x20
  [921588.559062]  md_handle_request+0x12d/0x1a0
  [921588.559065]  ? __part_start_io_acct+0x51/0xf0
  [921588.559068]  md_submit_bio+0xca/0x100
  [921588.559071]  submit_bio_noacct+0x112/0x4f0
  [921588.559075]  submit_bio+0x51/0x1a0
  [921588.559077]  ? _cond_resched+0x19/0x30
  [921588.559081]  ? kmem_cache_alloc+0x38e/0x440
  [921588.559084]  ? ext4_init_io_end+0x1f/0x50
  [921588.559088]  ext4_io_submit+0x4d/0x60
  [921588.559091]  ext4_writepages+0x2c6/0xcd0
  [921588.559094]  ? 

[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync

[Robert Lippmann]

I'm running checkarray manually, I took off all the start and stop stuff
like you did.

echo active > /sys/block/md0/md/array_state doesn't fix.

I must have not gotten all the trace last time.  I've attached it here.


** Attachment added: "kernel log snippet"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1942935/+attachment/5602089/+files/newkern.log

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

Title:
  kernel io hangs during mdcheck/resync

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.11 package in Ubuntu:
  Confirmed

Bug description:
  It seems to always occur during an mdcheck/resync, if I am logged in
  via SSH it is still somewhat responsive and basic utilities like dmesg
  will work.  But it apppears any write I/O will hang the terminal and
  nothing is written to syslog (presumably because it is blocked).

  Below is output of dmesg and cat /proc/mdstat, it appears the data
  check was interrupted and /proc/mdstat still shows progress, and a
  whole slew of hung tasks including md1_resync itself.

  [756484.534293] md: data-check of RAID array md0
  [756484.628039] md: delaying data-check of md1 until md0 has finished (they 
share one or more physical units)
  [756493.808773] md: md0: data-check done.
  [756493.829760] md: data-check of RAID array md1
  [778112.446410] md: md1: data-check interrupted.
  [810654.608102] md: data-check of RAID array md1
  [832291.201064] md: md1: data-check interrupted.
  [899745.389485] md: data-check of RAID array md1
  [921395.835305] md: md1: data-check interrupted.
  [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 
seconds.
  [921588.558846]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.558854] task:systemd-journal state:D stack:0 pid:  376 ppid: 
1 flags:0x0220
  [921588.558859] Call Trace:
  [921588.558864]  __schedule+0x44c/0x8a0
  [921588.558872]  schedule+0x4f/0xc0
  [921588.558876]  md_write_start+0x150/0x240
  [921588.558880]  ? wait_woken+0x80/0x80
  [921588.558886]  raid5_make_request+0x88/0x890 [raid456]
  [921588.558898]  ? wait_woken+0x80/0x80
  [921588.558901]  ? mempool_kmalloc+0x17/0x20
  [921588.558904]  md_handle_request+0x12d/0x1a0
  [921588.558907]  ? __part_start_io_acct+0x51/0xf0
  [921588.558912]  md_submit_bio+0xca/0x100
  [921588.558915]  submit_bio_noacct+0x112/0x4f0
  [921588.558918]  ? ext4_fc_reserve_space+0x110/0x230
  [921588.558922]  submit_bio+0x51/0x1a0
  [921588.558925]  ? _cond_resched+0x19/0x30
  [921588.558928]  ? kmem_cache_alloc+0x38e/0x440
  [921588.558932]  ? ext4_init_io_end+0x1f/0x50
  [921588.558936]  ext4_io_submit+0x4d/0x60
  [921588.558940]  ext4_writepages+0x2c6/0xcd0
  [921588.558944]  do_writepages+0x43/0xd0
  [921588.558948]  ? do_writepages+0x43/0xd0
  [921588.558951]  ? fault_dirty_shared_page+0xa5/0x110
  [921588.558955]  __filemap_fdatawrite_range+0xcc/0x110
  [921588.558960]  file_write_and_wait_range+0x74/0xc0
  [921588.558962]  ext4_sync_file+0xf5/0x350
  [921588.558967]  vfs_fsync_range+0x49/0x80
  [921588.558970]  do_fsync+0x3d/0x70
  [921588.558973]  __x64_sys_fsync+0x14/0x20
  [921588.558976]  do_syscall_64+0x38/0x90
  [921588.558980]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [921588.558984] RIP: 0033:0x7f4c97ee832b
  [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 
004a
  [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 
7f4c97ee832b
  [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 
0021
  [921588.558995] RBP: 0001 R08:  R09: 
7ffdceb29fa8
  [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 
7ffdceb29fa8
  [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 
55ced34bcf90
  [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds.
  [921588.559018]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.559025] task:mysqld  state:D stack:0 pid: 1505 ppid: 
1 flags:0x
  [921588.559030] Call Trace:
  [921588.559032]  __schedule+0x44c/0x8a0
  [921588.559036]  schedule+0x4f/0xc0
  [921588.559040]  md_write_start+0x150/0x240
  [921588.559044]  ? wait_woken+0x80/0x80
  [921588.559047]  raid5_make_request+0x88/0x890 [raid456]
  [921588.559056]  ? wait_woken+0x80/0x80
  [921588.559059]  ? mempool_kmalloc+0x17/0x20
  [921588.559062]  md_handle_request+0x12d/0x1a0
  [921588.559065]  ? __part_start_io_acct+0x51/0xf0
  [921588.559068]  md_submit_bio+0xca/0x100
  [921588.559071]  submit_bio_noacct+0x112/0x4f0
  [921588.559075]  submit_bio+0x51/0x1a0
  [921588.559077]  ? 

[Kernel-packages] [Bug 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)

[Robert Helewka]

Nvidia 3090 on an Alienware R10: boots normally, but the desktop appears as 
shades of bright green. 
It was corrected when I followed Andrii's solution in comment #28. 
Thank you Andrii, you just saved me a bunch of time.

I had already tried the Live USB and installed 22.04 on my Gigabyte
Aorus X5 MD Laptop (Nvidia 1080ti) and I have not encountered this issue
on it.

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

Title:
  [nouveau] Weird colors after startup (Ubuntu 22.04)

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [Workaround/Fix]

  1. When starting the Ubuntu live image, select the option 'Ubuntu
  (safe graphics)' from the boot menu.

  2. During installation be sure to select the third-party software
  option checkbox in order to get the right Nvidia driver installed.

  [Original Description]

  I started Ubuntu 22.04 from a live pen drive. Everything seems fine,
  the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
  appears. When hitting "Try Ubuntu", the screen turns black for a
  couple of seconds and then re-appears in yellow and brown colors,
  feels like a 4 color display (white, black, yellow and orange) and I
  can hardly see anything - sending this bug report from that live
  system right after starting it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:54:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 
00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7C56
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550-A PRO (MS-7C56)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C56
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 1978151] [NEW] Kernel Panic Running Specific Docker Image

[Robert Hencke]

Public bug reported:

This panic occur only on the latest Linux kernel release.

* 5.13.0-1030-gcp is broken
* 5.13.0-1027-gcp is okay
* 5.13.0-1024-gcp is okay

Steps to reproduce:
1) Ensure kernel version is 5.13.0-1030-gcp.
2) sudo apt update
3) sudo apt install docker.io
4) sudo docker run releases-docker.jfrog.io/jfrog/artifactory-pro:7.25.7

Expected behavior:
The container runs without issue.

Actual behavior (the logs got slightly garbled, but):
Kernel panics with:
[ 1237.492662] kernel BUG at include/linux/fs.h:3104!
[ 1237.497925] invalid opcode:  [#1] SMP PTI
[ 1Jun  9 18:20:15 23b7ootlooptest ker.502540]nel: [ 1237.4926 CPU: 1 PID: 58] 
19[2 cut here ]5 C
Jun  9omm: 18:20:15 bootlo doptest kernel: [ 1237.492662] keranel BUG at 
incltude/linux/fs.h:3e No104!
Jun  9 18:t2 0:15 bootlooptetst kernel: [ 123ainted 5.13.07.497925] 
invali1030-gcp #3d opcode:  [6~20.04.#1] SMP PTI
1-Ubuntu
[ 1237.535282] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
[ 1237.545178] RIP: 0010:__fput+0x247/0x250
[ 1237.549477] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff 
e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 7e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 
1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48
[ 1237.569173] RSP: 0018:b8b280b0fe18 EFLAGS: 00010246
[ 1237.574909] RAX:  RBX: 000a801d RCX: 97f011bf7000
[ 1237.586271] RDX: 97f011ae9280 RSI: 0001 RDI: 
[ 1237.593886] RBP: b8b280b0fe40 R08: 97f011aef140 R09: 97f022482570
[ 1237.601492] R10: b8b280b0fe18 R11: 97f026038910 R12: 97f026038900
[ 1237.608820] R13: 97f022482570 R14: 97f011ae92a0 R15: 97f0346bbc00
[ 1237.616301] FS:  () GS:97f03bd0() 
knlGS:
[ 1237.624680] CS:  0010 DS:  ES:  CR0: 80050033
[ 1237.630646] CR2: 7f08b7f7eff0 CR3: 00010e810001 CR4: 003706e0
[ 1237.637892] DR0:  DR1:  DR2: 
[ 1237.645134] DR3:  DR6: fffe0ff0 DR7: 0400
[ 1237.652379] Call Trace:
[ 1237.655022]  
[ 1237.657242]  fput+0xe/0x10
[ 1237.660585]  task_work_run+0x70/0xb0
[ 1237.664623]  do_exit+0x37b/0xaf0
[ 1237.668064]  do_group_exit+0x43/0xb0
[ 1237.671930]  __x64_sys_exit_group+0x18/0x20
[ 1237.676586]  do_syscall_64+0x40/0xb0
[ 1237.680298]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 1237.685880] RIP: 0033:0x7f08b7f7f026
[ 1237.689680] Code: Unable to access opcode bytes at RIP 0x7f08b7f7effc.
[ 1237.697194] RSP: 002b:7ffc949c3fe8 EFLAGS: 0246 ORIG_RAX: 
00e7
[ 1237.705346] RAX: ffda RBX: 7f08b8271880 RCX: 7f08b7f7f026
[ 1237.712960] RDX:  RSI: 003c RDI: 
[ 1237.720554] RBP:  R08: 00e7 R09: ff80
[ 1237.729387] R10: 7ffc949c3eb4 R11: 0246 R12: 7f08b8271880
[ 1237.737128] R13: 0002 R14: 7f08b827a388 R15: 
[ 1237.744398]  
[ 1237.746716] Modules linked in: veth xt_conntrack xt_MASQUERADE xfrm_user 
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat bpfilter br_netfilter 
bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel 
crypto_simd cryptd input_leds psmouse virtio_net serio_raw net_failover 
efi_pstore failover sch_fq_codel drm virtio_rng ip_tables x_tables autofs4
[ 1237.788902] ---[ end trace e45b85d1ea54b719 ]---

Other information:
lsb-release -rd prints:
Description:Ubuntu 20.04.4 LTS
Release:20.04

apt-cache policy linux-image-5.13.0-1030-gcp prints:
linux-image-5.13.0-1030-gcp:
  Installed: 5.13.0-1030.36~20.04.1
  Candidate: 5.13.0-1030.36~20.04.1
  Version table:
 *** 5.13.0-1030.36~20.04.1 500
500 http://us-east1.gce.archive.ubuntu.com/ubuntu focal-updates/main 
amd64 Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
100 /var/lib/dpkg/status

apt-cache policy docker.io prints:
docker.io:
  Installed: 20.10.12-0ubuntu2~20.04.1
  Candidate: 20.10.12-0ubuntu2~20.04.1
  Version table:
 *** 20.10.12-0ubuntu2~20.04.1 500
500 http://us-east1.gce.archive.ubuntu.com/ubuntu 
focal-updates/universe amd64 Packages
100 /var/lib/dpkg/status
 20.10.7-0ubuntu5~20.04.2 500
500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 
Packages
 19.03.8-0ubuntu1 500
500 http://us-east1.gce.archive.ubuntu.com/ubuntu focal/universe amd64 
Packages

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

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

Title:
  Kernel Panic Running Specific Docker 

[Kernel-packages] [Bug 1967013] Re: Bionic update: upstream stable patchset 2022-03-29

[Robert Schlabbach]

As stated in the bug ticket linked above, this commit:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b

causes issues on hardware where the intel_lpss driver tries to load the intel 
idma driver, because this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mfd/intel-lpss.c?id=569fac74627cc332a2097a7a4bfdc654b8e7f273

has not been backported to the 4.15 kernel.

I propose backporting this commit to the 4.15 kernel ASAP to fix the
issue.

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

Title:
  Bionic update: upstream stable patchset 2022-03-29

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-03-29

  Ported from the following upstream stable releases:
  v4.14.266, v4.19.229
  v4.14.267, v4.19.230
  v4.14.268, v4.19.231

     from git://git.kernel.org/

  moxart: fix potential use-after-free on remove path
  x86/mm, mm/hwpoison: Fix the unmap kernel 1:1 pages check condition
  UBUNTU: upstream stable to v4.14.266, v4.19.229
  integrity: check the return value of audit_log_start()
  ima: Remove ima_policy file before directory
  ima: Allow template selection with ima_template[_fmt]= after ima_hash=
  mmc: sdhci-of-esdhc: Check for error num after setting mask
  net: phy: marvell: Fix MDI-x polarity setting in 88e1118-compatible PHYs
  NFS: Fix initialisation of nfs_client cl_flags field
  NFSD: Clamp WRITE offsets
  NFSv4 only print the label when its queried
  nfs: nfs4clinet: check the return value of kstrdup()
  NFSv4.1: Fix uninitialised variable in devicenotify
  NFSv4 remove zero number of fs_locations entries error check
  NFSv4 expose nfs_parse_server_name function
  scsi: target: iscsi: Make sure the np under each tpg is unique
  usb: dwc2: gadget: don't try to disable ep0 in dwc2_hsotg_suspend
  net: stmmac: dwmac-sun8i: use return val of readl_poll_timeout()
  Revert "net: axienet: Wait for PhyRstCmplt after core reset"
  ARM: dts: imx23-evk: Remove MX23_PAD_SSP1_DETECT from hog group
  ARM: dts: meson: Fix the UART compatible strings
  staging: fbtft: Fix error path in fbtft_driver_module_init()
  ARM: dts: imx6qdl-udoo: Properly describe the SD card detect
  usb: f_fs: Fix use-after-free for epfile
  bonding: pair enable_port with slave_arr_updates
  ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path
  net: do not keep the dst cache when uncloning an skb dst and its metadata
  net: fix a memleak when uncloning an skb dst and its metadata
  tipc: rate limit warning for received illegal binding update
  net: amd-xgbe: disable interrupts during pci removal
  vt_ioctl: fix array_index_nospec in vt_setactivate
  vt_ioctl: add array_index_nospec to VT_ACTIVATE
  n_tty: wake up poll(POLLRDNORM) on receiving data
  usb: ulpi: Move of_node_put to ulpi_dev_release
  usb: ulpi: Call of_node_put correctly
  usb: dwc3: gadget: Prevent core from processing stale TRBs
  USB: gadget: validate interface OS descriptor requests
  usb: gadget: rndis: check size of RNDIS_MSG_SET command
  USB: serial: ftdi_sio: add support for Brainboxes US-159/235/320
  USB: serial: option: add ZTE MF286D modem
  USB: serial: ch341: add support for GW Instek USB2.0-Serial devices
  USB: serial: cp210x: add NCR Retail IO box id
  USB: serial: cp210x: add CPI Bulk Coin Recycler id
  seccomp: Invalidate seccomp mode to catch death failures
  hwmon: (dell-smm) Speed up setting of fan speed
  perf: Fix list corruption in perf_cgroup_switch()
  net: bridge: fix stale eth hdr pointer in br_dev_xmit
  UBUNTU: upstream stable to v4.14.267, v4.19.230
  Makefile.extrawarn: Move -Wunaligned-access to W=1
  net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup
  serial: parisc: GSC: fix build when IOSAPIC is not set
  parisc: Fix data TLB miss in sba_unmap_sg
  parisc: Fix sglist access in ccio-dma.c
  btrfs: send: in case of IO error log it
  net: ieee802154: at86rf230: Stop leaking skb's
  selftests/zram: Skip max_comp_streams interface on newer kernel
  selftests/zram01.sh: Fix compression ratio calculation
  selftests/zram: Adapt the situation that /dev/zram0 is being used
  ax25: improve the incomplete 

[Kernel-packages] [Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen

[Robert Schlabbach]

FIXED IT! It is indeed the intel_lpss driver, at least in my case.

This commit:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b

will not work right when a module that is asynchronously loaded tries to
synchronously load a module, which is not (or no longer?) allowed. It
appears the intel_lpss driver did just that until this commit:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mfd/intel-
lpss.c?id=569fac74627cc332a2097a7a4bfdc654b8e7f273

But this commit has not been backported to the 4.15 kernel, so the
intel_lpss driver delivered with the 4.15.0-177 kernel package does not
have it.

Applying this commit to the 4.15.0-177 source tree, rebuilding and
replacing (only!) the intel_lpss.ko module makes the kernel load without
delays for me. I confirmed the same with kernel 4.15.0-180.

So now we only need to convince the Ubuntu maintainers to backport
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mfd/intel-
lpss.c?id=569fac74627cc332a2097a7a4bfdc654b8e7f273 to the 4.15 kernel...

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

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.15.0-177-generic, my machine
  completely freezes on the Ubuntu Welcome screen, i.e. right after
  switching to GUI mode. The mouse pointer is frozen, the keyboard does
  not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows
  no reaction.

  I cannot work with my machine at this point and have to hard reset it.

  Selecting advanced boot options in grub and selecting the previous
  linux kernel 4.15.0-176 makes it work again. So this bad bug was
  introduced with the 4.15.0-177 kernel release.

  I tried removing the nvidia-driver-510 package, presumably making
  Ubuntu use the "nouveau" driver, and with that, I could use the
  welcome screen and log in, but the machine still froze shortly
  afterwards.

  So maybe this is some sort of interference with my GeForce 1080
  graphics card, but it is not specific to the driver used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
  Uname: Linux 4.15.0-176-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2082 F pulseaudio
   /dev/snd/controlC0:  robert 2082 F pulseaudio
   /dev/snd/controlC2:  robert 2082 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 12 13:36:28 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-29 (2386 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Supermicro Super Server
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic 
root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-176-generic N/A
   linux-backports-modules-4.15.0-176-generic  N/A
   linux-firmware  1.173.21
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago)
  dmi.bios.date: 09/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11SAE
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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


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

[Kernel-packages] [Bug 1967013] Re: Bionic update: upstream stable patchset 2022-03-29

[Robert Schlabbach]

This commit is suspected to cause issues for many users:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b

Please see this bug ticket:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167

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

Title:
  Bionic update: upstream stable patchset 2022-03-29

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-03-29

  Ported from the following upstream stable releases:
  v4.14.266, v4.19.229
  v4.14.267, v4.19.230
  v4.14.268, v4.19.231

     from git://git.kernel.org/

  moxart: fix potential use-after-free on remove path
  x86/mm, mm/hwpoison: Fix the unmap kernel 1:1 pages check condition
  UBUNTU: upstream stable to v4.14.266, v4.19.229
  integrity: check the return value of audit_log_start()
  ima: Remove ima_policy file before directory
  ima: Allow template selection with ima_template[_fmt]= after ima_hash=
  mmc: sdhci-of-esdhc: Check for error num after setting mask
  net: phy: marvell: Fix MDI-x polarity setting in 88e1118-compatible PHYs
  NFS: Fix initialisation of nfs_client cl_flags field
  NFSD: Clamp WRITE offsets
  NFSv4 only print the label when its queried
  nfs: nfs4clinet: check the return value of kstrdup()
  NFSv4.1: Fix uninitialised variable in devicenotify
  NFSv4 remove zero number of fs_locations entries error check
  NFSv4 expose nfs_parse_server_name function
  scsi: target: iscsi: Make sure the np under each tpg is unique
  usb: dwc2: gadget: don't try to disable ep0 in dwc2_hsotg_suspend
  net: stmmac: dwmac-sun8i: use return val of readl_poll_timeout()
  Revert "net: axienet: Wait for PhyRstCmplt after core reset"
  ARM: dts: imx23-evk: Remove MX23_PAD_SSP1_DETECT from hog group
  ARM: dts: meson: Fix the UART compatible strings
  staging: fbtft: Fix error path in fbtft_driver_module_init()
  ARM: dts: imx6qdl-udoo: Properly describe the SD card detect
  usb: f_fs: Fix use-after-free for epfile
  bonding: pair enable_port with slave_arr_updates
  ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path
  net: do not keep the dst cache when uncloning an skb dst and its metadata
  net: fix a memleak when uncloning an skb dst and its metadata
  tipc: rate limit warning for received illegal binding update
  net: amd-xgbe: disable interrupts during pci removal
  vt_ioctl: fix array_index_nospec in vt_setactivate
  vt_ioctl: add array_index_nospec to VT_ACTIVATE
  n_tty: wake up poll(POLLRDNORM) on receiving data
  usb: ulpi: Move of_node_put to ulpi_dev_release
  usb: ulpi: Call of_node_put correctly
  usb: dwc3: gadget: Prevent core from processing stale TRBs
  USB: gadget: validate interface OS descriptor requests
  usb: gadget: rndis: check size of RNDIS_MSG_SET command
  USB: serial: ftdi_sio: add support for Brainboxes US-159/235/320
  USB: serial: option: add ZTE MF286D modem
  USB: serial: ch341: add support for GW Instek USB2.0-Serial devices
  USB: serial: cp210x: add NCR Retail IO box id
  USB: serial: cp210x: add CPI Bulk Coin Recycler id
  seccomp: Invalidate seccomp mode to catch death failures
  hwmon: (dell-smm) Speed up setting of fan speed
  perf: Fix list corruption in perf_cgroup_switch()
  net: bridge: fix stale eth hdr pointer in br_dev_xmit
  UBUNTU: upstream stable to v4.14.267, v4.19.230
  Makefile.extrawarn: Move -Wunaligned-access to W=1
  net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup
  serial: parisc: GSC: fix build when IOSAPIC is not set
  parisc: Fix data TLB miss in sba_unmap_sg
  parisc: Fix sglist access in ccio-dma.c
  btrfs: send: in case of IO error log it
  net: ieee802154: at86rf230: Stop leaking skb's
  selftests/zram: Skip max_comp_streams interface on newer kernel
  selftests/zram01.sh: Fix compression ratio calculation
  selftests/zram: Adapt the situation that /dev/zram0 is being used
  ax25: improve the incomplete fix to avoid UAF and NPD bugs
  vfs: make freeze_super abort when sync_filesystem returns error
  quota: make dquot_quota_sync return errors from ->sync_fs
  Revert "module, async: async_synchronize_full() on module init iff async is 
used"
  iwlwifi: fix use-after-free
  drm/radeon: 

[Kernel-packages] [Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen

[Robert Schlabbach]

My "prime suspect" is this commit:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b

Also see Linus' comments when this patch was submitted to the mainline kernel:
https://www.spinics.net/lists/kernel/msg4223720.html

"that might be a big deal slowing things down at boot time.
[...]
Comments? Maybe this is a "just apply it, see if somebody screams" situation?"

>From what I understand, other measures taken in the kernel and modules
make this issue no longer occur, so my hypothesis is that this may not
have caused issues in the current kernel. So the mistake was that
Canonical backported this commit to a very old kernel version that
kernel.org no longer maintains...

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

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.15.0-177-generic, my machine
  completely freezes on the Ubuntu Welcome screen, i.e. right after
  switching to GUI mode. The mouse pointer is frozen, the keyboard does
  not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows
  no reaction.

  I cannot work with my machine at this point and have to hard reset it.

  Selecting advanced boot options in grub and selecting the previous
  linux kernel 4.15.0-176 makes it work again. So this bad bug was
  introduced with the 4.15.0-177 kernel release.

  I tried removing the nvidia-driver-510 package, presumably making
  Ubuntu use the "nouveau" driver, and with that, I could use the
  welcome screen and log in, but the machine still froze shortly
  afterwards.

  So maybe this is some sort of interference with my GeForce 1080
  graphics card, but it is not specific to the driver used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
  Uname: Linux 4.15.0-176-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2082 F.... pulseaudio
   /dev/snd/controlC0:  robert 2082 F.... pulseaudio
   /dev/snd/controlC2:  robert 2082 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 12 13:36:28 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-29 (2386 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Supermicro Super Server
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic 
root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-176-generic N/A
   linux-backports-modules-4.15.0-176-generic  N/A
   linux-firmware  1.173.21
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago)
  dmi.bios.date: 09/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11SAE
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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


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

[Kernel-packages] [Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen

[Robert Schlabbach]

I have found a change between 176 and 177 that looks suspicious:

diff -upr --color 176/linux-source-4.15.0/kernel/module.c 
177/linux-source-4.15.0/kernel/module.c
--- 176/linux-source-4.15.0/kernel/module.c 2022-03-29 19:39:48.0 
+0200
+++ 177/linux-source-4.15.0/kernel/module.c 2022-04-14 22:22:50.0 
+0200
@@ -3520,22 +3514,13 @@ static noinline int do_init_module(struc
 
-   /*
-* We need to finish all async code before the module init sequence
-* is done.  This has potential to deadlock.  For example, a newly
-* detected block device can trigger request_module() of the
-* default iosched from async probing task.  Once userland helper
-* reaches here, async_synchronize_full() will wait on the async
-* task waiting on request_module() and deadlock.
-*
-* This deadlock is avoided by perfomring async_synchronize_full()
-* iff module init queued any async jobs.  This isn't a full
-* solution as it will deadlock the same if module loading from
-* async jobs nests more than once; however, due to the various
-* constraints, this hack seems to be the best option for now.
-* Please refer to the following thread for details.
-*
-* http://thread.gmane.org/gmane.linux.kernel/1420814
-*/
-   if (!mod->async_probe_requested && (current->flags & PF_USED_ASYNC))
+   /*
+* We need to finish all async code before the module init sequence
+* is done. This has potential to deadlock if synchronous module
+* loading is requested from async (which is not allowed!).
+*
+* See commit 0fdff3ec6d87 ("async, kmod: warn on synchronous
+* request_module() from async workers") for more details.
+*/
+   if (!mod->async_probe_requested)
async_synchronize_full();

Maybe this is the deadlock we're all running into...?

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

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.15.0-177-generic, my machine
  completely freezes on the Ubuntu Welcome screen, i.e. right after
  switching to GUI mode. The mouse pointer is frozen, the keyboard does
  not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows
  no reaction.

  I cannot work with my machine at this point and have to hard reset it.

  Selecting advanced boot options in grub and selecting the previous
  linux kernel 4.15.0-176 makes it work again. So this bad bug was
  introduced with the 4.15.0-177 kernel release.

  I tried removing the nvidia-driver-510 package, presumably making
  Ubuntu use the "nouveau" driver, and with that, I could use the
  welcome screen and log in, but the machine still froze shortly
  afterwards.

  So maybe this is some sort of interference with my GeForce 1080
  graphics card, but it is not specific to the driver used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
  Uname: Linux 4.15.0-176-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2082 F pulseaudio
   /dev/snd/controlC0:  robert 2082 F pulseaudio
   /dev/snd/controlC2:  robert 2082 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 12 13:36:28 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-29 (2386 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Supermicro Super Server
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic 
root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-176-generic N/A
   linux-backports-modules-4.15.0-176-generic  N/A
   linux-firmware  1.173.21
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago)
  dmi.bios.date: 09/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11SAE
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.famil

[Kernel-packages] [Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen

[Robert Schlabbach]

Trying to isolate the issue, I:

1. Booted my portable Ubuntu 18.04.6 installation on a different machine
(different CPU, chipset, but still Intel). On the other machine, kernel
4.15.0-177 booted without issues, so apparently it does not depend on
the installation, but rather on the hardware or BIOS whether the freeze
occurs or not.

2. Replaced the entire /lib/modules/4.15.0-177-generic/ with the
contents from /lib/modules/4.15.0-176-generic/ and rebuilt initramfs.
This did NOT cure the freezes (only caused a lot of module signature
errors, confirming that the modules really were replaced). So whatever
is causing the freezes is not in one of loadable modules, but rather
within the kernel itself or the builtin modules.

Still, the 176-to-177 diff over the builtin modules is HUGE... :-/

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

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.15.0-177-generic, my machine
  completely freezes on the Ubuntu Welcome screen, i.e. right after
  switching to GUI mode. The mouse pointer is frozen, the keyboard does
  not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows
  no reaction.

  I cannot work with my machine at this point and have to hard reset it.

  Selecting advanced boot options in grub and selecting the previous
  linux kernel 4.15.0-176 makes it work again. So this bad bug was
  introduced with the 4.15.0-177 kernel release.

  I tried removing the nvidia-driver-510 package, presumably making
  Ubuntu use the "nouveau" driver, and with that, I could use the
  welcome screen and log in, but the machine still froze shortly
  afterwards.

  So maybe this is some sort of interference with my GeForce 1080
  graphics card, but it is not specific to the driver used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
  Uname: Linux 4.15.0-176-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2082 F pulseaudio
   /dev/snd/controlC0:  robert 2082 F pulseaudio
   /dev/snd/controlC2:  robert 2082 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 12 13:36:28 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-29 (2386 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Supermicro Super Server
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic 
root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-176-generic N/A
   linux-backports-modules-4.15.0-176-generic  N/A
   linux-firmware  1.173.21
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago)
  dmi.bios.date: 09/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11SAE
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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


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

[Kernel-packages] [Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen

[Robert Schlabbach]

Alas! I spoke to seen. The seeming "workaround" only lasted for one
boot, and after that, the ~180 seconds delay is back to stay, although
the Intel IOMMU is still disabled.

So this issue is "sporadic". Maybe even a race condition... :(

And maybe not even related to the intel-lpss driver: The line:

"intel-lpss :00:15.0: enabling device ( -> 0002)"

seems to come from drivers/pci/setup-res.c:

if (cmd != old_cmd) {
dev_info(>dev, "enabling device (%04x -> %04x)\n",
 old_cmd, cmd);
pci_write_config_word(dev, PCI_COMMAND, cmd);
}

So it just enables the PCI device, which at some point leads to
drivers/mfd/intel-lpss.c#intel_lpss_probe() being called which requests
the DMA module leading to drivers/dma/idma64.c#idma64_probe() being
called which finally outputs:

dev_info(chip->dev, "Found Intel integrated DMA 64-bit\n");

So a lot of code between these two log lines:

[6.439056] intel-lpss :00:15.0: enabling device ( -> 0002)
[  187.141427] idma64 idma64.0: Found Intel integrated DMA 64-bit

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

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.15.0-177-generic, my machine
  completely freezes on the Ubuntu Welcome screen, i.e. right after
  switching to GUI mode. The mouse pointer is frozen, the keyboard does
  not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows
  no reaction.

  I cannot work with my machine at this point and have to hard reset it.

  Selecting advanced boot options in grub and selecting the previous
  linux kernel 4.15.0-176 makes it work again. So this bad bug was
  introduced with the 4.15.0-177 kernel release.

  I tried removing the nvidia-driver-510 package, presumably making
  Ubuntu use the "nouveau" driver, and with that, I could use the
  welcome screen and log in, but the machine still froze shortly
  afterwards.

  So maybe this is some sort of interference with my GeForce 1080
  graphics card, but it is not specific to the driver used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
  Uname: Linux 4.15.0-176-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2082 F pulseaudio
   /dev/snd/controlC0:  robert 2082 F pulseaudio
   /dev/snd/controlC2:  robert 2082 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 12 13:36:28 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-29 (2386 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Supermicro Super Server
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic 
root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-176-generic N/A
   linux-backports-modules-4.15.0-176-generic  N/A
   linux-firmware  1.173.21
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago)
  dmi.bios.date: 09/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11SAE
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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


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

[Kernel-packages] [Bug 1973234] Re: Slow Boot, No SOUND, No Ethernet

[Robert Schlabbach]

When the machine is booted, open a terminal and run "dmesg" to see on
what the kernel was stuck so long. In my case, it was the intel-lpss PCI
device initialization, and I fixed it by disabling the Intel IOMMU. If
you get similar results, this issue might be a duplicate of mine which I
reported here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167

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

Title:
  Slow Boot, No SOUND, No Ethernet

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I would like to report the latest kernel update: 4.15.0.177.166 to my
  Linux Mint 19.1 systems displayed the following problems:

  1. After Update - Boot process is VERY SLOW.
  2. After Update - Once desktop comes up, mouse and keyboard are disabled for 
approx. 2 minutes.
  3. All sound is totally disabled (gone) on the system and the device under 
Sound reports as "Dummy Output".
  4. On another system with a USB-C to RJ45 Ethernet external connection dongle 
- the device was disabled, but could be re-detected, by removing and 
re-plugging into the USB-C port. This is not previously how it has operated.

  After having these issues on multiple machines, I restored the
  system(s) to the previous kernel 4.15.0-176-generic with Timeshift
  without issue, correcting all issues listed above.

  I believe this is a major issue(s) for the kernel and it's users and
  it needs to be addressed A.S.A.P.

  System Particulars:

  System:Host: mic-Aspire-E5-576G Kernel: 4.15.0-176-generic x86_64 bits: 
64 compiler: gcc v: 7.5.0 
 Desktop: Cinnamon 4.0.10 wm: muffin 4.0.7 dm: LightDM 1.26.0 
Distro: Linux Mint 19.1 Tessa 
 base: Ubuntu 18.04 bionic 
  Machine:   Type: Laptop System: Acer product: Aspire E5-576G v: V1.47 serial: 
 
 Mobo: KBL model: Ironman_SK v: V1.47 serial:  UEFI: Insyde 
v: 1.47 date: 09/06/2018 
  Battery:   ID-1: BAT1 charge: 34.3 Wh condition: 34.3/62.2 Wh (55%) volts: 
12.7/11.1 
 model: PANASONIC AS16B5J type: Li-ion serial:  status: 
Full 
 Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard 
K400 serial:  
 charge: 100% rechargeable: yes status: Discharging 
  CPU:   Topology: Quad Core model: Intel Core i5-8250U bits: 64 type: MT 
MCP arch: Kaby Lake rev: A 
 L2 cache: 6144 KiB 
 flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 
28800 
 Speed: 700 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 700 2: 
700 3: 700 4: 709 5: 706 
 6: 700 7: 720 8: 700 
  Graphics:  Device-1: Intel UHD Graphics 620 vendor: Acer Incorporated ALI 
driver: i915 v: kernel 
 bus ID: 00:02.0 chip ID: 8086:5917 
 Device-2: NVIDIA GP108M [GeForce MX150] vendor: Acer Incorporated 
ALI driver: N/A 
 bus ID: 01:00.0 chip ID: 10de:1d10 
 Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: 
fbdev,vesa 
 resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (KBL GT2) v: 4.6 
Mesa 20.0.8 compat-v: 3.0 
 direct render: Yes 
  Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Acer 
Incorporated ALI driver: snd_hda_intel 
 v: kernel bus ID: 00:1f.3 chip ID: 8086:9d71 
 Sound Server: ALSA v: k4.15.0-176-generic 
  Network:   Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: 
iwlwifi v: kernel port: 4000 
 bus ID: 03:00.0 chip ID: 8086:24fb 
 IF: wlp3s0 state: down mac:  
 Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Acer Incorporated ALI 
 driver: r8169 v: 2.3LK-NAPI port: 3000 bus ID: 04:00.1 chip ID: 
10ec:8168 
 IF: enp4s0f1 state: up speed: 1000 Mbps duplex: full mac:  
  Drives:Local Storage: total: 912.89 GiB used: 172.01 GiB (18.8%) 
 ID-1: /dev/sda vendor: SanDisk model: Ultra II 480GB size: 447.13 
GiB speed: 6.0 Gb/s 
 serial:  rev: 20RL scheme: GPT 
 ID-2: /dev/sdb vendor: Crucial model: CT500MX500SSD4 size: 465.76 
GiB speed: 6.0 Gb/s 
 serial:  rev: 023 scheme: MBR 
  Partition: ID-1: / size: 438.62 GiB used: 113.17 GiB (25.8%) fs: ext4 dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 46.5 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Repos: No active apt repos in: /etc/apt/sources.list 
 Active apt repos in: 
/etc/apt/sources.list.d/alex-p-aegisub-bionic.list 
 1: deb http://ppa.launchpad.net/alex-p/aegisub/ubuntu bionic main
 2: deb-src http://ppa.launchpad.net/alex-p/aegisub/ubuntu bionic 
main
 Active apt repos in: 
/etc/apt/sources.list.d/audio-recorder-ppa-bionic.list 
 1: deb http://ppa.launchpad.net/audio-recorder/ppa/ubuntu bionic 
main
 

[Kernel-packages] [Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen

[Robert Schlabbach]

After grepping dmesg for all lines about the "00:15" devices, I found
two lines starting with "DMAR:", which made me think of another machine
running debian which had issues with DMAR: devices that were related to
the Intel IOMMU.

So I tried the workaround I knew from there:

Edit /etc/default/grub and add "intel_iommu=off" to the
GRUB_CMDLINE_LINUX_DEFAULT value, then run "sudo update-grub" to update
the grub configuration and reboot.

and voila, intel-lpss initializes within a few milliseconds again:

[6.518592] intel-lpss :00:15.0: enabling device ( -> 0002)
[6.560693] idma64 idma64.0: Found Intel integrated DMA 64-bit
[6.569509] intel-lpss :00:15.1: enabling device ( -> 0002)
[6.569691] idma64 idma64.1: Found Intel integrated DMA 64-bit
[6.574164] mei_me :00:16.0: enabling device ( -> 0002)

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID= ro 
intel_iommu=off

So some change between 4.15.0-176 and 4.15.0-177 seemingly broke the
Intel IOMMU. Question is whether it was a formerly "dormant" BIOS bug
that was only unveiled by some change, or whether it is a newly
introduced Linux bug that broke Intel IOMMU support...

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

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.15.0-177-generic, my machine
  completely freezes on the Ubuntu Welcome screen, i.e. right after
  switching to GUI mode. The mouse pointer is frozen, the keyboard does
  not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows
  no reaction.

  I cannot work with my machine at this point and have to hard reset it.

  Selecting advanced boot options in grub and selecting the previous
  linux kernel 4.15.0-176 makes it work again. So this bad bug was
  introduced with the 4.15.0-177 kernel release.

  I tried removing the nvidia-driver-510 package, presumably making
  Ubuntu use the "nouveau" driver, and with that, I could use the
  welcome screen and log in, but the machine still froze shortly
  afterwards.

  So maybe this is some sort of interference with my GeForce 1080
  graphics card, but it is not specific to the driver used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
  Uname: Linux 4.15.0-176-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2082 F pulseaudio
   /dev/snd/controlC0:  robert 2082 F pulseaudio
   /dev/snd/controlC2:  robert 2082 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 12 13:36:28 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-29 (2386 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Supermicro Super Server
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic 
root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-176-generic N/A
   linux-backports-modules-4.15.0-176-generic  N/A
   linux-firmware  1.173.21
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago)
  dmi.bios.date: 09/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11SAE
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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


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

[Kernel-packages] [Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen

[Robert Schlabbach]

After finding someone reporting the same issue
(https://forums.linuxmint.com/viewtopic.php?t=373747=2175201) and
reading that the machine may come alive after a while, I found that
indeed after 3 minutes the machine works. dmesg that reveals that it
seemingly was the initialization of the intel_lpss driver that took 3
minutes:

[6.889189] intel-lpss :00:15.0: enabling device ( -> 0002)
[7.112397] input: PC Speaker as /devices/platform/pcspkr/input/input5
[7.220480] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms 
ovfl timer
[7.220481] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[7.220481] RAPL PMU: hw unit of domain package 2^-14 Joules
[7.220482] RAPL PMU: hw unit of domain dram 2^-14 Joules
[7.220482] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[7.220483] RAPL PMU: hw unit of domain psys 2^-14 Joules
[9.882380] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[   10.068162] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[   10.070009] IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready
[   10.115669] IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready
[   10.117735] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[   10.61] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[   14.114836] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
Rx/Tx
[   14.114883] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[   15.14] atlantic: link change old 0 new 1000
[   15.200150] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
[  187.423062] intel-lpss :00:15.1: enabling device ( -> 0002)
[  187.432242] mei_me :00:16.0: enabling device ( -> 0002)
[  187.432264] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[  187.441672] AVX2 version of gcm_enc/dec engaged.
[  187.441673] AES CTR mode by8 optimization enabled
[  187.445619] idma64 idma64.0: Found Intel integrated DMA 64-bit
[  187.452528] idma64 idma64.1: Found Intel integrated DMA 64-bit

Note these lines:
[6.889189] intel-lpss :00:15.0: enabling device ( -> 0002)
[  187.423062] intel-lpss :00:15.1: enabling device ( -> 0002)
[  187.432242] mei_me :00:16.0: enabling device ( -> 0002)
[  187.445619] idma64 idma64.0: Found Intel integrated DMA 64-bit
[  187.452528] idma64 idma64.1: Found Intel integrated DMA 64-bit

For comparison, the same lines from the 4.15.0-176 dmesg:

[6.321873] intel-lpss :00:15.0: enabling device ( -> 0002)
[6.340549] idma64 idma64.0: Found Intel integrated DMA 64-bit
[6.345409] intel-lpss :00:15.1: enabling device ( -> 0002)
[6.345610] idma64 idma64.1: Found Intel integrated DMA 64-bit
[6.350618] mei_me :00:16.0: enabling device ( -> 0002)

So the initialization time increased from 30ms of 180s, i.e. by a factor
of 6,000. This cannot be right.

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

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.15.0-177-generic, my machine
  completely freezes on the Ubuntu Welcome screen, i.e. right after
  switching to GUI mode. The mouse pointer is frozen, the keyboard does
  not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows
  no reaction.

  I cannot work with my machine at this point and have to hard reset it.

  Selecting advanced boot options in grub and selecting the previous
  linux kernel 4.15.0-176 makes it work again. So this bad bug was
  introduced with the 4.15.0-177 kernel release.

  I tried removing the nvidia-driver-510 package, presumably making
  Ubuntu use the "nouveau" driver, and with that, I could use the
  welcome screen and log in, but the machine still froze shortly
  afterwards.

  So maybe this is some sort of interference with my GeForce 1080
  graphics card, but it is not specific to the driver used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
  Uname: Linux 4.15.0-176-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2082 F.... pulseaudio
   /dev/snd/controlC0:  robert 2082 F.... pulseaudio
   /dev/snd/controlC2:  robert 2082 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 12 13:36:28 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-29 (2386 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Supermicro Super Server
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot

[Kernel-packages] [Bug 1973167] [NEW] linux-image-4.15.0-177-generic freezes on the welcome screen

[Robert Schlabbach]

Public bug reported:

After updating to linux-image-4.15.0-177-generic, my machine completely
freezes on the Ubuntu Welcome screen, i.e. right after switching to GUI
mode. The mouse pointer is frozen, the keyboard does not even respond to
CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows no reaction.

I cannot work with my machine at this point and have to hard reset it.

Selecting advanced boot options in grub and selecting the previous linux
kernel 4.15.0-176 makes it work again. So this bad bug was introduced
with the 4.15.0-177 kernel release.

I tried removing the nvidia-driver-510 package, presumably making Ubuntu
use the "nouveau" driver, and with that, I could use the welcome screen
and log in, but the machine still froze shortly afterwards.

So maybe this is some sort of interference with my GeForce 1080 graphics
card, but it is not specific to the driver used.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
Uname: Linux 4.15.0-176-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  robert 2082 F pulseaudio
 /dev/snd/controlC0:  robert 2082 F pulseaudio
 /dev/snd/controlC2:  robert 2082 F pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu May 12 13:36:28 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-10-29 (2386 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Supermicro Super Server
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic 
root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-176-generic N/A
 linux-backports-modules-4.15.0-176-generic  N/A
 linux-firmware  1.173.21
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago)
dmi.bios.date: 09/18/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X11SAE
dmi.board.vendor: Supermicro
dmi.board.version: 1.01
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Super Server
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

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


** Tags: amd64 apport-bug bionic

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

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

Status in linux package in Ubuntu:
  New

Bug description:
  After updating to linux-image-4.15.0-177-generic, my machine
  completely freezes on the Ubuntu Welcome screen, i.e. right after
  switching to GUI mode. The mouse pointer is frozen, the keyboard does
  not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows
  no reaction.

  I cannot work with my machine at this point and have to hard reset it.

  Selecting advanced boot options in grub and selecting the previous
  linux kernel 4.15.0-176 makes it work again. So this bad bug was
  introduced with the 4.15.0-177 kernel release.

  I tried removing the nvidia-driver-510 package, presumably making
  Ubuntu use the "nouveau" driver, and with that, I could use the
  welcome screen and log in, but the machine still froze shortly
  afterwards.

  So maybe this is some sort of interference with my GeForce 1080
  graphics card, but it is not specific to the driver used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
  Uname: Linux 4.15.0-176-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2082 F pulseaudio
   /dev/snd/controlC0:  robert 2082 F pulseaudio
   /dev/snd/controlC2:  robert 2082 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 12 13:36:28 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-29 (2386 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Supermicro Super Server
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic 
root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a5

[Kernel-packages] [Bug 1969633] Re: Continuous Bluetooth timeouts [Broadcom BCM20702A]

[Robert Pearson]

So how do I get Canonical to fix the kernel bug? How do I notify them of
the bug?

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

Title:
  Continuous Bluetooth timeouts [Broadcom BCM20702A]

Status in linux-hwe-5.13 package in Ubuntu:
  New

Bug description:
  My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable
  USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron
  K7 Bluetooth "keyboard".

  The Bluetooth manager finds the K480 but pairing always fails. The
  keyboard flashes blue but dongle steady blue.

  The K7 does not even show up. (But then the "keyboard" does not even
  work using a USB cable.)

  Bought dongle and K480 4 years ago, never got them to work at all,
  gave up as a bad investment.

  I ordered a K7 wireless keyboard. What I received was a Bluetooth
  keyboard. Bluetooth does not work. Plugging it in with a USB cable
  partially works (function keys and End key do not work).

  Got the K480 working with my Samsung Galaxy 5 Android tablet, but not
  with my computer. I want Bluetooth but do not know how to get it to
  work. It still does not work after 4 years of cold boots and the
  replacement of the power supply.

  I went to the Keychron Facebook Linux group. They were complaining
  that Ubuntu does not support Bluetooth and that the Keychron function
  keys do not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Wed Apr 20 10:45:57 2022
  InstallationDate: Installed on 2022-03-05 (46 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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


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

[Kernel-packages] [Bug 1969633] [NEW] Bluetooth not connecting

[Robert Pearson]

Public bug reported:

My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB
2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7
Bluetooth "keyboard".

The Bluetooth manager finds the K480 but pairing always fails. The
keyboard flashes blue but dongle steady blue.

The K7 does not even show up. (But then the "keyboard" does not even
work using a USB cable.)

Bought dongle and K480 4 years ago, never got them to work at all, gave
up as a bad investment.

I ordered a K7 wireless keyboard. What I received was a Bluetooth
keyboard. Bluetooth does not work. Plugging it in with a USB cable
partially works (function keys and End key do not work).

Got the K480 working with my Samsung Galaxy 5 Android tablet, but not
with my computer. I want Bluetooth but do not know how to get it to
work. It still does not work after 4 years of cold boots and the
replacement of the power supply.

I went to the Keychron Facebook Linux group. They were complaining that
Ubuntu does not support Bluetooth and that the Keychron function keys do
not work.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Wed Apr 20 10:45:57 2022
InstallationDate: Installed on 2022-03-05 (46 days ago)
InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1301
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A88XM-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
hciconfig:
 
rfkill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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


** Tags: amd64 apport-bug focal

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

Title:
  Bluetooth not connecting

Status in bluez package in Ubuntu:
  New

Bug description:
  My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable
  USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron
  K7 Bluetooth "keyboard".

  The Bluetooth manager finds the K480 but pairing always fails. The
  keyboard flashes blue but dongle steady blue.

  The K7 does not even show up. (But then the "keyboard" does not even
  work using a USB cable.)

  Bought dongle and K480 4 years ago, never got them to work at all,
  gave up as a bad investment.

  I ordered a K7 wireless keyboard. What I received was a Bluetooth
  keyboard. Bluetooth does not work. Plugging it in with a USB cable
  partially works (function keys and End key do not work).

  Got the K480 working with my Samsung Galaxy 5 Android tablet, but not
  with my computer. I want Bluetooth but do not know how to get it to
  work. It still does not work after 4 years of cold boots and the
  replacement of the power supply.

  I went to the Keychron Facebook Linux group. They were complaining
  that Ubuntu does not support Bluetooth and that the Keychron function
  keys do not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Wed Apr 20 10:45:57 2022
  InstallationDate: Installed on 2022-03-05 (46 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh 

[Kernel-packages] [Bug 1802821] Re: Serious design flaw using large external drives.

[Robert Pearson]

I read that Paragon Software NTFS drivers will be part of the 3.5
kernel. I would like to use NTFS so that other computers can actually
read my data.

The current drives I'm using are 8 TB Seagate external drives with a 2
year warranty. Their price went up to $150 when on sale. I will probably
get a Seagate Exos x18 18 TB drive for 2 times the cost and 2.25 times
the capacity and 2.5 times the warranty period. (Also greater MTBF and
annual data usage.)

It would be nice if Ubuntu could access an 18 TB drive with an NTFS at
greater than continental drift speeds.

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

Title:
  Serious design flaw using large external drives.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am trying to recover data from an HFS+ files system on a 4TB
  external USB 3 drive. Copying 3TB from the 4TB HFS+ drive to a 4TB
  NTFS drive using MATE Terminal cp -anR from to took 2 days.

  When I try to copy the same data to a 6TB NTFS USB 3 drive the results
  are glacial. 750GB has taken over 6 days. Obviously there is a problem
  of scale drive in Ubuntu MATE. I invite the developers to plug in a
  12TB drive and see just how glacial (no - not glacial, more on the
  order of plate techtonics) slow their design is.

  Robert Pearson

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2102 F pulseaudio
   /dev/snd/controlC0:  robert 2102 F pulseaudio
  CurrentDesktop: MATE
  Date: Sun Nov 11 23:50:13 2018
  HibernationDevice: RESUME=UUID=aa95f07d-f769-44ca-8b33-0c5b3c78bdeb
  InstallationDate: Installed on 2018-10-25 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=26dc3ca5-f3ae-47eb-92b6-4f02ed5ba4f0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Kernel-packages] [Bug 1950250] Re: Ubuntu MATE 20.04.3 something is Caja is badly broken

[Robert Pearson]

apport information

** Tags added: apport-collected

** Description changed:

  Caja is part of the Ubuntu MATE package but apparently unsupported.
  
  Caja after the latest update takes minutes to open a menu and it takes 3
  times to open files with Eye of MATE.
  
  Nautilus has similar problems but is not as slow. But then it crashes.
  
  How do I get Caja fixed?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Nov  9 00:43:41 2021
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.21
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2022-03-05 (33 days ago)
+ InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
+ Package: caja 1.24.0-1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
+ Tags:  focal
+ Uname: Linux 5.13.0-35-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1950250/+attachment/5578012/+files/Dependencies.txt

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

Title:
  Ubuntu MATE 20.04.3 something is Caja is badly broken

Status in caja package in Ubuntu:
  Incomplete
Status in linux-signed-hwe-5.11 package in Ubuntu:
  Invalid

Bug description:
  Caja is part of the Ubuntu MATE package but apparently unsupported.

  Caja after the latest update takes minutes to open a menu and it takes
  3 times to open files with Eye of MATE.

  Nautilus has similar problems but is not as slow. But then it crashes.

  How do I get Caja fixed?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Nov  9 00:43:41 2021
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (33 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Package: caja 1.24.0-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-35-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/caja/+bug/1950250/+subscriptions


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

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

[Robert Pearson]

apport information

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

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

Title:
  Ubuntu MATE 20.04.3 something is Caja is badly broken

Status in caja package in Ubuntu:
  Incomplete
Status in linux-signed-hwe-5.11 package in Ubuntu:
  Invalid

Bug description:
  Caja is part of the Ubuntu MATE package but apparently unsupported.

  Caja after the latest update takes minutes to open a menu and it takes
  3 times to open files with Eye of MATE.

  Nautilus has similar problems but is not as slow. But then it crashes.

  How do I get Caja fixed?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Nov  9 00:43:41 2021
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (33 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Package: caja 1.24.0-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-35-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/caja/+bug/1950250/+subscriptions


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

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

[Robert Pearson]

apport information

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

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

Title:
  Ubuntu MATE 20.04.3 something is Caja is badly broken

Status in caja package in Ubuntu:
  Incomplete
Status in linux-signed-hwe-5.11 package in Ubuntu:
  Invalid

Bug description:
  Caja is part of the Ubuntu MATE package but apparently unsupported.

  Caja after the latest update takes minutes to open a menu and it takes
  3 times to open files with Eye of MATE.

  Nautilus has similar problems but is not as slow. But then it crashes.

  How do I get Caja fixed?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Nov  9 00:43:41 2021
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (33 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Package: caja 1.24.0-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-35-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/caja/+bug/1950250/+subscriptions


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

[Kernel-packages] [Bug 1967434] [NEW] nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build

[Robert McDowell Hammer]

Public bug reported:

I attempted an upgrade a few weeks ago and have been receiving repeated
errors since.  I'm not sure what version I upgraded to or where to find
that information, but this may be the upgrade error listed on the
previous page of reported bugs.

I am operating Ubuntu 20.04.2 LTS.

I apologize for my limited knowledge.  I am a Windows Refugee, who
migrated before forced obsolescence of Windows 7.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.13.0-39-generic
Date: Wed Mar 30 15:07:03 2022
DuplicateSignature: 
dkms:nvidia-dkms-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23:
 error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state 
*)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct 
drm_plane_state *)’ [-Werror=incompatible-pointer-types]
InstallationDate: Installed on 2021-03-06 (390 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageVersion: 460.73.01-0ubuntu0.20.04.1
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: nvidia-graphics-drivers-460
Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed 
to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-460 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module
  failed to build

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New

Bug description:
  I attempted an upgrade a few weeks ago and have been receiving
  repeated errors since.  I'm not sure what version I upgraded to or
  where to find that information, but this may be the upgrade error
  listed on the previous page of reported bugs.

  I am operating Ubuntu 20.04.2 LTS.

  I apologize for my limited knowledge.  I am a Windows Refugee, who
  migrated before forced obsolescence of Windows 7.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.13.0-39-generic
  Date: Wed Mar 30 15:07:03 2022
  DuplicateSignature: 
dkms:nvidia-dkms-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23:
 error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state 
*)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct 
drm_plane_state *)’ [-Werror=incompatible-pointer-types]
  InstallationDate: Installed on 2021-03-06 (390 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageVersion: 460.73.01-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: nvidia-graphics-drivers-460
  Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

[Robert Pearson]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1940724/+attachment/5573095/+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/1940724

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

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

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

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

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1940724/+attachment/5573088/+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/1940724

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1940724/+attachment/5573089/+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/1940724

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

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

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1940724/+attachment/5573098/+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/1940724

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1940724/+attachment/5573097/+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/1940724

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Kernel-packages] [Bug 1940724] Re: 20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

[Robert Pearson]

apport-collect 1940724
dpkg-query: no packages found matching linux

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

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

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

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1940724/+attachment/5573086/+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/1940724

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

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

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

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

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

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

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1940724/+attachment/5573087/+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/1940724

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

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

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Kernel-packages] [Bug 1940724] IwConfig.txt

[Robert Pearson]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1940724/+attachment/5573084/+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/1940724

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

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

[Robert Pearson]

apport information

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

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 1572 F pulseaudio
   /dev/snd/controlC0:  robert 1572 F pulseaudio
   /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-03-05 (21 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-35-generic N/A
   linux-backports-modules-5.13.0-35-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Kernel-packages] [Bug 1940724] Re: 20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

[Robert Pearson]

apport information

** Tags added: apport-collected

** Description changed:

  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.
  
  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.
  
  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner app.
  It finds the scanner but cannot connect to it to actually scan.
  
  Apparently, something is wrong with connecting a scanner with a USB
  cable.
  
  If you need more information, please tell me how to get it and send it
  to you.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.21
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  robert 1572 F pulseaudio
+  /dev/snd/controlC0:  robert 1572 F pulseaudio
+  /dev/snd/pcmC0D3p:   robert 1572 F...m pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2022-03-05 (21 days ago)
+ InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
+ MachineType: System manufacturer System Product Name
+ Package: linux (not installed)
+ ProcFB: 0 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash
+ ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
+ RelatedPackageVersions:
+  linux-restricted-modules-5.13.0-35-generic N/A
+  linux-backports-modules-5.13.0-35-generic  N/A
+  linux-firmware 1.187.29
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  focal
+ Uname: Linux 5.13.0-35-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/01/2014
+ dmi.bios.release: 4.6
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1301
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: A88XM-A
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev X.0x
+ dmi.chassis.asset.tag: Asset-1234567890
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Chassis Manufacture
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: System Product Name
+ dmi.product.sku: SKU
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1940724/+attachment/5573081/+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/1940724

Title:
  20.04.2 does not connect HP OfficeJet Pro 7740 scanner via USB2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am trying Ubuntu MATE 20.04.2 to see what works and what is broken.

  My scanner is an HP OfficeJet Pro 7740 scanner connected to my ASUS
  A88XM-A motherboard via USB2 cable.

  With previous releases, I use VueScan Pro. Work fine. With 20.04.2 it
  cannot find my scanner at all. I tried the bundled Document Scanner
  app. It finds the scanner but cannot connect to it to actually scan.

  Apparently, something is wrong with connecting a scanner with a USB
  cable.

  If you need more information, please tell me how to get it and send it
  to you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Fri Aug 20 18:56:53 2021
  InstallationDate: Installed on 2021-04-17 (125 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release a

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

[Robert Mantel]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1965571/+attachment/5570617/+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/1965571

Title:
  No video after wake after S3 suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No video after wake after S3 suspend.

  System:
Kernel: 5.4.0-104-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una 
base: Ubuntu 20.04 focal 
  Machine:
Type: Desktop Mobo: MSI model: B75MA-E33 (MS-7808) v: 1.0 serial:  
UEFI: American Megatrends v: 1.7 date: 09/30/2013 
  CPU:
Topology: Quad Core model: Intel Core i7-3770 bits: 64 type: MT MCP 
arch: Ivy Bridge rev: 9 L2 cache: 8192 KiB 
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54277 
Speed: 3783 MHz min/max: 1600/3900 MHz Core speeds (MHz): 1: 3831 2: 3830 
3: 3711 4: 3708 5: 3781 6: 3767 7: 3712 8: 3733 
  Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: nvidia 
v: 470.103.01 bus ID: 01:00.0 
Display: x11 server: X.Org 1.20.13 driver: nvidia 
resolution: 3840x2160~30Hz 
OpenGL: renderer: NVIDIA GeForce GT 710/PCIe/SSE2 
v: 4.6.0 NVIDIA 470.103.01 direct render: Yes 
  Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio 
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ZOTAC driver: snd_hda_intel 
v: kernel bus ID: 01:00.1 
Device-3: Logitech Cisco VTCamera3 type: USB 
driver: snd-usb-audio,uvcvideo bus ID: 3-3:2 
Sound Server: ALSA v: k5.4.0-104-generic 
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 03:00.0 
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:  
  Drives:
Local Storage: total: 1.02 TiB used: 237.57 GiB (22.8%) 
ID-1: /dev/sda vendor: SanDisk model: SDSSDA120G size: 111.79 GiB 
ID-2: /dev/sdb vendor: Western Digital model: WD10EFRX-68JCSN0 
size: 931.51 GiB 
  Partition:
ID-1: / size: 101.29 GiB used: 79.81 GiB (78.8%) fs: ext4 dev: /dev/dm-0 
ID-2: swap-1 size: 7.87 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1 
  Sensors:
System Temperatures: cpu: 56.0 C mobo: N/A gpu: nvidia temp: 66 C 
Fan Speeds (RPM): N/A gpu: nvidia fan: 40% 
  Info:
Processes: 297 Uptime: 19m Memory: 7.70 GiB used: 3.07 GiB (39.9%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 Shell: bash v: 5.0.17 
inxi: 3.0.38
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rob1472 F pulseaudio
   /dev/snd/controlC1:  rob1472 F pulseaudio
   /dev/snd/controlC0:  rob1472 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  HibernationDevice: RESUME=UUID=7db2e63c-841b-43bb-99fb-dc011ce044cc
  InstallationDate: Installed on 2019-05-13 (1040 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: MSI MS-7808
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic 
root=/dev/mapper/mint--vg-root ro acpi_osi=! "acpi_osi=Windows 2012" quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-104-generic N/A
   linux-backports-modules-5.4.0-104-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   
  Tags:  una
  Uname: Linux 5.4.0-104-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75MA-E33 (MS-7808)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/30/2013:svnMSI:pnMS-7808:pvr1.0:rvnMSI:rnB75MA-E33(MS-7808):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7808
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:

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

[Robert Mantel]

apport information

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

Title:
  No video after wake after S3 suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No video after wake after S3 suspend.

  System:
Kernel: 5.4.0-104-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una 
base: Ubuntu 20.04 focal 
  Machine:
Type: Desktop Mobo: MSI model: B75MA-E33 (MS-7808) v: 1.0 serial:  
UEFI: American Megatrends v: 1.7 date: 09/30/2013 
  CPU:
Topology: Quad Core model: Intel Core i7-3770 bits: 64 type: MT MCP 
arch: Ivy Bridge rev: 9 L2 cache: 8192 KiB 
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54277 
Speed: 3783 MHz min/max: 1600/3900 MHz Core speeds (MHz): 1: 3831 2: 3830 
3: 3711 4: 3708 5: 3781 6: 3767 7: 3712 8: 3733 
  Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: nvidia 
v: 470.103.01 bus ID: 01:00.0 
Display: x11 server: X.Org 1.20.13 driver: nvidia 
resolution: 3840x2160~30Hz 
OpenGL: renderer: NVIDIA GeForce GT 710/PCIe/SSE2 
v: 4.6.0 NVIDIA 470.103.01 direct render: Yes 
  Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio 
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ZOTAC driver: snd_hda_intel 
v: kernel bus ID: 01:00.1 
Device-3: Logitech Cisco VTCamera3 type: USB 
driver: snd-usb-audio,uvcvideo bus ID: 3-3:2 
Sound Server: ALSA v: k5.4.0-104-generic 
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 03:00.0 
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:  
  Drives:
Local Storage: total: 1.02 TiB used: 237.57 GiB (22.8%) 
ID-1: /dev/sda vendor: SanDisk model: SDSSDA120G size: 111.79 GiB 
ID-2: /dev/sdb vendor: Western Digital model: WD10EFRX-68JCSN0 
size: 931.51 GiB 
  Partition:
ID-1: / size: 101.29 GiB used: 79.81 GiB (78.8%) fs: ext4 dev: /dev/dm-0 
ID-2: swap-1 size: 7.87 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1 
  Sensors:
System Temperatures: cpu: 56.0 C mobo: N/A gpu: nvidia temp: 66 C 
Fan Speeds (RPM): N/A gpu: nvidia fan: 40% 
  Info:
Processes: 297 Uptime: 19m Memory: 7.70 GiB used: 3.07 GiB (39.9%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 Shell: bash v: 5.0.17 
inxi: 3.0.38
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rob1472 F pulseaudio
   /dev/snd/controlC1:  rob1472 F pulseaudio
   /dev/snd/controlC0:  rob1472 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  HibernationDevice: RESUME=UUID=7db2e63c-841b-43bb-99fb-dc011ce044cc
  InstallationDate: Installed on 2019-05-13 (1040 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: MSI MS-7808
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic 
root=/dev/mapper/mint--vg-root ro acpi_osi=! "acpi_osi=Windows 2012" quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-104-generic N/A
   linux-backports-modules-5.4.0-104-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   
  Tags:  una
  Uname: Linux 5.4.0-104-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75MA-E33 (MS-7808)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/30/2013:svnMSI:pnMS-7808:pvr1.0:rvnMSI:rnB75MA-E33(MS-7808):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7808
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


-- 
Mailing list: 

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

[Robert Mantel]

apport information

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

Title:
  No video after wake after S3 suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No video after wake after S3 suspend.

  System:
Kernel: 5.4.0-104-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una 
base: Ubuntu 20.04 focal 
  Machine:
Type: Desktop Mobo: MSI model: B75MA-E33 (MS-7808) v: 1.0 serial:  
UEFI: American Megatrends v: 1.7 date: 09/30/2013 
  CPU:
Topology: Quad Core model: Intel Core i7-3770 bits: 64 type: MT MCP 
arch: Ivy Bridge rev: 9 L2 cache: 8192 KiB 
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54277 
Speed: 3783 MHz min/max: 1600/3900 MHz Core speeds (MHz): 1: 3831 2: 3830 
3: 3711 4: 3708 5: 3781 6: 3767 7: 3712 8: 3733 
  Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: nvidia 
v: 470.103.01 bus ID: 01:00.0 
Display: x11 server: X.Org 1.20.13 driver: nvidia 
resolution: 3840x2160~30Hz 
OpenGL: renderer: NVIDIA GeForce GT 710/PCIe/SSE2 
v: 4.6.0 NVIDIA 470.103.01 direct render: Yes 
  Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio 
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ZOTAC driver: snd_hda_intel 
v: kernel bus ID: 01:00.1 
Device-3: Logitech Cisco VTCamera3 type: USB 
driver: snd-usb-audio,uvcvideo bus ID: 3-3:2 
Sound Server: ALSA v: k5.4.0-104-generic 
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 03:00.0 
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:  
  Drives:
Local Storage: total: 1.02 TiB used: 237.57 GiB (22.8%) 
ID-1: /dev/sda vendor: SanDisk model: SDSSDA120G size: 111.79 GiB 
ID-2: /dev/sdb vendor: Western Digital model: WD10EFRX-68JCSN0 
size: 931.51 GiB 
  Partition:
ID-1: / size: 101.29 GiB used: 79.81 GiB (78.8%) fs: ext4 dev: /dev/dm-0 
ID-2: swap-1 size: 7.87 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1 
  Sensors:
System Temperatures: cpu: 56.0 C mobo: N/A gpu: nvidia temp: 66 C 
Fan Speeds (RPM): N/A gpu: nvidia fan: 40% 
  Info:
Processes: 297 Uptime: 19m Memory: 7.70 GiB used: 3.07 GiB (39.9%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 Shell: bash v: 5.0.17 
inxi: 3.0.38
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rob1472 F pulseaudio
   /dev/snd/controlC1:  rob1472 F pulseaudio
   /dev/snd/controlC0:  rob1472 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  HibernationDevice: RESUME=UUID=7db2e63c-841b-43bb-99fb-dc011ce044cc
  InstallationDate: Installed on 2019-05-13 (1040 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: MSI MS-7808
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic 
root=/dev/mapper/mint--vg-root ro acpi_osi=! "acpi_osi=Windows 2012" quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-104-generic N/A
   linux-backports-modules-5.4.0-104-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   
  Tags:  una
  Uname: Linux 5.4.0-104-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75MA-E33 (MS-7808)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/30/2013:svnMSI:pnMS-7808:pvr1.0:rvnMSI:rnB75MA-E33(MS-7808):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7808
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


-- 
Mailing list: 

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

[Robert Mantel]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1965571/+attachment/5570608/+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/1965571

Title:
  No video after wake after S3 suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No video after wake after S3 suspend.

  System:
Kernel: 5.4.0-104-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una 
base: Ubuntu 20.04 focal 
  Machine:
Type: Desktop Mobo: MSI model: B75MA-E33 (MS-7808) v: 1.0 serial:  
UEFI: American Megatrends v: 1.7 date: 09/30/2013 
  CPU:
Topology: Quad Core model: Intel Core i7-3770 bits: 64 type: MT MCP 
arch: Ivy Bridge rev: 9 L2 cache: 8192 KiB 
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54277 
Speed: 3783 MHz min/max: 1600/3900 MHz Core speeds (MHz): 1: 3831 2: 3830 
3: 3711 4: 3708 5: 3781 6: 3767 7: 3712 8: 3733 
  Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: nvidia 
v: 470.103.01 bus ID: 01:00.0 
Display: x11 server: X.Org 1.20.13 driver: nvidia 
resolution: 3840x2160~30Hz 
OpenGL: renderer: NVIDIA GeForce GT 710/PCIe/SSE2 
v: 4.6.0 NVIDIA 470.103.01 direct render: Yes 
  Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio 
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ZOTAC driver: snd_hda_intel 
v: kernel bus ID: 01:00.1 
Device-3: Logitech Cisco VTCamera3 type: USB 
driver: snd-usb-audio,uvcvideo bus ID: 3-3:2 
Sound Server: ALSA v: k5.4.0-104-generic 
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 03:00.0 
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:  
  Drives:
Local Storage: total: 1.02 TiB used: 237.57 GiB (22.8%) 
ID-1: /dev/sda vendor: SanDisk model: SDSSDA120G size: 111.79 GiB 
ID-2: /dev/sdb vendor: Western Digital model: WD10EFRX-68JCSN0 
size: 931.51 GiB 
  Partition:
ID-1: / size: 101.29 GiB used: 79.81 GiB (78.8%) fs: ext4 dev: /dev/dm-0 
ID-2: swap-1 size: 7.87 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1 
  Sensors:
System Temperatures: cpu: 56.0 C mobo: N/A gpu: nvidia temp: 66 C 
Fan Speeds (RPM): N/A gpu: nvidia fan: 40% 
  Info:
Processes: 297 Uptime: 19m Memory: 7.70 GiB used: 3.07 GiB (39.9%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 Shell: bash v: 5.0.17 
inxi: 3.0.38
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rob1472 F pulseaudio
   /dev/snd/controlC1:  rob1472 F pulseaudio
   /dev/snd/controlC0:  rob1472 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  HibernationDevice: RESUME=UUID=7db2e63c-841b-43bb-99fb-dc011ce044cc
  InstallationDate: Installed on 2019-05-13 (1040 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: MSI MS-7808
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic 
root=/dev/mapper/mint--vg-root ro acpi_osi=! "acpi_osi=Windows 2012" quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-104-generic N/A
   linux-backports-modules-5.4.0-104-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   
  Tags:  una
  Uname: Linux 5.4.0-104-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75MA-E33 (MS-7808)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/30/2013:svnMSI:pnMS-7808:pvr1.0:rvnMSI:rnB75MA-E33(MS-7808):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7808
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


-- 
Mailing list: 

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

[Robert Mantel]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1965571/+attachment/5570614/+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/1965571

Title:
  No video after wake after S3 suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No video after wake after S3 suspend.

  System:
Kernel: 5.4.0-104-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una 
base: Ubuntu 20.04 focal 
  Machine:
Type: Desktop Mobo: MSI model: B75MA-E33 (MS-7808) v: 1.0 serial:  
UEFI: American Megatrends v: 1.7 date: 09/30/2013 
  CPU:
Topology: Quad Core model: Intel Core i7-3770 bits: 64 type: MT MCP 
arch: Ivy Bridge rev: 9 L2 cache: 8192 KiB 
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54277 
Speed: 3783 MHz min/max: 1600/3900 MHz Core speeds (MHz): 1: 3831 2: 3830 
3: 3711 4: 3708 5: 3781 6: 3767 7: 3712 8: 3733 
  Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: nvidia 
v: 470.103.01 bus ID: 01:00.0 
Display: x11 server: X.Org 1.20.13 driver: nvidia 
resolution: 3840x2160~30Hz 
OpenGL: renderer: NVIDIA GeForce GT 710/PCIe/SSE2 
v: 4.6.0 NVIDIA 470.103.01 direct render: Yes 
  Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio 
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ZOTAC driver: snd_hda_intel 
v: kernel bus ID: 01:00.1 
Device-3: Logitech Cisco VTCamera3 type: USB 
driver: snd-usb-audio,uvcvideo bus ID: 3-3:2 
Sound Server: ALSA v: k5.4.0-104-generic 
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 03:00.0 
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:  
  Drives:
Local Storage: total: 1.02 TiB used: 237.57 GiB (22.8%) 
ID-1: /dev/sda vendor: SanDisk model: SDSSDA120G size: 111.79 GiB 
ID-2: /dev/sdb vendor: Western Digital model: WD10EFRX-68JCSN0 
size: 931.51 GiB 
  Partition:
ID-1: / size: 101.29 GiB used: 79.81 GiB (78.8%) fs: ext4 dev: /dev/dm-0 
ID-2: swap-1 size: 7.87 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1 
  Sensors:
System Temperatures: cpu: 56.0 C mobo: N/A gpu: nvidia temp: 66 C 
Fan Speeds (RPM): N/A gpu: nvidia fan: 40% 
  Info:
Processes: 297 Uptime: 19m Memory: 7.70 GiB used: 3.07 GiB (39.9%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 Shell: bash v: 5.0.17 
inxi: 3.0.38
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rob1472 F pulseaudio
   /dev/snd/controlC1:  rob1472 F pulseaudio
   /dev/snd/controlC0:  rob1472 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  HibernationDevice: RESUME=UUID=7db2e63c-841b-43bb-99fb-dc011ce044cc
  InstallationDate: Installed on 2019-05-13 (1040 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: MSI MS-7808
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic 
root=/dev/mapper/mint--vg-root ro acpi_osi=! "acpi_osi=Windows 2012" quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-104-generic N/A
   linux-backports-modules-5.4.0-104-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   
  Tags:  una
  Uname: Linux 5.4.0-104-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75MA-E33 (MS-7808)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/30/2013:svnMSI:pnMS-7808:pvr1.0:rvnMSI:rnB75MA-E33(MS-7808):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7808
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


-- 
Mailing list: 

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

[Robert Mantel]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1965571/+attachment/5570616/+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/1965571

Title:
  No video after wake after S3 suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No video after wake after S3 suspend.

  System:
Kernel: 5.4.0-104-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una 
base: Ubuntu 20.04 focal 
  Machine:
Type: Desktop Mobo: MSI model: B75MA-E33 (MS-7808) v: 1.0 serial:  
UEFI: American Megatrends v: 1.7 date: 09/30/2013 
  CPU:
Topology: Quad Core model: Intel Core i7-3770 bits: 64 type: MT MCP 
arch: Ivy Bridge rev: 9 L2 cache: 8192 KiB 
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54277 
Speed: 3783 MHz min/max: 1600/3900 MHz Core speeds (MHz): 1: 3831 2: 3830 
3: 3711 4: 3708 5: 3781 6: 3767 7: 3712 8: 3733 
  Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: nvidia 
v: 470.103.01 bus ID: 01:00.0 
Display: x11 server: X.Org 1.20.13 driver: nvidia 
resolution: 3840x2160~30Hz 
OpenGL: renderer: NVIDIA GeForce GT 710/PCIe/SSE2 
v: 4.6.0 NVIDIA 470.103.01 direct render: Yes 
  Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio 
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ZOTAC driver: snd_hda_intel 
v: kernel bus ID: 01:00.1 
Device-3: Logitech Cisco VTCamera3 type: USB 
driver: snd-usb-audio,uvcvideo bus ID: 3-3:2 
Sound Server: ALSA v: k5.4.0-104-generic 
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 03:00.0 
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:  
  Drives:
Local Storage: total: 1.02 TiB used: 237.57 GiB (22.8%) 
ID-1: /dev/sda vendor: SanDisk model: SDSSDA120G size: 111.79 GiB 
ID-2: /dev/sdb vendor: Western Digital model: WD10EFRX-68JCSN0 
size: 931.51 GiB 
  Partition:
ID-1: / size: 101.29 GiB used: 79.81 GiB (78.8%) fs: ext4 dev: /dev/dm-0 
ID-2: swap-1 size: 7.87 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1 
  Sensors:
System Temperatures: cpu: 56.0 C mobo: N/A gpu: nvidia temp: 66 C 
Fan Speeds (RPM): N/A gpu: nvidia fan: 40% 
  Info:
Processes: 297 Uptime: 19m Memory: 7.70 GiB used: 3.07 GiB (39.9%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 Shell: bash v: 5.0.17 
inxi: 3.0.38
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rob1472 F pulseaudio
   /dev/snd/controlC1:  rob1472 F pulseaudio
   /dev/snd/controlC0:  rob1472 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  HibernationDevice: RESUME=UUID=7db2e63c-841b-43bb-99fb-dc011ce044cc
  InstallationDate: Installed on 2019-05-13 (1040 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: MSI MS-7808
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic 
root=/dev/mapper/mint--vg-root ro acpi_osi=! "acpi_osi=Windows 2012" quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-104-generic N/A
   linux-backports-modules-5.4.0-104-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   
  Tags:  una
  Uname: Linux 5.4.0-104-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75MA-E33 (MS-7808)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/30/2013:svnMSI:pnMS-7808:pvr1.0:rvnMSI:rnB75MA-E33(MS-7808):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7808
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


-- 
Mailing list: 

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

[Robert Mantel]

apport information

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

Title:
  No video after wake after S3 suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No video after wake after S3 suspend.

  System:
Kernel: 5.4.0-104-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una 
base: Ubuntu 20.04 focal 
  Machine:
Type: Desktop Mobo: MSI model: B75MA-E33 (MS-7808) v: 1.0 serial:  
UEFI: American Megatrends v: 1.7 date: 09/30/2013 
  CPU:
Topology: Quad Core model: Intel Core i7-3770 bits: 64 type: MT MCP 
arch: Ivy Bridge rev: 9 L2 cache: 8192 KiB 
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54277 
Speed: 3783 MHz min/max: 1600/3900 MHz Core speeds (MHz): 1: 3831 2: 3830 
3: 3711 4: 3708 5: 3781 6: 3767 7: 3712 8: 3733 
  Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: nvidia 
v: 470.103.01 bus ID: 01:00.0 
Display: x11 server: X.Org 1.20.13 driver: nvidia 
resolution: 3840x2160~30Hz 
OpenGL: renderer: NVIDIA GeForce GT 710/PCIe/SSE2 
v: 4.6.0 NVIDIA 470.103.01 direct render: Yes 
  Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio 
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ZOTAC driver: snd_hda_intel 
v: kernel bus ID: 01:00.1 
Device-3: Logitech Cisco VTCamera3 type: USB 
driver: snd-usb-audio,uvcvideo bus ID: 3-3:2 
Sound Server: ALSA v: k5.4.0-104-generic 
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 03:00.0 
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:  
  Drives:
Local Storage: total: 1.02 TiB used: 237.57 GiB (22.8%) 
ID-1: /dev/sda vendor: SanDisk model: SDSSDA120G size: 111.79 GiB 
ID-2: /dev/sdb vendor: Western Digital model: WD10EFRX-68JCSN0 
size: 931.51 GiB 
  Partition:
ID-1: / size: 101.29 GiB used: 79.81 GiB (78.8%) fs: ext4 dev: /dev/dm-0 
ID-2: swap-1 size: 7.87 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1 
  Sensors:
System Temperatures: cpu: 56.0 C mobo: N/A gpu: nvidia temp: 66 C 
Fan Speeds (RPM): N/A gpu: nvidia fan: 40% 
  Info:
Processes: 297 Uptime: 19m Memory: 7.70 GiB used: 3.07 GiB (39.9%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 Shell: bash v: 5.0.17 
inxi: 3.0.38
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rob1472 F pulseaudio
   /dev/snd/controlC1:  rob1472 F pulseaudio
   /dev/snd/controlC0:  rob1472 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  HibernationDevice: RESUME=UUID=7db2e63c-841b-43bb-99fb-dc011ce044cc
  InstallationDate: Installed on 2019-05-13 (1040 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: MSI MS-7808
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic 
root=/dev/mapper/mint--vg-root ro acpi_osi=! "acpi_osi=Windows 2012" quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-104-generic N/A
   linux-backports-modules-5.4.0-104-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   
  Tags:  una
  Uname: Linux 5.4.0-104-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75MA-E33 (MS-7808)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/30/2013:svnMSI:pnMS-7808:pvr1.0:rvnMSI:rnB75MA-E33(MS-7808):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7808
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


-- 
Mailing list: 

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

[Robert Mantel]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1965571/+attachment/5570606/+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/1965571

Title:
  No video after wake after S3 suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No video after wake after S3 suspend.

  System:
Kernel: 5.4.0-104-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una 
base: Ubuntu 20.04 focal 
  Machine:
Type: Desktop Mobo: MSI model: B75MA-E33 (MS-7808) v: 1.0 serial:  
UEFI: American Megatrends v: 1.7 date: 09/30/2013 
  CPU:
Topology: Quad Core model: Intel Core i7-3770 bits: 64 type: MT MCP 
arch: Ivy Bridge rev: 9 L2 cache: 8192 KiB 
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54277 
Speed: 3783 MHz min/max: 1600/3900 MHz Core speeds (MHz): 1: 3831 2: 3830 
3: 3711 4: 3708 5: 3781 6: 3767 7: 3712 8: 3733 
  Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: nvidia 
v: 470.103.01 bus ID: 01:00.0 
Display: x11 server: X.Org 1.20.13 driver: nvidia 
resolution: 3840x2160~30Hz 
OpenGL: renderer: NVIDIA GeForce GT 710/PCIe/SSE2 
v: 4.6.0 NVIDIA 470.103.01 direct render: Yes 
  Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio 
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ZOTAC driver: snd_hda_intel 
v: kernel bus ID: 01:00.1 
Device-3: Logitech Cisco VTCamera3 type: USB 
driver: snd-usb-audio,uvcvideo bus ID: 3-3:2 
Sound Server: ALSA v: k5.4.0-104-generic 
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 03:00.0 
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:  
  Drives:
Local Storage: total: 1.02 TiB used: 237.57 GiB (22.8%) 
ID-1: /dev/sda vendor: SanDisk model: SDSSDA120G size: 111.79 GiB 
ID-2: /dev/sdb vendor: Western Digital model: WD10EFRX-68JCSN0 
size: 931.51 GiB 
  Partition:
ID-1: / size: 101.29 GiB used: 79.81 GiB (78.8%) fs: ext4 dev: /dev/dm-0 
ID-2: swap-1 size: 7.87 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1 
  Sensors:
System Temperatures: cpu: 56.0 C mobo: N/A gpu: nvidia temp: 66 C 
Fan Speeds (RPM): N/A gpu: nvidia fan: 40% 
  Info:
Processes: 297 Uptime: 19m Memory: 7.70 GiB used: 3.07 GiB (39.9%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 Shell: bash v: 5.0.17 
inxi: 3.0.38
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rob1472 F pulseaudio
   /dev/snd/controlC1:  rob1472 F pulseaudio
   /dev/snd/controlC0:  rob1472 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  HibernationDevice: RESUME=UUID=7db2e63c-841b-43bb-99fb-dc011ce044cc
  InstallationDate: Installed on 2019-05-13 (1040 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: MSI MS-7808
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic 
root=/dev/mapper/mint--vg-root ro acpi_osi=! "acpi_osi=Windows 2012" quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-104-generic N/A
   linux-backports-modules-5.4.0-104-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   
  Tags:  una
  Uname: Linux 5.4.0-104-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75MA-E33 (MS-7808)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/30/2013:svnMSI:pnMS-7808:pvr1.0:rvnMSI:rnB75MA-E33(MS-7808):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7808
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


-- 
Mailing list: 

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

[Robert Mantel]

apport information

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

Title:
  No video after wake after S3 suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No video after wake after S3 suspend.

  System:
Kernel: 5.4.0-104-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una 
base: Ubuntu 20.04 focal 
  Machine:
Type: Desktop Mobo: MSI model: B75MA-E33 (MS-7808) v: 1.0 serial:  
UEFI: American Megatrends v: 1.7 date: 09/30/2013 
  CPU:
Topology: Quad Core model: Intel Core i7-3770 bits: 64 type: MT MCP 
arch: Ivy Bridge rev: 9 L2 cache: 8192 KiB 
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54277 
Speed: 3783 MHz min/max: 1600/3900 MHz Core speeds (MHz): 1: 3831 2: 3830 
3: 3711 4: 3708 5: 3781 6: 3767 7: 3712 8: 3733 
  Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: nvidia 
v: 470.103.01 bus ID: 01:00.0 
Display: x11 server: X.Org 1.20.13 driver: nvidia 
resolution: 3840x2160~30Hz 
OpenGL: renderer: NVIDIA GeForce GT 710/PCIe/SSE2 
v: 4.6.0 NVIDIA 470.103.01 direct render: Yes 
  Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio 
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ZOTAC driver: snd_hda_intel 
v: kernel bus ID: 01:00.1 
Device-3: Logitech Cisco VTCamera3 type: USB 
driver: snd-usb-audio,uvcvideo bus ID: 3-3:2 
Sound Server: ALSA v: k5.4.0-104-generic 
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 03:00.0 
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:  
  Drives:
Local Storage: total: 1.02 TiB used: 237.57 GiB (22.8%) 
ID-1: /dev/sda vendor: SanDisk model: SDSSDA120G size: 111.79 GiB 
ID-2: /dev/sdb vendor: Western Digital model: WD10EFRX-68JCSN0 
size: 931.51 GiB 
  Partition:
ID-1: / size: 101.29 GiB used: 79.81 GiB (78.8%) fs: ext4 dev: /dev/dm-0 
ID-2: swap-1 size: 7.87 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1 
  Sensors:
System Temperatures: cpu: 56.0 C mobo: N/A gpu: nvidia temp: 66 C 
Fan Speeds (RPM): N/A gpu: nvidia fan: 40% 
  Info:
Processes: 297 Uptime: 19m Memory: 7.70 GiB used: 3.07 GiB (39.9%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 Shell: bash v: 5.0.17 
inxi: 3.0.38
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rob1472 F pulseaudio
   /dev/snd/controlC1:  rob1472 F pulseaudio
   /dev/snd/controlC0:  rob1472 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  HibernationDevice: RESUME=UUID=7db2e63c-841b-43bb-99fb-dc011ce044cc
  InstallationDate: Installed on 2019-05-13 (1040 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: MSI MS-7808
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic 
root=/dev/mapper/mint--vg-root ro acpi_osi=! "acpi_osi=Windows 2012" quiet 
splash
  ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-104-generic N/A
   linux-backports-modules-5.4.0-104-generic  N/A
   linux-firmware 1.187.29
  RfKill:
   
  Tags:  una
  Uname: Linux 5.4.0-104-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75MA-E33 (MS-7808)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/30/2013:svnMSI:pnMS-7808:pvr1.0:rvnMSI:rnB75MA-E33(MS-7808):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7808
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


-- 
Mailing list: