Re: [PATCH 3/5] fbdev: Introduce devm_register_framebuffer()

2024-08-30 Thread Bert Karwatzki
*dev, struct fb_info *fb_info) > { > int ret; > > ret = register_framebuffer(fb_info); > if (ret) > return ret; > > return devm_add_action_or_reset(dev, devm_unregister_framebuffer, > fb_info); > } > EXPORT_SYMBOL(devm_register_framebuffer); > > Bert, could you test this? > Helge, do you want me to resend the series, minus the original patch 1? Yes, this works for me. Thanks! Bert Karwatzki

commit f3123c2590005 causes deadlocks

2023-11-21 Thread Bert Karwatzki
there might be in the entity->dependency branch of drm_sched_entity_is_ready (some kind of circular dependencies ...). Bert Karwatzki

drm scheduler redesign causes deadlocks [extended repost]

2023-11-21 Thread Bert Karwatzki
full_recovery); void drm_sched_resubmit_jobs(struct drm_gpu_scheduler *sched); This brings the extra check to the old scheduler and has so far not caused any trouble (using the same stress test described above), so chances are that the error is somewhere else in redesigned scheduler. Bert Karwatzki

Re: drm scheduler redesign causes deadlocks [extended repost]

2023-11-21 Thread Bert Karwatzki
Am Dienstag, dem 21.11.2023 um 11:22 +0200 schrieb Jani Nikula: > On Tue, 21 Nov 2023, Bert Karwatzki wrote: > > As this simple patch fixes the problem > > Please use git send-email to send patches. Evolution botched up the > whitespace here. > > BR, > Jani. > &g

Re: drm scheduler redesign causes deadlocks [extended repost]

2023-11-24 Thread Bert Karwatzki
Am Mittwoch, dem 22.11.2023 um 18:02 -0500 schrieb Luben Tuikov: > On 2023-11-21 04:00, Bert Karwatzki wrote: > > Since linux-next-20231115 my linux system (debian sid on msi alpha 15 > > laptop) > > suffers from random deadlocks which can occur after  30 - 180min of usage. &g

[PATCH] Revert "drm/sched: Qualify drm_sched_wakeup() by drm_sched_entity_is_ready()"

2023-11-27 Thread Bert Karwatzki
Commit f3123c25 (in combination with the use of work queues by the gpu scheduler) leads to random lock ups of the GUI [1,2]. This is not a complete revert of commit f3123c25 as drm_sched_wakeup still needs its entity argument to pass it to drm_sched_can_queue. [1] https://gitlab.freedesktop.org/d

[PATCH] Revert "drm/sched: Qualify drm_sched_wakeup() by drm_sched_entity_is_ready()"

2023-11-27 Thread Bert Karwatzki
Commit f3123c25 (in combination with the use of work queues by the gpu scheduler) leads to random lock ups of the GUI [1,2]. This is not a complete revert of commit f3123c25 as drm_sched_wakeup still needs its entity argument to pass it to drm_sched_can_queue. [1] https://gitlab.freedesktop.org/d

[PATCH] drm/sched: Partial revert of "Qualify drm_sched_wakeup() by drm_sched_entity_is_ready()"

2023-11-27 Thread Bert Karwatzki
://gitlab.freedesktop.org/drm/amd/-/issues/2994 Link: https://lists.freedesktop.org/archives/dri-devel/2023-November/431606.html Fixes: f3123c2590005c ("drm/sched: Qualify drm_sched_wakeup() by drm_sched_entity_is_ready()") Signed-off-by: Bert Karwatzki --- drivers/gpu/drm/scheduler/sched_

Re: Warnings in next-20250703 caused by commit 582111e630f5

2025-07-03 Thread Bert Karwatzki
pu: Provide custom framebuffer destroy function 8d6c58332c7a (tag: next-20250703, origin/master, origin/HEAD, master) Add linux-next specific files for 20250703 and it solves the issue for me (i.e. no warnings). Bert Karwatzki

Warnings in next-20250703 caused by commit 582111e630f5

2025-07-03 Thread Bert Karwatzki
o Coprocessor (rev 01) 08:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h/1ah HD Audio Controller 08:00.7 Signal processing controller: Advanced Micro Devices, Inc. [AMD] Sensor Fusion Hub Bert Karwatzki

Re: Warnings in next-20250703 caused by commit 582111e630f5

2025-07-04 Thread Bert Karwatzki
Am Freitag, dem 04.07.2025 um 09:51 +0200 schrieb Thomas Zimmermann: > Hi > > Am 03.07.25 um 19:23 schrieb Bert Karwatzki: > > Am Donnerstag, dem 03.07.2025 um 18:09 +0200 schrieb Thomas Zimmermann: > > > Hi, > > > > > > before I give up on the issue