It is sadly quite easy to miss something when when configuring dynamic debug on a specific line/file/module, leading to no log being output and making one's urge to go back to raw printk.
Add a small checklist to prevent developers from sanity damage:
are logs output but only in kernel buffer (=> add ignore_loglevel to print them to console)
is debug really activated ? => grep entries in /dynamic_debug/control, ensure about state, =p is enabled, _p is not
if not properly activated, how activation is supposed to be done ?
if done with manual command in userspace, ensure about access rights on debugs and command return code
if done through kernel commandline (dyndbg) , ensure about how your kernel configuration or bootloader passes parameters (may need some quote escapes).
check your bootlogs: if dynamic debug is not properly enabled, kernel will pass parameters to userspace instead of processing them
It is sadly quite easy to miss something when when configuring dynamic debug on a specific line/file/module, leading to no log being output and making one's urge to go back to raw printk. Add a small checklist to prevent developers from sanity damage: