KernelNewbies
  • Comments
  • Immutable Page
  • Menu
    • Navigation
    • RecentChanges
    • FindPage
    • Local Site Map
    • Help
    • HelpContents
    • HelpOnMoinWikiSyntax
    • Display
    • Attachments
    • Info
    • Raw Text
    • Print View
    • Edit
    • Load
    • Save
  • Login

Kernel Hacking

  • Frontpage

  • Kernel Hacking

  • Kernel Documentation

  • Kernel Glossary

  • FAQ

  • Found a bug?

  • Kernel Changelog

  • Upstream Merge Guide

Projects

  • KernelJanitors

  • KernelMentors

  • KernelProjects

Community

  • Why a community?

  • Regional Kernelnewbies

  • Personal Pages

  • Upcoming Events

References

  • Mailing Lists

  • Related Sites

  • Programming Links

Wiki

  • Recent Changes

  • Site Editors

  • Side Bar

  • Tips for Editors

  • Hosted by WikiWall

Navigation

  • RecentChanges
  • FindPage
  • HelpContents
Revision 1 as of 2006-08-04 21:39:06
KernelNewbies:
  • FAQ
  • LinuxKernelDebug101

Describe FAQ/LinuxKernelDebug101 here.

  • easiest way is, as always, printk("format", ...) almost as easy is dev_info() and friends:
    • dev_info, dev_warn, dev_err, dev_dbg they do logging at the KERN_* levels (INFO, WARN, ERROR, DEBUG) respectively convenient shorthand, more readable.
    dev_dbg has additional features.
    • compiles out, unless #define DEBUG 1 is done before #include <device.h>

      • so to activate, recompile, reload
      to see them on console, lower console logging level
      • echo 8 > /proc/sys/kernel/printk

  • MoinMoin Powered
  • Python Powered
  • GPL licensed
  • Valid HTML 4.01