| /linux-4.4.14/arch/m68k/tools/amiga/ |
| D | Makefile | 6 All: dmesg
9 dmesg: dmesg.c target
10 $(CC) $(CFLAGS) -o dmesg dmesg.c -noixemul
|
| /linux-4.4.14/scripts/ |
| D | analyze_suspend.py | 215 dmesg = {} # root data structure variable in Data
237 self.dmesg = { # fixed list of 10 phases
261 return self.dmesg[self.phases[0]]['start']
264 self.dmesg[self.phases[0]]['start'] = time
266 return self.dmesg[self.phases[-1]]['end']
269 self.dmesg[self.phases[-1]]['end'] = time
272 list = self.dmesg[phase]['list']
293 list = self.dmesg[phase]['list']
307 list = self.dmesg[phase]['list']
342 p = self.dmesg[phase]
[all …]
|
| /linux-4.4.14/tools/nfsd/ |
| D | inject_fault.sh | 44 dmesg > $BEFORE
46 dmesg > $AFTER
|
| /linux-4.4.14/tools/testing/selftests/pstore/ |
| D | pstore_post_reboot_tests | 38 check_files_exist dmesg
50 files=`ls dmesg-${backend}-*`
|
| D | pstore_tests | 13 dmesg | grep -q "console \[pstore"
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | pstore | 18 -r--r--r-- 1 root root 7896 Nov 30 15:38 dmesg-erst-1
23 "dmesg" - saved console log
30 $ rm /sys/fs/pstore/dmesg-erst-1
|
| D | dev-kmsg | 110 Users: dmesg(1), userspace kernel log consumers
|
| D | sysfs-power | 112 dmesg -s 1000000 | grep 'hash matches'
|
| /linux-4.4.14/Documentation/zh_CN/ |
| D | oops-tracing.txt | 25 注意： ksymoops 在2.6中是没有用的。 请以原有格式使用Oops(来自dmesg，等等)。
44 能够运行dmesg > file来从内核缓冲区中读取数据并保存下来。 否则你可以
57 使用在Documentation/kdump/gdbmacros.txt中定义的dmesg gdb宏，从旧的内存中提取内核
|
| /linux-4.4.14/scripts/gdb/ |
| D | vmlinux-gdb.py | 28 import linux.dmesg
|
| /linux-4.4.14/kernel/debug/kdb/ |
| D | kdb_cmds | 16 -dmesg 600
|
| /linux-4.4.14/drivers/misc/cb710/ |
| D | Kconfig | 20 say N here. This adds a lot of debugging output to dmesg.
|
| /linux-4.4.14/Documentation/trace/ |
| D | mmiotrace.txt | 77 $ dmesg
91 $ dmesg > dmesg.txt
92 $ tar zcf pciid-nick-mmiotrace.tar.gz mydump.txt lspci.txt dmesg.txt
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | dmatest.txt | 79 % dmesg | tail -n 1
88 % dmesg | tail -n 1
|
| /linux-4.4.14/Documentation/block/ |
| D | cmdline-partition.txt | 37 dmesg:
|
| /linux-4.4.14/Documentation/networking/ |
| D | e100.txt | 114 console, you must set the dmesg level up to six. This can be done by
117 dmesg -n 8
120 messages, set the dmesg level to eight.
|
| D | batman-adv.txt | 134 mands: dmesg, logread, or looking in the files /var/log/kern.log
138 # dmesg | grep batman-adv
|
| D | netconsole.txt | 198 dmesg -n 8
203 dmesg(8) man page and Documentation/kernel-parameters.txt for details.
|
| D | i40e.txt | 85 message to the system log (displayed by the "dmesg" command):
|
| D | igb.txt | 102 message to the system log (displayed by the "dmesg" command):
|
| D | s2io.txt | 25 # dmesg | tail -40
|
| D | netdev-features.txt | 92 Errors returned are not (and cannot be) propagated anywhere except dmesg.
|
| D | ixgb.txt | 289 your console, set dmesg to eight by entering the following:
291 dmesg -n 8
|
| D | ixgbe.txt | 294 message to the system log (displayed by the "dmesg" command):
|
| D | filter.txt | 477 Example output from dmesg:
1280 including timings in nsec can be found in the kernel log (dmesg).
|
| /linux-4.4.14/Documentation/pcmcia/ |
| D | devicetable.txt | 19 If the hash is incorrect, the kernel will inform you about this in "dmesg"
|
| /linux-4.4.14/drivers/scsi/osd/ |
| D | Kconfig | 47 dmesg. Enable this if you found a bug and you want to help us
|
| /linux-4.4.14/Documentation/kdump/ |
| D | gdbmacros.txt | 182 define dmesg
199 document dmesg
|
| /linux-4.4.14/Documentation/ |
| D | gdb-kernel-debugging.txt | 95 (gdb) lx-dmesg
155 lx-dmesg -- Print Linux kernel log buffer
|
| D | oops-tracing.txt | 2 (from dmesg, etc). Ignore any references in this or other docs to "decoding
25 in which case you can run dmesg > file to read the data from the kernel
45 extract the kernel ring buffer from old memory with using dmesg
|
| D | ramoops.txt | 104 files is "dmesg-ramoops-N", where N is the record number in memory. To delete
|
| D | sysrq.txt | 234 console, even though it will appear in the dmesg buffer, and be accessible
235 via the dmesg command and to the consumers of /proc/kmsg. As a specific
|
| D | xz.txt | 34 Keep an eye on dmesg to see diagnostics printed by xz_dec_test.
|
| D | kmemcheck.txt | 145 "dmesg" command to save the log, then getting a lot of kmemcheck
|
| D | SubmittingPatches | 122 downstream: provoking circumstances, excerpts from dmesg, crash
|
| /linux-4.4.14/Documentation/locking/ |
| D | locktorture.txt | 9 messages via printk(), which can be examined via the dmesg (perhaps
141 dmesg | grep torture:
|
| /linux-4.4.14/Documentation/power/ |
| D | swsusp-dmcrypt.txt | 79 dmesg -n 1
97 dmesg -n 6
|
| D | interface.txt | 72 dmesg -s 1000000 | grep 'hash matches'
|
| D | s2ram.txt | 40 holding the power button down, and look at the dmesg output for things
|
| D | basic-pm-debugging.txt | 103 dmesg obtained after the failing test). Failure at this level usually means
|
| /linux-4.4.14/Documentation/dvb/ |
| D | technisat.txt | 14 dmesg | grep frontend may show you for example:
|
| D | avermedia.txt | 285 dmesg and the system logs, it does not appear to affect the
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | abituguru3 | 65 include the output of: "dmesg | grep abituguru"
|
| D | abituguru | 69 dmesg | grep abituguru
|
| D | sis5595 | 105 The driver will recognize this and print a message in dmesg.
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.cx88 | 37 entry for your card in that file. Check the kernel log (using dmesg)
|
| D | fimc.txt | 137 # dmesg | grep -i fimc
|
| D | Zoran | 456 the output of dmesg at high verbosity (load zr36067.o with debug=2,
467 information that might possibly be of interest. Also provide the dmesg output
|
| /linux-4.4.14/Documentation/laptops/ |
| D | asus-laptop.txt | 48 Try "modprobe asus-laptop". Check your dmesg (simply type dmesg). You should
|
| D | laptop-mode.txt | 108 "dmesg". When you use block_dump and your kernel logging level also includes
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi-changer.txt | 88 device [ try "dmesg" if you don't see anything ] and should show up in
109 You can display these messages with the dmesg command (or check the
|
| D | cxgb3i.txt | 79 would be logged to dmesg.
|
| D | osst.txt | 63 as root. dmesg should show you, whether your OnStream tapes have been
|
| D | ChangeLog.megaraid | 54 > It leads to the following messages in dmesg
|
| /linux-4.4.14/tools/testing/ktest/ |
| D | ktest.pl | 154 my $dmesg;
1611 "dmesg" => $dmesg,
1937 open(DMESG, "> $dmesg") or
1938 die "unable to write to $dmesg";
4247 $dmesg = "$tmpdir/dmesg-$machine";
4296 unlink $dmesg;
|
| /linux-4.4.14/Documentation/x86/x86_64/ |
| D | fake-numa-for-cpusets | 23 A machine may be split as follows with "numa=fake=4*512," as reported by dmesg:
|
| /linux-4.4.14/drivers/usb/dwc2/ |
| D | Kconfig | 78 Say Y here to enable logging of missed SOF events to the dmesg log.
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | fault_injection.txt | 26 of items forgotten (check dmesg).
|
| /linux-4.4.14/Documentation/input/ |
| D | walkera0701.txt | 40 walkera0701 module, check dmesg for error messages. Connect TX to PC by
|
| D | yealink.txt | 35 in dmesg, it means that the hid driver has grabbed the device first. Try to
|
| /linux-4.4.14/Documentation/RCU/ |
| D | torture.txt | 9 status messages via printk(), which can be examined via the dmesg
207 The command "dmesg | grep torture:" will extract this information on
314 dmesg | grep torture:
|
| D | stallwarn.txt | 169 like the following in dmesg:
|
| /linux-4.4.14/drivers/auxdisplay/ |
| D | Kconfig | 50 and execute "dmesg" or "cat /proc/ioports". You can see there how
|
| /linux-4.4.14/Documentation/cdrom/ |
| D | ide-cd | 115 the `dmesg' command.
172 In most cases, you should probably check with `dmesg' for any errors
276 - If you get errors from mount, it may help to check `dmesg' to see
318 e. Directory listings are unpredictably truncated, and `dmesg' shows
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | lis3lv02d | 79 If your laptop model is not recognized (cf "dmesg"), you can send an
|
| /linux-4.4.14/security/ |
| D | Kconfig | 14 syslog via dmesg(8).
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | paride.txt | 145 reviewed with the 'dmesg' command. Among those messages will be
366 3.4 Use the verbose option and dmesg if you need help
389 Use 'dmesg' to capture a log of all the PARIDE messages (any messages
|
| /linux-4.4.14/Documentation/x86/ |
| D | earlyprintk.txt | 124 On the host/target system you should see this help line in "dmesg" output:
|
| D | pat.txt | 197 printed to dmesg log.
|
| /linux-4.4.14/Documentation/fb/ |
| D | vesafb.txt | 155 If you see the following in dmesg, choose the type that matches the
|
| D | modedb.txt | 93 CVT also introduced a new naming convention (should be seen from dmesg output):
|
| /linux-4.4.14/Documentation/acpi/apei/ |
| D | einj.txt | 167 You should see something like this in dmesg:
|
| /linux-4.4.14/Documentation/m68k/ |
| D | kernel-options.txt | 162 same level as set by the "dmesg" command, just that the maximum level
163 selectable by dmesg is 8.
184 2.3) and at run time with "dmesg -n 8".
191 'dmesg'.
|
| /linux-4.4.14/fs/cifs/ |
| D | Kconfig | 51 allow optional logging of slow responses to dmesg (depending on the
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | kernel.txt | 268 from using dmesg(8) to view messages from the kernel's log buffer.
271 dmesg(8).
384 to protect against uses of %pK in dmesg(8) if leaking kernel pointer
|
| /linux-4.4.14/Documentation/wimax/ |
| D | README.i2400m | 109 and output messages in the kernel log (dmesg, /var/log/messages or
|
| /linux-4.4.14/Documentation/ide/ |
| D | ide.txt | 133 errors from the driver (with dmesg) complaining about `status=0xff',
|
| /linux-4.4.14/kernel/power/ |
| D | Kconfig | 231 dmesg -s 1000000 | grep 'hash matches'
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig.debug | 123 Look for a message in dmesg output like this:
|
| D | Kconfig | 1535 give you some hints here ["man dmesg"].) Everyone needs either a
2075 will be reported to dmesg, so that either old or
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.sc | 141 'dmesg'.
|
| D | README.gigaset | 356 dmesg
|
| /linux-4.4.14/drivers/ide/ |
| D | Kconfig | 129 similar (check the boot messages with dmesg). If this is your only
161 (check the boot messages with dmesg). Be sure to consult the
|
| /linux-4.4.14/Documentation/usb/ |
| D | gadget-testing.txt | 292 host: dmesg, see the USB drives appear (if system configured to automatically
|
| /linux-4.4.14/Documentation/PCI/ |
| D | MSI-HOWTO.txt | 576 be to examine your dmesg carefully to determine whether MSIs are enabled
|
| /linux-4.4.14/lib/ |
| D | Kconfig.debug | 1 menu "printk and dmesg options"
116 endmenu # "printk and dmesg options"
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | CHANGES | 413 Do not flag user_xattr mount parm in dmesg. Retry failures setting file time
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | spkguide.txt | 136 dmesg | more
|