date:20221017

This depends on a few more AMD PMF fixes:
* c2f7edf81a82 ("platform/x86/amd/pmf: Fix undefined reference to 
platform_profile")
* ea522b806162 ("platform/x86/amd/pmf: Fix clang unused variable warning")

These two commits also have Fixes tag for commits previously landed in
bug 1987670.

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

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

Title:
  Fix a race condition with AMD PMF and Thinkpad-ACPI

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:
  Confirmed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  Depending on module load order there is a possibility that the AMT
  mode selected initially by PMF will be incorrect if thinkpad_acpi has
  loaded first.

  To avoid this issue adjust the initialization order in the PMF driver.

  
https://github.com/torvalds/linux/commit/22ee98cb696e95b05a188756d479d382d93559ef

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


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

2022-10-17 Thread atactic

It actually does nothing.
Cursor continues blinking.

--
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 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04

2022-10-17 Thread Aravind Valloor Mana

Hi Jeff,

Do you have the kernel version which has these lpfc patches integrated?
If not, any ETA?

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

Title:
  Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress

Bug description:
  [IMPACT/Justification]
  There are numerous bug fixes included in the more recent version of lpfc That 
Broadcom has asked to pull into Jammy and Kinetic to better support customers 
in the field who are using the GA kernel and cant or wont move to the HWE 
kernels.  These all are limited to the lpfc driver itself, no patches to core 
code are requested.

  [FIX]
  A few of these were already landed in Jammy, and all but 6 (ones landed in 
6.0 upstream) were already in Kinetic.

  b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
  71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
  b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into 
lpfc_sli_prep_abort_xri()
  ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved 
configuration
  ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
  2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF 
WQE
  0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in 
queuecommand after VMID
  35251b4d79db scsi: lpfc: Set PU field when providing D_ID in 
XMIT_ELS_RSP64_CX iocb
  f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with 
malformed user input
  4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in 
lpfc_nvme_cancel_iocb()
  1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
  2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for 
nvme_admin_async_event cmd completion
  ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for 
aborted NVMe cmds
  336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT 
topology
  b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is 
aborted
  6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after 
starget_to_rport()
  e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path 
refactoring
  24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path 
refactoring
  44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in 
lpfc_ct_reject_event()
  a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
  348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol 
independent
  ed913cf4a533 scsi: lpfc: Commonize VMID code location
  fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
  a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for 
NVMe I/O
  e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
  de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
  5099478e436f scsi: lpfc: Change VMID registration to be based on fabric 
parameters
  dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if 
lpfc_err_lost_link()
  4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in 
rscn_recovery_check()
  596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
  ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
  b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
  ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
  84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
  775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
  cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
  c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
  92bd903da12b scsi: lpfc: Fix additional reference counting in 
lpfc_bsg_rport_els()
  db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
  646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
  3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in 
lpfc_sli_prep_wqe()
  a346f28ad231 scsi: lpfc: Remove unneeded variable
  66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
  4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
  fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
  f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
  ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
  d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure
  1045592fc968 scsi: lpfc: Introduce FC_RSCN_MEMENTO flag for tracking post 
RSCN completion
  6c983d327b9e scsi: lpfc: Register for Application Services FC-4 type in 
Fabric topology
  6c8a3ce64b2c scsi: lpfc: Remove false FDMI NVMe FC-4 support for NPIV ports

[Kernel-packages] [Bug 1993078] Re: immediate crash on boot HP Omnibook XE3-GF

2022-10-17 Thread stiltskin

there's no AMD64 support.

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

Title:
  immediate crash on boot HP Omnibook XE3-GF

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

Bug description:
  Immediate crash upon entering boot with linux-image-5.4.0-128-generic
  on HP Omnibook XE3-GF

  Prior versions up to linux-image-5.4.0-126-generic work fine

  
  I 8.3938581 Hardware name: Hewlett-Packard HP OmniBook PC GF M1 14 11/27/2002

  [ 8.3931371 EIP: switch_to_asm+0x44/0x54

  T A.3931941 Code: 54 e8 41 d2 bb 10 00 00 00 e8 07 00 00 00 f3 98 Of
  ae e8 eb 19 e8 87 00 00 00 f3 98 Of ae e8 eb f9 4b 75 e5 81 c4 80 00
  00 00 <0f> ae e8 9d

  Se 5f 5b 5d e9 9f ca 65 ff 8d 76 00 55 89 e5 50 e8 a3

  L 8.393297] EAX: d22005c0 EBX:  ECX: 176a5b33 EDX: f653da00 [
  0.3933571 ESI:  EDI: f75f2d40 EBP: d21f9e88 ESP: f6537f94

  L 8.393455] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS:
  00210082

  [ 0.3935411 CRO: 80050033 CRZ: ffbff000 CR3: 1242e000 CR4: 06f0

  [ 0.393640] Call Trace:

  [ 8.393746] Modules linked in:

  L 8.393846] ---[ end trace 7de00da7437d5ef2

  [ 8.393932] EIP: _switch_to_asm+0x44/0x54

  [ 8.394814] Code: 54 e8 41 d2 bb 10 00 00 00 e8 07 00 00 00 f3 90 of
  ae e8 eb

  f9 e8 07 00 00 00 f3 98 Of ae e8 eb f9 4b 75 e5 81 c4 80 00 00 00 <0f>
  ae e8 9d Se 5f 5b 5d e9 9f ca 65 ff 8d 76 88 55 89 e5 58 e8 a3

  [ 8.394248] EAX: d22005c8 EBX:  ECX: 176a5b33 EDX: f653da00

  [ 0.394388] ESI:  EDI: f75f2d48 EBP: d21f9e88 ESP: f6537f94 [
  8.394486] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS:
  00210082

  [ 0.394492] CRO: 80050033 CRZ: ffbff808 CR3: 1242e800 CR4: 06f8

  [ 0.394594] Kernel panic not syncing: Attempted to kill the idle task!

  [ 8.394683]---[ end Kernel panic not syncing: Attempted to kill the idle 
task! ]---
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-126-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCI [ESS Allegro PCI], device 0: Allegro [Allegro]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCI [ESS Allegro PCI], device 0: Allegro [Allegro]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  irgendjemand   1071 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCI'/'ESS Allegro PCI at 0x2000, irq 5'
 Mixer name : 'ESS Technology ESS1988'
 Components : 'AC97a:45838308'
 Controls  : 25
 Simple ctrls  : 19
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (1615 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
  IwConfig:
   enp2s8no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP OmniBook PC
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-126-generic 
root=UUID=39604362-f78a-488e-9780-2a750f169be6 ro recovery nomodeset 
dis_ucode_ldr
  ProcVersionSignature: Ubuntu 5.4.0-126.142~18.04.1-generic 5.4.203
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-126-generic N/A
   linux-backports-modules-5.4.0-126-generic  N/A
   linux-firmware 1.173.21
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-126-generic i686
  UpgradeStatus: Upgraded to bionic on 2020-11-18 (698 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/27/2002
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: GF.M1.14
  dmi.board.name: N/A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: OmniBook N32N-101
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrGF.M1.14:bd11/27/2002:svnHewlett-Packard:pnHPOmniBookPC:pvrHPOmniBookXE3GF:rvnHewlett-Packard:rnN/A:rvrOmniBookN32N-101:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP OmniBook PC
  dmi.product.version: HP OmniBook XE3 GF
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 1993242] [NEW] Fix a race condition with AMD PMF and Thinkpad-ACPI

Public bug reported:

Depending on module load order there is a possibility that the AMT mode
selected initially by PMF will be incorrect if thinkpad_acpi has loaded
first.

To avoid this issue adjust the initialization order in the PMF driver.

https://github.com/torvalds/linux/commit/22ee98cb696e95b05a188756d479d382d93559ef

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux-oem-6.0 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-6.0 (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: linux-oem-6.0 (Ubuntu Kinetic)
 Importance: Undecided
 Status: Invalid


** Tags: amd oem-priority originate-from-1992403

** Tags added: amd oem-priority originate-from-1992403

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

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

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

** Description changed:

  Depending on module load order there is a possibility that the AMT mode
  selected initially by PMF will be incorrect if thinkpad_acpi has loaded
  first.
  
  To avoid this issue adjust the initialization order in the PMF driver.
+ 
+ 
https://github.com/torvalds/linux/commit/22ee98cb696e95b05a188756d479d382d93559ef

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

Title:
  Fix a race condition with AMD PMF and Thinkpad-ACPI

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:
  New
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  Depending on module load order there is a possibility that the AMT
  mode selected initially by PMF will be incorrect if thinkpad_acpi has
  loaded first.

  To avoid this issue adjust the initialization order in the PMF driver.

  
https://github.com/torvalds/linux/commit/22ee98cb696e95b05a188756d479d382d93559ef

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


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

[Kernel-packages] [Bug 1993052] Re: iwlwifi Not valid error log pointer 0x00000000 causes WiFi to not work but bluetooth works

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

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

Title:
  iwlwifi Not valid error log pointer 0x causes WiFi to not work
  but bluetooth works

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  For some reason, Ubuntu gets glitched where the Bluetooth works but
  WiFi does not even show up. If I reboot into Windows, it is a similar
  issue (wifi does not show up, but device manager shows Code 10. If I
  disable and enable the adaptor Intel Wireless AC 9560, it sometimes
  works and most times does not). After a few days, the issue goes away.

  Relevent info:
  Laptop: Asus ROG Strig-G 531GT
  Using newest bios 308
  WiFi Adaptor: Intel Wireless AC 9560
  As for wifi connection, usually wifi icon does not even show and stays that 
way throughout the whole uptime. If I reboot a couple of times, this may 
change. However, the wifi I connect to usually is WiFi 5 on 5G channel running 
WPA2. If I use my laptop outside my home, it connects to enterprise WiFi
  Here is the Intel firmware version 
  [5.088777] kernel: iwlwifi :00:14.3: loaded firmware version 
46.fae53a8b.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm


  Here is the relevent Dmesg output 
  [code]
  [   10.661344] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 
0x234c
  [   10.661361] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [   10.909316] iwlwifi :00:14.3: Not valid error log pointer 0x 
for Init uCode
  [   10.909348] iwlwifi :00:14.3: IML/ROM dump:
  [   10.909349] iwlwifi :00:14.3: 0x | IML/ROM error/state
  [   10.909382] iwlwifi :00:14.3: 0x0003 | IML/ROM data1
  [   10.909397] iwlwifi :00:14.3: Fseq Registers:
  [   10.909406] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE
  [   10.909414] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
  [   10.909422] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION
  [   10.909431] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
  [   10.909438] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION
  [   10.909447] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN
  [   10.909456] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID
  [   10.909464] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID
  [   10.909472] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
  [   10.909483] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
  [   10.909494] iwlwifi :00:14.3: 0x485B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
  [   10.909535] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
  [   10.909543] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [   10.909544] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [   14.088686] iwlwifi :00:14.3: Failed to run INIT ucode: -110
  [   14.101296] iwlwifi :00:14.3: retry init count 1
  [   14.104445] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 
160MHz, REV=0x318
  [   14.112168] thermal thermal_zone6: failed to read out thermal zone (-61)
  [   15.141330] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 
0x234c
  [   15.141345] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [   15.390252] iwlwifi :00:14.3: Not valid error log pointer 0x 
for Init uCode
  [   15.390284] iwlwifi :00:14.3: IML/ROM dump:
  [   15.390285] iwlwifi :00:14.3: 0x | IML/ROM error/state
  [   15.390316] iwlwifi :00:14.3: 0x0003 | IML/ROM data1
  [   15.390332] iwlwifi :00:14.3: Fseq Registers:
  [   15.390340] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE
  [   15.390348] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
  [   15.390357] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION
  [   15.390365] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
  [   15.390373] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION
  [   15.390382] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN
  [   15.390390] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID
  [   15.390398] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID
  [   15.390407] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
  [   15.390417] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
  [   15.390428] iwlwifi :00:14.3: 0x485B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
  [   15.390469] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
  [   15.390477] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [   15.390480] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [/code]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04

[Kernel-packages] [Bug 1959681] Re: mic not working on HP-EliteBook-830-G7

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

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

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

Title:
  mic not working on HP-EliteBook-830-G7

Status in linux-firmware package in Ubuntu:
  Expired
Status in linux-firmware source package in Bionic:
  Expired
Status in linux-firmware source package in Focal:
  Expired

Bug description:
  There is no audio input from the built-in mic available on Bionic &
  Focal on certain intel audio hw (00:1f.3 Multimedia audio controller
  [0401]: Intel Corporation Device [8086:02c8]) despite trying different
  kernel cmdline options (snd_hda_intel.dmic_detect=0 or
  snd_intel_dspcfg.dsp_driver=1).

  The behavior was similar on Bionic and Focal - no mic listed in 
alsa/pulseaudio mixers. Additionally the following can be found in the kernel 
log:
sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using 
SOF driver
sof-audio-pci :00:1f.3: enabling device ( -> 0002)
sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found

  The situation is different on impish - on this release the mic is
  available out of the box.

  I made a simple test of overwriting sof files inside Focal's linux-
  firmware package with the contents of firmware-sof-signed package from
  impish finding it solved the issue without any trace of errors in the
  logs.

  The same approach did not work on Bionic (despite similar kernel versions 
used in both 5.4.0) - due to HWE). These are some excerpts from Bionic 
launching impish SOF firmware:
   sof-audio-pci :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:10:0
   sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel
   sof-audio-pci :00:1f.3: firmware boot complete
   sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:10:0
   sof-audio-pci :00:1f.3: warn: topology ABI is more recent than kernel
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp3 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec0_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp2 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec1_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp1 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec0_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Analog CPU Playback 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec1_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Digital CPU Playback 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec2_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Alt Analog CPU 
Playback not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec2_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Analog CPU Capture 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp1_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Digital CPU Capture 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp2_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Alt Analog CPU 
Capture not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp3_out not 
handled

  [ Test Plan ]
  1. Launch Ubuntu desktop on affected hardware.
  2. Open audio mixer (e.g. pulsemixer).
  3. Look for built-in audio input (e.g. Built-in Audio Analog Stereo).

  Expected result:
  Built-in mic is available for use.

  Actual result:
  Built-in mic is missing.

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


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

[Kernel-packages] [Bug 1993071] Re: dmesg -l err iwlwifi Intel(R) Wireless-AC 9560 160MHz, REV=0x430

Adding linux-firmware because firmware update usually help.

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

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

Title:
  dmesg -l err iwlwifi Intel(R) Wireless-AC 9560 160MHz, REV=0x430

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  lots of iwlwifi errors in dmesg.

  loaded firmware version 73.35c0a2c6.0 so-a0-jf-b0-73.ucode op_mode
  iwlmvm

  firmware didn't ACK the reset - continue anyway

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-iwlwifi-generic 5.15.0.50.50
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kimathi1734 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 16 19:29:23 2022
  InstallationDate: Installed on 2022-07-26 (82 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
   
   wlo1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1934:5168 Feature Integration Technology Inc. 
(Fintek) F71610A or F71612A Consumer Infrared Receiver/Transceiver
   Bus 001 Device 002: ID 045e:0800 Microsoft Corp. Wireless keyboard 
(All-in-One-Media)
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUS System Product Name
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=ab6e73ff-42d6-40bd-b4e1-617afcbabcf8 ro quiet splash loglevel=3 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2022
  dmi.bios.release: 16.20
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1620
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME H610I-PLUS D4
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1620:bd08/12/2022:br16.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH610I-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 1959681] Re: mic not working on HP-EliteBook-830-G7

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

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

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

Title:
  mic not working on HP-EliteBook-830-G7

Status in linux-firmware package in Ubuntu:
  Expired
Status in linux-firmware source package in Bionic:
  Expired
Status in linux-firmware source package in Focal:
  Expired

Bug description:
  There is no audio input from the built-in mic available on Bionic &
  Focal on certain intel audio hw (00:1f.3 Multimedia audio controller
  [0401]: Intel Corporation Device [8086:02c8]) despite trying different
  kernel cmdline options (snd_hda_intel.dmic_detect=0 or
  snd_intel_dspcfg.dsp_driver=1).

  The behavior was similar on Bionic and Focal - no mic listed in 
alsa/pulseaudio mixers. Additionally the following can be found in the kernel 
log:
sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using 
SOF driver
sof-audio-pci :00:1f.3: enabling device ( -> 0002)
sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found

  The situation is different on impish - on this release the mic is
  available out of the box.

  I made a simple test of overwriting sof files inside Focal's linux-
  firmware package with the contents of firmware-sof-signed package from
  impish finding it solved the issue without any trace of errors in the
  logs.

  The same approach did not work on Bionic (despite similar kernel versions 
used in both 5.4.0) - due to HWE). These are some excerpts from Bionic 
launching impish SOF firmware:
   sof-audio-pci :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:10:0
   sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel
   sof-audio-pci :00:1f.3: firmware boot complete
   sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:10:0
   sof-audio-pci :00:1f.3: warn: topology ABI is more recent than kernel
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp3 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec0_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp2 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec1_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp1 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec0_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Analog CPU Playback 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec1_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Digital CPU Playback 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec2_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Alt Analog CPU 
Playback not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec2_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Analog CPU Capture 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp1_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Digital CPU Capture 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp2_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Alt Analog CPU 
Capture not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp3_out not 
handled

  [ Test Plan ]
  1. Launch Ubuntu desktop on affected hardware.
  2. Open audio mixer (e.g. pulsemixer).
  3. Look for built-in audio input (e.g. Built-in Audio Analog Stereo).

  Expected result:
  Built-in mic is available for use.

  Actual result:
  Built-in mic is missing.

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


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

[Kernel-packages] [Bug 1959681] Re: mic not working on HP-EliteBook-830-G7

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

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

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

Title:
  mic not working on HP-EliteBook-830-G7

Status in linux-firmware package in Ubuntu:
  Expired
Status in linux-firmware source package in Bionic:
  Expired
Status in linux-firmware source package in Focal:
  Expired

Bug description:
  There is no audio input from the built-in mic available on Bionic &
  Focal on certain intel audio hw (00:1f.3 Multimedia audio controller
  [0401]: Intel Corporation Device [8086:02c8]) despite trying different
  kernel cmdline options (snd_hda_intel.dmic_detect=0 or
  snd_intel_dspcfg.dsp_driver=1).

  The behavior was similar on Bionic and Focal - no mic listed in 
alsa/pulseaudio mixers. Additionally the following can be found in the kernel 
log:
sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using 
SOF driver
sof-audio-pci :00:1f.3: enabling device ( -> 0002)
sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found

  The situation is different on impish - on this release the mic is
  available out of the box.

  I made a simple test of overwriting sof files inside Focal's linux-
  firmware package with the contents of firmware-sof-signed package from
  impish finding it solved the issue without any trace of errors in the
  logs.

  The same approach did not work on Bionic (despite similar kernel versions 
used in both 5.4.0) - due to HWE). These are some excerpts from Bionic 
launching impish SOF firmware:
   sof-audio-pci :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:10:0
   sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel
   sof-audio-pci :00:1f.3: firmware boot complete
   sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:10:0
   sof-audio-pci :00:1f.3: warn: topology ABI is more recent than kernel
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp3 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec0_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp2 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec1_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp1 Tx not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec0_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Analog CPU Playback 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec1_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Digital CPU Playback 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name codec2_in not handled
   sof-audio-pci :00:1f.3: warning: widget type 7 name Alt Analog CPU 
Playback not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name codec2_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Analog CPU Capture 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp1_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Digital CPU Capture 
not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp2_out not 
handled
   sof-audio-pci :00:1f.3: warning: widget type 0 name Alt Analog CPU 
Capture not handled
   sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp3_out not 
handled

  [ Test Plan ]
  1. Launch Ubuntu desktop on affected hardware.
  2. Open audio mixer (e.g. pulsemixer).
  3. Look for built-in audio input (e.g. Built-in Audio Analog Stereo).

  Expected result:
  Built-in mic is available for use.

  Actual result:
  Built-in mic is missing.

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


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

[Kernel-packages] [Bug 1986907] Re: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

[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/1986907

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Jammy:
  Expired

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io  size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io  size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io  size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io  size 0x1000]
  where 
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )

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


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

