[Bug 2139016] [NEW] S3 (deep) resume hard hang on AMD Ryzen 5 3550H (Picasso); s2idle only works with no_console_suspend

Public bug reported:

Description

This system consistently enters suspend successfully but fails to resume
when using ACPI S3 ("deep"). The failure occurs very early during resume
and leaves the system completely unresponsive, requiring a hard
power‑cycle.

The hardware is a Wo‑We R5 mini PC with an AMD Ryzen 5 3550H (Picasso /
Raven2) CPU and AMI UEFI firmware (ADB20D 1.04, dated 2025‑04‑28).

The issue is reproducible with the Ubuntu 25.10 kernel
(`6.17.0-8-generic`).

## Reproduction (S3 / deep)

1. Boot the system normally.
2. Trigger suspend using:
        sudo systemctl suspend
3. Allow the system to enter suspend.
4. Attempt to wake using keyboard, mouse, or power button.

## Observed result

* System appears to exit suspend partially:
    * fans spin up
    * power LED becomes steady
* No HDMI output (monitor reports no signal)
* Keyboard and mouse do not respond
* SSH is unreachable
* Magic SysRq does not produce any response
* System remains in this state indefinitely until powered off

After reboot, logs from the previous boot show:

    PM: suspend entry (deep)

There are **no resume‑related log entries** (e.g. "PM: resume from
suspend", "ACPI: Waking up from system sleep state S3", etc.).

I assume the resume failure occurs **before kernel logging and
interrupts are restored**.

## Expected result

The system should resume to a working state with display, input, and
networking restored.

## Additional diagnostics

Magic SysRq commands were tested during the hang (r/e/i/s/u) and
produced no observable effect, indicating the kernel is no longer
executing normally after the wake attempt.

The failure is therefore not limited to graphics or userspace and
appears to be a hard early‑resume hang.

## s2idle behaviour

When forcing suspend‑to‑idle (S0 idle) instead of S3:

    mem_sleep_default=s2idle

the system **does resume successfully**, but only if the following
kernel parameter is also present:

    no_console_suspend

If `no_console_suspend` is removed, suspend‑to‑idle resumes also begin
to hang again in a similar way.

This suggests the resume path is **timing‑sensitive**, and that keeping
the console active during suspend/resume alters execution timing in a
way that avoids the failure.

## Notes

* The system firmware appears to support S3 (`/sys/power/mem_sleep` advertises `deep`), but resume is consistently broken.
* This does not appear to be a GNOME or userspace issue; failures occur with manual suspend and before userspace regains control.
* Kernel log‑level suppression (`loglevel=3`) does not reliably affect the behaviour.
* A userspace workaround was required to handle cosmetic early DRM messages, but this does not influence the underlying resume reliability.

## Current workaround (for operability)

The system is currently operated with:

    mem_sleep_default=s2idle no_console_suspend

This configuration restores reliable suspend/resume behaviour, but S3
("deep") cannot be used.

## Conclusion

Suspend‑to‑RAM (S3) resume appears to be fundamentally broken on this
AMD Picasso (Raven2) platform with the current firmware, failing
extremely early during resume. Suspend‑to‑idle works but is sensitive to
timing and requires `no_console_suspend` to avoid hangs.

This may be a candidate for documentation as unsupported S3 on this
platform, or for a platform/DMI‑based quirk to avoid the broken resume
path.

## personal note

I can provide further details if needed.
This was worked out by me using AI help but I have read every word of this summary and tested all the steps.
My system now works with this work-around and I submit this bug report in good faith to hopefully help others.

ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-8-generic 6.17.0-8.8
ProcVersionSignature: Ubuntu 6.17.0-8.8-generic 6.17.2
Uname: Linux 6.17.0-8-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: sebastian 3488 F.... wireplumber
 /dev/snd/controlC0: sebastian 3488 F.... wireplumber
 /dev/snd/seq: sebastian 3472 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 25 13:31:02 2026
InstallationDate: Installed on 2025-11-28 (58 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: wo-we P6
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-8-generic root=UUID=266e1a2f-f26a-44e5-b87f-d980fa5c3454 ro quiet splash no_console_suspend mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
 firmware-sof N/A
 linux-firmware 20250901.git993ff19b-0ubuntu1.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/28/2025
dmi.bios.release: 1.4
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: ADB20D 1.04
dmi.board.asset.tag: Default string
dmi.board.name: ADB20
dmi.board.vendor: Shanghai Hub Union Industural Co.,Ltd
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 35
dmi.chassis.version: V1.0
dmi.ec.firmware.release: 3.14
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrADB20D1.04:bd04/28/2025:br1.4:efr3.14:svnwo-we:pnP6:pvrDefaultstring:rvnShanghaiHubUnionIndusturalCo.,Ltd:rnADB20:rvrDefaultstring:cvn:ct35:cvrV1.0:sku2502:
dmi.product.family: ADB20
dmi.product.name: P6
dmi.product.sku: 2502
dmi.product.version: Default string
dmi.sys.vendor: wo-we

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


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

** Description changed:

Description

This system consistently enters suspend successfully but fails to resume
when using ACPI S3 ("deep"). The failure occurs very early during resume
and leaves the system completely unresponsive, requiring a hard
power‑cycle.

The hardware is a Wo‑We R5 mini PC with an AMD Ryzen 5 3550H (Picasso /
Raven2) CPU and AMI UEFI firmware (ADB20D 1.04, dated 2025‑04‑28).

The issue is reproducible with the Ubuntu 25.10 kernel
(`6.17.0-8-generic`).

## Reproduction (S3 / deep)

1. Boot the system normally.
2. Trigger suspend using:
- sudo systemctl suspend
+         sudo systemctl suspend
3. Allow the system to enter suspend.
4. Attempt to wake using keyboard, mouse, or power button.

## Observed result

* System appears to exit suspend partially:
- * fans spin up
- * power LED becomes steady
+     * fans spin up
+     * power LED becomes steady
* No HDMI output (monitor reports no signal)
* Keyboard and mouse do not respond
* SSH is unreachable
* Magic SysRq does not produce any response
* System remains in this state indefinitely until powered off

After reboot, logs from the previous boot show:

- PM: suspend entry (deep)
+     PM: suspend entry (deep)

There are **no resume‑related log entries** (e.g. "PM: resume from
suspend", "ACPI: Waking up from system sleep state S3", etc.).

I assume the resume failure occurs **before kernel logging and
interrupts are restored**.

## Expected result

The system should resume to a working state with display, input, and
networking restored.
-

## Additional diagnostics

Magic SysRq commands were tested during the hang (r/e/i/s/u) and
produced no observable effect, indicating the kernel is no longer
executing normally after the wake attempt.

The failure is therefore not limited to graphics or userspace and
appears to be a hard early‑resume hang.

## s2idle behaviour

When forcing suspend‑to‑idle (S0 idle) instead of S3:

- mem_sleep_default=s2idle
+     mem_sleep_default=s2idle

the system **does resume successfully**, but only if the following
kernel parameter is also present:

- no_console_suspend
+     no_console_suspend

If `no_console_suspend` is removed, suspend‑to‑idle resumes also begin
to hang again in a similar way.

This suggests the resume path is **timing‑sensitive**, and that keeping
the console active during suspend/resume alters execution timing in a
way that avoids the failure.

## Notes

* The system firmware appears to support S3 (`/sys/power/mem_sleep` advertises `deep`), but resume is consistently broken.
* This does not appear to be a GNOME or userspace issue; failures occur with manual suspend and before userspace regains control.
* Kernel log‑level suppression (`loglevel=3`) does not reliably affect the behaviour.
* A userspace workaround was required to handle cosmetic early DRM messages, but this does not influence the underlying resume reliability.

## Current workaround (for operability)

The system is currently operated with:

- mem_sleep_default=s2idle no_console_suspend
+     mem_sleep_default=s2idle no_console_suspend

This configuration restores reliable suspend/resume behaviour, but S3
("deep") cannot be used.

## Conclusion

Suspend‑to‑RAM (S3) resume appears to be fundamentally broken on this
AMD Picasso (Raven2) platform with the current firmware, failing
extremely early during resume. Suspend‑to‑idle works but is sensitive to
timing and requires `no_console_suspend` to avoid hangs.

This may be a candidate for documentation as unsupported S3 on this
platform, or for a platform/DMI‑based quirk to avoid the broken resume
path.

-
## personal note

I can provide further details if needed.
- This was worked out by me using AI help but I have ready every word of this summary and tested many things.
+ This was worked out by me using AI help but I have read every word of this summary and tested all the steps.
My system now works with this work-around and I submit this bug report in good faith to hopefully help others.

ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-8-generic 6.17.0-8.8
ProcVersionSignature: Ubuntu 6.17.0-8.8-generic 6.17.2
Uname: Linux 6.17.0-8-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
- USER PID ACCESS COMMAND
- /dev/snd/controlC1: sebastian 3488 F.... wireplumber
- /dev/snd/controlC0: sebastian 3488 F.... wireplumber
- /dev/snd/seq: sebastian 3472 F.... pipewire
+  USER PID ACCESS COMMAND
+  /dev/snd/controlC1: sebastian 3488 F.... wireplumber
+  /dev/snd/controlC0: sebastian 3488 F.... wireplumber
+  /dev/snd/seq: sebastian 3472 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 25 13:31:02 2026
InstallationDate: Installed on 2025-11-28 (58 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: wo-we P6
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-8-generic root=UUID=266e1a2f-f26a-44e5-b87f-d980fa5c3454 ro quiet splash no_console_suspend mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
- firmware-sof N/A
- linux-firmware 20250901.git993ff19b-0ubuntu1.5
+  firmware-sof N/A
+  linux-firmware 20250901.git993ff19b-0ubuntu1.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/28/2025
dmi.bios.release: 1.4
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: ADB20D 1.04
dmi.board.asset.tag: Default string
dmi.board.name: ADB20
dmi.board.vendor: Shanghai Hub Union Industural Co.,Ltd
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 35
dmi.chassis.version: V1.0
dmi.ec.firmware.release: 3.14
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrADB20D1.04:bd04/28/2025:br1.4:efr3.14:svnwo-we:pnP6:pvrDefaultstring:rvnShanghaiHubUnionIndusturalCo.,Ltd:rnADB20:rvrDefaultstring:cvn:ct35:cvrV1.0:sku2502:
dmi.product.family: ADB20
dmi.product.name: P6
dmi.product.sku: 2502
dmi.product.version: Default string
dmi.sys.vendor: wo-we

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139016

Title:
S3 (deep) resume hard hang on AMD Ryzen 5 3550H (Picasso); s2idle only
works with no_console_suspend

Status in linux package in Ubuntu:
New

Bug description:
Description

This system consistently enters suspend successfully but fails to
resume when using ACPI S3 ("deep"). The failure occurs very early
during resume and leaves the system completely unresponsive, requiring
a hard power‑cycle.

The hardware is a Wo‑We R5 mini PC with an AMD Ryzen 5 3550H (Picasso
/ Raven2) CPU and AMI UEFI firmware (ADB20D 1.04, dated 2025‑04‑28).

The issue is reproducible with the Ubuntu 25.10 kernel
(`6.17.0-8-generic`).

## Reproduction (S3 / deep)

1. Boot the system normally.
2. Trigger suspend using:
        sudo systemctl suspend
3. Allow the system to enter suspend.
4. Attempt to wake using keyboard, mouse, or power button.

## Observed result

* System appears to exit suspend partially:
    * fans spin up
    * power LED becomes steady
* No HDMI output (monitor reports no signal)
* Keyboard and mouse do not respond
* SSH is unreachable
* Magic SysRq does not produce any response
* System remains in this state indefinitely until powered off

After reboot, logs from the previous boot show:

    PM: suspend entry (deep)

There are **no resume‑related log entries** (e.g. "PM: resume from
suspend", "ACPI: Waking up from system sleep state S3", etc.).

I assume the resume failure occurs **before kernel logging and
interrupts are restored**.

## Expected result

The system should resume to a working state with display, input, and
networking restored.

## Additional diagnostics

Magic SysRq commands were tested during the hang (r/e/i/s/u) and
produced no observable effect, indicating the kernel is no longer
executing normally after the wake attempt.

The failure is therefore not limited to graphics or userspace and
appears to be a hard early‑resume hang.

## s2idle behaviour

When forcing suspend‑to‑idle (S0 idle) instead of S3:

    mem_sleep_default=s2idle

the system **does resume successfully**, but only if the following
kernel parameter is also present:

    no_console_suspend

If `no_console_suspend` is removed, suspend‑to‑idle resumes also begin
to hang again in a similar way.

This suggests the resume path is **timing‑sensitive**, and that
keeping the console active during suspend/resume alters execution
timing in a way that avoids the failure.

## Notes

* The system firmware appears to support S3 (`/sys/power/mem_sleep` advertises `deep`), but resume is consistently broken.
* This does not appear to be a GNOME or userspace issue; failures occur with manual suspend and before userspace regains control.
* Kernel log‑level suppression (`loglevel=3`) does not reliably affect the behaviour.
* A userspace workaround was required to handle cosmetic early DRM messages, but this does not influence the underlying resume reliability.

## Current workaround (for operability)

The system is currently operated with:

    mem_sleep_default=s2idle no_console_suspend

This configuration restores reliable suspend/resume behaviour, but S3
("deep") cannot be used.

## Conclusion

Suspend‑to‑RAM (S3) resume appears to be fundamentally broken on this
AMD Picasso (Raven2) platform with the current firmware, failing
extremely early during resume. Suspend‑to‑idle works but is sensitive
to timing and requires `no_console_suspend` to avoid hangs.

This may be a candidate for documentation as unsupported S3 on this
platform, or for a platform/DMI‑based quirk to avoid the broken resume
path.

## personal note

I can provide further details if needed.
This was worked out by me using AI help but I have read every word of this summary and tested all the steps.
My system now works with this work-around and I submit this bug report in good faith to hopefully help others.

ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-8-generic 6.17.0-8.8
ProcVersionSignature: Ubuntu 6.17.0-8.8-generic 6.17.2
Uname: Linux 6.17.0-8-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: sebastian 3488 F.... wireplumber
 /dev/snd/controlC0: sebastian 3488 F.... wireplumber
 /dev/snd/seq: sebastian 3472 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 25 13:31:02 2026
InstallationDate: Installed on 2025-11-28 (58 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: wo-we P6
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-8-generic root=UUID=266e1a2f-f26a-44e5-b87f-d980fa5c3454 ro quiet splash no_console_suspend mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
 firmware-sof N/A
 linux-firmware 20250901.git993ff19b-0ubuntu1.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/28/2025
dmi.bios.release: 1.4
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: ADB20D 1.04
dmi.board.asset.tag: Default string
dmi.board.name: ADB20
dmi.board.vendor: Shanghai Hub Union Industural Co.,Ltd
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 35
dmi.chassis.version: V1.0
dmi.ec.firmware.release: 3.14
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrADB20D1.04:bd04/28/2025:br1.4:efr3.14:svnwo-we:pnP6:pvrDefaultstring:rvnShanghaiHubUnionIndusturalCo.,Ltd:rnADB20:rvrDefaultstring:cvn:ct35:cvrV1.0:sku2502:
dmi.product.family: ADB20
dmi.product.name: P6
dmi.product.sku: 2502
dmi.product.version: Default string
dmi.sys.vendor: wo-we

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

[Bug 2139015] [NEW] touchpad not working

Public bug reported:

Touchpad is not working properly and not showing up as connected.

ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-8-generic 6.17.0-8.8
ProcVersionSignature: Ubuntu 6.17.0-8.8-generic 6.17.2
Uname: Linux 6.17.0-8-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: drazil 1971 F.... pipewire
drazil 1979 F.... wireplumber
/dev/snd/seq: drazil 1971 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat Jan 24 21:56:27 2026
InstallationDate: Installed on 2025-01-09 (381 days ago)
InstallationMedia: Kubuntu 24.10 "Oracular Oriole" - Release amd64 (20241007.6)
MachineType: LENOVO 83DL
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-8-generic root=UUID=428a0e6f-601e-4d1f-b130-423f573bd40b ro 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:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.5
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2025-12-08 (47 days ago)
dmi.bios.date: 08/28/2024
dmi.bios.release: 1.18
dmi.bios.vendor: LENOVO
dmi.bios.version: NWCN18WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Yoga 7 2-in-1 16IML9
dmi.ec.firmware.release: 1.18
dmi.modalias: dmi:bvnLENOVO:bvrNWCN18WW:bd08/28/2024:br1.18:efr1.18:svnLENOVO:pn83DL:pvrYoga72-in-116IML9:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga72-in-116IML9:skuLENOVO_MT_83DL_BU_idea_FM_Yoga72-in-116IML9:
dmi.product.family: Yoga 7 2-in-1 16IML9
dmi.product.name: 83DL
dmi.product.sku: LENOVO_MT_83DL_BU_idea_FM_Yoga 7 2-in-1 16IML9
dmi.product.version: Yoga 7 2-in-1 16IML9
dmi.sys.vendor: LENOVO

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


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

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139015

Title:
touchpad not working

Status in linux package in Ubuntu:
New

Bug description:
Touchpad is not working properly and not showing up as connected.

ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-8-generic 6.17.0-8.8
ProcVersionSignature: Ubuntu 6.17.0-8.8-generic 6.17.2
Uname: Linux 6.17.0-8-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: drazil 1971 F.... pipewire
drazil 1979 F.... wireplumber
/dev/snd/seq: drazil 1971 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat Jan 24 21:56:27 2026
InstallationDate: Installed on 2025-01-09 (381 days ago)
InstallationMedia: Kubuntu 24.10 "Oracular Oriole" - Release amd64 (20241007.6)
MachineType: LENOVO 83DL
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-8-generic root=UUID=428a0e6f-601e-4d1f-b130-423f573bd40b ro 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:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.5
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2025-12-08 (47 days ago)
dmi.bios.date: 08/28/2024
dmi.bios.release: 1.18
dmi.bios.vendor: LENOVO
dmi.bios.version: NWCN18WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Yoga 7 2-in-1 16IML9
dmi.ec.firmware.release: 1.18
dmi.modalias: dmi:bvnLENOVO:bvrNWCN18WW:bd08/28/2024:br1.18:efr1.18:svnLENOVO:pn83DL:pvrYoga72-in-116IML9:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga72-in-116IML9:skuLENOVO_MT_83DL_BU_idea_FM_Yoga72-in-116IML9:
dmi.product.family: Yoga 7 2-in-1 16IML9
dmi.product.name: 83DL
dmi.product.sku: LENOVO_MT_83DL_BU_idea_FM_Yoga 7 2-in-1 16IML9
dmi.product.version: Yoga 7 2-in-1 16IML9
dmi.sys.vendor: LENOVO

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

[Bug 2139014] Re: Regression: Hang and numerous thinkpad_acpi: acpi_evalf failed: AE_BAD_PARAMETER on HWE Kernel 6.14,Lenovo laptop

** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139014/+attachment/5940697/+files/lspci-vnvn.log

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139014

Title:
Regression: Hang and numerous thinkpad_acpi: acpi_evalf failed:
AE_BAD_PARAMETER on HWE Kernel 6.14,Lenovo laptop

Status in linux package in Ubuntu:
New

Bug description:
Hi,

Sometimes there's a hang that never happened earlier.

Ubuntu 24.04.
There's NUMEROUS error messages in dmesg like these (and the cycle repeats every 5 sec or so I believe):

==================================================
[66469.063656] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063665] ACPI: \: BCTG: evaluate failed
[66469.063722] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063729] ACPI: \: BCTG: evaluate failed
[66469.063782] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063788] ACPI: \: BCSG: evaluate failed
[66469.063863] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063869] ACPI: \: BCSG: evaluate failed
[66469.604040] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604059] ACPI: \: BCTG: evaluate failed
[66469.604156] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604168] ACPI: \: BCTG: evaluate failed
[66469.604255] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604266] ACPI: \: BCSG: evaluate failed
[66469.604358] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604373] ACPI: \: B66474CSG: evaluate failed
[66474.058247] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058260] ACPI: \: BCTG: evaluate failed
[66474.058326] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058333] ACPI: \: BCTG: evaluate failed
[66474.058387] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058394] ACPI: \: BCSG: evaluate failed
[66474.058447] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058453] ACPI: \: BCSG: evaluate failed
[66474.059488] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66474.059497] ACPI: \: BCTG: evaluate failed
======================================================

