date:20230924

This change was made by a bot.

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

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

Title:
  No HDMI in Nvidia on-demand mode

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

Bug description:
  Hi,

  Legion laptop with Nvidia.
  - Nouveau : no hdmi
  - Nvidia 535 dynamic graphics : no HDMI (screen not detected)
  - Nvidia 535 discrete graphics : HDMI is detected

  So I suppose this bug to be linked to Intel GPU.

  All was ok with previous 6.3 kernel.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fthx   3395 F wireplumber
   /dev/snd/controlC1:  fthx   3395 F wireplumber
   /dev/snd/seq:fthx   3390 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-09-15 (723 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230815.git0e048b06-0ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-5-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-03-06 (186 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/10/2023
  dmi.bios.release: 1.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J2CN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 5 Pro 16IAH7H
  dmi.ec.firmware.release: 1.54
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ2CN54WW:bd07/10/2023:br1.54:efr1.54:svnLENOVO:pn82RF:pvrLegion5Pro16IAH7H:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion5Pro16IAH7H:skuLENOVO_MT_82RF_BU_idea_FM_Legion5Pro16IAH7H:
  dmi.product.family: Legion 5 Pro 16IAH7H
  dmi.product.name: 82RF
  dmi.product.sku: LENOVO_MT_82RF_BU_idea_FM_Legion 5 Pro 16IAH7H
  dmi.product.version: Legion 5 Pro 16IAH7H
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033735/+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 2033735] Re: [mantic] New 6.5.0.2 kernel + Intel GPU = no HDMI

> Again, the issue is present using Nouveau too in 6.5.

I assume you mean the main bug here and not those log messages because
'nvidia-drm' is the proprietary driver meaning Nouveau shouldn't be
loaded.

** Summary changed:

- [mantic] New 6.5.0.2 kernel + Intel GPU = no HDMI
+ No HDMI in Nvidia on-demand mode

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

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

** Tags added: multimonitor 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/2033735

Title:
  No HDMI in Nvidia on-demand mode

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

Bug description:
  Hi,

  Legion laptop with Nvidia.
  - Nouveau : no hdmi
  - Nvidia 535 dynamic graphics : no HDMI (screen not detected)
  - Nvidia 535 discrete graphics : HDMI is detected

  So I suppose this bug to be linked to Intel GPU.

  All was ok with previous 6.3 kernel.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fthx   3395 F wireplumber
   /dev/snd/controlC1:  fthx   3395 F wireplumber
   /dev/snd/seq:fthx   3390 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-09-15 (723 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230815.git0e048b06-0ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-5-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-03-06 (186 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/10/2023
  dmi.bios.release: 1.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J2CN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 5 Pro 16IAH7H
  dmi.ec.firmware.release: 1.54
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ2CN54WW:bd07/10/2023:br1.54:efr1.54:svnLENOVO:pn82RF:pvrLegion5Pro16IAH7H:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion5Pro16IAH7H:skuLENOVO_MT_82RF_BU_idea_FM_Legion5Pro16IAH7H:
  dmi.product.family: Legion 5 Pro 16IAH7H
  dmi.product.name: 82RF
  dmi.product.sku: LENOVO_MT_82RF_BU_idea_FM_Legion 5 Pro 16IAH7H
  dmi.product.version: Legion 5 Pro 16IAH7H
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033735/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

Disabling/reenabling Wayland didn't help for my setup.  I have seen
other reports elsewhere about issues with sound for those using
motherboards containing the B550 chipset.  The success reported above
was encouraging.  Knock on wood the soundblaster audigy pcix card I
ordered will arrive soon and I'll test that with this chipset.

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

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

Bug description:
  [Impact]
  For amdgpu/i915, hdmi audio output device has disappeared.

  [Fix]
  The latest fix for the non-contiguous memalloc helper changed the
  allocation method for a non-IOMMU system to use only the fallback
  allocator.  This should have worked, but it caused a problem sometimes
  when too many non-contiguous pages are allocated that can't be treated
  by HD-audio controller.
  
  As a quirk workaround, go back to the original strategy: use
  dma_alloc_noncontiguous() at first, and apply the fallback only when
  it fails, but only for non-IOMMU case

  [Test Case]
  1. boot with kernel applied the patches.
  2. check the cards in /proc/asound/cards.
 Get the hdmi cards.

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xe232 irq 137
   1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe226 irq 134

  [Where problems could occur]
  Low, this is just workaround and may have a better solution in the future.

  [Misc]
  All patches has been landed on OEM-6.1 and lunar.

  ~~
  CLARIFICATION: Just to avoid any confusion for those coming to this bug 
report; the "Jammy: invalid" status above does *not* mean that this bug doesn't 
affect jammy -- it does, and the kernel team is aware of this. All it reflects 
is that the fix has to go into the kinetic kernel package which will then flow 
into the kernel-hwe package implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the dmesg of the -32 kernel, but not in the -35
  kernel's log. Meanwhile, the following lines appear in the -35
  kernel's log but not in the -32:

  hdaudio hdaudioC0D0: no AFG or MFG node found
  snd_hda_intel :2b:00.1: no codecs initialized

  I'll also attach the output of "pactl list" under each kernel (this
  shows the HDMI audio sink showing up under -32, but not -35) just in
  case that helps shed any light on things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2037212] Re: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)

Also mentioned in bug 2017224

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

Title:
  ConfigurationDirectory 'bluetooth' already exists but the mode is
  different. (File system: 755 ConfigurationDirectoryMode: 555)

Status in bluez package in Ubuntu:
  New
Status in bluez package in Debian:
  New

Bug description:
  Hi,

  when my system boots it logs the following warning in the journal:

  $ journalctl | grep ConfigurationDirectory
  Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 
ConfigurationDirectoryMode: 555)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: bluez 5.68-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 13:28:20 2023
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 70:9C:D1:50:1F:7B  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037212/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

so I tried a 6500xt radeon, 6700xt, 6800xt, they all didn't like the
asmedia asm1083 pcix soundcard.  I think the soundcard drivers for the
asmedia pcix card I tested out are bad or the card it'self is defective,
kernel failure and reboot after 5 seconds of sound.

I purchased and installed this card because the MSI B550 chipset
motherboard with any of the video cards I tried has no sound.

I noticed some people reporting better luck with some kernels above.
the 5.15.0-84-generic kernel I just tested made no difference in my
situation.

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

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

Bug description:
  [Impact]
  For amdgpu/i915, hdmi audio output device has disappeared.

  [Fix]
  The latest fix for the non-contiguous memalloc helper changed the
  allocation method for a non-IOMMU system to use only the fallback
  allocator.  This should have worked, but it caused a problem sometimes
  when too many non-contiguous pages are allocated that can't be treated
  by HD-audio controller.
  
  As a quirk workaround, go back to the original strategy: use
  dma_alloc_noncontiguous() at first, and apply the fallback only when
  it fails, but only for non-IOMMU case

  [Test Case]
  1. boot with kernel applied the patches.
  2. check the cards in /proc/asound/cards.
 Get the hdmi cards.

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xe232 irq 137
   1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe226 irq 134

  [Where problems could occur]
  Low, this is just workaround and may have a better solution in the future.

  [Misc]
  All patches has been landed on OEM-6.1 and lunar.

  ~~
  CLARIFICATION: Just to avoid any confusion for those coming to this bug 
report; the "Jammy: invalid" status above does *not* mean that this bug doesn't 
affect jammy -- it does, and the kernel team is aware of this. All it reflects 
is that the fix has to go into the kinetic kernel package which will then flow 
into the kernel-hwe package implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the dmesg of the -32 kernel, but not in the -35
  kernel's log. Meanwhile, the following lines appear in the -35
  kernel's log but not in the -32:

  hdaudio hdaudioC0D0: no AFG or MFG node found
  snd_hda_intel :2b:00.1: no codecs initialized

  I'll also attach the output of "pactl list" under each kernel (this
  shows the HDMI audio sink showing up under -32, but not -35) just in
  case that helps shed any light on things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

Ok I managed to get back onto 5.15.x,
still no sound options available other than "Sortie fictive" (Fake output).  - 
my OS is in French language.

5.15.0-84-generic #93-Ubuntu SMP Tue Sep 5 17:16:10 UTC 2023

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"


12:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 HDMI Audio 
[Radeon RX 6800/6800 XT / 6900 XT]
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 HDMI Audio 
[Radeon RX 6800/6800 XT / 6900 XT]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel


30:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High 
Definition Audio Controller
Subsystem: Micro-Star International Co., Ltd. [MSI] Renoir Radeon High 
Definition Audio Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

Meanwhile, I've tried 3rd party made in china asmedia asm1083 pcix
soundcard, it crashes the system after 5 seconds of playing sound.  as
soon as sound started, crash.  Removed the soundcard, no more crashing.
This happened with 6.2 kernel, I tried many kernels.

Now I'm on 5.15.0-84-generic (assembled this new computer for my
daughter) and with the Rx series video cards (I have 3 of them, 6500xt,
6700xt, 6800xt, no sound when used with the MSI b550 chipset
motherboard.

On an older AM3 motherboard that my son has there is sound but I'm not
sure if it's the AC97 chipset or the hdmi doing the sound on that
computer which is working, haven't checked that.


This MSI B550 running AMD Ryzen 5500 has no sound.

I've ordered a sound blaster audigy card now, hopefully better luck than
the knockoff card that claimed to be linux ready.

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

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

Bug description:
  [Impact]
  For amdgpu/i915, hdmi audio output device has disappeared.

  [Fix]
  The latest fix for the non-contiguous memalloc helper changed the
  allocation method for a non-IOMMU system to use only the fallback
  allocator.  This should have worked, but it caused a problem sometimes
  when too many non-contiguous pages are allocated that can't be treated
  by HD-audio controller.
  
  As a quirk workaround, go back to the original strategy: use
  dma_alloc_noncontiguous() at first, and apply the fallback only when
  it fails, but only for non-IOMMU case

  [Test Case]
  1. boot with kernel applied the patches.
  2. check the cards in /proc/asound/cards.
 Get the hdmi cards.

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xe232 irq 137
   1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe226 irq 134

  [Where problems could occur]
  Low, this is just workaround and may have a better solution in the future.

  [Misc]
  All patches has been landed on OEM-6.1 and lunar.

  ~~
  CLARIFICATION: Just to avoid any confusion for those coming to this bug 
report; the "Jammy: invalid" status above does *not* mean that this bug doesn't 
affect jammy -- it does, and the kernel team is aware of this. All it reflects 
is that the fix has to go into the kinetic kernel package which will then flow 
into the kernel-hwe package implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as

[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

joseph@joseph-desktop:~$ sudo apt install linux-image-generic

linux-image-generic est déjà la version la plus récente (5.15.0.84.81).
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.

joseph@joseph-desktop:~$ uname -a
Linux joseph-desktop 6.2.0-33-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 
Thu Sep  7 10:33:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux


I uninstalled linux-image-generic-hwe-22.04 but I'm still stuck on 
6.2.0-33-generic, I'll try again

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

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

Bug description:
  [Impact]
  For amdgpu/i915, hdmi audio output device has disappeared.

  [Fix]
  The latest fix for the non-contiguous memalloc helper changed the
  allocation method for a non-IOMMU system to use only the fallback
  allocator.  This should have worked, but it caused a problem sometimes
  when too many non-contiguous pages are allocated that can't be treated
  by HD-audio controller.
  
  As a quirk workaround, go back to the original strategy: use
  dma_alloc_noncontiguous() at first, and apply the fallback only when
  it fails, but only for non-IOMMU case

  [Test Case]
  1. boot with kernel applied the patches.
  2. check the cards in /proc/asound/cards.
 Get the hdmi cards.

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xe232 irq 137
   1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe226 irq 134

  [Where problems could occur]
  Low, this is just workaround and may have a better solution in the future.

  [Misc]
  All patches has been landed on OEM-6.1 and lunar.

  ~~
  CLARIFICATION: Just to avoid any confusion for those coming to this bug 
report; the "Jammy: invalid" status above does *not* mean that this bug doesn't 
affect jammy -- it does, and the kernel team is aware of this. All it reflects 
is that the fix has to go into the kinetic kernel package which will then flow 
into the kernel-hwe package implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the dmesg of the -32 kernel, but not in the -35
  kernel's log. Meanwhile, the following lines appear in the -35
  kernel's log but not in the -32:

  hdaudio hdaudioC0D0: no AFG or MFG node found
  snd_hda_intel :2b:00.1: no codecs initialized

  I'll also attach the output of "pactl list" under each kernel (this
  shows the HDMI audio sink showing up under -32, but not -35) just in
  case that helps shed any light on things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

2023-09-24 Thread koba

@Joseph,
please try
#5.15
sudo apt install linux-image-generic
#6.2
sudo apt install linux-image-generic-hwe-22.04

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

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

Bug description:
  [Impact]
  For amdgpu/i915, hdmi audio output device has disappeared.

  [Fix]
  The latest fix for the non-contiguous memalloc helper changed the
  allocation method for a non-IOMMU system to use only the fallback
  allocator.  This should have worked, but it caused a problem sometimes
  when too many non-contiguous pages are allocated that can't be treated
  by HD-audio controller.
  
  As a quirk workaround, go back to the original strategy: use
  dma_alloc_noncontiguous() at first, and apply the fallback only when
  it fails, but only for non-IOMMU case

  [Test Case]
  1. boot with kernel applied the patches.
  2. check the cards in /proc/asound/cards.
 Get the hdmi cards.

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xe232 irq 137
   1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe226 irq 134

  [Where problems could occur]
  Low, this is just workaround and may have a better solution in the future.

  [Misc]
  All patches has been landed on OEM-6.1 and lunar.

  ~~
  CLARIFICATION: Just to avoid any confusion for those coming to this bug 
report; the "Jammy: invalid" status above does *not* mean that this bug doesn't 
affect jammy -- it does, and the kernel team is aware of this. All it reflects 
is that the fix has to go into the kinetic kernel package which will then flow 
into the kernel-hwe package implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the dmesg of the -32 kernel, but not in the -35
  kernel's log. Meanwhile, the following lines appear in the -35
  kernel's log but not in the -32:

  hdaudio hdaudioC0D0: no AFG or MFG node found
  snd_hda_intel :2b:00.1: no codecs initialized

  I'll also attach the output of "pactl list" under each kernel (this
  shows the HDMI audio sink showing up under -32, but not -35) just in
  case that helps shed any light on things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

ah, actually I was fiddling around with kernel installers and ended up with 
6.2.0-33-generic
now I have to figure out how to put 22.04 back on the regular 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/2009136

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

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

Bug description:
  [Impact]
  For amdgpu/i915, hdmi audio output device has disappeared.

  [Fix]
  The latest fix for the non-contiguous memalloc helper changed the
  allocation method for a non-IOMMU system to use only the fallback
  allocator.  This should have worked, but it caused a problem sometimes
  when too many non-contiguous pages are allocated that can't be treated
  by HD-audio controller.
  
  As a quirk workaround, go back to the original strategy: use
  dma_alloc_noncontiguous() at first, and apply the fallback only when
  it fails, but only for non-IOMMU case

  [Test Case]
  1. boot with kernel applied the patches.
  2. check the cards in /proc/asound/cards.
 Get the hdmi cards.

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xe232 irq 137
   1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe226 irq 134

  [Where problems could occur]
  Low, this is just workaround and may have a better solution in the future.

  [Misc]
  All patches has been landed on OEM-6.1 and lunar.

  ~~
  CLARIFICATION: Just to avoid any confusion for those coming to this bug 
report; the "Jammy: invalid" status above does *not* mean that this bug doesn't 
affect jammy -- it does, and the kernel team is aware of this. All it reflects 
is that the fix has to go into the kinetic kernel package which will then flow 
into the kernel-hwe package implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the dmesg of the -32 kernel, but not in the -35
  kernel's log. Meanwhile, the following lines appear in the -35
  kernel's log but not in the -32:

  hdaudio hdaudioC0D0: no AFG or MFG node found
  snd_hda_intel :2b:00.1: no codecs initialized

  I'll also attach the output of "pactl list" under each kernel (this
  shows the HDMI audio sink showing up under -32, but not -35) just in
  case that helps shed any light on things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

@ivanto, trying 5.15.0-83 now

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

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

Bug description:
  [Impact]
  For amdgpu/i915, hdmi audio output device has disappeared.

  [Fix]
  The latest fix for the non-contiguous memalloc helper changed the
  allocation method for a non-IOMMU system to use only the fallback
  allocator.  This should have worked, but it caused a problem sometimes
  when too many non-contiguous pages are allocated that can't be treated
  by HD-audio controller.
  
  As a quirk workaround, go back to the original strategy: use
  dma_alloc_noncontiguous() at first, and apply the fallback only when
  it fails, but only for non-IOMMU case

  [Test Case]
  1. boot with kernel applied the patches.
  2. check the cards in /proc/asound/cards.
 Get the hdmi cards.

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xe232 irq 137
   1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe226 irq 134

  [Where problems could occur]
  Low, this is just workaround and may have a better solution in the future.

  [Misc]
  All patches has been landed on OEM-6.1 and lunar.

  ~~
  CLARIFICATION: Just to avoid any confusion for those coming to this bug 
report; the "Jammy: invalid" status above does *not* mean that this bug doesn't 
affect jammy -- it does, and the kernel team is aware of this. All it reflects 
is that the fix has to go into the kinetic kernel package which will then flow 
into the kernel-hwe package implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the dmesg of the -32 kernel, but not in the -35
  kernel's log. Meanwhile, the following lines appear in the -35
  kernel's log but not in the -32:

  hdaudio hdaudioC0D0: no AFG or MFG node found
  snd_hda_intel :2b:00.1: no codecs initialized

  I'll also attach the output of "pactl list" under each kernel (this
  shows the HDMI audio sink showing up under -32, but not -35) just in
  case that helps shed any light on things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2037161] Missing required logs.

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 2037161

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

Title:
  drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -110

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I noticed that when I choose Wayland to logon to my Ubuntu 23.04
  desktop PC, the display would crash at least once within 6 hours.
  Crash means total dark screen. Mouse,keyboard, or replugging the HDMI
  cable doesn't have any effects. Once the display crashes, ssh is
  possible but reboot commands would time out. sudo commands take more
  than 10 seconds. The problem does not occur if I choose xorg to logon
  to the desktop. The hardware specifications are:

  amd-ryzen5-4600g
  description: Computer
  width: 64 bits
  capabilities: smp vsyscall32
    *-core
     description: Motherboard
     physical id: 0
   *-memory
    description: System memory
    physical id: 0
    size: 15GiB
   *-cpu
    product: AMD Ryzen 5 4600G with Radeon Graphics
    vendor: Advanced Micro Devices [AMD]
    physical id: 1
    bus info: cpu@0
    version: 23.96.1
    size: 4291MHz
    capacity: 4307MHz
    width: 64 bits

  Kernel info:
  uname -a
  Linux amd-ryzen5-4600g 6.2.0-32-generic #32-Ubuntu SMP PREEMPT_DYNAMIC Mon 
Aug 14 10:03:50 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  more logs in the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037161/+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 2037161] Re: drm:amdgpu_job_timedout [amdgpu]] ERROR GPU Recovery Failed: -110

** Tags added: lunar

** Package changed: gdm3 (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/2037161

Title:
  drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -110

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I noticed that when I choose Wayland to logon to my Ubuntu 23.04
  desktop PC, the display would crash at least once within 6 hours.
  Crash means total dark screen. Mouse,keyboard, or replugging the HDMI
  cable doesn't have any effects. Once the display crashes, ssh is
  possible but reboot commands would time out. sudo commands take more
  than 10 seconds. The problem does not occur if I choose xorg to logon
  to the desktop. The hardware specifications are:

  amd-ryzen5-4600g
  description: Computer
  width: 64 bits
  capabilities: smp vsyscall32
    *-core
     description: Motherboard
     physical id: 0
   *-memory
    description: System memory
    physical id: 0
    size: 15GiB
   *-cpu
    product: AMD Ryzen 5 4600G with Radeon Graphics
    vendor: Advanced Micro Devices [AMD]
    physical id: 1
    bus info: cpu@0
    version: 23.96.1
    size: 4291MHz
    capacity: 4307MHz
    width: 64 bits

  Kernel info:
  uname -a
  Linux amd-ryzen5-4600g 6.2.0-32-generic #32-Ubuntu SMP PREEMPT_DYNAMIC Mon 
Aug 14 10:03:50 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  more logs in the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037161/+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 2037161] [NEW] drm:amdgpu_job_timedout [amdgpu]] ERROR GPU Recovery Failed: -110

2023-09-24 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

I noticed that when I choose Wayland to logon to my Ubuntu 23.04 desktop
PC, the display would crash at least once within 6 hours. Crash means
total dark screen. Mouse,keyboard, or replugging the HDMI cable doesn't
have any effects. Once the display crashes, ssh is possible but reboot
commands would time out. sudo commands take more than 10 seconds. The
problem does not occur if I choose xorg to logon to the desktop. The
hardware specifications are:

amd-ryzen5-4600g
description: Computer
width: 64 bits
capabilities: smp vsyscall32
  *-core
   description: Motherboard
   physical id: 0
 *-memory
  description: System memory
  physical id: 0
  size: 15GiB
 *-cpu
  product: AMD Ryzen 5 4600G with Radeon Graphics
  vendor: Advanced Micro Devices [AMD]
  physical id: 1
  bus info: cpu@0
  version: 23.96.1
  size: 4291MHz
  capacity: 4307MHz
  width: 64 bits

Kernel info:
uname -a
Linux amd-ryzen5-4600g 6.2.0-32-generic #32-Ubuntu SMP PREEMPT_DYNAMIC Mon Aug 
14 10:03:50 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

more logs in the attachment.

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


** Tags: amdgpu lunar
-- 
drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -110
https://bugs.launchpad.net/bugs/2037161
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 2029372] Re: Remove force_probe for i915 on MTL platforms to ease the development process

** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: hwe-next
   Status: In Progress => Fix Released

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

Title:
  Remove force_probe for i915 on MTL platforms to ease the development
  process

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Won't Fix
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  To remove force_probe for i915 on MTL platforms to ease the
  development process.

  [Fix]

  Sauced fix to remove force_probe flag.

  [Test Case]

  i915 should then be enabled automatically without the need of
  i915.force_probe= in boot parameters.

  [Where problems could occur]

  This is for the convenience of early development. i915 may not be
  stable/fully functional on MTL platforms.

  [Other Info]

  While this is only meant for kernel >= 6.5, only oem-6.5 is nominated
  for fix so far.

  == original bug report ==

  i915 on MTL platforms still takes an additional boot parameter
  i915.force_probe= to drive the graphic device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2029372/+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 2036802] Re: HDMI not detected on HP Zbook Power 15 G9

In that case this sounds like a bug in Xorg/Nvidia/Mutter, but not the
kernel because the Intel GPU is not being used.

Please connect the monitor and then run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

** Package changed: linux-hwe-6.2 (Ubuntu) => nvidia-graphics-
drivers-535 (Ubuntu)

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

Title:
  HDMI not detected on HP Zbook Power 15 G9

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

Bug description:
  As discussed in this thread:
  https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811

  On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected.

  According to the discussion a fix has been implemented in kernel
  v6.6-rc1.

  If it's possible for Ubuntu to implement some fix in the current LTS
  version that would be MUCH helpful and appreciated for me and all
  other ubuntu users on the same laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.104.05  Sat Aug 19 
01:15:15 UTC 2023
   GCC version:  gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 19:25:44 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   evdi/1.14.1, 6.2.0-32-generic, x86_64: installed
   evdi/1.14.1, 6.2.0-33-generic, x86_64: installed
   nvidia/535.104.05, 6.2.0-32-generic, x86_64: installed
   nvidia/535.104.05, 6.2.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:89c0]
 Subsystem: Hewlett-Packard Company Device [103c:89c1]
  InstallationDate: Installed on 2023-08-21 (29 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: HP HP ZBook Power 15.6 inch G9 Mobile Workstation PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic 
root=UUID=8a70988e-02bd-462a-b919-7e3ff4500355 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2023
  dmi.bios.release: 8.0
  dmi.bios.vendor: HP
  dmi.bios.version: U97 Ver. 01.08.00
  dmi.board.name: 89C0
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.63.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 17.99
  dmi.modalias: 
dmi:bvnHP:bvrU97Ver.01.08.00:bd06/26/2023:br8.0:efr17.99:svnHP:pnHPZBookPower15.6inchG9MobileWorkstationPC:pvr:rvnHP:rn89C0:rvrKBCVersion11.63.00:cvnHP:ct10:cvr:sku6B867EA#UUW:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Power 15.6 inch G9 Mobile Workstation PC
  dmi.product.sku: 6B867EA#UUW
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2036802/+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 1878007] Re: Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off

2023-09-24 Thread Carlos Cesar Caballero Diaz

@ricmelero no, I couldn't solve it. Soon the laptop started having
hardware problems and I ended up buying a new one (different brand).

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

Title:
   Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off

Status in linux package in Ubuntu:
  Expired

Bug description:
  This issue is happening with Ubuntu 18.04 and 20.04 in a Dell Inspiron
  7373. When the screen is turned off (so, the suspend or screen lock
  features are affected), the system freeze and I need to force the
  laptop turn off and on again. There are some cases when it turn off
  the screen without issues, but most of the time it freezes. Even
  "SysRq REISUB" does not work for rebooting when system crash. I can
  reproduce the issue using `xset dpms force off`.

  Initially this bug report was filled thinking it was a suspend issue:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144

  Syslog or systemd journal does not provide any error information about
  the crash.

  "lsb_release -rd" output:
  Description: Ubuntu 20.04 LTS
  Release: 20.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cccaballero   2023 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-06-09 (344 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7373
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=d8203f53-c2e5-4934-8616-0a71507c9190 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-02 (16 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/06/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0JW0D6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd09/06/2019:svnDellInc.:pnInspiron7373:pvr:rvnDellInc.:rn0JW0D6:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7373
  dmi.product.sku: 07EB
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878007/+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 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module

2023-09-24 Thread Chris Bertin

So, I have 2 systems with kubuntu 22.04.3, a desktop and a laptop. The
desktop has a 5.15 kernel, even though I always install all available
updates, but the laptop has a 6.2 kernel. I'd be happy to "downgrade"
that kernel to see what would happen with the rogue runaway kthreads. Is
that possible? Has anyone reported these issues on 5.15 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/1990876

Title:
  kworker high CPU usage: issue with xhci_hub_control from xhci_pci
  kernel module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 22.04, as of yesterday night upon rebooting the framework
  laptop (which had not been rebooted for several weeks), the fans come
  on strong and I see, with top, a kworker process at nearly 100% CPU
  utilization, which makes the laptop unusable.

  I have an early Framework laptop with an 11th Gen Intel(R) Core(TM)
  i7-1165G7 @ 2.80GHz.

  I removed all USB-c expansion cards except for one with an USB-c pass
  through, to no avail.

  With perf I have been able to determine that the xhci_hub_control and
  perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop
  cannot suspend any more, when it was working flawlessly until the
  reboot.

  $ sudo apt install linux-tools-common linux-tools-$(uname -r)
  $ sudo -i
  # echo -1 > /proc/sys/kernel/perf_event_paranoid
  # perf record
  control-c
  # perf report

  Samples: 125K of event 'cycles', Event count (approx.): 142991820424
  Overhead  Command  Shared Object  Symbol
  54.11%  kworker/5:2+usb  [kernel.kallsyms]  [k] xhci_hub_control  
◆
  7.94%  kworker/5:2+usb  [kernel.kallsyms]  [k] xhci_bus_suspend   
   ▒
  0.98%  kworker/5:2+usb  [kernel.kallsyms]  [k] kfree  
   ▒
  0.86%  kworker/5:2+usb  [kernel.kallsyms]  [k] 
_raw_spin_lock_irqsave
  ...

  What can be done to address this issue with a kworker?

  I suspect perhaps the new kernel is at fault. I tried rebooting to the
  prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the
  same result.

  What has changed? What can be done about this kworker and the
  xchi_hub_control?

  A temporary solution:

  $ sudo modprobe -r xhci_pci

  … which results in the kworker process disappearing from `top`
  (reduced CPU usage to near zero), the fans wind down, and
  unfortunately the ethernet expansion bay doesn’t work anymore but at
  least wifi does. Keyboard and touchpad also work. And suspend with
  deep also work well, just tested it.

  I assume other expansion bays will stop working too, but the laptop is
  at least charging: the USB-c pass-through works.

  See also:
  
https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 4870 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 18:14:26 2022
  InstallationDate: Installed on 2022-03-11 (199 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Framework Laptop
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic 
root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 
mem_sleep_default=deep vt.handoff=1
  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:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (150 days ago)
  dmi.bios.date: 07/19/2022
  dmi.bios.release: 3.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.10
  dmi.board.asset.tag: *
  dmi.board.name: FRANBMCP0B
  dmi.board.vendor: Framework
  dmi.board.version: AB
  dmi.chassis.asset.tag: FRANBMCPAB1484011X
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: AB
  dmi.modalias:

[Kernel-packages] [Bug 2036862] Re: ath10k_pci (QCA9377) firmware crashes when charger plugged

Deleted unimportant attachments. This will save us precious time.

Also, i'm unfamiliar with LaunchPad, if i were going to check the code
to see what's going on,  where i'm supposed to go?

** Attachment removed: "Lspci-vt.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702538/+files/Lspci-vt.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702545/+files/ProcModules.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702544/+files/ProcInterrupts.txt

** Attachment removed: "Lsusb-t.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702539/+files/Lsusb-t.txt

** Attachment removed: "Lsusb-v.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702540/+files/Lsusb-v.txt

** Attachment removed: "PaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702541/+files/PaInfo.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702542/+files/ProcCpuinfo.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702543/+files/ProcCpuinfoMinimal.txt

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

Title:
  ath10k_pci (QCA9377) firmware crashes when charger plugged

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

Bug description:
  This issue only occurs when charger is plugged. My network adapter is 
built-in in my laptop (it's not an usb).
  I'm also connected in a 5ghz network, so i suggest using it.

  === How to reproduce ==
  * shutdown your laptop (do not use reboot option);
  * connect charger to laptop and turn it on; (the firmware should start and 
connect to the 5ghz network)
  * If no error is thrown, continue using your laptop and your wlan device. It 
took me about 5 minutes to get a "firmware crash" error with code "-11".
  * If the firmware crashed, reboot (using shutdown command) your laptop with 
charger plugged in.
  You might similar error: "device descriptor read/64, error -71"
  * Temporary fix: Unplug the charger and reboot using shutdown command (two 
times as it might not work for the first)

  === Device Info: ===
  # uname -a && lsb_release -a:
  Linux eduapps 6.2.0-33-generic #33-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep  5 
14:49:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.04
  Release:  23.04
  Codename: lunar

  # apt-cache policy linux-firmware:
  linux-firmware:
Instalado: 20230323.gitbcdcfbcf-0ubuntu1.6
Candidato: 20230323.gitbcdcfbcf-0ubuntu1.6
Tabela de versão:
   *** 20230323.gitbcdcfbcf-0ubuntu1.6 500
  500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main amd64 
Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   20230323.gitbcdcfbcf-0ubuntu1.2 500
  500 http://br.archive.ubuntu.com/ubuntu lunar-security/main amd64 
Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar-security/main i386 
Packages
   20230323.gitbcdcfbcf-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar/main i386 Packages

  # cat /var/log/dmesg.0:
  [...]
  [9.852826] kernel: i915 :00:02.0: [drm] fb0: i915drmfb frame buffer 
device
  [9.964095] kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for 
ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [9.964109] kernel: snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [9.964112] kernel: snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [9.964115] kernel: snd_hda_codec_realtek hdaudioC0D0:mono: 
mono_out=0x0
  [9.964117] kernel: snd_hda_codec_realtek hdaudioC0D0:inputs:
  [9.964120] kernel: snd_hda_codec_realtek hdaudioC0D0:  Headset 
Mic=0x19
  [9.964122] kernel: snd_hda_codec_realtek hdaudioC0D0:  Internal 
Mic=0x1b
  [9.964124] kernel: snd_hda_codec_realtek hdaudioC0D0:  Internal 
Mic=0x13
  [   10.037952] kernel: input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:0e.0/sound/card0/input13
  [   10.038029] kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:0e.0/sound/card0/input14
  [   10.038091] kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:0e.0/sound/card0/input15
  [   10.038153] kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as

[Kernel-packages] [Bug 2036862] Re: ath10k_pci (QCA9377) firmware crashes when charger plugged

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

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

Title:
  ath10k_pci (QCA9377) firmware crashes when charger plugged

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

Bug description:
  This issue only occurs when charger is plugged. My network adapter is 
built-in in my laptop (it's not an usb).
  I'm also connected in a 5ghz network, so i suggest using it.

  === How to reproduce ==
  * shutdown your laptop (do not use reboot option);
  * connect charger to laptop and turn it on; (the firmware should start and 
connect to the 5ghz network)
  * If no error is thrown, continue using your laptop and your wlan device. It 
took me about 5 minutes to get a "firmware crash" error with code "-11".
  * If the firmware crashed, reboot (using shutdown command) your laptop with 
charger plugged in.
  You might similar error: "device descriptor read/64, error -71"
  * Temporary fix: Unplug the charger and reboot using shutdown command (two 
times as it might not work for the first)

  === Device Info: ===
  # uname -a && lsb_release -a:
  Linux eduapps 6.2.0-33-generic #33-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep  5 
14:49:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.04
  Release:  23.04
  Codename: lunar

  # apt-cache policy linux-firmware:
  linux-firmware:
Instalado: 20230323.gitbcdcfbcf-0ubuntu1.6
Candidato: 20230323.gitbcdcfbcf-0ubuntu1.6
Tabela de versão:
   *** 20230323.gitbcdcfbcf-0ubuntu1.6 500
  500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main amd64 
Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   20230323.gitbcdcfbcf-0ubuntu1.2 500
  500 http://br.archive.ubuntu.com/ubuntu lunar-security/main amd64 
Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar-security/main i386 
Packages
   20230323.gitbcdcfbcf-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar/main i386 Packages

  # cat /var/log/dmesg.0:
  [...]
  [9.852826] kernel: i915 :00:02.0: [drm] fb0: i915drmfb frame buffer 
device
  [9.964095] kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for 
ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [9.964109] kernel: snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [9.964112] kernel: snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [9.964115] kernel: snd_hda_codec_realtek hdaudioC0D0:mono: 
mono_out=0x0
  [9.964117] kernel: snd_hda_codec_realtek hdaudioC0D0:inputs:
  [9.964120] kernel: snd_hda_codec_realtek hdaudioC0D0:  Headset 
Mic=0x19
  [9.964122] kernel: snd_hda_codec_realtek hdaudioC0D0:  Internal 
Mic=0x1b
  [9.964124] kernel: snd_hda_codec_realtek hdaudioC0D0:  Internal 
Mic=0x13
  [   10.037952] kernel: input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:0e.0/sound/card0/input13
  [   10.038029] kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:0e.0/sound/card0/input14
  [   10.038091] kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:0e.0/sound/card0/input15
  [   10.038153] kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:0e.0/sound/card0/input16
  [   13.658522] kernel: kauditd_printk_skb: 73 callbacks suppressed
  [   13.658528] kernel: audit: type=1400 audit(1695260291.507:85): 
apparmor="DENIED" operation="capable" class="cap" 
profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" pid=835 
comm="snap-confine" capability=12  capname="net_admin"
  [   13.659312] kernel: audit: type=1400 audit(1695260291.507:86): 
apparmor="DENIED" operation="capable" class="cap" 
profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" pid=835 
comm="snap-confine" capability=38  capname="perfmon"
  [   13.703536] kernel: loop22: detected capacity change from 0 to 8
  [   14.776596] kernel: usb 1-1: new full-speed USB device number 8 using 
xhci_hcd
  [   14.905067] kernel: usb 1-1: device descriptor read/64, error -71
  [   15.148740] kernel: usb 1-1: device descriptor read/64, error -71
  [   15.392606] kernel: usb 1-1: new full-speed USB device number 9 using 
xhci_hcd
  [   15.524631] kernel: usb 1-1: device descriptor read/64, error -71
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eduardo1647 F wireplumber
   /dev/snd/seq:eduardo1641 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop:

[Kernel-packages] [Bug 2036862] Re: ath10k_pci (QCA9377) firmware crashes when charger plugged

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702537/+files/Lspci.txt

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

Title:
  ath10k_pci (QCA9377) firmware crashes when charger plugged

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

Bug description:
  This issue only occurs when charger is plugged. My network adapter is 
built-in in my laptop (it's not an usb).
  I'm also connected in a 5ghz network, so i suggest using it.

  === How to reproduce ==
  * shutdown your laptop (do not use reboot option);
  * connect charger to laptop and turn it on; (the firmware should start and 
connect to the 5ghz network)
  * If no error is thrown, continue using your laptop and your wlan device. It 
took me about 5 minutes to get a "firmware crash" error with code "-11".
  * If the firmware crashed, reboot (using shutdown command) your laptop with 
charger plugged in.
  You might similar error: "device descriptor read/64, error -71"
  * Temporary fix: Unplug the charger and reboot using shutdown command (two 
times as it might not work for the first)

  === Device Info: ===
  # uname -a && lsb_release -a:
  Linux eduapps 6.2.0-33-generic #33-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep  5 
14:49:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.04
  Release:  23.04
  Codename: lunar

  # apt-cache policy linux-firmware:
  linux-firmware:
Instalado: 20230323.gitbcdcfbcf-0ubuntu1.6
Candidato: 20230323.gitbcdcfbcf-0ubuntu1.6
Tabela de versão:
   *** 20230323.gitbcdcfbcf-0ubuntu1.6 500
  500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main amd64 
Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   20230323.gitbcdcfbcf-0ubuntu1.2 500
  500 http://br.archive.ubuntu.com/ubuntu lunar-security/main amd64 
Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar-security/main i386 
Packages
   20230323.gitbcdcfbcf-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar/main i386 Packages

  # cat /var/log/dmesg.0:
  [...]
  [9.852826] kernel: i915 :00:02.0: [drm] fb0: i915drmfb frame buffer 
device
  [9.964095] kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for 
ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [9.964109] kernel: snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [9.964112] kernel: snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [9.964115] kernel: snd_hda_codec_realtek hdaudioC0D0:mono: 
mono_out=0x0
  [9.964117] kernel: snd_hda_codec_realtek hdaudioC0D0:inputs:
  [9.964120] kernel: snd_hda_codec_realtek hdaudioC0D0:  Headset 
Mic=0x19
  [9.964122] kernel: snd_hda_codec_realtek hdaudioC0D0:  Internal 
Mic=0x1b
  [9.964124] kernel: snd_hda_codec_realtek hdaudioC0D0:  Internal 
Mic=0x13
  [   10.037952] kernel: input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:0e.0/sound/card0/input13
  [   10.038029] kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:0e.0/sound/card0/input14
  [   10.038091] kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:0e.0/sound/card0/input15
  [   10.038153] kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:0e.0/sound/card0/input16
  [   13.658522] kernel: kauditd_printk_skb: 73 callbacks suppressed
  [   13.658528] kernel: audit: type=1400 audit(1695260291.507:85): 
apparmor="DENIED" operation="capable" class="cap" 
profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" pid=835 
comm="snap-confine" capability=12  capname="net_admin"
  [   13.659312] kernel: audit: type=1400 audit(1695260291.507:86): 
apparmor="DENIED" operation="capable" class="cap" 
profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" pid=835 
comm="snap-confine" capability=38  capname="perfmon"
  [   13.703536] kernel: loop22: detected capacity change from 0 to 8
  [   14.776596] kernel: usb 1-1: new full-speed USB device number 8 using 
xhci_hcd
  [   14.905067] kernel: usb 1-1: device descriptor read/64, error -71
  [   15.148740] kernel: usb 1-1: device descriptor read/64, error -71
  [   15.392606] kernel: usb 1-1: new full-speed USB device number 9 using 
xhci_hcd
  [   15.524631] kernel: usb 1-1: device descriptor read/64, error -71
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eduardo1647 F wireplumber
   /dev/snd/seq:eduardo1641 F

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

This change was made by a bot.

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

Title:
  ath10k_pci (QCA9377) firmware crashes when charger plugged

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

Bug description:
  This issue only occurs when charger is plugged. My network adapter is 
built-in in my laptop (it's not an usb).
  I'm also connected in a 5ghz network, so i suggest using it.

  === How to reproduce ==
  * shutdown your laptop (do not use reboot option);
  * connect charger to laptop and turn it on; (the firmware should start and 
connect to the 5ghz network)
  * If no error is thrown, continue using your laptop and your wlan device. It 
took me about 5 minutes to get a "firmware crash" error with code "-11".
  * If the firmware crashed, reboot (using shutdown command) your laptop with 
charger plugged in.
  You might similar error: "device descriptor read/64, error -71"
  * Temporary fix: Unplug the charger and reboot using shutdown command (two 
times as it might not work for the first)

  === Device Info: ===
  # uname -a && lsb_release -a:
  Linux eduapps 6.2.0-33-generic #33-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep  5 
14:49:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.04
  Release:  23.04
  Codename: lunar

  # apt-cache policy linux-firmware:
  linux-firmware:
Instalado: 20230323.gitbcdcfbcf-0ubuntu1.6
Candidato: 20230323.gitbcdcfbcf-0ubuntu1.6
Tabela de versão:
   *** 20230323.gitbcdcfbcf-0ubuntu1.6 500
  500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main amd64 
Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   20230323.gitbcdcfbcf-0ubuntu1.2 500
  500 http://br.archive.ubuntu.com/ubuntu lunar-security/main amd64 
Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar-security/main i386 
Packages
   20230323.gitbcdcfbcf-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar/main i386 Packages

  # cat /var/log/dmesg.0:
  [...]
  [9.852826] kernel: i915 :00:02.0: [drm] fb0: i915drmfb frame buffer 
device
  [9.964095] kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for 
ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [9.964109] kernel: snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [9.964112] kernel: snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [9.964115] kernel: snd_hda_codec_realtek hdaudioC0D0:mono: 
mono_out=0x0
  [9.964117] kernel: snd_hda_codec_realtek hdaudioC0D0:inputs:
  [9.964120] kernel: snd_hda_codec_realtek hdaudioC0D0:  Headset 
Mic=0x19
  [9.964122] kernel: snd_hda_codec_realtek hdaudioC0D0:  Internal 
Mic=0x1b
  [9.964124] kernel: snd_hda_codec_realtek hdaudioC0D0:  Internal 
Mic=0x13
  [   10.037952] kernel: input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:0e.0/sound/card0/input13
  [   10.038029] kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:0e.0/sound/card0/input14
  [   10.038091] kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:0e.0/sound/card0/input15
  [   10.038153] kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:0e.0/sound/card0/input16
  [   13.658522] kernel: kauditd_printk_skb: 73 callbacks suppressed
  [   13.658528] kernel: audit: type=1400 audit(1695260291.507:85): 
apparmor="DENIED" operation="capable" class="cap" 
profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" pid=835 
comm="snap-confine" capability=12  capname="net_admin"
  [   13.659312] kernel: audit: type=1400 audit(1695260291.507:86): 
apparmor="DENIED" operation="capable" class="cap" 
profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" pid=835 
comm="snap-confine" capability=38  capname="perfmon"
  [   13.703536] kernel: loop22: detected capacity change from 0 to 8
  [   14.776596] kernel: usb 1-1: new full-speed USB device number 8 using 
xhci_hcd
  [   14.905067] kernel: usb 1-1: device descriptor read/64, error -71
  [   15.148740] kernel: usb 1-1: device descriptor read/64, error -71
  [   15.392606] kernel: usb 1-1: new full-speed USB device number 9 using 
xhci_hcd
  [   15.524631] kernel: usb 1-1: device descriptor read/64, error -71
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eduardo1647 F wireplumber
   /dev/snd/seq:eduardo1641 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Dependencies:

[Kernel-packages] [Bug 2036862] Re: ath10k_pci (QCA9377) firmware crashes when charger plugged

Journalctl file from the firmware crash

** Attachment removed: "Dmesg output at the crash time."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5704150/+files/dmesg-crash

** Attachment added: "Journalctl output (firmware crash)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5704155/+files/journalctl-file

** Attachment removed: "acpidump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702549/+files/acpidump.txt

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702548/+files/WifiSyslog.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702535/+files/CurrentDmesg.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702547/+files/UdevDb.txt

** Attachment removed: "RfKill.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702546/+files/RfKill.txt

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702534/+files/AlsaInfo.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5702536/+files/IwConfig.txt

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

Title:
  ath10k_pci (QCA9377) firmware crashes when charger plugged

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

Bug description:
  This issue only occurs when charger is plugged. My network adapter is 
built-in in my laptop (it's not an usb).
  I'm also connected in a 5ghz network, so i suggest using it.

  === How to reproduce ==
  * shutdown your laptop (do not use reboot option);
  * connect charger to laptop and turn it on; (the firmware should start and 
connect to the 5ghz network)
  * If no error is thrown, continue using your laptop and your wlan device. It 
took me about 5 minutes to get a "firmware crash" error with code "-11".
  * If the firmware crashed, reboot (using shutdown command) your laptop with 
charger plugged in.
  You might similar error: "device descriptor read/64, error -71"
  * Temporary fix: Unplug the charger and reboot using shutdown command (two 
times as it might not work for the first)

  === Device Info: ===
  # uname -a && lsb_release -a:
  Linux eduapps 6.2.0-33-generic #33-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep  5 
14:49:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.04
  Release:  23.04
  Codename: lunar

  # apt-cache policy linux-firmware:
  linux-firmware:
Instalado: 20230323.gitbcdcfbcf-0ubuntu1.6
Candidato: 20230323.gitbcdcfbcf-0ubuntu1.6
Tabela de versão:
   *** 20230323.gitbcdcfbcf-0ubuntu1.6 500
  500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main amd64 
Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   20230323.gitbcdcfbcf-0ubuntu1.2 500
  500 http://br.archive.ubuntu.com/ubuntu lunar-security/main amd64 
Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar-security/main i386 
Packages
   20230323.gitbcdcfbcf-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar/main i386 Packages

  # cat /var/log/dmesg.0:
  [...]
  [9.852826] kernel: i915 :00:02.0: [drm] fb0: i915drmfb frame buffer 
device
  [9.964095] kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for 
ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [9.964109] kernel: snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [9.964112] kernel: snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [9.964115] kernel: snd_hda_codec_realtek hdaudioC0D0:mono: 
mono_out=0x0
  [9.964117] kernel: snd_hda_codec_realtek hdaudioC0D0:inputs:
  [9.964120] kernel: snd_hda_codec_realtek hdaudioC0D0:  Headset 
Mic=0x19
  [9.964122] kernel: snd_hda_codec_realtek hdaudioC0D0:  Internal 
Mic=0x1b
  [9.964124] kernel: snd_hda_codec_realtek hdaudioC0D0:  Internal 
Mic=0x13
  [   10.037952] kernel: input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:0e.0/sound/card0/input13
  [   10.038029] kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:0e.0/sound/card0/input14
  [   10.038091] kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:0e.0/sound/card0/input15
  [   10.038153] kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as

[Kernel-packages] [Bug 2036862] Re: ath10k_pci (QCA9377) firmware crashes when charger plugged

Here it is, the firmware crash it at "7119.478819" There's also interesting 
data in the end of the file.
It happened when i did plug the charger when my laptop was at 4%.

Given the fact that it's related with the charger, and sometimes it also
happens during the suspension. I suspect it's caused by the powersave
mode.

** Attachment added: "Dmesg output at the crash time."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036862/+attachment/5704150/+files/dmesg-crash

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

Title:
  ath10k_pci (QCA9377) firmware crashes when charger plugged

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

Bug description:
  This issue only occurs when charger is plugged. My network adapter is 
built-in in my laptop (it's not an usb).
  I'm also connected in a 5ghz network, so i suggest using it.

  === How to reproduce ==
  * shutdown your laptop (do not use reboot option);
  * connect charger to laptop and turn it on; (the firmware should start and 
connect to the 5ghz network)
  * If no error is thrown, continue using your laptop and your wlan device. It 
took me about 5 minutes to get a "firmware crash" error with code "-11".
  * If the firmware crashed, reboot (using shutdown command) your laptop with 
charger plugged in.
  You might similar error: "device descriptor read/64, error -71"
  * Temporary fix: Unplug the charger and reboot using shutdown command (two 
times as it might not work for the first)

  === Device Info: ===
  # uname -a && lsb_release -a:
  Linux eduapps 6.2.0-33-generic #33-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep  5 
14:49:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.04
  Release:  23.04
  Codename: lunar

  # apt-cache policy linux-firmware:
  linux-firmware:
Instalado: 20230323.gitbcdcfbcf-0ubuntu1.6
Candidato: 20230323.gitbcdcfbcf-0ubuntu1.6
Tabela de versão:
   *** 20230323.gitbcdcfbcf-0ubuntu1.6 500
  500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main amd64 
Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   20230323.gitbcdcfbcf-0ubuntu1.2 500
  500 http://br.archive.ubuntu.com/ubuntu lunar-security/main amd64 
Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar-security/main i386 
Packages
   20230323.gitbcdcfbcf-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  500 http://br.archive.ubuntu.com/ubuntu lunar/main i386 Packages

  # cat /var/log/dmesg.0:
  [...]
  [9.852826] kernel: i915 :00:02.0: [drm] fb0: i915drmfb frame buffer 
device
  [9.964095] kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for 
ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [9.964109] kernel: snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [9.964112] kernel: snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [9.964115] kernel: snd_hda_codec_realtek hdaudioC0D0:mono: 
mono_out=0x0
  [9.964117] kernel: snd_hda_codec_realtek hdaudioC0D0:inputs:
  [9.964120] kernel: snd_hda_codec_realtek hdaudioC0D0:  Headset 
Mic=0x19
  [9.964122] kernel: snd_hda_codec_realtek hdaudioC0D0:  Internal 
Mic=0x1b
  [9.964124] kernel: snd_hda_codec_realtek hdaudioC0D0:  Internal 
Mic=0x13
  [   10.037952] kernel: input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:0e.0/sound/card0/input13
  [   10.038029] kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:0e.0/sound/card0/input14
  [   10.038091] kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:0e.0/sound/card0/input15
  [   10.038153] kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:0e.0/sound/card0/input16
  [   13.658522] kernel: kauditd_printk_skb: 73 callbacks suppressed
  [   13.658528] kernel: audit: type=1400 audit(1695260291.507:85): 
apparmor="DENIED" operation="capable" class="cap" 
profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" pid=835 
comm="snap-confine" capability=12  capname="net_admin"
  [   13.659312] kernel: audit: type=1400 audit(1695260291.507:86): 
apparmor="DENIED" operation="capable" class="cap" 
profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" pid=835 
comm="snap-confine" capability=38  capname="perfmon"
  [   13.703536] kernel: loop22: detected capacity change from 0 to 8
  [   14.776596] kernel: usb 1-1: new full-speed USB device number 8 using 
xhci_hcd
  [   14.905067] kernel: usb 1-1: device descriptor read/64, error -71
  [   15.148740] kernel: usb 1-1: device descriptor read/64,

[Kernel-packages] [Bug 2037224] Re: Failed to manually enable the RTL8851BE BT function

Proposed firmware fix in https://lore.kernel.org/linux-
firmware/20230922055525.49787-1-max.c...@realtek.com/T/#u

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

** Also affects: linux-firmware (Ubuntu Mantic)
   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/2037224

Title:
  Failed to manually enable the RTL8851BE BT function

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Mantic:
  New

Bug description:
  After disabling BT and leaving it idle for a period, manually turning
  on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)

  Test step:
  1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
  2. Check BT function after boot into OS.
  3. Manually turn OFF BT function. Then wait for 1 minute.
  4. Manually turn ON the BT function.
  5. Unable to enable BT function. (issue occurs)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037224/+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 2037224] [NEW] Failed to manually enable the RTL8851BE BT function

Public bug reported:

After disabling BT and leaving it idle for a period, manually turning on
the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)

Test step:
1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
2. Check BT function after boot into OS.
3. Manually turn OFF BT function. Then wait for 1 minute.
4. Manually turn ON the BT function.
5. Unable to enable BT function. (issue occurs)

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

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

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

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


** Tags: flying-fox oem-priority originate-from-2036579

** Tags added: flying-fox oem-priority originate-from-2036579

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

Title:
  Failed to manually enable the RTL8851BE BT function

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Mantic:
  New

Bug description:
  After disabling BT and leaving it idle for a period, manually turning
  on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)

  Test step:
  1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
  2. Check BT function after boot into OS.
  3. Manually turn OFF BT function. Then wait for 1 minute.
  4. Manually turn ON the BT function.
  5. Unable to enable BT function. (issue occurs)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037224/+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 2036697] Re: i915: Update DMC, GuC, HuC fw for Meteor Lake

* a5dbe400f (drm/mtl_huc_8.5.4) i915: update MTL HuC to version 8.5.4
|  i915/mtl_huc_gsc.bin | Bin 569344 -> 561152 bytes
|  1 file changed, 0 insertions(+), 0 deletions(-)
* 49f9e3479 (drm/dmc-mtl_2.16) i915: Update MTL DMC to v2.16
|  i915/mtl_dmc.bin | Bin 52164 -> 52388 bytes
|  1 file changed, 0 insertions(+), 0 deletions(-)
* 81caac98e (drm/mtl_gsc_1655) i915: add GSC 102.0.0.1655 for MTL
|  i915/mtl_gsc_1.bin | Bin 0 -> 1142784 bytes
|  1 file changed, 0 insertions(+), 0 deletions(-)
* fd6e13ca2 (drm/dmc-adlp_2.20-mtl_2.13) i915: Update MTL DMC to v2.13
|  i915/mtl_dmc.bin | Bin 49104 -> 52164 bytes
|  1 file changed, 0 insertions(+), 0 deletions(-)
* 0ee23bd11 i915: update to GuC 70.8.0 and HuC 8.5.1 for MTL
|  i915/mtl_guc_70.bin  | Bin 303936 -> 308032 bytes
|  i915/mtl_huc_gsc.bin | Bin 565248 -> 569344 bytes
|  2 files changed, 0 insertions(+), 0 deletions(-)

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

Title:
  i915: Update DMC, GuC, HuC fw for Meteor Lake

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

Bug description:
  [Impact]
  There are new firmware versions available for MTL, which contain undisclosed 
fixes.

  lunar is omitted as it doesn't have support for MTL, while jammy does
  via oem-6.5

  [Test case]
  Install the update, test on MTL that things keep working at least the same as 
before.

  [Regression potential]
  MTL is a new platform being enabled, these do not affect any shipping hardware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036697/+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 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module

2023-09-24 Thread Chris Bertin

The situation has gotten much worse with the 6.2.0.33 kernel! There are
now kworker threads spinning out of control even without an SD drive in
the slot. Inserting an SD drive just adds new kworker threads! Testing
anyone? How can things deteriorate so badly?

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

Title:
  kworker high CPU usage: issue with xhci_hub_control from xhci_pci
  kernel module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 22.04, as of yesterday night upon rebooting the framework
  laptop (which had not been rebooted for several weeks), the fans come
  on strong and I see, with top, a kworker process at nearly 100% CPU
  utilization, which makes the laptop unusable.

  I have an early Framework laptop with an 11th Gen Intel(R) Core(TM)
  i7-1165G7 @ 2.80GHz.

  I removed all USB-c expansion cards except for one with an USB-c pass
  through, to no avail.

  With perf I have been able to determine that the xhci_hub_control and
  perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop
  cannot suspend any more, when it was working flawlessly until the
  reboot.

  $ sudo apt install linux-tools-common linux-tools-$(uname -r)
  $ sudo -i
  # echo -1 > /proc/sys/kernel/perf_event_paranoid
  # perf record
  control-c
  # perf report

  Samples: 125K of event 'cycles', Event count (approx.): 142991820424
  Overhead  Command  Shared Object  Symbol
  54.11%  kworker/5:2+usb  [kernel.kallsyms]  [k] xhci_hub_control  
◆
  7.94%  kworker/5:2+usb  [kernel.kallsyms]  [k] xhci_bus_suspend   
   ▒
  0.98%  kworker/5:2+usb  [kernel.kallsyms]  [k] kfree  
   ▒
  0.86%  kworker/5:2+usb  [kernel.kallsyms]  [k] 
_raw_spin_lock_irqsave
  ...

  What can be done to address this issue with a kworker?

  I suspect perhaps the new kernel is at fault. I tried rebooting to the
  prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the
  same result.

  What has changed? What can be done about this kworker and the
  xchi_hub_control?

  A temporary solution:

  $ sudo modprobe -r xhci_pci

  … which results in the kworker process disappearing from `top`
  (reduced CPU usage to near zero), the fans wind down, and
  unfortunately the ethernet expansion bay doesn’t work anymore but at
  least wifi does. Keyboard and touchpad also work. And suspend with
  deep also work well, just tested it.

  I assume other expansion bays will stop working too, but the laptop is
  at least charging: the USB-c pass-through works.

  See also:
  
https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 4870 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 18:14:26 2022
  InstallationDate: Installed on 2022-03-11 (199 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Framework Laptop
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic 
root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 
mem_sleep_default=deep vt.handoff=1
  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:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (150 days ago)
  dmi.bios.date: 07/19/2022
  dmi.bios.release: 3.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.10
  dmi.board.asset.tag: *
  dmi.board.name: FRANBMCP0B
  dmi.board.vendor: Framework
  dmi.board.version: AB
  dmi.chassis.asset.tag: FRANBMCPAB1484011X
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: AB
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B:
  dmi.product.family: FRANBMCP
  dmi.product.name: Laptop

[Kernel-packages] [Bug 1861419] Re: kworker takes a lot of CPU

2023-09-24 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1861419

** Tags added: iso-testing

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

Title:
  kworker takes a lot of CPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kworker takes a lot of CPU. no other app are active.

  top - 15:52:50 up 8 min,  1 user,  load average: 1,16, 1,24, 0,77
  Tasks: 204 total,   2 running, 202 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  4,9 us, 26,2 sy,  0,0 ni, 62,3 id,  0,0 wa,  0,0 hi,  6,6 si,  0,0 
st
  MiB Mem :   3867,1 total,   1737,2 free,895,9 used,   1234,0 buff/cache
  MiB Swap:   4096,0 total,   4096,0 free,  0,0 used.   2568,5 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
239 root  20   0   0  0  0 R  81,2   0,0   0:31.92 
kworker/0+
   1623 corrado   20   0  304848  53436  38048 S   6,2   1,3   0:13.02 Xorg
   1921 corrado   20   0  323484  10544   8768 S   6,2   0,3   0:00.42 
ibus-daem+
  1 root  20   0  167140  10868   7952 S   0,0   0,3   0:02.04 systemd

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1613 F pulseaudio
   /dev/snd/controlC1:  corrado1613 F pulseaudio
  Date: Thu Jan 30 15:49:01 2020
  InstallationDate: Installed on 2019-12-28 (33 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Hewlett-Packard HP 250 G3 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=24e2ba6f-1b75-4b3c-835e-63387635551b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP250G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=CON B=HP S=PAV
  dmi.product.name: HP 250 G3 Notebook PC
  dmi.product.sku: J4R70EA#ABZ
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861419/+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 1861419] Re: kworker takes a lot of CPU

2023-09-24 Thread corrado venturini

same problem in Ubuntu 23.10 live session
same workaround with: echo "disable" > /sys/firmware/acpi/interrupts/gpe03

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

Title:
  kworker takes a lot of CPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kworker takes a lot of CPU. no other app are active.

  top - 15:52:50 up 8 min,  1 user,  load average: 1,16, 1,24, 0,77
  Tasks: 204 total,   2 running, 202 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  4,9 us, 26,2 sy,  0,0 ni, 62,3 id,  0,0 wa,  0,0 hi,  6,6 si,  0,0 
st
  MiB Mem :   3867,1 total,   1737,2 free,895,9 used,   1234,0 buff/cache
  MiB Swap:   4096,0 total,   4096,0 free,  0,0 used.   2568,5 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
239 root  20   0   0  0  0 R  81,2   0,0   0:31.92 
kworker/0+
   1623 corrado   20   0  304848  53436  38048 S   6,2   1,3   0:13.02 Xorg
   1921 corrado   20   0  323484  10544   8768 S   6,2   0,3   0:00.42 
ibus-daem+
  1 root  20   0  167140  10868   7952 S   0,0   0,3   0:02.04 systemd

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1613 F pulseaudio
   /dev/snd/controlC1:  corrado1613 F pulseaudio
  Date: Thu Jan 30 15:49:01 2020
  InstallationDate: Installed on 2019-12-28 (33 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Hewlett-Packard HP 250 G3 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=24e2ba6f-1b75-4b3c-835e-63387635551b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP250G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=CON B=HP S=PAV
  dmi.product.name: HP 250 G3 Notebook PC
  dmi.product.sku: J4R70EA#ABZ
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861419/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices

2023-09-24 Thread M-Rick

** Attachment added: "Capture d’écran du 2023-09-24 15-44-45.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2013236/+attachment/5704098/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-09-24%2015-44-45.png

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

Title:
  b43 driver conflicts with bcmwl driver for some Broadcom devices

Status in broadcom-sta package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Incomplete
Status in broadcom-sta source package in Lunar:
  New
Status in linux-firmware source package in Lunar:
  Invalid
Status in ubuntu-drivers-common source package in Lunar:
  Incomplete
Status in broadcom-sta source package in Mantic:
  New
Status in linux-firmware source package in Mantic:
  Invalid
Status in ubuntu-drivers-common source package in Mantic:
  Incomplete

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

  Workaround
  --
  You'll first need to blacklist the b43 driver by adding a blacklist file to 
/etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run 
"update-initramfs -u". Then install the bcmwl-kernel-source package. After a 
reboot your wireless device should be available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices

2023-09-24 Thread M-Rick

** Attachment added: "Capture d’écran du 2023-09-24 15-44-18.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2013236/+attachment/5704097/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-09-24%2015-44-18.png

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

Title:
  b43 driver conflicts with bcmwl driver for some Broadcom devices

Status in broadcom-sta package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Incomplete
Status in broadcom-sta source package in Lunar:
  New
Status in linux-firmware source package in Lunar:
  Invalid
Status in ubuntu-drivers-common source package in Lunar:
  Incomplete
Status in broadcom-sta source package in Mantic:
  New
Status in linux-firmware source package in Mantic:
  Invalid
Status in ubuntu-drivers-common source package in Mantic:
  Incomplete

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

  Workaround
  --
  You'll first need to blacklist the b43 driver by adding a blacklist file to 
/etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run 
"update-initramfs -u". Then install the bcmwl-kernel-source package. After a 
reboot your wireless device should be available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices

2023-09-24 Thread M-Rick

I got it working on a 2015 MacBook Air 7.2
From a 23.04 fresh installation it didin't work neither with a 22.04 fresh 
installation. I tried all the tricks I found over internet and nothing worked.
I then had first to install an old Ubuntu 20.04 and block the version of the 
following packages bcmwl-kernel-source linux-headers-5-10.0.84 
linux-headers-5-10.0.84-generic linux-modules-5-10.0.84-generic. Now I have a 
fresh 23.04 version with Wifi on a Broadcom BCM 4360 14e4:43a0.
It seems defintely to be a bug since it worked perfectly out-of-the-box with 
other distros such as Fedora or Arch.

** Attachment added: "Capture d’écran du 2023-09-24 15-43-57.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2013236/+attachment/5704096/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-09-24%2015-43-57.png

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

Title:
  b43 driver conflicts with bcmwl driver for some Broadcom devices

Status in broadcom-sta package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Incomplete
Status in broadcom-sta source package in Lunar:
  New
Status in linux-firmware source package in Lunar:
  Invalid
Status in ubuntu-drivers-common source package in Lunar:
  Incomplete
Status in broadcom-sta source package in Mantic:
  New
Status in linux-firmware source package in Mantic:
  Invalid
Status in ubuntu-drivers-common source package in Mantic:
  Incomplete

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

  Workaround
  --
  You'll first need to blacklist the b43 driver by adding a blacklist file to 
/etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run 
"update-initramfs -u". Then install the bcmwl-kernel-source package. After a 
reboot your wireless device should be available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2037212] Re: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)

2023-09-24 Thread Bug Watch Updater

** Changed in: bluez (Debian)
   Status: Unknown => New

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

Title:
  ConfigurationDirectory 'bluetooth' already exists but the mode is
  different. (File system: 755 ConfigurationDirectoryMode: 555)

Status in bluez package in Ubuntu:
  New
Status in bluez package in Debian:
  New

Bug description:
  Hi,

  when my system boots it logs the following warning in the journal:

  $ journalctl | grep ConfigurationDirectory
  Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 
ConfigurationDirectoryMode: 555)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: bluez 5.68-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 13:28:20 2023
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 70:9C:D1:50:1F:7B  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0

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


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

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

This change was made by a bot.

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

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  during boot the kernel logs the following messages:

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

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

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

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

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


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

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

Public bug reported:

Hi,

during boot the kernel logs the following messages:

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

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

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

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

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


** Tags: amd64 apport-bug mantic

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  during boot the kernel logs the following messages:

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

[Kernel-packages] [Bug 2036342] Re: no sound cards found afer kernel update from 6.2.0-26 to 6.2.0-32

2023-09-24 Thread Lars W

It resolved itself. Sorry to bother you.

I listed all installed Linux kernel packages (dpkg -l | grep
"linux\-[a-z]*\-") and kept only the 6.2.0-26 versions. Then I removed
unused packages (sudo apt autoremove) and afterwards reinstalled
6.2.0-32 (sudo apt install linux-image-6.2.0-32-generic linux-
modules-6.2.0-32-generic linux-modules-extra-6.2.0-32-generic linux-
modules-nvidia-525-6.2.0-32-generic linux-objects-
nvidia-525-6.2.0-32-generic linux-signatures-nvidia-6.2.0-32-generic).
Now sounds works again! (I don't know if WiFi was affected, but it works
now.)

For reference, I attach the dmesg logs without timestamps (sed 's/^\[
*[0-9]*\.[0-9]*\] //') from the original problematic 6.2.0-32 kernel and
again after reinstall. The first substantial difference I could spot is
after "PM: Magic number" it no longer says "acpi AMDI0020:02: hash
matches".

** Attachment added: "dmesg log of 6.2.0-32-generic before and after reinstall"

https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036342/+attachment/5704061/+files/dmesg.zip

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

Title:
no sound cards found afer kernel update from 6.2.0-26 to 6.2.0-32

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

Bug description:
After the update from kernel 6.2.0-26 to 6.2.0-32 under Ubuntu 22.04
LTS, there are no more sound cards found. I can reliably reproduce
this by switching in the grub boot menu between the kernel versions.

I used sound over HDMI of the NVIDIA Corporation GP108 [GeForce GT
1030] and it used to use the module snd_hda_intel. Now, a symptom is
that `aplay -l` reports "no soundcards found", and neither does any
other program.

I had similar problems after the Ubuntu update from 5.19.0-43 to
5.19.0-45.

I reported this to the offical linux kernel mailinglist yesterday (
https://bugzilla.kernel.org/show_bug.cgi?id=217917 ). They have sent
me here. Indeed, I now tried the vanilla "mainline" kernels 6.2.0-rc8
and 6.5.3 - and there the sound cards are correctly found.

I am attaching logfiles and info from /proc for the different tried
kernel version that are hopefully useful. Please let me know if there
is more info I can provide or things I could try to narrow down the
problem.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-32-generic (not installed)
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 17 09:52:19 2023
InstallationDate: Installed on 2023-04-16 (153 days ago)
InstallationMedia: Kubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230223)
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036342/+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 2037212] [NEW] ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)

Public bug reported:

Hi,

when my system boots it logs the following warning in the journal:

$ journalctl | grep ConfigurationDirectory
Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 
ConfigurationDirectoryMode: 555)

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 13:28:20 2023
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 70:9C:D1:50:1F:7B  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0

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

** Affects: bluez (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug mantic

** Bug watch added: Debian Bug tracker #1017988
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017988

** Also affects: bluez (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017988
   Importance: Unknown
   Status: Unknown

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

Title:
  ConfigurationDirectory 'bluetooth' already exists but the mode is
  different. (File system: 755 ConfigurationDirectoryMode: 555)

Status in bluez package in Ubuntu:
  New
Status in bluez package in Debian:
  Unknown

Bug description:
  Hi,

  when my system boots it logs the following warning in the journal:

  $ journalctl | grep ConfigurationDirectory
  Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 
ConfigurationDirectoryMode: 555)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: bluez 5.68-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 13:28:20 2023
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 70:9C:D1:50:1F:7B  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1806437] Re: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)

This bug is fixed in recent kernels.
Thanks:

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

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

Title:
  acpi PNP0C14:02: duplicate WMI GUID
  05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on
  PNP0C14:01)

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

Bug description:
  Hello,

  dmesg:
  [   15.390738] acpi PNP0C14:02: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2769 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 12:49:26 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806437/+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 1912509] Re: ucsi_acpi USBC000:00: PPM init failed (-110)

** Tags added: mantic

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

Title:
  ucsi_acpi USBC000:00: PPM init failed (-110)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting with kernel 5.8.0-38-generic on my Asus Tuf 15 with 2 NVMe 
