On Tue, Jun 03, 2025 at 03:04:33PM +0200, Rafael J. Wysocki wrote:
> On Tue, Jun 3, 2025 at 2:27 PM Chris Bainbridge
> wrote:
> >
> > On Tue, 3 Jun 2025 at 13:24, Rafael J. Wysocki wrote:
> > > >
> > > > This patch does fix the list corruption, but
On Tue, 3 Jun 2025 at 13:24, Rafael J. Wysocki wrote:
> >
> > This patch does fix the list corruption, but the "Unbalanced
> > pm_runtime_enable" still occurs:
>
> Have you applied it together with the previous patch?
Yes
On Tue, Jun 03, 2025 at 11:38:37AM +0200, Rafael J. Wysocki wrote:
>
> Chris, please check if the attached patch helps. I'm going to post it
> as a fix anyway later today, but it would be good to verify that it is
> sufficient.
This did not fix my test case, pstore crash log was:
<6>[ 100.6902
On Fri, Mar 14, 2025 at 02:13:53PM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> In analogy with the previous change affecting the resume path,
> make device_suspend() start the async suspend of the device's parent
> after the device itself has been processed and make dpm_suspend(
On Sun, Jun 01, 2025 at 08:44:29PM -0500, Mario Limonciello wrote:
> From: Mario Limonciello
>
> Chris Bainbridge reported some list corruption occurring around the
> suspend sequence when an aborted suspend occurs.
>
> I couldn't reproduce this specific problem, but when
There is a reference couting / lifecycle issue with drm_connector when used
with a USB-C dock. The problem has been previously reproduced on both Intel and
AMD GPUs.
On both Intel and AMD, the symptoms are:
- multiple connectors being listed in sysfs `sys/class/drm/cardX/` (because
the old
Hardware is HP Pavilion Aero 13 laptop with Dell WD19 dock and three
external monitors. I get a warning with recent kernel builds when
enabling the external monitors with xrandr after initial boot:
16:57:49 kernel: WARNING: CPU: 4 PID: 1347 at
drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn
EDID.
Signed-off-by: Chris Bainbridge
Fixes: c6a837088bed ("drm/amd/display: Fetch the EDID from _DDC if available
for eDP")
---
Changes in v2:
- check kmemdup() return value
- move buffer management into acpi_video_device_EDID()
- return actual length val
#regzbot introduced: c6a837088bed ^
acpi_video_get_edid.
Signed-off-by: Chris Bainbridge
Fixes: c6a837088bed ("drm/amd/display: Fetch the EDID from _DDC if available
for eDP")
---
drivers/acpi/acpi_video.c | 3 ++-
drivers/gpu/drm/nouveau/nouveau_acpi.c | 2 +-
2 files changed, 3 insertions(+), 2 deletions
On Thu, Dec 26, 2024 at 12:19:02AM +0100, Tobias Jakobi wrote:
> Hi Chris!
>
> On 12/26/24 00:09, Chris Bainbridge wrote:
>
> > Commit c6a837088bed ("drm/amd/display: Fetch the EDID from _DDC if
> > available for eDP") added function dm_helpers_probe_acpi_edi
On Tue, Jun 04, 2024 at 10:02:29AM +0800, kernel test robot wrote:
> Hi Mario,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on drm-misc/drm-misc-next]
> [also build test ERROR on drm/drm-next drm-exynos/exynos-drm-next
> drm-intel/for-linux-next drm-intel/
I
> lid status and if it's closed disable any eDP connectors.
>
> Suggested-by: Alex Deucher
> Reported-by: Chris Bainbridge
> Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3349
> Signed-off-by: Mario Limonciello
> ---
> drivers/gpu/drm/drm_client_modeset.c
On Tue, May 21, 2024 at 02:39:06PM +0500, Mikhail Gavrilov wrote:
> Hi,
> Yesterday on the fresh kernel snapshot
> I spotted a new bug message with follow stacktrace:
> [4.307097] BUG: sleeping function called from invalid context at
> kernel/locking/mutex.c:585
> [4.307135] in_atomic(): 1,
14 matches
Mail list logo
