Home
last modified time | relevance | path

Searched refs:dmesg (Results 1 – 25 of 186) sorted by relevance

12345678

/linux-6.15/arch/m68k/tools/amiga/
H A DMakefile7 All: dmesg
10 dmesg: dmesg.c target
11 $(CC) $(CFLAGS) -o dmesg dmesg.c -noixemul
/linux-6.15/tools/testing/selftests/damon/
H A Dsysfs_update_removed_scheme_dir.sh21 dmesg -C
42 if dmesg | grep -q BUG
45 dmesg
51 if dmesg | grep -q BUG
54 dmesg
/linux-6.15/scripts/
H A Dleaking_addresses.pl580 my ($total, $dmesg, $paths, $files) = parse_raw_file($file);
585 print_dmesg($dmesg);
618 my @dmesg; # dmesg output.
627 push @dmesg, $line;
635 return $total, \@dmesg, \%paths, \%files;
640 my ($dmesg) = @_;
644 if (@$dmesg == 0) {
649 foreach(@$dmesg) {
/linux-6.15/tools/testing/selftests/powerpc/mm/
H A Dstress_code_patching.sh28 dmesg -C
35 if dmesg | grep -q 'ftrace bug'
42 if dmesg | grep -q 'ftrace bug'
/linux-6.15/Documentation/translations/zh_CN/core-api/
H A Dprintk-basics.rst27 形缓冲区。读取它的通常方法是使用 ``dmesg`` 。
80 另一种方式，使用 ``dmesg``::
82 # dmesg -n 5
85 见 ``dmesg(1)`` 。
/linux-6.15/tools/testing/selftests/lkdtm/
H A Drun.sh71 DMESG=$(mktemp --tmpdir -t lkdtm-dmesg-XXXXXX)
83 dmesg > "$DMESG"
97 dmesg | comm --nocheck-order -13 "$DMESG" - > "$LOG" || true
/linux-6.15/tools/power/pm-graph/
H A Dbootgraph.py213 dmesg = {} # root data structure variable in Data
229 self.dmesg = {
241 list = self.dmesg[phase]['list']
258 list = self.dmesg[p]['list']
284 self.dmesg[phase]['start']*1000,
371 data.dmesg['user']['end'] = data.end
385 list = data.dmesg[p]['list']
547 list = data.dmesg[p]['list']
558 phase = data.dmesg[p]
570 list = data.dmesg[phase]['list']
[all …]
H A Dsleepgraph.py1545 return sorted(self.dmesg, key=lambda k:self.dmesg[k]['order'])
1552 self.dmesg[pnew] = self.dmesg.pop(phase)
1558 for p in self.dmesg:
1815 p = self.dmesg[phase]
1855 tS, tR = self.dmesg[lp]['end'], self.dmesg[phase]['start']
2195 dm = self.dmesg
3597 del data.dmesg[lp]
3769 data.dmesg[lp]['end'] = data.dmesg[p]['start']
4203 if lp not in data.dmesg:
4219 data.dmesg[lp]['end'] = data.dmesg[p]['start']
[all …]
/linux-6.15/tools/testing/selftests/bpf/
H A Dtest_kmod.sh33 dmesg -C
51 dmesg | grep FAIL
/linux-6.15/tools/testing/selftests/pstore/
H A Dpstore_post_reboot_tests41 check_files_exist dmesg
53 files=`ls dmesg-${backend}-*`
H A Dpstore_tests13 dmesg | grep -Eq "console \[(pstore|${backend})"
/linux-6.15/tools/testing/selftests/net/openvswitch/
H A Dopenvswitch.sh220 PRE_TEST=$(dmesg | grep -c "${ERR_MSG}")
222 POST_TEST=$(dmesg | grep -c "${ERR_MSG}")
694 PRE_TEST=$(dmesg | grep -E "RIP: [0-9a-fA-Fx]+:ovs_dp_cmd_new\+")
696 POST_TEST=$(dmesg | grep -E "RIP: [0-9a-fA-Fx]+:ovs_dp_cmd_new\+")
716 PRE_TEST=$(dmesg | grep -c "${ERR_MSG}")
721 POST_TEST=$(dmesg | grep -c "${ERR_MSG}")
728 PRE_TEST=$(dmesg | grep -c "${ERR_MSG}")
732 POST_TEST=$(dmesg | grep -c "${ERR_MSG}")
/linux-6.15/Documentation/ABI/testing/
H A Dpstore19 -r--r--r-- 1 root root 7896 Nov 30 15:38 dmesg-erst-1
24 - "dmesg" - saved console log
31 $ rm /sys/fs/pstore/dmesg-erst-1
/linux-6.15/Documentation/core-api/
H A Dprintk-basics.rst21 using ``dmesg``.
77 Another way, using ``dmesg``::
79 # dmesg -n 5
82 console. See ``dmesg(1)`` for more information.
/linux-6.15/tools/testing/selftests/cpufreq/
H A Dmain.sh191 dmesg | grep cpufreq >> $1.dmesg_cpufreq.txt
194 dmesg >> $1.dmesg_full.txt
/linux-6.15/tools/testing/selftests/net/netfilter/
H A Dnft_fib.sh28 if dmesg | grep -q ' nft_rpfilter: ';then
29 dmesg -c | grep ' nft_rpfilter: '
77 if dmesg | grep -q ' nft_rpfilter: ';then
78 dmesg | grep ' nft_rpfilter: '
/linux-6.15/Documentation/gpu/amdgpu/display/
H A Ddc-debug.rst17 DC dmesg important messages
20 The dmesg log is the first source of information to be checked, and amdgpu
24 information can be found in the dmesg log. In this sense, look for the part of
49 display version of the hardware in use, which can be retrieved from the dmesg
52 dmesg | grep -i 'display core'
76 From the dmesg file, it is also possible to get the ATOM bios code by using::
78 dmesg | grep -i 'ATOM BIOS'
93 from the dmesg log; for example, search for the following log::
269 Sometimes, dmesg logs aren't enough. This is especially true if a feature is
270 implemented primarily in DMUB firmware. In such cases, all we see in dmesg when
/linux-6.15/Documentation/translations/zh_TW/admin-guide/
H A Dreporting-issues.rst126 構建配置（.config）和 ``dmesg`` 的輸出放在網上的某個地方，並鏈接到它。包
759 [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh ./linux-5.10.5/vmlinux
765 [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh \
833 核構建配置（.config）和 ``dmesg`` 的輸出放在網上的某個地方，並鏈接到它。
872 * 內核的信息，你從 ``dmesg`` 得到的信息寫到一個文件裏。確保它以像“Linux
877 ``dmesg`` 。
H A Dsysrq.rst258 的控制檯上，即使它會出現在 dmesg 緩存中，也可以通過 dmesg 命令和 ``/proc/kmsg``
/linux-6.15/Documentation/translations/zh_CN/admin-guide/
H A Dreporting-issues.rst125 构建配置（.config）和 ``dmesg`` 的输出放在网上的某个地方，并链接到它。包
758 [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh ./linux-5.10.5/vmlinux
764 [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh \
832 核构建配置（.config）和 ``dmesg`` 的输出放在网上的某个地方，并链接到它。
871 * 内核的信息，你从 ``dmesg`` 得到的信息写到一个文件里。确保它以像“Linux
876 ``dmesg`` 。
/linux-6.15/include/linux/
H A Dptdump.h23 bool checkwx, bool dmesg);
/linux-6.15/tools/testing/selftests/powerpc/scripts/
H A Dhmi.sh80 echo "Processed $expected_hmis events; presumed success. Check dmesg."
/linux-6.15/tools/testing/selftests/livepatch/
H A Dfunctions.sh305 LAST_DMESG=$(dmesg | grep "$last_dmesg_msg")
321 result=$(dmesg | awk -v last_dmesg="$LAST_DMESG" 'p; $0 == last_dmesg { p=1 }' | \
/linux-6.15/tools/power/pm-graph/config/
H A Dfreeze.cfg25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
33 # add the dmesg and ftrace log to the html output (default: false)
H A Dstandby.cfg25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
33 # add the dmesg and ftrace log to the html output (default: false)

12345678