** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122372
Title:
6.8 and 6.14 kernels massive shared memory bug
Status in linux package in Ubuntu:
New
Bug description:
This is a place holder report, I will add more information as time
permits, mostly I want to see if this is recognised by others.
I have an Ubuntu 24.04 VM on 24.04 host, AMD 64, 64 GB. 20GB ram, 2GB
swap file. Used for development: runs docker compose and JetBrains IDE
mostly.
Problem. For the last couple of weeks, massive amounts of shared memory are consumed. This leads to OOM and the kernel OOM killer activates usually killing the gnome session. The systemd oomd does nothing and reports nothing in journald.
The trigger to the shared memory use is elusive, but seems to be any kind of activity, possibly terminal activity. Running docker compose will quickly consume the 16 Gbi of free memory I have after boot (more or less), but so does general use of the IDE. In typical use, I can get one to two hours before OOM kill with the 20GBi allocated and 2GBi swap. I was using swapspace; the swap file would grow to 8GBi but the kernel OOM kill came just the same.
Good news: kernel OOM kills are really decisive now :)
Observations:
* Problem is not reproducible with mainline 6.16.4 or 6.16.5 kernels. I have been doing normal activity, and shared memory is < 1 GBi. By now with an ubuntu kernel, it would be many GBi. (and thank goodness for this)
* Old versions of the IDE have the same problem. It is not a
regression in PyCharm. Also, it happens outside of the IDE.
* No diagnostic tool known to an LLM can find the process behind the shared memory consumption. I have no actual proof of what is causing it. My suspicious is writing output to terminals, but nothing I do could account for GBs (scroll backlines were 10K now 1K, no difference)
* it is never handed back by closing any process or app. It is orphaned. It continues to grow.
* it is a hard, kernel recognised memory allocation which the kernel can not reclaim (until I log out). It causes swap exhaustion and then OOM killing, every time.
* merely logging out releases all the shared memory. So it belongs to the user and user cgroup slice, I guess.
* is the wayland gnome session
Initially huge pages were used for the guest, but in troubleshooting
as I removed them, the problem didn't change
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122372/+subscriptions
вторник
[Bug 2122398] Re: No on-screen keyboard on dell tablets
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122398
Title:
No on-screen keyboard on dell tablets
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.14 source package in Noble:
In Progress
Status in linux source package in Questing:
In Progress
Status in linux-oem-6.14 source package in Questing:
Invalid
Bug description:
[Impact]
No on-screen keyboard in gdm and can't enter password if there is no keyboard is connected.
[Fix]
Added those tablets to dmi_vgbs_allow_list() to read tablet mode while probing fixes the issue.
[Test]
Boot up the affected tablets to gdm without touching any physical keys, the on-screen keyboard should pop up.
[Where problems could occur]
Current BIOS is reliablely to report the tablet mode during probing intel hid driver, but when it fails, it may report the wrong state and show the on-screen keyboard when keyboard is connected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122398/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122398
Title:
No on-screen keyboard on dell tablets
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.14 source package in Noble:
In Progress
Status in linux source package in Questing:
In Progress
Status in linux-oem-6.14 source package in Questing:
Invalid
Bug description:
[Impact]
No on-screen keyboard in gdm and can't enter password if there is no keyboard is connected.
[Fix]
Added those tablets to dmi_vgbs_allow_list() to read tablet mode while probing fixes the issue.
[Test]
Boot up the affected tablets to gdm without touching any physical keys, the on-screen keyboard should pop up.
[Where problems could occur]
Current BIOS is reliablely to report the tablet mode during probing intel hid driver, but when it fails, it may report the wrong state and show the on-screen keyboard when keyboard is connected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122398/+subscriptions
[Bug 2122421] Re: drm/xe/bmg: fix frequency changes workaround
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122421
Title:
drm/xe/bmg: fix frequency changes workaround
Status in linux package in Ubuntu:
New
Status in linux source package in Plucky:
In Progress
Bug description:
[ Impact ]
* Previous workaround was limiting BMG frequency in some
circumstances but didn't wait for it to reduce effectively before
proceeding.
[ Fix ]
* This is fixed by upstream commit: deea6a7d6d8 drm/xe/bmg: Update Wa_22019338487
* This commit has been included in v6.15.6
* Cherry pick it and other related commit that leads to it.
[ Test Plan ]
* Tested by intel.
* Built and boot tested on supported device.
[ Where problems could occur ]
* Regression in the BMG driver and graphics handling.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122421/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122421
Title:
drm/xe/bmg: fix frequency changes workaround
Status in linux package in Ubuntu:
New
Status in linux source package in Plucky:
In Progress
Bug description:
[ Impact ]
* Previous workaround was limiting BMG frequency in some
circumstances but didn't wait for it to reduce effectively before
proceeding.
[ Fix ]
* This is fixed by upstream commit: deea6a7d6d8 drm/xe/bmg: Update Wa_22019338487
* This commit has been included in v6.15.6
* Cherry pick it and other related commit that leads to it.
[ Test Plan ]
* Tested by intel.
* Built and boot tested on supported device.
[ Where problems could occur ]
* Regression in the BMG driver and graphics handling.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122421/+subscriptions
[Bug 2122435] Re: drm/xe: support power limits
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122435
Title:
drm/xe: support power limits
Status in linux package in Ubuntu:
New
Status in linux source package in Plucky:
New
Bug description:
[ Impact ]
* Support power limits for hardware supported by drm/xe driver.
[ Fix ]
* Integrate patchset coming from https://lore.kernel.org/all/20250529163458.2354509-1-karthik.poosa@intel.com/
* Include prerequisite commit: drm/xe/hwmon: expose fan speed
* Include also a fix commit: drm/xe/hwmon: Fix xe_hwmon_power_max_write
Everything is upstream.
[ Test Plan ]
* Tested by intel.
* Compile, test on supported hardware and checks exposed hwmon sysfs entries.
[ Where problems could occur ]
* Regression in drm/xe power management.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122435/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122435
Title:
drm/xe: support power limits
Status in linux package in Ubuntu:
New
Status in linux source package in Plucky:
New
Bug description:
[ Impact ]
* Support power limits for hardware supported by drm/xe driver.
[ Fix ]
* Integrate patchset coming from https://lore.kernel.org/all/20250529163458.2354509-1-karthik.poosa@intel.com/
* Include prerequisite commit: drm/xe/hwmon: expose fan speed
* Include also a fix commit: drm/xe/hwmon: Fix xe_hwmon_power_max_write
Everything is upstream.
[ Test Plan ]
* Tested by intel.
* Compile, test on supported hardware and checks exposed hwmon sysfs entries.
[ Where problems could occur ]
* Regression in drm/xe power management.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122435/+subscriptions
[Bug 2122379] Re: [SRU] Add support of cs42l43 and cs35l56 on ThinkPad P1 and P16
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122379
Title:
[SRU] Add support of cs42l43 and cs35l56 on ThinkPad P1 and P16
Status in HWE Next:
In Progress
Status in firmware-sof package in Ubuntu:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in firmware-sof source package in Noble:
New
Status in linux source package in Noble:
Invalid
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.14 source package in Noble:
In Progress
Status in firmware-sof source package in Plucky:
New
Status in linux source package in Plucky:
In Progress
Status in linux-firmware source package in Plucky:
In Progress
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in firmware-sof source package in Questing:
New
Status in linux source package in Questing:
Invalid
Status in linux-firmware source package in Questing:
In Progress
Status in linux-oem-6.14 source package in Questing:
Invalid
Bug description:
[Impact]
No audio input or output on ThinkPad P1 or P16.
[Fix]
Add sof-bin, linux-firmware and kernel commits to support it.
sof-bin:
c2c74b7 v2.13.x: Update v2.13.1 new/updated topology files
linux-firmware:
c6a9ced6 cirrus: cs35l56: Add firmware for Cirrus Amps for some Lenovo laptops
kernel commits:
f7690d058170d ASoC: Intel: sof_sdw: Add quirks for Lenovo P1 and P16
a7528e9beadbd ASoC: Intel: soc-acpi: arl: Correct order of cs42l43 matches
[Test]
Steps:
1, hear the sound from
$ speaker-test -c 2
2, make sound and recorded, replay the file:
$ arecord -f cd test.wav
$ aplay test.wav
3, press speaker-mute and mic-mute key, the OSD are shown,
and the LED is on when it's muted.
4, plugin headset and restest the steps above for sound input and output.
sound ctl led is not controlled by headset, it's by design:
please refer to:
https://github.com/alsa-project/alsa-ucm-conf/blob/master/ucm2/common/ctl/led.conf
[Where problems could occur]
It may break cirrus audio support.
SRU for OEM-6.14/Plucky/Questing those support new these platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2122379/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122379
Title:
[SRU] Add support of cs42l43 and cs35l56 on ThinkPad P1 and P16
Status in HWE Next:
In Progress
Status in firmware-sof package in Ubuntu:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in firmware-sof source package in Noble:
New
Status in linux source package in Noble:
Invalid
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.14 source package in Noble:
In Progress
Status in firmware-sof source package in Plucky:
New
Status in linux source package in Plucky:
In Progress
Status in linux-firmware source package in Plucky:
In Progress
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in firmware-sof source package in Questing:
New
Status in linux source package in Questing:
Invalid
Status in linux-firmware source package in Questing:
In Progress
Status in linux-oem-6.14 source package in Questing:
Invalid
Bug description:
[Impact]
No audio input or output on ThinkPad P1 or P16.
[Fix]
Add sof-bin, linux-firmware and kernel commits to support it.
sof-bin:
c2c74b7 v2.13.x: Update v2.13.1 new/updated topology files
linux-firmware:
c6a9ced6 cirrus: cs35l56: Add firmware for Cirrus Amps for some Lenovo laptops
kernel commits:
f7690d058170d ASoC: Intel: sof_sdw: Add quirks for Lenovo P1 and P16
a7528e9beadbd ASoC: Intel: soc-acpi: arl: Correct order of cs42l43 matches
[Test]
Steps:
1, hear the sound from
$ speaker-test -c 2
2, make sound and recorded, replay the file:
$ arecord -f cd test.wav
$ aplay test.wav
3, press speaker-mute and mic-mute key, the OSD are shown,
and the LED is on when it's muted.
4, plugin headset and restest the steps above for sound input and output.
sound ctl led is not controlled by headset, it's by design:
please refer to:
https://github.com/alsa-project/alsa-ucm-conf/blob/master/ucm2/common/ctl/led.conf
[Where problems could occur]
It may break cirrus audio support.
SRU for OEM-6.14/Plucky/Questing those support new these platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2122379/+subscriptions
[Bug 2122171] Re: PCI realloc failing
Linking to other bugs which could be resolved by setting 'pci=realloc=off' as a workaround:
- LP#1363313: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363313
- LP#2032120: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032120
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122171
Title:
PCI realloc failing
Status in linux package in Ubuntu:
Incomplete
Bug description:
The Ubuntu kernel is enabling PCI reallocation ("pci=realloc=on"b by
default), and this reallocation is failing on some Dell server
systems, particularly those with NVidia GPUs. When reallocation
fails, the kernel does not restore the original BIOS-assigned
resources, and the system does not function correctly.
Would it be possible to turn off kernel config option
CONFIG_PCI_REALLOC_ENABLE_AUTO? That option should only be helpful on
systems with BIOS that don't fully configure PCI devices, and it is
breaking systems that are configured correctly. Other enterprise
distros (RHEL, SLES) seem to have this disabled by default.
I can provide kernel logs or more details if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122171/+subscriptions
- LP#1363313: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363313
- LP#2032120: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032120
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122171
Title:
PCI realloc failing
Status in linux package in Ubuntu:
Incomplete
Bug description:
The Ubuntu kernel is enabling PCI reallocation ("pci=realloc=on"b by
default), and this reallocation is failing on some Dell server
systems, particularly those with NVidia GPUs. When reallocation
fails, the kernel does not restore the original BIOS-assigned
resources, and the system does not function correctly.
Would it be possible to turn off kernel config option
CONFIG_PCI_REALLOC_ENABLE_AUTO? That option should only be helpful on
systems with BIOS that don't fully configure PCI devices, and it is
breaking systems that are configured correctly. Other enterprise
distros (RHEL, SLES) seem to have this disabled by default.
I can provide kernel logs or more details if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122171/+subscriptions
[Bug 2122171] Re: PCI realloc failing
Hi Stuart,
If you could indeed provide some logs by running:
$ sudo apport-collect 2122171
that would be great :)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122171
Title:
PCI realloc failing
Status in linux package in Ubuntu:
Incomplete
Bug description:
The Ubuntu kernel is enabling PCI reallocation ("pci=realloc=on"b by
default), and this reallocation is failing on some Dell server
systems, particularly those with NVidia GPUs. When reallocation
fails, the kernel does not restore the original BIOS-assigned
resources, and the system does not function correctly.
Would it be possible to turn off kernel config option
CONFIG_PCI_REALLOC_ENABLE_AUTO? That option should only be helpful on
systems with BIOS that don't fully configure PCI devices, and it is
breaking systems that are configured correctly. Other enterprise
distros (RHEL, SLES) seem to have this disabled by default.
I can provide kernel logs or more details if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122171/+subscriptions
If you could indeed provide some logs by running:
$ sudo apport-collect 2122171
that would be great :)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122171
Title:
PCI realloc failing
Status in linux package in Ubuntu:
Incomplete
Bug description:
The Ubuntu kernel is enabling PCI reallocation ("pci=realloc=on"b by
default), and this reallocation is failing on some Dell server
systems, particularly those with NVidia GPUs. When reallocation
fails, the kernel does not restore the original BIOS-assigned
resources, and the system does not function correctly.
Would it be possible to turn off kernel config option
CONFIG_PCI_REALLOC_ENABLE_AUTO? That option should only be helpful on
systems with BIOS that don't fully configure PCI devices, and it is
breaking systems that are configured correctly. Other enterprise
distros (RHEL, SLES) seem to have this disabled by default.
I can provide kernel logs or more details if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122171/+subscriptions
[Bug 2122368] Re: Re-enable memcg v1 on Noble (6.14)
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122368
Title:
Re-enable memcg v1 on Noble (6.14)
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Bug description:
[Impact]
Although v1 cgroups are deprecated in Noble, it was still possible for
users on 6.8 kernels to utilize them. This was especially helpful in
helping migrating users to Noble and then separately upgrading their
remaining v1 cgroups applications. Instead of requiring all users to
upgrade and fix their v2 support, v1 support could be provisionally
enabled until the necessary support was available in the applications
that still lack v2 support.
Starting in 6.12, CONFIG_MEMCG_V1 was added and defaulted to false.
Noble 6.8 users that were unlucky enough to still need V1 cgroups found
that they could no longer use memcgs in the 6.14 kernel.
Specific use cases include older JVMs that fail to correctly handle
missing controllers from /proc/cgroups. In that case, the container
limit detection is turned off and the JVM uses the host's limits.
Further, Apache Yarn is still completing their v1 -> v2 migration, which
leaves some Hadoop use cases without proper support.
The request here is to enable MEMCG_V1 on Noble, but not newer releases,
for as long as the Noble HWE kernel train still has kernels with cgroup
v1 support. This gives users a little bit longer to complete their
migration while still using newer hardware, but with the understanding
that this really is the end of the line for v1 cgroups.
[Fix]
Re-enable CONFIG_MEMCG_V1 in the 6.14 Noble config.
[Test]
Booted a kernel with this change and validated that v1 memcgs were
present again.
[Potential Regression]
The regression potential here should be low since this merely restores
and existing feature that most users were not using but that a few still
depended upon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122368/+subscriptions
Status: New => In Progress
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122368
Title:
Re-enable memcg v1 on Noble (6.14)
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Bug description:
[Impact]
Although v1 cgroups are deprecated in Noble, it was still possible for
users on 6.8 kernels to utilize them. This was especially helpful in
helping migrating users to Noble and then separately upgrading their
remaining v1 cgroups applications. Instead of requiring all users to
upgrade and fix their v2 support, v1 support could be provisionally
enabled until the necessary support was available in the applications
that still lack v2 support.
Starting in 6.12, CONFIG_MEMCG_V1 was added and defaulted to false.
Noble 6.8 users that were unlucky enough to still need V1 cgroups found
that they could no longer use memcgs in the 6.14 kernel.
Specific use cases include older JVMs that fail to correctly handle
missing controllers from /proc/cgroups. In that case, the container
limit detection is turned off and the JVM uses the host's limits.
Further, Apache Yarn is still completing their v1 -> v2 migration, which
leaves some Hadoop use cases without proper support.
The request here is to enable MEMCG_V1 on Noble, but not newer releases,
for as long as the Noble HWE kernel train still has kernels with cgroup
v1 support. This gives users a little bit longer to complete their
migration while still using newer hardware, but with the understanding
that this really is the end of the line for v1 cgroups.
[Fix]
Re-enable CONFIG_MEMCG_V1 in the 6.14 Noble config.
[Test]
Booted a kernel with this change and validated that v1 memcgs were
present again.
[Potential Regression]
The regression potential here should be low since this merely restores
and existing feature that most users were not using but that a few still
depended upon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122368/+subscriptions
[Bug 2122280] Re: iwlwifi: Intel AX211 disconnects and roams constantly on TP-Link Deco Mesh (AP Mode)
Hi borhanudin,
Thanks for submitting this bug report. Could you include some more logs
from an affected system by running:
$ sudo apport-collect 2122280
This will help us have all the info needed to diagnose the issue.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122280
Title:
iwlwifi: Intel AX211 disconnects and roams constantly on TP-Link Deco
Mesh (AP Mode)
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hello Ubuntu Kernel Team,
I am reporting a reproducible Wi-Fi instability issue with the Intel
AX211 card on a TP-Link Deco mesh network. This affects both Linux
Mint and a live Ubuntu environment, pointing to a kernel or driver-
level incompatibility.
**[Core Problem]**
The connection drops every few minutes. The kernel log confirms this is not a signal loss, but a forced roam between mesh nodes initiated by a "deauthenticating by local choice (Reason: 3=DEAUTH_LEAVING)" event. The iwlwifi driver does not handle this handoff seamlessly, resulting in a full disconnection.
**[Hardware & Network Environment]**
* **Wi-Fi Card:** Intel Corporation Wi-Fi 6E AX211 160MHz
* **Mesh System:** TP-Link Deco M9 Plus
* **Mode:** Access Point (AP) mode
**[Critical Test Results]**
* **Hardware Confirmed Working:** The laptop is 100% stable on a non-mesh mobile hotspot.
* **Mesh Features Disabled:** The issue persists even after disabling Fast Roaming, Beamforming, and separating the 2.4/5GHz bands in the Deco app.
* **Guest Network Fails:** The instability also occurs on the Deco's isolated Guest Network.
This isolates the fault to the Deco's fundamental (non-optional) node-
steering logic and its incompatibility with the iwlwifi driver's
handling of these specific deauthentication commands.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122280/+subscriptions
Thanks for submitting this bug report. Could you include some more logs
from an affected system by running:
$ sudo apport-collect 2122280
This will help us have all the info needed to diagnose the issue.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122280
Title:
iwlwifi: Intel AX211 disconnects and roams constantly on TP-Link Deco
Mesh (AP Mode)
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hello Ubuntu Kernel Team,
I am reporting a reproducible Wi-Fi instability issue with the Intel
AX211 card on a TP-Link Deco mesh network. This affects both Linux
Mint and a live Ubuntu environment, pointing to a kernel or driver-
level incompatibility.
**[Core Problem]**
The connection drops every few minutes. The kernel log confirms this is not a signal loss, but a forced roam between mesh nodes initiated by a "deauthenticating by local choice (Reason: 3=DEAUTH_LEAVING)" event. The iwlwifi driver does not handle this handoff seamlessly, resulting in a full disconnection.
**[Hardware & Network Environment]**
* **Wi-Fi Card:** Intel Corporation Wi-Fi 6E AX211 160MHz
* **Mesh System:** TP-Link Deco M9 Plus
* **Mode:** Access Point (AP) mode
**[Critical Test Results]**
* **Hardware Confirmed Working:** The laptop is 100% stable on a non-mesh mobile hotspot.
* **Mesh Features Disabled:** The issue persists even after disabling Fast Roaming, Beamforming, and separating the 2.4/5GHz bands in the Deco app.
* **Guest Network Fails:** The instability also occurs on the Deco's isolated Guest Network.
This isolates the fault to the Deco's fundamental (non-optional) node-
steering logic and its incompatibility with the iwlwifi driver's
handling of these specific deauthentication commands.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122280/+subscriptions
[Bug 2122279] Re: Kernel unable to load firmware
** Also affects: linux (Ubuntu Questing)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122279
Title:
Kernel unable to load firmware
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
New
Bug description:
I found these error messages while browsing the journalctl log on
Xubuntu 25.10:
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: msvld: unable to load firmware data
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: msvld: init failed, -19
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: TRAP_PROP - TP 0 - 00000008 [SURF_HEIGHT_OVERRUN] - Address 0000000000
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00040000, e20: 00003700, e24: 00000000
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: 00200000 [] ch 6 [001f4b4000 gst-plugin-scan[3023]] subc 3 class 8397 mthd 1b0c data 1000f010
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: TRAP_PROP - TP 0 - 00000008 [SURF_HEIGHT_OVERRUN] - Address 0000000000
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00040000, e20: 00003700, e24: 00000000
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: 00200000 [] ch 6 [001f4b4000 gst-plugin-scan[3023]] subc 3 class 8397 mthd 1b0c data 1000f010
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: TRAP_PROP - TP 0 - 00000008 [SURF_HEIGHT_OVERRUN] - Address 0000000000
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00040000, e20: 00003700, e24: 00000000
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: 00200000 [] ch 6 [001f4b4000 gst-plugin-scan[3023]] subc 3 class 8397 mthd 1b0c data 1000f010
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: davide 2356 F.... wireplumber
/dev/snd/seq: davide 2349 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
DistroRelease: Ubuntu 25.10
InstallationDate: Installed on 2025-08-24 (14 days ago)
InstallationMedia: Xubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 30fa:0301 USB OPTICAL MOUSE
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s
Bus 002 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
MachineType: ASUSTeK Computer Inc. K50IN
Package: linux-meta (not installed)
ProcEnviron:
LANG=it_IT.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-3-generic root=UUID=9c6e1e50-792b-48e9-9ea7-24ff80fcb2b9 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.17.0-3.3-generic 6.17.0-rc3
RelatedPackageVersions:
linux-restricted-modules-6.17.0-3-generic N/A
linux-backports-modules-6.17.0-3-generic N/A
linux-firmware 20250818.git07ed893d-0ubuntu1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: questing
Uname: Linux 6.17.0-3-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 07/05/2011
dmi.bios.release: 6.64
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 223
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K50IN
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.ec.firmware.release: 153.153
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr223:bd07/05/2011:br6.64:efr153.153:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: K50IN
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: davide 2349 F.... pipewire
davide 2356 F.... wireplumber
/dev/snd/pcmC0D0p: davide 2349 F...m pipewire
/dev/snd/seq: davide 2349 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
DistroRelease: Ubuntu 25.10
InstallationDate: Installed on 2025-08-24 (14 days ago)
InstallationMedia: Xubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 30fa:0301 USB OPTICAL MOUSE
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s
Bus 002 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
MachineType: ASUSTeK Computer Inc. K50IN
Package: linux (not installed)
ProcEnviron:
LANG=it_IT.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-3-generic root=UUID=9c6e1e50-792b-48e9-9ea7-24ff80fcb2b9 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.17.0-3.3-generic 6.17.0-rc3
RelatedPackageVersions:
linux-restricted-modules-6.17.0-3-generic N/A
linux-backports-modules-6.17.0-3-generic N/A
linux-firmware 20250818.git07ed893d-0ubuntu1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: questing
Uname: Linux 6.17.0-3-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 07/05/2011
dmi.bios.release: 6.64
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 223
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K50IN
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.ec.firmware.release: 153.153
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr223:bd07/05/2011:br6.64:efr153.153:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: K50IN
dmi.product.sku: To Be Filled By O.E.M.
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/2122279/+subscriptions
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122279
Title:
Kernel unable to load firmware
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
New
Bug description:
I found these error messages while browsing the journalctl log on
Xubuntu 25.10:
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: msvld: unable to load firmware data
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: msvld: init failed, -19
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: TRAP_PROP - TP 0 - 00000008 [SURF_HEIGHT_OVERRUN] - Address 0000000000
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00040000, e20: 00003700, e24: 00000000
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: 00200000 [] ch 6 [001f4b4000 gst-plugin-scan[3023]] subc 3 class 8397 mthd 1b0c data 1000f010
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: TRAP_PROP - TP 0 - 00000008 [SURF_HEIGHT_OVERRUN] - Address 0000000000
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00040000, e20: 00003700, e24: 00000000
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: 00200000 [] ch 6 [001f4b4000 gst-plugin-scan[3023]] subc 3 class 8397 mthd 1b0c data 1000f010
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: TRAP_PROP - TP 0 - 00000008 [SURF_HEIGHT_OVERRUN] - Address 0000000000
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: TRAP_PROP - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00040000, e20: 00003700, e24: 00000000
set 07 13:39:24 davide-K50IN kernel: nouveau 0000:02:00.0: gr: 00200000 [] ch 6 [001f4b4000 gst-plugin-scan[3023]] subc 3 class 8397 mthd 1b0c data 1000f010
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: davide 2356 F.... wireplumber
/dev/snd/seq: davide 2349 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
DistroRelease: Ubuntu 25.10
InstallationDate: Installed on 2025-08-24 (14 days ago)
InstallationMedia: Xubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 30fa:0301 USB OPTICAL MOUSE
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s
Bus 002 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
MachineType: ASUSTeK Computer Inc. K50IN
Package: linux-meta (not installed)
ProcEnviron:
LANG=it_IT.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-3-generic root=UUID=9c6e1e50-792b-48e9-9ea7-24ff80fcb2b9 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.17.0-3.3-generic 6.17.0-rc3
RelatedPackageVersions:
linux-restricted-modules-6.17.0-3-generic N/A
linux-backports-modules-6.17.0-3-generic N/A
linux-firmware 20250818.git07ed893d-0ubuntu1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: questing
Uname: Linux 6.17.0-3-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 07/05/2011
dmi.bios.release: 6.64
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 223
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K50IN
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.ec.firmware.release: 153.153
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr223:bd07/05/2011:br6.64:efr153.153:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: K50IN
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: davide 2349 F.... pipewire
davide 2356 F.... wireplumber
/dev/snd/pcmC0D0p: davide 2349 F...m pipewire
/dev/snd/seq: davide 2349 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
DistroRelease: Ubuntu 25.10
InstallationDate: Installed on 2025-08-24 (14 days ago)
InstallationMedia: Xubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 30fa:0301 USB OPTICAL MOUSE
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s
Bus 002 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
MachineType: ASUSTeK Computer Inc. K50IN
Package: linux (not installed)
ProcEnviron:
LANG=it_IT.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-3-generic root=UUID=9c6e1e50-792b-48e9-9ea7-24ff80fcb2b9 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.17.0-3.3-generic 6.17.0-rc3
RelatedPackageVersions:
linux-restricted-modules-6.17.0-3-generic N/A
linux-backports-modules-6.17.0-3-generic N/A
linux-firmware 20250818.git07ed893d-0ubuntu1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: questing
Uname: Linux 6.17.0-3-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 07/05/2011
dmi.bios.release: 6.64
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 223
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K50IN
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.ec.firmware.release: 153.153
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr223:bd07/05/2011:br6.64:efr153.153:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: K50IN
dmi.product.sku: To Be Filled By O.E.M.
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/2122279/+subscriptions
[Bug 2122228] Re: XFCE display issue using VBox in 25.10
** Also affects: xfce4 (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: virtualbox (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Questing)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122228
Title:
XFCE display issue using VBox in 25.10
Status in linux package in Ubuntu:
New
Status in virtualbox package in Ubuntu:
New
Status in xfce4 package in Ubuntu:
New
Status in linux source package in Questing:
New
Status in virtualbox source package in Questing:
New
Status in xfce4 source package in Questing:
New
Bug description:
I use Xubuntu in a VM for my email and (a)social media accounts, say since 2018. With the current development version I have 1 issue and they started occurring in Linux 6.16 and 6.17 did not solve it:
1. Normally the VBox-VM Window returns in it previous size and location, like now in Xubuntu 24.04 LTS. In the current 25.10 it always returns to a default physical display setting.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: xorg 1:7.7+24ubuntu1
ProcVersionSignature: Ubuntu 6.17.0-3.3-generic 6.17.0-rc3
Uname: Linux 6.17.0-3-generic x86_64
ApportVersion: 2.33.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Sat Sep 6 13:10:06 2025
DistUpgraded: Fresh install
DistroCodename: questing
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2024-12-18 (262 days ago)
InstallationMedia: Xubuntu 25.04 "Plucky Puffin" - Daily amd64 (20241218)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/8p, 480M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000M
MachineType: innotek GmbH VirtualBox
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-3-generic root=UUID=084599bc-3226-4ea9-af0d-1c43d4966d44 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.125-1
version.libgl1-mesa-dri: libgl1-mesa-dri 25.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.18-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.18-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122228/+subscriptions
Importance: Undecided
Status: New
** Also affects: virtualbox (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Questing)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2122228
Title:
XFCE display issue using VBox in 25.10
Status in linux package in Ubuntu:
New
Status in virtualbox package in Ubuntu:
New
Status in xfce4 package in Ubuntu:
New
Status in linux source package in Questing:
New
Status in virtualbox source package in Questing:
New
Status in xfce4 source package in Questing:
New
Bug description:
I use Xubuntu in a VM for my email and (a)social media accounts, say since 2018. With the current development version I have 1 issue and they started occurring in Linux 6.16 and 6.17 did not solve it:
1. Normally the VBox-VM Window returns in it previous size and location, like now in Xubuntu 24.04 LTS. In the current 25.10 it always returns to a default physical display setting.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: xorg 1:7.7+24ubuntu1
ProcVersionSignature: Ubuntu 6.17.0-3.3-generic 6.17.0-rc3
Uname: Linux 6.17.0-3-generic x86_64
ApportVersion: 2.33.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Sat Sep 6 13:10:06 2025
DistUpgraded: Fresh install
DistroCodename: questing
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2024-12-18 (262 days ago)
InstallationMedia: Xubuntu 25.04 "Plucky Puffin" - Daily amd64 (20241218)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/8p, 480M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000M
MachineType: innotek GmbH VirtualBox
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-3-generic root=UUID=084599bc-3226-4ea9-af0d-1c43d4966d44 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.125-1
version.libgl1-mesa-dri: libgl1-mesa-dri 25.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.18-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.18-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122228/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-ibm-6.8/6.8.0-1035.35~22.04.1)
All autopkgtests for the newly accepted linux-meta-ibm-6.8 (6.8.0-1035.35~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
glibc/2.35-0ubuntu3.10 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-ibm-6.8
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
glibc/2.35-0ubuntu3.10 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-ibm-6.8
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 2106553] Re: Epyc Genoa system unable to boot starting with Kernel 6.14.0
I am having a bit of strange issue, picked two different AMD platforms
Ruby and Quartz both running Genoa.
- Plucky 25.04 deployments with the 6.14.0-27 and 6.14.0-29 kernel Do get into a boot loop.
- Noble 24.04 LTS deployments with the 6.14.0-27 and 6.14.0-29 kernel DO NO get into a boot loop.
The workaround for the issue was to block the ae4dma module:
echo "blacklist ae4dma" | sudo tee -a /etc/modprobe.d/blacklist.conf
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106553
Title:
Epyc Genoa system unable to boot starting with Kernel 6.14.0
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have an Epyc Genoa system that won't boot with either the 6.14.0 or
6.14.1 kernels without mce=off. The system is only a few months old,
and has run without issue on all kernels up to the most recent 6.13.10
release. Starting with kernel 6.14.0, the system is unable to boot,
apparently due to a CPU cache issue (based on my reading of the
journalctl -b logs). I don't believe this is actually a hardware issue
as reported by the logs, since I have run thorough stress tests on
both the CPU and memory without any problem since first coming accross
this. I have reached out to the board manufacturer, and there are no
newer BIOS updates available. System details are below.
CPU: AMD EPYC 9554 (microcode 0x0a101148)
Motherboard: ASRock Rack GENOAD8X-2T/BCM (BIOS Firmware Version 10.05, BMC Firmware Version 10.02.00)
Memory: 8x64GB MICRON DDR5 RDIMM
[ 2.016623] BERT: Error records from previous boot:
[ 2.019601] [Hardware Error]: event severity: fatal
[ 2.022688] [Hardware Error]: Error 0, type: fatal
[ 2.026173] [Hardware Error]: fru_text: ProcessorError
[ 2.028867] [Hardware Error]: section_type: IA32/X64 processor error
[ 2.031706] [Hardware Error]: Local APIC_ID: 0x0
[ 2.033879] [Hardware Error]: CPUID Info:
[ 2.036475] [Hardware Error]: 00000000: 00a10f11 00000000 00800800 00000000
[ 2.038856] [Hardware Error]: 00000010: 76fa320b 00000000 178bfbff 00000000
[ 2.040891] [Hardware Error]: 00000020: 00000000 00000000 00000000 00000000
[ 2.043879] [Hardware Error]: Error Information Structure 0:
[ 2.045883] [Hardware Error]: Error Structure Type: cache error
[ 2.047903] [Hardware Error]: Check Information: 0x000000000602001f
[ 2.050184] [Hardware Error]: Transaction Type: 2, Generic
[ 2.052881] [Hardware Error]: Operation: 0, generic error
[ 2.054882] [Hardware Error]: Level: 0
[ 2.057883] [Hardware Error]: Processor Context Corrupt: true
[ 2.059883] [Hardware Error]: Uncorrected: true
[ 2.061899] [Hardware Error]: Context Information Structure 0:
[ 2.063883] [Hardware Error]: Register Context Type: MSR Registers (Machine Check and other MSRs)
[ 2.067872] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 2.067891] [Hardware Error]: Register Array Size: 0x0050
[ 2.073207] [Hardware Error]: MSR Address: 0xc0002051
[ 2.076587] [Hardware Error]: Context Information Structure 1:
[ 2.078873] [Hardware Error]: Register Context Type: Unclassified Data
[ 2.081350] [Hardware Error]: Register Array Size: 0x0010
[ 2.083291] [Hardware Error]: Register Array:
[ 2.085194] [Hardware Error]: 00000000: 00000010 00000000 1c3010c0 fffffffe
[ 2.087887] BERT: Total records found: 1
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-13-generic 6.14.0-13.13
ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0
Uname: Linux 6.14.0-13-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.14.0-13-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/hwC1D0', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card2.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card2.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Tue Apr 8 23:49:59 2025
InstallationDate: Installed on 2025-04-08 (0 days ago)
InstallationMedia: Ubuntu-Server 25.04 "Plucky Puffin" - Daily amd64 (20250324)
MachineType: To Be Filled By O.E.M. GENOAD8X-2T/BCM
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.14.0-13-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M mce=off
RelatedPackageVersions:
linux-restricted-modules-6.14.0-13-generic N/A
linux-backports-modules-6.14.0-13-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: 12/12/2024
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 10.05
dmi.board.name: GENOAD8X-2T/BCM
dmi.board.vendor: ASRockRack
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr10.05:bd12/12/2024:br5.27:svnToBeFilledByO.E.M.:pnGENOAD8X-2T/BCM:pvrToBeFilledByO.E.M.:rvnASRockRack:rnGENOAD8X-2T/BCM:rvr:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: GENOAD8X-2T/BCM
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106553/+subscriptions
Ruby and Quartz both running Genoa.
- Plucky 25.04 deployments with the 6.14.0-27 and 6.14.0-29 kernel Do get into a boot loop.
- Noble 24.04 LTS deployments with the 6.14.0-27 and 6.14.0-29 kernel DO NO get into a boot loop.
The workaround for the issue was to block the ae4dma module:
echo "blacklist ae4dma" | sudo tee -a /etc/modprobe.d/blacklist.conf
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106553
Title:
Epyc Genoa system unable to boot starting with Kernel 6.14.0
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have an Epyc Genoa system that won't boot with either the 6.14.0 or
6.14.1 kernels without mce=off. The system is only a few months old,
and has run without issue on all kernels up to the most recent 6.13.10
release. Starting with kernel 6.14.0, the system is unable to boot,
apparently due to a CPU cache issue (based on my reading of the
journalctl -b logs). I don't believe this is actually a hardware issue
as reported by the logs, since I have run thorough stress tests on
both the CPU and memory without any problem since first coming accross
this. I have reached out to the board manufacturer, and there are no
newer BIOS updates available. System details are below.
CPU: AMD EPYC 9554 (microcode 0x0a101148)
Motherboard: ASRock Rack GENOAD8X-2T/BCM (BIOS Firmware Version 10.05, BMC Firmware Version 10.02.00)
Memory: 8x64GB MICRON DDR5 RDIMM
[ 2.016623] BERT: Error records from previous boot:
[ 2.019601] [Hardware Error]: event severity: fatal
[ 2.022688] [Hardware Error]: Error 0, type: fatal
[ 2.026173] [Hardware Error]: fru_text: ProcessorError
[ 2.028867] [Hardware Error]: section_type: IA32/X64 processor error
[ 2.031706] [Hardware Error]: Local APIC_ID: 0x0
[ 2.033879] [Hardware Error]: CPUID Info:
[ 2.036475] [Hardware Error]: 00000000: 00a10f11 00000000 00800800 00000000
[ 2.038856] [Hardware Error]: 00000010: 76fa320b 00000000 178bfbff 00000000
[ 2.040891] [Hardware Error]: 00000020: 00000000 00000000 00000000 00000000
[ 2.043879] [Hardware Error]: Error Information Structure 0:
[ 2.045883] [Hardware Error]: Error Structure Type: cache error
[ 2.047903] [Hardware Error]: Check Information: 0x000000000602001f
[ 2.050184] [Hardware Error]: Transaction Type: 2, Generic
[ 2.052881] [Hardware Error]: Operation: 0, generic error
[ 2.054882] [Hardware Error]: Level: 0
[ 2.057883] [Hardware Error]: Processor Context Corrupt: true
[ 2.059883] [Hardware Error]: Uncorrected: true
[ 2.061899] [Hardware Error]: Context Information Structure 0:
[ 2.063883] [Hardware Error]: Register Context Type: MSR Registers (Machine Check and other MSRs)
[ 2.067872] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 2.067891] [Hardware Error]: Register Array Size: 0x0050
[ 2.073207] [Hardware Error]: MSR Address: 0xc0002051
[ 2.076587] [Hardware Error]: Context Information Structure 1:
[ 2.078873] [Hardware Error]: Register Context Type: Unclassified Data
[ 2.081350] [Hardware Error]: Register Array Size: 0x0010
[ 2.083291] [Hardware Error]: Register Array:
[ 2.085194] [Hardware Error]: 00000000: 00000010 00000000 1c3010c0 fffffffe
[ 2.087887] BERT: Total records found: 1
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-13-generic 6.14.0-13.13
ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0
Uname: Linux 6.14.0-13-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.14.0-13-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/hwC1D0', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card2.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card2.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Tue Apr 8 23:49:59 2025
InstallationDate: Installed on 2025-04-08 (0 days ago)
InstallationMedia: Ubuntu-Server 25.04 "Plucky Puffin" - Daily amd64 (20250324)
MachineType: To Be Filled By O.E.M. GENOAD8X-2T/BCM
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.14.0-13-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M mce=off
RelatedPackageVersions:
linux-restricted-modules-6.14.0-13-generic N/A
linux-backports-modules-6.14.0-13-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: 12/12/2024
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 10.05
dmi.board.name: GENOAD8X-2T/BCM
dmi.board.vendor: ASRockRack
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr10.05:bd12/12/2024:br5.27:svnToBeFilledByO.E.M.:pnGENOAD8X-2T/BCM:pvrToBeFilledByO.E.M.:rvnASRockRack:rnGENOAD8X-2T/BCM:rvr:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: GENOAD8X-2T/BCM
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106553/+subscriptions
Подписаться на:
Сообщения (Atom)