wdt_notify_sys(9)
π wdt_notify_sys(9) β from the Kernel API Manual, bestie β¨
okay so you're looking at a kernel API manual page, bestie, and it's for wdt_notify_sys β it lives in the Kernel API Manual and the whole page is right here, served fresh π
β¨ NAME β¨
wdt_notify_sys -
fr fr the original page just leaves the description after the dash completely blank π so that's what we're working with. No cap, nothing to add β moving on π
πΈ SYNOPSIS πΈ
int wdt_notify_sys (struct notifier_block *this , unsigned long code ,
void *unused );
the way it's int, and the way it takes three things β that's the whole vibe check π¦
π ARGUMENTS π
thisβ our notifier block, it's literally us, main character energy πcodeβ the event being reported, i.e. what is going downunusedβ unused. that's it. that's the description. iconic honestly π
π DESCRIPTION π
so our notifier gets called on system shutdowns β that's its moment β¨
and the goal? we want to turn the card off at reboot. why, you ask? because otherwise the machine will reboot again during memory test, or β worse yet β during the following fsck π
this would suck. in fact, trust me β if it happens, it does suck. no notes, just facts π₯
lowkey a cautionary tale: if the card isn't powered down at reboot, you get a double reboot and then fsck joins the party π not the vibe
π¦ SEE ALSO π¦
kernel file ./drivers/watchdog/wdt.c β and the whole friend group is here, bestie:
wdt_start(9)wdt_stop(9)wdt_ping(9)wdt_set_heartbeat(9)wdt_get_status(9)wdt_get_temperature(9)wdt_interrupt(9)wdt_write(9)wdt_ioctl(9)wdt_open(9)wdt_release(9)wdt_temp_read(9)wdt_temp_open(9)wdt_temp_release(9)wdt_exit(9)wdt_init(9)
that's the page!! the source is ./drivers/watchdog, dated October 2026, and of course it's wdt_notify_sys(9) β periodt ππ«Ά go read it and slay β¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms