[Kernel-packages] [Bug 1970155] Re: System wakes from suspend almost immediately

[prathamesh]

As per your suggestion i unplugged usb keyboard before suspending.
Everytime it works if i unplugged usb keyboard. It looks like this is
something usb keyboard specific issue. Is there any permanent solution
on this or i have to unplugged usb keyboard everytime.

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

Title:
  System wakes from suspend almost immediately

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Suspend mode does not seems to work. Clicking on suspend button sends
  laptop in suspend mode and in few seconds laptop comes out of suspend
  mode and shows login screen again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 10:31:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9]
  InstallationDate: Installed on 2022-04-22 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 34601F4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=be040347-6300-407e-9e19-da58389c3a6f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.release: 2.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34601F4
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:br2.59:efr1.4:svnLENOVO:pn34601F4:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F4:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3460:
  dmi.product.family: ThinkPad X1 Carbon
  dmi.product.name: 34601F4
  dmi.product.sku: LENOVO_MT_3460
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 1970072] Re: [nvidia] Frequent GPU Resets (and GUI Freeze) by gsd-media-keys

[ebsf]

Here's the other file ...

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1970072/+attachment/5584573/+files/prevboot.txt

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

Title:
  [nvidia] Frequent GPU Resets (and GUI Freeze) by gsd-media-keys

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

Bug description:
  A fresh install of Ubuntu 20.04.4 has GUI freezes frequently (i.e., a
  dozen times daily) at inconsistent intervals and times, and not
  obviously in response to any particular user input.  The system then
  is unresponsive to user input, although the mouse cursor does continue
  to move about.

  The syslog messages reveal the message from gsd-media-keys "[GFX1]:
  Device reset due to WR context"

  The freeze also is preceded by often hundreds of pulseaudio messages
  related to latency issues, notwithstanding that no audio is playing.
  Often, gdm-x-session messages appear referencing the NVIDIA GPU and
  "WAIT".  The pulseaudio message "setting avail_min=87496" often is the
  last message and if not, one of the last, before the reboot.

  Also common before is a gnome-shell message "Ignored exception from
  dbus method: Gio.DBusError:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  com.gonzaarcr.appmenu was not provided by any .service files", which
  precedes the pulseaudio messages.

  Happy to provide any other information but would welcome some guidance
  because I'm on day 11 or 12 of this installation and wearing out my
  welcome at Google.

  Ubuntu 20.04.4 LTS

  apt-cache returns:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 3.36.9-0ubuntu0.20.04.2
Version table:
   *** 3.36.9-0ubuntu0.20.04.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Expected behavior:  Stability, especially from the fourth release of a
  LTS.

  Behavior:  Persistent GUI freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 23 16:26:45 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-04-09 (14 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1970072] Re: [nvidia] Frequent GPU Resets (and GUI Freeze) by gsd-media-keys

[ebsf]

Thanks.  I'm glad to learn that the problems could be discerned.

I made the change you suggested  to /etc/default/grub and did <# update-
grub>.

I also removed the Fildem menu GNOME extension, messages about which
preceded every crash.

Attached are the logs from te latest hang, which occurred just now.  The
trigger was nothing but using Firefox and opening windows as I was
scrolling through a feed.

I'll be interested to learn your diagnosis this time, also.

It also would be good to knwo what is causing the Nvidia kernel driver
to fail, so I can get in front of that, if possible.

It also would be good to rule out hardware failure, if possible or, on
the other hand, to find evidence of such.

Thanks again.



** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1970072/+attachment/5584569/+files/lspci.txt

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

Title:
  [nvidia] Frequent GPU Resets (and GUI Freeze) by gsd-media-keys

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

Bug description:
  A fresh install of Ubuntu 20.04.4 has GUI freezes frequently (i.e., a
  dozen times daily) at inconsistent intervals and times, and not
  obviously in response to any particular user input.  The system then
  is unresponsive to user input, although the mouse cursor does continue
  to move about.

  The syslog messages reveal the message from gsd-media-keys "[GFX1]:
  Device reset due to WR context"

  The freeze also is preceded by often hundreds of pulseaudio messages
  related to latency issues, notwithstanding that no audio is playing.
  Often, gdm-x-session messages appear referencing the NVIDIA GPU and
  "WAIT".  The pulseaudio message "setting avail_min=87496" often is the
  last message and if not, one of the last, before the reboot.

  Also common before is a gnome-shell message "Ignored exception from
  dbus method: Gio.DBusError:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  com.gonzaarcr.appmenu was not provided by any .service files", which
  precedes the pulseaudio messages.

  Happy to provide any other information but would welcome some guidance
  because I'm on day 11 or 12 of this installation and wearing out my
  welcome at Google.

  Ubuntu 20.04.4 LTS

  apt-cache returns:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 3.36.9-0ubuntu0.20.04.2
Version table:
   *** 3.36.9-0ubuntu0.20.04.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Expected behavior:  Stability, especially from the fourth release of a
  LTS.

  Behavior:  Persistent GUI freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 23 16:26:45 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-04-09 (14 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1970456] Re: Still no bluetoot on 5.15.0-27

[Amir]

So this is not a bug but a feature? @Tim Gardner

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

Title:
  Still no bluetoot on 5.15.0-27

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  From 22.04 beta, there is no bluetooth on my computers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-27-generic 5.15.0-27.28
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zolal  2817 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 18:38:40 2022
  InstallationDate: Installed on 2021-12-20 (126 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 2189
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-03-25 (31 days ago)
  dmi.bios.date: 09/14/2012
  dmi.bios.release: 0.146
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.ec.firmware.release: 8.146
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:br0.146:efr8.146:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:skuLENOVO_MT_2189:
  dmi.product.family: IDEAPAD
  dmi.product.name: 2189
  dmi.product.sku: LENOVO_MT_2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)

[Moataz]

This workaround is no longer working when upgraded to 22.04. I have
added all the details on ask ubuntu and ubuntu forums:

https://askubuntu.com/questions/1402796/touch-pad-and-touch-screen-are-
not-working-after-upgrading-to-ubuntu-22-04

https://ubuntuforums.org/showthread.php?t=2474206=14092022#post14092022

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

Title:
  touchpad and touchscreen doesn't work at all on ACER Spin 5
  (SP513-54N)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad is not working at all on ACER Spin 5 SP513-54N.

  According to
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
  I am creating this kernel bug issue.

  There are more issues, too, like touchscreen not working and Ubuntu
  not installable - see here if interrested
  https://askubuntu.com/questions/1251719/

  I would like to run Ubuntu on this machine and I am willing to help
  with any debug or kernel tweaking... Please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4195 F pulseaudio
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 10:44:58 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Spin SP513-54N
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.00
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.00
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.00
  dmi.sys.vendor: Acer

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


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

[Kernel-packages] [Bug 1970688] 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/1970688

Title:
  Touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My touchpad is not working. I typed "cat /proc/bus/input/devices |
  grep -i touchpad" on the terminal, and it returned nothing. My
  computer is a Lenovo IdeaPad S145.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-27-generic 5.15.0-27.28
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mpds   1301 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 23:39:54 2022
  InstallationDate: Installed on 2022-04-28 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera
   Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 046d:c542 Logitech, Inc. Wireless Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 82DJ
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=3eaea9a9-683e-4c1c-af95-b4d918236d1a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2021
  dmi.bios.release: 1.53
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN53WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IIL
  dmi.ec.firmware.release: 1.53
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN53WW:bd05/31/2021:br1.53:efr1.53:svnLENOVO:pn82DJ:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL:skuLENOVO_MT_82DJ_BU_idea_FM_IdeaPadS145-15IIL:
  dmi.product.family: IdeaPad S145-15IIL
  dmi.product.name: 82DJ
  dmi.product.sku: LENOVO_MT_82DJ_BU_idea_FM_IdeaPad S145-15IIL
  dmi.product.version: Lenovo IdeaPad S145-15IIL
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1970456] Re: Still no bluetoot on 5.15.0-27

[Kai-Heng Feng]

ar3k firmware is somehow removed, not sure the reason:
commit 85ee46eb913671b41591cf6ff4bb5eb09d5d2f5f
Author: Tim Gardner 
Date:   Thu Apr 12 14:43:57 2012 -0600

UBUNTU: Remove obsolete ar3k firmware

Signed-off-by: Tim Gardner 


** Package changed: linux (Ubuntu) => linux-firmware (Ubuntu)

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

Title:
  Still no bluetoot on 5.15.0-27

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  From 22.04 beta, there is no bluetooth on my computers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-27-generic 5.15.0-27.28
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zolal  2817 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 18:38:40 2022
  InstallationDate: Installed on 2021-12-20 (126 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 2189
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-03-25 (31 days ago)
  dmi.bios.date: 09/14/2012
  dmi.bios.release: 0.146
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.ec.firmware.release: 8.146
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:br0.146:efr8.146:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:skuLENOVO_MT_2189:
  dmi.product.family: IDEAPAD
  dmi.product.name: 2189
  dmi.product.sku: LENOVO_MT_2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1970456] Re: Still no bluetoot on 5.15.0-27

[Kai-Heng Feng]

[   23.846974] usb 1-1.3: Direct firmware load for ar3k/AthrBT_0x01020200.dfu 
failed with error -2
[   23.846980] Bluetooth: Patch file not found ar3k/AthrBT_0x01020200.dfu
[   23.846983] Bluetooth: Loading patch file failed

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

Title:
  Still no bluetoot on 5.15.0-27

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  From 22.04 beta, there is no bluetooth on my computers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-27-generic 5.15.0-27.28
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zolal  2817 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 18:38:40 2022
  InstallationDate: Installed on 2021-12-20 (126 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 2189
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-03-25 (31 days ago)
  dmi.bios.date: 09/14/2012
  dmi.bios.release: 0.146
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.ec.firmware.release: 8.146
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:br0.146:efr8.146:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:skuLENOVO_MT_2189:
  dmi.product.family: IDEAPAD
  dmi.product.name: 2189
  dmi.product.sku: LENOVO_MT_2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1970453] Re: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set

[Kai-Heng Feng]

Please give mainline kernel a try:
https://wiki.ubuntu.com/Kernel/MainlineBuilds

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

Title:
  DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 22.04 with kernel 5.15.0.27.30 on an HPE ProLiant
  DL20 Gen9 server. The server has an HPE Smart HBA H240 SATA
  controller.

  Since Ubuntu 22.04, the kernel runs into trouble after a few hours of
  uptime. The problem starts with a few instances of a message such as
  this:

  Apr 26 12:03:37  kernel: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 
already set (to 7bf32003 not 24c563801)
  Apr 26 12:03:37  kernel: [ cut here ]
  Apr 26 12:03:37  kernel: WARNING: CPU: 1 PID: 10171 at 
drivers/iommu/intel/iommu.c:2391 __domain_mapping.cold+0x94/0xcb
  Apr 26 12:03:37  kernel: Modules linked in: tls rpcsec_gss_krb5 
binfmt_misc ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT 
nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limi>
  Apr 26 12:03:37  kernel:  drm_kms_helper aesni_intel syscopyarea 
sysfillrect sysimgblt fb_sys_fops xhci_pci cec crypto_simd i2c_i801 rc_core 
cryptd drm xhci_pci_renesas ahci i2c_smbus tg3 hpsa>
  Apr 26 12:03:37  kernel: CPU: 1 PID: 10171 Comm: kworker/u4:0 Not 
tainted 5.15.0-27-generic #28-Ubuntu
  Apr 26 12:03:37  kernel: Hardware name: HP ProLiant DL20 
Gen9/ProLiant DL20 Gen9, BIOS U22 04/01/2021
  Apr 26 12:03:37  kernel: Workqueue: writeback wb_workfn 
(flush-253:2)
  Apr 26 12:03:37  kernel: RIP: 0010:__domain_mapping.cold+0x94/0xcb
  Apr 26 12:03:37  kernel: Code: 27 9d 4c 89 4d b8 4c 89 45 c0 e8 03 
c5 fa ff 8b 05 e7 e6 40 01 4c 8b 45 c0 4c 8b 4d b8 85 c0 74 09 83 e8 01 89 05 
d2 e6 40 01 <0f> 0b e9 7e b2 b1 ff 89 ca 48 83 >
  Apr 26 12:03:37  kernel: RSP: 0018:c077826b2fa0 EFLAGS: 00010202
  Apr 26 12:03:37  kernel: RAX: 0004 RBX: 
9f0042062990 RCX: 
  Apr 26 12:03:37  kernel: RDX:  RSI: 
9f02b3d20980 RDI: 9f02b3d20980
  Apr 26 12:03:37  kernel: RBP: c077826b2ff0 R08: 
00024c563801 R09: 0024c563
  Apr 26 12:03:37  kernel: R10:  R11: 
c01550e0 R12: 000f
  Apr 26 12:03:37  kernel: R13: 0007bf32 R14: 
9f00412f5800 R15: 9f0042062938
  Apr 26 12:03:37  kernel: FS:  () 
GS:9f02b3d0() knlGS:
  Apr 26 12:03:37  kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 26 12:03:37  kernel: CR2: 1530f676a01c CR3: 
00029c210001 CR4: 002706e0
  Apr 26 12:03:37  kernel: Call Trace:
  Apr 26 12:03:37  kernel:  
  Apr 26 12:03:37  kernel:  intel_iommu_map_pages+0xdc/0x120
  Apr 26 12:03:37  kernel:  ? 
__alloc_and_insert_iova_range+0x203/0x240
  Apr 26 12:03:37  kernel:  __iommu_map+0xda/0x270
  Apr 26 12:03:37  kernel:  __iommu_map_sg+0x8e/0x120
  Apr 26 12:03:37  kernel:  iommu_map_sg_atomic+0x14/0x20
  Apr 26 12:03:37  kernel:  iommu_dma_map_sg+0x345/0x4d0
  Apr 26 12:03:37  kernel:  __dma_map_sg_attrs+0x68/0x70
  Apr 26 12:03:37  kernel:  dma_map_sg_attrs+0xe/0x20
  Apr 26 12:03:37  kernel:  scsi_dma_map+0x39/0x50
  Apr 26 12:03:37  kernel:  
hpsa_scsi_ioaccel2_queue_command.constprop.0+0x11e/0x570 [hpsa]
  Apr 26 12:03:37  kernel:  ? __blk_rq_map_sg+0x36/0x160
  Apr 26 12:03:37  kernel:  hpsa_scsi_ioaccel_queue_command+0x82/0xd0 
[hpsa]
  Apr 26 12:03:37  kernel:  hpsa_ioaccel_submit+0x174/0x190 [hpsa]
  Apr 26 12:03:37  kernel:  hpsa_scsi_queue_command+0x19c/0x240 [hpsa]
  Apr 26 12:03:37  kernel:  ? recalibrate_cpu_khz+0x10/0x10
  Apr 26 12:03:37  kernel:  scsi_dispatch_cmd+0x93/0x1f0
  Apr 26 12:03:37  kernel:  scsi_queue_rq+0x2d1/0x690
  Apr 26 12:03:37  kernel:  blk_mq_dispatch_rq_list+0x126/0x600
  Apr 26 12:03:37  kernel:  ? __sbitmap_queue_get+0x1/0x10
  Apr 26 12:03:37  kernel:  __blk_mq_do_dispatch_sched+0xba/0x2d0
  Apr 26 12:03:37  kernel:  
__blk_mq_sched_dispatch_requests+0x104/0x150
  Apr 26 12:03:37  kernel:  blk_mq_sched_dispatch_requests+0x35/0x60
  Apr 26 12:03:37  kernel:  __blk_mq_run_hw_queue+0x34/0xb0
  Apr 26 12:03:37  kernel:  __blk_mq_delay_run_hw_queue+0x162/0x170
  Apr 26 12:03:37  kernel:  blk_mq_run_hw_queue+0x83/0x120
  Apr 26 12:03:37  kernel:  blk_mq_sched_insert_requests+0x69/0xf0
  Apr 26 12:03:37  kernel:  blk_mq_flush_plug_list+0x103/0x1c0
  Apr 26 12:03:37  kernel:  blk_flush_plug_list+0xdd/0x100
  Apr 26 12:03:37  kernel:  blk_mq_submit_bio+0x2bd/0x600
  Apr 26 12:03:37  kernel:  __submit_bio+0x1ea/0x220
  Apr 26 12:03:37  kernel:  ? mempool_alloc_slab+0x17/0x20
  Apr 26 12:03:37  kernel:  __submit_bio_noacct+0x85/0x1f0
  Apr 26 12:03:37  kernel:  submit_bio_noacct+0x4e/0x120
  Apr 26 12:03:37  kernel:  ? radix_tree_lookup+0xd/0x10
  Apr 26 12:03:37  kernel:  ? bio_associate_blkg_from_css+0x1b2/0x310
  Apr 26 12:03:37  kernel: 

[Kernel-packages] [Bug 1970688] [NEW] Touchpad not working

[Matheus Müller]

Public bug reported:

My touchpad is not working. I typed "cat /proc/bus/input/devices | grep
-i touchpad" on the terminal, and it returned nothing. My computer is a
Lenovo IdeaPad S145.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-27-generic 5.15.0-27.28
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mpds   1301 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 23:39:54 2022
InstallationDate: Installed on 2022-04-28 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera
 Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications 
 Bus 001 Device 002: ID 046d:c542 Logitech, Inc. Wireless Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 82DJ
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=3eaea9a9-683e-4c1c-af95-b4d918236d1a ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-27-generic N/A
 linux-backports-modules-5.15.0-27-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2021
dmi.bios.release: 1.53
dmi.bios.vendor: LENOVO
dmi.bios.version: DKCN53WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S145-15IIL
dmi.ec.firmware.release: 1.53
dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN53WW:bd05/31/2021:br1.53:efr1.53:svnLENOVO:pn82DJ:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL:skuLENOVO_MT_82DJ_BU_idea_FM_IdeaPadS145-15IIL:
dmi.product.family: IdeaPad S145-15IIL
dmi.product.name: 82DJ
dmi.product.sku: LENOVO_MT_82DJ_BU_idea_FM_IdeaPad S145-15IIL
dmi.product.version: Lenovo IdeaPad S145-15IIL
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Touchpad not working

Status in linux package in Ubuntu:
  New

Bug description:
  My touchpad is not working. I typed "cat /proc/bus/input/devices |
  grep -i touchpad" on the terminal, and it returned nothing. My
  computer is a Lenovo IdeaPad S145.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-27-generic 5.15.0-27.28
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mpds   1301 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 23:39:54 2022
  InstallationDate: Installed on 2022-04-28 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera
   Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 046d:c542 Logitech, Inc. Wireless Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 82DJ
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=3eaea9a9-683e-4c1c-af95-b4d918236d1a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2021
  dmi.bios.release: 1.53
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN53WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IIL
  dmi.ec.firmware.release: 1.53
  dmi.modalias: 

[Kernel-packages] [Bug 1959345] Re: vulkaninfo reports error

[Kai-Heng Feng]

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

