[Kernel-packages] [Bug 1992468] Re: segfault in ld-linux-x86-64.so

[Pete Lomax]

** Bug watch added: Sourceware.org Bugzilla #29456
   https://sourceware.org/bugzilla/show_bug.cgi?id=29456

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

Title:
  segfault in ld-linux-x86-64.so

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My manually built elf x64 file has started crashing on load, within the last 
month or so.
  It worked fine on Ubuntu 20.04.x, but fails on 22.04 - same problem on Mint 
19.3 and Fedora 36.

  dmesg ... gives this:

  [ 107.121214] p[4370]: segfault at 0 ip 7f3d725b8350 sp 7ffea111fba0 
error 4 in ld-linux-x86-64.so.2[7f3d72598000+2a000]
  [ 107.121230] Code: ff ff 00 45 31 db 48 8d 15 c9 ac 00 00 4c 8d 05 46 8f 01 
00 4c 8d 2d 1f 8f 01 00 49 89 c2 48 8d 58 ff 48 89 f8 49 f7 da 66 90 <8b> 08 83 
f9 07 77 19 85 c9 74 45 83 f9 07 77 40 48 63 0c 8a 48 01

  You can download the offending file (a single plain 4MB ELF x64) from
  http://phix.x10.mx/p64

  It almost certainly contains older/rarer forms of relocations and suchlike, 
but 
  only about ten or so and meant to be as simple as possible.

  If I need to change the binary content of that file, I can, but might
  need a wee bit of help.

  Of course, if/once it gets through ld-linux-x86-64.so and complains
  about something else, ignore it, or should you be at all intrigued you
  can visit http://phix.x10.mx/download.php to get the full package.

  References, just in case you need them, or to ask a wider set than just me 
for more details direct:
  https://openeuphoria.org/forum/136972.wc?last_id=136973
  https://github.com/petelomax/Phix/issues/13

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


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

[Kernel-packages] [Bug 1989334] Re: remove circular dep between linux-image and modules

[Launchpad Bug Tracker]

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

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

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

Title:
  remove circular dep between linux-image and modules

Status in linux package in Ubuntu:
  Expired

Bug description:
  remove circular dep between linux-image and modules

  Currently we have circular dependencies between linux-image and linux-
  modules/linux-modules-extra packages.

  This is redundant, and harmful when additional types of linux-images
  are provided (i.e. kernel.efi).

  Break the circular dependency by only keeping linux-image -> linux-
  modules dep, remove linux-modules -> linux-image dep, remove linux-
  modules-extra -> linux-image dep, add linux-modules-extra -> linux-
  modules dep.

  this is now applied in kinetic:linux, next need to apply to this to
  derivative kernels, and then we can roll it out to jammy too.

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


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

[Kernel-packages] [Bug 1989340] Re: installation crashes on a brand new VM on a brand new server

[Launchpad Bug Tracker]

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

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

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

Title:
  installation crashes on a brand new VM on a brand new server

Status in linux package in Ubuntu:
  Expired

Bug description:
  Installation of Ubuntu 22.04 crashed on a VMware VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity 22.04.17
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 12 14:24:17 2022
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[Drew R.]

Ok... So, I had previously done those steps 1 through 8.  On top of those 
however, since I had followed the instructions from that link 
(https://forum.manjaro.org/t/howto-set-up-the-audio-card-in-samsung-galaxy-book/37090),
 I had also added on top:
options snd slots=snd_soc_skl_hda_dsp
blacklist snd_hda_intel
as well as (for good measure, or in desperation rather):
options snd-hda-intel model=alc298-samsung-headphone
options snd-hda-intel model=alc298-spk-volume

So, I just removed those extras, to be sure I'm exactly as you.  Also,
to be sure the TO912.sh script is being called by those services, I put
a 'touch' command at the end of the script, so it creates a file so I'm
sure it ran.  Still no go... but I am determined.  I assume there is
only one version of that TO912 script, right?

As far as your lspci output, thank you for that.  It really helps to have 
something to compare it to.
My output was (changing the grep a little for more info): 

 00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P 
High Definition Audio Controller (rev 01)
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

So that is different than yours, but that's when I had "dsp_driver=1".
I took that option back out, to be 100% in line, and now it's the same
as your output ("sof-audio-pci-intel-tgl").  (And, taking that
dsp_driver=1 out also restores the microphone working)  - But, still no
go.  This was all on kernel 6.0, but I also tried 5.17, same result
(rebooting between all tests).

This is really strange, since we both have book2 pros.  My only
difference is the dedicated Arc graphics model (which I only got because
I wanted 32gb ram).  It comes with an HDMI port, does yours?  (Part of
me wonders if that plays a role in this).

In the beginning, I too went down the QEMU route.  It seemed extreme,
but hopefully full proof if I could get through it (since its gonna
mimic whatever windows does).  But, at least in the blog post I
followed, it had me download a custom qemu build, which then wouldn't
compile, and I got stuck in the rabbit hole of trying to figure out its
compilation errors (maybe it was an old build).

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, 

[Kernel-packages] [Bug 1889968] Re: [regression] Changed CONFIG_SATA_MOBILE_LPM_POLICY=3 default causes I/O errors

[Launchpad Bug Tracker]

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

** Changed in: linux-signed-hwe-5.4 (Ubuntu)
   Status: New => Confirmed

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

Title:
  [regression] Changed CONFIG_SATA_MOBILE_LPM_POLICY=3 default causes
  I/O errors

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

Bug description:
  Somewhere between 4.15.0-112-generic and 5.3.0-62-generic the kernel
  config option SATA_MOBILE_LPM_POLICY was changed from 0 (the upstream
  default) to 3. This is causing frequent SATA link resets, resulting in
  I/O stalls and errors. For example:

  ata1.00: exception Emask 0x0 SAct 0xdc SErr 0x5 action 0x6 frozen
  ata1: SError: { PHYRdyChg CommWake }
  ata1.00: failed command: WRITE FPDMA QUEUED
  ata1.00: cmd 61/20:90:d8:62:c6/00:00:24:00:00/40 tag 18 ncq dma 16384 out
   res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  ata1.00: status: { DRDY }
  ata1.00: failed command: READ FPDMA QUEUED
  ata1.00: cmd 60/20:98:60:26:1e/00:00:00:00:00/40 tag 19 ncq dma 16384 in
   res 40/00:01:06:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
  ata1.00: status: { DRDY }
  ata1.00: failed command: WRITE FPDMA QUEUED
  ata1.00: cmd 61/08:a0:78:85:11/00:00:03:00:00/40 tag 20 ncq dma 4096 out
   res 40/00:00:00:4f:c2/00:01:00:00:00/00 Emask 0x4 (timeout)
  ata1.00: status: { DRDY }
  ata1.00: failed command: WRITE FPDMA QUEUED
  ata1.00: cmd 61/10:b0:80:60:c6/00:00:24:00:00/40 tag 22 ncq dma 8192 out
   res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  ata1.00: status: { DRDY }
  ata1.00: failed command: READ FPDMA QUEUED
  ata1.00: cmd 60/08:b8:d0:13:ac/00:00:02:00:00/40 tag 23 ncq dma 4096 in
   res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
  ata1.00: status: { DRDY }
  ata1: hard resetting link
  ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  ata1.00: configured for UDMA/100
  ata1.00: device reported invalid CHS sector 0
  ata1.00: device reported invalid CHS sector 0
  sd 0:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  sd 0:0:0:0: [sda] tag#23 Sense Key : Illegal Request [current] 
  sd 0:0:0:0: [sda] tag#23 Add. Sense: Unaligned write command
  sd 0:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 02 ac 13 d0 00 00 08 00
  blk_update_request: I/O error, dev sda, sector 44831696 op 0x0:(READ) flags 
0x80700 phys_seg 1 prio class 0
  ata1: EH complete

  Available workarounds:

  1) downgrading to 4.15.0-*-generic
  2) appending 'ahci.mobile_lpm_policy=n' to the kernel command line, where 'n' 
is either 0, 1 or 2.

  The meanings of policy numbers can be found at
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/ata/Kconfig?h=v5.8-rc7#n118:

0 => Keep firmware settings
1 => Maximum performance
2 => Medium power
3 => Medium power with Device Initiated PM enabled
4 => Minimum power

  The computer in question is an Intel NUC DN2820FYK (running the latest
  system firmware version), containing an embedded Intel Corporation
  Atom Processor E3800 Series SATA AHCI Controller (rev 0e) controller.
  The hard drive is a HITACHI HTS723232L9SA60.

  I have confirmed that the issue persists in the latest mainline kernel
  build (5.8.0-050800rc7-generic).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  Date: Sat Aug  1 10:51:29 2020
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: Upgraded to bionic on 2020-06-28 (33 days ago)

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


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

[Kernel-packages] [Bug 1993563] Re: support for same series backports versioning numbers

[Kleber Sacilotto de Souza]

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

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

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

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

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

Title:
  support for same series backports versioning numbers

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

Bug description:
  packaging support for sameport versioning numbers

  Allow generating kernel packages, that use backports mechanism within
  the same series. For example linux-lowlatancy linux-riscv.

  Those kernels already have customized packaging to achieve the above,
  this is introducing standard support for this in the main kernels for
  jammy and kinetic series.

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


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

[Kernel-packages] [Bug 1995320] Re: [amdgpu] intermittent green static

[Kai Groner]

Updating to report I've been running the 5.15 kernel for a week without
seeing the green static return.

I've been combing some upstream bug trackers for similar issues and came across
https://gitlab.freedesktop.org/drm/amd/-/issues/2010
which migrated to
https://gitlab.freedesktop.org/mesa/mesa/-/issues/6456
and was resolved by
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/18494

The videos show similar effects, but more colorful and they attribute
the problem to gtk applications specifically. Nevertheless it does occur
with the hardware I am using.

This fix does not appear in any releases prior to mesa-22.3.0 rc1.

I may give ppa:oibaf/graphics-drivers a try to see if it improves
things.

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2010
   https://gitlab.freedesktop.org/drm/amd/-/issues/2010

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #6456
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/6456

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

Title:
  [amdgpu] intermittent green static

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 22.04 to 22.10 I've been seeing some display
  glitches.

  - green static appears, usually when scrolling, regular sized green blocks, 
like giant pixels
  - firefox not refreshing when full screen video plays (separate windows, 
separate screens)

  I would guess I probably have the wrong package here, but there's no
  way for me to tell if it's mesa, the kernel, gnome-shell, or something
  else.

  Radeon 6700XT
  Dual displays
  Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 31 21:46:03 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1231 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2019-06-18 (1232 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic 
root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic wayland-session
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.90
  dmi.board.name: B450M Steel Legend
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 1995957] Re: Add cs35l41 firmware loading support

[Kleber Sacilotto de Souza]

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

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

Title:
  Add cs35l41 firmware loading support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Confirmed
Status in linux-oem-5.17 source package in Jammy:
  Confirmed
Status in linux-oem-6.0 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Confirmed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Speakers on some laptops are rather quiet even with max volume.

  [Fix]
  Loading firmware to make cs35l41 speaker amplifier really work.

  [Test]
  With the fix applied, the speaker has become really loud as intended.

  [Where problems could occur]
  Most commits are refactoring codes on both ASoC and HDA parts, so things
  can be missed.

  Other than that, the change is strictly limited to cs35l41, so the
  regression scope is rather narrow.

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


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

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

[Clement Cherlin]

apport information

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

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

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


-- 
Mailing 

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

[Clement Cherlin]

apport information

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

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

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

[Clement Cherlin]

apport information

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

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

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

[Clement Cherlin]

apport information

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

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

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

[Clement Cherlin]

apport information

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

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

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

[Clement Cherlin]

apport information

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

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

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

[Clement Cherlin]

apport information

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

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

[Kernel-packages] [Bug 1996112] PaInfo.txt

[Clement Cherlin]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1996112/+attachment/5630620/+files/PaInfo.txt

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

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

[Clement Cherlin]

apport information

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

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

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

[Clement Cherlin]

apport information

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

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

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

[Clement Cherlin]

apport information

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

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

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

[Clement Cherlin]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1996112/+attachment/5630616/+files/IwConfig.txt

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

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

[Clement Cherlin]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1996112/+attachment/5630614/+files/CRDA.txt

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

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

[Clement Cherlin]

apport information

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

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users running
  virtualized Linux would not need to install the drivers for real
  hardware in linux-modules-extra.

  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.

  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.

  A previous kernel (5.15) had the modules in linux-modules:

  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  The current kernel (5.19) has the modules in linux-modules-extra:

  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $

  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   2582 F wireplumber
   /dev/snd/seq:ccherlin   2580 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-05 (675 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware N/A
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

[Kernel-packages] [Bug 1996112] Re: Virtual GPU driver packaging regression

[Clement Cherlin]

apport information

** Tags added: apport-collected kinetic

** Description changed:

  Several virtual machine GPU drivers were moved from linux-modules-extra
  to linux-modules in bug #1960633 so that users running virtualized Linux
  would not need to install the drivers for real hardware in linux-
  modules-extra.
  
  linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these
  drivers, but linux-modules-extra-5.19.0-23-generic does. This is a
  regression.
  
  Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was
  limited to sub-HD resolutions until I installed linux-modules-
  extra-5.19.0-23-generic.
  
  A previous kernel (5.15) had the modules in linux-modules:
  
  $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  
  $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $
  
  The current kernel (5.19) has the modules in linux-modules-extra:
  
  $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  $
  
  $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 
'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko'
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
  /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.23.1-0ubuntu3
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ccherlin   2582 F wireplumber
+  /dev/snd/seq:ccherlin   2580 F pipewire
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.10
+ InstallationDate: Installed on 2021-01-05 (675 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ Lsusb:
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
+  Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ Lsusb-t:
+  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
+  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
+  |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
+ MachineType: VMware, Inc. VMware Virtual Platform
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=screen-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 svgadrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
+ ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-5.19.0-23-generic N/A
+  linux-backports-modules-5.19.0-23-generic  N/A
+  linux-firmware N/A
+ RfKill:
+  
+ Tags:  kinetic
+ Uname: Linux 5.19.0-23-generic x86_64
+ UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/12/2020
+ dmi.bios.release: 4.6
+ dmi.bios.vendor: Phoenix Technologies LTD
+ dmi.bios.version: 6.00
+ dmi.board.name: 440BX Desktop Reference Platform
+ dmi.board.vendor: Intel Corporation
+ dmi.board.version: None
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: No Enclosure
+ dmi.chassis.version: N/A
+ dmi.ec.firmware.release: 0.0
+ dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
+ dmi.product.name: VMware Virtual Platform
+ dmi.product.version: None
+ dmi.sys.vendor: VMware, Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1996112/+attachment/5630613/+files/AlsaInfo.txt

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

Title:
  Virtual GPU driver packaging regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several virtual machine GPU drivers were moved from linux-modules-
  extra to linux-modules in bug #1960633 so that users 

[Kernel-packages] [Bug 1990272] Re: PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0], AER UnsupReq

[Bjorn Helgaas]

The Unsupported Request errors look like the same issue as
https://bugzilla.kernel.org/show_bug.cgi?id=215453 and should be
resolved by https://git.kernel.org/linus/c01163dbd1b8 ("PCI/PM: Always
disable PTM for all devices during suspend"), which appeared in
v6.1-rc1.

I don't know whether the NIC and USB drive issues are related.

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

Title:
  PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0],AER
  UnsupReq

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dmesg is getting spammed by these AER errors. The laptop (Lenovo X1
  Extreme Gen 5, Intel Core i7-12700H) is otherwise working fine.

  The errors come in random waves of 60..160 back-to-back errors with an
  interval of 130..140 microseconds.

  Device [8086:51b0] is the PCI/thunderbolt bridge.

  [   20.086628] pcieport :00:1d.0: AER: Uncorrected (Non-Fatal) error 
received: :00:1d.0
  [   20.086671] pcieport :00:1d.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [   20.086680] pcieport :00:1d.0:   device [8086:51b0] error 
status/mask=0010/4000
  [   20.086688] pcieport :00:1d.0:[20] UnsupReq   (First)
  [   20.086694] pcieport :00:1d.0: AER:   TLP Header: 3400 2052 
 
  [   20.086810] thunderbolt :22:00.0: AER: can't recover (no 
error_detected callback)
  [   20.086846] xhci_hcd :56:00.0: AER: can't recover (no error_detected 
callback)
  [   20.086878] pcieport :00:1d.0: AER: device recovery failed
  [   20.106033] pcieport :00:1d.0: AER: Multiple Uncorrected (Non-Fatal) 
error received: :00:1d.0
  [   20.106082] pcieport :00:1d.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [   20.106093] pcieport :00:1d.0:   device [8086:51b0] error 
status/mask=0010/4000
  [   20.106101] pcieport :00:1d.0:[20] UnsupReq   (First)
  [   20.106108] pcieport :00:1d.0: AER:   TLP Header: 3400 2052 
 
  [   20.106219] thunderbolt :22:00.0: AER: can't recover (no 
error_detected callback)
  [   20.106257] xhci_hcd :56:00.0: AER: can't recover (no error_detected 
callback)
  [   20.106301] pcieport :00:1d.0: AER: device recovery failed

  Another wave was at 418s, 440s, 1168s, etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-48-generic 5.15.0-48.54
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  me 1827 F pulseaudio
   /dev/snd/controlC0:  me 1827 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Sep 20 13:34:43 2022
  InstallationDate: Installed on 2022-08-31 (19 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 21DE001QMH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=d4a7fdda-30e3-439b-b327-e87d7b2bc81e ro
  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-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2022
  dmi.bios.release: 1.8
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3JET24W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21DE001QMH
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3JET24W(1.08):bd07/21/2022:br1.8:efr1.5:svnLENOVO:pn21DE001QMH:pvrThinkPadX1ExtremeGen5:rvnLENOVO:rn21DE001QMH:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21DE_BU_Think_FM_ThinkPadX1ExtremeGen5:
  dmi.product.family: ThinkPad X1 Extreme Gen 5
  dmi.product.name: 21DE001QMH
  dmi.product.sku: LENOVO_MT_21DE_BU_Think_FM_ThinkPad X1 Extreme Gen 5
  dmi.product.version: ThinkPad X1 Extreme Gen 5
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)

[Kleber Sacilotto de Souza]

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

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

Title:
   Fibocom WWAN FM350-GL suspend error (notebook not suspend)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Fibocom WWAN FM350-GL equipped platform fails to suspend.

  [Fix]

  Full t7xx driver is still under development and some of them have
  already accepted and merged in mainline kernel. The following commits
  are once in the mainline and are reverted in v6.0:

    d20ef656f994 net: wwan: t7xx: Add AP CLDMA
    007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration
    140424d90165 net: wwan: t7xx: PCIe reset rescan
    87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and
     coredump collection

  The first patch implemented the other AP-CLDMA, and with that applied,
  platforms in question may suspend and resume normally as every bits are in 
position.

  However, while these patches had been reverted for another revision
  that is still being worked on by the hardware vendor, a minimum,
  sauced patch is created to work-around this first to meet project
  schedules, and will be reverted and superseded with a final, mainline
  landing revision.

  [Test Case]

  Trigger suspend and there should be no more suspend errors from t7xx:

    mtk_t7xx :58:00.0: [PM] SAP suspend error: -110
    mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 
[mtk_t7xx] returns -110
    mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 
returns -110
    mtk_t7xx :58:00.0: PM: failed to suspend async: error -110

  [Where problems could occur]

  The t7xx driver is still incomplete and we're staging aforementioned 4
  patches in internal experimental kernels for development use.

  [Other Info]

  This affects Kinetic and above, so only Unstable, Kinetic and OEM-6.0
  are nominated for fix.

  == original bug report ==

  Hi,
  I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module 
mtk_t7xx . Power management for this modem is bad. When the notebook goes to 
sleep/suspend, kernel module mtk_t7xx return an error:

  mtk_t7xx :58:00.0: [PM] SAP suspend error: -110
  mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 
[mtk_t7xx] returns -110
  mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 
returns -110
  mtk_t7xx :58:00.0: PM: failed to suspend async: error -110

  So power management failed to suspend:
  PM: Some devices failed to suspend, or early wake event detected

  And the notebook not suspend and wake up again.
  It must be this module, because if I remove the module first (modprobe -r), 
the laptop goes to sleep and wakes up normally.
  However, after reinserting the module, the modem no longer appears in the 
system.

  Expected state: sleep occurs when the device is put to sleep -
  including the modem. When you wake up, you will wake up, including
  activating the modem and logging into the operator's network.

  Description:Ubuntu 20.04.5 LTS
  Release:20.04

  lspci -v:
  58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01)
  Subsystem: Device 1cf8:3500
  Flags: bus master, fast devsel, latency 0, IRQ 17
  Memory at 601e80 (64-bit, prefetchable) [size=32K]
  Memory at 5e80 (64-bit, non-prefetchable) [size=8M]
  Memory at 601e00 (64-bit, prefetchable) [size=8M]
  Capabilities: [80] Express Endpoint, MSI 00
  Capabilities: [d0] MSI-X: Enable+ Count=34 Masked-
  Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
  Capabilities: [f8] Power Management version 3
  Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 
Len=008 
  Capabilities: [108] Latency Tolerance Reporting
  Capabilities: [110] L1 PM Substates
  Capabilities: [200] Advanced Error Reporting
  Capabilities: [300] Secondary PCI Express
  Kernel driver in use: mtk_t7xx
  Kernel modules: mtk_t7xx

  lshw:
  *-generic
  description: Wireless controller
  product: MEDIATEK Corp.
  vendor: MEDIATEK Corp.
  physical id: 0
  bus info: pci@:58:00.0
     

[Kernel-packages] [Bug 1950792] Re: No boot possible - Cannot open root device

[Stefan Fleischmann]

Happy to provide more info/logs/whatever if you can tell me where to
look ;-)

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

Title:
  No boot possible - Cannot open root device

Status in MAAS:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MaaS cannot boot on my X11DPi-NT and will therefore fail to
  commission. It will instantly fail after grub.

  It will fail to boot saying that is not able to open root device. I
  even tried supplying the squashfs via python on a different port as
  the url is somehow cut off a bit, but to no avail. The python
  webserver doesn't even see any connection try.

  ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs
  python webserver: python3 -m http.server 8080)

  Steps to reproduce:

  1. Setup maas ;)
  2. Try to commision server
  3. See the kernel and initrd download fly by 
  4. Boom kernel panic

  Hardware:
  Supermicro X11DPi-NT with UEFI http Networkboot enabled
  NIC: Intel X722

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


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

[Kernel-packages] [Bug 1995573] Re: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Kinetic)
   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.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1995573

Title:
  Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Screen cannot turn on after screen is off

  [Fix]
  Below commit from v6.0-rc1 fixes the issue
  c577b2f43e80 drm/mgag200: Enable atomic gamma lut update

  And applied some other commits to fix the conflicts
  c48a36301634 drm/mgag200: Optimize damage clips
  3064debaf55e drm/mgag200: Add FB_DAMAGE_CLIPS support
  5913ab941d6e drm/mgag200: Acquire I/O lock while reading EDID
  931e3f3a0e99 drm/mgag200: Protect concurrent access to I/O registers with lock
  e13f13e039dc drm: Add DRM-managed mutex_init()

  [Tests]
  Verified on the machine with Matrox G200eW3 [102b:0536] graphics card.

  [Where problems could occur]
  The commits to solve the conflicts are trivial, and not likely to introduce 
regressions. The fix patch change a lot of code and hard to evaluate the risk, 
but check the latest linus/master tree and linux-next/master tree, there is no 
fixed commit for all these cherry-picked commits, so should be safe to include 
them.

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


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

[Kernel-packages] [Bug 1991608] Re: TEE Support for CCP driver

[Kleber Sacilotto de Souza]

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

** Changed in: linux (Ubuntu Kinetic)
   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.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1991608

Title:
  TEE Support for CCP driver

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

Bug description:
  [SRU Justification]

  [Impact]

  Missing support for of AMD Secure Processor device for PCI ID 0x14CA.

  [Fix]

  A patch is being proposed in upstream and CC-ed stable.

  [Test Case]

  Without a proper fix, following error appears in dmesg:

ccp :02:00.5: tee: missing driver data
ccp :02:00.5: tee initialization failed

  [Where problems could occur]

  This adds a new driver data entry to support ccp device that provides
  both sev and tee feature at the same time.

  [Other Info]

  While this is proposed to stable 5.15+, all kernels >= 5.15 are
  nominated for fix.

  == original bug description ==

  Client and datacenter Zen4 SOC same PCI-ID but offer different
  functionality from the PSP.

  Genoa offers SEV, Client part offers TEE.
  This patch fixes an ERR level message and CCP driver functionality not 
working.

  ccp :02:00.5: tee: missing driver data
  ccp :02:00.5: tee initialization failed

  https://lore.kernel.org/linux-
  
crypto/20220928184506.13981-1-mario.limoncie...@amd.com/T/#m1b933ea4b961d17cb1be5be74e2d22a860507ca0

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


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

[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)

[Linuxium]

The latest Nvidia BETA driver
(https://www.nvidia.com/Download/driverResults.aspx/194278/en-us/):

Linux X64 (AMD64/EM64T) Display Driver 
Version:525.53 BETA
Release Date:   2022.11.10
Operating System:   Linux 64-bit
Language:   English (US)
File Size:  394.19 MB

includes:

Fixed a regression in 515.76 that caused blank screens and hangs when
starting an X server on RTX 30 series GPUs in some configurations where
the boot display is connected via HDMI.

and this did indeed fix this issue for me.

Alternatively, keep an eye on 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa and when updated 
with version 525 do
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
and then install the Ubuntu packaged driver for your series.

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

Title:
  Can not login after new kernel installed (nvidia driver crashed)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  New
Status in linux source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510 source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Confirmed
Status in xserver-xorg-video-intel source package in Jammy:
  New

Bug description:
  Hello. Today i have installed new kernel from. I installed 5.15.0-50
  and after that i can not login to system... I see boot text, but after
  booting i see black log screen and can not login. I able boot and
  login with old kernel  (5.15.0-48).

  I updated these packages:
  Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic)
  Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), 
google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), 
linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 
(5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 
5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50)

  Updated logs see in attachement.

  Logs from journalctl see in attachements.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vodka  1819 F pulseaudio
   /dev/snd/controlC1:  vodka  1819 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Wed Oct 12 19:56:43 2022
  InstallationDate: Installed on 2018-05-02 (1623 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device
   Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro
  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-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago)
  dmi.bios.date: 03/28/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F7a
  dmi.board.asset.tag: Default string
  dmi.board.name: H610M S2H DDR4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[jhubuntu20]

Thanks, I had tried a couple of things on the brightness, but it doesn't really 
bother me that much and I kind of forgot about it.  I will try your approach.

So full disclaimer, I am usually an Angular architect and not a linux
admin so try at your own risk, etc., etc., but here are my thoughts on
your post...  Back when I created the original script, the Ion and
ubuntu 20.04 had several sound related issues.  I had found fixes for
the headphone jack and a few other issues initially, and then Mike
Pozulp gave me a wonderful conceptual process and some key pointers for
how to use qemu to get the verbs for the speakers.  The process in that
blog is the old, more complicated process.  Fast forward to the galaxy
book 2 and ubuntu 22.04, and on this laptop I didn't have to do most of
the same steps because several of the issues were fixed in the base
ubuntu version.  So in general I would say you shouldn't need to do any
of the hda retasking or alsmixer steps on your new laptop.  In fact it
was so easy on this laptop I didn't even install alsamixer or the other
sound tools I had installed before to work on the ion.  Here is the full
entirety of everything I did on a fresh 22.04 install on the book 2 pro
to get to working sound... perhaps one of these steps is the key...


1) Install pavucontrol.  I don't think this was actually necessary, but I 
wanted the tool available just in case.

sudo apt install pavucontrol

2) Install alsa-tools.  This is absolutely required because it installs
the hda verb utility.  If you try to run the script without the verb
tool then it won't work, but I would assume you would have seen the
errors.

sudo apt-get install alsa-tools

3) Kill the default alsa-base.  Don't substitute or replace, just make
sure this file is no longer present.  I recommend rename instead of
delete in case you ever want to back.  This is likely the step your
missing.  Don't substitute a new file.

Go into folder and just rename this file so it is not present

 /etc/modprobe.d/alsa-base.conf

4) Place the TO912.sh script and be sure to chmod the permissions to 777
and make it executable with +x

5) Create the two daemon files, making sure you did the chmod 664 step
and making sure the paths to the TO912 script are updated.

6) Activate the daemons.  be sure to do the reload before enabling.

sudo systemctl daemon-reload
sudo systemctl enable ionsound.service  
sudo systemctl enable ionsoundsleep.service 

7) Turn off suspend on idle.  This should not be needed to make it run,
but keeps the change working through standby mode after it starts
working

sudo gedit /etc/pulse/default.pa
Add comments to ### load-module module-suspend-on-idle

8) Reboot and verify

That's it, should be every thing you need to do from a fresh 22.04 to
get full sound on headphones and speakers.  I never actually tried
running the TO script on this unit before doing these steps, so I can't
say for sure if that works before removing alsa-base, but I have had to
reload this laptop 3 times for other reasons and this process worked
every time.

If it helps here is my output from sudo lspci -v | grep  -i audio.  you
should seem something similar...

00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High 
Definition Audio Controller (rev 01)
Kernel driver in use: sof-audio-pci-intel-tgl

I am also currently running the generic kernel, but previously I did try
the oem kernel and the sound worked with it also, so if you have
upgraded from 5.15 then I don't think that's your issue.  The mainline
tool is very handy though.

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: 

[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

[Timo Aaltonen]

I suspect there's a commit missing from the kernel, and if so, there's
not much time before the new cycle starts next week..

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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

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

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

Title:
  Crashed boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating Linux Mint 21, along with kernal updates from 5.15.0-48.
  Update hung near end of kernal update and never moved. Rebooted and system 
would hang at flashing courser after booting to just after the login and pw and 
would just hang there.
  Had to start in emergency mode and revert to kernal 5.15.0-48.

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


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

[Kernel-packages] [Bug 1992393] Re: Crashed boot

[Paul White]

Kernel bugs need to be reported against the Linux kernel and not against
the Ubuntu project in general. As Linux Mint seems to be based on Ubuntu
22.04 I'll tag this as being a 'jammy' bug and move this to the 'linux'
package.

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

** Tags added: jammy

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

Title:
  Crashed boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating Linux Mint 21, along with kernal updates from 5.15.0-48.
  Update hung near end of kernal update and never moved. Rebooted and system 
would hang at flashing courser after booting to just after the login and pw and 
would just hang there.
  Had to start in emergency mode and revert to kernal 5.15.0-48.

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


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

[Kernel-packages] [Bug 1992393] [NEW] Crashed boot

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After updating Linux Mint 21, along with kernal updates from 5.15.0-48.
Update hung near end of kernal update and never moved. Rebooted and system 
would hang at flashing courser after booting to just after the login and pw and 
would just hang there.
Had to start in emergency mode and revert to kernal 5.15.0-48.

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


** Tags: bot-comment
-- 
Crashed boot
https://bugs.launchpad.net/bugs/1992393
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1970603] Re: DSI touchscreen not working with KMS under 5.15

[Juerg Haefliger]

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

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

-- 
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:
  Confirmed
Status in linux-raspi source package in Jammy:
  New
Status in linux-raspi source package in Kinetic:
  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 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:

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


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

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

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

Title:
  bug USB in Ubuntu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There is such a problem. UPSs are not working. Powercom and East - also.
  He began to find out what was the matter. If you enter once a second, the 
lsusb command, then we get the following:
  https://ibb.co/y0nfqMQ
  
[url=https://ibb.co/y0nfqMQ][img]https://i.ibb.co/y0nfqMQ/zevstst-u18-lsusb.png[/img][/url]

  it turns out that he sees UPS in USB, then he does not see.
  The output of sudo dmesg | grep usb is as follows:
  https://ibb.co/mRG548r
  
[url=https://ibb.co/mRG548r][img]https://i.ibb.co/mRG548r/zevstst-u18-dmesg.png[/img][/url]

  Here we also see the problem.
  The fact is that there used to be Ub16 and there were no such problems. 
Installed 18 - and started. Put 16 again - no problem again.
  I began to find out in more detail. It turned out that on the kernel 4.11.12 
- UPS work clearly, but as soon as the kernel 4.12-rc3 was installed. 
Everything. problems began.

  What have you done with the kernel since version 4.12? That some UPS
  are now down?? Would they fix it?

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


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

[Kernel-packages] [Bug 1995127] Re: bug USB in Ubuntu

[Paul White]

Bug report seems to infer that the problem lies with the kernel so
moving this to 'linux'.

Ruslan, if this is still an issue then please follow any instructions
that the kernel bot may give you while using Ubuntu 18.04, thanks.


** Tags added: bionic

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

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

Title:
  bug USB in Ubuntu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There is such a problem. UPSs are not working. Powercom and East - also.
  He began to find out what was the matter. If you enter once a second, the 
lsusb command, then we get the following:
  https://ibb.co/y0nfqMQ
  
[url=https://ibb.co/y0nfqMQ][img]https://i.ibb.co/y0nfqMQ/zevstst-u18-lsusb.png[/img][/url]

  it turns out that he sees UPS in USB, then he does not see.
  The output of sudo dmesg | grep usb is as follows:
  https://ibb.co/mRG548r
  
[url=https://ibb.co/mRG548r][img]https://i.ibb.co/mRG548r/zevstst-u18-dmesg.png[/img][/url]

  Here we also see the problem.
  The fact is that there used to be Ub16 and there were no such problems. 
Installed 18 - and started. Put 16 again - no problem again.
  I began to find out in more detail. It turned out that on the kernel 4.11.12 
- UPS work clearly, but as soon as the kernel 4.12-rc3 was installed. 
Everything. problems began.

  What have you done with the kernel since version 4.12? That some UPS
  are now down?? Would they fix it?

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


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

[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

[Timo Aaltonen]

please try with 6.1-rc mainline

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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

[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

[Timo Aaltonen]

and if still not lucky, file an issue on the sof firmware github?

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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

[Kernel-packages] [Bug 1995941] Re: [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait

[Stefan Bader]

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

Title:
  [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW
  wait

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

   * In a secure execution guest, the external interrupt for the SIGP
 external call order is delivered twice to a VCPU even though it was 
 only sent once.

   * Under PV (protected virtualization), external call interrupts are
     delivered by the SIGP interpretation facility, without KVM's
     involvement.
     But, if the receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered.
     Hence, in this case, the SIGP external call order causes
     an interception.

   * In response, KVM only needs to wake the receiving VCPU.
     Interrupt delivery is then handled by the SIGP interpretation facility.

   * KVM wrongly assumed it also needs to request injection for the
     external call interrupt after the respective intercept, causing the
     interrupt to be delivered twice:
     * once through the SIGP interpretation facility
     * and once through the interrupt injection control by KVM.

   * Solution is to add appropriate special handling for 108 external
     call intercepts.

  [Fix]

   * c3f0e5fd2d33 c3f0e5fd2d33d80c5a5a8b5e5d2bab2841709cc8
     "KVM: s390: pv: don't present the ecall interrupt twice"

  [Test Case]

   * Have an Secure Execution (PV) environment setup on an
     IBM z15 or LinuxONE III LPAR using Ubuntu Server 20.04 (latest).

   * Apply kvm-unit-test submitted upstream:
     "[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP call \
  orders in enabled wait"

   * Run the smp_PV kvm-unit-test: ./run_tests.sh smp_PV

   * Check logs/smp_PV.log.
     If system is affected, the following line can be found:
     "ABORT: smp: psw wait: ecall: Unexpected external call interrupt \
  (code 0x1202): on cpu 1 at 0x11958"

   * If the system is not affected, the line should look like this:
     "PASS: smp: psw wait: ecall: received"

  [Regression Potential / What can go wrong]

   * The handle_pv_notification can be wrong and misleading
     in case 'ret' is not handled correctly.

   * trace_kvm_s390_handle_sigp_pei might not be called correctly,
     now after the if condition.

   * In worst case the external interrupt could not be delivered
     at all or still too often.

  [Other]

   * The fix/patch c3f0e5fd2d33 got upstream accepted with kernel v6.0,
     so it not only needs to be applied to 20.04/5.4, but also to 22.04/5.15
     and 22.10/5.19.

   * But the patch got properly tagged for upstream stable:
     Cc:  # 5.7
     Fixes: da24a0cc58ed ("KVM: s390: protvirt: Instruction emulation")

   * And with that it got already picked up and is included in:
     22.04 with Ubuntu-5.15.0-53.59 (currently in jammy-proposed)
     22.10 with Ubuntu-5.19.0-16.16 means incl. in the release kernel.

   * So the only Ubuntu release that is affected is 20.04/focal.
  __

  Description:   KVM: PV: ext call delivered twice when receiver in PSW wait
  Symptom:   In a secure execution guest, the external interrupt for the
     SIGP external call order is delivered twice to a VCPU even
     though it was only sent once.
  Problem:   Under PV, external call interrupts are delivered by the SIGP
     interpretation facility, without KVM's involvement. But, if the
     receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered. Hence,
     in this case, the SIGP external call order causes an
     interception. In response, KVM only needs to wake the receiving
     VCPU. Interrupt delivery is then handled by the SIGP
     interpretation facility.

     KVM wrongfuly assumed it also needs to request injection for 
the
     external call interrupt after the respective intercept, causing
     the interrupt to be delivered twice: once through the SIGP
     interpretation facility and once through the interrupt 
injection
     control by KVM.
  Solution:  Add appropriate special handling for 108 external call
     intercepts.
  Reproduction:  0. Apply kvm-unit-test submitted upstream
    ("[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP
    call orders in enabled wait").
     1. Run the smp_PV kvm-unit-test:
  ./run_tests.sh smp_PV
     2. 

[Kernel-packages] [Bug 1995127] [NEW] bug USB in Ubuntu

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

There is such a problem. UPSs are not working. Powercom and East - also.
He began to find out what was the matter. If you enter once a second, the lsusb 
command, then we get the following:
https://ibb.co/y0nfqMQ
[url=https://ibb.co/y0nfqMQ][img]https://i.ibb.co/y0nfqMQ/zevstst-u18-lsusb.png[/img][/url]

it turns out that he sees UPS in USB, then he does not see.
The output of sudo dmesg | grep usb is as follows:
https://ibb.co/mRG548r
[url=https://ibb.co/mRG548r][img]https://i.ibb.co/mRG548r/zevstst-u18-dmesg.png[/img][/url]

Here we also see the problem.
The fact is that there used to be Ub16 and there were no such problems. 
Installed 18 - and started. Put 16 again - no problem again.
I began to find out in more detail. It turned out that on the kernel 4.11.12 - 
UPS work clearly, but as soon as the kernel 4.12-rc3 was installed. Everything. 
problems began.

What have you done with the kernel since version 4.12? That some UPS are
now down?? Would they fix it?

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


** Tags: bionic bot-comment
-- 
bug USB in Ubuntu
https://bugs.launchpad.net/bugs/1995127
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Frank Heimes]

** Changed in: ubuntu-z-systems
   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/1996071

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

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


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

[Kernel-packages] [Bug 1996121] Re: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec

[Stefan Bader]

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

Title:
  alsa: soc: the kernel print UBSAN calltrace on the machine with
  cs35l41 codec

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

Bug description:
  The cs35l41 codec driver was backported to Jammy kernel a couple of
  months ago, recently the Jammy kernel was adopted as the hwe kernel
  for OEM machines and with this kernel the UBSAN calltrace was seen,
  need to backport these 2 patches. Kinetic kernel already has the
  patches, so this SRU is only for Jammy kernel.

  [Impact]
  Install the 5.15 hwe kernel on the machines with cs35l41
  codec, after booting and check the dmesg, there is a UBSAN calltrace.

  [Fix]
  Backport 2 patches from mainlie kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine, check the dmesg, there
  is no UBSAN calltrace, and test the audio functions, all input
  and output devices coudl work as well as before.

  
  [Where problems could occur]
  The patch only affects the cirruslogic asoc codec driver, if it
  could introduce the regression, it will be on the machines with
  cs codec, and it will make the audio driver initialization fail
  and make the system lose the audio function. But this possibility
  is very low, we tested the patches on many oem machines, all
  worked well.

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


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

[Kernel-packages] [Bug 1993715] Re: AMD Cezanne takes 5 minutes to wake up from suspend

[Stefan Bader]

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

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

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

Title:
  AMD Cezanne takes 5 minutes to wake up from suspend

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  AMD Cezanne takes 5 minutes to wake up from suspend.

  [Fix]

  A fix originated from AMD is being proposed to upstream mailing list.

  [Test Case]

  $ rtcwake -m mem -s 10

  [Where problems could occur]

  This patch fixes the issue we had, but maybe there are still some
  other corner cases that can cause similar problems.

  [Other Info]

  The problematic commit landed in v5.19-rc1, so kernels >= v5.19 are
  nominated for fix.

  == original bug description ==

  [Summary]
  rtcwake may be blocked for 5 minutes.

  Model name: AMD Ryzen 5 7530U with Radeon Graphics
  CPU family: 25
  Model: 80
  Thread(s) per core: 2
  Core(s) per socket: 6
  Socket(s): 1
  Stepping: 0

  [Reproduce Steps]
  1. $ rtcwake -m mem -s 10
  2. The device takes 5 minutes to resume

  [Results]
  Expected: Should resume after 10 seconds
  Actual: System stays asleep for 5 minutes

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


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

[Kernel-packages] [Bug 1995041] Re: Fix ath11k deadlock on WCN6855

[Stefan Bader]

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

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

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

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

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

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

Title:
  Fix ath11k deadlock on WCN6855

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  ath11k is in deadlock when stress reboot or suspend on WCN6855.
  sometimes kernel hang.

  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace:
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: 
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? 
ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211]

  [Fix]
  Fix this by switching from using regulatory_set_wiphy_regd_sync() to
  regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue 
which
  handles the locking on it's own. So the ath11k workqueue can simply exit 
without
  taking any locks, avoiding the deadlock.

  [Test]
  Verified on hardware, stress reboot and suspend 30 times OK.

  [Where problems could occur]
  It may break ath11k wifi driver.

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


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

[Kernel-packages] [Bug 1988461] Re: intel_pmc_core not load on Raptor Lake

[Stefan Bader]

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

** Changed in: linux (Ubuntu Kinetic)
   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.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1988461

Title:
  intel_pmc_core not load on Raptor Lake

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Missing kernel pmc sysfs interface in /sys/kernel/debug/pmc_core.

  [Fix]

  Two commits for kernel version older than v6.0-rc3, and one for
  otherwise.

  [Test Case]

  $ ls /sys/kernel/debug/pmc_core

  [Where problems could occur]

  No.

  [Other Info]

  RPL-S is supported since oem-5.17, so unstable/oem-6.0/kinetic/oem-5.17
  are affected. oem-5.17/oem-6.0 are skipped here for they have been
  applied manually.

  == original bug description ==

  [Summary]
  intel_pmc_core not load on Raptor Lake

  [Reproduce Steps]
  1. Boot into Ubuntu desktop
  2. Check if /sys/kernel/debug/pmc_core folder exist

  [Results]
  Expected: folder /sys/kernel/debug/pmc_core folder been created
  Actual: /sys/kernel/debug/pmc_core not exist

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


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

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Stefan Bader]

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

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

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

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

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

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

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


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

[Kernel-packages] [Bug 1990750] Re: Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15, now hanging with blinking cursor after update to Kernel 5.19.0.21.21

[atactic]

Dear launchpad community,
Sorry to bump this, but it is a serious bug with Kinetic kernels.
My system is nothing extraordinary and therefore other users probably are 
encountering the same and staying away from Kinetic for that reason. 
Anyone of you could become the solver for this issue?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1990750

Title:
  Boot issue with Ubuntu 22.10 Kinetic Kudu since Kernel 5.19.0.15.15,
  now hanging with blinking cursor after update to Kernel 5.19.0.21.21

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When starting the PC, the splash screen freezes with the motherboard logo 
displayed.
  As my disk is encrypted the decryption field does not appear below the logo.

  By typing [ALT] + [CTRL] + [DEL] then the splash screen appears again 
followed by a start-up menu with the following line:
  *Ubuntu
   Advanced options for Ubuntu

  By selecting 'Advanced options for Ubuntu' the following submenu appears:
  *Ubuntu, with Linux5.19.0-15-generic
   Ubuntu, with Linux5.19.0-15-generic (recovery mode)

  Selecting the second option, then the system starts loading with the initial 
lines of code:
  Loading Linux 5.19.0-15-generic ...
  Loading initial ramdisk ...

  When code has finished loading, the last line at the bottom of the screen is 
for unlocking the disk:
  Begin: Mounting root fie system ... Begin Running /script/local-top ... 
Please unlock disk nvme0n1p3_crypt:

  Then i type in the code and hit [return] and more code is loading, until a 
recovery menu with purple background appears, with the title:
  Recovery Menu (filesystem state: read-only).

  I select the first menu item:
  resume  Resume normal boot
  and hit [return].

  The menu changes to the notification:
  You are now going to exit the recovery mode bla bla bla
  with the [OK] button below it.

  I hit the [OK] button and then the login screen finally appears.

  I will post a video of the complete boot sequence later on as I need
  to install a softaware to edit the video.

  It is noteworthy that on my previous Ubuntu 22.04 install the same
  issue with the frozen splash screen occurred when my system was
  updated with Kernel 5.15.5, but then I did not try out to execute the
  [ALT] + [CTRL] + [DEL] command.

  Therefore the bug is probably affecting all kernels from 5.15.5
  upwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset wl nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 25 08:30:29 2022
  InstallationDate: Installed on 2022-09-24 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220920)
  MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD5H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97X-UD5H
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1950792] Re: No boot possible - Cannot open root device

[Stefan Fleischmann]

I am having similar problems since updating from 3.0 to the latest
release 3.2.6

We mainly use legacy boot (instead of UEFI) and the boot order of all our nodes 
is set to:
1. Network/PXE
2. harddisk

A deployed node would boot PXE and then immediately MAAS tells it (not
sure how exactly) to boot from the harddrive instead. This doesn't seem
to work anymore with 3.2.6. Instead of booting the node stops with a
kernel panic. Error messages I can see on the screen are (nothing in the
SOL at this early stage):

```
VFS: Cannot open root device 
"squash:http://172.17.100.3:5248/images/ubuntu/amd64/ga-20.04/fo; or 
unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
```

If I set the harddisk as first boot device in the BIOS the node boots
okay. Commission of a node works, and new deployments work up to the
point where the node would boot into the newly installed OS, then above
error prevents it from succeeding. Then I need to manually change the
boot order to allow deployment to succeed.

Any idea what has changed here from 3.0 to 3.2?

What is the recommended boot order for legacy boot now? I suppose
nowadays MAAS requests PXE boot via IPMI whenever needed, so hard disk
as first boot option should work. But I remember this was not always the
case when we started using 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/1950792

Title:
  No boot possible - Cannot open root device

Status in MAAS:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MaaS cannot boot on my X11DPi-NT and will therefore fail to
  commission. It will instantly fail after grub.

  It will fail to boot saying that is not able to open root device. I
  even tried supplying the squashfs via python on a different port as
  the url is somehow cut off a bit, but to no avail. The python
  webserver doesn't even see any connection try.

  ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs
  python webserver: python3 -m http.server 8080)

  Steps to reproduce:

  1. Setup maas ;)
  2. Try to commision server
  3. See the kernel and initrd download fly by 
  4. Boom kernel panic

  Hardware:
  Supermicro X11DPi-NT with UEFI http Networkboot enabled
  NIC: Intel X722

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


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

[Kernel-packages] [Bug 1991608] Re: TEE Support for CCP driver

[You-Sheng Yang]

Verified linux-oem-6.0/jammy version 6.0.0-1007.7.

** Tags added: verification-done-jammy

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

Title:
  TEE Support for CCP driver

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

Bug description:
  [SRU Justification]

  [Impact]

  Missing support for of AMD Secure Processor device for PCI ID 0x14CA.

  [Fix]

  A patch is being proposed in upstream and CC-ed stable.

  [Test Case]

  Without a proper fix, following error appears in dmesg:

ccp :02:00.5: tee: missing driver data
ccp :02:00.5: tee initialization failed

  [Where problems could occur]

  This adds a new driver data entry to support ccp device that provides
  both sev and tee feature at the same time.

  [Other Info]

  While this is proposed to stable 5.15+, all kernels >= 5.15 are
  nominated for fix.

  == original bug description ==

  Client and datacenter Zen4 SOC same PCI-ID but offer different
  functionality from the PSP.

  Genoa offers SEV, Client part offers TEE.
  This patch fixes an ERR level message and CCP driver functionality not 
working.

  ccp :02:00.5: tee: missing driver data
  ccp :02:00.5: tee initialization failed

  https://lore.kernel.org/linux-
  
crypto/20220928184506.13981-1-mario.limoncie...@amd.com/T/#m1b933ea4b961d17cb1be5be74e2d22a860507ca0

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


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

[Kernel-packages] [Bug 1989041] Re: Add iommu passthrough quirk for Intel IPU6 on RaptorLake

[You-Sheng Yang]

Verified linux-oem-6.0/jammy version 6.0.0-1007.7.

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

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

Title:
  Add iommu passthrough quirk for Intel IPU6 on RaptorLake

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Intel iommu was turned on by default in mainline build v5.15.5 or jammy
  -generic kernel 5.15.0-12.12. This would breaks IPU6.

  For TGL and ADL platforms, it has been fixed in bug 1958004 for oem-5.14 and
  above. This patch adds a new ID for RPL.

  [Fix]

  Use IOMMU passthrough mode for IPU6 as it has its own iommu hardware.

  [Test Case]

  Apply the fix and kernel should print a new info line:

Passthrough IOMMU for integrated Intel IPU

  and IPU6 camera should continue to work without intel_iommu=off
  work-around.

  [Where problems could occur]

  No. That's what it should have been done.

  [Other Info]

  Nominates only oem-6.0 and unstable for we have RPL IPU6 enabled on oem-6.0
  and newer.

  == original bug report ==

  Per
  
https://github.com/intel/ipu6-drivers/commit/89c6b99e4bec00a04b53f37cd8c3c01ce824a4ab,
  an additional quirk is necessary for Intel IPU6 on Raptor Lake as
  previous TGL/ADL do.

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


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

[Kernel-packages] [Bug 1991609] Re: Add support for AMD PMF Cool and Quiet Framework (CnQF)

[You-Sheng Yang]

Verified linux-oem-6.0/jammy version 6.0.0-1007.7.

** Tags added: verification-done-jammy

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

Title:
  Add support for AMD PMF Cool and Quiet Framework (CnQF)

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Missing AMD CnQF that will dynamically adjust performance and power
  consumption based upon OEM specified metrics on supported systems.

  [Fix]

  Three commits from linux-next to be backported to oem-6.0 and above.

  [Test Case]

  To enable this in AMD Phoenix CRB:

BIOS: AMD PBS > AMD PMF Settings, enable function 11/12 & flag=1

  And feature enabled message should appear in dmesg:

[ 3.203628] amd-pmf AMDI0102:00: registered PMF device successfully

  Access via sysfs:

root@test:/sys/devices/platform/AMDI0102:00# cat cnqf_enable
on

  [Where problems could occur]

  This is a new feature and will probably receive some more fixes in the
  future. So far we have little, in both kernel and userspace, runtime and
  testing, involved.

  [Other Info]

  This series depends on AMD PMF support in bug 1987670. And since these
  patches targets v6.1 and AMD phoenix target oem-6.0, only oem-6.0 and
  unstable is nominated for fix.

  == original bug description ==

  CnQF is a feature that will dynamically adjust performance and power
  consumption based upon OEM specified metrics on supported systems.

  This is targeted for 6.1.

  platform/x86/amd/pmf: Add support for CnQF
  
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next=1738061c9ec854db2db76be8bb968f550d9bdddc

  platform/x86/amd/pmf: Add sysfs to toggle CnQF
  
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next=3dae5825295d7b3284fc349cd6bfa641f4033e16

  Documentation/ABI/testing/sysfs-amd-pmf: Add ABI doc for AMD PMF
  
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next=1590ac2c6615329d30e25753e03c295cdaf2ae44

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


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

[Kernel-packages] [Bug 1996071] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From peter.oberparlei...@de.ibm.com 2022-11-11 03:49 EDT---
(In reply to comment #12)
> Created attachment 156118 [details]
> 0001-s390-boot-add-secure-boot-trailer.patch

I verified that this patch correctly adds the required secure boot
trailer for v5.4 kernels.

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

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


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

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Frank Heimes]

** Description changed:

  SRU Justification:
  ==
  
  [Impact]
  
-  * Secure boot of Linux on s390x will no longer be possible
-with an upcoming IBM zSystems firmware update.
+  * Secure boot of Linux on s390x will no longer be possible
+    with an upcoming IBM zSystems firmware update.
  
  [Fix]
  
-  * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
-for kinetic and jammy
+  * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
+    for kinetic and jammy
  
-  * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
-backport for focal
+  * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
+    backport for focal
  
  [Test Plan]
  
-  * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
+  * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.
  
-  * Ensure that 'Enable Secure Boot for Linux' is marked in case
-'SCSI Load' is selected at the HMCs Load task and Activation Profile.
+  * Ensure that 'Enable Secure Boot for Linux' is marked in case
+    'SCSI Load' is selected at the HMCs Load task and Activation Profile.
  
-  * Perform an Ubuntu Server installation, either 20.04 or 22.04
-(latest ISO).
-It will be a secure boot installation by default in case 
-'Enable Secure Boot for Linux' was marked.
+  * Perform an Ubuntu Server installation, either 20.04 or 22.04
+    (latest ISO).
+    It will be a secure boot installation by default in case
+    'Enable Secure Boot for Linux' was marked.
  
-  * Check sysfs:
-/sys/firmware/ipl/has_secure
-   '1' indicates hw support for secure boot, otherwise '0'
-/sys/firmware/ipl/secure
-   '1' indicates that secure IPL was successful, otherwise '0'
+  * Check sysfs:
+    /sys/firmware/ipl/has_secure
+   '1' indicates hw support for secure boot, otherwise '0'
+    /sys/firmware/ipl/secure
+   '1' indicates that secure IPL was successful, otherwise '0'
  
-  * Navigate to the HMC task 'System information'
-and check the active firmware release.
+  * Navigate to the HMC task 'System information'
+    and check the active firmware release.
  
-  * Ensure that Ubuntu is still bootable in secure-boot mode
-with the updated firmware active,
-by for example doing a reboot after the firmware upgrade.
+  * Ensure that Ubuntu is still bootable in secure-boot mode
+    with the updated firmware active,
+    by for example doing a reboot after the firmware upgrade.
+ 
+  * There is also a way to test the trailer on systems that do not
+have the updated firmware yet - in this case use the following script:
+https://launchpadlibrarian.net/633126861/check_sb_trailer.sh
  
  [Where problems could occur]
  
-  * The 'trailer' might be broken, invalid or in a wrong format
-and can't be identified or read properly,
-or may cause issues while compressing/decompressing the kernel.
+  * The 'trailer' might be broken, invalid or in a wrong format
+    and can't be identified or read properly,
+    or may cause issues while compressing/decompressing the kernel.
  
-  * In worst case secure boot might become broken,
-even on systems that are still on the unpatched firmware level.
+  * In worst case secure boot might become broken,
+    even on systems that are still on the unpatched firmware level.
  
-  * Or secure boot will become broken in general.
+  * Or secure boot will become broken in general.
  
  [Other Info]
  
-  * The above commit was upstream accepted with v6.1-rc3.
+  * The above commit was upstream accepted with v6.1-rc3.
  
-  * And it got tagged for upstream stable with:
-"Cc:  # 5.2+"
+  * And it got tagged for upstream stable with:
+    "Cc:  # 5.2+"
  
-  * But since this bug is marked as critical, and the patch is relatively
-short, traceable and s390x-specific, I'll go ahead and submit this
-patch for Jammy and Focal ahead of upstream stable.
+  * But since this bug is marked as critical, and the patch is relatively
+    short, traceable and s390x-specific, I'll go ahead and submit this
+    patch for Jammy and Focal ahead of upstream stable.
  
-  * Since on focal file 'vmlinux.lds.S' is at a different location
-'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
-and the context is slightly different, the backport is needed.
+  * Since on focal file 'vmlinux.lds.S' is at a different location
+    'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
+    and the context is slightly different, the backport is needed.
  
-  * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
-the patch incl. when at the planned target level.
+  * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
+    the patch incl. when at the planned target level.
  
  __
  
  Description:   boot: Add secure boot trailer
  

[Kernel-packages] [Bug 1996071] Secure boot trailer test script

[bugproxy]

--- Comment on attachment From peter.oberparlei...@de.ibm.com 2022-11-11 
03:46 EDT---


Bash script to test if kernel image and zipl stage3.bin files contain the 
correct secure boot trailer.

Usage examples:

$ check_sb_trailer.sh s390-tools/zipl/boot/stage3.bin
Checking secure boot trailer of file s390-tools/zipl/boot/stage3.bin
  * Read 32 bytes at offset 3fe0:
c0088000a000a0207a49504c
  * Success - stage3 trailer found
$ check_sb_trailer.sh linux/arch/s390/boot/bzImage 
Checking secure boot trailer of file linux/arch/s390/boot/bzImage
  * Read 32 bytes at offset 00ac0fe0:
00207a49504c
  * Success - Linux kernel trailer found

** Attachment added: "Secure boot trailer test script"
   
https://bugs.launchpad.net/bugs/1996071/+attachment/5630584/+files/check_sb_trailer.sh

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
 with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
 for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
 backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
 'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
 (latest ISO).
 It will be a secure boot installation by default in case 
 'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
 /sys/firmware/ipl/has_secure
'1' indicates hw support for secure boot, otherwise '0'
 /sys/firmware/ipl/secure
'1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
 and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
 with the updated firmware active,
 by for example doing a reboot after the firmware upgrade.

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
 and can't be identified or read properly,
 or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
 even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
 "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
 short, traceable and s390x-specific, I'll go ahead and submit this
 patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
 'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
 and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
 the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

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


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

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Frank Heimes]

SRU request submitted to the Ubuntu kernel team mailing list for kinetic, jammy 
and focal.
https://lists.ubuntu.com/archives/kernel-team/2022-November/thread.html#134685
It's a cherrypick for K and J, but a backport for F.
Changing status to 'In Progress' for kinetic, jammy and focal.

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

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

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

** Changed in: ubuntu-z-systems
   Status: New => In Progress

** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
 with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
 for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
 backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
 'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
 (latest ISO).
 It will be a secure boot installation by default in case 
 'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
 /sys/firmware/ipl/has_secure
'1' indicates hw support for secure boot, otherwise '0'
 /sys/firmware/ipl/secure
'1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
 and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
 with the updated firmware active,
 by for example doing a reboot after the firmware upgrade.

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
 and can't be identified or read properly,
 or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
 even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
 "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
 short, traceable and s390x-specific, I'll go ahead and submit this
 patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
 'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
 and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
 the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

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


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

[Kernel-packages] [Bug 1989041] Re: Add iommu passthrough quirk for Intel IPU6 on RaptorLake

[Timo Aaltonen]

** Tags added: verification-needed-jammy

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

Title:
  Add iommu passthrough quirk for Intel IPU6 on RaptorLake

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Intel iommu was turned on by default in mainline build v5.15.5 or jammy
  -generic kernel 5.15.0-12.12. This would breaks IPU6.

  For TGL and ADL platforms, it has been fixed in bug 1958004 for oem-5.14 and
  above. This patch adds a new ID for RPL.

  [Fix]

  Use IOMMU passthrough mode for IPU6 as it has its own iommu hardware.

  [Test Case]

  Apply the fix and kernel should print a new info line:

Passthrough IOMMU for integrated Intel IPU

  and IPU6 camera should continue to work without intel_iommu=off
  work-around.

  [Where problems could occur]

  No. That's what it should have been done.

  [Other Info]

  Nominates only oem-6.0 and unstable for we have RPL IPU6 enabled on oem-6.0
  and newer.

  == original bug report ==

  Per
  
https://github.com/intel/ipu6-drivers/commit/89c6b99e4bec00a04b53f37cd8c3c01ce824a4ab,
  an additional quirk is necessary for Intel IPU6 on Raptor Lake as
  previous TGL/ADL do.

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


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

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

[Timo Aaltonen]

** Tags added: verification-needed-jammy

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

Title:
  Can only reach PC3 when ethernet is plugged r8169

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Won't Fix
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Confirmed
Status in linux-oem-5.13 source package in Kinetic:
  Invalid
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

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

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

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

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

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


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