Anybody knows whats "BCTG" and "BCSG"?

Kernel 6.14.0-37-generic
The actual package is linux-image-generic-hwe-24.04, but couldn't find it in the search.

The above is written to syslog (which is huge now).
Thinkbook G7 ARP (Ryzen).
I believe this is a regression that started with a recent update.

Thank you.

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

[Bug 2139014] Re: Regression: Hang and numerous thinkpad_acpi: acpi_evalf failed: AE_BAD_PARAMETER on HWE Kernel 6.14,Lenovo laptop

** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139014/+attachment/5940696/+files/version.log

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139014

Title:
Regression: Hang and numerous thinkpad_acpi: acpi_evalf failed:
AE_BAD_PARAMETER on HWE Kernel 6.14,Lenovo laptop

Status in linux package in Ubuntu:
New

Bug description:
Hi,

Sometimes there's a hang that never happened earlier.

Ubuntu 24.04.
There's NUMEROUS error messages in dmesg like these (and the cycle repeats every 5 sec or so I believe):

==================================================
[66469.063656] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063665] ACPI: \: BCTG: evaluate failed
[66469.063722] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063729] ACPI: \: BCTG: evaluate failed
[66469.063782] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063788] ACPI: \: BCSG: evaluate failed
[66469.063863] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063869] ACPI: \: BCSG: evaluate failed
[66469.604040] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604059] ACPI: \: BCTG: evaluate failed
[66469.604156] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604168] ACPI: \: BCTG: evaluate failed
[66469.604255] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604266] ACPI: \: BCSG: evaluate failed
[66469.604358] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604373] ACPI: \: B66474CSG: evaluate failed
[66474.058247] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058260] ACPI: \: BCTG: evaluate failed
[66474.058326] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058333] ACPI: \: BCTG: evaluate failed
[66474.058387] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058394] ACPI: \: BCSG: evaluate failed
[66474.058447] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058453] ACPI: \: BCSG: evaluate failed
[66474.059488] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66474.059497] ACPI: \: BCTG: evaluate failed
======================================================

