Lines Matching full:message

47 	r             if present, prepend kernel version (release) to the message
136 	release		Prepend kernel release to message	(read-write)
202  echo "This is a message" > /dev/kmsg
206  12,607,22085407756,-;This is a message
226  echo "This is a message" > /dev/kmsg
227  12,607,22085407756,-;This is a message
254 sneding the message.
263 currently scheduled when that message was generated, providing extra context
268   echo "This is a message" > /dev/kmsg
269   12,607,22085407756,-;This is a message
272 In this example, the message was generated while "echo" was the current
281 to userdata dictionary in every message sent.
289   echo "This is a message" > /dev/kmsg
290   12,607,22085407756,-;This is a message
297    dictionary rather than being included in the message header.
306 populates the CPU number that is sending the message.
320   echo "This is a message" > /dev/kmsg
321   12,607,22085407756,-;This is a message
324 In this example, the message was sent by CPU 42.
338      12,607,22085407756,-;This is a message
343 Message ID auto population in userdata
347 located in the `userdata` directory. This file controls the message ID
348 auto-population feature, which assigns a numeric id to each message sent to a
349 given target and appends the ID to userdata dictionary in every message sent.
351 The message ID is generated using a per-target 32 bit counter that is
352 incremented for every message sent to the target. Note that this counter will
353 eventually wrap around after reaching uint32_t max value, so the message ID is
358 It is important to distinguish message IDs from the message <sequnum> field.
361 indicate that a message was dropped during transmission, as it may never have
362 been sent via netconsole. The message ID, on the other hand, is only assigned
367   echo "This is message #1" > /dev/kmsg
368   echo "This is message #2" > /dev/kmsg
369   13,434,54928466,-;This is message #1
371   13,435,54934019,-;This is message #2
387  <level>,<sequnum>,<timestamp>,<contflag>;<message text>
390 prepended to the start of the message. Example::
394 Non printable characters in <message text> are escaped using "\xff"
395 notation. If the message contains optional dictionary, verbatim
398 If a message doesn't fit in certain number of bytes (currently 1000),
399 the message is split into multiple fragments by netconsole. These
404 For example, assuming a lot smaller chunk size, a message "the first