drm_dev_wedged_event(9)

okay so bestie, welcome to drm_dev_wedged_event(9) from the Kernel API Manual 💖 this is literally the page where a DRM device gets its “wedged” uevent moment, and we’re gonna walk through it together, no cap ✨

🎀 NAME 🎀

drm_dev_wedged_event - generate a device wedged uevent

✨ SYNOPSIS ✨

int drm_dev_wedged_event (struct drm_device *dev , unsigned long method
, struct drm_wedge_task_info *info );

🦋 ARGUMENTS 🦋

• dev — the DRM device, aka the main character here 👑
• method — the method(s) to be used for recovery, so like the recovery vibe check 💅
• info — optional information about the guilty task 🕵️‍♀️

🔥 DESCRIPTION 🔥

So this function generates a device wedged uevent for the DRM device specified by dev — yes, it’s giving “something went sideways” energy 😭

The recovery method of choice gets sent in the uevent environment as WEDGED=<method1>[,..,<methodN>], and the order is from less to more side-effects, bestie 💅

If the caller is unsure about recovery or the method is unknown (0), then WEDGED=unknown will be sent instead. No guessing 🫶

For more details, refer to the "Device Wedging" chapter in Documentation/gpu/drm-uapi.rst. It’s literally right there, iykyk 📖✨

🌸 RETURN 🌸

0 on success, negative error code otherwise. Slay when it works, sad little negative number when it doesn’t 😭

💜 SEE ALSO 💜

• Kernel file ./drivers/gpu/drm/drm_drv.c driver instance overview(9)
• drm_put_dev(9)
• drm_dev_enter(9)
• drm_dev_exit(9)
• drm_dev_unplug(9)
• drm_dev_set_dma_dev(9)
• component helper usage recommendations(9)
• __drm_dev_alloc(9)
• drm_dev_alloc(9)
• drm_dev_get(9)
• drm_dev_put(9)
• drmm_cgroup_register_region(9)
• drm_dev_register(9)
• drm_dev_unregister(9)

okay that’s the whole vibe 🎀 this page’s source/version corner says ./drivers/gpu/drm, dated October 2026, and the title is drm_dev_wedged_event(9) — periodt 💅💖