Anybody knows whats "BCTG" and "BCSG"?

Kernel 6.14.0-37-generic
The actual package is linux-image-generic-hwe-24.04, but couldn't find it in the search.

The above is written to syslog (which is huge now).
Thinkbook G7 ARP (Ryzen).
I believe this is a regression that started with a recent update.

Thank you.

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

[Bug 2139014] [NEW] Regression: Hang and numerous thinkpad_acpi: acpi_evalf failed: AE_BAD_PARAMETER on HWE Kernel 6.14,Lenovo laptop

Public bug reported:

Hi,

Sometimes there's a hang that never happened earlier.

Ubuntu 24.04.
There's NUMEROUS error messages in dmesg like these (and the cycle repeats every 5 sec or so I believe):

==================================================
[66469.063656] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063665] ACPI: \: BCTG: evaluate failed
[66469.063722] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063729] ACPI: \: BCTG: evaluate failed
[66469.063782] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063788] ACPI: \: BCSG: evaluate failed
[66469.063863] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063869] ACPI: \: BCSG: evaluate failed
[66469.604040] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604059] ACPI: \: BCTG: evaluate failed
[66469.604156] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604168] ACPI: \: BCTG: evaluate failed
[66469.604255] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604266] ACPI: \: BCSG: evaluate failed
[66469.604358] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604373] ACPI: \: B66474CSG: evaluate failed
[66474.058247] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058260] ACPI: \: BCTG: evaluate failed
[66474.058326] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058333] ACPI: \: BCTG: evaluate failed
[66474.058387] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058394] ACPI: \: BCSG: evaluate failed
[66474.058447] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058453] ACPI: \: BCSG: evaluate failed
[66474.059488] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66474.059497] ACPI: \: BCTG: evaluate failed
======================================================

Anybody knows whats "BCTG" and "BCSG"?

Kernel 6.14.0-37-generic
The actual package is linux-image-generic-hwe-24.04, but couldn't find it in the search.

The above is written to syslog (which is huge now).
Thinkbook G7 ARP (Ryzen).
I believe this is a regression that started with a recent update.

Thank you.

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


** Tags: kernel-bug

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139014

Title:
Regression: Hang and numerous thinkpad_acpi: acpi_evalf failed:
AE_BAD_PARAMETER on HWE Kernel 6.14,Lenovo laptop

Status in linux package in Ubuntu:
New

Bug description:
Hi,

Sometimes there's a hang that never happened earlier.

Ubuntu 24.04.
There's NUMEROUS error messages in dmesg like these (and the cycle repeats every 5 sec or so I believe):

==================================================
[66469.063656] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063665] ACPI: \: BCTG: evaluate failed
[66469.063722] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063729] ACPI: \: BCTG: evaluate failed
[66469.063782] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063788] ACPI: \: BCSG: evaluate failed
[66469.063863] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.063869] ACPI: \: BCSG: evaluate failed
[66469.604040] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604059] ACPI: \: BCTG: evaluate failed
[66469.604156] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604168] ACPI: \: BCTG: evaluate failed
[66469.604255] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604266] ACPI: \: BCSG: evaluate failed
[66469.604358] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66469.604373] ACPI: \: B66474CSG: evaluate failed
[66474.058247] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058260] ACPI: \: BCTG: evaluate failed
[66474.058326] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058333] ACPI: \: BCTG: evaluate failed
[66474.058387] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058394] ACPI: \: BCSG: evaluate failed
[66474.058447] thinkpad_acpi: acpi_evalf(BCSG, dd, ...) failed: AE_BAD_PARAMETER
[66474.058453] ACPI: \: BCSG: evaluate failed
[66474.059488] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_BAD_PARAMETER
[66474.059497] ACPI: \: BCTG: evaluate failed
======================================================

Anybody knows whats "BCTG" and "BCSG"?

Kernel 6.14.0-37-generic
The actual package is linux-image-generic-hwe-24.04, but couldn't find it in the search.

The above is written to syslog (which is huge now).
Thinkbook G7 ARP (Ryzen).
I believe this is a regression that started with a recent update.

Thank you.

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

[Bug 2138991] Re: Dell 16 Premium DA16250 webcam (OV02C10) not working - INT3472 GPIO type 0x02 unknown

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

Title:
Dell 16 Premium DA16250 webcam (OV02C10) not working - INT3472 GPIO
type 0x02 unknown

Status in linux package in Ubuntu:
New

Bug description:
## Description