** Changed in: mesa (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/1959345

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  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/mesa/+bug/1959345/+subscriptions


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

[Kernel-packages] [Bug 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04

[Kai-Heng Feng]

Have you tried the patch mentioned in the description?

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

Title:
  [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal
  (black screen) when install  Ubuntu 22.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:
  When we install Ubuntu 22.04, the physical VGA displayer show black screen.  
It can only show rarely boot logs just for few seconds after kebyboard Enter 
key be pressed to install Ubuntu OS, and then the physical VGA displayer keeps 
black screen, but the XCC remote KVM monitor can show the boot log and the GUI 
interface.

  Produce Steps:
1. Connect  a physical VGA displayer.
2. Fresh install Ubuntu22.04 on a server that integrated Matrox MGA 
G200-family.
3. When the install menu comes out, press keyboard Enter key, the 
physical VGA displayer just get the signal for few seconds and then the monitor 
go to black screen.

  Configuration:
  Systems：Lenovo SR590, SR650, SR630 with magag200 as GFX
  OS:jammy-live-server20220405-amd64.iso
  CPU:Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz
  UEFI:3.30 (Build ID: IVE178D)
  XCC:1.30 (Build ID: PDL114N)
  HDD:1.00TB 7.2K 6Gbps SATA 3.5" HD

  Actual results:
  The VGA display keep the black screen, during Ubuntu 22.04 installation.

  Expected results:
  The VGA display is OK when install the Ubuntu 22.04 in a server that 
integrated Matrox MGA G200-family video processor

  
  Additional info:
1. The issue can be reproduced 100% in the server that integrated 
Matrox MGA G200-family platforms.
2. Both UEFI mode and legacy mode are failed.
3. After we finish installing Ubuntu OS through XCC remote KVM monitor, 
 and reboot the system,  the physical VGA displayer still show nothing after a 
few seconds.
4. We did more tests, modified the cmdline of the kernel, add 
"nomodeset", the VGA displayer display well.
5. This issue could be found on both  Intel and AMD platforms , which 
have onboard video chip as mgag200, also called pilot 4. 
6. Upstream kernel patch 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1=147696720eca12ae48d020726208b9a61cdd80bc
 (drm/mgag200: Select clock in PLL update functions) probalby resovle the issue 
on BIOS legacy mode.

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


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

[Kernel-packages] [Bug 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

[Daniel van Vugt]

Fractional scaling certainly changes the display layout logic so it's a
plausible if surprising workaround.

I would only ask anyone reading this to please verify you're not seeing
any files left in /var/crash when the bug occurs.

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+subscriptions


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

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

[Daniel van Vugt]

When you first boot the live USB you should probably choose "Ubuntu
(safe graphics)" instead of "Try or Install Ubuntu". Despite sounding
different they are the same thing with the only difference being that
troublesome graphics drivers are disabled in safe graphics mode.

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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


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

[Kernel-packages] [Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

[Daniel van Vugt]

Ubuntu has already released a solution, it's only a more performant
solution that requires changes from NVIDIA. They are aware of the issue
as I've seen it on their list of missing features in Wayland sessions.

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

Title:
  Wayland sessions can't use external monitors that are connected to an
  Nvidia GPU with the proprietary driver

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed

Bug description:
  When an external display is connected to my laptop, running Ubuntu
  22.04, the display is detected and I am sent to the login screen.
  After logging in again, the display is not running, although the
  primary laptop display works fine. The external monitor is looking for
  connection in that moment, which it never founds.

  The bug is tested on two Samsung monitors: S24R350FHUXEN and
  S22F350FHU.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  495.46  Wed Oct 27 16:31:33 
UTC 2021
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1)
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  3 13:25:04 2022
  DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/495.46, 5.15.0-17-generic, x86_64: installed
   nvidia/495.46, 5.15.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f]
  InstallationDate: Installed on 2021-09-09 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. G3 3579
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.109-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-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/mutter/+bug/1959888/+subscriptions


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

[Kernel-packages] [Bug 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS

[DeathByDenim]

Ok, I figured out kernel compiling. And many git bisects later, I think
I found the commit causing the issue. It's commit
4eb4bb735a536d922fc92de347b90ea290067c71 that causes my WiFi to become
unstable. If I go one commit earlier
(ef8f38d37265d79607e1fc132e28fadec8f51056) it all works perfectly, using
that right now.

The commit causing breakage is a pretty short patch, but I don't really 
understand what it does:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-next=4eb4bb735a536d922fc92de347b90ea290067c71

I hope this helps at least!

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

Title:
  Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using the current beta of Jammy, I no longer have stable WiFi after
  April 5, 2022 update of wpasupplicant from 2:2.10-2 to 2:2.10-6. There
  is a chance it may also be related to network-manager going from
  1.36.4-1ubuntu1 to 1.36.4-2ubuntu1, but the logs seems to point to
  wpasupplicant (see below)

  Wifi is stable often, but also often it fails to load webpages
  intermittently or fails to download the packages using apt for
  example, so it's not browser related.

  Example output of journalctl -xe -u wpasupplicant:
  Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - 
Connection to fc:34:97:23:4c:3c completed [id=0 id_str=]
  Apr 08 19:26:28 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-72 noise=-95 txrate=7200
  Apr 08 19:26:32 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:33 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:34 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:35 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:36 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:37 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:38 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-BEACON-LOSS
  Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-DISCONNECTED 
bssid=fc:34:97:23:4c:3c reason=4 locally_generated=1
  Apr 08 19:26:39 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
  Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
  Apr 08 19:26:40 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
  Apr 08 19:26:42 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: SME: Trying to 
authenticate with fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz)
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Trying to associate with 
fc:34:97:23:4c:3c (SSID='CamplingVanDerKolk5G' freq=5260 MHz)
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: Associated with 
fc:34:97:23:4c:3c
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-REGDOM-CHANGE 
init=COUNTRY_IE type=COUNTRY alpha2=CA
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: WPA: Key negotiation 
completed with fc:34:97:23:4c:3c [PTK=CCMP GTK=CCMP]
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-CONNECTED - 
Connection to fc:34:97:23:4c:3c completed [id=0 id_str=]
  Apr 08 19:26:43 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-72 noise=-95 txrate=7200
  Apr 08 19:29:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=1 signal=-66 noise=-94 txrate=27
  Apr 08 19:49:04 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-73 noise=-95 txrate=27
  Apr 08 19:59:04 weasel wpa_supplicant[772]: wlp13s0: WPA: Group rekeying 
completed with fc:34:97:23:4c:3c [GTK=CCMP]
  Apr 08 20:00:23 weasel wpa_supplicant[772]: wlp13s0: CTRL-EVENT-SIGNAL-CHANGE 
above=1 signal=-66 noise=-95 txrate=243000

  
  Additional info:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy wpasupplicant 
  wpasupplicant:
Geïnstalleerd: 2:2.10-6
Kandidaat: 2:2.10-6
Versietabel:
   *** 2:2.10-6 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-oracle/4.15.0-1093.102)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-oracle 
(4.15.0-1093.102) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.147-0ubuntu0.18.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-restricted-modules-oracle

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic

[Launchpad Bug Tracker]

This bug was fixed in the package firmware-sof - 2.0-1ubuntu3

---
firmware-sof (2.0-1ubuntu3) jammy; urgency=low

  * Add a new tplg file to v2.0.x
- Intel released a new tplg file in the sof-bin-v1.9.3-tplg2 for a
  Dell machine which has no internal mic. Now picking that file and
  put it as v2.0.x/sof-tplg-v2.0/sof-adl-rt711-l2-rt1316-l01.tplg.
  (LP: #1966841)

 -- Hui Wang   Wed, 13 Apr 2022 11:30:46 +0800

** Changed in: firmware-sof (Ubuntu)
   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/1966841

Title:
  alsa/sdw: Fix the audio issue on a Dell machine without internal mic

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

Bug description:
  SRU template for linux-firmware
  [Impact]
  we have a Dell ADL laptop which has sdw audio, but there is no camera
  and no internal digital mic in this machine, the current asoc driver
  can't work on this machine, the speaker and headset couldn't work.

  [Fix]
  Backport a tplg file which is specific to this mahcine

  [Test]
  Install the patched linux-firmware and boot the latest oem-5.14 kernel
  on the machine, check dmesg, it loads the correct tplg, and
  test speaker and headset, all work well.

  [Where problems could occur]
  This SRU is adding a new tplg file, it has no chance to introduce
  a regression.

  SRU template for linux
  [Impact]
  we have a Dell ADL laptop which has sdw audio, but there is no camera
  and no internal digital mic in this machine, the current soc driver
  can't work on this machine, it will load a wrong tplg without this patch,
  and the speaker and headset couldn't work.

  [Fix]
  Backport one patch from upstream.

  [Test]
  Boot the patched kernel on the machine, check dmesg, it loads the
  correct tplg, and test speaker and headset, all work well.

  [Where problems could occur]
  If it could introduce regression, it will be on the sdw codec matching
  for adl machines, then it will make the driver load wrong tplg and make
  output device and input device not work anymore. But this possibility
  is very low, we already tested the patch on some dell adl machines, no
  regression found.

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


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

[Kernel-packages] [Bug 1967579] Re: harden indirect calls against BHI attacks

[Launchpad Bug Tracker]

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

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

  * jammy/linux: 5.15.0-27.28 -proposed tracker (LP: #1968954)

 -- Paolo Pisati   Thu, 14 Apr 2022 06:46:57
+0200

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

Title:
  harden indirect calls against BHI attacks

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

Bug description:
  [Impact]
  Branch History Injection is made easier when all indirect calls are funneled 
through very few points where the retpolines were. By replacing the retpoline 
jumps by indirect calls whenever retpolines are disabled, BHI attacks are more 
difficult to execute as the BTB is not as fixed as before.

  [Fixes]
  Though there are fixes that allow retpoline,lfence to be directly replaced in 
the indirect calls, given that mitigation is not recommended for most of the 
situations, that hardening is not as important as the one that works for the 
spectre_v2=off option (the default one for systems with eIBRS). This latter one 
is present starting with 5.13, but backporting to 5.4 might be a good measure.

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


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

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

[Kellen Renshaw]

** Summary changed:

- makedumpfile fails with __vtop4_x86_64: Can't get a valid pmd_pte.
+ makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid 
pmd_pte."

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

Title:
  makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
  pmd_pte."

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  [Impact] 
   * On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with 
"__vtop4_x86_64: Can't get a valid pmd_pte."

   * makedumpfile falls back to cp for the dump, resulting in extremely
  large vmcores. This can impact both collection and analysis due to
  lack of space for the resulting vmcore.

   * This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
  
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

  commit 646456862df8926ba10dd7330abf3bf0f887e1b6
  Author: Kazuhito Hagio 
  Date:   Wed May 26 14:31:26 2021 +0900

  [PATCH] Increase SECTION_MAP_LAST_BIT to 5
  
  * Required for kernel 5.12
  
  Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
  ZONE_DEVICE section collisions") added a section flag
  (SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
  some machines like this:
  
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical 
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
  
  Increase SECTION_MAP_LAST_BIT to 5 to fix this.  The bit had not
  been used until the change, so we can just increase the value.
  
  Signed-off-by: Kazuhito Hagio 

  [Test Plan]
   * Confirm that makedumpfile works as expected by triggering a kdump.

   * Confirm that the patched makedumpfile works as expected on a system
  known to experience the issue.

   * Confirm that the patched makedumpfile is able to work with a cp-
  generated known affected vmcore to compress it. The unpatched version
  fails.

  [Where problems could occur]

   * This change could adversely affect the collection/compression of
  vmcores during a kdump situation resulting in fallback to cp.

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


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

[Kernel-packages] [Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel

[rustyx]

Had the same issue with Ubuntu 22.04 install ISO flashed onto a USB.

Even tried booting "manually" (press "c" to enter GRUB command prompt)

grub> ls
(proc) (hd0) (hd0,gpt1) (hd0,gpt2) (hd0,gpt3) (hd1) . . .
grub> ls (hd0,gpt1)
Partition hd0,gpt1: Filesystem type ... - Label 'UBUNTU 22_0' ...
grub> set root=(hd0,gpt1)
grub> linux /casper/vmlinuz
grub> initrd /casper/initrd
error: out of memory.
grub>

Couldn't find any way out of this condition (is there?).

Fortunately I already had GRUB installed on the machine so I could
proceed from that one.

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

Title:
  Out of Memory on boot with 5.2.0 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d".
  Can still boot using the previous 5.0.0-25-generic kernel, but the
  5.2.0-15-generic fails to start.

  On selecting Ubuntu from Grub, the message "error: out of memory." is
  immediately shown. Pressing a key attempts to start boot-up but fails
  to mount root fs.

  Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free
  shows the following (run from Gnome terminal):

    totalusedfree  shared  buff/cache   
available
  Mem:7906564 1761196 3833240 1020216 2312128 
4849224
  Swap:   1003516   0 1003516

  Kernel packages installed:

  linux-generic  5.2.0.15.16 amd64
  linux-headers-5.2.0-15 5.2.0-15.16 all
  linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64
  linux-headers-generic  5.2.0.15.16 amd64
  linux-image-5.0.0-25-generic   5.0.0-25.26 amd64
  linux-image-5.2.0-15-generic   5.2.0-15.16+signed1 amd64
  linux-image-generic5.2.0.15.16 amd64
  linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64
  linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64
  linux-modules-extra-5.0.0-25-generic   5.0.0-25.26 amd64
  linux-modules-extra-5.2.0-15-generic   5.2.0-15.16 amd64

  Photo of kernel panic attached.

  NVMe drive partition layout (GPT):

  Device   StartEnd   Sectors   Size Type
  /dev/nvme0n1p120481050623   1048576   512M EFI System
  /dev/nvme0n1p2 10506242549759   1499136   732M Linux filesystem
  /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem

  $ sudo pvs
    PV  VGFmt  Attr PSizePFree
    /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a--  <475.71g0

  $ sudo lvs
    LV VGAttr   LSize   Pool Origin Data%  Meta%  Move Log 
Cpy%Sync Convert
    root   ubuntu-vg -wi-ao 474.75g
    swap_1 ubuntu-vg -wi-ao 980.00m

  Partition 3 is LUKS encrypted. Root LV is ext4.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gmckeown   1647 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-15 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision 
FHD Camera
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-25-generic N/A
   linux-backports-modules-5.0.0-25-generic  N/A
   linux-firmware1.181
  Tags:  eoan
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.25:bd05/17/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2QH38EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1970672] [NEW] makedumpfile fails with __vtop4_x86_64: Can't get a valid pmd_pte.

[Kellen Renshaw]

Public bug reported:

[Impact] 
 * On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with 
"__vtop4_x86_64: Can't get a valid pmd_pte."

 * makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to lack
of space for the resulting vmcore.

 * This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio 
Date:   Wed May 26 14:31:26 2021 +0900

[PATCH] Increase SECTION_MAP_LAST_BIT to 5

* Required for kernel 5.12

Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
ZONE_DEVICE section collisions") added a section flag
(SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
some machines like this:

  __vtop4_x86_64: Can't get a valid pmd_pte.
  readmem: Can't convert a virtual address(e2bdc200) to physical 
address.
  readmem: type_addr: 0, addr:e2bdc200, size:32768
  __exclude_unnecessary_pages: Can't read the buffer of struct page.
  create_2nd_bitmap: Can't exclude unnecessary pages.

Increase SECTION_MAP_LAST_BIT to 5 to fix this.  The bit had not
been used until the change, so we can just increase the value.

Signed-off-by: Kazuhito Hagio 

[Test Plan]
 * Confirm that makedumpfile works as expected by triggering a kdump.

 * Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.

 * Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.

[Where problems could occur]

 * This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.

** Affects: makedumpfile (Ubuntu)
 Importance: Undecided
 Assignee: Kellen Renshaw (krenshaw)
 Status: New


** Tags: sts

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Kellen Renshaw (krenshaw)

** Tags added: sts

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

Title:
  makedumpfile fails with __vtop4_x86_64: Can't get a valid pmd_pte.

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  [Impact] 
   * On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with 
"__vtop4_x86_64: Can't get a valid pmd_pte."

   * makedumpfile falls back to cp for the dump, resulting in extremely
  large vmcores. This can impact both collection and analysis due to
  lack of space for the resulting vmcore.

   * This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
  
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

  commit 646456862df8926ba10dd7330abf3bf0f887e1b6
  Author: Kazuhito Hagio 
  Date:   Wed May 26 14:31:26 2021 +0900

  [PATCH] Increase SECTION_MAP_LAST_BIT to 5
  
  * Required for kernel 5.12
  
  Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
  ZONE_DEVICE section collisions") added a section flag
  (SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
  some machines like this:
  
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical 
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
  
  Increase SECTION_MAP_LAST_BIT to 5 to fix this.  The bit had not
  been used until the change, so we can just increase the value.
  
  Signed-off-by: Kazuhito Hagio 

  [Test Plan]
   * Confirm that makedumpfile works as expected by triggering a kdump.

   * Confirm that the patched makedumpfile works as expected on a system
  known to experience the issue.

   * Confirm that the patched makedumpfile is able to work with a cp-
  generated known affected vmcore to compress it. The unpatched version
  fails.

  [Where problems could occur]

   * This change could adversely affect the collection/compression of
  vmcores during a kdump situation resulting in fallback to cp.

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


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

[Kernel-packages] [Bug 1970670] [NEW] package nvidia-driver-510 510.60.02-0ubuntu0.20.04.2 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Andres Felipe Puello Gomez]

Public bug reported:

idk, when i started the computer this was the rror

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-driver-510 510.60.02-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.23
AptOrdering:
 linux-signatures-nvidia-5.13.0-30-generic:amd64: Remove
 linux-modules-extra-5.13.0-30-generic:amd64: Remove
 linux-image-5.13.0-30-generic:amd64: Remove
 linux-modules-5.13.0-30-generic:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Apr 19 09:39:51 2022
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2022-04-04 (23 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: nvidia-graphics-drivers-510
Title: package nvidia-driver-510 510.60.02-0ubuntu0.20.04.2 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check third-party-packages

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

Title:
  package nvidia-driver-510 510.60.02-0ubuntu0.20.04.2 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

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

Bug description:
  idk, when i started the computer this was the rror

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-driver-510 510.60.02-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.23
  AptOrdering:
   linux-signatures-nvidia-5.13.0-30-generic:amd64: Remove
   linux-modules-extra-5.13.0-30-generic:amd64: Remove
   linux-image-5.13.0-30-generic:amd64: Remove
   linux-modules-5.13.0-30-generic:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 19 09:39:51 2022
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2022-04-04 (23 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-510
  Title: package nvidia-driver-510 510.60.02-0ubuntu0.20.04.2 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1970668] 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/1970668

Title:
  missing wifi network after update to 22.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
  which I've been using for years on my machine without a problem.  I
  just updated to Jammy and I no longer see my wifi network (all my
  other computer are using it).  It was the network that I used to
  download the update (updated from 20.04).

  I do see a ton of networks, however, using wavemon or nmcli, and can
  use my phone hotspot without a problem.

  I haven't found any alarming entries in /var/log/syslog.

  Please let me know if I can help debug this.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-27-generic 5.15.0-27.28
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kodi   2145 F pulseaudio
   /dev/snd/controlC0:  kodi   2145 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 22:30:35 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2015-09-30 (2400 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUS All Series
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=77249377-1b29-42a0-a36a-8615f4e9a27a ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-26 (0 days ago)
  WifiSyslog:
   
  dmi.bios.date: 03/04/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2404
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2404:bd03/04/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 1970668] [NEW] missing wifi network after update to 22.04

[Krister Swenson]

Public bug reported:

I have a Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01) which
I've been using for years on my machine without a problem.  I just
updated to Jammy and I no longer see my wifi network (all my other
computer are using it).  It was the network that I used to download the
update (updated from 20.04).

I do see a ton of networks, however, using wavemon or nmcli, and can use
my phone hotspot without a problem.

I haven't found any alarming entries in /var/log/syslog.

Please let me know if I can help debug this.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-27-generic 5.15.0-27.28
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  kodi   2145 F pulseaudio
 /dev/snd/controlC0:  kodi   2145 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 22:30:35 2022
HibernationDevice: RESUME=none
InstallationDate: Installed on 2015-09-30 (2400 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: ASUS All Series
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=77249377-1b29-42a0-a36a-8615f4e9a27a ro noprompt persistent quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-27-generic N/A
 linux-backports-modules-5.15.0-27-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-04-26 (0 days ago)
WifiSyslog:
 
dmi.bios.date: 03/04/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2404
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H97M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2404:bd03/04/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  missing wifi network after update to 22.04

Status in linux package in Ubuntu:
  New

Bug description:
  I have a Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
  which I've been using for years on my machine without a problem.  I
  just updated to Jammy and I no longer see my wifi network (all my
  other computer are using it).  It was the network that I used to
  download the update (updated from 20.04).

  I do see a ton of networks, however, using wavemon or nmcli, and can
  use my phone hotspot without a problem.

  I haven't found any alarming entries in /var/log/syslog.

  Please let me know if I can help debug this.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-27-generic 5.15.0-27.28
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kodi   2145 F pulseaudio
   /dev/snd/controlC0:  kodi   2145 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 22:30:35 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2015-09-30 (2400 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUS All Series
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=77249377-1b29-42a0-a36a-8615f4e9a27a ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-26 (0 days ago)
  WifiSyslog:
   
  dmi.bios.date: 03/04/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2404
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 

[Kernel-packages] [Bug 1929894] Re: [TGL][EHL][ADL] Enable MEI (Intel Management Engine Interface)

[Philip Cox]

@Sachin, Both the  CONFIG_INTEL_MEI_DAL and CONFIG_INTEL_MEI_VIRTIO code
paths have build breakages currently.

I have not looked in to these failures too much yet, but the virtio one
looks like missing function prototypes, or actually missing functions.
This may be a patch is that is missing, or something has moved/renamed.

The MEI_DAL one looks like the function pointer return type changed from
"int" to "void".

Looking at dal_remove(), I suspect changing the return type from int to
void would be safe, but there I haven't found an upstream version of
this code to compare with.

With: CONFIG_INTEL_MEI_VIRTIO=m


/build/focal/drivers/misc/mei/hw-virtio.c: In function 'mei_virtio_intr_enable':
/build/focal/drivers/misc/mei/hw-virtio.c:178:2: error: implicit declaration of 
function 'virtio_config_enable'; did you mean 'virtio_config_changed'? 
[-Werror=implicit-function-declaration]
  178 |  virtio_config_enable(vdev);
  |  ^~~~

/build/focal/drivers/misc/mei/hw-virtio.c: In function 
'mei_virtio_intr_disable':
/build/focal/drivers/misc/mei/hw-virtio.c:194:2: error: implicit declaration of 
function 'virtio_config_disable'; did you mean 'virtio_config_changed'? 
[-Werror=implicit-function-declaration]
  194 |  virtio_config_disable(vdev);
  |  ^
  |  virtio_config_changed


With CONFIG_INTEL_MEI_DAL=m

/build/focal/drivers/misc/mei/dal/dal_class.c:800:12: error: initialization of 
'void (*)(struct mei_cl_device *)' from incompatible pointer type 'int 
(*)(struct mei_cl_device *)' [-Werror=incompatible-pointer-types]
  800 |  .remove = dal_remove,
  |^~
/build/focal/drivers/misc/mei/dal/dal_class.c:800:12: note: (near 
initialization for 'dal_driver.remove')

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

Title:
  [TGL][EHL][ADL] Enable MEI (Intel Management Engine Interface)

Status in intel:
  New
Status in intel lookout-canyon series:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-intel package in Ubuntu:
  Won't Fix
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Incomplete
Status in linux-intel source package in Focal:
  Won't Fix
Status in linux-intel-5.13 source package in Focal:
  Fix Released

Bug description:
  Description
  Enable MEI (Intel Management Engine Interface)
  Host communicates with secured apps in firmware with this interface

  Hardware: Tiger Lake/Elkhart Lake/Alder Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

  X-HWE-Bug: Bug #1945464

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


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

[Kernel-packages] [Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

[gutopardini]

Is there any way to charge NVIDIA for a solution?

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

Title:
  Wayland sessions can't use external monitors that are connected to an
  Nvidia GPU with the proprietary driver

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed

Bug description:
  When an external display is connected to my laptop, running Ubuntu
  22.04, the display is detected and I am sent to the login screen.
  After logging in again, the display is not running, although the
  primary laptop display works fine. The external monitor is looking for
  connection in that moment, which it never founds.

  The bug is tested on two Samsung monitors: S24R350FHUXEN and
  S22F350FHU.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  495.46  Wed Oct 27 16:31:33 
UTC 2021
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1)
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  3 13:25:04 2022
  DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/495.46, 5.15.0-17-generic, x86_64: installed
   nvidia/495.46, 5.15.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f]
  InstallationDate: Installed on 2021-09-09 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. G3 3579
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.109-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-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/mutter/+bug/1959888/+subscriptions


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

Re: [Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Mikołaj Neronowicz]

I also think this problem is very serious. Quite frustrating. I did not
suspect that I would have such problems on the LTS version where everything
should be stable. This is the third kernel update which has not fixed this
problem. I keep going back to kernel 5.13.0-35.

Operating System: Feren OS 2022.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.13.0-35-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-6820HQ CPU @ 2.70GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Quadro M2000M/PCIe/SSE2

śr., 27 kwi 2022 o 00:01 Richard Vincent <1966...@bugs.launchpad.net>
napisał(a):

> This bug is affecting me as well. Considering I run ubuntu studio, and
> the reason I run it is for audio, this is definitely more than a medium
> priority bug for me. This is happening on my Scarlett 2i2 audio
> interface.
>
> I am running kernel:
>
> 5.13.0-40-lowlatency
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1966327).
> https://bugs.launchpad.net/bugs/1966066
>
> Title:
>   audio from external sound card is distorted
>
> Status in linux package in Ubuntu:
>   Fix Committed
> Status in linux-signed-hwe-5.13 package in Ubuntu:
>   Invalid
> Status in linux source package in Impish:
>   Fix Committed
> Status in linux-signed-hwe-5.13 source package in Impish:
>   Invalid
> Status in linux source package in Jammy:
>   Fix Committed
> Status in linux-signed-hwe-5.13 source package in Jammy:
>   Invalid
>
> Bug description:
>   [Impact]
>   Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
>   next packet size") landed in 5.13.0-35 introduced regression to USB
>   audio device.
>
>   It's because this patch introduced the available frame size check, but
>   the conversion forgot to initialize the temporary variable properly.
>
>   A workaround is to modify /etc/pulse/daemon.conf, set the
>   default-sample-rate to 48000, uncomment it by removing the semicolon
>   at the beginning of the line. And restart pulseaudio with:
> systemctl --user restart pulseaudio.service
>
>   [Fix]
>   * 23939115 ALSA: usb-audio: Fix packet size calculation regression
>   This patch can be cherry-picked into Impish kernel, and it's already in
>   the master-next branch of Jammy tree.
>
>   [Test]
>   Test kernels built with 5.13.0-37 + this patch, can be found in:
>   * Focal-5.13 -
> https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
>   * Impish-5.13 -
> https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/
>
>   Both kernels were tested by affected users and they're working as
>   expected.
>
>   [Where problems could occur]
>   If this patch is incorrect, it might affect USB audio devices.
>
>
>   [Original Bug Report]
>   The sound card is a Focusrite Scarlett 2i2.
>
>   The sound is distorted everywhere.
>
>   Sound via HDMI works.
>
>   Seen others having the same problem:
>   (Edit because of previously wrong link here)
> https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
>
>   ubuntu release: Ubuntu 20.04.4 LTS
>   package name involved in bug: linux-image-5.13.0-37-generic
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
>   ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
>   Uname: Linux 5.13.0-35-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu27.21
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Mar 23 12:56:02 2022
>   InstallationDate: Installed on 2020-12-18 (459 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/+bug/1966066/+subscriptions
>
>

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

Title:
  audio from external sound card is distorted

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Impish:
  Fix Committed
Status in linux-signed-hwe-5.13 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
  next packet size") landed in 5.13.0-35 introduced regression to USB
  audio device.

  It's because this patch introduced the available frame size check, but
  the conversion forgot to initialize the temporary variable properly.

[Kernel-packages] [Bug 1950914] Re: [daily jammy-live-server-amd64] Hangs at start of VM installation

[Launchpad Bug Tracker]

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

** Changed in: libvirt (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/1950914

Title:
  [daily jammy-live-server-amd64] Hangs at start of VM installation

Status in subiquity:
  Invalid
Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I downloaded  the 2021.11.14 daily:

  -rw-rwxr--+ 1 doug doug 1277655040 Nov 14 09:12 jammy-live-server-
  amd64.iso

  I tried to install it as a VM on a debian 11 server host and an Ubuntu
  20.04.3 server host, both were up to date as of a few days ago.
  Command used (pretty much the same command I have used for years):

  virt-install -n serv-jj -r 8192 \
  --disk path=/home/doug/vm/serv-jj.img,bus=virtio,size=50 \
  -c jammy-live-server-amd64-2021-11-14.iso \
  --network bridge=br0,model=virtio,mac=52:54:00:27:1c:6e \
  --video=vmvga --graphics vnc,listen=0.0.0.0 --noautoconsole -v --vcpus=4

  On both hosts it just hangs a after a couple of seconds. "virsh list"
  shows it running and "virsh destroy" does work.

  Note: I have never used the new installer before, I have always used
  the legacy Debain installer in the past, but I gather is is no longer
  supported.

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


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

[Kernel-packages] [Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32

[dann frazier]

Released upstream in 5.4.183. The inclusion of the changes from that
stable release is being tracked in bug 1969239.

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

Title:
  ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25
  report incorrect sched domain for cpu#32

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  On scobee-kernel(arm64) with hirsute:linux(5.11.0-41.45) for
  sru-20211108 there are several reports about the sched domain not
  covering the full range. The same does not happen on kuzzle. But 32 is
  a bit of a suspicious number.

Running tests...
cpuset_sched_domains 1 TINFO: CPUs are numbered continuously starting at 0 
(0-127)
cpuset_sched_domains 1 TINFO: Nodes are numbered continuously starting at 0 
(0-3)
cpuset_sched_domains 1 TINFO: root group load balance test
cpuset_sched_domains 1 TINFO:  sched load balance: 0
cpuset_sched_domains 1 TINFO: CPU hotplug:
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 1 TPASS: partition sched domains succeeded.
cpuset_sched_domains 3 TINFO: root group load balance test
cpuset_sched_domains 3 TINFO:  sched load balance: 1
cpuset_sched_domains 3 TINFO: CPU hotplug:
cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:110: 
cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95).
cpuset_sched_domains 3 TFAIL: partition sched domains failed.
cpuset_sched_domains 5 TINFO: root group load balance test
cpuset_sched_domains 5 TINFO:  sched load balance: 0
cpuset_sched_domains 5 TINFO: CPU hotplug:
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 5 TPASS: partition sched domains succeeded.
cpuset_sched_domains 7 TINFO: root group load balance test
cpuset_sched_domains 7 TINFO:  sched load balance: 0
cpuset_sched_domains 7 TINFO: CPU hotplug:
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 7 TPASS: partition sched domains succeeded.
cpuset_sched_domains 9 TINFO: root group load balance test
cpuset_sched_domains 9 TINFO:  sched load balance: 1
cpuset_sched_domains 9 TINFO: CPU hotplug:
cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:110: 
cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95).
cpuset_sched_domains 9 TFAIL: partition sched domains failed.
cpuset_sched_domains 11 TINFO: root group load balance test
cpuset_sched_domains 11 TINFO:  sched load balance: 1
cpuset_sched_domains 11 TINFO: CPU hotplug:
cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:110: 
cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95).
cpuset_sched_domains 11 TFAIL: partition sched domains failed.
cpuset_sched_domains 13 TINFO: general group load balance test
cpuset_sched_domains 13 TINFO: root group info:
cpuset_sched_domains 13 TINFO:  sched load balance: 0
cpuset_sched_domains 13 TINFO: general group info:
cpuset_sched_domains 13 TINFO:  cpus: -
cpuset_sched_domains 13 TINFO:  sched load balance: 1
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 13 TPASS: partition sched domains succeeded.
cpuset_sched_domains 15 TINFO: general group load balance test
cpuset_sched_domains 15 TINFO: root group info:
cpuset_sched_domains 15 TINFO:  sched load balance: 0
cpuset_sched_domains 15 TINFO: general group info:
cpuset_sched_domains 15 TINFO:  cpus: 1
cpuset_sched_domains 15 TINFO:  sched load balance: 0
cpuset_check_domains1  TPASS  :  check_sched_domains passed
cpuset_sched_domains 15 TPASS: partition sched domains succeeded.
cpuset_sched_domains 17 TINFO: general group load balance test
cpuset_sched_domains 17 TINFO: root group info:
cpuset_sched_domains 17 TINFO:  sched load balance: 1
cpuset_sched_domains 17 TINFO: general group info:
cpuset_sched_domains 17 TINFO:  cpus: -
cpuset_sched_domains 17 TINFO:  sched load balance: 1
cpuset_check_domains1  TFAIL  :  cpuset_sched_domains_check.c:110: 
cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95).
cpuset_sched_domains 17 TFAIL: partition sched domains failed.

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

[zeli]

I created a live USB stick with persistent store on it to test the workaround, 
and the system booted up fine. I didn't get screen where you choose between 
'Try Ubuntu' or 'Install', so probably that's why it is working. I checked it 
and the nouveau driver was selected so i'm not sure if it's directly related, 
something is messing up the screen when you click on the try button.
Also i usually don't use persistent space because it makes the live boot very 
slow.

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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


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

[Kernel-packages] [Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot

[Noctis Bennington]

PS: In case you need see what's going on with pci=nocrs on 22.04

https://i.stack.imgur.com/KZtIy.jpg

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

Title:
  MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized
  from any given boot

Status in Linux:
  Confirmed
Status in Ubuntu:
  Confirmed
Status in linux-signed-hwe package in Ubuntu:
  In Progress
Status in linux-signed-hwe package in Fedora:
  New

Bug description:
  Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work
  at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5
  14IIL05 81YH' from first system start on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tilman 1607 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 21:22:22 2020
  InstallationDate: Installed on 2020-05-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DSCN23WW(V1.09)
  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: IdeaPad 5 14IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05:
  dmi.product.family: IdeaPad 5 14IIL05
  dmi.product.name: 81YH
  dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05
  dmi.product.version: IdeaPad 5 14IIL05
  dmi.sys.vendor: LENOVO

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


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

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

[tomeq_]

@Daniel - I understand how to troubleshoot things and your steps seems
very valid, but I don't have any discrete AMD card right here to
test.

Also - AMD Ryzen CPUs are not equipped with builtin GPU :)

Whole case is about the installation process is simply impossible to be
accomplished for 99% of the users. Screen get yellow-green when you
click any of the available options in the installer, "live" or
"install". That's it.

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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


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

[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown

[Martien Lagerweij]

Since there is no patch yet, I am using this work-around for my HP laptop 
(hw/sw details: see #45):
- put this in /etc/default/grub (in my setup it is only changing the default 
value of that var)
  GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! \"acpi_osi=Windows 2015\" "
- then run this command to update the grub menu config:
  sudo update-grub2

@kaihengfeng
Any progress on the rework of the 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/1912935

Title:
  battery drain while notebook off / shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu.
  It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 .

  Tested:

  - with ubuntu 20.04
  - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4)
  - no usb devices are plugged in
  - no wake ob lan available
  - no USB power when off (checked with optical mouse)
  - no visible LEDs are on when shutdown

  I reinstalled window 10, when shutdown from windows there is no
  (visible) battery drain (or significantly lower).

  Linux is unusable on this device, if the battery drains in a short
  time to 0% percent. This cause battery damage ...

  ---

  Tested TLP with default settings and activated
  DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power
  consumption after shutdown.

  Same power consumption on 20.10 (Groovy Gorilla).

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  test953 F pulseaudio
   /dev/snd/controlC0:  test953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-24 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: HP HP Laptop 15s-eq0xxx
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-64-generic N/A
   linux-backports-modules-5.4.0-64-generic  N/A
   linux-firmware1.187.8
  Tags:  focal
  Uname: Linux 5.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FD
  dmi.board.vendor: HP
  dmi.board.version: 99.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15s-eq0xxx
  dmi.product.sku: 20T63EA#ABD
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

[Pete Woods]

Thankyou for doing this so quickly - let me see if I can get one of the
customers setup to work with this kernel.

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

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Jammy:
  In Progress

Bug description:
  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.

  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their
  CI runs.

  Unfortunately they cannot run their tests on our AWS based VMs, as
  there is no sound support compiled into the kernel on the AWS kernel
  and images.

  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```

  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

  again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

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


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

[Kernel-packages] [Bug 1970293] Re: The system hangs when HDMI external monitor involved on AMD Yellow Carp platforms

[You-Sheng Yang]

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2022-April/129806.html (focal, 
linux-firmware)
* https://lists.ubuntu.com/archives/kernel-team/2022-April/129807.html (jammy, 
linux-firmware)

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

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

** Changed in: linux-firmware (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: linux-firmware (Ubuntu Focal)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux-firmware (Ubuntu Jammy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-firmware (Ubuntu Kinetic)
   Status: New => 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/1970293

Title:
  The system hangs when HDMI external monitor involved on AMD Yellow
  Carp platforms

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [Summary]
  1. The system will hang on when the HDMI external monitor is connected.
  2. The system will hang on after the HDMI external monitor is unplugged.
  3. The system will show no display when the HDMI external monitor is 
unplugged, but the system not hangs on.
   a. if connect HDMI external monitor back, the system will hang on.
   b. if connect type-c HDMI external monitor, the system works well.

  Note:
  1. Only built-in HDMI can duplicate.
  2. FHD/4K monitor both can duplicate

  [Steps to reproduce]
  2. Boot to OS
  3. Connect external montior on HDMI port.

  [Expected result]
  The system can work well when the external monitor is connected.

  [Actual result]
  The system hangs on with the HDMI external monitor.

  [Failure rate]
  2/3

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


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

[Kernel-packages] [Bug 1968900] Re: linux-azure: Harmonize arm64 config settings with amd64

[Tim Gardner]

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

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

Title:
  linux-azure: Harmonize arm64 config settings with amd64

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

Bug description:
  SRU Justification

  [Impact]

  Many arm64 config settings are unnecessarily different from amd64.

  [Test Case]

  Kernel regression test suite.

  [Where things could go wrong]

  Enabling or disabling config options may impact kernel behavior.

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


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

[Kernel-packages] [Bug 1970223] Re: linux-azure: add check to prevent attempting to resize an fs with sparse_super2

[Tim Gardner]

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

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

Title:
  linux-azure: add check to prevent attempting to resize an fs with
  sparse_super2

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

Bug description:
  SRU Justification

  [Impact]

  Microsoft has detected an Xfstest failure scenario. There might be fs
  corruption when resizing ext4 filesystems mounted with sparse_super2
  option enabled.

  Fix: commit b1489186cc8391e0c1e342f9fbc3eedf6b944c61 ("ext4: add check
  to prevent attempting to resize an fs with sparse_super2")

  [Test Case]
  mkfs.ext4 -b 4096 -I 256 -J size=32 -E resize=$((256*1024*1024)) -O 
sparse_super2 ext4.img 65M truncate -s 30G ext4.img
  mount ext4.img /mnt
  python3 -c 'import fcntl, os, struct ; fd = os.open("/mnt", os.O_RDONLY | 
os.O_DIRECTORY) ; fcntl.ioctl(fd, 0x40086610, struct.pack("Q", 30 * 1024 * 1024 
* 1024 // 4096), False) ; os.close(fd)'
  dmesg | tail
  e2fsck ext4.img

  [Where things could go wrong]

  The file system may erroneously not mount.

  [Other Info]

  SF: #00334996

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


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

[Kernel-packages] [Bug 1970621] 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 1970621

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

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

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

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

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

Title:
  [Ubuntu 22.04] Update nvme-cli to v2.0

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in nvme-cli package in Ubuntu:
  New

Bug description:
  Request you to update nvme-cli to v2.0 which has several fixes and
  features required for NVMe over TCP.

  nvme-cli v2.0 also depends on libnvme, inclusion of which is requested
  in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636

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


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

[Kernel-packages] [Bug 1970621] [NEW] [Ubuntu 22.04] Update nvme-cli to v2.0

[Sujith Pandel]

Public bug reported:

Request you to update nvme-cli to v2.0 which has several fixes and
features required for NVMe over TCP.

nvme-cli v2.0 also depends on libnvme, inclusion of which is requested
in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636

** Affects: dellserver
 Importance: Undecided
 Status: New

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

** Affects: nvme-cli (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: nvme-cli (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: dellserver
   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/1970621

Title:
  [Ubuntu 22.04] Update nvme-cli to v2.0

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in nvme-cli package in Ubuntu:
  New

Bug description:
  Request you to update nvme-cli to v2.0 which has several fixes and
  features required for NVMe over TCP.

  nvme-cli v2.0 also depends on libnvme, inclusion of which is requested
  in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636

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


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

[Kernel-packages] [Bug 1965241] Re: Include DPC Fixes in Ubuntu 22.04 and 20.04

[Michael Reed]

** Description changed:

  SRU Justification:
  
  [Impact]
  Recovery from DownPort Containment events fail and the NVMe endpoint is not 
accessible in some scenarios.
  
  [Fix]
  
  These are some of the DPC fixes which help in handling some of the
  failure cases of DownPort Containment events.
  
  Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu
  20.04.5:
  
  Already in Jammy as of Ubuntu-5.15.0-1.1
  PCI/portdrv: Enable Bandwidth Notification only if port supports it
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4
  
  Not yet pulled
  PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884
  
  [Test Case]
  
+ 1. Disable the memory space of NVMe end point device
+ 2. Issue IO to the device
+ 3. Observe dmesg. dmesg shows that EDR event is generated, link is contained 
and NVMe device is recovered.
+ 
+ 2. Observe the dmesg
  [Other Info]
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965241

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

Title:
  Include DPC Fixes in Ubuntu 22.04 and 20.04

Status in dellserver:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress

Bug description:
  SRU Justification:

  [Impact]
  Recovery from DownPort Containment events fail and the NVMe endpoint is not 
accessible in some scenarios.

  [Fix]

  These are some of the DPC fixes which help in handling some of the
  failure cases of DownPort Containment events.

  Upstream kernel patches to be included into Ubuntu 22.04 and into
  Ubuntu 20.04.5:

  Already in Jammy as of Ubuntu-5.15.0-1.1
  PCI/portdrv: Enable Bandwidth Notification only if port supports it
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4

  Not yet pulled
  PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884

  [Test Case]

  1. Disable the memory space of NVMe end point device
  2. Issue IO to the device
  3. Observe dmesg. dmesg shows that EDR event is generated, link is contained 
and NVMe device is recovered.

  2. Observe the dmesg
  [Other Info]
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965241

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


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

[Kernel-packages] [Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot

[Noctis Bennington]

Yeah...I'm agree Michael. At least in 20.04 that workaround was working
with me and a lot of users (but as I said, I'm agree with you). Now in
22.04 it's impossible to make it works. Let's see if we can do something
about it...

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

Title:
  MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized
  from any given boot

Status in Linux:
  Confirmed
Status in Ubuntu:
  Confirmed
Status in linux-signed-hwe package in Ubuntu:
  In Progress
Status in linux-signed-hwe package in Fedora:
  New

Bug description:
  Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work
  at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5
  14IIL05 81YH' from first system start on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tilman 1607 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 21:22:22 2020
  InstallationDate: Installed on 2020-05-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DSCN23WW(V1.09)
  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: IdeaPad 5 14IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05:
  dmi.product.family: IdeaPad 5 14IIL05
  dmi.product.name: 81YH
  dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05
  dmi.product.version: IdeaPad 5 14IIL05
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1970552] Re: Mute/mic LEDs no function on EliteBook G9 platfroms

[Stefan Bader]

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

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

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

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

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

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

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

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

** Changed in: linux-oem-5.14 (Ubuntu)
   Status: New => Invalid

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

** Changed in: linux-oem-5.14 (Ubuntu Jammy)
   Status: New => Invalid

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

Title:
  Mute/mic LEDs no function on EliteBook G9 platfroms

Status in OEM Priority Project:
  Confirmed
Status in linux 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.14 source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on
  1) HP EliteBook x360 830 G9
  2) HP EliteBook 830 G9
  3) HP EliteBook 840 G9
  4) HP EliteBook 860 G9
  5) HP EliteBook 840 Aero G9
  6) HP EliteBook x360 840 Aero G9

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

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


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

Re: [Kernel-packages] [Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot

[Michael Amplatz]

It has never been no problem. A bug that can be solved by a workaround 
that works most times with many people is not solved.

In my opinion the case can be closed when the new Touchpad used by 
Lenovo works after booting into the official image. I am waiting for 
that for two years now on different Notebooks.

Am 26.04.22 um 22:11 schrieb Noctis Bennington:
> Hello there.
>
> the pci=nocrs on Ubuntu 22.04 doesn't allow boot. So this is again a
> problem in the last LTS (22.04).
>

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

Title:
  MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized
  from any given boot

Status in Linux:
  Confirmed
Status in Ubuntu:
  Confirmed
Status in linux-signed-hwe package in Ubuntu:
  In Progress
Status in linux-signed-hwe package in Fedora:
  New

Bug description:
  Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work
  at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5
  14IIL05 81YH' from first system start on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tilman 1607 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 21:22:22 2020
  InstallationDate: Installed on 2020-05-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DSCN23WW(V1.09)
  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: IdeaPad 5 14IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05:
  dmi.product.family: IdeaPad 5 14IIL05
  dmi.product.name: 81YH
  dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05
  dmi.product.version: IdeaPad 5 14IIL05
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1970412] Re: [VROC] Ubuntu doesn't support 3rd SATA

[Lukasz]

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

Title:
  [VROC] Ubuntu doesn't support 3rd SATA

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  An effort has been made to enable 3rd SATA support in kernel, but 
unfortunately the patch didn't make it to upstream (we are still working to 
make it happen). Without it certain utility programs cannot function properly 
when 3rd SATA is engaged.
  The patch itself adds Intel Emmitsburg PCH RAID PCI IDs to the list of 
supported controllers. Would you kindly apply this patch to 22.04 release?

  Patch to be applied: https://lore.kernel.org/linux-
  ide/20201119104318.79297-1-mika.westerb...@linux.intel.com/

  Regards,
  Lukasz

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


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

[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

[Stéphane Verdy]

Latest FM350 is FR 1.26.13 (equivalent to
81600..00.29.19.16_5000..036.000.036_C40). Intel clarified that
we should get that firmware from Fibocom and use that for testing.

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

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]

  
https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/
  --- 
  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-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  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-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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


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

[Kernel-packages] [Bug 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

[Tim Gardner]

Please try the test kernel at https://kernel.ubuntu.com/~rtg/jammy-snd-
aloop-lp1970586/5.15.0-1006.8~lp1970586.1/. I've made only the minimal
config change to enable CONFIG_SND_ALOOP=m.

wget 
https://kernel.ubuntu.com/~rtg/jammy-snd-aloop-lp1970586/5.15.0-1006.8~lp1970586.1/amd64/linux-image-unsigned-5.15.0-1006-aws_5.15.0-1006.8~lp1970586.1_amd64.deb
wget 
https://kernel.ubuntu.com/~rtg/jammy-snd-aloop-lp1970586/5.15.0-1006.8~lp1970586.1/amd64/linux-modules-5.15.0-1006-aws_5.15.0-1006.8~lp1970586.1_amd64.deb
wget 
https://kernel.ubuntu.com/~rtg/jammy-snd-aloop-lp1970586/5.15.0-1006.8~lp1970586.1/amd64/linux-modules-extra-5.15.0-1006-aws_5.15.0-1006.8~lp1970586.1_amd64.deb
sudo dpkg -i *.deb
sudo apt-get -f install

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

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Jammy:
  In Progress

Bug description:
  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.

  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their
  CI runs.

  Unfortunately they cannot run their tests on our AWS based VMs, as
  there is no sound support compiled into the kernel on the AWS kernel
  and images.

  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```

  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

  again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

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


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

[Kernel-packages] [Bug 1944080] Re: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error

[Canonical Juju QA Bot]

** Changed in: juju
Milestone: 2.9.29 => 2.9.30

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

Title:
  [fan-network] Race-condition between "apt update" and dhcp request
  causes cloud-init error

Status in OpenStack RabbitMQ Server Charm:
  Invalid
Status in juju:
  Triaged
Status in ubuntu-fan package in Ubuntu:
  New

Bug description:
  Hi,

  Using manual provider on top of VMWare.

  Juju: 2.9.14
  VM: Focal
  Containers: Bionic

  I've noticed that, in a given Focal host, 2x Bionic containers may
  have different behavior: one successfully completes cloud-init whereas
  the other fails. The failed container errors at "apt update" in cloud-
  init with:

  Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Something wicked happened resolving 'PROXY_IP:' (-9 - Address family 
for hostname not supported)
  (Likely this is the line where it breaks: 
https://github.com/Debian/apt/blob/766b24b7f7484751950c76bc66d3d6cdeaf949a5/methods/connect.cc#L436)

  Failed container, full cloud-init-output.log: 
https://pastebin.canonical.com/p/hKNw49mvJP/
  Successful container, full cloud-init-output.log: 
https://pastebin.canonical.com/p/P6MZdQPrWd/
  Host syslog: https://pastebin.canonical.com/p/jjMmWRFd9y/

  I can see that, on the host, dnsmasq served the FAN IP to the broken
  container after the "apt-update" was called.

  - FAILED CONTAINER -:
  Sep 19 13:02:14 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 
252.252.15.198 00:16:3e:da:dd:c4 
  apt-update on cloud-init was ran:
  Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at 
Sun, 19 Sep 2021 13:02:13 +. Up 3.90 seconds.

  
  - SUCCESSFUL CONTAINER -:
  Sep 19 13:09:40 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 
252.252.15.253 00:16:3e:d7:6b:ef 
  apt-update on cloud-init was ran:
  Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at 
Sun, 19 Sep 2021 13:10:10 +. Up 35.99 seconds.

  In the case of the Failed Container, the DHCPOFFER arrived 1s after
  the "apt update" was requested, whereas the Successful Container
  logged a DHCPOFFER 30s before the "apt update".

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1944080/+subscriptions


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

[Kernel-packages] [Bug 1955042] Re: SBI SRST extension is missing

[Alexandre Ghiti]

This fix was merged in 5.15.0-1005.5.

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

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

Title:
  SBI SRST extension is missing

Status in linux-riscv package in Ubuntu:
  Fix Released

Bug description:
  SBI SRST extension is needed for handling sifive unmatched reboot and
  with the reset now merged into openSBI package, enabling SRST
  extension finally gives us the possibility to reset the board.

  The patch to enable SRST extension can be found here:
  https://lore.kernel.org/all/20210609121322.3058-2-anup.pa...@wdc.com/
  or use the attached patch.

  I tested it on top of 5.13.0-1006.6+22.04.1 on the unmatched board and
  it allows to successfully reboots the board.

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


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

[Kernel-packages] [Bug 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

[hidaris]

Very strange, with comment 3 I can avoid freeze but have to turn on
fractional scaling, not a permanent way to solve the problem, do I need
to capture anything between the two  states again?

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+subscriptions


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

[Kernel-packages] [Bug 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

[Tim Gardner]

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

** Changed in: linux-aws (Ubuntu Jammy)
   Importance: Undecided => Low

** Changed in: linux-aws (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-aws (Ubuntu Jammy)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Jammy:
  In Progress

Bug description:
  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.

  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their
  CI runs.

  Unfortunately they cannot run their tests on our AWS based VMs, as
  there is no sound support compiled into the kernel on the AWS kernel
  and images.

  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```

  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

  again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

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


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

[Kernel-packages] [Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE

[Kai-Chuan Hsieh]

yes, the driver patch for jammy 5.15 kernel is still in progress.
Therefore, the modules's hotspot mode is not supported yet.

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

Title:
  Enable hotspot feature for Realtek 8821CE

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  In Progress

Bug description:
  [Impact]
  The wifi hotspot doesn't work without the fix.

  [Fix]
  Realtek provides us the patches to add this feature which are still in 
linux-next.
  
https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/
  ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value
  f5207c122102 rtw88: do PHY calibration while starting AP
  f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames
  f2217968ffda rtw88: Add update beacon flow for AP mode
  6723c0cde84f rtw88: fix incorrect frequency reported
  c1edc86472fc rtw88: add ieee80211:sta_rc_update ops

  Realtek provides us another series of patches for 5.14, and it
  contains 5 commits, we'd verified this series of patches.

  [Test]
  Verified on the Realtek 8821CE card.

  [Where problems could occur]
  The patches are introducing new interfaces, I think it only has minimal 
impact to the origin behaviors.

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


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

[Kernel-packages] [Bug 1929894] Re: [TGL][EHL][ADL] Enable MEI (Intel Management Engine Interface)

[Philip Cox]

@Sachin, I've looked into those two, and they seem to have been disabled
because they were not building.  I am looking at them again, and will
see about re-enabling them.

** Changed in: intel/lookout-canyon
   Status: Fix Released => Triaged

** Changed in: intel/lookout-canyon
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  [TGL][EHL][ADL] Enable MEI (Intel Management Engine Interface)

Status in intel:
  New
Status in intel lookout-canyon series:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-intel package in Ubuntu:
  Won't Fix
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Incomplete
Status in linux-intel source package in Focal:
  Won't Fix
Status in linux-intel-5.13 source package in Focal:
  Fix Released

Bug description:
  Description
  Enable MEI (Intel Management Engine Interface)
  Host communicates with secured apps in firmware with this interface

  Hardware: Tiger Lake/Elkhart Lake/Alder Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

  X-HWE-Bug: Bug #1945464

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


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

[Kernel-packages] [Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE

[Soumadeep Sarkar]

I am using ubuntu 22.04. My lapitop has Realtek 8821CE. Kernel version
is 5.15.0-27-generic. Wifi hotspot turns on, but other devices are
unable to connect. Is this problem related to this bug?

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

Title:
  Enable hotspot feature for Realtek 8821CE

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  In Progress

Bug description:
  [Impact]
  The wifi hotspot doesn't work without the fix.

  [Fix]
  Realtek provides us the patches to add this feature which are still in 
linux-next.
  
https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/
  ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value
  f5207c122102 rtw88: do PHY calibration while starting AP
  f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames
  f2217968ffda rtw88: Add update beacon flow for AP mode
  6723c0cde84f rtw88: fix incorrect frequency reported
  c1edc86472fc rtw88: add ieee80211:sta_rc_update ops

  Realtek provides us another series of patches for 5.14, and it
  contains 5 commits, we'd verified this series of patches.

  [Test]
  Verified on the Realtek 8821CE card.

  [Where problems could occur]
  The patches are introducing new interfaces, I think it only has minimal 
impact to the origin behaviors.

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


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

[Kernel-packages] [Bug 1962674] Re: Add IIO sensors ID for ACPI based platform

[Launchpad Bug Tracker]

This bug was fixed in the package linux-intel-5.13 - 5.13.0-1011.11

---
linux-intel-5.13 (5.13.0-1011.11) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1011.11 -proposed tracker (LP:
#1968865)

  * Ubuntu Server lose connection when download >1G large file (LP: #1967257)
- bus: mhi: pci-generic: configurable network interface MRU
- bus: mhi: pci_generic: Add mru_default for Quectel EM1xx series
- bus: mhi: pci_generic: Add mru_default for Foxconn SDX55

  * Add IIO sensors ID for ACPI based platform (LP: #1962674)
- iio: accel: adxl345: Convert to use dev_err_probe()
- iio: accel: adxl345: Set driver_data for OF enumeration
- iio: accel: adxl345: Get rid of name parameter in adxl345_core_probe()
- iio: accel: adxl345: Make use of device properties
- iio: accel: adxl345: Add ACPI HID table
- iio: accel: adxl345: Extract adxl345_powerup() helper
- iio: accel: adxl345: Drop comma in terminator entries
- iio: accel: adxl345: Remove unneeded blank lines
- iio: humidity: hdc100x: Add ACPI HID table
- iio: pressure: dps310: Add ACPI HID table

  * Bail out when USB port is stuck in reset loop (LP: #1960777)
- usb: core: Bail out when port is stuck in reset loop

  [ Ubuntu: 5.13.0-40.45~20.04.1 ]

  * focal/linux-hwe-5.13: 5.13.0-40.45~20.04.1 -proposed tracker (LP: #1967356)
  * impish/linux: 5.13.0-40.45 -proposed tracker (LP: #1966701)
  * CVE-2022-1016
- netfilter: nf_tables: initialize registers in nft_do_chain()
  * CVE-2022-1015
- netfilter: nf_tables: validate registers coming from userspace.
  * audit: improve audit queue handling when "audit=1" on cmdline
(LP: #1965723) // Impish update: upstream stable patchset 2022-03-22
(LP: #1966021)
- audit: improve audit queue handling when "audit=1" on cmdline
  * PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp platform
(LP: #1961739)
- PM: s2idle: ACPI: Fix wakeup interrupts handling
  * Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
  * [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
  * Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
  * Impish update: upstream stable patchset 2022-03-09 (LP: #1964422)
- bnx2x: Utilize firmware 7.13.21.0
- bnx2x: Invalidate fastpath HSI version for VFs
- rcu: Tighten rcu_advance_cbs_nowake() checks
- select: Fix indefinitely sleeping task in poll_schedule_timeout()
- drm/amdgpu: Use correct VIEWPORT_DIMENSION for DCN2
- arm64/bpf: Remove 128MB limit for BPF JIT programs
- Bluetooth: refactor malicious adv data check
- net: sfp: ignore disabled SFP node
- net: stmmac: skip only stmmac_ptp_register when resume from suspend
- s390/hypfs: include z/VM guests with access control group set
- bpf: Guard against accessing NULL pt_regs in bpf_get_task_stack()
- scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP
  devices
- udf: Restore i_lenAlloc when inode expansion fails
- udf: Fix NULL ptr deref when converting from inline format
- efi: runtime: avoid EFIv2 runtime services on Apple x86 machines
- PM: wakeup: simplify the output logic of pm_show_wakelocks()
- tracing/histogram: Fix a potential memory leak for kstrdup()
- tracing: Don't inc err_log entry count if entry allocation fails
- ceph: properly put ceph_string reference after async create attempt
- ceph: set pool_ns in new inode layout for async creates
- fsnotify: fix fsnotify hooks in pseudo filesystems
- Revert "KVM: SVM: avoid infinite loop on NPF from bad address"
- perf/x86/intel/uncore: Fix CAS_COUNT_WRITE issue for ICX
- drm/etnaviv: relax submit size limits
- KVM: x86: Update vCPU's runtime CPUID on write to MSR_IA32_XSS
- netfilter: nft_payload: do not update layer 4 checksum when mangling
  fragments
- serial: 8250: of: Fix mapped region size when using reg-offset property
- serial: stm32: fix software flow control transfer
- tty: n_gsm: fix SW flow control encoding/handling
- tty: Add support for Brainboxes UC cards.
- usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge
- usb: xhci-plat: fix crash when suspend if remote wake enable
- usb: common: ulpi: Fix crash in ulpi_match()
- usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS
- USB: core: Fix hang in usb_kill_urb by adding memory barriers
- usb: typec: tcpm: Do not disconnect while receiving VBUS off
- ucsi_ccg: Check DEV_INT bit only when starting CCG4
- jbd2: export jbd2_journal_[grab|put]_journal_head
- ocfs2: fix a deadlock when commit trans
- sched/membarrier: Fix 

[Kernel-packages] [Bug 1960777] Re: Bail out when USB port is stuck in reset loop

[Launchpad Bug Tracker]

This bug was fixed in the package linux-intel-5.13 - 5.13.0-1011.11

---
linux-intel-5.13 (5.13.0-1011.11) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1011.11 -proposed tracker (LP:
#1968865)

  * Ubuntu Server lose connection when download >1G large file (LP: #1967257)
- bus: mhi: pci-generic: configurable network interface MRU
- bus: mhi: pci_generic: Add mru_default for Quectel EM1xx series
- bus: mhi: pci_generic: Add mru_default for Foxconn SDX55

  * Add IIO sensors ID for ACPI based platform (LP: #1962674)
- iio: accel: adxl345: Convert to use dev_err_probe()
- iio: accel: adxl345: Set driver_data for OF enumeration
- iio: accel: adxl345: Get rid of name parameter in adxl345_core_probe()
- iio: accel: adxl345: Make use of device properties
- iio: accel: adxl345: Add ACPI HID table
- iio: accel: adxl345: Extract adxl345_powerup() helper
- iio: accel: adxl345: Drop comma in terminator entries
- iio: accel: adxl345: Remove unneeded blank lines
- iio: humidity: hdc100x: Add ACPI HID table
- iio: pressure: dps310: Add ACPI HID table

  * Bail out when USB port is stuck in reset loop (LP: #1960777)
- usb: core: Bail out when port is stuck in reset loop

  [ Ubuntu: 5.13.0-40.45~20.04.1 ]

  * focal/linux-hwe-5.13: 5.13.0-40.45~20.04.1 -proposed tracker (LP: #1967356)
  * impish/linux: 5.13.0-40.45 -proposed tracker (LP: #1966701)
  * CVE-2022-1016
- netfilter: nf_tables: initialize registers in nft_do_chain()
  * CVE-2022-1015
- netfilter: nf_tables: validate registers coming from userspace.
  * audit: improve audit queue handling when "audit=1" on cmdline
(LP: #1965723) // Impish update: upstream stable patchset 2022-03-22
(LP: #1966021)
- audit: improve audit queue handling when "audit=1" on cmdline
  * PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp platform
(LP: #1961739)
- PM: s2idle: ACPI: Fix wakeup interrupts handling
  * Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
  * [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
  * Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
  * Impish update: upstream stable patchset 2022-03-09 (LP: #1964422)
- bnx2x: Utilize firmware 7.13.21.0
- bnx2x: Invalidate fastpath HSI version for VFs
- rcu: Tighten rcu_advance_cbs_nowake() checks
- select: Fix indefinitely sleeping task in poll_schedule_timeout()
- drm/amdgpu: Use correct VIEWPORT_DIMENSION for DCN2
- arm64/bpf: Remove 128MB limit for BPF JIT programs
- Bluetooth: refactor malicious adv data check
- net: sfp: ignore disabled SFP node
- net: stmmac: skip only stmmac_ptp_register when resume from suspend
- s390/hypfs: include z/VM guests with access control group set
- bpf: Guard against accessing NULL pt_regs in bpf_get_task_stack()
- scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP
  devices
- udf: Restore i_lenAlloc when inode expansion fails
- udf: Fix NULL ptr deref when converting from inline format
- efi: runtime: avoid EFIv2 runtime services on Apple x86 machines
- PM: wakeup: simplify the output logic of pm_show_wakelocks()
- tracing/histogram: Fix a potential memory leak for kstrdup()
- tracing: Don't inc err_log entry count if entry allocation fails
- ceph: properly put ceph_string reference after async create attempt
- ceph: set pool_ns in new inode layout for async creates
- fsnotify: fix fsnotify hooks in pseudo filesystems
- Revert "KVM: SVM: avoid infinite loop on NPF from bad address"
- perf/x86/intel/uncore: Fix CAS_COUNT_WRITE issue for ICX
- drm/etnaviv: relax submit size limits
- KVM: x86: Update vCPU's runtime CPUID on write to MSR_IA32_XSS
- netfilter: nft_payload: do not update layer 4 checksum when mangling
  fragments
- serial: 8250: of: Fix mapped region size when using reg-offset property
- serial: stm32: fix software flow control transfer
- tty: n_gsm: fix SW flow control encoding/handling
- tty: Add support for Brainboxes UC cards.
- usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge
- usb: xhci-plat: fix crash when suspend if remote wake enable
- usb: common: ulpi: Fix crash in ulpi_match()
- usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS
- USB: core: Fix hang in usb_kill_urb by adding memory barriers
- usb: typec: tcpm: Do not disconnect while receiving VBUS off
- ucsi_ccg: Check DEV_INT bit only when starting CCG4
- jbd2: export jbd2_journal_[grab|put]_journal_head
- ocfs2: fix a deadlock when commit trans
- sched/membarrier: Fix 

[Kernel-packages] [Bug 1967257] Re: Ubuntu Server lose connection when download >1G large file

[Launchpad Bug Tracker]

This bug was fixed in the package linux-intel-5.13 - 5.13.0-1011.11

---
linux-intel-5.13 (5.13.0-1011.11) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1011.11 -proposed tracker (LP:
#1968865)

  * Ubuntu Server lose connection when download >1G large file (LP: #1967257)
- bus: mhi: pci-generic: configurable network interface MRU
- bus: mhi: pci_generic: Add mru_default for Quectel EM1xx series
- bus: mhi: pci_generic: Add mru_default for Foxconn SDX55

  * Add IIO sensors ID for ACPI based platform (LP: #1962674)
- iio: accel: adxl345: Convert to use dev_err_probe()
- iio: accel: adxl345: Set driver_data for OF enumeration
- iio: accel: adxl345: Get rid of name parameter in adxl345_core_probe()
- iio: accel: adxl345: Make use of device properties
- iio: accel: adxl345: Add ACPI HID table
- iio: accel: adxl345: Extract adxl345_powerup() helper
- iio: accel: adxl345: Drop comma in terminator entries
- iio: accel: adxl345: Remove unneeded blank lines
- iio: humidity: hdc100x: Add ACPI HID table
- iio: pressure: dps310: Add ACPI HID table

  * Bail out when USB port is stuck in reset loop (LP: #1960777)
- usb: core: Bail out when port is stuck in reset loop

  [ Ubuntu: 5.13.0-40.45~20.04.1 ]

  * focal/linux-hwe-5.13: 5.13.0-40.45~20.04.1 -proposed tracker (LP: #1967356)
  * impish/linux: 5.13.0-40.45 -proposed tracker (LP: #1966701)
  * CVE-2022-1016
- netfilter: nf_tables: initialize registers in nft_do_chain()
  * CVE-2022-1015
- netfilter: nf_tables: validate registers coming from userspace.
  * audit: improve audit queue handling when "audit=1" on cmdline
(LP: #1965723) // Impish update: upstream stable patchset 2022-03-22
(LP: #1966021)
- audit: improve audit queue handling when "audit=1" on cmdline
  * PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp platform
(LP: #1961739)
- PM: s2idle: ACPI: Fix wakeup interrupts handling
  * Low RX performance for 40G Solarflare NICs (LP: #1964512)
- SAUCE: sfc: The size of the RX recycle ring should be more flexible
  * [UBUNTU 20.04] Fix SIGP processing on KVM/s390 (LP: #1962578)
- KVM: s390: Simplify SIGP Set Arch handling
- KVM: s390: Add a routine for setting userspace CPU state
  * Move virtual graphics drivers from linux-modules-extra to linux-modules
(LP: #1960633)
- [Packaging] Move VM DRM drivers into modules
  * Impish update: upstream stable patchset 2022-03-09 (LP: #1964422)
- bnx2x: Utilize firmware 7.13.21.0
- bnx2x: Invalidate fastpath HSI version for VFs
- rcu: Tighten rcu_advance_cbs_nowake() checks
- select: Fix indefinitely sleeping task in poll_schedule_timeout()
- drm/amdgpu: Use correct VIEWPORT_DIMENSION for DCN2
- arm64/bpf: Remove 128MB limit for BPF JIT programs
- Bluetooth: refactor malicious adv data check
- net: sfp: ignore disabled SFP node
- net: stmmac: skip only stmmac_ptp_register when resume from suspend
- s390/hypfs: include z/VM guests with access control group set
- bpf: Guard against accessing NULL pt_regs in bpf_get_task_stack()
- scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP
  devices
- udf: Restore i_lenAlloc when inode expansion fails
- udf: Fix NULL ptr deref when converting from inline format
- efi: runtime: avoid EFIv2 runtime services on Apple x86 machines
- PM: wakeup: simplify the output logic of pm_show_wakelocks()
- tracing/histogram: Fix a potential memory leak for kstrdup()
- tracing: Don't inc err_log entry count if entry allocation fails
- ceph: properly put ceph_string reference after async create attempt
- ceph: set pool_ns in new inode layout for async creates
- fsnotify: fix fsnotify hooks in pseudo filesystems
- Revert "KVM: SVM: avoid infinite loop on NPF from bad address"
- perf/x86/intel/uncore: Fix CAS_COUNT_WRITE issue for ICX
- drm/etnaviv: relax submit size limits
- KVM: x86: Update vCPU's runtime CPUID on write to MSR_IA32_XSS
- netfilter: nft_payload: do not update layer 4 checksum when mangling
  fragments
- serial: 8250: of: Fix mapped region size when using reg-offset property
- serial: stm32: fix software flow control transfer
- tty: n_gsm: fix SW flow control encoding/handling
- tty: Add support for Brainboxes UC cards.
- usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge
- usb: xhci-plat: fix crash when suspend if remote wake enable
- usb: common: ulpi: Fix crash in ulpi_match()
- usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS
- USB: core: Fix hang in usb_kill_urb by adding memory barriers
- usb: typec: tcpm: Do not disconnect while receiving VBUS off
- ucsi_ccg: Check DEV_INT bit only when starting CCG4
- jbd2: export jbd2_journal_[grab|put]_journal_head
- ocfs2: fix a deadlock when commit trans
- sched/membarrier: Fix 

[Kernel-packages] [Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline

[Kleber Sacilotto de Souza]

Manually marking focal/linux as 'Fix Released' as the fix was released
under bug 1964634.

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

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

Title:
  audit: improve audit queue handling when "audit=1" on cmdline

Status in linux package in Ubuntu:
  Fix Committed
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:
  SRU Justification

  [Impact]
  When an admin enables audit at early boot via the "audit=1" kernel
  command line the audit queue behavior is slightly different; the
  audit subsystem goes to greater lengths to avoid dropping records,
  which unfortunately can result in problems when the audit daemon is
  forcibly stopped for an extended period of time.

  [Fix]
  upstream discussion:
  
https://lore.kernel.org/all/cahc9vhqgx070poxzk_pusawgzppdqvpezvfybse2dnryrbw...@mail.gmail.com/T/
  upstream commit:
  f26d04331360d42dbd6b58448bd98e4edbfbe1c5

  [Test]
  configurations:
  auditctl -b 64
  auditctl --backlog_wait_time 6
  auditctl -r 0
  auditctl -w /root/aaa  -p wrx
  shell scripts：
  #!/bin/bash
  i=0
  while [ $i -le 66 ]
  do
  touch /root/aaa
let i++
  done
  mandatory conditions:
  add "audit=1" to the cmdline, and kill -19 pid_number(for /sbin/auditd).

  As long as we keep the audit_hold_queue non-empty, flush the hold
  queue will fall into an infinite loop.

  This could also trigger soft lockup when it drops into a infinite loop, e.g.
  kernel: [   94.186433] watchdog: BUG: soft lockup - CPU#2 stuck for 11s! 
[kauditd:34]
  kernel: [   94.187736] Modules linked in: xfs iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_
  conntrack libcrc32c iptable_filter isofs xt_cgroup xt_tcpudp iptable_mangle 
ip_tables x_tables sb_edac crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
pcbc aesni_intel aes_x86_64 pp
  dev crypto_simd glue_helper joydev vmwgfx ttm cryptd vmw_balloon 
drm_kms_helper intel_rapl_perf input_leds psmouse drm fb_sys_fops syscopyarea 
vmxnet3 sysfillrect parport_pc parport m
  ac_hid shpchp i2c_piix4 vmw_vsock_vmci_transport vsock sysimgblt vmw_vmci 
serio_raw mptspi mptscsih mptbase scsi_transport_spi pata_acpi floppy autofs4
  kernel: [   94.187757] CPU: 2 PID: 34 Comm: kauditd Not tainted 
4.15.0-171-generic #180~16.04.1-Ubuntu
  kernel: [   94.187757] Hardware name: VMware, Inc. VMware Virtual 
Platform/440BX Desktop Reference Platform, BIOS
   6.00 11/12/2020
  kernel: [   94.187800]  skb_queue_head+0x47/0x50
  kernel: [   94.187803]  kauditd_rehold_skb+0x18/0x20
  kernel: [   94.187805]  kauditd_send_queue+0xcd/0x100
  kernel: [   94.187806]  ? kauditd_retry_skb+0x20/0x20
  kernel: [   94.187808]  ? kauditd_send_multicast_skb+0x80/0x80
  kernel: [   94.187809]  kauditd_thread+0xa7/0x240
  kernel: [   94.187812]  ? wait_woken+0x80/0x80
  kernel: [   94.187815]  kthread+0x105/0x140
  kernel: [   94.187817]  ? auditd_reset+0x90/0x90
  kernel: [   94.187818]  ? kthread_bind+0x40/0x40
  kernel: [   94.187820]  ret_from_fork+0x35/0x40

  [Other Info]
  SF: #00330803

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


-- 
Mailing list: https://launchpad.net/~kernel-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

[Stefan Bader]

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

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

-- 
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-oem-5.17 package in Ubuntu:
  In Progress
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-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  In Progress

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: 

[Kernel-packages] [Bug 1958006] Re: multiple UBSAN warnings in Intel IPU6 camera driver at boot

[Stefan Bader]

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

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

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

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

Title:
  multiple UBSAN warnings in Intel IPU6 camera driver at boot

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

Bug description:
  [SRU Justfication]

  [Impact]

  Several UBSAN warnings captured on Intel IPU6 camera equipped platforms
  running 5.15+ kernels.

  [Fix]

  Upstream fix commit 8dcb7d8df28f ("media: pci: intel: Avoid UBSAN
  warnings of index bound and shift").

  [Test Case]

  Boot Intel IPU6 camera equipped platforms and check dmesg.

  [Where problems could occur]

  This patch turns a few return statements to error to stop further
  processing that may fall in UBSAN warnings. No other side effect.

  [Other Info]

  While plan for -generic and oem-5.17 is still under discuss, only Jammy
  is nominated for linux-oem-5.14/focal migration (to hwe-5.15).

  This depends on the pull request titled "Support Intel IPU6 MIPI camera
  on Alder Lake platforms" for bug 1955383 for Jammy.

  == original bug report ==

  UBSAN is turned on by default in Ubuntu 5.15 kernel. While Intel IPU6
  driver is still suffering from bug 1958004, intel_iommu issue, so
  these are found with intel_iommu=off.

  [   51.469485] 

  [   51.469490] UBSAN: invalid-load in 
/tmp/kernel-vicamo-8789bd62d725-b752/build/include/linux/dma-buf-map.h:224:9
  [   51.469494] load of value 2 is not a valid value for type '_Bool'
  [   51.469497] CPU: 8 PID: 1315 Comm: camerasrc0:src Tainted: G   O   
   5.15.0-2017-generic #17~20.04.1+lp1955383.2
  [   51.469500] Hardware name: Dell Inc. XPS 9320/, BIOS 0.2.7 12/02/2021
  [   51.469501] Call Trace:
  [   51.469504]  
  [   51.469508]  dump_stack_lvl+0x4a/0x5f
  [   51.469516]  dump_stack+0x10/0x12
  [   51.469519]  ubsan_epilogue+0x9/0x45
  [   51.469523]  __ubsan_handle_load_invalid_value.cold+0x44/0x49
  [   51.469530]  dma_buf_vmap.cold+0x38/0x3d
  [   51.469537]  ipu_psys_mapbuf_locked+0x178/0x450 [intel_ipu6_psys]
  [   51.469545]  ipu_psys_ioctl+0x148/0x4f0 [intel_ipu6_psys]
  [   51.469550]  ? __fget_files+0xa7/0xd0
  [   51.469556]  __x64_sys_ioctl+0x91/0xc0
  [   51.469560]  do_syscall_64+0x59/0xc0
  [   51.469564]  ? do_user_addr_fault+0x1dc/0x650
  [   51.469567]  ? irqentry_exit_to_user_mode+0x9/0x20
  [   51.469570]  ? irqentry_exit+0x19/0x30
  [   51.469573]  ? exc_page_fault+0x89/0x160
  [   51.469576]  ? asm_exc_page_fault+0x8/0x30
  [   51.469581]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   51.469585] RIP: 0033:0x7fa5e047250b
  [   51.469588] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48
  [   51.469589] RSP: 002b:7fa5debfa298 EFLAGS: 0246 ORIG_RAX: 
0010
  [   51.469592] RAX: ffda RBX: 7fa5d0004000 RCX: 
7fa5e047250b
  [   51.469593] RDX: 001f RSI: c0044102 RDI: 
001e
  [   51.469595] RBP: 7fa5d4a371e0 R08:  R09: 
007c
  [   51.469596] R10: 7fa5debfa120 R11: 0246 R12: 

  [   51.469597] R13: 7fa5d4a31bc0 R14: 7fa5debfa36c R15: 
7fa5debfa430
  [   51.469598]  
  [   51.469599] 


  [   52.050608] 

  [   52.050620] UBSAN: array-index-out-of-bounds in 
/tmp/kernel-vicamo-8789bd62d725-b752/build/drivers/media/pci/intel/ipu6/ipu-resources.c:633:30
  [   52.050631] index -1 is out of range for type 'ipu_resource_alloc [128]'
  [   52.050637] CPU: 8 PID: 803 Comm: psys_sched_cmd Tainted: G   O
  5.15.0-2017-generic #17~20.04.1+lp1955383.2
  [   52.050647] Hardware name: Dell Inc. XPS 9320/, BIOS 0.2.7 12/02/2021
  [   52.050651] Call Trace:
  [   52.050656]  
  [   52.050664]  dump_stack_lvl+0x4a/0x5f
  [   52.050692]  dump_stack+0x10/0x12
  [   52.050703]  ubsan_epilogue+0x9/0x45
  [   52.050716]  __ubsan_handle_out_of_bounds.cold+0x44/0x49
  [   52.050731]  ipu_psys_allocate_resources+0x4de/0x670 [intel_ipu6_psys]
  [   52.050761]  ipu_psys_ppg_start+0xff/0x250 [intel_ipu6_psys]
  [   52.050781]  ? ipu_psys_scheduler_ppg_start+0x1b6/0x510 [intel_ipu6_psys]
  [   52.050801]  ipu_psys_scheduler_ppg_start+0x429/0x510 [intel_ipu6_psys]
  [   52.050819]  ipu_psys_run_next+0x1c4/0x7c0 [intel_ipu6_psys]
  [   52.050836]  

[Kernel-packages] [Bug 1964983] Re: IPU6 camera has no function on Andrews MLK

[Stefan Bader]

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

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

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

Title:
  IPU6 camera has no function on Andrews MLK

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

Bug description:
  [SRU Justification]

  [Impact]

  New Andrews MLK equips yet another new I2C sensor and takes a few
  driver updates to function normally.

  [Fix]

  Upstream driver commit:
  
https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e

  [Test Case]

  To verify by following steps:

1. disable secure boot
2. $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
3. $ sudo add-apt-repository ppa:kchsieh/ipu6
4. $ sudo apt install linux-oem-5.14 version 5.14.0-9029-oem or newer
6. $ sudo apt install libipu6ep
7. $ sudo apt install libcamhal-ipu6ep-common
8. $ sudo apt install libcamhal-ipu6ep0
9. $ sudo apt install libgsticamerainterface-1.0-1
   10. $ sudo apt install gstreamer1.0-icamera
   11. $ sudo vim /etc/v4l2-relayd
  -FORMAT=YUY2
  +FORMAT=NV12
   12. $ sudo reboot

  [Where problems could occur]

  Intel IPU6 platform is still under development and is not capable of
  advanced power management features and may still suffer from stability
  issues.

  [Other Info]

  Nomination for 5.15 is necessary for oem-5.14 to hwe-5.15 migration and
  will depend on previous SRU proposal in bug 1955383
  (https://lists.ubuntu.com/archives/kernel-team/2022-March/128922.html).
  Nomination for generic-5.17 and oem-5.17 is still under planning.

  == original bug description ==

  The new platform uses yet another ov sensor OV02C10.

  Prerequisites:
  * kernel fix: 
https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e
  * ipu6-camera-bins: 
https://github.com/intel/ipu6-camera-bins/commit/7cc1dc2d9ab2b0766e034edf808d751bd25b42cc
  * ipu6-camera-hal: 
https://github.com/intel/ipu6-camera-hal/commit/b9b56de11de70b7c4520595176e4831bacf4a7fe
  * icamerasrc: 
https://github.com/intel/icamerasrc/commit/a35978264002acaad72bb9956238ccaef3743932

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


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

[Kernel-packages] [Bug 1969105] Re: Jammy update: v5.15.31 upstream stable release

[Stefan Bader]

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

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

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

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

Title:
  Jammy update: v5.15.31 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  
  Linux 5.15.31
  btrfs: skip reserved bytes warning on unmount after log cleanup failure
  perf symbols: Fix symbol size calculation condition
  Input: aiptek - properly check endpoint type
  scsi: mpt3sas: Page fault in reply q processing
  usb: usbtmc: Fix bug in pipe direction for control transfers
  usb: gadget: Fix use-after-free bug by not setting udc->dev.driver
  usb: gadget: rndis: prevent integer overflow in rndis_set_response()
  arm64: fix clang warning about TRAMP_VALIAS
  iavf: Fix hang during reboot/shutdown
  net: mscc: ocelot: fix backwards compatibility with single-chain tc-flower 
offload
  net: bcmgenet: skip invalid partial checksums
  bnx2x: fix built-in kernel driver load failure
  net: phy: mscc: Add MODULE_FIRMWARE macros
  net: dsa: Add missing of_node_put() in dsa_port_parse_of
  drm: Don't make DRM_PANEL_BRIDGE dependent on DRM_KMS_HELPERS
  net: handle ARPHRD_PIMREG in dev_is_mac_header_xmit()
  drm/panel: simple: Fix Innolux G070Y2-L01 BPP settings
  drm/imx: parallel-display: Remove bus flags check in 
imx_pd_bridge_atomic_check()
  hv_netvsc: Add check for kvmalloc_array
  iavf: Fix double free in iavf_reset_task
  atm: eni: Add check for dma_map_single
  net/packet: fix slab-out-of-bounds access in packet_recvmsg()
  net: phy: marvell: Fix invalid comparison in the resume and suspend functions
  esp6: fix check on ipv6_skip_exthdr's return value
  vsock: each transport cycles only on its own sockets
  alx: acquire mutex for alx_reinit in alx_change_mtu
  efi: fix return value of __setup handlers
  drm/mgag200: Fix PLL setup for g200wb and g200ew
  block: release rq qos structures for queue without disk
  mm: swap: get rid of livelock in swapin readahead
  ocfs2: fix crash when initialize filecheck kobj fails
  crypto: qcom-rng - ensure buffer for generate is completely filled

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


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

[Kernel-packages] [Bug 1968475] Re: Fix broken HDMI audio on AMD PRO VII after S3

[Stefan Bader]

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

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

Title:
  Fix broken HDMI audio on AMD PRO VII after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
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 Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  DP/HDMI audio on AMD PRO VII stops working after S3.

  [Fix]
  Ensure HDA function is suspended before ASIC reset so the subsequent
  resume can be carried out successfully.

  [Test]
  With the patch applied, DP/HDMI audio continues to work after S3.

  [Where problems could occur]
  The suspend_noirq phase should not trigger any interrupt, so if
  amdgpu_asic_reset() somehow raised IRQ, it can break the system.

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


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

[Kernel-packages] [Bug 1969107] Re: Jammy update: v5.15.34 upstream stable release

[Stefan Bader]

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

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

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

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

Title:
  Jammy update: v5.15.34 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  
  Linux 5.15.34
  stacktrace: move filter_irq_stacks() to kernel/stacktrace.c
  powerpc: Fix virt_addr_valid() for 64-bit Book3E & 32-bit
  static_call: Don't make __static_call_return0 static
  mm/sparsemem: fix 'mem_section' will never be NULL gcc 12 warning
  irqchip/gic, gic-v3: Prevent GSI to SGI translations
  powerpc/64: Fix build failure with allyesconfig in book3s_64_entry.S
  irqchip/gic-v4: Wait for GICR_VPENDBASER.Dirty to clear before descheduling
  x86,static_call: Fix __static_call_return0 for i386
  sched: Teach the forced-newidle balancer about CPU affinity limitation.
  x86/bug: Prevent shadowing in __WARN_FLAGS
  Drivers: hv: vmbus: Replace smp_store_mb() with virt_store_mb()
  mm: don't skip swap entry even if zap_details specified
  selftests: cgroup: Test open-time cgroup namespace usage for migration checks
  selftests: cgroup: Test open-time credential usage for migration checks
  selftests: cgroup: Make cg_create() use 0755 for permission instead of 0644
  ubsan: remove CONFIG_UBSAN_OBJECT_SIZE
  Revert "net/mlx5: Accept devlink user input after driver initialization 
complete"
  KVM: avoid NULL pointer dereference in kvm_dirty_ring_push
  dmaengine: Revert "dmaengine: shdma: Fix runtime PM imbalance on error"
  tools build: Use $(shell ) instead of `` to get embedded libperl's ccopts
  tools build: Filter out options and warnings not supported by clang
  perf python: Fix probing for some clang command line options
  perf build: Don't use -ffat-lto-objects in the python feature test when 
building with clang-13
  Revert "nbd: fix possible overflow on 'first_minor' in nbd_dev_add()"
  SUNRPC: Don't call connect() more than once on a TCP socket
  rtc: mc146818-lib: fix signedness bug in mc146818_get_time()
  selftests/bpf: Fix u8 narrow load checks for bpf_sk_lookup remote_port
  bpf: Make remote_port field in struct bpf_sk_lookup 16-bit wide
  Revert "selftests: net: Add tls config dependency for tls selftests"
  net/smc: send directly on setting TCP_NODELAY
  KVM: SVM: Allow AVIC support on system w/ physical APIC ID > 255
  drm/amdgpu: don't use BACO for reset in S3
  drm/amdkfd: Create file descriptor after client is added to smi_clients list
  drm/nouveau/pmu: Add missing callbacks for Tegra devices
  drm/amdgpu/vcn: Fix the register setting for vcn1
  drm/amdgpu/smu10: fix SoC/fclk units in auto mode
  drm/amdgpu/display: change pipe policy for DCN 2.1
  drm/panel: ili9341: fix optional regulator handling
  SUNRPC: Prevent immediate close+reconnect
  amd/display: set backlight only if required
  fbdev: Fix unregistering of framebuffers without device
  irqchip/gic-v3: Fix GICR_CTLR.RWP polling
  perf/core: Inherit event_caps
  perf: qcom_l2_pmu: fix an incorrect NULL check on list iterator
  ata: sata_dwc_460ex: Fix crash due to OOB write
  perf/x86/intel: Don't extend the pseudo-encoding to GP counters
  x86/mm/tlb: Revert retpoline avoidance approach
  x86/msi: Fix msi message data shadow struct
  gpio: Restrict usage of GPIO chip irq members before initialization
  RDMA/hfi1: Fix use-after-free bug for mm struct
  arm64: patch_text: Fixup last cpu should be master
  spi: core: add dma_map_dev for __spi_unmap_msg()
  btrfs: prevent subvol with swapfile from being deleted
  btrfs: fix qgroup reserve overflow the qgroup limit
  perf/x86/intel: Update the FRONTEND MSR mask on Sapphire Rapids
  x86/speculation: Restore speculation related MSRs during S3 resume
  x86/pm: Save the MSR validity status at context setup
  io_uring: fix race between timeout flush and removal
  io_uring: implement compat handling for IORING_REGISTER_IOWQ_AFF
  io_uring: defer splice/tee file validity check until command issue
  io_uring: don't check req->file in io_fsync_prep()
  mm/mempolicy: fix mpol_new leak in shared_policy_replace
  mmmremap.c: avoid pointless invalidate_range_start/end on 

[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container

[Stefan Bader]

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

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

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

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

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

Title:
  linux-image-5.0.0-35-generic breaks checkpointing of container

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Eoan:
  Won't Fix
Status in linux-azure source package in Eoan:
  New
Status in linux source package in Focal:
  Fix Released
Status in linux-azure source package in Focal:
  New
Status in linux source package in Groovy:
  Fix Released
Status in linux-azure source package in Groovy:
  New
Status in linux source package in Hirsute:
  Fix Released
Status in linux-azure source package in Hirsute:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in linux-azure source package in Jammy:
  New

Bug description:
  Trying to checkpoint a container (docker/podman) on 18.04 fails
  starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see
  this in Travis starting a few weeks ago. Manually testing it locally
  shows that linux-image-5.0.0-32-generic still works and linux-
  image-5.0.0-35-generic does not longer work. It seems to be overlayfs
  related, at least that is what we believe. The CRIU error message we
  see is:

  (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 
path=/bin/busybox
  (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed 
with -1

  
  We have not seen this only in Travis, but also multiple CRIU users reported 
that bug already. Currently we have to tell them to downgrade the kernel.

  I also able to reproduce it with linux-image-5.3.0-24-generic. Staying
  on the 4.18.0 kernel series does not show this error.
  4.18.0-25-generic works without problems.

  See also https://github.com/checkpoint-restore/criu/issues/860

  One of the possible explanations from our side include:

  "Looks like we have the same as for st_dev now with mnt_id, that is
  bad, because we can't find on which mount to open the file if kernel
  hides these information from us."

  Running on the upstream 5.5.0-rc1 kernel does not show this error.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 18:52 seq
   crw-rw 1 root audio 116, 33 Jan  7 18:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 19.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: DigitalOcean Droplet
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20171212
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr:
  dmi.product.family: DigitalOcean_Droplet
  dmi.product.name: Droplet
  dmi.product.version: 20171212
  dmi.sys.vendor: DigitalOcean

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


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

[Kernel-packages] [Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering

[Stefan Bader]

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

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

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

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

Title:
  [Jammy, mlx5, ConnectX-7] add CX7 support for software steering

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

Bug description:
  [Impact]
  Add support for software steering on cx7

  [Test Case]
  configure software steering on cx7 setup
  run asap testing 
  (reference https://github.com/Mellanox/ovs-tests)
   

  [Regression Potential]
  TBD

  [Other Info]

  Feature patchset: 
  All patches are cleanly applied on Jamy master-next beside 
  these two who add minor conflicts due to context difference.
  net/mlx5: Introduce software defined steering capabilities
  net/mlx5: DR, Add support for matching on
   

  #fixes
  624bf42c2e39 net/mlx5: DR, Fix querying eswitch manager vport for ECPF
  0aec12d97b20 net/mlx5: DR, Fix slab-out-of-bounds in mlx5_cmd_dr_create_fte
  9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately

  
  #CX7 SMFS support
  6862c787c7e8 net/mlx5: DR, Add support for ConnectX-7 steering
  638a07f1090e net/mlx5: DR, Refactor ste_ctx handling for STE v0/1
  75a3926ca6a4 net/mlx5: DR, Rename action modify fields to reflect naming in 
HW spec
  bdc3ab5795a6 net/mlx5: DR, Fix handling of different actions on the same STE 
in STEv1
  11659ef8d28e net/mlx5: DR, Remove unneeded comments
  5c422bfad2fb net/mlx5: DR, Add support for matching on Internet Header Length 
(IHL)

  
  #dependencies:
  60dc0ef674ec net/mlx5: VLAN push on RX, pop on TX
  8348b71ccd92 net/mlx5: Introduce software defined steering capabilities

  #depencecies:
  #SW STEERING DEBUG DUMP
  aa36c94853b2 net/mlx5: Set SMFS as a default steering mode if device supports 
it
  4ff725e1d4ad net/mlx5: DR, Ignore modify TTL if device doesn't support it
  cc2295cd54e4 net/mlx5: DR, Improve steering for empty or RX/TX-only matchers
  f59464e257bd net/mlx5: DR, Add support for matching on 
geneve_tlv_option_0_exist field
  09753babaf46 net/mlx5: DR, Support matching on tunnel headers 0 and 1
  8c2b4fee9c4b net/mlx5: DR, Add misc5 to match_param structs
  0f2a6c3b9219 net/mlx5: Add misc5 flow table match parameters
  b54128275ef8 net/mlx5: DR, Warn on failure to destroy objects due to refcount
  e3a0f40b2f90 net/mlx5: DR, Add support for UPLINK destination type
  9222f0b27da2 net/mlx5: DR, Add support for dumping steering info
  7766c9b922fe net/mlx5: DR, Add missing reserved fields to dr_match_param
  89cdba3224f0 net/mlx5: DR, Add check for flex parser ID value
  08fac109f7bb net/mlx5: DR, Rename list field in matcher struct to list_node
  32e9bd585307 net/mlx5: DR, Remove unused struct member in matcher
  c3fb0e280b4c net/mlx5: DR, Fix lower case macro prefix "mlx5_" to "MLX5_"
  84dfac39c61f net/mlx5: DR, Fix error flow in creating matcher

  
  58a606dba708 net/mlx5: Introduce new uplink destination type

  455832d49666 net/mlx5: DR, Fix check for unsupported fields in match param
  9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately

  #SW STEERING SF
  515ce2ffa621 net/mlx5: DR, init_next_match only if needed
  5dde00a73048 net/mlx5: DR, Fix typo 'offeset' to 'offset'
  1ffd498901c1 net/mlx5: DR, Increase supported num of actions to 32
  11a45def2e19 net/mlx5: DR, Add support for SF vports
  c0e90fc2ccaa net/mlx5: DR, Support csum recalculation flow table on SFs
  ee1887fb7cdd net/mlx5: DR, Align error messages for failure to obtain vport 
caps
  dd4acb2a0954 net/mlx5: DR, Add missing query for vport 0
  7ae8ac9a5820 net/mlx5: DR, Replace local WIRE_PORT macro with the existing 
MLX5_VPORT_UPLINK
  f9f93bd55ca6 net/mlx5: DR, Fix vport number data type to u16
  c228dce26222 net/mlx5: DR, Fix code indentation in dr_ste_v1

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


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

[Kernel-packages] [Bug 1968861] Re: Support Cirrus audio codec configurations for Odin platform

[Stefan Bader]

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

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

Title:
  Support Cirrus audio codec configurations for Odin platform

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

Bug description:
  [Impact]
  CS8409 needs new configuration for Odin platform

  [Fix]
  Cirrus provides us 2 patches to add the support which are not in upstream yet
  ALSA: hda/cs8409: Add Speaker Playback Switch for Cyborg
  ALSA: hda/cs8409: Support new Odin Variants

  Below series of patch is required to be applied before these 2.
  https://lists.ubuntu.com/archives/kernel-team/2022-April/129223.html

  [Test]
  Verified on the target machine

  [Where problems could occur]
  The first commit only affects the new added Odin platform, and the second one 
do some modification for other platforms which is hard to know what may lead to.

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


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

[Kernel-packages] [Bug 1967986] Re: Fix ADL, WD22TB4, Dual monitors display resolution can't reach 4K 60hz

[Stefan Bader]

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

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

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

Title:
  Fix ADL, WD22TB4,Dual monitors display resolution can't reach 4K 60hz

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

Bug description:
  [Impact]
  SUT attach WD22TB4 dock, plug in two 4K monitor, the monitor resolution can't 
reach 4K 60Hz

  [Fix]
  Fix maximum DP source rate.

  this patch should be taken first,
  73867c8709) drm/i915/display: Remove check for low voltage sku for max dp 
source rate

  Then, on U/J/OEM-5.14, apply 3fd6afb623ba) drm/i915/intel_combo_phy:
  Print I/O voltage info,

  [Test Case]
  1. Connect two 4K external monitor to WD22TB4
  2. the monitor resolution can reach 4K 60Hz

  [Where problems could occur]
  Low

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


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

[Kernel-packages] [Bug 1967988] Re: Support different Cirrus audio codec configurations on Dell laptops

[Stefan Bader]

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

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

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

Title:
  Support different Cirrus audio codec configurations on Dell laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
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 Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  On Dell's platform, Warlock/Bullseye Laptops have a mono DMIC, Cyborg and 
some Warlock variants uses a stereo DMIC. They are not correctly mapped to the 
corresponding configurations so the microphone function are not working as 
expected.

  [Fix]
  Cirrus upstream new FIXUPs to support different microphone configurations on 
different Dell laptop variants.

  [Test Case]
  1. Go to Audio Settings
  2. Make sure the microphone is correctly detected and responds to audio input.
  3. Issue command "arecord record_file" and check the record_file is 
consistent with audio input.

  [Where problems could occur]
  Risk should be Low. The patches come from Cirrus and the configurations are 
mapped based on the audio codec's SSIDs for different Dell variants.

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


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

[Kernel-packages] [Bug 1967750] Re: Intel: enable x86 AMX

[Stefan Bader]

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

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Andrea Righi (arighi)

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

Title:
  Intel: enable x86 AMX

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

Bug description:
  [Impact]

  Enable AMX (aka TMUL) new instructions on the 5.15 kernel.

  [Test case]

  Tests have been performed directly by Intel.

  [Fix]

  Apply the following upstream commits:

  20df73756148 ("selftests/x86/amx: Update the ARCH_REQ_XCOMP_PERM test")
  063452fd94d1 ("x86/fpu/xstate: Fix the ARCH_REQ_XCOMP_PERM implementation")
  fa31a4d669bd ("x86/cpufeatures: Put the AMX macros in the word 18 block")
  6c3118c32129 ("signal: Skip the altstack update when not needed")
  52d0b8b18776 ("x86/fpu/signal: Initialize sw_bytes in save_xstate_epilog()")
  d7a9590f608d ("Documentation/x86: Add documentation for using dynamic XSTATE 
features")
  101c669d165d ("selftests/x86/amx: Add context switch test")
  6a3e0651b4a0 ("selftests/x86/amx: Add test cases for AMX state management")
  2308ee57d93d ("x86/fpu/amx: Enable the AMX feature in 64-bit mode")
  db3e7321b4b8 ("x86/fpu: Add XFD handling for dynamic states")
  2ae996e0c1a3 ("x86/fpu: Calculate the default sizes independently")
  eec2113eabd9 ("x86/fpu/amx: Define AMX state components and have it used for 
boot-time checks")
  70c3f1671b0c ("x86/fpu/xstate: Prepare XSAVE feature table for gaps in state 
component numbers")
  500afbf645a0 ("x86/fpu/xstate: Add fpstate_realloc()/free()")
  783e87b40495 ("x86/fpu/xstate: Add XFD #NM handler")
  672365477ae8 ("x86/fpu: Update XFD state where required")
  5529acf47ec3 ("x86/fpu: Add sanity checks for XFD")
  8bf26758ca96 ("x86/fpu: Add XFD state to fpstate")
  dae1bd583896 ("x86/msr-index: Add MSRs for XFD")
  c351101678ce ("x86/cpufeatures: Add eXtended Feature Disabling (XFD) feature 
bit")
  e61d6310a0f8 ("x86/fpu: Reset permission and fpstate on exec()")
  9e798e9aa14c ("x86/fpu: Prepare fpu_clone() for dynamically enabled features")
  53599b4d54b9 ("x86/fpu/signal: Prepare for variable sigframe length")
  4b7ca609a33d ("x86/signal: Use fpu::__state_user_size for sigalt stack 
validation")
  23686ef25d4a ("x86/fpu: Add basic helpers for dynamically enabled features")
  db8268df0983 ("x86/arch_prctl: Add controls for dynamic XSTATE components")
  c33f0a81a2cf ("x86/fpu: Add fpu_state_config::legacy_features")
  6f6a7c09c406 ("x86/fpu: Add members to struct fpu to cache permission 
information")
  84e4dccc8fce ("x86/fpu/xstate: Provide xstate_calculate_size()")
  3aac3ebea08f ("x86/signal: Implement sigaltstack size validation")
  1bdda24c4af6 ("signal: Add an optional check for altstack size")
  582b01b6ab27 ("x86/fpu: Remove old KVM FPU interface")
  d69c1382e1b7 ("x86/kvm: Convert FPU handling to a single swap buffer")
  69f6ed1d14c6 ("x86/fpu: Provide infrastructure for KVM FPU cleanup")
  75c52dad5e32 ("x86/fpu: Prepare for sanitizing KVM FPU code")
  d72c87018d00 ("x86/fpu/xstate: Move remaining xfeature helpers to core")
  eda32f4f93b4 ("x86/fpu: Rework restore_regs_from_fpstate()")
  daddee247319 ("x86/fpu: Mop up xfeatures_mask_uabi()")
  1c253ff2287f ("x86/fpu: Move xstate feature masks to fpu_*_cfg")
  2bd264bce238 ("x86/fpu: Move xstate size to fpu_*_cfg")
  cd9ae7617449 ("x86/fpu/xstate: Cleanup size calculations")
  617473acdfe4 ("x86/fpu: Cleanup fpu__init_system_xstate_size_legacy()")
  578971f4e228 ("x86/fpu: Provide struct fpu_config")
  5509cc78080d ("x86/fpu/signal: Use fpstate for size and features")
  49e4eb4125d5 ("x86/fpu/xstate: Use fpstate for copy_uabi_to_xstate()")
  3ac8d75778fc ("x86/fpu: Use fpstate in __copy_xstate_to_uabi_buf()")
  ad6ede407aae ("x86/fpu: Use fpstate in fpu_copy_kvm_uabi_to_fpstate()")
  0b2d39aa0357 ("x86/fpu/xstate: Use fpstate for xsave_to_user_sigframe()")
  073e627a4537 ("x86/fpu/xstate: Use fpstate for os_xsave()")
  be31dfdfd75b ("x86/fpu: Use fpstate::size")
  248452ce21ae ("x86/fpu: Add size and mask information to fpstate")
  2dd8eedc80b1 ("x86/process: Move arch_thread_struct_whitelist() out of line")
  f0cbc8b3cdf7 ("x86/fpu: Do not leak fpstate pointer on fork")
  2f27b5034244 ("x86/fpu: Remove fpu::state")
  63d6bdf36ce1 ("x86/math-emu: Convert to fpstate")
  c20942ce5128 ("x86/fpu/core: Convert to fpstate")
  7e049e8b7459 ("x86/fpu/signal: Convert to fpstate")
  caee31a36c33 ("x86/fpu/regset: Convert to fpstate")
  cceb496420fa ("x86/fpu: Convert tracing to fpstate")
  1c57572d754f ("x86/KVM: Convert to fpstate")
  087df48c298c ("x86/fpu: Replace KVMs xstate component clearing")
  18b3fa1ad15f ("x86/fpu: Convert 

[Kernel-packages] [Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes

[Stefan Bader]

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

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

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

Title:
  [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes

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

Bug description:
  Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04
  kernel. These patches got accepted by the upstream and please find the
  corresponding commit IDs as below:

  334ae6459aa3 scsi: mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning
  22754f7fbb40 scsi: mpi3mr: Bump driver version to 8.0.0.68.0
  d44b5fefb22e scsi: mpi3mr: Fix memory leaks
  21401408ddeb scsi: mpi3mr: Update the copyright year
  999224612724 scsi: mpi3mr: Fix reporting of actual data transfer size
  b3911ab3a76e scsi: mpi3mr: Fix cmnd getting marked as in use forever
  191a3ef58634 scsi: mpi3mr: Fix hibernation issue
  04b27e538d50 scsi: mpi3mr: Update MPI3 headers
  6d211f1d2635 scsi: mpi3mr: Fix printing of pending I/O count
  580e6742205e scsi: mpi3mr: Fix deadlock while canceling the fw event
  3bb3c24e268a scsi: mpi3mr: Fix formatting problems in some kernel-doc comments
  5867b8569e64 scsi: mpi3mr: Fix some spelling mistakes
  c77b1f8a8fae scsi: mpi3mr: Bump driver version to 8.0.0.61.0
  a91603a5d504 scsi: mpi3mr: Enhanced Task Management Support Reply handling
  c86651345ca5 scsi: mpi3mr: Use TM response codes from MPI3 headers
  afd3a5793fe2 scsi: mpi3mr: Add io_uring interface support in I/O-polled mode
  95cca8d5542a scsi: mpi3mr: Print cable mngnt and temp threshold events
  78b76a0768ef scsi: mpi3mr: Support Prepare for Reset event
  c1af985d27da scsi: mpi3mr: Add Event acknowledgment logic
  c5758fc72b92 scsi: mpi3mr: Gracefully handle online FW update operation
  b64845a7d403 scsi: mpi3mr: Detect async reset that occurred in firmware
  c0b00a931e5e scsi: mpi3mr: Add IOC reinit function
  fe6db6151565 scsi: mpi3mr: Handle offline FW activation in graceful manner
  59bd9cfe3fa0 scsi: mpi3mr: Code refactor of IOC init - part2
  e3605f65ef69 scsi: mpi3mr: Code refactor of IOC init - part1
  a6856cc4507b scsi: mpi3mr: Fault IOC when internal command gets timeout
  2ac794baaec9 scsi: mpi3mr: Display IOC firmware package version
  13fd7b1555b6 scsi: mpi3mr: Handle unaligned PLL in unmap cmnds
  4f08b9637f63 scsi: mpi3mr: Increase internal cmnds timeout to 60s
  ba68779a518d scsi: mpi3mr: Do access status validation before adding devices
  17d6b9cf89cf scsi: mpi3mr: Add support for PCIe Managed Switch SES device
  ec5ebd2c14a9 scsi: mpi3mr: Update MPI3 headers - part2
  d00ff7c31195 scsi: mpi3mr: Update MPI3 headers - part1
  fbaa9aa48bb4 scsi: mpi3mr: Don't reset IOC if cmnds flush with reset status
  a83ec831b24a scsi: mpi3mr: Replace spin_lock() with spin_lock_irqsave()
  9cf0666f34b1 scsi: mpi3mr: Add debug APIs based on logging_level bits
  30e99f05f8b1 scsi: mpi3mr: Use scnprintf() instead of snprintf()
  97e6ea6d7806 scsi: mpi3mr: Fix duplicate device entries when scanning through 
sysfs
  1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly
  76a4f7cc5973 scsi: mpi3mr: Clean up mpi3mr_print_ioc_info()
  92cc94adfce4 scsi: mpi3mr: Use the proper SCSI midlayer interfaces for PI
  69868c3b6939 scsi: mpi3mr: Use scsi_cmd_to_rq() instead of scsi_cmnd.request
  aa0dc6a73309 scsi: mpi3mr: Fix W=1 compilation warnings
  62e528b80d6b scsi: mpi3mr: Fix warnings reported by smatch
  a254eae30b45 scsi: mpi3mr: Fix error return code in mpi3mr_init_ioc()
  f9dc034d0402 scsi: mpi3mr: Fix missing unlock on error
  2938bedd0efa scsi: mpi3mr: Fix error handling in mpi3mr_setup_isr()
  d46bdecd9f3c scsi: mpi3mr: Delete unnecessary NULL check
  d3d61f9c8c2d scsi: mpi3mr: Fix a double free
  7b8a49881b01 scsi: mpi3mr: Fix fall-through warning for Clang
  9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints

  
  Thanks,
  Sumit

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


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

[Kernel-packages] [Bug 1969106] Re: Jammy update: v5.15.32 upstream stable release

[Stefan Bader]

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

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

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

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

Title:
  Jammy update: v5.15.32 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  
  Linux 5.15.32
  llc: only change llc->dev when bind() succeeds
  nds32: fix access_ok() checks in get/put_user
  m68k: fix access_ok for coldfire
  wcn36xx: Differentiate wcn3660 from wcn3620
  tpm: use try_get_ops() in tpm-space.c
  mac80211: fix potential double free on mesh join
  uaccess: fix integer overflow on access_ok()
  rcu: Don't deboost before reporting expedited quiescent state
  drm/virtio: Ensure that objs is not NULL in virtio_gpu_array_put_free()
  Revert "ath: add support for special 0x0 regulatory domain"
  Bluetooth: btusb: Add one more Bluetooth part for the Realtek RTL8852AE
  crypto: qat - disable registration of algorithms
  ACPI: video: Force backlight native for Clevo NL5xRU and NL5xNU
  ACPI: battery: Add device HID and quirk for Microsoft Surface Go 3
  ACPI / x86: Work around broken XSDT on Advantech DAC-BJ01 board
  netfilter: nf_tables: validate registers coming from userspace.
  netfilter: nf_tables: initialize registers in nft_do_chain()
  drivers: net: xgene: Fix regression in CRC stripping
  ALSA: pci: fix reading of swapped values from pcmreg in AC97 codec
  ALSA: cmipci: Restore aux vol on suspend/resume
  ALSA: usb-audio: Add mute TLV for playback volumes on RODE NT-USB
  ALSA: pcm: Add stream lock during PCM reset ioctl operations
  ALSA: pcm: Fix races among concurrent prealloc proc writes
  ALSA: pcm: Fix races among concurrent prepare and hw_params/hw_free calls
  ALSA: pcm: Fix races among concurrent read/write and buffer changes
  ALSA: pcm: Fix races among concurrent hw_params and hw_free calls
  ALSA: hda/realtek: Add quirk for ASUS GA402
  ALSA: hda/realtek - Fix headset mic problem for a HP machine with alc671
  ALSA: hda/realtek: Add quirk for Clevo NP50PNJ
  ALSA: hda/realtek: Add quirk for Clevo NP70PNJ
  ALSA: usb-audio: add mapping for new Corsair Virtuoso SE
  ALSA: oss: Fix PCM OSS buffer allocation overflow
  ASoC: sti: Fix deadlock via snd_pcm_stop_xrun() call
  llc: fix netdevice reference leaks in llc_ui_bind()
  Bluetooth: btusb: Add another Realtek 8761BU
  tpm: Fix error handling in async work
  net: ipv6: fix skb_over_panic in __ip6_append_data
  nfc: st21nfca: Fix potential buffer overflows in EVT_TRANSACTION

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


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

[Kernel-packages] [Bug 1969110] Re: Jammy update: v5.15.33 upstream stable release

[Stefan Bader]

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

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

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

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

Title:
  Jammy update: v5.15.33 upstream stable release

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

Bug description:
  SRU Justification

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

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

  Linux 5.15.33

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


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

[Kernel-packages] [Bug 1970603] [NEW] DSI touchscreen not working with KMS under 5.15

[Dave Jones]

Public bug reported:

The official Raspberry Pi touchscreen (the 7" model connected via the
DSI port) does not operate when the KMS overlay is applied (as is the
default on the Ubuntu Desktop for Raspberry Pi images). The display does
operate on RaspiOS Bullseye, also running kernel 5.15, when the KMS
overlay is used. Notably, the display does work on Ubuntu with no KMS
overlay (legacy framebuffer), or with the FKMS ("fake" KMS) overlay.

The symptom is simply no output at all on the display. Sometimes there
is the initial "rainbow" screen of the start4.elf bootloader, but then
nothing. Notably this is *slightly* different to the Impish 5.13 kernel.
On thata version, the DSI display also failed with the KMS overlay, but
in that case there was an initial flashing cursor (presumably at the
start of the initrd, perhaps on a leftover framebuffer?) which then
disappears before anything is printed. On 5.15 there's nothing after the
"rainbow".

The symptoms are the same on both armhf and arm64 images.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-raspi 5.15.0.1005.5
ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30
Uname: Linux 5.15.0-1005-raspi armv7l
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-1005-raspi.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82
Architecture: armhf
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: unknown
Date: Wed Apr 27 10:04:10 2022
ImageMediaBuild: 20220419
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 xHCI 
USB 3.0 Controller
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04d9:0006 Holtek Semiconductor, Inc. Wired Keyboard 
(78/79 key) [RPI Wired Keyboard 5]
 Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB:
 
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  
smsc95xx.macaddr=DC:A6:32:33:F5:57 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  console=ttyS0,115200 dwc_otg.lpm_enable=0 
console=tty1 root=LABEL=writable rootfstype=ext4 rootwait 
video=DSI-1:800x480@60,rotate=180 fixrtc quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-1005-raspi N/A
 linux-backports-modules-5.15.0-1005-raspi  N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux-raspi
StagingDrivers: bcm2835_v4l2 bcm2835_isp vc_sm_cma bcm2835_codec 
bcm2835_mmal_vchiq snd_bcm2835
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:

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


** Tags: apport-bug jammy raspi-image staging uec-images

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

Title:
  DSI touchscreen not working with KMS under 5.15

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  The official Raspberry Pi touchscreen (the 7" model connected via the
  DSI port) does not operate when the KMS overlay is applied (as is the
  default on the Ubuntu Desktop for Raspberry Pi images). The display
  does operate on RaspiOS Bullseye, also running kernel 5.15, when the
  KMS overlay is used. Notably, the display does work on Ubuntu with no
  KMS overlay (legacy framebuffer), or with the FKMS ("fake" KMS)
  overlay.

  The symptom is simply no output at all on the display. Sometimes there
  is the initial "rainbow" screen of the start4.elf bootloader, but then
  nothing. Notably this is *slightly* different to the Impish 5.13
  kernel. On thata version, the DSI display also failed with the KMS
  overlay, but in that case there was an initial flashing cursor
  (presumably at the start of the initrd, perhaps on a leftover
  framebuffer?) which then disappears before anything is printed. On
  5.15 there's nothing after the "rainbow".

  The symptoms are the same on both armhf and arm64 images.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-raspi 5.15.0.1005.5
  ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30
  Uname: Linux 5.15.0-1005-raspi armv7l
  AlsaVersion: Advanced Linux 

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

[Daniel van Vugt]

Keep it simple. Please start with only the AMD GPU.

If you have a laptop, just disconnect the external monitor.

If you have a desktop, just move the monitor connection to the
motherboard. You might have to also temporarily remove the Nvidia card
during that time or else the system will still prefer Nvidia even while
no monitor is connected to it.

Once you can use the machine with only AMD graphics, you can install the
Nvidia driver manually (even when no Nvidia card is installed):

  sudo apt install nvidia-driver-510

and reboot. Then it should be safe to go back to using Nvidia and multi-
monitors.

If you're installing Ubuntu from scratch then the shortcut to all this
is to choose the third-party software option during installation.

I am of course guessing that the problem is the nouveau driver and not
AMD...

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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


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

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

[tomeq_]

@Daniel - I wish I could but how I can do that, when the screen is
totally unreadable (click blindly around especially on 4K display? ;) )
and this is just live USB drive before any installation happening?

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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


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

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

[Daniel van Vugt]

Has anyone tried logging into a Wayland session to see if that avoids
the bug? On the login screen it will either be called 'Ubuntu on
Wayland' or just 'Ubuntu' if the only other option is 'Ubuntu on Xorg'.

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws-5.4/5.4.0.1073.55)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-aws-5.4 (5.4.0.1073.55) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

kpatch/0.5.0-0ubuntu1.1 (amd64)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
snapd/2.54.3+18.04.2ubuntu0.2 (amd64, arm64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-aws-5.4

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

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

[Daniel van Vugt]

I don't want to spend too much time on nouveau bugs when it has so many
known problems. So all Nvidia owners please open the 'Additional
Drivers' app and install the proprietary Nvidia driver from there.

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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


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

[Kernel-packages] [Bug 1968361] Re: rawsock test BUG: soft lockup

[Colin Ian King]

Work-aound committed to stress-ng:

commit 69328da97f04745a9da2890c90c131c2322f81e2 (HEAD -> master)
Author: Colin Ian King 
Date:   Wed Apr 27 08:49:12 2022 +

stress-rawsock: make client wait for server to start

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

Title:
  rawsock test BUG: soft lockup

Status in Linux:
  New
Status in Stress-ng:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  When running the rawsock stressor on large system with 32 CPUs and
  above, I always hit soft lockup in the kernel, and sometime it will
  lock up the system if running it for longtime. This issue is on all
  major OSes that I tested: Ubunutu 20.04. RHEL7,8, SUSE 15

  
  my system:
  stress-ng V0.13.03-5-g9093bce7

  #lscpu | grep CPU
  CPU(s):  64
  On-line CPU(s) list: 0-63
  NUMA node0 CPU(s):   0-63

  # ./stress-ng --rawsock 20 -t 5
  stress-ng: info:  [49748] setting to a 5 second run per stressor
  stress-ng: info:  [49748] dispatching hogs: 20 rawsock

  Message from syslogd@rain65 at Apr  8 12:18:26 ...
   kernel:watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [stress-ng:49781]
  

  If I run with --timeout 60 secs, it will lock up the systems.

  The issue is lock starvation in the kernel:
  - when stressor create an instance, forking a new child/client and 
parent/server processes, recreating sockets for these processes. The kernel 
acquires the Write lock for adding them to raw sock hash table.
  - the client process immediately starts sending data in a do while {} loop. 
The kernel acquires the Read Lock for accessing raw sock hash table, and 
cloning the data packets for all raw socket processes.
  - The main stress-ng process may still continue to create the rest of 
instances. The kernel may hit the lock starvation (as error shown above)
  - similar to it, when the timeout expires, the parents would try to close 
their sockets, which the kernel also try to acquire the Write Lock, before 
sending SIGKILL to their child processes. We may hit the lock starvation, since 
clients have not closed their sockets and continue sending data.

  I'm not sure this is intended, but to avoid the kernel lock starvation
  in raw socket, I propose the simple patch attached. I has tested it a
  large system with 128 CPUs without hitting any BUG: soft lock up.

  Thanks,
  Thinh Tran

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


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

[Kernel-packages] [Bug 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

[Pete Woods]

** Description changed:

  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.
  
  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their CI
  runs.
  
  Unfortunately they cannot run their tests on our AWS based VMs, as there
  is no sound support compiled into the kernel on the AWS kernel and
  images.
  
  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```
  
  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.
  
  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884
  
  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu
  
- again there. The reasoning for the removal appears to be in this commit:
+ again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

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

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

Status in linux-aws package in Ubuntu:
  New

Bug description:
  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.

  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their
  CI runs.

  Unfortunately they cannot run their tests on our AWS based VMs, as
  there is no sound support compiled into the kernel on the AWS kernel
  and images.

  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```

  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

  again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

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


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

[Kernel-packages] [Bug 1970586] [NEW] No sound support on Linux AWS kernel (but supported on GCP)

[Pete Woods]

Public bug reported:

In GCP images it is possible to create virtual MIDI devices and
generally do stuff like audio routing, etc.

At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
our customers use this functionality to test audio equipment in their CI
runs.

Unfortunately they cannot run their tests on our AWS based VMs, as there
is no sound support compiled into the kernel on the AWS kernel and
images.

See the package listings for the other kernels for, e.g. the loopback driver:
```
linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
```

We would love to be able to install the sound drivers (especially snd-
aloop) with the linux-modules-extra-aws package, but currently cannot,
and obviously do not want to start running our own kernels, as then we
lose the immediacy of kernel patches provided upstream by Canonical.

You can see the difference in the GCP:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

and AWS kernel:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

again there. The reasoning for the removal appears to be in this commit from 
2016:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

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

** Description changed:

  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.
  
  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their CI
  runs.
  
  Unfortunately they cannot run their tests on our AWS based VMs, as there
  is no sound support compiled into the kernel on the AWS kernel and
  images.
  
- See the package listings for, e.g. the loopback driver:
+ See the package listings for the other kernels for, e.g. the loopback driver:
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  
  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

** Description changed:

  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.
  
  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their CI
  runs.
  
  Unfortunately they cannot run their tests on our AWS based VMs, as there
  is no sound support compiled into the kernel on the AWS kernel and
  images.
  
  See the package listings for the other kernels for, e.g. the loopback driver:
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  
  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.
+ 
+ You can see the difference in the GCP:
+ 
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884
+ 
+ and AWS kernel:
+ 
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu
+ 
+ again there. The reasoning for the removal appears to be in this commit:
+ 
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

** Description changed:

  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.
  
  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their CI
  runs.
  
  Unfortunately they 

[Kernel-packages] [Bug 1970559] 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/1970559

Title:
  MacBook Air Mid-2013 not booting with iommu enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a MacBook Air Mid-2013 which doesn't boot with iommu enabled
  due to the onboard SATA not working with it, and I see that with
  KUbuntu 22.04, the new 5.15 kernels have Intel IOMMU enabled by
  default.  So at the moment I need to add kernel option:
  intel_iommu=off .  The MacBook was working with default boot options
  with KUbuntu 22.10 and kernel: 5.13.0-40-generic, but that also didn't
  have CONFIG_INTEL_IOMMU_DEFAULT_ON set.  I have attached the output of
  dmesg when the intel mmu is enabled if that helps.  Is there a patch
  that can be applied to fix this or perhaps a dmi whitelist to make it
  so intel mmu isn't enabled for this model?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.27.30
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  staples1028 F pulseaudio
   /dev/snd/controlC1:  staples1028 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Wed Apr 27 18:05:16 2022
  InstallationDate: Installed on 2021-08-19 (250 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Apple Inc. MacBookAir6,1
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=130dde04-85ad-4fcc-919c-1664e646e8df ro quiet splash 
intel_pstate=active intel_iommu=off
  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.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-26 (0 days ago)
  dmi.bios.date: 02/22/2021
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 431.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-35C1E88140C3E6CF
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-35C1E88140C3E6CF
  dmi.modalias: 
dmi:bvnAppleInc.:bvr431.0.0.0.0:bd02/22/2021:br0.1:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF:skuSystemSKU#:
  dmi.product.family: MacBook Air
  dmi.product.name: MacBookAir6,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

[Kernel-packages] [Bug 1970559] [NEW] MacBook Air Mid-2013 not booting with iommu enabled

[Matthew Stapleton]

Public bug reported:

I have a MacBook Air Mid-2013 which doesn't boot with iommu enabled due
to the onboard SATA not working with it, and I see that with KUbuntu
22.04, the new 5.15 kernels have Intel IOMMU enabled by default.  So at
the moment I need to add kernel option: intel_iommu=off .  The MacBook
was working with default boot options with KUbuntu 22.10 and kernel:
5.13.0-40-generic, but that also didn't have
CONFIG_INTEL_IOMMU_DEFAULT_ON set.  I have attached the output of dmesg
when the intel mmu is enabled if that helps.  Is there a patch that can
be applied to fix this or perhaps a dmi whitelist to make it so intel
mmu isn't enabled for this model?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-generic 5.15.0.27.30
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  staples1028 F pulseaudio
 /dev/snd/controlC1:  staples1028 F pulseaudio
CasperMD5CheckResult: unknown
Date: Wed Apr 27 18:05:16 2022
InstallationDate: Installed on 2021-08-19 (250 days ago)
InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Apple Inc. MacBookAir6,1
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=130dde04-85ad-4fcc-919c-1664e646e8df ro quiet splash 
intel_pstate=active intel_iommu=off
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.15.0-27-generic N/A
 linux-backports-modules-5.15.0-27-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-04-26 (0 days ago)
dmi.bios.date: 02/22/2021
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 431.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-35C1E88140C3E6CF
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir6,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-35C1E88140C3E6CF
dmi.modalias: 
dmi:bvnAppleInc.:bvr431.0.0.0.0:bd02/22/2021:br0.1:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF:skuSystemSKU#:
dmi.product.family: MacBook Air
dmi.product.name: MacBookAir6,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug jammy

** Attachment added: "dmesg_with_iommu"
   
https://bugs.launchpad.net/bugs/1970559/+attachment/5584286/+files/dmesg_with_iommu

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

Title:
  MacBook Air Mid-2013 not booting with iommu enabled

Status in linux package in Ubuntu:
  New

Bug description:
  I have a MacBook Air Mid-2013 which doesn't boot with iommu enabled
  due to the onboard SATA not working with it, and I see that with
  KUbuntu 22.04, the new 5.15 kernels have Intel IOMMU enabled by
  default.  So at the moment I need to add kernel option:
  intel_iommu=off .  The MacBook was working with default boot options
  with KUbuntu 22.10 and kernel: 5.13.0-40-generic, but that also didn't
  have CONFIG_INTEL_IOMMU_DEFAULT_ON set.  I have attached the output of
  dmesg when the intel mmu is enabled if that helps.  Is there a patch
  that can be applied to fix this or perhaps a dmi whitelist to make it
  so intel mmu isn't enabled for this model?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.27.30
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  staples1028 F pulseaudio
   /dev/snd/controlC1:  staples1028 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Wed Apr 27 18:05:16 2022
  InstallationDate: Installed on 2021-08-19 (250 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Apple Inc. MacBookAir6,1
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=130dde04-85ad-4fcc-919c-1664e646e8df ro quiet splash 
intel_pstate=active intel_iommu=off
  PulseList: Error: command ['pacmd', 'list'] failed with exit 

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

[tomeq_]

Same here - 
Nvidia 3060 Ti on AMD X570 platform
Panasonic 4K TV via HDMI cable.

While welcome screen is fine - the one with "Install" or "try ubuntu",
then the screen blink for a while then return with fluo-green-yellow
colorset. It is hard to read anything.

Re-inserting HDMI cable to force reset the link has no effect.

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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


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

[Kernel-packages] [Bug 1970552] 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 1970552

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

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

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

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

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

Title:
  Mute/mic LEDs no function on EliteBook G9 platfroms

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on
  1) HP EliteBook x360 830 G9
  2) HP EliteBook 830 G9
  3) HP EliteBook 840 G9
  4) HP EliteBook 860 G9
  5) HP EliteBook 840 Aero G9
  6) HP EliteBook x360 840 Aero G9

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

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


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

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

[Launchpad Bug Tracker]

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

** Changed in: mutter (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/1969959

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

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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


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

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

[Launchpad Bug Tracker]

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

** Changed in: xorg-server (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/1969959

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

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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


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

[Kernel-packages] [Bug 1970543] Re: Add missing inside-secure firmwares

[Juerg Haefliger]

** Summary changed:

- Add missing firmwares
+ Add missing inside-secure firmwares

** Description changed:

- TBD
+ [Impact]
+ 
+ Firmware files for the inside-secure safexcel driver/module are missing.
+ 
+ [Fix]
+ 
+ Don't remove inside-secure firmwares from the package.
+ 
+ [Where Problems Could Occur]
+ 
+ None expected. Keep shipping the blobs as before.
+ 
+ [Notes]
+ 
+ These firmwares were removed because the kernel doesn't reference them.
+ Which is a bug [1].
+ 
+ [1]
+ 
https://lore.kernel.org/lkml/20220427074351.391580-1-jue...@protonmail.com/T/#u

** Summary changed:

- Add missing inside-secure firmwares
+ Add missing inside-secure firmware

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

Title:
  Add missing inside-secure firmware

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  New

Bug description:
  [Impact]

  Firmware files for the inside-secure safexcel driver/module are
  missing.

  [Fix]

  Don't remove inside-secure firmwares from the package.

  [Where Problems Could Occur]

  None expected. Keep shipping the blobs as before.

  [Notes]

  These firmwares were removed because the kernel doesn't reference
  them. Which is a bug [1].

  [1]
  
https://lore.kernel.org/lkml/20220427074351.391580-1-jue...@protonmail.com/T/#u

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


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

[Kernel-packages] [Bug 1970552] Re: Mute/mic LEDs no function on EliteBook G9 platfroms

[Andy Chi]

** Tags added: oem-priority originate-from-1966012 stella

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

** Changed in: oem-priority
   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/1970552

Title:
  Mute/mic LEDs no function on EliteBook G9 platfroms

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on
  1) HP EliteBook x360 830 G9
  2) HP EliteBook 830 G9
  3) HP EliteBook 840 G9
  4) HP EliteBook 860 G9
  5) HP EliteBook 840 Aero G9
  6) HP EliteBook x360 840 Aero G9

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

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


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

[Kernel-packages] [Bug 1970555] [NEW] linux-tools-5.15.0-27-lowlatency clashes with linux-tools-5.15.0-27

[arturo]

Public bug reported:

After updating to ubuntu 22.04 I'm getting an error on linux-
tools-5.15.0-27-lowlatency trying to install
/usr/lib/libcpupower.so.5.15.0-27 which is already installed by linux-
tools-5.15.0-27.

The generic version of the package linux-tools-5.15.0-27-generic,
doesn't have that file and installs without problem but the lowlatency
version seems to erroneously pack that file which leads to a clash with
linux-tools-5.15.0-27.

This happens when a low latency kernel is installed without trying to
install anything else, just by updating the system.

The specific versions of the packages are:

linux-tools-5.15.0-27-lowlatency: 5.15.0-27.28
linux-tools-5.15.0-27:5.15.0-27.28

The generic version which works without problem is the same:


linux-tools-5.15.0-27-generic:5.15.0-27.28

** Affects: ubuntu
 Importance: Undecided
 Status: New

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

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

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

Title:
  linux-tools-5.15.0-27-lowlatency clashes with linux-tools-5.15.0-27

Status in Ubuntu:
  New
Status in linux-lowlatency package in Ubuntu:
  New

Bug description:
  After updating to ubuntu 22.04 I'm getting an error on linux-
  tools-5.15.0-27-lowlatency trying to install
  /usr/lib/libcpupower.so.5.15.0-27 which is already installed by linux-
  tools-5.15.0-27.

  The generic version of the package linux-tools-5.15.0-27-generic,
  doesn't have that file and installs without problem but the lowlatency
  version seems to erroneously pack that file which leads to a clash
  with linux-tools-5.15.0-27.

  This happens when a low latency kernel is installed without trying to
  install anything else, just by updating the system.

  The specific versions of the packages are:

  linux-tools-5.15.0-27-lowlatency: 5.15.0-27.28
  linux-tools-5.15.0-27:5.15.0-27.28

  The generic version which works without problem is the same:

  
  linux-tools-5.15.0-27-generic:5.15.0-27.28

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


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

[Kernel-packages] [Bug 1960777] Re: Bail out when USB port is stuck in reset loop

[Jesse Sung]

Set as verified based on the QA test result from the linked project.

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

Title:
  Bail out when USB port is stuck in reset loop

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

Bug description:
  [Impact]
  USB port stops working after unplug an USB device.

  [Fix]
  Commit c89686118c786a523eee3ef68ed38330319626d8 ("usb: core: Bail out when 
port is stuck in reset loop")

  [Test]
  Affected vendor confirmed the patch can fix the issue after numerous round of 
tests.

  [Where problems could occur]
  If there's any peculiar USB hub depends on the old (and buggy) behavior, this 
can potentially bring a regression to the hub.

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


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

[Kernel-packages] [Bug 1970552] [NEW] Mute/mic LEDs no function on EliteBook G9 platfroms

[Andy Chi]

Public bug reported:

[Impact]
The mic mute/audio mute LEDS are not work on
1) HP EliteBook x360 830 G9
2) HP EliteBook 830 G9
3) HP EliteBook 840 G9
4) HP EliteBook 860 G9
5) HP EliteBook 840 Aero G9
6) HP EliteBook x360 840 Aero G9

[Fix]
It needs the specific quirk for the hardware layout.
Thus, add the quirks to make it works.

[Test]
After applying the quirk, the audio/mic mute LEDs are working good.

[Where problems could occur]
If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

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

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

Title:
  Mute/mic LEDs no function on EliteBook G9 platfroms

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on
  1) HP EliteBook x360 830 G9
  2) HP EliteBook 830 G9
  3) HP EliteBook 840 G9
  4) HP EliteBook 860 G9
  5) HP EliteBook 840 Aero G9
  6) HP EliteBook x360 840 Aero G9

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

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


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

[Kernel-packages] [Bug 1963088] Re: Add support for TPM

[Stefan Bader]

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

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

** Changed in: linux-kvm (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-kvm (Ubuntu Jammy)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

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

Title:
  Add support for TPM

Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Jammy:
  In Progress

Bug description:
  LXD, libvirt, openstack support launching qemu-kvm instances with TIS
  and CRB tpm's passed through from the host.

  linux-kvm currently is configured without TCG_TPM meaning it doesn't
  allow loading TPM modules, nor does it support exposing measurements,
  and thus allowing to use TPM backed FDE.

  Update config to enable TCG_TPM and compile TIS and CRB tpm's as
  modules. This still keeps linux-kvm fairly minimal in size, and yet
  able to support modern measured boot.

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


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

[Kernel-packages] [Bug 1970543] [NEW] Add missing firmwares

[Juerg Haefliger]

Public bug reported:

TBD

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-firmware (Ubuntu Jammy)
 Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
 Status: New

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

** Changed in: linux-firmware (Ubuntu Jammy)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

** Changed in: linux-firmware (Ubuntu)
   Status: New => Invalid

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

Title:
  Add missing firmwares

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  New

Bug description:
  TBD

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


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

[Kernel-packages] [Bug 1970519] Re: Many errors on amd 570x with amdgpu driver during dvb watching

[toths...@gmail.com]

Abńd please also respect rpm max for this device...1700 rpm. I dont
know, why in linux doing on boot on maybe up 3000 rpm !!! very loud
booting time !

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

Title:
  Many errors on amd 570x with amdgpu driver during dvb watching

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please chceck this erros after run kaffeine with dvb-t on linux mint
  (and sometimes is many artefacts to time of freezing X.org after some
  minutes - only during dvb-t watching. In other time is all ok without
  errors in dmesg):

  Linux version 5.13.0-40-generic (buildd@ubuntu) (gcc (Ubuntu
  9.4.0-1ubuntu1~20.04.1) 9.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34)
  #45~20.04.1-Ubuntu SMP Mon Apr 4 09:38:31 UTC 2022 (Ubuntu
  5.13.0-40.45~20.04.1-generic 5.13.19)

  dmesg | grep -i amdgpu
  [1.143673] [drm] amdgpu kernel modesetting enabled.
  [1.143701] amdgpu: Ignoring ACPI CRAT on non-APU system
  [1.143703] amdgpu: Virtual CRAT table created for CPU
  [1.143707] amdgpu: Topology: Add CPU node
  [1.143739] fb0: switching to amdgpudrmfb from EFI VGA
  [1.143766] amdgpu :09:00.0: vgaarb: deactivate vga console
  [1.143784] amdgpu :09:00.0: enabling device (0006 -> 0007)
  [1.143829] amdgpu :09:00.0: amdgpu: Trusted Memory Zone (TMZ) feature 
not supported
  [1.143851] amdgpu :09:00.0: amdgpu: Fetched VBIOS from VFCT
  [1.143852] amdgpu: ATOM BIOS: 113-D00035-L01
  [1.143897] amdgpu :09:00.0: amdgpu: VRAM: 4096M 0x00F4 - 
0x00F4 (4096M used)
  [1.143898] amdgpu :09:00.0: amdgpu: GART: 256M 0x00FF - 
0x00FF0FFF
  [1.143919] [drm] amdgpu: 4096M of VRAM memory ready
  [1.143920] [drm] amdgpu: 4096M of GTT memory ready.
  [1.146620] amdgpu: hwmgr_sw_init smu backed is polaris10_smu
  [1.450125] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
  [1.450208] amdgpu: Virtual CRAT table created for GPU
  [1.450240] amdgpu: Topology: Add dGPU node [0x67df:0x1002]
  [1.450241] kfd kfd: amdgpu: added device 1002:67df
  [1.450242] amdgpu :09:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 9, 
active_cu_number 32
  [1.452030] fbcon: amdgpudrmfb (fb0) is primary device
  [1.452031] amdgpu :09:00.0: [drm] fb0: amdgpudrmfb frame buffer device
  [1.464169] [drm] Initialized amdgpu 3.41.0 20150101 for :09:00.0 on 
minor 0
  [6.390938] snd_hda_intel :09:00.1: bound :09:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])
  [   74.758702] amdgpu :09:00.0: amdgpu: GPU fault detected: 146 
0x0512ba14 for process kaffeine pid 3252 thread kaffeine:cs0 pid 3264
  [   74.758709] amdgpu :09:00.0: amdgpu:   
VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001018A2
  [   74.758711] amdgpu :09:00.0: amdgpu:   
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x050BA014
  [   74.758712] amdgpu :09:00.0: amdgpu: VM fault (0x14, vmid 2, pasid 
32772) at page 1054882, write from 'UVD' (0x55564400) (186)
  ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  attila 2384 F pulseaudio
   /dev/snd/pcmC1D0p:   attila 2384 F...m pulseaudio
   /dev/snd/controlC0:  attila 2384 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Linux Mint 20.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-01-03 (113 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20211209
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic 
root=UUID=94607ee3-fa29-4732-a8d0-ef6429ff2c41 ro quiet splash 
acpi_enforce_resources=lax
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-40-generic N/A
   linux-backports-modules-5.13.0-40-generic  N/A
   linux-firmware 1.190.2~mesarc0
  Tags:  una
  Uname: Linux 5.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/25/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2604
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING B550M-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws-5.4/5.4.0-1073.78~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-aws-5.4 
(5.4.0-1073.78~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.147-0ubuntu0.18.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-restricted-modules-aws-5.4

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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