| dmesg | |
| dmesg | |
| Screenshot Alt: | dmesg output piped through grep |
| Engines: | --> |
| Operating System: | Unix-like |
| Platform: | Cross-platform |
| Genre: | Command |
| Licence: | --> |
dmesg (diagnostic messages[1]) is a command on most Unix-like operating systems that prints the message buffer of the kernel.[2] [3] The output includes messages produced by the device drivers.
When initially booted, a computer system loads its kernel into memory. At this stage device drivers present in the kernel are set up to drive relevant hardware. Such drivers, as well as other elements within the kernel, may produce output ("messages") reporting both the presence of modules and the values of any parameters adopted. (It may be possible to specify boot parameters which control the level of detail in the messages.) The booting process typically happens at a speed where individual messages scroll off the top of the screen before an operator can read/digest them. The command allows the review of such messages in a controlled manner after the system has started.[4]
Even after the system has fully booted, the kernel may occasionally produce further diagnostic messages. Common examples of when this might happen are when I/O devices encounter errors, or USB devices are hot-plugged. dmesg provides a mechanism to review these messages at a later time. When first produced, they will be directed to the system console. If the console is in use, these messages may be confused with or quickly overwritten by the output of user programs.[5]
The output of dmesg can amount to many complete screens. For this reason, this output is normally reviewed using standard text-manipulation tools such as more, tail, less or grep.[6] Size of the dmesg buffer is limited and the output is often captured in a permanent system logfile via a logging daemon, such as syslog.
Traditionally, dmesg lines begin with a device name followed by a colon, followed with detailed text. Often these come in clusters, with the same device showing up on multiple lines in succession. Each cluster is usually associated with a single device enumeration, by one particular device driver (or device facility) associated with the device name.
Each driver or facility emits diagnostic information in its own chosen format. Device drivers may specify the format in the manual page by convention called identically to the device file name without the trailing number.