### Summary
The integrated webcam on Dell 16 Premium (DA16250) with Intel Meteor Lake CPU does not work on Ubuntu 24.04 with OEM kernel. The camera sensor (OV02C10) is detected but fails to initialize due to unsupported GPIO type 0x02 in the INT3472 discrete driver.

### System Information
- **Hardware:** Dell 16 Premium DA16250
- **CPU:** Intel Core Ultra 9 285H (Meteor Lake)
- **Camera Sensor:** OmniVision OV02C10 (ACPI: OVTI02C1:00)
- **OS:** Ubuntu 24.04.3 LTS
- **Kernel:** 6.14.0-1019-oem

### Steps to Reproduce
1. Install Ubuntu 24.04 on Dell 16 Premium DA16250
2. Install OEM kernel: `sudo apt install linux-oem-24.04`
3. Install IPU6 modules: `sudo apt install linux-modules-ipu6-6.14.0-1019-oem`
4. Install camera HAL: `sudo apt install libcamhal-ipu6epmtl` (from OEM PPA)
5. Reboot and try to use the webcam

### Expected Behavior
Webcam should be detected and functional in applications like Cheese, Firefox, Chromium.

### Actual Behavior
Camera is detected by the IPU6 driver but fails to initialize. The sensor does not register in the media pipeline.

### Error Messages (from dmesg)
```
int3472-discrete INT3472:0c: GPIO type 0x02 unknown; the sensor may not work
intel-ipu6 0000:00:05.0: Found supported sensor OVTI02C1:00
intel-ipu6 0000:00:05.0: Connected 1 cameras
```

### Error Messages (from GStreamer test)
```
CamHAL[INF] aiqb file name AR0234_TGL_10bits.aiqb
CamHAL[ERR] Stream config is not supported. format:V4L2_PIX_FMT_NV12 (1920x1080)
```

The camera HAL loads the wrong config file (AR0234 instead of OV02C10)
because the sensor is not bound to the I2C bus.

### Diagnosis
The ov02c10 kernel module is loaded but not bound to any device:
```
$ ls /sys/bus/i2c/drivers/ov02c10/
bind module uevent unbind
```

The ACPI device exists and is enabled (status 15):
```
$ cat /sys/bus/acpi/devices/OVTI02C1:00/status
15
```

But there is no physical_node because the INT3472 GPIO initialization
fails.

### Root Cause
GPIO type 0x02 is a "strobe" GPIO used for LED/IR control on Meteor Lake systems. The int3472-discrete driver does not recognize this GPIO type, preventing proper camera power-up.

### Existing Kernel Patch
A patch exists that adds support for GPIO type 0x02 (strobe):
https://patchwork.kernel.org/project/linux-media/patch/20231007021309.9332-1-hao.yao@intel.com/

### Related Issues
- Intel IPU6 drivers: https://github.com/intel/ipu6-drivers/issues/413
- Intel IPU6 drivers: https://github.com/intel/ipu6-drivers/issues/40
- Ubuntu Bug #2117188: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2117188

### Workarounds Attempted (None Successful)
1. Added `intel_iommu=on` to kernel parameters
2. Fixed /dev/ipu-psys0 permissions with udev rules
3. Installed libcamhal-ipu6epmtl from OEM PPA
4. Tried Dell OEM archive packages

### Request
Please backport the INT3472 GPIO strobe patch to the Ubuntu OEM kernel to support Dell 16 Premium and other Meteor Lake laptops with OV02C10 cameras.

## Attachments

### uname -a
```
Linux Dell-16-Premium-DA16250 6.14.0-1019-oem #19-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 18 05:40:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
```

### CPU Info
```
vendor_id : GenuineIntel
cpu family : 6
model : 197
model name : Intel(R) Core(TM) Ultra 9 285H
```

### lspci (IPU6 device)
```
0000:00:05.0 Multimedia controller [0480]: Intel Corporation Device [8086:7d19] (rev 05)
Subsystem: Dell Device [1028:0ce7]
Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 3
Memory at 581c000000 (64-bit, non-prefetchable) [size=16M]
Kernel driver in use: intel-ipu6
Kernel modules: intel_ipu6
```

### dmesg (camera related)
```
[ 16.744854] int3472-discrete INT3472:0c: GPIO type 0x02 unknown; the sensor may not work
[ 16.764935] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002)
[ 16.781627] intel-ipu6 0000:00:05.0: Found supported sensor OVTI02C1:00
[ 16.781717] intel-ipu6 0000:00:05.0: Connected 1 cameras
[ 16.784617] intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE
[ 16.821495] intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE
[ 16.879001] intel-ipu6 0000:00:05.0: CSE authenticate_run done
[ 16.879013] intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6
[ 17.565317] intel_ipu6_psys.psys intel_ipu6.psys.40: pkg_dir entry count:8
[ 17.565808] intel_ipu6_psys.psys intel_ipu6.psys.40: psys probe minor: 0
[ 2663.927955] intel-ipu6 0000:00:05.0: IPU6 in secure mode
[ 7592.628584] intel-ipu6 0000:00:05.0: IPU6 in secure mode
```

### Installed packages (camera related)
```
ii gstreamer1.0-icamera 0~git202509260937.4fb31db~ubuntu24.04.7 amd64
ii libcamhal-common 0~git202601200757.9899efa~ubuntu24.04.1 all
ii libcamhal-ipu6ep 0~git202601200757.9899efa~ubuntu24.04.1 amd64
ii libcamhal-ipu6epmtl 0~git202601200757.9899efa~ubuntu24.04.1 amd64
ii libcamhal0 0~git202601200757.9899efa~ubuntu24.04.1 amd64
ii linux-image-6.14.0-1019-oem 6.14.0-1019.19 amd64
ii linux-image-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64
ii linux-image-generic-hwe-24.04 6.14.0-37.37~24.04.1 amd64
ii linux-image-oem-24.04 6.14.0-1019.19 amd64
ii linux-modules-6.14.0-1019-oem 6.14.0-1019.19 amd64
ii linux-modules-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64
ii linux-modules-extra-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64
ii linux-modules-ipu6-6.14.0-1019-oem 6.14.0-1019.19 amd64
```

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

[Bug 2098730] Re: Kernel 6.8.0 memory leak

I can reproduce this issue on Ubuntu 22.04 with the HWE kernel
6.8.0-90-generic.

Test environment:
- Ubuntu 22.04.5 LTS (Jammy)
- Kernel: 6.8.0-90-generic (HWE)
- Architecture: amd64
- auditd enabled and running

Audit rules used:
/etc/audit/rules.d/audit-leak.rules:
-D
-b 8192
-f 1
-r 100
-a always,exit -F arch=b64 -S openat -S truncate -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access

Reproduction steps:
1. Loaded the above rules with `augenrules --load` and verified with `auditctl -l`.
2. As an unprivileged user (UID >= 1000), executed:
while :; do cat /root/secretfile > /dev/null; done
3. Monitored kernel memory with:
watch -d -n 1 'grep -i SUnreclaim /proc/meminfo'
and `slabtop -s c`.

Observed behavior:
- SUnreclaim increases steadily over time.
- slabtop shows kmalloc-rnd-(*)-2k and skbuff_head_cache growing continuously.
- Behavior matches the original report and the upstream stack trace involving audit_log_start() and __alloc_skb().

This confirms the memory leak on the 6.8.0 HWE kernel series.

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2098730

Title:
Kernel 6.8.0 memory leak

Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Noble:
Confirmed
Status in linux source package in Oracular:
Won't Fix
Status in linux source package in Plucky:
Won't Fix

Bug description:
We discovered a kernel memory leak in the Ubuntu 24.04 distribution
using the 6.8.0 series kernel while testing on our cluster.

After performing a fresh installation of Ubuntu Server 24.04 from the
official ISO: `https://ubuntu.com/download/server/thank-
you?version=24.04.1&architecture=amd64&lts=true`, with the built-in
kernel `linux-image-6.8.0-51-generic`, we observed that Slab consumes
all available memory due to the kernel threads `kmalloc-rnd-(*)-2k`
and `skbuff_head_cache` when the audit subsystem is enabled. The value
of `SUnreclaim` in `/proc/meminfo` nearly reaches the system's total
memory.

We validated this bug on both amd64 and aarch64 architectures,
affecting bare metal and virtual machines alike across all platforms.
Here's the stack information obtained using the eBPF tool `memleak`:
"https://github.com/iovisor/bcc/blob/master/tools/memleak.py" to
detect the kernel memory leak:

195362816 bytes in 5962 allocations from stack
0xffffffff96652314 __alloc_pages+0x264 [kernel]
0xffffffff96652314 __alloc_pages+0x264 [kernel]
0xffffffff9665b0a8 allocate_slab+0xa8 [kernel]
0xffffffff9665b3b8 new_slab+0x38 [kernel]
0xffffffff9665e3d5 ___slab_alloc+0x435 [kernel]
0xffffffff9665f62b __kmalloc_node_track_caller+0x18b [kernel]
0xffffffff970d8317 kmalloc_reserve+0x67 [kernel]
0xffffffff970db4aa __alloc_skb+0x8a [kernel]
0xffffffff96457f98 audit_log_start+0x198 [kernel]
0xffffffff96462103 audit_log_exit+0x433 [kernel]
0xffffffff96462dbe __audit_syscall_exit+0xee [kernel]
0xffffffff963f111b syscall_exit_work+0x12b [kernel]
0xffffffff963f1189 syscall_exit_to_user_mode_prepare+0x39 [kernel]
0xffffffff97430ae1 syscall_exit_to_user_mode+0x11 [kernel]
0xffffffff97428fec do_syscall_64+0x8c [kernel]
0xffffffff97600130 entry_SYSCALL_64_after_hwframe+0x78 [kernel]

To reproduce this memory leak issue, follow these steps:
1. Install and start auditd.
2. Add audit rules in `/etc/audit/rules.d/audit.rules`:
```
-D
-b 8192
-f 1
-r 100
-a always,exit -F arch=b64 -S openat -S truncate -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
```
3. Reboot or run `augenrules --load`, then execute `auditctl -l` to verify that the audit rule above has been loaded.
4. Run command `while :; do cat /proc/1/environ; done` as a normal user (uid >= 1000) to triger the audit events.
5. Monitor kernel memory allocation by running either:
```
watch -d -n 1 'cat /proc/meminfo | grep -i SUnreclaim'
```
or simply use
```
slabtop -s c
```

We tested several kernels within the 6.8.0 series, and this bug was
present in all of them, including when installing HWE Kernel 6.8.0 in
Ubuntu 22.04 via `apt install linux-generic-hwe-22.04`. However, after
installing mainline kernels v6.8.1 or higher from
https://kernel.ubunt.com/mainline/, this bug disappears, indicating it
may have been fixed on upstream.

Therefore, it is essential to update your stable repository's kernel and refresh your ISO accordingly.
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D0c', '/dev/snd/hwC0D0', '/dev/snd/controlC0', '/dev/snd/by-path'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-08-13 (191 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release arm64 (20240423)
IwConfig:
lo no wireless extensions.

enp0s5 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 203a:fffc PARALLELS Virtual Mouse
Bus 003 Device 003: ID 203a:fffb PARALLELS Virtual Keyboard
MachineType: Parallels International GmbH. Parallels ARM Virtual Machine
NonfreeKernelModules: prl_fs_freeze prl_tg
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=tmux-256color
ProcFB: 0 virtio_gpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-53-generic root=UUID=0c00eea2-089b-4002-90e1-ca43db4a623e ro
ProcVersionSignature: Ubuntu 6.8.0-53.55-generic 6.8.12
RelatedPackageVersions:
linux-restricted-modules-6.8.0-53-generic N/A
linux-backports-modules-6.8.0-53-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.9
RfKill:

Tags: noble
Uname: Linux 6.8.0-53-generic aarch64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: False
dmi.bios.date: Mon, 23 Dec 2024 15:54:53
dmi.bios.release: 0.1
dmi.bios.vendor: Parallels International GmbH.
dmi.bios.version: 20.2.0 (55872)
dmi.board.asset.tag: None
dmi.board.name: Parallels ARM Virtual Platform
dmi.board.vendor: Parallels ARM Virtual Machine
dmi.board.version: 0.1
dmi.chassis.type: 2
dmi.chassis.vendor: Parallels International GmbH.
dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr20.2.0(55872):bdMon,23Dec2024155453:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM:
dmi.product.family: Parallels VM
dmi.product.name: Parallels ARM Virtual Machine
dmi.product.sku: Parallels_ARM_VM
dmi.product.version: 0.1
dmi.sys.vendor: Parallels International GmbH.

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

[Bug 2138991] [NEW] Dell 16 Premium DA16250 webcam (OV02C10) not working - INT3472 GPIO type 0x02 unknown

Public bug reported:

## Description

### Summary
The integrated webcam on Dell 16 Premium (DA16250) with Intel Meteor Lake CPU does not work on Ubuntu 24.04 with OEM kernel. The camera sensor (OV02C10) is detected but fails to initialize due to unsupported GPIO type 0x02 in the INT3472 discrete driver.

### System Information
- **Hardware:** Dell 16 Premium DA16250
- **CPU:** Intel Core Ultra 9 285H (Meteor Lake)
- **Camera Sensor:** OmniVision OV02C10 (ACPI: OVTI02C1:00)
- **OS:** Ubuntu 24.04.3 LTS
- **Kernel:** 6.14.0-1019-oem

### Steps to Reproduce
1. Install Ubuntu 24.04 on Dell 16 Premium DA16250
2. Install OEM kernel: `sudo apt install linux-oem-24.04`
3. Install IPU6 modules: `sudo apt install linux-modules-ipu6-6.14.0-1019-oem`
4. Install camera HAL: `sudo apt install libcamhal-ipu6epmtl` (from OEM PPA)
5. Reboot and try to use the webcam

### Expected Behavior
Webcam should be detected and functional in applications like Cheese, Firefox, Chromium.

### Actual Behavior
Camera is detected by the IPU6 driver but fails to initialize. The sensor does not register in the media pipeline.

### Error Messages (from dmesg)
```
int3472-discrete INT3472:0c: GPIO type 0x02 unknown; the sensor may not work
intel-ipu6 0000:00:05.0: Found supported sensor OVTI02C1:00
intel-ipu6 0000:00:05.0: Connected 1 cameras
```

### Error Messages (from GStreamer test)
```
CamHAL[INF] aiqb file name AR0234_TGL_10bits.aiqb
CamHAL[ERR] Stream config is not supported. format:V4L2_PIX_FMT_NV12 (1920x1080)
```

The camera HAL loads the wrong config file (AR0234 instead of OV02C10)
because the sensor is not bound to the I2C bus.

### Diagnosis
The ov02c10 kernel module is loaded but not bound to any device:
```
$ ls /sys/bus/i2c/drivers/ov02c10/
bind module uevent unbind
```

The ACPI device exists and is enabled (status 15):
```
$ cat /sys/bus/acpi/devices/OVTI02C1:00/status
15
```

But there is no physical_node because the INT3472 GPIO initialization
fails.

### Root Cause
GPIO type 0x02 is a "strobe" GPIO used for LED/IR control on Meteor Lake systems. The int3472-discrete driver does not recognize this GPIO type, preventing proper camera power-up.

### Existing Kernel Patch
A patch exists that adds support for GPIO type 0x02 (strobe):
https://patchwork.kernel.org/project/linux-media/patch/20231007021309.9332-1-hao.yao@intel.com/

### Related Issues
- Intel IPU6 drivers: https://github.com/intel/ipu6-drivers/issues/413
- Intel IPU6 drivers: https://github.com/intel/ipu6-drivers/issues/40
- Ubuntu Bug #2117188: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2117188

### Workarounds Attempted (None Successful)
1. Added `intel_iommu=on` to kernel parameters
2. Fixed /dev/ipu-psys0 permissions with udev rules
3. Installed libcamhal-ipu6epmtl from OEM PPA
4. Tried Dell OEM archive packages

### Request
Please backport the INT3472 GPIO strobe patch to the Ubuntu OEM kernel to support Dell 16 Premium and other Meteor Lake laptops with OV02C10 cameras.

## Attachments

### uname -a
```
Linux Dell-16-Premium-DA16250 6.14.0-1019-oem #19-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 18 05:40:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
```

### CPU Info
```
vendor_id : GenuineIntel
cpu family : 6
model : 197
model name : Intel(R) Core(TM) Ultra 9 285H
```

### lspci (IPU6 device)
```
0000:00:05.0 Multimedia controller [0480]: Intel Corporation Device [8086:7d19] (rev 05)
Subsystem: Dell Device [1028:0ce7]
Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 3
Memory at 581c000000 (64-bit, non-prefetchable) [size=16M]
Kernel driver in use: intel-ipu6
Kernel modules: intel_ipu6
```

### dmesg (camera related)
```
[ 16.744854] int3472-discrete INT3472:0c: GPIO type 0x02 unknown; the sensor may not work
[ 16.764935] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002)
[ 16.781627] intel-ipu6 0000:00:05.0: Found supported sensor OVTI02C1:00
[ 16.781717] intel-ipu6 0000:00:05.0: Connected 1 cameras
[ 16.784617] intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE
[ 16.821495] intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE
[ 16.879001] intel-ipu6 0000:00:05.0: CSE authenticate_run done
[ 16.879013] intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6
[ 17.565317] intel_ipu6_psys.psys intel_ipu6.psys.40: pkg_dir entry count:8
[ 17.565808] intel_ipu6_psys.psys intel_ipu6.psys.40: psys probe minor: 0
[ 2663.927955] intel-ipu6 0000:00:05.0: IPU6 in secure mode
[ 7592.628584] intel-ipu6 0000:00:05.0: IPU6 in secure mode
```

### Installed packages (camera related)
```
ii gstreamer1.0-icamera 0~git202509260937.4fb31db~ubuntu24.04.7 amd64
ii libcamhal-common 0~git202601200757.9899efa~ubuntu24.04.1 all
ii libcamhal-ipu6ep 0~git202601200757.9899efa~ubuntu24.04.1 amd64
ii libcamhal-ipu6epmtl 0~git202601200757.9899efa~ubuntu24.04.1 amd64
ii libcamhal0 0~git202601200757.9899efa~ubuntu24.04.1 amd64
ii linux-image-6.14.0-1019-oem 6.14.0-1019.19 amd64
ii linux-image-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64
ii linux-image-generic-hwe-24.04 6.14.0-37.37~24.04.1 amd64
ii linux-image-oem-24.04 6.14.0-1019.19 amd64
ii linux-modules-6.14.0-1019-oem 6.14.0-1019.19 amd64
ii linux-modules-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64
ii linux-modules-extra-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64
ii linux-modules-ipu6-6.14.0-1019-oem 6.14.0-1019.19 amd64
```

** Affects: linux (Ubuntu)
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/2138991

Title:
Dell 16 Premium DA16250 webcam (OV02C10) not working - INT3472 GPIO
type 0x02 unknown

Status in linux package in Ubuntu:
New

Bug description:
## Description

### Summary
The integrated webcam on Dell 16 Premium (DA16250) with Intel Meteor Lake CPU does not work on Ubuntu 24.04 with OEM kernel. The camera sensor (OV02C10) is detected but fails to initialize due to unsupported GPIO type 0x02 in the INT3472 discrete driver.

### System Information
- **Hardware:** Dell 16 Premium DA16250
- **CPU:** Intel Core Ultra 9 285H (Meteor Lake)
- **Camera Sensor:** OmniVision OV02C10 (ACPI: OVTI02C1:00)
- **OS:** Ubuntu 24.04.3 LTS
- **Kernel:** 6.14.0-1019-oem

### Steps to Reproduce
1. Install Ubuntu 24.04 on Dell 16 Premium DA16250
2. Install OEM kernel: `sudo apt install linux-oem-24.04`
3. Install IPU6 modules: `sudo apt install linux-modules-ipu6-6.14.0-1019-oem`
4. Install camera HAL: `sudo apt install libcamhal-ipu6epmtl` (from OEM PPA)
5. Reboot and try to use the webcam

### Expected Behavior
Webcam should be detected and functional in applications like Cheese, Firefox, Chromium.

### Actual Behavior
Camera is detected by the IPU6 driver but fails to initialize. The sensor does not register in the media pipeline.

### Error Messages (from dmesg)
```
int3472-discrete INT3472:0c: GPIO type 0x02 unknown; the sensor may not work
intel-ipu6 0000:00:05.0: Found supported sensor OVTI02C1:00
intel-ipu6 0000:00:05.0: Connected 1 cameras
```

### Error Messages (from GStreamer test)
```
CamHAL[INF] aiqb file name AR0234_TGL_10bits.aiqb
CamHAL[ERR] Stream config is not supported. format:V4L2_PIX_FMT_NV12 (1920x1080)
```

The camera HAL loads the wrong config file (AR0234 instead of OV02C10)
because the sensor is not bound to the I2C bus.

### Diagnosis
The ov02c10 kernel module is loaded but not bound to any device:
```
$ ls /sys/bus/i2c/drivers/ov02c10/
bind module uevent unbind
```

The ACPI device exists and is enabled (status 15):
```
$ cat /sys/bus/acpi/devices/OVTI02C1:00/status
15
```

But there is no physical_node because the INT3472 GPIO initialization
fails.

### Root Cause
GPIO type 0x02 is a "strobe" GPIO used for LED/IR control on Meteor Lake systems. The int3472-discrete driver does not recognize this GPIO type, preventing proper camera power-up.

### Existing Kernel Patch
A patch exists that adds support for GPIO type 0x02 (strobe):
https://patchwork.kernel.org/project/linux-media/patch/20231007021309.9332-1-hao.yao@intel.com/

### Related Issues
- Intel IPU6 drivers: https://github.com/intel/ipu6-drivers/issues/413
- Intel IPU6 drivers: https://github.com/intel/ipu6-drivers/issues/40
- Ubuntu Bug #2117188: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2117188

### Workarounds Attempted (None Successful)
1. Added `intel_iommu=on` to kernel parameters
2. Fixed /dev/ipu-psys0 permissions with udev rules
3. Installed libcamhal-ipu6epmtl from OEM PPA
4. Tried Dell OEM archive packages

### Request
Please backport the INT3472 GPIO strobe patch to the Ubuntu OEM kernel to support Dell 16 Premium and other Meteor Lake laptops with OV02C10 cameras.

## Attachments

### uname -a
```
Linux Dell-16-Premium-DA16250 6.14.0-1019-oem #19-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 18 05:40:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
```

### CPU Info
```
vendor_id : GenuineIntel
cpu family : 6
model : 197
model name : Intel(R) Core(TM) Ultra 9 285H
```

### lspci (IPU6 device)
```
0000:00:05.0 Multimedia controller [0480]: Intel Corporation Device [8086:7d19] (rev 05)
Subsystem: Dell Device [1028:0ce7]
Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 3
Memory at 581c000000 (64-bit, non-prefetchable) [size=16M]
Kernel driver in use: intel-ipu6
Kernel modules: intel_ipu6
```

### dmesg (camera related)
```
[ 16.744854] int3472-discrete INT3472:0c: GPIO type 0x02 unknown; the sensor may not work
[ 16.764935] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002)
[ 16.781627] intel-ipu6 0000:00:05.0: Found supported sensor OVTI02C1:00
[ 16.781717] intel-ipu6 0000:00:05.0: Connected 1 cameras
[ 16.784617] intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE
[ 16.821495] intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE
[ 16.879001] intel-ipu6 0000:00:05.0: CSE authenticate_run done
[ 16.879013] intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6
[ 17.565317] intel_ipu6_psys.psys intel_ipu6.psys.40: pkg_dir entry count:8
[ 17.565808] intel_ipu6_psys.psys intel_ipu6.psys.40: psys probe minor: 0
[ 2663.927955] intel-ipu6 0000:00:05.0: IPU6 in secure mode
[ 7592.628584] intel-ipu6 0000:00:05.0: IPU6 in secure mode
```

### Installed packages (camera related)
```
ii gstreamer1.0-icamera 0~git202509260937.4fb31db~ubuntu24.04.7 amd64
ii libcamhal-common 0~git202601200757.9899efa~ubuntu24.04.1 all
ii libcamhal-ipu6ep 0~git202601200757.9899efa~ubuntu24.04.1 amd64
ii libcamhal-ipu6epmtl 0~git202601200757.9899efa~ubuntu24.04.1 amd64
ii libcamhal0 0~git202601200757.9899efa~ubuntu24.04.1 amd64
ii linux-image-6.14.0-1019-oem 6.14.0-1019.19 amd64
ii linux-image-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64
ii linux-image-generic-hwe-24.04 6.14.0-37.37~24.04.1 amd64
ii linux-image-oem-24.04 6.14.0-1019.19 amd64
ii linux-modules-6.14.0-1019-oem 6.14.0-1019.19 amd64
ii linux-modules-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64
ii linux-modules-extra-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64
ii linux-modules-ipu6-6.14.0-1019-oem 6.14.0-1019.19 amd64
```

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

[Bug 2098730] Re: Kernel 6.8.0 memory leak

I can confirm similar behavior on Ubuntu 22.04/24.04 with Realtek
ALC887-VD.

Hardware:
- Realtek ALC887-VD (Azalia)
- Drivers: snd_hda_intel
- HDMI device: AMD Trinity HDMI Audio
- Analog device: AMD FCH Azalia

WirePlumber logs:
Error opening low-level control device 'hw:0': No such file or directory
can't open control for card hw:0
Card can't get card_name from card_index 1

PipeWire logs:
mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown

System info:
PipeWire version: 1.0.5
Kernel: 6.14.0-37-generic
ALSA API: kernel-api

The issue appears on every boot.

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2098730

Title:
Kernel 6.8.0 memory leak

Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Noble:
Confirmed
Status in linux source package in Oracular:
Won't Fix
Status in linux source package in Plucky:
Won't Fix

Bug description:
We discovered a kernel memory leak in the Ubuntu 24.04 distribution
using the 6.8.0 series kernel while testing on our cluster.

After performing a fresh installation of Ubuntu Server 24.04 from the
official ISO: `https://ubuntu.com/download/server/thank-
you?version=24.04.1&architecture=amd64&lts=true`, with the built-in
kernel `linux-image-6.8.0-51-generic`, we observed that Slab consumes
all available memory due to the kernel threads `kmalloc-rnd-(*)-2k`
and `skbuff_head_cache` when the audit subsystem is enabled. The value
of `SUnreclaim` in `/proc/meminfo` nearly reaches the system's total
memory.

We validated this bug on both amd64 and aarch64 architectures,
affecting bare metal and virtual machines alike across all platforms.
Here's the stack information obtained using the eBPF tool `memleak`:
"https://github.com/iovisor/bcc/blob/master/tools/memleak.py" to
detect the kernel memory leak:

195362816 bytes in 5962 allocations from stack
0xffffffff96652314 __alloc_pages+0x264 [kernel]
0xffffffff96652314 __alloc_pages+0x264 [kernel]
0xffffffff9665b0a8 allocate_slab+0xa8 [kernel]
0xffffffff9665b3b8 new_slab+0x38 [kernel]
0xffffffff9665e3d5 ___slab_alloc+0x435 [kernel]
0xffffffff9665f62b __kmalloc_node_track_caller+0x18b [kernel]
0xffffffff970d8317 kmalloc_reserve+0x67 [kernel]
0xffffffff970db4aa __alloc_skb+0x8a [kernel]
0xffffffff96457f98 audit_log_start+0x198 [kernel]
0xffffffff96462103 audit_log_exit+0x433 [kernel]
0xffffffff96462dbe __audit_syscall_exit+0xee [kernel]
0xffffffff963f111b syscall_exit_work+0x12b [kernel]
0xffffffff963f1189 syscall_exit_to_user_mode_prepare+0x39 [kernel]
0xffffffff97430ae1 syscall_exit_to_user_mode+0x11 [kernel]
0xffffffff97428fec do_syscall_64+0x8c [kernel]
0xffffffff97600130 entry_SYSCALL_64_after_hwframe+0x78 [kernel]

To reproduce this memory leak issue, follow these steps:
1. Install and start auditd.
2. Add audit rules in `/etc/audit/rules.d/audit.rules`:
```
-D
-b 8192
-f 1
-r 100
-a always,exit -F arch=b64 -S openat -S truncate -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
```
3. Reboot or run `augenrules --load`, then execute `auditctl -l` to verify that the audit rule above has been loaded.
4. Run command `while :; do cat /proc/1/environ; done` as a normal user (uid >= 1000) to triger the audit events.
5. Monitor kernel memory allocation by running either:
```
watch -d -n 1 'cat /proc/meminfo | grep -i SUnreclaim'
```
or simply use
```
slabtop -s c
```

We tested several kernels within the 6.8.0 series, and this bug was
present in all of them, including when installing HWE Kernel 6.8.0 in
Ubuntu 22.04 via `apt install linux-generic-hwe-22.04`. However, after
installing mainline kernels v6.8.1 or higher from
https://kernel.ubunt.com/mainline/, this bug disappears, indicating it
may have been fixed on upstream.

Therefore, it is essential to update your stable repository's kernel and refresh your ISO accordingly.
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D0c', '/dev/snd/hwC0D0', '/dev/snd/controlC0', '/dev/snd/by-path'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-08-13 (191 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release arm64 (20240423)
IwConfig:
lo no wireless extensions.

enp0s5 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 203a:fffc PARALLELS Virtual Mouse
Bus 003 Device 003: ID 203a:fffb PARALLELS Virtual Keyboard
MachineType: Parallels International GmbH. Parallels ARM Virtual Machine
NonfreeKernelModules: prl_fs_freeze prl_tg
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=tmux-256color
ProcFB: 0 virtio_gpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-53-generic root=UUID=0c00eea2-089b-4002-90e1-ca43db4a623e ro
ProcVersionSignature: Ubuntu 6.8.0-53.55-generic 6.8.12
RelatedPackageVersions:
linux-restricted-modules-6.8.0-53-generic N/A
linux-backports-modules-6.8.0-53-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.9
RfKill:

Tags: noble
Uname: Linux 6.8.0-53-generic aarch64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: False
dmi.bios.date: Mon, 23 Dec 2024 15:54:53
dmi.bios.release: 0.1
dmi.bios.vendor: Parallels International GmbH.
dmi.bios.version: 20.2.0 (55872)
dmi.board.asset.tag: None
dmi.board.name: Parallels ARM Virtual Platform
dmi.board.vendor: Parallels ARM Virtual Machine
dmi.board.version: 0.1
dmi.chassis.type: 2
dmi.chassis.vendor: Parallels International GmbH.
dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr20.2.0(55872):bdMon,23Dec2024155453:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM:
dmi.product.family: Parallels VM
dmi.product.name: Parallels ARM Virtual Machine
dmi.product.sku: Parallels_ARM_VM
dmi.product.version: 0.1
dmi.sys.vendor: Parallels International GmbH.

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

[Bug 1516025] Re: Realtek ALC3661 Alienware14 / Soundoutput / Jack

I can confirm similar behavior on Ubuntu 22.04/24.04 with Realtek
ALC887-VD.

Hardware:
- Realtek ALC887-VD (Azalia)
- Drivers: snd_hda_intel
- HDMI device: AMD Trinity HDMI Audio
- Analog device: AMD FCH Azalia

PipeWire logs show:
mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown

WirePlumber logs show:
Error opening low-level control device 'hw:0': No such file or directory
can't open control for card hw:0
Card can't get card_name from card_index 1

PipeWire version: 1.0.5
Kernel: 6.14.0-37-generic
ALSA API: kernel-api

This issue is reproducible on every boot.

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1516025

Title:
Realtek ALC3661 Alienware14 / Soundoutput / Jack

Status in ALSA driver:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
When watching the following video (but also audio from other programs) with the volume at 100%, the audio loudness is lower in comparison to the same audio being played at 100% in Windows 10:
https://www.youtube.com/watch?v=YQHsXMglC9A

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-18-generic 4.2.0-18.22
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: imran 1619 F.... pulseaudio
 /dev/snd/controlC1: imran 1619 F.... pulseaudio