drives I get:
  usci_acpi USBC000:00: PPM init failed (-110) and the laptop freezes.

  kernel 5.4.0-26-generic usually boots (but get an occasional freeze).

  Since I cannot boot in the 5.8 kernel I cannot file the bug with that
  kernel running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vincent1381 F pulseaudio
   /dev/snd/controlC0:  vincent1381 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 20 17:28:23 2021
  InstallationDate: Installed on 2021-01-20 (0 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LI_FX506LI
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=74589408-5655-4728-b040-86c06177a989 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX506LI.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX506LI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX506LI.307:bd12/17/2020:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LI_FX506LI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ASUS TUF Gaming F15
  dmi.product.name: ASUS TUF Gaming F15 FX506LI_FX506LI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912509/+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 1959384] Re: CONFIG_IO_STRICT_DEVMEM could be enabled

** Tags added: mantic

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

Title:
  CONFIG_IO_STRICT_DEVMEM could be enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace
  access of active io-memory ranges.

  This could impact kernel debugability. In that case, you may reboot with
  iomem=relaxed on the kernel command line to override this setting.

  This config option is recommended by the Kernel Self Protection
  Project[1] and a 2019 study performed by Capsule 8 shows that it is
  enabled in many other major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

  In Ubuntu impish:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.13.0-27-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.13.0-27-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set

  In Debian 11:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.10.0-10-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.10.0-11-amd64:CONFIG_IO_STRICT_DEVMEM=y

  In Debian sid:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.15.0-3-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.15.0-3-rt-amd64:CONFIG_IO_STRICT_DEVMEM=y

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959384/+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 1971186] Re: Suggests linux-lowlatency-tools instead of linux-tools-lowlatency

