[Kernel-packages] [Bug 1956467] Re: powerlight stays on after shutdown

[Aïré]

Kernel 5.13.0-25 is always bad

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

Title:
  powerlight stays on after shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After kernel upgrade from 5.11.0.40 to versions 5.11.0.41, 5.11.0.43,
  5.11.0.44 power-button light fails to switch off, after shutdown.

  shutdown can be triggered from command line or via desktop menu,
  result is the same. After rebooting from 5.11.0.40 normal
  functionality is restored.

  systemd appears to complete shutdown looking at the logs (see
  attached)

  Switching to suspend mode (sleep) functions as expected (power light blinks) 
and stays permanently on after wake-up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christian   1896 F pulseaudio
   /dev/snd/controlC0:  christian   1896 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-06 (609 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81MT
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-40-generic N/A
   linux-backports-modules-5.11.0-40-generic  N/A
   linux-firmware 1.187.24
  Tags:  focal
  Uname: Linux 5.11.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/09/2019
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8ZCN23WW(V2.02)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V145-15AST
  dmi.ec.firmware.release: 2.23
  dmi.modalias: 
dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST:
  dmi.product.family: V145-15AST
  dmi.product.name: 81MT
  dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST
  dmi.product.version: Lenovo V145-15AST
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1956413] Re: Intel EHL: Two of the on-board ethernet ports don't work

[Anthony Wong]

Confirmed with Kent Lin, he has verified the proposed kernel on an
Elkhart Lake board, the problem is fixed.

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

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

Title:
  Intel EHL: Two of the on-board ethernet ports don't work

Status in HWE Next:
  New
Status in linux-intel-5.13 package in Ubuntu:
  Triaged
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  == Impact ==
  Only one of the three on-board ethernet ports works. The other two can't get 
IP addresses.

  == Fix ==
  commit 884d2b845477cd0a18302444dc20fe2d9a01743e
  Author: David Wu 
  Date:   Mon Dec 13 19:15:15 2021 +0800

  net: stmmac: Add GFP_DMA32 for rx buffers if no 64 capability
  
  Use page_pool_alloc_pages instead of page_pool_dev_alloc_pages, which
  can give the gfp parameter, in the case of not supporting 64-bit width,
  using 32-bit address memory can reduce a copy from swiotlb.
  
  Signed-off-by: David Wu 
  Signed-off-by: David S. Miller 

  == Risk of Regression ==
  Low. The commit changes gfp parameter only when there's no 64-bit capability, 
and it is already in mainline.

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


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

[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo

[Benjamin Burns]

And one more tool that might help you get a more reliable repro:
https://github.com/HexHive/USBFuzz - likely would need modification to
target this specific problem, however. More details here:
https://www.usenix.org/conference/usenixsecurity20/presentation/peng

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

Title:
  null pointer dereference in uvcvideo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a logitech c920 webcam. When using this camera in obs-studio
  v23.x, all of my USB devices stop working and I see the following in
  my kernel log:

  [  590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd
  [  592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, 
bcdDevice= 0.11
  [  592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=1
  [  592.660925] usb 3-3: Product: HD Pro Webcam C920
  [  592.660928] usb 3-3: SerialNumber: 2EAD866F
  [  592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d)
  [  592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not 
initialized!
  [  592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not 
initialized!
  [  592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not 
initialized!
  [  592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not 
initialized!
  [  592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not 
initialized!
  [  592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not 
initialized!
  [  592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not 
initialized!
  [  592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not 
initialized!
  [  592.22] input: HD Pro Webcam C920 as 
/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23
  [  748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd
  [  938.125745] usb 3-3: USB disconnect, device number 5
  [  943.298530] BUG: unable to handle kernel NULL pointer dereference at 

  [  943.298533] #PF error: [normal kernel read fault]
  [  943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 
  [  943.298536] Oops:  [#1] SMP PTI
  [  943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P   OE 
5.0.0-13-generic #14-Ubuntu
  [  943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, 
BIOS F7 01/20/2014
  [  943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60
  [  943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 
48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 
0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48
  [  943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202
  [  943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 
0004
  [  943.298547] RDX:  RSI: 0001 RDI: 
a1070ad0a800
  [  943.298548] RBP: bdae493dbab0 R08: 00027040 R09: 
b57825b8
  [  943.298549] R10: fba45fce4bc0 R11: 0001 R12: 

  [  943.298550] R13: a10644187b98 R14: ff92 R15: 
a1075131a000
  [  943.298551] FS:  7f93c40d7700() GS:a1075ea0() 
knlGS:
  [  943.298552] CS:  0010 DS:  ES:  CR0: 80050033
  [  943.298553] CR2:  CR3: 0006f8a94004 CR4: 
001606f0
  [  943.298553] Call Trace:
  [  943.298557]  usb_hcd_alloc_bandwidth+0x241/0x370
  [  943.298559]  usb_set_interface+0xfc/0x380
  [  943.298565]  uvc_video_start_transfer+0x155/0x4b0 [uvcvideo]
  [  943.298568]  uvc_video_start_streaming+0x7f/0xd0 [uvcvideo]
  [  943.298570]  uvc_start_streaming+0x28/0x70 [uvcvideo]
  [  943.298573]  vb2_start_streaming+0x6d/0x110 [videobuf2_common]
  [  943.298575]  vb2_core_streamon+0x59/0xc0 [videobuf2_common]
  [  943.298578]  vb2_streamon+0x18/0x30 [videobuf2_v4l2]
  [  943.298580]  uvc_queue_streamon+0x2e/0x50 [uvcvideo]
  [  943.298582]  uvc_ioctl_streamon+0x3f/0x60 [uvcvideo]
  [  943.298588]  v4l_streamon+0x20/0x30 [videodev]
  [  943.298592]  __video_do_ioctl+0x19a/0x3f0 [videodev]
  [  943.298596]  video_usercopy+0x1a6/0x660 [videodev]
  [  943.298599]  ? v4l_s_fmt+0x630/0x630 [videodev]
  [  943.298603]  video_ioctl2+0x15/0x20 [videodev]
  [  943.298606]  v4l2_ioctl+0x49/0x50 [videodev]
  [  943.298608]  do_vfs_ioctl+0xa9/0x640
  [  943.298610]  ? __switch_to_asm+0x34/0x70
  [  943.298611]  ? __switch_to_asm+0x40/0x70
  [  943.298612]  ? __switch_to_asm+0x34/0x70
  [  943.298612]  ? __switch_to_asm+0x40/0x70
  [  943.298613]  ? __switch_to_asm+0x34/0x70
  [  943.298614]  ? __switch_to_asm+0x40/0x70
  [  943.298615]  ? __switch_to_asm+0x34/0x70
  [  943.298616]  ? __switch_to_asm+0x40/0x70
  [  943.298617]  ksys_ioctl+0x67/0x90
  [  

[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo

[Benjamin Burns]

Ah, I suppose I could try booting off of a Live USB.

It'd be a fair amount of effort, but if you're looking for a more
reliable test jig, you might try using a Teensy 2.0++ or similar.
They've been used in the past for similar purposes (e.g.
https://fail0verflow.com/blog/2014/hubcap-chromecast-root-pt1/), as they
allow very low-level access to their USB interface.

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

Title:
  null pointer dereference in uvcvideo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a logitech c920 webcam. When using this camera in obs-studio
  v23.x, all of my USB devices stop working and I see the following in
  my kernel log:

  [  590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd
  [  592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, 
bcdDevice= 0.11
  [  592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=1
  [  592.660925] usb 3-3: Product: HD Pro Webcam C920
  [  592.660928] usb 3-3: SerialNumber: 2EAD866F
  [  592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d)
  [  592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not 
initialized!
  [  592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not 
initialized!
  [  592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not 
initialized!
  [  592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not 
initialized!
  [  592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not 
initialized!
  [  592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not 
initialized!
  [  592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not 
initialized!
  [  592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not 
initialized!
  [  592.22] input: HD Pro Webcam C920 as 
/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23
  [  748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd
  [  938.125745] usb 3-3: USB disconnect, device number 5
  [  943.298530] BUG: unable to handle kernel NULL pointer dereference at 

  [  943.298533] #PF error: [normal kernel read fault]
  [  943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 
  [  943.298536] Oops:  [#1] SMP PTI
  [  943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P   OE 
5.0.0-13-generic #14-Ubuntu
  [  943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, 
BIOS F7 01/20/2014
  [  943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60
  [  943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 
48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 
0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48
  [  943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202
  [  943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 
0004
  [  943.298547] RDX:  RSI: 0001 RDI: 
a1070ad0a800
  [  943.298548] RBP: bdae493dbab0 R08: 00027040 R09: 
b57825b8
  [  943.298549] R10: fba45fce4bc0 R11: 0001 R12: 

  [  943.298550] R13: a10644187b98 R14: ff92 R15: 
a1075131a000
  [  943.298551] FS:  7f93c40d7700() GS:a1075ea0() 
knlGS:
  [  943.298552] CS:  0010 DS:  ES:  CR0: 80050033
  [  943.298553] CR2:  CR3: 0006f8a94004 CR4: 
001606f0
  [  943.298553] Call Trace:
  [  943.298557]  usb_hcd_alloc_bandwidth+0x241/0x370
  [  943.298559]  usb_set_interface+0xfc/0x380
  [  943.298565]  uvc_video_start_transfer+0x155/0x4b0 [uvcvideo]
  [  943.298568]  uvc_video_start_streaming+0x7f/0xd0 [uvcvideo]
  [  943.298570]  uvc_start_streaming+0x28/0x70 [uvcvideo]
  [  943.298573]  vb2_start_streaming+0x6d/0x110 [videobuf2_common]
  [  943.298575]  vb2_core_streamon+0x59/0xc0 [videobuf2_common]
  [  943.298578]  vb2_streamon+0x18/0x30 [videobuf2_v4l2]
  [  943.298580]  uvc_queue_streamon+0x2e/0x50 [uvcvideo]
  [  943.298582]  uvc_ioctl_streamon+0x3f/0x60 [uvcvideo]
  [  943.298588]  v4l_streamon+0x20/0x30 [videodev]
  [  943.298592]  __video_do_ioctl+0x19a/0x3f0 [videodev]
  [  943.298596]  video_usercopy+0x1a6/0x660 [videodev]
  [  943.298599]  ? v4l_s_fmt+0x630/0x630 [videodev]
  [  943.298603]  video_ioctl2+0x15/0x20 [videodev]
  [  943.298606]  v4l2_ioctl+0x49/0x50 [videodev]
  [  943.298608]  do_vfs_ioctl+0xa9/0x640
  [  943.298610]  ? __switch_to_asm+0x34/0x70
  [  943.298611]  ? __switch_to_asm+0x40/0x70
  [  943.298612]  ? __switch_to_asm+0x34/0x70
  [  943.298612]  ? __switch_to_asm+0x40/0x70
  [  943.298613]  ? __switch_to_asm+0x34/0x70
  [  943.298614]  ? __switch_to_asm+0x40/0x70
  [  943.298615]  ? 

[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo

[Benjamin Burns]

Unfortunately at the moment I no longer have access to a box that's
running Ubuntu (or any linux) on bare metal. I suppose I can give it a
try with USB passthrough in a VM over the weekend, perhaps?

Also it's been ages since I've built and booted a custom kernel. Does
Ubuntu have an easy method for building a patched kernel w/ official
config, or is it just like it always was - clone source tree, etc?

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

Title:
  null pointer dereference in uvcvideo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a logitech c920 webcam. When using this camera in obs-studio
  v23.x, all of my USB devices stop working and I see the following in
  my kernel log:

  [  590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd
  [  592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, 
bcdDevice= 0.11
  [  592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=1
  [  592.660925] usb 3-3: Product: HD Pro Webcam C920
  [  592.660928] usb 3-3: SerialNumber: 2EAD866F
  [  592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d)
  [  592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not 
initialized!
  [  592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not 
initialized!
  [  592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not 
initialized!
  [  592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not 
initialized!
  [  592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not 
initialized!
  [  592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not 
initialized!
  [  592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not 
initialized!
  [  592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not 
initialized!
  [  592.22] input: HD Pro Webcam C920 as 
/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23
  [  748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd
  [  938.125745] usb 3-3: USB disconnect, device number 5
  [  943.298530] BUG: unable to handle kernel NULL pointer dereference at 

  [  943.298533] #PF error: [normal kernel read fault]
  [  943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 
  [  943.298536] Oops:  [#1] SMP PTI
  [  943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P   OE 
5.0.0-13-generic #14-Ubuntu
  [  943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, 
BIOS F7 01/20/2014
  [  943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60
  [  943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 
48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 
0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48
  [  943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202
  [  943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 
0004
  [  943.298547] RDX:  RSI: 0001 RDI: 
a1070ad0a800
  [  943.298548] RBP: bdae493dbab0 R08: 00027040 R09: 
b57825b8
  [  943.298549] R10: fba45fce4bc0 R11: 0001 R12: 

  [  943.298550] R13: a10644187b98 R14: ff92 R15: 
a1075131a000
  [  943.298551] FS:  7f93c40d7700() GS:a1075ea0() 
knlGS:
  [  943.298552] CS:  0010 DS:  ES:  CR0: 80050033
  [  943.298553] CR2:  CR3: 0006f8a94004 CR4: 
001606f0
  [  943.298553] Call Trace:
  [  943.298557]  usb_hcd_alloc_bandwidth+0x241/0x370
  [  943.298559]  usb_set_interface+0xfc/0x380
  [  943.298565]  uvc_video_start_transfer+0x155/0x4b0 [uvcvideo]
  [  943.298568]  uvc_video_start_streaming+0x7f/0xd0 [uvcvideo]
  [  943.298570]  uvc_start_streaming+0x28/0x70 [uvcvideo]
  [  943.298573]  vb2_start_streaming+0x6d/0x110 [videobuf2_common]
  [  943.298575]  vb2_core_streamon+0x59/0xc0 [videobuf2_common]
  [  943.298578]  vb2_streamon+0x18/0x30 [videobuf2_v4l2]
  [  943.298580]  uvc_queue_streamon+0x2e/0x50 [uvcvideo]
  [  943.298582]  uvc_ioctl_streamon+0x3f/0x60 [uvcvideo]
  [  943.298588]  v4l_streamon+0x20/0x30 [videodev]
  [  943.298592]  __video_do_ioctl+0x19a/0x3f0 [videodev]
  [  943.298596]  video_usercopy+0x1a6/0x660 [videodev]
  [  943.298599]  ? v4l_s_fmt+0x630/0x630 [videodev]
  [  943.298603]  video_ioctl2+0x15/0x20 [videodev]
  [  943.298606]  v4l2_ioctl+0x49/0x50 [videodev]
  [  943.298608]  do_vfs_ioctl+0xa9/0x640
  [  943.298610]  ? __switch_to_asm+0x34/0x70
  [  943.298611]  ? __switch_to_asm+0x40/0x70
  [  943.298612]  ? __switch_to_asm+0x34/0x70
  [  943.298612]  ? __switch_to_asm+0x40/0x70
  [  943.298613]  ? __switch_to_asm+0x34/0x70
  [  943.298614]  ? __switch_to_asm+0x40/0x70
  

[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo

[Kai-Heng Feng]

Benjamin,

Can you please test my patch in comment #23? Thanks in advance.

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

Title:
  null pointer dereference in uvcvideo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a logitech c920 webcam. When using this camera in obs-studio
  v23.x, all of my USB devices stop working and I see the following in
  my kernel log:

  [  590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd
  [  592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, 
bcdDevice= 0.11
  [  592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=1
  [  592.660925] usb 3-3: Product: HD Pro Webcam C920
  [  592.660928] usb 3-3: SerialNumber: 2EAD866F
  [  592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d)
  [  592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not 
initialized!
  [  592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not 
initialized!
  [  592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not 
initialized!
  [  592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not 
initialized!
  [  592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not 
initialized!
  [  592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not 
initialized!
  [  592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not 
initialized!
  [  592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not 
initialized!
  [  592.22] input: HD Pro Webcam C920 as 
/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23
  [  748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd
  [  938.125745] usb 3-3: USB disconnect, device number 5
  [  943.298530] BUG: unable to handle kernel NULL pointer dereference at 

  [  943.298533] #PF error: [normal kernel read fault]
  [  943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 
  [  943.298536] Oops:  [#1] SMP PTI
  [  943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P   OE 
5.0.0-13-generic #14-Ubuntu
  [  943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, 
BIOS F7 01/20/2014
  [  943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60
  [  943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 
48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 
0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48
  [  943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202
  [  943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 
0004
  [  943.298547] RDX:  RSI: 0001 RDI: 
a1070ad0a800
  [  943.298548] RBP: bdae493dbab0 R08: 00027040 R09: 
b57825b8
  [  943.298549] R10: fba45fce4bc0 R11: 0001 R12: 

  [  943.298550] R13: a10644187b98 R14: ff92 R15: 
a1075131a000
  [  943.298551] FS:  7f93c40d7700() GS:a1075ea0() 
knlGS:
  [  943.298552] CS:  0010 DS:  ES:  CR0: 80050033
  [  943.298553] CR2:  CR3: 0006f8a94004 CR4: 
001606f0
  [  943.298553] Call Trace:
  [  943.298557]  usb_hcd_alloc_bandwidth+0x241/0x370
  [  943.298559]  usb_set_interface+0xfc/0x380
  [  943.298565]  uvc_video_start_transfer+0x155/0x4b0 [uvcvideo]
  [  943.298568]  uvc_video_start_streaming+0x7f/0xd0 [uvcvideo]
  [  943.298570]  uvc_start_streaming+0x28/0x70 [uvcvideo]
  [  943.298573]  vb2_start_streaming+0x6d/0x110 [videobuf2_common]
  [  943.298575]  vb2_core_streamon+0x59/0xc0 [videobuf2_common]
  [  943.298578]  vb2_streamon+0x18/0x30 [videobuf2_v4l2]
  [  943.298580]  uvc_queue_streamon+0x2e/0x50 [uvcvideo]
  [  943.298582]  uvc_ioctl_streamon+0x3f/0x60 [uvcvideo]
  [  943.298588]  v4l_streamon+0x20/0x30 [videodev]
  [  943.298592]  __video_do_ioctl+0x19a/0x3f0 [videodev]
  [  943.298596]  video_usercopy+0x1a6/0x660 [videodev]
  [  943.298599]  ? v4l_s_fmt+0x630/0x630 [videodev]
  [  943.298603]  video_ioctl2+0x15/0x20 [videodev]
  [  943.298606]  v4l2_ioctl+0x49/0x50 [videodev]
  [  943.298608]  do_vfs_ioctl+0xa9/0x640
  [  943.298610]  ? __switch_to_asm+0x34/0x70
  [  943.298611]  ? __switch_to_asm+0x40/0x70
  [  943.298612]  ? __switch_to_asm+0x34/0x70
  [  943.298612]  ? __switch_to_asm+0x40/0x70
  [  943.298613]  ? __switch_to_asm+0x34/0x70
  [  943.298614]  ? __switch_to_asm+0x40/0x70
  [  943.298615]  ? __switch_to_asm+0x34/0x70
  [  943.298616]  ? __switch_to_asm+0x40/0x70
  [  943.298617]  ksys_ioctl+0x67/0x90
  [  943.298619]  __x64_sys_ioctl+0x1a/0x20
  [  943.298621]  do_syscall_64+0x5a/0x110
  [  943.298622]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  943.298623] RIP: 0033:0x7f9430e082e9
  [  

[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  null pointer dereference in uvcvideo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a logitech c920 webcam. When using this camera in obs-studio
  v23.x, all of my USB devices stop working and I see the following in
  my kernel log:

  [  590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd
  [  592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, 
bcdDevice= 0.11
  [  592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=1
  [  592.660925] usb 3-3: Product: HD Pro Webcam C920
  [  592.660928] usb 3-3: SerialNumber: 2EAD866F
  [  592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d)
  [  592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not 
initialized!
  [  592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not 
initialized!
  [  592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not 
initialized!
  [  592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not 
initialized!
  [  592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not 
initialized!
  [  592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not 
initialized!
  [  592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not 
initialized!
  [  592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not 
initialized!
  [  592.22] input: HD Pro Webcam C920 as 
/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23
  [  748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd
  [  938.125745] usb 3-3: USB disconnect, device number 5
  [  943.298530] BUG: unable to handle kernel NULL pointer dereference at 

  [  943.298533] #PF error: [normal kernel read fault]
  [  943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 
  [  943.298536] Oops:  [#1] SMP PTI
  [  943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P   OE 
5.0.0-13-generic #14-Ubuntu
  [  943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, 
BIOS F7 01/20/2014
  [  943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60
  [  943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 
48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 
0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48
  [  943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202
  [  943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 
0004
  [  943.298547] RDX:  RSI: 0001 RDI: 
a1070ad0a800
  [  943.298548] RBP: bdae493dbab0 R08: 00027040 R09: 
b57825b8
  [  943.298549] R10: fba45fce4bc0 R11: 0001 R12: 

  [  943.298550] R13: a10644187b98 R14: ff92 R15: 
a1075131a000
  [  943.298551] FS:  7f93c40d7700() GS:a1075ea0() 
knlGS:
  [  943.298552] CS:  0010 DS:  ES:  CR0: 80050033
  [  943.298553] CR2:  CR3: 0006f8a94004 CR4: 
001606f0
  [  943.298553] Call Trace:
  [  943.298557]  usb_hcd_alloc_bandwidth+0x241/0x370
  [  943.298559]  usb_set_interface+0xfc/0x380
  [  943.298565]  uvc_video_start_transfer+0x155/0x4b0 [uvcvideo]
  [  943.298568]  uvc_video_start_streaming+0x7f/0xd0 [uvcvideo]
  [  943.298570]  uvc_start_streaming+0x28/0x70 [uvcvideo]
  [  943.298573]  vb2_start_streaming+0x6d/0x110 [videobuf2_common]
  [  943.298575]  vb2_core_streamon+0x59/0xc0 [videobuf2_common]
  [  943.298578]  vb2_streamon+0x18/0x30 [videobuf2_v4l2]
  [  943.298580]  uvc_queue_streamon+0x2e/0x50 [uvcvideo]
  [  943.298582]  uvc_ioctl_streamon+0x3f/0x60 [uvcvideo]
  [  943.298588]  v4l_streamon+0x20/0x30 [videodev]
  [  943.298592]  __video_do_ioctl+0x19a/0x3f0 [videodev]
  [  943.298596]  video_usercopy+0x1a6/0x660 [videodev]
  [  943.298599]  ? v4l_s_fmt+0x630/0x630 [videodev]
  [  943.298603]  video_ioctl2+0x15/0x20 [videodev]
  [  943.298606]  v4l2_ioctl+0x49/0x50 [videodev]
  [  943.298608]  do_vfs_ioctl+0xa9/0x640
  [  943.298610]  ? __switch_to_asm+0x34/0x70
  [  943.298611]  ? __switch_to_asm+0x40/0x70
  [  943.298612]  ? __switch_to_asm+0x34/0x70
  [  943.298612]  ? __switch_to_asm+0x40/0x70
  [  943.298613]  ? __switch_to_asm+0x34/0x70
  [  943.298614]  ? __switch_to_asm+0x40/0x70
  [  943.298615]  ? __switch_to_asm+0x34/0x70
  [  943.298616]  ? __switch_to_asm+0x40/0x70
  [  943.298617]  ksys_ioctl+0x67/0x90
  [  943.298619]  __x64_sys_ioctl+0x1a/0x20
  [  943.298621]  do_syscall_64+0x5a/0x110
  [  943.298622]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  943.298623] RIP: 0033:0x7f9430e082e9
  [  943.298624] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 

[Kernel-packages] [Bug 1949262] Re: Power Savings doesn't turn monitor off on NUC8i5INH

[Launchpad Bug Tracker]

[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Power Savings doesn't turn monitor off on NUC8i5INH

Status in linux package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  On previous versions of Ubuntu, after 5 minutes, my monitor would turn
  off as per settings. Since I reinstalled fresh 21.10, this is not
  happening. Screen becomes black and stays powered on.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 30 08:11:02 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / 
E9171 MCM] [1002:6987] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Lexa [Radeon 540X/550X/630 / RX 640 / E9171 
MCM] [8086:2079]
  InstallationDate: Installed on 2021-10-14 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Intel(R) Client Systems NUC8i5INH
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=1e81e0c8-99b9-447b-b8a2-2ebe4bf0eb88 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: INWHL357.0043.2021.0817.1957
  dmi.board.name: NUC8i5INB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K29935-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrINWHL357.0043.2021.0817.1957:bd08/17/2021:br5.13:svnIntel(R)ClientSystems:pnNUC8i5INH:pvrK47340-403:skuBXNUC8i5INHPA:rvnIntelCorporation:rnNUC8i5INB:rvrK29935-402:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: IN
  dmi.product.name: NUC8i5INH
  dmi.product.sku: BXNUC8i5INHPA
  dmi.product.version: K47340-403
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Kernel-packages] [Bug 1949262] Re: Power Savings doesn't turn monitor off on NUC8i5INH

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Power Savings doesn't turn monitor off on NUC8i5INH

Status in linux package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  On previous versions of Ubuntu, after 5 minutes, my monitor would turn
  off as per settings. Since I reinstalled fresh 21.10, this is not
  happening. Screen becomes black and stays powered on.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 30 08:11:02 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / 
E9171 MCM] [1002:6987] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Lexa [Radeon 540X/550X/630 / RX 640 / E9171 
MCM] [8086:2079]
  InstallationDate: Installed on 2021-10-14 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Intel(R) Client Systems NUC8i5INH
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=1e81e0c8-99b9-447b-b8a2-2ebe4bf0eb88 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: INWHL357.0043.2021.0817.1957
  dmi.board.name: NUC8i5INB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K29935-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrINWHL357.0043.2021.0817.1957:bd08/17/2021:br5.13:svnIntel(R)ClientSystems:pnNUC8i5INH:pvrK47340-403:skuBXNUC8i5INHPA:rvnIntelCorporation:rnNUC8i5INB:rvrK29935-402:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: IN
  dmi.product.name: NUC8i5INH
  dmi.product.sku: BXNUC8i5INHPA
  dmi.product.version: K47340-403
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Flickering and disforming booting into desktop both on wayland/xorg

Status in linux package in Ubuntu:
  Confirmed

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

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

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

  adding the kernel paramater intel_idle.max_cstate=4 fixed this

  i had these same bugs on this machine before:

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

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

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

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


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

[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo

[Benjamin Burns]

I wasn't aware that I could change the status of this bug. It's clear to
me from the comments above that others have observed it, so I've gone
ahead and switched it from "Expired" to "Confirmed."

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

Title:
  null pointer dereference in uvcvideo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a logitech c920 webcam. When using this camera in obs-studio
  v23.x, all of my USB devices stop working and I see the following in
  my kernel log:

  [  590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd
  [  592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, 
bcdDevice= 0.11
  [  592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=1
  [  592.660925] usb 3-3: Product: HD Pro Webcam C920
  [  592.660928] usb 3-3: SerialNumber: 2EAD866F
  [  592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d)
  [  592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not 
initialized!
  [  592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not 
initialized!
  [  592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not 
initialized!
  [  592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not 
initialized!
  [  592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not 
initialized!
  [  592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not 
initialized!
  [  592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not 
initialized!
  [  592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not 
initialized!
  [  592.22] input: HD Pro Webcam C920 as 
/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23
  [  748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd
  [  938.125745] usb 3-3: USB disconnect, device number 5
  [  943.298530] BUG: unable to handle kernel NULL pointer dereference at 

  [  943.298533] #PF error: [normal kernel read fault]
  [  943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 
  [  943.298536] Oops:  [#1] SMP PTI
  [  943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P   OE 
5.0.0-13-generic #14-Ubuntu
  [  943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, 
BIOS F7 01/20/2014
  [  943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60
  [  943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 
48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 
0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48
  [  943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202
  [  943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 
0004
  [  943.298547] RDX:  RSI: 0001 RDI: 
a1070ad0a800
  [  943.298548] RBP: bdae493dbab0 R08: 00027040 R09: 
b57825b8
  [  943.298549] R10: fba45fce4bc0 R11: 0001 R12: 

  [  943.298550] R13: a10644187b98 R14: ff92 R15: 
a1075131a000
  [  943.298551] FS:  7f93c40d7700() GS:a1075ea0() 
knlGS:
  [  943.298552] CS:  0010 DS:  ES:  CR0: 80050033
  [  943.298553] CR2:  CR3: 0006f8a94004 CR4: 
001606f0
  [  943.298553] Call Trace:
  [  943.298557]  usb_hcd_alloc_bandwidth+0x241/0x370
  [  943.298559]  usb_set_interface+0xfc/0x380
  [  943.298565]  uvc_video_start_transfer+0x155/0x4b0 [uvcvideo]
  [  943.298568]  uvc_video_start_streaming+0x7f/0xd0 [uvcvideo]
  [  943.298570]  uvc_start_streaming+0x28/0x70 [uvcvideo]
  [  943.298573]  vb2_start_streaming+0x6d/0x110 [videobuf2_common]
  [  943.298575]  vb2_core_streamon+0x59/0xc0 [videobuf2_common]
  [  943.298578]  vb2_streamon+0x18/0x30 [videobuf2_v4l2]
  [  943.298580]  uvc_queue_streamon+0x2e/0x50 [uvcvideo]
  [  943.298582]  uvc_ioctl_streamon+0x3f/0x60 [uvcvideo]
  [  943.298588]  v4l_streamon+0x20/0x30 [videodev]
  [  943.298592]  __video_do_ioctl+0x19a/0x3f0 [videodev]
  [  943.298596]  video_usercopy+0x1a6/0x660 [videodev]
  [  943.298599]  ? v4l_s_fmt+0x630/0x630 [videodev]
  [  943.298603]  video_ioctl2+0x15/0x20 [videodev]
  [  943.298606]  v4l2_ioctl+0x49/0x50 [videodev]
  [  943.298608]  do_vfs_ioctl+0xa9/0x640
  [  943.298610]  ? __switch_to_asm+0x34/0x70
  [  943.298611]  ? __switch_to_asm+0x40/0x70
  [  943.298612]  ? __switch_to_asm+0x34/0x70
  [  943.298612]  ? __switch_to_asm+0x40/0x70
  [  943.298613]  ? __switch_to_asm+0x34/0x70
  [  943.298614]  ? __switch_to_asm+0x40/0x70
  [  943.298615]  ? __switch_to_asm+0x34/0x70
  [  943.298616]  ? __switch_to_asm+0x40/0x70
  [  943.298617]  ksys_ioctl+0x67/0x90
  [  

[Kernel-packages] [Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le

[Po-Hsu Lin]

** Changed in: ubuntu-kernel-tests
   Status: New => 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/1867570

Title:
  reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on
  ppc64le

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]
  The reuseport_bpf_numa testcase in selftests/net fails on some PowerPC 
systems with:

   # selftests: net: reuseport_bpf_numa
   #  IPv4 UDP 
   # send node 0, receive socket 0
   # libnuma: Warning: Cannot read node cpumask from sysfs
   # ./reuseport_bpf_numa: failed to pin to node: No such file or directory
   not ok 3 selftests: net: reuseport_bpf_numa # exit=1

  [ Fix ]
  In some platforms the numa node numbers are not necessarily consecutive, so 
when reuseport_bpf_numa iterates on the nodes from 0 to the max available node 
some of those will not be available. The fix is to change the testcase so it 
checks whether the node is available before trying to send/receive from it.

  [ Test ]
  Run reuseport_bpf_numa from selftests/net in one of the affected test nodes.

  [ Where Problems Could Occur ]
  This is a very simple fix which relies on the libnuma exported functions and 
bitmaps to check whether a numa node number is available on the system. If 
something is not right on how this check is made or on the libnuma code itself 
only the reuseport_bpf_numa testcase will be affected by reporting false 
negatives or having a reduced test coverage.

  [ Original bug report ]
  This issue was extracted from the comment in bug 1812638, since that bug will 
be specific for i386

  This reuseport_bpf_numa in net will fail on PowerPC with:

  The output on B-5.3 P8 is:
   # selftests: net: reuseport_bpf_numa
   #  IPv4 UDP 
   # send node 0, receive socket 0
   # send node 1, receive socket 7
   # ./reuseport_bpf_numa: node id/receive socket mismatch
   not ok 3 selftests: net: reuseport_bpf_numa # exit=1

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


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

[Kernel-packages] [Bug 1958191] Re: Flickering and disforming booting into desktop both on wayland/xorg

[lotuspsychje]

adding dmesg for 5.15 without cstate paramater

** Attachment added: "dmesg-without-cstate.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+attachment/046/+files/dmesg-without-cstate.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/1958191

Title:
  Flickering and disforming booting into desktop both on wayland/xorg

Status in linux package in Ubuntu:
  New

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

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

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

  adding the kernel paramater intel_idle.max_cstate=4 fixed this

  i had these same bugs on this machine before:

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

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

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

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


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

[Kernel-packages] [Bug 1956518] Re: linux-firmware 1.187.24 may crash USB ports

[You-Sheng Yang]

Hi, Neurer and Pawel or anyone affected, please file a new bug of your
own so that you can run apport-collect to submit more hardware
information. Please also help paste your bug link here for further
reference.

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

Title:
  linux-firmware 1.187.24 may crash USB ports

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  5.4.0-92-generic

  linux-firmware:
Instalados: 1.187.24
Candidato:  1.187.24
Tabla de versión:
   *** 1.187.24 500
  500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.187 500
  500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages

  linux-firmware 1.187.24 upgrade disabled all mainboard USB ports.
  USB keyboard and mouse stopped working on the next reboot after upgrade.
  I disconnected an USB bluetooth key from a back USB port, rebooted, and 
everything restored to normality.
  My personal conclusion: there is a bug in the bluetooth firmware update that 
may cause a general USB crash when an USB bluetooth key is connected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alvaro 2225 F pulseaudio
   /dev/snd/controlC0:  alvaro 2225 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a
  InstallationDate: Installed on 2014-10-25 (2634 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B365M H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-firmware 1.187.24
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic 
root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-92-generic N/A
   linux-backports-modules-5.4.0-92-generic  N/A
   linux-firmware1.187.24
  RfKill:
   2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-92-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago)
  UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 08/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4b
  dmi.board.asset.tag: Default string
  dmi.board.name: B365M H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B365M H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1958191] [NEW] Flickering and disforming booting into desktop both on wayland/xorg

[lotuspsychje]

Public bug reported:

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

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

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

adding the kernel paramater intel_idle.max_cstate=4 fixed this

i had these same bugs on this machine before:

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

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

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

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

Title:
  Flickering and disforming booting into desktop both on wayland/xorg

Status in linux package in Ubuntu:
  New

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

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

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

  adding the kernel paramater intel_idle.max_cstate=4 fixed this

  i had these same bugs on this machine before:

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1201 F pipewire-media-
lotuspsychje   1207 F pulseaudio
   /dev/snd/seq:lotuspsychje   1193 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 04:22:00 2022
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash 
intel_idle.max_cstate=4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 

[Kernel-packages] [Bug 1958182] Re: Just applied the latest patch and the Broadcom 802.11 wifi on my Dell latitude is broken again.

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1958182

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Just applied the latest patch and the Broadcom 802.11 wifi on my Dell
  latitude is broken again.

Status in bcmwl package in Ubuntu:
  New

Bug description:
  
  uname -r 5.4.0-94-lowlatency

  lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  Booting under previous kernel (5.4.0-92-lowlatency) does not resolve
  the issue.

  lspci -vnn | grep Network
  00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network 
Connection (Lewisville) [8086:1502] (rev 04)
Subsystem: Dell 82579LM Gigabit Network Connection (Lewisville) 
[1028:0534]
  02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43228 
802.11a/b/g/n [14e4:4359]

  ip link show
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: eno1:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether f0:1f:af:34:68:4c brd ff:ff:ff:ff:ff:ff
  3: wlp2s0:  mtu 1500 qdisc 
fq_codel state DORMANT mode DORMANT group default qlen 1000
  link/ether 70:18:8b:14:bc:e5 brd ff:ff:ff:ff:ff:ff

  
  sudo lshw -class network
*-network 
 description: Ethernet interface
 product: 82579LM Gigabit Network Connection (Lewisville)
 vendor: Intel Corporation
 physical id: 19
 bus info: pci@:00:19.0
 logical name: eno1
 version: 04
 serial: f0:1f:af:34:68:4c
 size: 10Mbit/s
 capacity: 1Gbit/s
 width: 32 bits
 clock: 33MHz
 capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=3.2.6-k duplex=full firmware=0.13-3 ip=192.168.0.102 latency=0 
link=yes multicast=yes port=twisted pair speed=10Mbit/s
 resources: irq:27 memory:f7e0-f7e1 memory:f7e39000-f7e39fff 
ioport:f080(size=32)
*-network
 description: Wireless interface
 product: BCM43228 802.11a/b/g/n
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: 70:18:8b:14:bc:e5
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=wl0 driverversion=6.30.223.271 
(r587334) latency=0 multicast=yes wireless=IEEE 802.11
 resources: irq:17 memory:f7d0-f7d03fff

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


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

[Kernel-packages] [Bug 1958182] [NEW] Just applied the latest patch and the Broadcom 802.11 wifi on my Dell latitude is broken again.

[Doug Forguson]

Public bug reported:


uname -r 5.4.0-94-lowlatency

lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04

Booting under previous kernel (5.4.0-92-lowlatency) does not resolve the
issue.

lspci -vnn | grep Network
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network 
Connection (Lewisville) [8086:1502] (rev 04)
Subsystem: Dell 82579LM Gigabit Network Connection (Lewisville) 
[1028:0534]
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43228 
802.11a/b/g/n [14e4:4359]

ip link show
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
link/ether f0:1f:af:34:68:4c brd ff:ff:ff:ff:ff:ff
3: wlp2s0:  mtu 1500 qdisc fq_codel 
state DORMANT mode DORMANT group default qlen 1000
link/ether 70:18:8b:14:bc:e5 brd ff:ff:ff:ff:ff:ff


sudo lshw -class network
  *-network 
   description: Ethernet interface
   product: 82579LM Gigabit Network Connection (Lewisville)
   vendor: Intel Corporation
   physical id: 19
   bus info: pci@:00:19.0
   logical name: eno1
   version: 04
   serial: f0:1f:af:34:68:4c
   size: 10Mbit/s
   capacity: 1Gbit/s
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=3.2.6-k duplex=full firmware=0.13-3 ip=192.168.0.102 latency=0 
link=yes multicast=yes port=twisted pair speed=10Mbit/s
   resources: irq:27 memory:f7e0-f7e1 memory:f7e39000-f7e39fff 
ioport:f080(size=32)
  *-network
   description: Wireless interface
   product: BCM43228 802.11a/b/g/n
   vendor: Broadcom Inc. and subsidiaries
   physical id: 0
   bus info: pci@:02:00.0
   logical name: wlp2s0
   version: 00
   serial: 70:18:8b:14:bc:e5
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=wl0 driverversion=6.30.223.271 
(r587334) latency=0 multicast=yes wireless=IEEE 802.11
   resources: irq:17 memory:f7d0-f7d03fff

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

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

Title:
  Just applied the latest patch and the Broadcom 802.11 wifi on my Dell
  latitude is broken again.

Status in bcmwl package in Ubuntu:
  New

Bug description:
  
  uname -r 5.4.0-94-lowlatency

  lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  Booting under previous kernel (5.4.0-92-lowlatency) does not resolve
  the issue.

  lspci -vnn | grep Network
  00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network 
Connection (Lewisville) [8086:1502] (rev 04)
Subsystem: Dell 82579LM Gigabit Network Connection (Lewisville) 
[1028:0534]
  02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43228 
802.11a/b/g/n [14e4:4359]

  ip link show
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: eno1:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether f0:1f:af:34:68:4c brd ff:ff:ff:ff:ff:ff
  3: wlp2s0:  mtu 1500 qdisc 
fq_codel state DORMANT mode DORMANT group default qlen 1000
  link/ether 70:18:8b:14:bc:e5 brd ff:ff:ff:ff:ff:ff

  
  sudo lshw -class network
*-network 
 description: Ethernet interface
 product: 82579LM Gigabit Network Connection (Lewisville)
 vendor: Intel Corporation
 physical id: 19
 bus info: pci@:00:19.0
 logical name: eno1
 version: 04
 serial: f0:1f:af:34:68:4c
 size: 10Mbit/s
 capacity: 1Gbit/s
 width: 32 bits
 clock: 33MHz
 capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=3.2.6-k duplex=full firmware=0.13-3 ip=192.168.0.102 latency=0 
link=yes multicast=yes port=twisted pair speed=10Mbit/s
 resources: irq:27 memory:f7e0-f7e1 memory:f7e39000-f7e39fff 
ioport:f080(size=32)
*-network
 description: Wireless interface
 product: BCM43228 802.11a/b/g/n
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: 70:18:8b:14:bc:e5
 width: 64 bits
 

[Kernel-packages] [Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)

[Dominic Pfromm]

on 22.04 Daily Live from today everything works out of the Box on ASUS
C200 with Bay Trail

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

Title:
  [SRU] No sound from internal card chtmax98090 (missing UCM2 files in
  alsa-ucm-conf)

Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  There is no ucm for ASUS C300 in the 20.04 and 20.10, as a result,
  the audio doesn't work on this machine after installing the 20.04 or
  20.10.

  [Fix]
  The ucm files for this machine are in the alsa-ucm-conf 1.2.3,
  cherry-pick them to ubuntu 20.04 and 20.10

  [Test Case]
  After booting up, use speaker to play some sound, it works well,
  plug a headset, play sound to headphone, it basically works but has
  some crankling noise, it is a kernel issue for this noise.

  [Regression Risk]
  This SRU adds new ucm files, If the machine uses the audio driver
  of chtmax98090, it will apply this new added ucm files, there will
  be speaker/headphone in the UI. So the possible regression is with
  this SRU, users could see the audio devices in the UI but the audio
  doesn't work (without this SRU, users couldn't see the audio devices
  in the UI at all and the audio doesn't work). This possibility is
  low since we tested it on the ASUS C300.


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

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

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

  I attach the alsa-info.sh output.

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

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


-- 
Mailing list: 

[Kernel-packages] [Bug 1952674] Re: Kernel 5.13 fails to work with lots of hardware (HP Zbook)

[a1291762]

My machine was pushed the 5.13.0-25 kernel today but this time it did
not cause everything to break. All of the things I originally reported
as broken on my HP Zbook are now fixed.

The internal display works.
The trackpad works.
The keyboard works.
The Ethernet on the Thunderbolt dock works.

My system has an NVIDIA GPU (looks like a Quadro T1000) so I do not see
the 4700U graphics driver crash that rasdpm reports.

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

Title:
  Kernel 5.13 fails to work with lots of hardware (HP Zbook)

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

Bug description:
  The Internal display does not work. External monitors connected via 
Thunderbolt down continue to work.
  The trackpad does not work. The keyboard does work.
  The Ethernet on the Thunderbolt dock does not work.

  Booting the 5.11 kernel allows everything to work.

  
  I'm not sure how useful the automatically-attached files are since I had to 
boot with 5.11 in order to get the network working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-22-generic 5.13.0-22.22~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Nov 30 10:37:03 2021
  InstallationDate: Installed on 2021-08-30 (91 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  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.13/+bug/1952674/+subscriptions


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

[Kernel-packages] [Bug 1958089] Re: Acer laptop screen goes black after a few hours of work

[Steve Beattie]

** Information type changed from Public Security to Public

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

Title:
  Acer laptop screen goes black after a few hours of work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently switched from LM Cinnamon build to LM MATE build.
  Everything went fine at first, but now I experience issues where my
  screen goes black showing only the underscore flashing.

  Results:

  ubuntu-bug linux results:

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ...

  *** Problem in linux-image-5.4.0-94-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  
  cat /proc/version_signature > version.log results: 
  Ubuntu 5.4.0-94.106-generic 5.4.157

  sudo lspci -vnvn > lspci-vnvn.log results:
  pcilib: sysfs_read_vpd: read failed: Input/output error
  pcilib: sysfs_read_vpd: read failed: Input/output error

  lsb_release -rd results:
  Description:  Linux Mint 20.2
  Release:  20.2

  
  While browsing through 'System Log Viewer' tool on the system, I noticed a 
few lines saying things like 'kernel bug' or 'firmware bug'. After no luck on 
the forums, I was told that I should put this up here.

  Inxi -Fzn result: https://pastebin.com/raw/W3DUxUzu
  Xorg log (from System Log Viewer): https://pastebin.com/raw/ePCk2DaL
  kern.log (from System Log Viewer): https://pastebin.com/raw/ju233mxe
  syslog from System Log Viewer tool will be attached.

  I hope that any of this will be enough to identify the issue.

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[elguavas]

So the kernel in jammy has the fix released, well fine. but where is the
the fixed released kernel for impish!!

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  [Impact]

  On some thinkpads we may get a kernel panic at boot, because the
  elantech driver (trakcpad) can trigger out-of-bounds access in the
  stack.

  [Test case]

  Simply boot the kernel on one of the affected systems (e.g., Thinkpad
  E14 Gen2).

  [Fix]

  Prevent the stack out of bound access by applying the following
  upstream commit (from linux-next):

  1d72d9f960cc ("Input: elantech - fix stack out of bound access in
  elantech_change_report_id()")

  [Regression potential]

  The fix is touching the elantech driver, so we could only see
  regressions with this specific trackpad/mouse driver.

  [Original bug report]

  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1955790] Re: Got black screen when resume from s2idle with AMD dGPU

[Mario Limonciello]

This caused a regression on APUs that do S3; please pick up
https://gitlab.freedesktop.org/agd5f/linux/-/commit/8cf1a5e7e7ab6532beaa14b03bb5bf838be906e0
as well to avoid it

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

Title:
  Got black screen when resume from s2idle with AMD dGPU

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  On Dell AIO with AMD dGPU platforms, it looks like AMD dGPU can't be waken up 
after s2idle and got black screen.

  [Fix]
  AMD provides us 2 commits to fix this issue.
  https://patchwork.freedesktop.org/patch/463002/
  https://patchwork.freedesktop.org/series/98338/

  [Test]
  Verified by AMD.

  [Where problems could occur]
  It should be fine to reset the asic and set to the proper state while 
entering suspended.

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


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

[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

[Ian]

Ah, this PC (Nvidia GT1050 Ti graphics card) won't boot with the 495
drivers, so I am back with 470.

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

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


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

[Kernel-packages] [Bug 1922406]

[raymond]

(In reply to Doug Coleman from comment #27)
> I updated Ubuntu and got a broken wifi driver again. I got fed up with old
> kernels (5.11, 5.13) and installed 5.16 and it fixed the wifi and a
> screen-tearing issue that was driving me mad!
> 
> sudo add-apt-repository ppa:tuxinvader/lts-mainline -y
> sudo apt update
> sudo apt-get install linux-generic-5.16 -y

Yes, it fixed for me too when I upgraded to 5.16 but but..
5.16 isn't official 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/1922406

Title:
  Intel AX210 Wi-Fi card does not work since updating to 1.196

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  Running 21.04, updated daily.

  Since updating the linux-firmware package yesterday, the Wireless card
  does not work with current kernel (5.11.0-13).

  The error message is as follows:

  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start 
RT ucode: -110
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1

  It **does** work with 5.11.0-11 (previous version)

  Distro: Ubuntu 21.04 (Hirsute Hippo)
  Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020
  CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
L2 cache: 4 MiB

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


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

[Kernel-packages] [Bug 1922406]

[doug.coleman]

I updated Ubuntu and got a broken wifi driver again. I got fed up with
old kernels (5.11, 5.13) and installed 5.16 and it fixed the wifi and a
screen-tearing issue that was driving me mad!

sudo add-apt-repository ppa:tuxinvader/lts-mainline -y
sudo apt update
sudo apt-get install linux-generic-5.16 -y

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

Title:
  Intel AX210 Wi-Fi card does not work since updating to 1.196

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  Running 21.04, updated daily.

  Since updating the linux-firmware package yesterday, the Wireless card
  does not work with current kernel (5.11.0-13).

  The error message is as follows:

  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start 
RT ucode: -110
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1

  It **does** work with 5.11.0-11 (previous version)

  Distro: Ubuntu 21.04 (Hirsute Hippo)
  Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020
  CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
L2 cache: 4 MiB

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


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

[Kernel-packages] [Bug 1922406]

[raymond]

I had similar problem on a gaming PC, I'm on Ubuntu 5.11.0-46-generic
kernel. I renamed pnvm file, rebooted and it worked for me. Bluetooth
also seems to be working for me. Any idea when will it be fixed?

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

Title:
  Intel AX210 Wi-Fi card does not work since updating to 1.196

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  Running 21.04, updated daily.

  Since updating the linux-firmware package yesterday, the Wireless card
  does not work with current kernel (5.11.0-13).

  The error message is as follows:

  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start 
RT ucode: -110
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1

  It **does** work with 5.11.0-11 (previous version)

  Distro: Ubuntu 21.04 (Hirsute Hippo)
  Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020
  CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
L2 cache: 4 MiB

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


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

[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

[Ian]

Yes, it also affects version 470 of the drivers.

Fortunately, this time when I switched to another user having not closed
a (paused) video in VLC, I had plenty of free space: /var/log/syslog got
7GB bigger in a couple of minutes.

I see version 495 is available. I have installed that, but after over
two years of this problem not being fixed, I am not holding my breath...


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

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

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


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

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

[Nicolas Maeding]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1958032/+attachment/5554974/+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/1958032

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 x86_64 x86_64 

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

[Nicolas Maeding]

apport information

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

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 x86_64 x86_64 
GNU/Linux
 

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

[Nicolas Maeding]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1958032/+attachment/5554976/+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/1958032

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 x86_64 x86_64 

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

[Nicolas Maeding]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1958032/+attachment/5554977/+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/1958032

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  

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

[Nicolas Maeding]

apport information

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

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 x86_64 

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

[Nicolas Maeding]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1958032/+attachment/5554968/+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/1958032

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 x86_64 x86_64 

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

[Nicolas Maeding]

apport information

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

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 x86_64 x86_64 
GNU/Linux
  

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

[Nicolas Maeding]

apport information

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

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 x86_64 

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

[Nicolas Maeding]

apport information

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

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 

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

[Nicolas Maeding]

apport information

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

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 x86_64 x86_64 
GNU/Linux
  

[Kernel-packages] [Bug 1958032] IwConfig.txt

[Nicolas Maeding]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1958032/+attachment/5554966/+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/1958032

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 x86_64 x86_64 

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

[Nicolas Maeding]

apport information

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

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 x86_64 x86_64 

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

[Nicolas Maeding]

apport information

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

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 x86_64 x86_64 

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

[Nicolas Maeding]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1958032/+attachment/5554969/+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/1958032

Title:
  [igb - Intel NIC] Adapter reset due to TX unit hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:

  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter

  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 x86_64 x86_64 

[Kernel-packages] [Bug 1958032] Re: [igb - Intel NIC] Adapter reset due to TX unit hangs

[Nicolas Maeding]

apport information

** Tags added: apport-collected focal

** Description changed:

  Hi,
  
  I get no network connection established.
  In dmesg I get repeatively messages regarding a TX hang and adapter reset:
  
  [  202.700164] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX
  [  204.929067] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  204.929065] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  206.911750] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  208.931728] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <2>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<98471433>
   jiffies  
   desc.status  <128200>
  [  210.911642] igb :01:00.0: Detected Tx Unit Hang
   Tx Queue <3>
   TDH  <0>
   TDT  <2>
   next_to_use  <2>
   next_to_clean<0>
     buffer_info[next_to_clean]
   time_stamp   
   next_to_watch<3bbba65a>
   jiffies  
   desc.status  <128200>
  [  212.091622] igb :01:00.0 enp1s0: igb: enp1s0 NIC Link is Down
  [  212.091950] igb :01:00.0 enp1s0: Reset adapter
  
  System: Shuttle SH570
  Kernel: Linux  5.11.0-46-generic #51~20.04.1-Ubuntu SMP  x86_64 x86_64 x86_64 
GNU/Linux
  NIC:
  /sys/class/net/enp1s0/device/vendor = 0x8086
  /sys/class/net/enp1s0/device/device = 0x157b
  
  sudo ethtool enp1s0
  Settings for enp1s0:
   Supported ports: [ TP ]
   Supported link modes:   10baseT/Half 10baseT/Full
   100baseT/Half 100baseT/Full
   1000baseT/Full
   Supported 

[Kernel-packages] [Bug 1949516] Re: require CAP_NET_ADMIN to attach N_HCI ldisc

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  require CAP_NET_ADMIN to attach N_HCI ldisc

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem-5.10 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.10 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  Any unprivileged user can attach N_HCI ldisc and send packets coming from a
  virtual controller by using PTYs. This exposes attack surface on systems
  where bluetooth is not needed or even allow local attacks that would otherwise
  require physical proximity.

  [Test case]
  Try attaching N_HCI ldisc to a tty.

  ldattach HCI /dev/tty

  [Potential regression]
  Users who rely on programs using N_HCI line discipline in order to emulate or 
proxy a bluetooth controller will require privilege they may not have.

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


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

[Kernel-packages] [Bug 1946433] Re: Can only reach PC3 when ethernet is plugged r8169

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  Can only reach PC3 when ethernet is plugged r8169

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Impact]
  System only can reach PC3, and it affects power consumption alot.

  [Fix]
  Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state 
issue, but also fixes network speed issue.
  
https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/

  [Test]
  Verified on 2 different systems which has PC state issue and has network 
speed issue, these patches fix both issues.

  [Where problems could occur]
  It toggles ASPM on and off depends on the network traffic during runtime, I 
don't think it'll lead to any regressions. Some potential issues have been 
addressed during the patch submitting. It's v6 now and accepted by upstream.

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


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

[Kernel-packages] [Bug 1942215] Re: OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

Title:
  OOPs on boot: invalid opcode:  [#1] SMP NOPTI

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Incomplete

Bug description:
  Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon
  boot on vought we get this:

  ...
  [   11.502916] invalid opcode:  [#1] SMP NOPTI
  [   11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 
5.13.0-15-generic #15-Ubuntu
  [   11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.0D.01.0395.022720191340 02/27/2019
  [   11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774
  [   11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 
89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 
c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01
  [   11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286
  [   11.513428] RAX:  RBX: 8f08a7573800 RCX: 
0040
  [   11.514972] RDX:  RSI: 91ea9980 RDI: 
02cb
  [   11.516100] RBP: aaeca1a77710 R08:  R09: 
8f08a8c84af0
  [   11.517479] R10:  R11: 0003 R12: 

  [   11.518985] R13: 8f08a8c84af0 R14:  R15: 

  [   11.520425] FS:  7f7fb403ed00() GS:8f348d5c() 
knlGS:
  [   11.521931] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 
007706e0
  [   11.524924] DR0:  DR1:  DR2: 

  [   11.526221] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   11.527636] PKRU: 5554
  [   11.528820] Call Trace:
  [   11.529807]  acpi_ps_parse_loop+0x587/0x660
  [   11.531198]  acpi_ps_parse_aml+0x1af/0x552
  [   11.532595]  acpi_ps_execute_method+0x208/0x2ca
  [   11.533972]  acpi_ns_evaluate+0x34e/0x4f0
  [   11.535361]  acpi_evaluate_object+0x18e/0x3b4
  [   11.536736]  acpi_evaluate_dsm+0xb3/0x120
  [   11.537943]  ? acpi_evaluate_dsm+0xb3/0x120
  [   11.539214]  nfit_intel_shutdown_status+0xed/0x1b0 [nfit]
  [   11.540603]  acpi_nfit_add_dimm+0x3cb/0x670 [nfit]
  [   11.541990]  acpi_nfit_register_dimms+0x141/0x460 [nfit]
  [   11.543377]  acpi_nfit_init+0x54f/0x620 [nfit]
  [   11.544755]  acpi_nfit_add+0x192/0x1f0 [nfit]
  [   11.546116]  acpi_device_probe+0x49/0x170
  [   11.547431]  really_probe+0x245/0x4c0
  [   11.548749]  driver_probe_device+0xf0/0x160
  [   11.550064]  device_driver_attach+0xab/0xb0
  [   11.551387]  __driver_attach+0xb2/0x140
  [   11.552692]  ? device_driver_attach+0xb0/0xb0
  [   11.554001]  bus_for_each_dev+0x7e/0xc0
  [   11.555326]  driver_attach+0x1e/0x20
  [   11.556630]  bus_add_driver+0x135/0x1f0
  [   11.557917]  driver_register+0x95/0xf0
  [   11.559226]  acpi_bus_register_driver+0x39/0x50
  [   11.560139]  nfit_init+0x168/0x1000 [nfit]
  [   11.561230]  ? 0xc0649000
  [   11.562442]  do_one_initcall+0x46/0x1d0
  [   11.563701]  ? kmem_cache_alloc_trace+0x11c/0x240
  [   11.564846]  do_init_module+0x62/0x290
  [   11.565768]  load_module+0xaa6/0xb40
  [   11.566811]  __do_sys_finit_module+0xc2/0x120
  [   11.567825]  __x64_sys_finit_module+0x18/0x20
  [   11.568747]  do_syscall_64+0x61/0xb0
  [   11.569694]  ? syscall_exit_to_user_mode+0x27/0x50
  [   11.570680]  ? __x64_sys_mmap+0x33/0x40
  [   11.571606]  ? do_syscall_64+0x6e/0xb0
  [   11.572442]  ? asm_exc_page_fault+0x8/0x30
  [   11.573395]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   11.574392] RIP: 0033:0x7f7fb45d670d
  [   11.575373] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48
  [   11.577496] RSP: 002b:7ffe815a56d8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   11.578573] RAX: ffda RBX: 5624b212e410 RCX: 
7f7fb45d670d
  [   11.579646] RDX:  RSI: 7f7fb47683fe RDI: 
0006
  [   11.580712] RBP: 0002 R08:  R09: 

  [   11.581774] R10: 0006 R11: 0246 R12: 
7f7fb47683fe
  [   11.582847] R13: 5624b2090bf0 R14: 5624b208f940 R15: 
5624b2096cd0
  [   11.583907] Modules linked in: nfit(+) mac_hid sch_fq_codel msr ip_tables 
x_tables autofs4 btrfs blake2b_generic 

[Kernel-packages] [Bug 1938531] Re: support signed v4l2loopback dkms build

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  support signed v4l2loopback dkms build

Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  v4l2loopback is used as a critical role on Intel IPU6 camera platforms,
  which takes userspace middleware involvements to correctly configure
  hardware sensors. While all the legacy camera applications are not yet
  learned how to support libcamera, v4l2loopback and a v4l2-relayd step in
  as a video streaming proxy for backward compatibility.

  To preinstall v4l2loopback kernel module on secureboot systems, signed
  modules should be used.

  [Fix]

  All Ubuntu specific changes to enable signed v4l2loopback dkms builds.

  [Test Case]

  Install signed modules package and check `modinfo v4l2loopback`.

  [Where problems could occur]

  N/A.

  [Other Info]

  This adds current revision of v4l2loopback in the ubuntu archive. While
  some other fixes are also needed for v4l2loopback/focal, expects version
  bumps recently.

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


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

[Kernel-packages] [Bug 1945556] Re: Fix missing HDMI audio on Intel RKL

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1945556

Title:
  Fix missing HDMI audio on Intel RKL

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Impact]
  HDMI audio is missing on Intel RKL.

  [Fix]
  Also use BIOS provided value for HDA link.

  [Test]
  HDMI audio is back after the fix gets applied.

  [Where problems could occur]
  Because this is a regression, this patch simply brings back the old
  behavior for RKL systems. There could be RKL systems get fixed by
  the offending commit, so this might break those hypothetical systems.

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1945590

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  [Impact]

  On some thinkpads we may get a kernel panic at boot, because the
  elantech driver (trakcpad) can trigger out-of-bounds access in the
  stack.

  [Test case]

  Simply boot the kernel on one of the affected systems (e.g., Thinkpad
  E14 Gen2).

  [Fix]

  Prevent the stack out of bound access by applying the following
  upstream commit (from linux-next):

  1d72d9f960cc ("Input: elantech - fix stack out of bound access in
  elantech_change_report_id()")

  [Regression potential]

  The fix is touching the elantech driver, so we could only see
  regressions with this specific trackpad/mouse driver.

  [Original bug report]

  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1954646] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus  show error 
"severity=Uncorrected (Non-Fatal)",
  and failed to probe.

  [Fix]
  Re-enable PCIe port LTR after reset or hotplug, and probe it properly.

  [Test]
  Verified on HW with TBT4 dock. it works fine.
  Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine.
  Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt.

  [Where problems could occur]
  PCI bus may break.

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


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

[Kernel-packages] [Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on
  ppc64le

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]
  The reuseport_bpf_numa testcase in selftests/net fails on some PowerPC 
systems with:

   # selftests: net: reuseport_bpf_numa
   #  IPv4 UDP 
   # send node 0, receive socket 0
   # libnuma: Warning: Cannot read node cpumask from sysfs
   # ./reuseport_bpf_numa: failed to pin to node: No such file or directory
   not ok 3 selftests: net: reuseport_bpf_numa # exit=1

  [ Fix ]
  In some platforms the numa node numbers are not necessarily consecutive, so 
when reuseport_bpf_numa iterates on the nodes from 0 to the max available node 
some of those will not be available. The fix is to change the testcase so it 
checks whether the node is available before trying to send/receive from it.

  [ Test ]
  Run reuseport_bpf_numa from selftests/net in one of the affected test nodes.

  [ Where Problems Could Occur ]
  This is a very simple fix which relies on the libnuma exported functions and 
bitmaps to check whether a numa node number is available on the system. If 
something is not right on how this check is made or on the libnuma code itself 
only the reuseport_bpf_numa testcase will be affected by reporting false 
negatives or having a reduced test coverage.

  [ Original bug report ]
  This issue was extracted from the comment in bug 1812638, since that bug will 
be specific for i386

  This reuseport_bpf_numa in net will fail on PowerPC with:

  The output on B-5.3 P8 is:
   # selftests: net: reuseport_bpf_numa
   #  IPv4 UDP 
   # send node 0, receive socket 0
   # send node 1, receive socket 7
   # ./reuseport_bpf_numa: node id/receive socket mismatch
   not ok 3 selftests: net: reuseport_bpf_numa # exit=1

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


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

[Kernel-packages] [Bug 1947206] Re: Updates to ib_peer_memory requested by Nvidia

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

Title:
  Updates to ib_peer_memory requested by Nvidia

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in linux source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Nvidia notified me via private email that they'd discovered some issues with 
the ib_peer_memory patch we are carrying in hirsute/impish and sent me a patch 
intended to resolve them. My knowledge of these changes is limited to what is 
mentioned in the commit message:

  - Allow clients to opt out of unmap during invalidation
  - Fix some bugs in the sequencing of mlx5 MRs
  - Enable ATS for peer memory

  [Test Case]
  ib_write_bw from the perftest package, rebuilt with CUDA support, can be used 
as a smoke test of this feature. I'll attach a sample test script here. I've 
verified this test passes with the kernels in the archive, and continues to 
pass with the provided patch applied.

  [Fix]
  Nvidia has emailed me fixes for both trees. They are not currently available 
in a public tree elsewhere, though I'm told at some point they should end up in 
a branch here:
    https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/

  [What could go wrong]
  The only known use case for ib_peer_memory are Nvidia GPU users making use of 
the GPU PeerDirect feature where GPUs can share memory with one another over an 
Infiniband network. Bugs here could cause problems (hangs, crashes, corruption) 
with such workloads.

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


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

[Kernel-packages] [Bug 1951868] Re: [amdgpu] USB4 support for DP tunneling

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  [amdgpu] USB4 support for DP tunneling

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released

Bug description:
  [Impact]
  DP tunneling over USB4 requires additional work in the AMD GPU driver that 
isn't present in 5.14 or 5.15. The code is included in 5.16 kernel and will 
need to be backported into 5.14 OEM kernel (and jammy/5.15) to support any 
programs that need it.

  [Fix]
  Cherry-pick/backport 30 commits from 5.16 to 5.15. OEM-5.14 needs a few 
additional ones from 5.15.

  [Test case]
  WIP

  [Where things could go wrong]
  WIP

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


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

[Kernel-packages] [Bug 1954930] Re: AMD: Suspend not working when some cores are disabled through cpufreq

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  AMD: Suspend not working when some cores are disabled through cpufreq

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Committed
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Detailed in https://gitlab.freedesktop.org/drm/amd/-/issues/1708, taking
  some cpu cores offline using cpufreq gadgets or via sysfs may hang the
  system.

  [Fix]

  In v5.16-rc1 commit d6b88ce2eb9d ("ACPI: processor idle: Allow playing
  dead in C3 state") fixes this issue.

  [Test Case]

  As stated in aforementioned bug url, setup cpufreq extention to take
  down a few cpu cores, and trigger system suspend. There are ~50% chances
  that networking/input/... would hang and the user can only reboot by
  sysrq keys.

  [Where problems could occur]

  According to the patch discussion thread in
  https://lore.kernel.org/linux-acpi/20210922133116.102-1-richard.g...@amd.com/,
  the limitation to allow enter_dead in no more than ACPI_STATE_C2 might
  not have a practical meaning, but simply C2 was the deepest supported
  then.

  [Other Info]

  While this is currently only available in v5.16-rc1 and affects AMD
  Cezanne/Barcelo, oem-5.14/impish and jammy are nominated.

  == original bug report ==

  https://gitlab.freedesktop.org/drm/amd/-/issues/1708

  Reproduce steps:
  1. Install cpufeq gnome extension 
(https://extensions.gnome.org/extension/1082/cpufreq/)
  2. Click on the cpu freq extention in the top bar
  3. Slide the "cores online" from 16 to 3
  4. close lid of laptop

  Expected result: the laptop goes into suspend
  Actual result: the laptop stay on but screen is now always black and keyboard 
input is ignored

  Fix committed to v5.16-rc1: 
https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1188 F pulseaudio
   /dev/snd/controlC2:  ubuntu 1188 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1188 F pulseaudio
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-09 (97 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IwConfig:
   lono wireless extensions.

   enp1s0f0  no wireless extensions.
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AMD Celadon-CZN
  Package: linux-firmware 1.187.23+staging.38 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  PackageArchitecture: all
  ProcFB: 0 amdgpu
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem 
root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config 
no_console_suspend
  ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-9011-oem N/A
   linux-backports-modules-5.14.0-9011-oem  N/A
   linux-firmware   1.187.23+staging.38
  RfKill:

  Tags: third-party-packages focal
  Uname: Linux 5.14.0-9011-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 06/30/2021
  dmi.bios.release: 19.1
 

[Kernel-packages] [Bug 1945938] Re: [impish] Remove the downstream xr-usb-uart driver

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

Title:
  [impish] Remove the downstream xr-usb-uart driver

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

Bug description:
  [Impact]

  The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS 
kernel
  to add support for USB UART chips:
  Family: USB UART
  Part Numbers:
  XR21V1410, XR21V1412, XR21V1414,
  XR21B1411, XR21B1420, XR21B1422,
  XR21B1424, XR22801, XR22802,
  XR22804

  [Fix]
  In 5.13.x, support for these devices was added to the kernel via. following 
patch series:
  Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/

  There have been long term maintenance challenges with the downstream vendor 
driver
  over the period of time (since 4.4.y based Xenial LTS). Now that upstream 
driver
  supports most of the above part numbers, let's remove this redundant 
out-of-tree driver.

  [Test]
  The driver was functionally verified to work fine with XR21V1412. The support 
for
  other chips with part numbers mentioned above are also supported with the 
above
  patch series.

  [Where problems could occur]
  The downstream driver was designed to work with specific BIOS configs only
  defined on an IoT GW project which is locked to use only Xenial ESM and 
Bionic LTS
  kernels, there is a low chance of regression on the Impish series.

  [This is a tracking bug, please do not triage]

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


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

[Kernel-packages] [Bug 1954369] Re: Fix runtime power management on USB controller with XHCI_RESET_ON_RESUME flag

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954369

Title:
  Fix runtime power management on USB controller with
  XHCI_RESET_ON_RESUME flag

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Released

Bug description:
  [Impact]
  xHCI driver's runtime resume routine tries to reset USB controller with
  XHCI_RESET_ON_RESUME flag. That causes USB devices connect to the xHCI
  fail to work.

  [Fix]
  Disable runtime power management regardless of
  CONFIG_USB_DEFAULT_PERSIST option.

  [Test]
  USB devices which connect to the xHCI controller can work normally.

  [Where problems could occur] 
  USB_DEFAULT_PERSIST is a config for system-wide PM to speed up resume
  time, so it shouldn't be applied to runtime PM at first place.

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


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

[Kernel-packages] [Bug 1948038] Re: disable CONFIG_KFENCE_STATIC_KEYS in linux 5.15

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   Status: Expired => 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/1948038

Title:
  disable CONFIG_KFENCE_STATIC_KEYS in linux 5.15

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

Bug description:
  [Impact]

  KFENCE devs are changing CONFIG_KFENCE_STATIC_KEYS to be disabled by
  default, because it's introducing more problems than benefits:

  https://lore.kernel.org/all/20211019102524.2807208-2-el...@google.com/T/#u

  This also seems to trigger QEMU bugs during the systemd autopkgtest, like:
  https://bugs.launchpad.net/qemu/+bug/1920934

  [Test case]

  Run systemd autopkgtest.

  [Fix]

  Disable CONFIG_KFENCE_STATIC_KEYS.

  [Regression potential]

  We may experience an overall performance regression for not using
  static branches in the KFENCE code.

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


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

[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => Fix Released

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

Title:
  rtw88_8821ce causes freeze

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Committed
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card.
  Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic 
kernel,and it works "well" for both WiFi and Bluetooth.
  However, this module (driver) causes frequent freezes, randomly but usually 
within a few minutes of running (thus very soon after boot): screen display 
remains frozen, no response to either keyboard or mouse input. All I can do is 
to hold the power button to power off, then reboot.

  After reboot, I do not see any crash reports, nor logs about the freeze.
  Please let me know if I should try to collect some info, and how.

  For now I use the DKMS module/driver from
    https://github.com/tomaspinho/rtl8821ce
  (having blacklisted rtw88_8821ce), and it seems to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psz1189 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 16:58:19 2021
  InstallationDate: Installed on 2021-04-23 (14 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Protempo Ltd L116HTN6SPW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: L116HTN6SPW
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Protempo Ltd

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


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

[Kernel-packages] [Bug 1953731] Re: Jammy update: v5.15.7 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1953731

Title:
  Jammy update: v5.15.7 upstream stable release

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  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:

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

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


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

[Kernel-packages] [Bug 1947557] Re: kernel panic: NULL pointer dereference in wb_timer_f()

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

Title:
  kernel panic: NULL pointer dereference in wb_timer_f()

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

Bug description:
  [Impact]

  It is possible to trigger a kernel panic with the latest impish kernel
  running systemd autopkgtest using --enable-kvm with the test instances
  created by systemd during the autotest. The panic happens in the host,
  not in the guest VM executed by systemd.

  [Test case]

  Add --enable-kvm to the options in test/testdata/test-functions
  (systemd), run `sudo autopkgtest . -- null`, wait for the panic to
  happen.

  [Fix]

  https://lore.kernel.org/lkml/YW6N2qXpBU3oc50q@arighi-desktop/T/#u

  [Regression potential]

  The fix is addressing a race in the block layer (in the buffered write
  throttling code - block/blk-wbt.c) between a disk being released and
  the timer callback that periodically checks if the latency for a
  specific block device has been exceeded. If the fix is not correct we
  may still have a race in this code, that can still show potential
  kernel panics in the block layer subsystem.

  [Original bug report]

  I can trigger the following kernel panic with the latest impish kernel
  5.13.0-19-generic, running systemd autopkgtest using --enable-kvm for
  the instances created by systemd to run the autotest:

  [  119.987108] BUG: kernel NULL pointer dereference, address: 0098
  [  119.987617] #PF: supervisor read access in kernel mode
  [  119.987971] #PF: error_code(0x) - not-present page
  [  119.988325] PGD 7c4a4067 P4D 7c4a4067 PUD 7bf63067 PMD 0
  [  119.988697] Oops:  [#1] SMP NOPTI
  [  119.988959] CPU: 1 PID: 9353 Comm: cloud-init Not tainted 
5.15-rc5+arighi-aws #rc5+arighi
  [  119.989520] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 
1.14.0-2 04/01/2014
  [  119.990055] RIP: 0010:wb_timer_fn+0x44/0x3c0
  [  119.990376] Code: 41 8b 9c 24 98 00 00 00 41 8b 94 24 b8 00 00 00 41 8b 84 
24 d8 00 00 00 4d 8b 74 24 28 01 d3 01 c3 49 8b 44 24 60 48 8b 40 78 <4c> 8b b8 
98 00 00 00 4d 85 f6 0f 84 c4 00 00 00 49 83 7c 24 30 00
  [  119.991578] RSP: :b5f580957da8 EFLAGS: 00010246
  [  119.991937] RAX:  RBX:  RCX: 
0004
  [  119.992412] RDX:  RSI:  RDI: 
88f476d7f780
  [  119.992895] RBP: b5f580957dd0 R08:  R09: 

  [  119.993371] R10: 0004 R11: 0002 R12: 
88f476c84500
  [  119.993847] R13: 88f4434390c0 R14:  R15: 
88f4bdc98c00
  [  119.994323] FS:  7fb90bcd9c00() GS:88f4bdc8() 
knlGS:
  [  119.994952] CS:  0010 DS:  ES:  CR0: 80050033
  [  119.995380] CR2: 0098 CR3: 7c0d6000 CR4: 
06e0
  [  119.995906] Call Trace:
  [  119.996130]  ? blk_stat_free_callback_rcu+0x30/0x30
  [  119.996505]  blk_stat_timer_fn+0x138/0x140
  [  119.996830]  call_timer_fn+0x2b/0x100
  [  119.997136]  __run_timers.part.0+0x1d1/0x240
  [  119.997470]  ? kvm_clock_get_cycles+0x11/0x20
  [  119.997826]  ? ktime_get+0x3e/0xa0
  [  119.998110]  ? native_apic_msr_write+0x2c/0x30
  [  119.998456]  ? lapic_next_event+0x20/0x30
  [  119.998779]  ? clockevents_program_event+0x94/0xf0
  [  119.999150]  run_timer_softirq+0x2a/0x50
  [  119.999465]  __do_softirq+0xcb/0x26f
  [  119.999764]  irq_exit_rcu+0x8c/0xb0
  [  120.57]  sysvec_apic_timer_interrupt+0x43/0x90
  [  120.000429]  ? asm_sysvec_apic_timer_interrupt+0xa/0x20
  [  120.000836]  asm_sysvec_apic_timer_interrupt+0x12/0x20
  [  120.001226] RIP: 0033:0x501969
  [  120.001486] Code: 8d 54 e5 00 4d 8b a2 80 02 00 00 4d 89 ba 88 02 00 00 4d 
39 f4 75 0f e9 84 00 00 00 0f 1f 44 00 00 4c 39 f2 74 7a 49 8b 14 24 <4d> 89 e7 
49 89 d4 49 81 7f 18 e0 33 8f 00 75 e7 48 85 d2 74 e7 49
  [  120.002793] RSP: 002b:7ffc407d68b0 EFLAGS: 0206
  [  120.003196] RAX: 008eaa20 RBX: 7ffc407d6930 RCX: 

  [  120.003711] RDX: 00d2d940 RSI: 7fb90b9522c0 RDI: 
0001
  [  120.004224] RBP: 7ffc407d6940 R08: 7fb90a53df60 R09: 

  [  120.004750] R10: 00bc6130 R11: 0006 R12: 
00d2dda0
  [  120.005262] R13: 00bc6100 R14: 00bc63b0 R15: 
7fb90b4dde30
  [  120.005775] Modules linked in: essiv authenc crypto_simd cryptd dm_crypt 
scsi_debug isofs nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua kvm_amd 

[Kernel-packages] [Bug 1947709] Re: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active"

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1947709

Title:
  Drop "UBUNTU: SAUCE: cachefiles: Page leaking in
  cachefiles_read_backing_file while vmscan is active"

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  "UBUNTU: SAUCE: cachefiles: Page leaking in
  cachefiles_read_backing_file while vmscan is active" has been applied
  to fix a page leaking issue.

  However a slightly different fix has been applied upstream:

  9a24ce5b66f9c8190d63b15f4473600db4935f1f cachefiles: Fix page leak in
  cachefiles_read_backing_file while vmscan is active

  Basically we are fixing the same issue in two different ways at the
  same time, but even worse our patch an introduce a potential NULL
  pointer dereference: we do a put_page(newpage) and set newpage = NULL
  in the main for() loop and then we may do additional put_page(newpage)
  after the main for loop if ret == -EEXIST, that would trigger the NULL
  pointer dereference.

  [Test case]

  No test case or reproducer is available at the moment, this issue has
  been found simply by reviewing the code.

  [Fix]

  Drop the SAUCE patch and rely on the upstream fix.

  [Regression potential]

  If the analysis is not correct we may re-introduce a page leak in
  cachefiles (NFS for example), but it seems unlikely to happen, since the 
upstream fix is addressing the page leaking already.

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


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

[Kernel-packages] [Bug 1952579] Re: Jammy update: v5.15.5 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1952579

Title:
  Jammy update: v5.15.5 upstream stable release

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  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:

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

  
  Linux 5.15.5
  ALSA: hda: hdac_stream: fix potential locking issue in 
snd_hdac_stream_assign()
  ALSA: hda: hdac_ext_stream: fix potential locking issues
  x86/Kconfig: Fix an unused variable error in dell-smm-hwmon
  net: add and use skb_unclone_keeptruesize() helper
  btrfs: update device path inode time instead of bd_inode
  fs: export an inode_update_time helper
  ice: Delete always true check of PF pointer
  ice: Fix VF true promiscuous mode
  usb: max-3421: Use driver data instead of maintaining a list of bound devices
  ASoC: rsnd: fixup DMAEngine API
  ASoC: DAPM: Cover regression by kctl change notification fix
  selinux: fix NULL-pointer dereference when hashtab allocation fails
  bpf: Forbid bpf_ktime_get_coarse_ns and bpf_timer_* in tracing progs
  RDMA/netlink: Add __maybe_unused to static inline in C file
  hugetlbfs: flush TLBs correctly after huge_pmd_unshare
  signal: Replace force_fatal_sig with force_exit_sig when in doubt
  signal: Don't always set SA_IMMUTABLE for forced signals
  signal: Replace force_sigsegv(SIGSEGV) with force_fatal_sig(SIGSEGV)
  signal/x86: In emulate_vsyscall force a signal instead of calling do_exit
  signal/vm86_32: Properly send SIGSEGV when the vm86 state cannot be saved.
  signal/sparc32: In setup_rt_frame and setup_fram use force_fatal_sig
  signal/sparc32: Exit with a fatal signal when try_to_clear_window_buffer fails
  signal/s390: Use force_sigsegv in default_trap_handler
  signal/powerpc: On swapcontext failure force SIGSEGV
  exit/syscall_user_dispatch: Send ordinary signals on failure
  signal: Implement force_fatal_sig
  drm/amd/pm: avoid duplicate powergate/ungate setting
  drm/amdgpu: fix set scaling mode Full/Full aspect/Center not works on vga and 
dvi connectors
  drm/i915: Fix type1 DVI DP dual mode adapter heuristic for modern platforms
  drm/i915/dp: Ensure max link params are always valid
  drm/i915/dp: Ensure sink rate values are always valid
  drm/nouveau: clean up all clients on device removal
  drm/nouveau: use drm_dev_unplug() during device removal
  drm/nouveau: Add a dedicated mutex for the clients list
  drm/prime: Fix use after free in mmap with drm_gem_ttm_mmap
  drm/udl: fix control-message timeout
  drm/i915/guc: Unwind context requests in reverse order
  drm/i915/guc: Don't drop ce->guc_active.lock when unwinding context
  drm/i915/guc: Workaround reset G2H is received after schedule done G2H
  drm/i915/guc: Don't enable scheduling on a banned context, guc_id invalid, 
not registered
  drm/i915/guc: Fix outstanding G2H accounting
  drm/amd/display: Limit max DSC target bpp for specific monitors
  drm/amd/display: Update swizzle mode enums
  mac80211: drop check for DONT_REORDER in __ieee80211_select_queue
  mac80211: fix radiotap header generation
  cfg80211: call cfg80211_stop_ap when switch from P2P_GO type
  parisc/sticon: fix reverse colors
  net: stmmac: Fix signed/unsigned wreckage
  fs: handle circular mappings correctly
  btrfs: fix memory ordering between normal and ordered work functions
  Drivers: hv: balloon: Use VMBUS_RING_SIZE() wrapper for dm_ring_size
  net: stmmac: socfpga: add runtime suspend/resume callback for stratix10 
platform
  spi: fix use-after-free of the add_lock mutex
  udf: Fix crash after seekdir
  printk: restore flushing of NMI buffers on remote CPUs after NMI backtraces
  drm/cma-helper: Release non-coherent memory with dma_free_noncoherent()
  KVM: nVMX: don't use vcpu->arch.efer when checking host state on nested state 
load
  KVM: SEV: Disallow COPY_ENC_CONTEXT_FROM if target has created vCPUs
  fbdev: Prevent probing generic drivers if a FB is already registered
  block: Check ADMIN before NICE for IOPRIO_CLASS_RT
  s390/dump: fix copying to user-space of swapped kdump oldmem
  s390/kexec: fix 

[Kernel-packages] [Bug 1949063] Re: Add F81966 watchdog support

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  Add F81966 watchdog support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in linux-hwe-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.11 source package in Focal:
  Fix Released
Status in linux-hwe-5.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid
Status in linux-hwe-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Committed
Status in linux-hwe-5.11 source package in Impish:
  Invalid
Status in linux-hwe-5.13 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-hwe-5.11 source package in Jammy:
  Invalid
Status in linux-hwe-5.13 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  f71808e_wdt watchdog driver can't recognize F81966 chip.

  [Fix]
  AAEON provides a patch to add the ID.
  https://www.spinics.net/lists/kernel/msg4147351.html

  [Test]
  Testing was done on the Aaeon SSE-OPTI

  [Where problems could occur]
  Simply adding one ID, should not introduce any regressions.

  [Misc]
  This patch is for ODM project and need this to be included as soon as 
possible, so we submit this patch as a sauce patch before upstream merges it.
  BTW, Jammy already included this commit when the patch was submitted for the 
SRU the first time.

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


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

[Kernel-packages] [Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  Fix A yellow screen pops up in an instant (< 1 second) and then
  disappears before loading the system

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Impact]
  *** this issue happen with secure boot on and issue gone when secure boot is 
off***

  After the BIOS loading screen, a yellow screen pops up in an instant
  (< 1 second) and then disappears. Attached a demo video.

  [Fix]
  do what intel_color_commit() does to make sure the bottom color state
  matches whatever out hardware readout produced.
  Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171=1

  [Test]
  1. Power on the system
  2. Check if any unusual screen shows before and after the system loading 
screen.
  3. No unusual screen shows before and after the system loading screen

  [Regression Potential]
  Medium, maintainer still not totally sure what should do about color 
management
  features here in general.

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


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

[Kernel-packages] [Bug 1951820] Re: Jammy update: v5.15.4 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1951820

Title:
  Jammy update: v5.15.4 upstream stable release

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  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:

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

  
  Linux 5.15.4
  Revert "ACPI: scan: Release PM resources blocked by unused objects"
  thermal: Fix NULL pointer dereferences in of_thermal_ functions
  perf/core: Avoid put_page() when GUP fails
  PCI: Add MSI masking quirk for Nvidia ION AHCI
  PCI/MSI: Deal with devices lying about their MSI mask capability
  parisc/entry: fix trace test in syscall exit path
  Bluetooth: btusb: Add support for TP-Link UB500 Adapter
  loop: Use blk_validate_block_size() to validate block size
  block: Add a helper to validate the block size
  fortify: Explicitly disable Clang support
  btrfs: zoned: allow preallocation for relocation inodes
  btrfs: check for relocation inodes on zoned btrfs in should_nocow
  btrfs: zoned: use regular writes for relocation
  btrfs: zoned: only allow one process to add pages to a relocation inode
  btrfs: zoned: add a dedicated data relocation block group
  btrfs: introduce btrfs_is_data_reloc_root
  KVM: Fix steal time asm constraints
  Revert "drm: fb_helper: fix CONFIG_FB dependency"
  Revert "drm: fb_helper: improve CONFIG_FB dependency"
  string: uninline memcpy_and_pad

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


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

[Kernel-packages] [Bug 1945989] Re: Check for changes relevant for security certifications

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

Title:
  Check for changes relevant for security certifications

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Released

Bug description:
  [Impact]

  When producing a new version of some kernels, we need to check for
  changes that might affect FIPS or other certs and justify why a commit
  was kept or removed.

  To simplify this process we can add an automated check that will abort
  the kernel preparation and build when such changes exist without a
  justification.

  [Test Plan]

  Check if the kernel preparation fails (cranky close) when one of a
  security certification changes is added.

  [Where problems could occur]

  No kernels should be affected until we enable this check on each one.
  Even when enabled, that only affects the kernel preparation and not
  the resulting kernel.

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


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

[Kernel-packages] [Bug 1953208] Re: Fix bogus HDMI audio interface

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1953208

Title:
  Fix bogus HDMI audio interface

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Bogus HDMI audio can be selected as output, without any HDMI monitor
  connected.

  [Fix]
  Consider 0 SAD as invalid ELD - no SAD means no audio.

  [Test]
  With the patch applied, no bogus HDMI audio can be found in GNOME's
  setting app.

  [Where problems could occur]
  Basically none. No SAD means no PCM - so it has never worked before.

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


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

[Kernel-packages] [Bug 1950974] Re: Improve USB Type-C support

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1950974

Title:
  Improve USB Type-C support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Confirmed

Bug description:
  [Impact]
  Error message "ucsi_acpi USBC000:00: GET_CONEECTOR_STATUS failed (-110)"
  can be found on many systems.

  [Fix]
  The main issue is that the PD firmware is unreliable, so use more
  deterministic methods to make it reliable 

  [Test]
  The error message is gone. Also tried to plug/unplug USB Type-C power
  cord, and the status are always reported correctly.

  [Where problems could occur]
  This is quite a huge refactor, so regression can be expected. Only
  target to unstable and latest OEM kernel to reduce risk we are taking.

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


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

[Kernel-packages] [Bug 1953286] Re: Add support for NVIDIA EC backlight

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1953286

Title:
  Add support for NVIDIA EC backlight

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Released

Bug description:
  
  [Impact]
  Some system equipped with NVIDIA GFX cannot change screen brightness.

  [Fix]
  Add new way to change brightness.

  [Test]
  After the fix is applied, there's a new backlight sysfs
  "nvidia_wmi_ec_backlight" can change the screen brightness.

  [Where problems could occur]
  The driver relies on BIOS to behave correctly. If the BIOS lies or has a
  bug, the new backlight interface will overtake other backlight
  interfaces. It's rather unlikely though.

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


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

[Kernel-packages] [Bug 1954300] Re: mt7921e: Failed to start WM firmware

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  mt7921e: Failed to start WM firmware

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Committed
Status in linux-firmware source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  MT7921 might fail at device probe at boot:

  mt7921e :03:00.0: WM Firmware Version: 01, Build Time: 
20211014150922
  IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
  mt7921e :03:00.0: Message 8002 (seq 9) timeout
  mt7921e :03:00.0: Failed to start WM firmware
  mt7921e: probe of :03:00.0 failed with error -110

  [Fix]

  Kernel fixes:
  * 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
  * 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")

  And firmware:
  * 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")

  [Test Case]

  Run checkbox reboot stress tests to try trigger this issue:

$ checkbox-cli run com.canonical.certification::stress/reboot

  [Where problems could occur]

  This imports fixes requiring both kernel driver and proprietary firmware
  updates, the firmware part might cause instability or so.

  == original bug report ==

  Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware 
Version: 01, Build Time: 20211014150922
  Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
  Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up - 
1Gbps/Full - flow control rx/tx
  Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: 
link becomes ready
  Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64, 
error -110
  Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002 
(seq 9) timeout
  Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start 
WM firmware
  Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed 
with error -110

  This takes following fixes to resolve completely:
  * kernel patch:
    * 
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
    * 
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
  * firmware:
    * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a

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


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

[Kernel-packages] [Bug 1945967] Re: rtw89 kernel module for Realtek 8852 wifi is missing

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1945967

Title:
  rtw89 kernel module for Realtek 8852 wifi is missing

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Confirmed

Bug description:
  == SRU Justification ==
  [Impact]
  Realtek 8852AE, which is used by many new laptops, doesn't have a
  driver.

  [Fix]
  Add rtw89 driver to support Realtek 8852AE.

  [Test]
  After applying the patch, 8852AE can scan, connect and do TX/RX.

  [Where problems could occur]
  This is a brand new driver, unless the driver hits some subtle PCI or
  IOMMU bugs, there isn't much chance to introduce any regression.

  == Original Bug Report ==
  Hi,

  Resulting: no wifi adapter detected.
  Currently WIP: 
https://patchwork.kernel.org/project/linux-wireless/list/?series=534633=*

  Workaround: use https://github.com/lwfinger/rtw89
  that allows to build a dkms deb package.

  Ubuntu Impish
  kernel 5.13 (or 5.15 from unstable ppa)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fthx   4574 F pulseaudio
   /dev/snd/controlC2:  fthx   4574 F pulseaudio
   /dev/snd/controlC0:  fthx   4574 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-09-15 (20 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  MachineType: LENOVO 21AVFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpu
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-4-generic N/A
   linux-backports-modules-5.15.0-4-generic  N/A
   linux-firmware1.201
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-4-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: 06/21/2021
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET39W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21AVFR
  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.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21AVFR
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1953192] Re: Enable Landlock by default

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

Title:
  Enable Landlock by default

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  The Landlock security feature is built in Ubuntu kernel since 5.13
  which is great!  However, it is not enough to enable the
  CONFIG_SECURITY_LANDLOCK option as described in the related help. The
  CONFIG_LSM option needs to be prepended by "landlock," to make
  Landlock system calls available without modifying the kernel boot
  arguments.

  Could you please update the CONFIG_LSM variable accordingly?

  Regards,
   Mickaël

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


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

[Kernel-packages] [Bug 1951861] Re: Fix non-working e1000e device after resume

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1951861

Title:
  Fix non-working e1000e device after resume

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Impact]
  e1000e devices stop working after s2idle resume.

  [Fix] 
  Revert the offending patch series, which is to bring some minor power
  saving.
   
  [Test]
  Vendor did extensive tests and didn't find any regression, and the power
  consumption remains the same.

  [Where problems could occur]
  Maybe on some system the series can save some energy, so reverting will
  cause some power consumption increase.

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


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

[Kernel-packages] [Bug 1950013] Re: Add s0i3 RTC wake up for AMD systems

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  Add s0i3 RTC wake up for AMD systems

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released

Bug description:
  [Impact]

    RTC based wakeup is not supported natively by the hardware for s0i3.

  [Fix]

    A firmware and driver updates were implemented. The driver passes
  wakeup time to SMU to to enable RTC from S0i3.

    Note this s0i3 RTC wake up also requires new firmware.

    The first patch is the prerequisite actual fix (patch 2 and 3).

  [Test]

    This is requested by AMD and tested by an AMD developer as below:

  Testing a suspend run with RTC for 15 seconds and then 30 seconds:
  ```
  $ sudo rtcwake --seconds 15 -m mem
  rtcwake: assuming RTC uses UTC ...
  rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021
  $ sudo rtcwake --seconds 30 -m mem
  rtcwake: assuming RTC uses UTC ...
  rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021
  $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats
  === S0ix statistics ===
  S0ix Entry Time: 4793618285
  S0ix Exit Time: 6209036738
  Residency Time: 29487884
  ```
  Residency divided by 100 is 29.4 seconds.

  Reading idle mask works fine too.

  [Where problems could occur]

    Low risk.

    First patch only exports Idlemask value.
    The actual fix only affects a specific AMD CPU (CZN).

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


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

[Kernel-packages] [Bug 1949321] Re: Fix System hangs on black screen when reboot

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  Fix System hangs on black screen when reboot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.10 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  System hangs on black screen when reboot

  [Fix]
  Looks like our VBIOS/GOP generally fail to turn the DP dual mode adater
  TMDS output buffers back on after a reboot. This leads to a black screen
  after reboot if we turned the TMDS output buffers off prior to reboot.
  And if i915 decides to do a fastboot the black screen will persist even
  after i915 takes over.
  
  Apparently this has been a problem ever since commit b2ccb822d376 
("drm/i915:Enable/disable TMDS output buffers in DP++ adaptor as needed") if 
one rebooted while the display was turned off. And things became worse with 
commit fe0f1e3bfdfe ("drm/i915: Shut down displays gracefully on reboot") since 
now we always turn the display off before a reboot.
  
  This was reported on a RKL, but I confirmed the same behaviour on my
  SNB as well. So looks pretty universal.
  
  Let's fix this by explicitly turning the TMDS output buffers back on
  in the encoder->shutdown() hook. Note that this gets called after irqs
  have been disabled, so the i2c communication with the DP dual mode
  adapter has to be performed via polling (which the gmbus code is
  perfectly happy to do for us).
  
  We also need a bit of care in handling DDI encoders which may or may
  not be set up for HDMI output. Specifically ddc_pin will not be
  populated for a DP only DDI encoder, in which case we don't want to
  call intel_gmbus_get_adapter(). We can handle that by simply doing
  the dual mode adapter type check before calling
  intel_gmbus_get_adapter().
  Ref: https://patchwork.freedesktop.org/series/96433/

  [Test]
  1. install kernel
  2. reboot
  3. check the monitor works well.

  [Regression Potential]
  Medium, patch has sent to patchwork but may have a upgraded version in the 
furtue.

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


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

[Kernel-packages] [Bug 1951767] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  [SRU][I/J/OEM-5.13/OEM-5.14] Add MAC passthrough support for more
  Lenovo docks

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  MAC pass through is not working on new TBT and USB-C docks.

  [Fix]
  Enable MAC pass through based on Lenovo USB hub.

  [Test]
  Tested on Lenovo TBT4 and TBT3 dock, MAC pass through works well.

  [Where problems could occur]
  The Realtek USB ethernet in Lenovo USB hub will mess the MAC address.

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


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

[Kernel-packages] [Bug 1953370] Re: Jammy update: v5.15.6 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1953370

Title:
  Jammy update: v5.15.6 upstream stable release

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  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:

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

  
  Linux 5.15.6
  drm/amdgpu/gfx9: switch to golden tsc registers for renoir+
  drm/amdgpu/gfx10: add wraparound gpu counter check for APUs as well
  block: avoid to quiesce queue in elevator_init_mq
  blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and 
disk_release()
  docs: accounting: update delay-accounting.rst reference
  firmware: arm_scmi: Fix type error in sensor protocol
  firmware: arm_scmi: Fix type error assignment in voltage protocol
  io_uring: fix soft lockup when call __io_remove_buffers
  cifs: nosharesock should be set on new server
  tracing: Check pid filtering when creating events
  ksmbd: Fix an error handling path in 'smb2_sess_setup()'
  vhost/vsock: fix incorrect used length reported to the guest
  vdpa_sim: avoid putting an uninitialized iova_domain
  iommu/amd: Clarify AMD IOMMUv2 initialization messages
  ceph: properly handle statfs on multifs setups
  cifs: nosharesock should not share socket with future sessions
  riscv: dts: microchip: drop duplicated MMC/SDHC node
  riscv: dts: microchip: fix board compatible
  f2fs: set SBI_NEED_FSCK flag when inconsistent node block found
  f2fs: quota: fix potential deadlock
  iommu/vt-d: Fix unmap_pages support
  iommu/rockchip: Fix PAGE_DESC_HI_MASKs for RK3568
  sched/scs: Reset task stack state in bringup_cpu()
  perf: Ignore sigtrap for tracepoints destined for other tasks
  locking/rwsem: Make handoff bit handling more consistent
  net: mscc: ocelot: correctly report the timestamping RX filters in ethtool
  net: mscc: ocelot: don't downgrade timestamping RX filters in SIOCSHWTSTAMP
  net: hns3: fix incorrect components info of ethtool --reset command
  net: hns3: fix VF RSS failed problem after PF enable multi-TCs
  net/smc: Don't call clcsock shutdown twice when smc shutdown
  net: vlan: fix underflow for the real_dev refcnt
  ethtool: ioctl: fix potential NULL deref in ethtool_set_coalesce()
  net/sched: sch_ets: don't peek at classes beyond 'nbands'
  net: stmmac: Disable Tx queues when reconfiguring the interface
  tls: fix replacing proto_ops
  tls: splice_read: fix accessing pre-processed records
  tls: splice_read: fix record type check
  MIPS: use 3-level pgtable for 64KB page size on MIPS_VA_BITS_48
  MIPS: loongson64: fix FTLB configuration
  igb: fix netpoll exit with traffic
  nvmet: use IOCB_NOWAIT only if the filesystem supports it
  net/smc: Fix loop in smc_listen
  net/smc: Fix NULL pointer dereferencing in smc_vlan_by_tcpsk()
  net: phylink: Force retrigger in case of latched link-fail indicator
  net: phylink: Force link down and retrigger resolve on interface change
  lan743x: fix deadlock in lan743x_phy_link_status_change()
  tcp_cubic: fix spurious Hystart ACK train detections for not-cwnd-limited 
flows
  drm/amd/display: Set plane update flags for all planes in reset
  drm/amd/display: Fix DPIA outbox timeout after GPU reset
  PM: hibernate: use correct mode for swsusp_close()
  net/ncsi : Add payload to be 32-bit aligned to fix dropped packets
  arm64: uaccess: avoid blocking within critical sections
  drm/hyperv: Fix device removal on Gen1 VMs
  nvmet-tcp: fix incomplete data digest send
  cpufreq: intel_pstate: Add Ice Lake server to out-of-band IDs
  net: marvell: mvpp2: increase MTU limit when XDP enabled
  net: ipa: kill ipa_cmd_pipeline_clear()
  net: ipa: separate disabling setup from modem stop
  net: ipa: directly disable ipa-setup-ready interrupt
  mlxsw: spectrum: Protect driver from buggy firmware
  net/smc: Ensure the active closing peer first closes clcsock
  i2c: virtio: disable timeout handling
  erofs: fix deadlock when shrink erofs slab
  scsi: scsi_debug: Zero clear zones at reset write pointer
  scsi: core: sysfs: Fix setting device state to SDEV_RUNNING
  ice: avoid bpf_prog 

[Kernel-packages] [Bug 1950949] Re: Jammy update: v5.15.2 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1950949

Title:
  Jammy update: v5.15.2 upstream stable release

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  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:

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

  
  Linux 5.15.2
  rsi: fix control-message timeout
  media: staging/intel-ipu3: css: Fix wrong size comparison imgu_css_fw_init
  staging: r8188eu: fix memleak in rtw_wx_set_enc_ext
  staging: rtl8192u: fix control-message timeouts
  staging: r8712u: fix control-message timeout
  comedi: vmk80xx: fix bulk and interrupt message timeouts
  comedi: vmk80xx: fix bulk-buffer overflow
  comedi: vmk80xx: fix transfer-buffer overflows
  comedi: ni_usb6501: fix NULL-deref in command paths
  comedi: dt9812: fix DMA buffers on stack
  isofs: Fix out of bound access for corrupted isofs image
  staging: rtl8712: fix use-after-free in rtl8712_dl_fw
  btrfs: fix lzo_decompress_bio() kmap leakage
  kfence: default to dynamic branch instead of static keys mode
  kfence: always use static branches to guard kfence_alloc()
  binder: don't detect sender/target during buffer cleanup
  binder: use cred instead of task for getsecid
  binder: use cred instead of task for selinux checks
  binder: use euid from cred instead of using task
  Revert "proc/wchan: use printk format instead of lookup_symbol_name()"
  usb-storage: Add compatibility quirk flags for iODD 2531/2541
  usb: musb: Balance list entry in musb_gadget_queue
  usb: gadget: Mark USB_FSL_QE broken on 64-bit
  usb: ehci: handshake CMD_RUN instead of STS_HALT
  Revert "x86/kvm: fix vcpu-id indexed array sizes"
  KVM: x86: avoid warning with -Wbitwise-instead-of-logical

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


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

[Kernel-packages] [Bug 1951440] Re: Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1951440

Title:
  Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and
  CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15

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

Bug description:
  Starting with the following commit, upstream kernel is enabling Intel
  IOMMU related options by default:

   792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by
  default")

  We should follow upstream direction enabling
  CONFIG_INTEL_IOMMU_DEFAULT_ON and
  CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.

  A downside is that this change may introduce boot regressions on old
  systems (especially those with buggy firmware).

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


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

[Kernel-packages] [Bug 1951784] Re: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  Can't read/write SD card after running CPU offline test in 5.11.0 and
  5.13.0

Status in linux package in Ubuntu:
  Fix Released
Status in linux-signed-hwe-5.11 package in Ubuntu:
  New
Status in linux-signed-hwe-5.13 package in Ubuntu:
  New

Bug description:
  [Summary]
  I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard 
test always fails.
  I found that after CPU offline test, I can't read/write SD card.
  After checking dmesg, I got those error msgs.
  [  232.577510] __common_interrupt: 7.34 No irq handler for vector
  [  234.354327] mmc0: error -110 doing runtime resume

  I found the same issue on Dell Precision 3551(202002-27718) and Dell
  Precision 5530(201807-26342) in 5.13.0-21 and 5.11.0-36

  Before I didn't think it's a bug since I re-run mediacard test then
  it's pass. But this cycle there are more systems failed to the test, I
  just started digging into that.

  [Step to reproduce]
  1. install ubuntu-20.04.2/ubuntu-21.10/ubuntu-21.04
  2. sudo apt update; sudo apt dist-upgrade -y
  3. run cpu offline test via checkbox-cli or execute following command
     for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; 
done;
     cd $mount_point_of_sd_card
     sudo dd if=/dev/urandom of=test bs=1M count=10

  [Expected result]
  Can read/write SD card.

  [Actual result]
  Can't read/write SD card.

  [Failure rate]
  5/5

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Nov 22 01:28:59 2021
  InstallationDate: Installed on 2020-08-03 (475 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1951822] Re: Jammy update: v5.15.3 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1951822

Title:
  Jammy update: v5.15.3 upstream stable release

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  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:

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

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


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

[Kernel-packages] [Bug 1956302] Re: Jammy update: v5.15.11 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1956302

Title:
  Jammy update: v5.15.11 upstream stable release

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  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:

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

  
  Linux 5.15.11
  xen/netback: don't queue unlimited number of packages
  xen/netback: fix rx queue stall detection
  xen/console: harden hvc_xen against event channel storms
  xen/netfront: harden netfront against event channel storms
  xen/blkfront: harden blkfront against event channel storms
  Revert "xsk: Do not sleep in poll() when need_wakeup set"
  selftests/damon: test debugfs file reads/writes with huge count
  bus: ti-sysc: Fix variable set but not used warning for reinit_modules
  io-wq: drop wqe lock before creating new worker
  rcu: Mark accesses to rcu_state.n_force_qs
  io-wq: check for wq exit after adding new worker task_work
  io-wq: remove spurious bit clear on task_work addition
  scsi: scsi_debug: Sanity check block descriptor length in resp_mode_select()
  scsi: scsi_debug: Fix type in min_t to avoid stack OOB
  scsi: scsi_debug: Don't call kcalloc() if size arg is zero
  ovl: fix warning in ovl_create_real()
  fuse: annotate lock in fuse_reverse_inval_entry()
  media: mxl111sf: change mutex_init() location
  USB: core: Make do_proc_control() and do_proc_bulk() killable
  bpf: Fix extable address check.
  bpf, x64: Factor out emission of REX byte in more cases
  mptcp: add missing documented NL params
  xsk: Do not sleep in poll() when need_wakeup set
  ARM: dts: imx6ull-pinfunc: Fix CSI_DATA07__ESAI_TX0 pad name
  can: m_can: pci: use custom bit timings for Elkhart Lake
  can: m_can: make custom bittiming fields const
  Revert "can: m_can: remove support for custom bit timing"
  drm/amd/pm: fix reading SMU FW version from amdgpu_firmware_info on YC
  drm/amdgpu: don't override default ECO_BITs setting
  drm/amdgpu: correct register access for RLC_JUMP_TABLE_RESTORE
  powerpc/module_64: Fix livepatching for RO modules
  libata: if T_LENGTH is zero, dma direction should be DMA_NONE
  perf inject: Fix segfault due to perf_data__fd() without open
  perf inject: Fix segfault due to close without open
  riscv: dts: unmatched: Add gpio card detect to mmc-spi-slot
  riscv: dts: unleashed: Add gpio card detect to mmc-spi-slot
  locking/rtmutex: Fix incorrect condition in rtmutex_spin_on_owner()
  cifs: sanitize multiple delimiters in prepath
  timekeeping: Really make sure wall_to_monotonic isn't positive
  serial: 8250_fintek: Fix garbled text for console
  iocost: Fix divide-by-zero on donation from low hweight cgroup
  zonefs: add MODULE_ALIAS_FS
  btrfs: fix missing blkdev_put() call in btrfs_scan_one_device()
  btrfs: check WRITE_ERR when trying to read an extent buffer
  btrfs: fix double free of anon_dev after failure to create subvolume
  btrfs: fix memory leak in __add_inode_ref()
  selinux: fix sleeping function called from invalid context
  USB: serial: option: add Telit FN990 compositions
  USB: serial: cp210x: fix CP2105 GPIO registration
  usb: gadget: u_ether: fix race in setting MAC address in setup phase
  usb: typec: tcpm: fix tcpm unregister port but leave a pending timer
  usb: cdnsp: Fix lack of spin_lock_irqsave/spin_lock_restore
  usb: cdnsp: Fix issue in cdnsp_log_ep trace event
  usb: cdnsp: Fix incorrect calling of cdnsp_died function
  usb: cdnsp: Fix incorrect status for control request
  usb: xhci: Extend support for runtime power management for AMD's Yellow carp.
  usb: xhci-mtk: fix list_del warning when enable list debug
  PCI/MSI: Mask MSI-X vectors only on success
  PCI/MSI: Clear PCI_MSIX_FLAGS_MASKALL on error
  usb: dwc2: fix STM ID/VBUS detection startup delay in dwc2_driver_probe
  USB: NO_LPM quirk Lenovo USB-C to Ethernet Adapher(RTL8153-04)
  tty: n_hdlc: make n_hdlc_tty_wakeup() asynchronous
  KVM: x86: Drop guest CPUID check for host initiated writes to 
MSR_IA32_PERF_CAPABILITIES
  Revert "usb: early: convert to readl_poll_timeout_atomic()"
  USB: 

[Kernel-packages] [Bug 1956305] Re: Jammy update: v5.15.12 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1956305

Title:
  Jammy update: v5.15.12 upstream stable release

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  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:

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

  
  Linux 5.15.12
  phonet/pep: refuse to enable an unbound pipe
  tun: avoid double free in tun_free_netdev
  hamradio: improve the incomplete fix to avoid NPD
  hamradio: defer ax25 kfree after unregister_netdev
  ax25: NPD bug when detaching AX25 device
  r8152: sync ocp base
  hwmon: (lm90) Do not report 'busy' status bit as alarm
  hwmom: (lm90) Fix citical alarm status for MAX6680/MAX6681
  pinctrl: mediatek: fix global-out-of-bounds issue
  ASoC: rt5682: fix the wrong jack type detected
  ASoC: SOF: Intel: pci-tgl: add ADL-N support
  ASoC: SOF: Intel: pci-tgl: add new ADL-P variant
  ASoC: tas2770: Fix setting of high sample rates
  Input: goodix - add id->model mapping for the "9111" model
  Input: elants_i2c - do not check Remark ID on eKTH3900/eKTH5312
  Input: iqs626a - prohibit inlining of channel parsing functions
  kfence: fix memory leak when cat kfence objects
  arm64: dts: lx2160a: fix scl-gpios property name
  KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state
  netfs: fix parameter of cleanup()
  f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr()
  tee: optee: Fix incorrect page free bug
  mm/damon/dbgfs: protect targets destructions with kdamond_lock
  mm/hwpoison: clear MF_COUNT_INCREASED before retrying get_any_page()
  mm, hwpoison: fix condition in free hugetlb page path
  mm: mempolicy: fix THP allocations escaping mempolicy restrictions
  mac80211: fix locking in ieee80211_start_ap error path
  ksmbd: disable SMB2_GLOBAL_CAP_ENCRYPTION for SMB 3.1.1
  ksmbd: fix uninitialized symbol 'pntsd_size'
  ksmbd: fix error code in ndr_read_int32()
  ARM: 9169/1: entry: fix Thumb2 bug in iWMMXt exception handling
  mmc: mmci: stm32: clear DLYB_CR after sending tuning command
  mmc: core: Disable card detect during shutdown
  mmc: meson-mx-sdhc: Set MANUAL_STOP for multi-block SDIO commands
  mmc: sdhci-tegra: Fix switch to HS400ES mode
  gpio: dln2: Fix interrupts when replugging the device
  pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines
  KVM: VMX: Wake vCPU when delivering posted IRQ even if vCPU == this vCPU
  KVM: VMX: Always clear vmx->fail on emulation_required
  KVM: nVMX: Synthesize TRIPLE_FAULT for L2 if emulation is required
  KVM: x86/mmu: Don't advance iterator after restart due to yielding
  KVM: x86: Always set kvm_run->if_flag
  platform/x86: intel_pmc_core: fix memleak on registration failure
  platform/x86: amd-pmc: only use callbacks for suspend
  x86/pkey: Fix undefined behaviour with PKRU_WD_BIT
  tee: handle lookup of shm with reference count 0
  parisc: Fix mask used to select futex spinlock
  parisc: Correct completer in lws start
  ipmi: fix initialization when workqueue allocation fails
  ipmi: ssif: initialize ssif_info->client early
  ipmi: bail out if init_srcu_struct fails
  Input: atmel_mxt_ts - fix double free in mxt_read_info_block
  ASoC: tegra: Restore headphones jack name on Nyan Big
  ASoC: tegra: Add DAPM switches for headphones and mic jack
  ASoC: meson: aiu: Move AIU_I2S_MISC hold setting to aiu-fifo-i2s
  ALSA: hda/realtek: Fix quirk for Clevo NJ51CU
  ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook
  ALSA: hda/realtek: Add new alc285-hp-amp-init model
  ALSA: hda/realtek: Amp init fixup for HP ZBook 15 G6
  ALSA: hda/hdmi: Disable silent stream on GLK
  ALSA: rawmidi - fix the uninitalized user_pversion
  ALSA: drivers: opl3: Fix incorrect use of vp->state
  ALSA: jack: Check the return value of kstrdup()
  x86/boot: Move EFI range reservation after cmdline parsing
  Revert "x86/boot: Pull up cmdline preparation and early param parsing"
  kernel/crash_core: suppress unknown crashkernel parameter warning
  platform/x86/intel: Remove X86_PLATFORM_DRIVERS_INTEL
  compiler.h: Fix 

[Kernel-packages] [Bug 1955161] Re: Jammy update: v5.15.9 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1955161

Title:
  Jammy update: v5.15.9 upstream stable release

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  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:

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

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


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

[Kernel-packages] [Bug 1955443] Re: Fix USB3 detection on HP dock

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => Fix Released

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

Title:
   Fix USB3 detection on HP dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Confirmed
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  Hotplug a USB3 device to HP dock can go undetected.

  [Fix]
  Add a delay for USB3 hub resume routine so the link has enough time to
  transit to U0. 

  [Test]
  After the patch is applied, the dock can always detect USB3 devices.

  [Where problems could occur]
  A non-noticeable delay was added, so no basically no impact.

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


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

[Kernel-packages] [Bug 1955686] Re: alsa/sdw: fix the audio sdw codec parsing logic in the acpi table

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  alsa/sdw: fix the  audio sdw codec parsing logic in the acpi table

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Impish:
  Fix Committed
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  we have a couple of Dell ADL laptops which have sdw audio, after upgrading
  the BIOS to 0.1.4 or above, the sdw audio can't work anymore, the driver
  can't parse the codec layout from ACPI table anymore.

  
  [Fix]
  Backport two patches from upstream.

  [Test]
  Boot the patched kernel on those machines both with old bios and
  new bios, all work well, the sdw audio could initialize and the
  audio function work well.

  [Where problems could occur]
  If it could introduce regression, it will be on the acpi sdw codec
  parsing, so some sdw audio machines could fail to find the codec, then
  the whole audio function fails. But this possibility is very low, we
  already tested the patches on both old bios and new bios.

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


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

[Kernel-packages] [Bug 1956780] Re: 5.15 stuck at boot on c4.large

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

Title:
  5.15 stuck at boot on c4.large

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  c4.large instances are stuck at boot with kernel 5.15.0-15.15.

  [Test case]

  Simply deploy a c4.large instance and install the latest jammy kernel
  (5.15.0-15.15).

  [Fix]

  It looks like the offending commit is the following:

   02c70033b98b ("PCI/MSI: Mask MSI-X vectors only on success")

  Reverting the commit fixes the problem.

  [Regression potential]

  It looks like the commit was fixing a potential breakage with broken
  Marvell NVME devices, so we may see crashes in presence of these
  devices. However, reverting the commit we are simply restoring the
  previous behavior, so potential regressions should be limited to these
  broken devices.

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


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

[Kernel-packages] [Bug 1954931] Re: Jammy update: v5.15.8 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1954931

Title:
  Jammy update: v5.15.8 upstream stable release

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  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:

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

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


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

[Kernel-packages] [Bug 1955790] Re: Got black screen when resume from s2idle with AMD dGPU

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

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

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

Title:
  Got black screen when resume from s2idle with AMD dGPU

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  On Dell AIO with AMD dGPU platforms, it looks like AMD dGPU can't be waken up 
after s2idle and got black screen.

  [Fix]
  AMD provides us 2 commits to fix this issue.
  https://patchwork.freedesktop.org/patch/463002/
  https://patchwork.freedesktop.org/series/98338/

  [Test]
  Verified by AMD.

  [Where problems could occur]
  It should be fine to reset the asic and set to the proper state while 
entering suspended.

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


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

[Kernel-packages] [Bug 1956301] Re: Jammy update: v5.15.10 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-17.17

---
linux (5.15.0-17.17) jammy; urgency=medium

  * jammy/linux: 5.15.0-17.17 -proposed tracker (LP: #1957809)

 -- Andrea Righi   Thu, 13 Jan 2022 17:11:21
+0100

** Changed in: linux (Ubuntu Jammy)
   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/1956301

Title:
  Jammy update: v5.15.10 upstream stable release

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  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:

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

  
  Linux 5.15.10
  perf inject: Fix itrace space allowed for new attributes
  fuse: make sure reclaim doesn't write the inode
  staging: most: dim2: use device release method
  tracing: Fix a kmemleak false positive in tracing_map
  drm/amdkfd: process_info lock not needed for svm
  drm/amd/display: add connector type check for CRC source set
  drm/amdkfd: fix double free mem structure
  drm/amd/display: Fix for the no Audio bug with Tiled Displays
  drm/amdgpu: check atomic flag to differeniate with legacy path
  drm/amdgpu: cancel the correct hrtimer on exit
  net: netlink: af_netlink: Prevent empty skb by adding a check on len.
  i2c: rk3x: Handle a spurious start completion interrupt flag
  parisc/agp: Annotate parisc agp init functions with __init
  ALSA: hda/hdmi: fix HDA codec entry table order for ADL-P
  ALSA: hda: Add Intel DG2 PCI ID and HDMI codec vid
  loop: Use pr_warn_once() for loop_control_remove() warning
  net/mlx4_en: Update reported link modes for 1/10G
  Revert "tty: serial: fsl_lpuart: drop earlycon entry for i.MX8QXP"
  s390/test_unwind: use raw opcode instead of invalid instruction
  KVM: arm64: Save PSTATE early on exit
  drm/msm/dp: Avoid unpowered AUX xfers that caused crashes
  drm/msm/dsi: set default num_data_lanes
  drm/msm/a6xx: Fix uinitialized use of gpu_scid
  drm/msm: Fix null ptr access msm_ioctl_gem_submit()
  i2c: virtio: fix completion handling
  vmxnet3: fix minimum vectors alloc issue
  ice: fix FDIR init missing when reset VF
  RDMA/irdma: Don't arm the CQ more than two times if no CE for this CQ
  RDMA/irdma: Report correct WC errors
  RDMA/irdma: Fix a potential memory allocation issue in 
'irdma_prm_add_pble_mem()'
  RDMA/irdma: Fix a user-after-free in add_pble_prm
  netfs: Fix lockdep warning from taking sb_writers whilst holding mmap_lock
  perf bpf_skel: Do not use typedef to avoid error on old clang
  clk: qcom: sm6125-gcc: Swap ops of ice and apps on sdcc1
  dt-bindings: media: nxp,imx7-mipi-csi2: Drop bad if/then schema
  inet: use #ifdef CONFIG_SOCK_RX_QUEUE_MAPPING consistently
  mtd: rawnand: Fix nand_choose_best_timings() on unsupported interface
  mtd: rawnand: Fix nand_erase_op delay
  RDMA/mlx5: Fix releasing unallocated memory in dereg MR flow
  RDMA: Fix use-after-free in rxe_queue_cleanup
  hwmon: (corsair-psu) fix plain integer used as NULL pointer
  nfc: fix segfault in nfc_genl_dump_devices_done

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


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

[Kernel-packages] [Bug 1958153] Re: [SRU][F]Add firmware of MT7922

[AaronMa]

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

** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => 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/1958153

Title:
  [SRU][F]Add firmware of MT7922

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  No driver is loaded for MT7922, and fw is missing too.

  [Fix]
  Add firmware of MT7922 wifi and bluetooth.

  [Test]
  Verified on RZ616, it works fine, suspend OK.
  iperf test result looks fine.
  Bluetooth works fine.

  [Where problems could occur]
  These firmware is specific for MT7922, it should be low risk.

  The firmware is already in impish and jammy, only SRU fw for focal.

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


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

[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390

[Ubuntu Foundations Team Bug Bot]

The attachment "18-lp1957094-adjust-on-demand-mode-description.patch"
seems to be a patch.  If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in nvidia-settings source package in Impish:
  New
Status in ubuntu-drivers-common source package in Impish:
  Triaged
Status in nvidia-settings source package in Jammy:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

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


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

[Kernel-packages] [Bug 1958155] Re: Pod traffic not taking advantage of interfaces with multiple tx queues

[Tim Gardner]

** Description changed:

  SRU Justification
  
  [Impact]
  
  
https://patchwork.kernel.org/project/netdevbpf/patch/ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.dan...@iogearbox.net/
  
  Performance is impacted when multiple TX queues are enabled.
  
  [Fix]
  commit 710ad98c363a66a0cd8526465426c5c5f8377ee0 ("veth: Do not record rx 
queue hint in veth_xmit")
  
  This patch is already scheduled for release in these stable kernel
  versions:
  
  linux-5.10.y.txt:5f76445a31b79be85b337cce5f35affb77cc18fc veth: Do not record 
rx queue hint in veth_xmit
  linux-5.15.y.txt:78a19e506bdcd1bfff73523ec99190794e0af39c veth: Do not record 
rx queue hint in veth_xmit
  linux-5.16.y.txt:bf8963ea39ecfd1bddc657a81f1d657b43c950e8 veth: Do not record 
rx queue hint in veth_xmit
  linux-5.4.y.txt:d08a0a88db88462bdf1b2df33ded23269b832afc veth: Do not record 
rx queue hint in veth_xmit
  
+ [Test Plan]
+ 
+ AWS tested
  
  [Where things could go wrong]
  
  Transmit performance could be impacted in other ways.
  
  [Other Info]
  
  SF: #00326544

** Description changed:

  SRU Justification
  
  [Impact]
  
  
https://patchwork.kernel.org/project/netdevbpf/patch/ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.dan...@iogearbox.net/
  
  Performance is impacted when multiple TX queues are enabled.
  
  [Fix]
  commit 710ad98c363a66a0cd8526465426c5c5f8377ee0 ("veth: Do not record rx 
queue hint in veth_xmit")
  
  This patch is already scheduled for release in these stable kernel
  versions:
  
  linux-5.10.y.txt:5f76445a31b79be85b337cce5f35affb77cc18fc veth: Do not record 
rx queue hint in veth_xmit
  linux-5.15.y.txt:78a19e506bdcd1bfff73523ec99190794e0af39c veth: Do not record 
rx queue hint in veth_xmit
  linux-5.16.y.txt:bf8963ea39ecfd1bddc657a81f1d657b43c950e8 veth: Do not record 
rx queue hint in veth_xmit
  linux-5.4.y.txt:d08a0a88db88462bdf1b2df33ded23269b832afc veth: Do not record 
rx queue hint in veth_xmit
  
  [Test Plan]
  
- AWS tested
+ Upstream tested
  
  [Where things could go wrong]
  
  Transmit performance could be impacted in other ways.
  
  [Other Info]
  
  SF: #00326544

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

Title:
  Pod traffic not taking advantage of interfaces with multiple tx queues

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  
https://patchwork.kernel.org/project/netdevbpf/patch/ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.dan...@iogearbox.net/

  Performance is impacted when multiple TX queues are enabled.

  [Fix]
  commit 710ad98c363a66a0cd8526465426c5c5f8377ee0 ("veth: Do not record rx 
queue hint in veth_xmit")

  This patch is already scheduled for release in these stable kernel
  versions:

  linux-5.10.y.txt:5f76445a31b79be85b337cce5f35affb77cc18fc veth: Do not record 
rx queue hint in veth_xmit
  linux-5.15.y.txt:78a19e506bdcd1bfff73523ec99190794e0af39c veth: Do not record 
rx queue hint in veth_xmit
  linux-5.16.y.txt:bf8963ea39ecfd1bddc657a81f1d657b43c950e8 veth: Do not record 
rx queue hint in veth_xmit
  linux-5.4.y.txt:d08a0a88db88462bdf1b2df33ded23269b832afc veth: Do not record 
rx queue hint in veth_xmit

  [Test Plan]

  Upstream tested

  [Where things could go wrong]

  Transmit performance could be impacted in other ways.

  [Other Info]

  SF: #00326544

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


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

[Kernel-packages] [Bug 1958151] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922

[AaronMa]

** Description changed:

  [Impact]
  No driver is loaded for MT7922, and fw is missing too.
  
  [Fix]
  Add basic support of MT7922, and add ID of AMD RZ616/RZ608.
  Enable 160Mhz channel.
  
  [Test]
  Verified on RZ616, it works fine, suspend OK.
  iperf test result looks fine.
+ Bluetooth works fine.
  
  [Where problems could occur]
  It may break MT7921 wifi support which shares mt7921e driver.
  Almost the code is specific for MT7922, checking security fw is based on 
MT7922 fw.
  
  The firmware is already in impish and jammy, only SRU fw for focal.

** Description changed:

  [Impact]
  No driver is loaded for MT7922, and fw is missing too.
  
  [Fix]
  Add basic support of MT7922, and add ID of AMD RZ616/RZ608.
  Enable 160Mhz channel.
  
  [Test]
  Verified on RZ616, it works fine, suspend OK.
  iperf test result looks fine.
  Bluetooth works fine.
  
  [Where problems could occur]
  It may break MT7921 wifi support which shares mt7921e driver.
  Almost the code is specific for MT7922, checking security fw is based on 
MT7922 fw.
- 
- The firmware is already in impish and jammy, only SRU fw for focal.

** No longer affects: linux-firmware (Ubuntu)

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

Title:
  [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux-oem-5.13 source package in Focal:
  New
Status in linux-oem-5.14 source package in Focal:
  New
Status in linux source package in Impish:
  New
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  No driver is loaded for MT7922, and fw is missing too.

  [Fix]
  Add basic support of MT7922, and add ID of AMD RZ616/RZ608.
  Enable 160Mhz channel.

  [Test]
  Verified on RZ616, it works fine, suspend OK.
  iperf test result looks fine.
  Bluetooth works fine.

  [Where problems could occur]
  It may break MT7921 wifi support which shares mt7921e driver.
  Almost the code is specific for MT7922, checking security fw is based on 
MT7922 fw.

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


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

[Kernel-packages] [Bug 1958153] Re: [SRU][F]Add firmware of MT7922

[AaronMa]

** Description changed:

  [Impact]
  No driver is loaded for MT7922, and fw is missing too.
  
  [Fix]
  Add firmware of MT7922 wifi and bluetooth.
  
  [Test]
  Verified on RZ616, it works fine, suspend OK.
  iperf test result looks fine.
  Bluetooth works fine.
  
  [Where problems could occur]
- It may break MT7921 wifi support which shares mt7921e driver.
- Almost the code is specific for MT7922, checking security fw is based on 
MT7922 fw.
+ These firmware is specific for MT7922, it should be low risk.
  
  The firmware is already in impish and jammy, only SRU fw for focal.

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

Title:
  [SRU][F]Add firmware of MT7922

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  [Impact]
  No driver is loaded for MT7922, and fw is missing too.

  [Fix]
  Add firmware of MT7922 wifi and bluetooth.

  [Test]
  Verified on RZ616, it works fine, suspend OK.
  iperf test result looks fine.
  Bluetooth works fine.

  [Where problems could occur]
  These firmware is specific for MT7922, it should be low risk.

  The firmware is already in impish and jammy, only SRU fw for focal.

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


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

[Kernel-packages] [Bug 1958155] [NEW] Pod traffic not taking advantage of interfaces with multiple tx queues

[Tim Gardner]

Public bug reported:

SRU Justification

[Impact]

https://patchwork.kernel.org/project/netdevbpf/patch/ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.dan...@iogearbox.net/

Performance is impacted when multiple TX queues are enabled.

[Fix]
commit 710ad98c363a66a0cd8526465426c5c5f8377ee0 ("veth: Do not record rx queue 
hint in veth_xmit")

This patch is already scheduled for release in these stable kernel
versions:

linux-5.10.y.txt:5f76445a31b79be85b337cce5f35affb77cc18fc veth: Do not record 
rx queue hint in veth_xmit
linux-5.15.y.txt:78a19e506bdcd1bfff73523ec99190794e0af39c veth: Do not record 
rx queue hint in veth_xmit
linux-5.16.y.txt:bf8963ea39ecfd1bddc657a81f1d657b43c950e8 veth: Do not record 
rx queue hint in veth_xmit
linux-5.4.y.txt:d08a0a88db88462bdf1b2df33ded23269b832afc veth: Do not record rx 
queue hint in veth_xmit


[Where things could go wrong]

Transmit performance could be impacted in other ways.

[Other Info]

SF: #00326544

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux (Ubuntu Hirsute)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux (Ubuntu Impish)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux (Ubuntu Impish)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  Pod traffic not taking advantage of interfaces with multiple tx queues

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  
https://patchwork.kernel.org/project/netdevbpf/patch/ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.dan...@iogearbox.net/

  Performance is impacted when multiple TX queues are enabled.

  [Fix]
  commit 710ad98c363a66a0cd8526465426c5c5f8377ee0 ("veth: Do not record rx 
queue hint in veth_xmit")

  This patch is already scheduled for release in these stable kernel
  versions:

  linux-5.10.y.txt:5f76445a31b79be85b337cce5f35affb77cc18fc veth: Do not record 
rx queue hint in veth_xmit
  linux-5.15.y.txt:78a19e506bdcd1bfff73523ec99190794e0af39c veth: Do not record 
rx queue hint in veth_xmit
  linux-5.16.y.txt:bf8963ea39ecfd1bddc657a81f1d657b43c950e8 veth: Do not record 
rx queue hint in veth_xmit
  linux-5.4.y.txt:d08a0a88db88462bdf1b2df33ded23269b832afc veth: Do not record 
rx queue hint in veth_xmit

  
  [Where things could go wrong]

  Transmit performance could be impacted in other ways.

  [Other Info]

  SF: #00326544

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1958153

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

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

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

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

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

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

Title:
  [SRU][F]Add firmware of MT7922

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  [Impact]
  No driver is loaded for MT7922, and fw is missing too.

  [Fix]
  Add firmware of MT7922 wifi and bluetooth.

  [Test]
  Verified on RZ616, it works fine, suspend OK.
  iperf test result looks fine.
  Bluetooth works fine.

  [Where problems could occur]
  It may break MT7921 wifi support which shares mt7921e driver.
  Almost the code is specific for MT7922, checking security fw is based on 
MT7922 fw.

  The firmware is already in impish and jammy, only SRU fw for focal.

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


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

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[You-Sheng Yang]

SRU: https://lists.ubuntu.com/archives/kernel-
team/2022-January/127192.html (jammy)

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

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 0.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.7
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.7:bd12/02/2021:br0.2:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3:
  dmi.product.family: 

[Kernel-packages] [Bug 1958153] [NEW] [SRU][F]Add firmware of MT7922

[AaronMa]

Public bug reported:

[Impact]
No driver is loaded for MT7922, and fw is missing too.

[Fix]
Add firmware of MT7922 wifi and bluetooth.

[Test]
Verified on RZ616, it works fine, suspend OK.
iperf test result looks fine.
Bluetooth works fine.

[Where problems could occur]
It may break MT7921 wifi support which shares mt7921e driver.
Almost the code is specific for MT7922, checking security fw is based on MT7922 
fw.

The firmware is already in impish and jammy, only SRU fw for focal.

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

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

** Also affects: linux (Ubuntu Focal)
   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/1958153

Title:
  [SRU][F]Add firmware of MT7922

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

Bug description:
  [Impact]
  No driver is loaded for MT7922, and fw is missing too.

  [Fix]
  Add firmware of MT7922 wifi and bluetooth.

  [Test]
  Verified on RZ616, it works fine, suspend OK.
  iperf test result looks fine.
  Bluetooth works fine.

  [Where problems could occur]
  It may break MT7921 wifi support which shares mt7921e driver.
  Almost the code is specific for MT7922, checking security fw is based on 
MT7922 fw.

  The firmware is already in impish and jammy, only SRU fw for focal.

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


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

[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390

[jeremyszu]

nvidia-settings for focal

** Patch added: "18-lp1957094-adjust-on-demand-mode-description.focal.patch"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1957094/+attachment/5554942/+files/18-lp1957094-adjust-on-demand-mode-description.focal.patch

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in nvidia-settings source package in Impish:
  New
Status in ubuntu-drivers-common source package in Impish:
  Triaged
Status in nvidia-settings source package in Jammy:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

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


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

[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390

[jeremyszu]

ubuntu-drivers-common for impish

** Patch added: 
"0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.patch"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1957094/+attachment/5554940/+files/0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.patch

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in nvidia-settings source package in Impish:
  New
Status in ubuntu-drivers-common source package in Impish:
  Triaged
Status in nvidia-settings source package in Jammy:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

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


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