CurrentDesktop: Unity
Date: Fri Nov 13 18:08:07 2015
HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1
InstallationDate: Installed on 2015-11-07 (5 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Alienware Alienware 14
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-18-generic N/A
 linux-backports-modules-4.2.0-18-generic N/A
 linux-firmware 1.149.1
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/23/2014
dmi.bios.vendor: Alienware
dmi.bios.version: A09
dmi.board.name: 07MJ2Y
dmi.board.vendor: Alienware
dmi.board.version: A01
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A09
dmi.modalias: dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09:
dmi.product.name: Alienware 14
dmi.product.version: A09
dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1516025/+subscriptions

[Bug 2138961] Re: USB-C Monitor not detected on boot (DWC3 soft reset timeout) on X1E80100/Snapdragon X Elite

** Attachment added: "Build information."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2138961/+attachment/5940525/+files/launchpad-2138961-uname-info.tar.gz

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2138961

Title:
USB-C Monitor not detected on boot (DWC3 soft reset timeout) on
X1E80100/Snapdragon X Elite

Status in linux package in Ubuntu:
New

Bug description:
On the Lenovo Yoga Slim 7x (Snapdragon X Elite / X1E80100), if a
monitor is connected during boot, the display is often not detected or
powered up. The monitor remains black/no-signal until the cable is
physically disconnected and reconnected.

The following error appears in dmesg during the failed boot attempt:

dwc3 a000000.usb: error -ETIMEDOUT: failed to initialize core
dwc3 a000000.usb: DWC3 controller soft reset failed

Analysis: This appears to be a timing issue where the DWC3 controller
attempts to reset the core immediately after the PHY initialization,
but the PHY pipe clock has not yet stabilized. The soft reset then
times out waiting for clock synchronization.

Fix: Adding a 2ms delay in drivers/phy/qualcomm/phy-qcom-qmp-combo.c
inside qmp_combo_usb_init() (after the PHY power-on sequence) resolves
the issue reliably. This ensures the PHY clock is stable before the
DWC3 core driver takes over.

Patch: Add stabilization delay for USB pipe clock

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

[Bug 2138756] Re: [ov02c10] Camera unusable on Lenovo Yoga Slim 7x - system hangs, I2C timeouts, color artifacts

I have submitted two patch series to the upstream Linux kernel to fix
the OV02C10 camera issues on Lenovo Yoga Slim 7x (Snapdragon X Elite):

- Series 1: Camera Stability and Power Cycling Fixes (Submitted Jan 24,
2026)

Status: Under review on linux-media@vger.kernel.org

Patches:
1. [media: qcom: camss: Fix pipeline lock leak in stop_streaming](https://lore.kernel.org/linux-media/20260124071751.5885-2-bjsaikiran@gmail.com/)
- Fixes camera becoming permanently locked after browser/app closes
- Prevents "Pipeline handler in use by another process" errors

2. [media: i2c: ov02c10: Check for errors in disable_streams](https://lore.kernel.org/linux-media/20260124071751.5885-3-bjsaikiran@gmail.com/)
- Adds proper error logging when camera fails to stop
- Aids in debugging power management issues

3. [media: i2c: ov02c10: Enforce cool-down period to prevent brownout](https://lore.kernel.org/linux-media/20260124071751.5885-4-bjsaikiran@gmail.com/)
- Fixes brownout/latch-up during rapid power cycling
- Prevents system crashes requiring reboot
- Enforces 2-second minimum gap between power cycles

Cover letter: https://lore.kernel.org/linux-
media/20260124071751.5885-1-bjsaikiran@gmail.com/

Series 2: Camera Color and Basic Stability Fixes (Submitting shortly)

Status: Prepared, will be submitted to linux-media@vger.kernel.org

Patches:
1. [media: i2c: ov02c10: Fix incorrect Bayer pattern to SGRBG10] (https://lore.kernel.org/linux-media/20260124074402.7165-2-bjsaikiran@gmail.com/T/#u)
- Fixes severe green color tint in all captured images
- Changes from incorrect SBGGR10 to correct SGRBG10 pattern
- Tested all 4 Bayer patterns - only SGRBG10 produces natural colors

2. [media: i2c: ov02c10: Fix race condition in remove and relax reset timings] (https://lore.kernel.org/linux-media/20260124074402.7165-3-bjsaikiran@gmail.com/T/#u)
- Fixes kernel oops ("Execute from non-executable memory") during camera removal
- Fixes "master 1 queue 0 timeout" CCI I2C errors during initialization
- Reorders cleanup sequence to prevent Use-After-Free

Cover letter: https://lore.kernel.org/linux-media/20260124074402.7165-1-bjsaikiran@gmail.com/T/#t

Prerequisites:
Full camera enablement also requires device tree patches by Aleksandrs Vinarskis:
- Fix RGB camera regulator supplies (avdd/dvdd/dovdd)
- Enable camera privacy indicator LED

Submission Status - Unknown

Testing:

All patches have been tested together on:
- Linux kernel 6.19-rc5
- Lenovo Yoga Slim 7x (Snapdragon X Elite x1e80100)

Results:
With all patches applied:
- Camera produces natural colors (no green tint)
- No crashes on camera close/removal
- Survives rapid open/close cycles
- No system lockups requiring reboot
- Stable operation with all tested applications

** Attachment added: "Patch series fixing camera brownout issue upon rapidly turning the camera on and off"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2138756/+attachment/5940524/+files/Camera_brownout_fixes.zip

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2138756

Title:
[ov02c10] Camera unusable on Lenovo Yoga Slim 7x - system hangs, I2C
timeouts, color artifacts

Status in linux package in Ubuntu:
New

Bug description:
Impact:
The OV02C10 camera sensor on Lenovo Yoga Slim 7x is completely unusable due to system hangs, I2C timeouts, and severe color corruption.

Affected Hardware:
- Device: Lenovo Yoga Slim 7x (Snapdragon X Elite / x1e80100)
- Camera sensor: OmniVision OV02C10 (RGB, 2MP)
- Platform: Qualcomm Camera Control Interface (CCI)

Ubuntu Version:
Ubuntu 25.10

Symptoms:
1. System Hangs/Crashes (Critical):
- System hangs or kernel oops during camera initialization or usage
- "master 1 queue 0 timeout" errors from CCI/I2C
- Hangs persist across camera app launches (Cheese, qcam, PipeWire)

2. Initialization Failures:
- Camera fails to probe or initialize
- Regulator supply errors in dmesg

3. Color Artifacts:
- Severe green/incorrect color tint in all images
- Cannot be corrected by white balance adjustments
- Raw Bayer pattern mismatch

Root Causes:

Issue 1 - System Hang (Critical):
Race condition in ov02c10_remove() where resources are freed before sensor power-off, causing use-after-free errors when Runtime PM or PipeWire/WirePlumber interact with the device. Additionally, internal sensor reset timings are too aggressive for reliable hardware initialization.

Issue 2 - Color Pattern:
Driver reports incorrect Bayer pattern (SBGGR10 or SGBRG10), but the physical sensor layout on this device is SGRBG10, causing color channel misalignment.

Issue 3 - DTS Configuration:
Missing regulator supplies for RGB sensor and camera privacy LED not configured.

Fix:
A patch series of 4 commits addresses all issues:

1. DTS: Fix regulator supplies for RGB sensor
- Adds missing vdda/vddd supplies
- Fixes camera initialization failures

2. DTS: Enable Camera Privacy LED
- Configures GPIO 110 for privacy indicator

3. Driver: Update Bayer pattern to SGRBG10
- Changes MEDIA_BUS_FMT_SBGGR10_1X10 → MEDIA_BUS_FMT_SGRBG10_1X10
- Fixes severe green color cast

4. Driver: Fix race condition and relax reset timings
- Reorders cleanup in ov02c10_remove(): disable Runtime PM *before* freeing resources
- Increases reset timing: 5ms assert, 20ms post-delay (was 1ms/2ms)
- Fixes system hangs and "master 1 queue 0 timeout" errors

Testing Results:
- Camera stable across repeated sessions (no hangs/crashes)
- Proper initialization on every boot
- Sharp images with correct orientation
- Color accuracy significantly improved (green tint eliminated)
- Userspace color tuning still needed for perfect white balance (libcamera YAML)

Configuration Requirements:

Kernel config:
CONFIG_VIDEO_OV02C10=m

Userspace packages:
libcamera-tools libcamera-ipa gstreamer1.0-libcamera

Pipeline: libcamera 'simple' pipeline with SoftISP (Software Image
Signal Processor)

Reference:
Camera stack setup for X1E: https://github.com/alexVinarskis/linux-x1e80100-zenbook-a14#camera-configuration

Complete Technical Details:
Full description, patches, and optional YAML tuning file available at:
https://bugs.launchpad.net/ubuntu-concept/+bug/2138706

Patches attached as lenovo-yoga-slim7x-camera-fixes.zip

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

[Bug 2138756] Re: [ov02c10] Camera unusable on Lenovo Yoga Slim 7x - system hangs, I2C timeouts, color artifacts

** Tags added: patch

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2138756

Title:
[ov02c10] Camera unusable on Lenovo Yoga Slim 7x - system hangs, I2C
timeouts, color artifacts

Status in linux package in Ubuntu:
New

Bug description:
Impact:
The OV02C10 camera sensor on Lenovo Yoga Slim 7x is completely unusable due to system hangs, I2C timeouts, and severe color corruption.

Affected Hardware:
- Device: Lenovo Yoga Slim 7x (Snapdragon X Elite / x1e80100)
- Camera sensor: OmniVision OV02C10 (RGB, 2MP)
- Platform: Qualcomm Camera Control Interface (CCI)

Ubuntu Version:
Ubuntu 25.10

Symptoms:
1. System Hangs/Crashes (Critical):
- System hangs or kernel oops during camera initialization or usage
- "master 1 queue 0 timeout" errors from CCI/I2C
- Hangs persist across camera app launches (Cheese, qcam, PipeWire)

2. Initialization Failures:
- Camera fails to probe or initialize
- Regulator supply errors in dmesg

3. Color Artifacts:
- Severe green/incorrect color tint in all images
- Cannot be corrected by white balance adjustments
- Raw Bayer pattern mismatch

Root Causes:

Issue 1 - System Hang (Critical):
Race condition in ov02c10_remove() where resources are freed before sensor power-off, causing use-after-free errors when Runtime PM or PipeWire/WirePlumber interact with the device. Additionally, internal sensor reset timings are too aggressive for reliable hardware initialization.

Issue 2 - Color Pattern:
Driver reports incorrect Bayer pattern (SBGGR10 or SGBRG10), but the physical sensor layout on this device is SGRBG10, causing color channel misalignment.

Issue 3 - DTS Configuration:
Missing regulator supplies for RGB sensor and camera privacy LED not configured.

Fix:
A patch series of 4 commits addresses all issues:

1. DTS: Fix regulator supplies for RGB sensor
- Adds missing vdda/vddd supplies
- Fixes camera initialization failures

2. DTS: Enable Camera Privacy LED
- Configures GPIO 110 for privacy indicator

3. Driver: Update Bayer pattern to SGRBG10
- Changes MEDIA_BUS_FMT_SBGGR10_1X10 → MEDIA_BUS_FMT_SGRBG10_1X10
- Fixes severe green color cast

4. Driver: Fix race condition and relax reset timings
- Reorders cleanup in ov02c10_remove(): disable Runtime PM *before* freeing resources
- Increases reset timing: 5ms assert, 20ms post-delay (was 1ms/2ms)
- Fixes system hangs and "master 1 queue 0 timeout" errors

Testing Results:
- Camera stable across repeated sessions (no hangs/crashes)
- Proper initialization on every boot
- Sharp images with correct orientation
- Color accuracy significantly improved (green tint eliminated)
- Userspace color tuning still needed for perfect white balance (libcamera YAML)

Configuration Requirements:

Kernel config:
CONFIG_VIDEO_OV02C10=m

Userspace packages:
libcamera-tools libcamera-ipa gstreamer1.0-libcamera

Pipeline: libcamera 'simple' pipeline with SoftISP (Software Image
Signal Processor)

Reference:
Camera stack setup for X1E: https://github.com/alexVinarskis/linux-x1e80100-zenbook-a14#camera-configuration

Complete Technical Details:
Full description, patches, and optional YAML tuning file available at:
https://bugs.launchpad.net/ubuntu-concept/+bug/2138706

Patches attached as lenovo-yoga-slim7x-camera-fixes.zip

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