[Kernel-packages] [Bug 1986907] Re: There are failed messages showing "BAR 13: failed to assign [io size 0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

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

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

Title:
  There are failed messages showing "BAR 13: failed to assign [io size
  0x1000]" in dmesg, syslog, and kern.log in Ubuntu 22.04 LTS

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Jammy:
  Expired

Bug description:
  1. Power on SUT and boot into UEFI setup.
  2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
  3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC 
NVMe RAID disk.
  4. Boot into OS then check system logs to check if there are any unexpected 
failed or error messages. (=> failed, there are failed messages in dmesg, 
/var/log/syslog, and /var/log/kern.log, showing:
  pci 10001:80:02.0: BAR 13: failed to assign [io  size 0x1000]
  pci 10001:80:03.0: BAR 13: failed to assign [io  size 0x1000]
  pci 10001:80:04.0: BAR 13: failed to assign [io  size 0x1000]
  pci 10001:80:05.0: BAR 13: failed to assign [io  size 0x1000]
  where 
  10001:80:02.0 = PCI bridge: Intel Corporation Device 347a (rev 04)
  10001:80:03.0 = PCI bridge: Intel Corporation Device 347b (rev 04)
  10001:80:04.0 = PCI bridge: Intel Corporation Device 347c (rev 04)
  10001:80:05.0 = PCI bridge: Intel Corporation Device 347d (rev 04)
  )

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


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

[Kernel-packages] [Bug 1993223] Re: MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04

Included in linux-firmware/jammy version
20220329.git681281e4-0ubuntu3.6+exp.55 in
https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/linux-
firmware-staging. To be SRU-ed when necessary.

** Tags added: amd oem-priority originate-from-1992818

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

Title:
  MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04

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

Bug description:
  Ryzen 7000 (AM5) desktop processors contain RDNA2 GFX that needs
  firmware to be loaded by amdgpu.

  This firmware has been upstreamed by these commits, which are already
  part of Kinetic (version 20220923.gitf09bebf3-0ubuntu1)

  db6db36a amdgpu: add firmware for VCN 3.1.2 IP block
  3647da5c amdgpu: add firmware for SDMA 5.2.6 IP block
  639b5c13 amdgpu: add firmware for PSP 13.0.5 IP block
  76589464 amdgpu: add firmware for GC 10.3.6 IP block
  427ca6ca amdgpu: add firmware for DCN 3.1.5 IP block

  Matching kernel code for this processor is already upstreamed in 6.0
  kernel, and so this should work with OEM-6.0.

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


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

[Kernel-packages] [Bug 1993240] [NEW] amd_sfh modprobe fails when no sensor reported from AMD MP2

Public bug reported:

Fix amd_sfh to make each sensor with proper initialization & resource
allocation during MP2 loaded.

To be in v6.1

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/drivers/hid/amd-sfh-
hid?h=next-20221010=68266bdcceec10ea364e62c63732cd6fe5a256a8

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/drivers/hid/amd-sfh-
hid?h=next-20221010=beb18bb22cd4fb88648bb2925d56f36131c1ac21

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux-oem-6.0 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-6.0 (Ubuntu Jammy)
 Importance: Undecided
 Status: Confirmed

** Affects: linux-oem-6.0 (Ubuntu Kinetic)
 Importance: Undecided
 Status: Invalid


** Tags: amd oem-priority originate-from-1992402

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

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

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

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

** Tags added: amd oem-priority originate-from-1992402

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

Title:
  amd_sfh modprobe fails when no sensor reported from AMD MP2

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:
  Confirmed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  Fix amd_sfh to make each sensor with proper initialization & resource
  allocation during MP2 loaded.

  To be in v6.1

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/drivers/hid/amd-sfh-
  hid?h=next-20221010=68266bdcceec10ea364e62c63732cd6fe5a256a8

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/drivers/hid/amd-sfh-
  hid?h=next-20221010=beb18bb22cd4fb88648bb2925d56f36131c1ac21

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


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

[Kernel-packages] [Bug 1992474] Re: [Lenovo ThinkPad P1 Gen2] Flickering started right after install

2022-10-17 Thread Daniel van Vugt

When the problem is happening, please run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.


** Summary changed:

- Flickering started right after install
+ [Lenovo ThinkPad P1 Gen2] Flickering started right after install

** Tags added: i915 multigpu nvidia

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

Title:
  [Lenovo ThinkPad P1 Gen2] Flickering started right after install

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My computer is a Lenovo Thinkpad p-Series Gen 2 with Intel Core i9.
  I've tried updating my grub file as is suggested in Bugs #1970426,
  #1958191, and #1973676.

  That is, I've tried

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0
  intel_idle.max_cstate=2"

  And, I've tried cstate=4.

  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/controlC0:  moon   2093 F pulseaudio
   /dev/snd/controlC1:  moon   2093 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 11 08:05:20 2022
  InstallationDate: Installed on 2020-03-29 (926 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QTCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=39110848-f164-47a5-bf96-fda0216c46fb ro quiet splash i915.enable_dc=0 
intel_idle.max_cstate=2 vt.handoff=7
  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: Upgraded to jammy on 2022-08-20 (51 days ago)
  dmi.bios.date: 05/07/2020
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET44W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QTCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:br1.31:efr1.23:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QT_BU_Think_FM_ThinkPadP1Gen2:
  dmi.product.family: ThinkPad P1 Gen2
  dmi.product.name: 20QTCTO1WW
  dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen2
  dmi.product.version: ThinkPad P1 Gen2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1612916] Re: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

Can you please attach dmesg?

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

Title:
  [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

Status in linux package in Ubuntu:
  Confirmed
Status in Arch Linux:
  New
Status in linux package in Debian:
  New

Bug description:
  On initial boot, sound on internal speakers is working. After standby
  it doesn work anymore, but a analog headset does. Switching around in
  pavucontrol doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.

  Toshiba/Dynabook Portege Z20T-C:
  
https://support.dynabook.com/support/modelHome?freeText=1200015981=785

  WORKAROUND: Use suspend to disk.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

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


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

[Kernel-packages] [Bug 1993078] Re: immediate crash on boot HP Omnibook XE3-GF

Does the laptop support AMD64? i686 is quite old and won't be support in
newer releases..

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

Title:
  immediate crash on boot HP Omnibook XE3-GF

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

Bug description:
  Immediate crash upon entering boot with linux-image-5.4.0-128-generic
  on HP Omnibook XE3-GF

  Prior versions up to linux-image-5.4.0-126-generic work fine

  
  I 8.3938581 Hardware name: Hewlett-Packard HP OmniBook PC GF M1 14 11/27/2002

  [ 8.3931371 EIP: switch_to_asm+0x44/0x54

  T A.3931941 Code: 54 e8 41 d2 bb 10 00 00 00 e8 07 00 00 00 f3 98 Of
  ae e8 eb 19 e8 87 00 00 00 f3 98 Of ae e8 eb f9 4b 75 e5 81 c4 80 00
  00 00 <0f> ae e8 9d

  Se 5f 5b 5d e9 9f ca 65 ff 8d 76 00 55 89 e5 50 e8 a3

  L 8.393297] EAX: d22005c0 EBX:  ECX: 176a5b33 EDX: f653da00 [
  0.3933571 ESI:  EDI: f75f2d40 EBP: d21f9e88 ESP: f6537f94

  L 8.393455] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS:
  00210082

  [ 0.3935411 CRO: 80050033 CRZ: ffbff000 CR3: 1242e000 CR4: 06f0

  [ 0.393640] Call Trace:

  [ 8.393746] Modules linked in:

  L 8.393846] ---[ end trace 7de00da7437d5ef2

  [ 8.393932] EIP: _switch_to_asm+0x44/0x54

  [ 8.394814] Code: 54 e8 41 d2 bb 10 00 00 00 e8 07 00 00 00 f3 90 of
  ae e8 eb

  f9 e8 07 00 00 00 f3 98 Of ae e8 eb f9 4b 75 e5 81 c4 80 00 00 00 <0f>
  ae e8 9d Se 5f 5b 5d e9 9f ca 65 ff 8d 76 88 55 89 e5 58 e8 a3

  [ 8.394248] EAX: d22005c8 EBX:  ECX: 176a5b33 EDX: f653da00

  [ 0.394388] ESI:  EDI: f75f2d48 EBP: d21f9e88 ESP: f6537f94 [
  8.394486] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS:
  00210082

  [ 0.394492] CRO: 80050033 CRZ: ffbff808 CR3: 1242e800 CR4: 06f8

  [ 0.394594] Kernel panic not syncing: Attempted to kill the idle task!

  [ 8.394683]---[ end Kernel panic not syncing: Attempted to kill the idle 
task! ]---
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-126-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCI [ESS Allegro PCI], device 0: Allegro [Allegro]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCI [ESS Allegro PCI], device 0: Allegro [Allegro]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  irgendjemand   1071 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCI'/'ESS Allegro PCI at 0x2000, irq 5'
 Mixer name : 'ESS Technology ESS1988'
 Components : 'AC97a:45838308'
 Controls  : 25
 Simple ctrls  : 19
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (1615 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
  IwConfig:
   enp2s8no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP OmniBook PC
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-126-generic 
root=UUID=39604362-f78a-488e-9780-2a750f169be6 ro recovery nomodeset 
dis_ucode_ldr
  ProcVersionSignature: Ubuntu 5.4.0-126.142~18.04.1-generic 5.4.203
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-126-generic N/A
   linux-backports-modules-5.4.0-126-generic  N/A
   linux-firmware 1.173.21
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-126-generic i686
  UpgradeStatus: Upgraded to bionic on 2020-11-18 (698 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/27/2002
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: GF.M1.14
  dmi.board.name: N/A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: OmniBook N32N-101
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrGF.M1.14:bd11/27/2002:svnHewlett-Packard:pnHPOmniBookPC:pvrHPOmniBookXE3GF:rvnHewlett-Packard:rnN/A:rvrOmniBookN32N-101:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP OmniBook PC
  dmi.product.version: HP OmniBook XE3 GF
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 1993217] Re: HDMI audio not available RS880 between 4.9.177 and 4.9.178

4.9 is quite old. Please try mainline kernel v6.0.

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

Title:
  HDMI audio not available RS880 between 4.9.177 and 4.9.178

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is on my friend laptop with his TV.
  HDMI audio not available in pavucontrol (profile say unplugged, unavailable) 
in kernel versions with bugs.
  It is just shown as an audio output (HDMI audio) on kernels where it is 
working.
  When not working, I can play with aplay -D HDMI ... 
  When working... I select HDMI audio in output, and test sound ok, Youtube 
videos ok, etc.

  4.9.177 working.
  4.9.178 not working.

  I suspect commit 72cf0b07418a9c8349aa9137194b1ccba6e54a9d because it
  is between those versions, and is related to audio (realtek in part).

  More info at:
  https://forums.linuxmint.com/viewtopic.php?f=49=383607=2246352#p2246352
  although the laptop now runs ... 17.10 I think (a version with a not broken 
kernel).

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


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

[Kernel-packages] [Bug 1993223] [NEW] MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04

Public bug reported:

Ryzen 7000 (AM5) desktop processors contain RDNA2 GFX that needs
firmware to be loaded by amdgpu.

This firmware has been upstreamed by these commits, which are already
part of Kinetic (version 20220923.gitf09bebf3-0ubuntu1)

db6db36a amdgpu: add firmware for VCN 3.1.2 IP block
3647da5c amdgpu: add firmware for SDMA 5.2.6 IP block
639b5c13 amdgpu: add firmware for PSP 13.0.5 IP block
76589464 amdgpu: add firmware for GC 10.3.6 IP block
427ca6ca amdgpu: add firmware for DCN 3.1.5 IP block

Matching kernel code for this processor is already upstreamed in 6.0
kernel, and so this should work with OEM-6.0.

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux-firmware (Ubuntu Jammy)
 Importance: Undecided
 Status: Confirmed

** Affects: linux-firmware (Ubuntu Kinetic)
 Importance: Undecided
 Status: Fix Released

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

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

** Changed in: linux-firmware (Ubuntu Kinetic)
   Status: New => Fix Released

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

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

Title:
  MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Confirmed
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  Ryzen 7000 (AM5) desktop processors contain RDNA2 GFX that needs
  firmware to be loaded by amdgpu.

  This firmware has been upstreamed by these commits, which are already
  part of Kinetic (version 20220923.gitf09bebf3-0ubuntu1)

  db6db36a amdgpu: add firmware for VCN 3.1.2 IP block
  3647da5c amdgpu: add firmware for SDMA 5.2.6 IP block
  639b5c13 amdgpu: add firmware for PSP 13.0.5 IP block
  76589464 amdgpu: add firmware for GC 10.3.6 IP block
  427ca6ca amdgpu: add firmware for DCN 3.1.5 IP block

  Matching kernel code for this processor is already upstreamed in 6.0
  kernel, and so this should work with OEM-6.0.

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


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

[Kernel-packages] [Bug 1740736] Re: The it87.ko driver is too old and does not support newer chipsets (such as Z370).

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

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

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

Title:
  The it87.ko driver is too old and does not support newer chipsets
  (such as Z370).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Summary: Thermal sensors are not accessible due to being unsupported
  by the it87.ko module in linux-image-extra which does not include the
  it8686 model line among others..

  Expected behavior:

  $ journalctl | grep it87:
  Apr 20 21:36:00 lakshmi kernel: it87: it87 driver version v1.0-38-g948ad8d
  Apr 20 21:36:00 lakshmi kernel: it87: Found IT8686E chip at 0xa40, revision 2
  Apr 20 21:36:00 lakshmi kernel: it87: Beeping is supported
  Apr 20 21:36:00 lakshmi kernel: it87: Found IT8792E/IT8795E chip at 0xa60, 
revision 3
  Apr 20 21:36:00 lakshmi kernel: it87: Beeping is supported

  Actual behavior:

  $ journalctl | grep it87:
  Apr 20 20:56:31 lakshmi kernel: it87: Found IT8733E chip at 0xa60, revision 3
  Apr 20 20:56:31 lakshmi kernel: it87: Beeping is supported

  
  Reproducing:

  sudo modprobe it87
  journalctl | grep it87:
  Apr 20 20:56:31 lakshmi kernel: it87: Found IT8733E chip at 0xa60, revision 3
  Apr 20 20:56:31 lakshmi kernel: it87: Beeping is supported

  ...

  sudo rmmod it87

  git clone https://github.com/groeck/it87.git
  cd it87/
  make
  sudo make install
  sudo modprobe it87
  $ journalctl | grep it87:
  Apr 20 21:36:00 lakshmi kernel: it87: it87 driver version v1.0-38-g948ad8d
  Apr 20 21:36:00 lakshmi kernel: it87: Found IT8686E chip at 0xa40, revision 2
  Apr 20 21:36:00 lakshmi kernel: it87: Beeping is supported
  Apr 20 21:36:00 lakshmi kernel: it87: Found IT8792E/IT8795E chip at 0xa60, 
revision 3
  Apr 20 21:36:00 lakshmi kernel: it87: Beeping is supported

  
  Details:

  $ uname -rsv
  Linux 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018

  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

  
  $ sudo dmidecode |grep -i product | uniq
Product Name: AX370-Gaming 5


  Background:

  Filed a bug report as per question:
  https://answers.launchpad.net/ubuntu/+question/662421

  I'm trying to run lm_sensors on my brand new motherboard (Gigabyte
  Technology Co., Ltd. Z370 AORUS Ultra Gaming-CF) using the Z370
  chipset, and according to the author/maintainer of lm_sensors/it87
  driver, fan controls would be supported by chip it8686.

  Currently such chip is supported only in it87 version
  https://github.com/groeck/it87; unfortunately both Ubuntu's new LTS
  Bionic and Torvalds' repositories have got an outdated version of this
  driver (and possible lm_sensors itself):

  * 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/tree/drivers/hwmon/it87.c
  * https://github.com/torvalds/linux/blob/master/drivers/hwmon/it87.c

  Can you please update Bionic (at least) to feature this updated driver?
  Controlling fans speed and other motherboard parameters would be great, 
especially on new hardware.

  Thanks!

  Full discussion thread with driver maintainer here:
  https://github.com/groeck/lm-sensors/issues/44

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


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

[Kernel-packages] [Bug 1992517] Re: rtw88_8822ce: unable to ping anything, "failed to write TX skb to HCI" and "failed to pusk skb, ret -28" in dmesg