** Tags added: mantic

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

Title:
  Suggests linux-lowlatency-tools instead of linux-tools-lowlatency

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  Hi,

  the linux-image-*-lowlatency kernel package suggests the linux-
  lowlatency-tools package:

  $ apt show linux-image-5.15.0-27-lowlatency
  Package: linux-image-5.15.0-27-lowlatency
  Version: 5.15.0-27.28
  [...]
  Suggests: fdutils, linux-doc | linux-lowlatency-source-5.15.0, 
linux-lowlatency-tools, linux-headers-5.15.0-27-lowlatency, 
linux-modules-extra-5.15.0-27-lowlatency

  The linux-lowlatency-tools package does not exist.  However, a linux-
  tools-lowlatency does exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-27-lowlatency 5.15.0-27.28
  Uname: Linux 5.17.5-051705-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon May  2 20:06:21 2022
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/1971186/+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 1991691] Re: cannot change mount namespace

The fix a now upstream according to last comment.
Thanks!

** Changed in: linux
   Status: New => Fix Released

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

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

Title:
  cannot change mount namespace

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  Multiple snaps are either broken or "only" display permission denied
  messages.

  slack snap is not starting at all with:

  > update.go:85: cannot change mount namespace according to change
  mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none
  bind,rw,x-snapd.ignore-missing 0 0): cannot inspect
  "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied

  firefox snap does start, but also logs errors:

  
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot 
inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat 
/var/lib/snapd/hostfs/usr/share/doc: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat 
/var/lib/snapd/hostfs/usr/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat 
/usr/local/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none 
bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission 
denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none 
bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat 
/var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": 
lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: snap (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Oct  4 17:29:01 2022
  InstallationDate: Installed on 2017-09-26 (1834 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170924)
  SourcePackage: snap
  UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1991691/+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 1993566] Re: dbus-daemon: Unknown group "power" in message bus configuration file

** Tags added: mantic

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

Title:
  dbus-daemon: Unknown group "power" in message bus configuration file

Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Hi,

  I see the following error message in the logs:

  # journalctl | grep 'Unknown group "power"'
  Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in 
message bus configuration file
  Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file
  Oct 19 18:46:36 jophur dbus-daemon[630]: Unknown group "power" in message bus 
configuration file

  The problem comes from this file:

  # grep -r power /etc/dbus-1/
  /etc/dbus-1/system.d/org.freedesktop.thermald.conf:

[Kernel-packages] [Bug 1979633] Re: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated"