| /openbmc/linux/Documentation/translations/zh_CN/admin-guide/ |
| H A D | bug-hunting.rst | 79 有时 ``klogd`` 会挂掉，这种情况下您可以运行 ``dmesg > file`` 从内核缓冲区
97 Documentation/admin-guide/kdump/gdbmacros.txt 中的dmesg gdbmacro从旧内存
|
| /openbmc/linux/Documentation/translations/zh_TW/admin-guide/ |
| H A D | bug-hunting.rst | 82 有時 ``klogd`` 會掛掉，這種情況下您可以運行 ``dmesg > file`` 從內核緩衝區
100 Documentation/admin-guide/kdump/gdbmacros.txt 中的dmesg gdbmacro從舊內存
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A D | gdb-kernel-debugging.rst | 111 (gdb) lx-dmesg
174 lx-dmesg -- Print Linux kernel log buffer
|
| /openbmc/linux/tools/power/pm-graph/config/ |
| H A D | custom-timeline-functions.cfg | 25 # add the dmesg and ftrace log to the html output (default: false)
57 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
|
| /openbmc/linux/Documentation/virt/kvm/x86/ |
| H A D | running-nested-guests.rst | 195 undefined behavior. You might see a ``kernel BUG!`` entry in ``dmesg``, a
254 - Full ``dmesg`` output from L0
256 - Full ``dmesg`` output from L1
|
| /openbmc/linux/Documentation/dev-tools/kunit/ |
| H A D | running_tips.rst | 159 results to dmesg in TAP format. So you just need to add your tests to your
169 Then we'd see output like this in dmesg signaling the test ran and passed:
216 You can use ``kunit.py parse`` to parse dmesg for test output and print out
221 $ ./tools/testing/kunit/kunit.py parse /var/log/dmesg
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/packagegroups/ |
| H A D | packagegroup-obmc-apps.bbappend | 40 …st-code-manager phosphor-host-postd kexec-tools makedumpfile kdump vmcore-dmesg debug-trigger libm…
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | os_utils_config.robot | 74 ${output} ${stderr}= Execute Command dmesg -xT -l emerg,alert,crit,err
|
| H A D | os_utilities.robot | 20 # Error strings to check from dmesg.
23 # GPU specific error message from dmesg.
256 [Documentation] Check if dmesg has nvidia errors logged.
259 ... dmesg | egrep '${ERROR_REGEX}'
262 ... msg=OS dmesg shows ${ERROR_DBE_MSG}.
|
| /openbmc/linux/Documentation/networking/ |
| H A D | batman-adv.rst | 111 a number of ways. Try using the commands: ``dmesg``, ``logread``, or looking in
115 $ dmesg | grep batman-adv
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | technisat.rst | 25 dmesg | grep frontend may show you for example:
|
| /openbmc/qemu/docs/system/s390x/ |
| H A D | vfio-ccw.rst | 72 [root@guest ~]# dmesg -t
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | abituguru3.rst | 75 include the output of: `dmesg | grep abituguru`
|
| /openbmc/openbmc/poky/meta/lib/oeqa/runtime/cases/ |
| H A D | parselogs.py | 165 (status, dmesg) = self.target.run('dmesg > /tmp/dmesg_output.log')
|
| /openbmc/linux/Documentation/translations/zh_CN/PCI/ |
| H A D | msi-howto.rst | 225 仔细检查你的dmesg以确定你的机器是否启用了MSI。你还应该检查你的.config以确定你已经
|
| /openbmc/linux/Documentation/userspace-api/media/rc/ |
| H A D | lirc-dev-intro.rst | 19 Example dmesg output upon a driver registering w/LIRC:
23 $ dmesg |grep lirc_dev
|
| /openbmc/openbmc/meta-openembedded/meta-initramfs/recipes-devtools/klibc/ |
| H A D | klibc-utils.inc | 23 install -m 755 usr/utils/${KLIBC_UTILS_VARIANT}/dmesg ${D}${base_bindir}
|
| /openbmc/linux/samples/vfio-mdev/ |
| H A D | README.rst | 75 In the Linux guest VM, dmesg output for the device is as follows:
|
| /openbmc/linux/Documentation/admin-guide/laptops/ |
| H A D | asus-laptop.rst | 52 Try "modprobe asus-laptop". Check your dmesg (simply type dmesg). You should
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | scsi-changer.rst | 92 device [ try "dmesg" if you don't see anything ] and should show up in
113 You can display these messages with the dmesg command (or check the
|
| /openbmc/linux/drivers/of/ |
| H A D | Kconfig | 33 via capturing the console output or via the dmesg command. Process
|
| /openbmc/linux/Documentation/admin-guide/kdump/ |
| H A D | gdbmacros.txt | 289 define dmesg
321 document dmesg
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/amd/ |
| H A D | pds_core.rst | 23 $ dmesg | grep pds_core
|
| /openbmc/linux/Documentation/arch/x86/x86_64/ |
| H A D | fake-numa-for-cpusets.rst | 30 A machine may be split as follows with "numa=fake=4*512," as reported by dmesg::
|
| /openbmc/linux/drivers/usb/dwc2/ |
| H A D | Kconfig | 83 Say Y here to enable logging of missed SOF events to the dmesg log.
|