Informative dmesg logging?

Steve Kargl sgk at troutmask.apl.washington.edu
Sat Sep 26 19:34:07 UTC 2020


Just updated to head including replacing drm-legacy-kmod
with drm-current-kmod.  During boot, I see these mesages:

% dmesg | grep "local kernel"
__pm_runtime_resume not implemented -- see your local kernel hacker
pm_runtime_mark_last_busy not implemented -- see your local kernel hacker
__pm_runtime_suspend not implemented -- see your local kernel hacker
pm_runtime_get_if_in_use not implemented -- see your local kernel hacker
__pm_runtime_resume not implemented -- see your local kernel hacker
kmem_cache_shrink not implemented -- see your local kernel hacker
register_oom_notifier not implemented -- see your local kernel hacker
kmem_cache_shrink not implemented -- see your local kernel hacker
kmem_cache_shrink not implemented -- see your local kernel hacker
kmem_cache_shrink not implemented -- see your local kernel hacker
kmem_cache_shrink not implemented -- see your local kernel hacker
kmem_cache_shrink not implemented -- see your local kernel hacker
kmem_cache_shrink not implemented -- see your local kernel hacker
register_acpi_notifier not implemented -- see your local kernel hacker
async_schedule is dodgy -- see your local kernel hacker
pm_runtime_set_autosuspend_delay not implemented -- see your local kernel hacker
__pm_runtime_use_autosuspend not implemented -- see your local kernel hacker
async_synchronize_cookie not implemented -- see your local kernel hacker
check_move_unevictable_pages not implemented -- see your local kernel hacker

Other than filling dmesg output, is anyone interested in this info?

-- 
Steve


More information about the freebsd-hackers mailing list