/openbmc/linux/Documentation/process/ |
H A D | submitting-patches.rst | 61 downstream: provoking circumstances, excerpts from dmesg, crash 756 unique and obvious. Copying the full dmesg output verbatim, however,
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | runtime-testing.rst | 381 DEFAULT_TEST_SUITES:pn-image = "ping ssh df connman syslog xorg scp vnc date rpm dnf dmesg"
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/intel/ |
H A D | ixgbe.rst | 512 the system log (displayed by the "dmesg" command)::
|
/openbmc/linux/Documentation/scsi/ |
H A D | ChangeLog.megaraid | 54 > It leads to the following messages in dmesg
|
/openbmc/linux/Documentation/translations/sp_SP/process/ |
H A D | submitting-patches.rst | 71 dmesg, descripciones del error fatal, regresiones de rendimiento, picos de 774 y obvias. Sin embargo, al copiar la salida completa de dmesg textualmente,
|
/openbmc/openbmc/meta-security/recipes-ids/tripwire/files/ |
H A D | twpol-yocto.txt | 571 /bin/dmesg -> $(SEC_CRIT) ;
|
/openbmc/linux/Documentation/admin-guide/pm/ |
H A D | amd-pstate.rst | 595 $ dmesg | grep "amd_pstate_ut" | tee log.txt
|
/openbmc/linux/Documentation/RCU/ |
H A D | stallwarn.rst | 366 like the following in dmesg::
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | bcache.rst | 189 Be sure to provide as much information that you can including kernel dmesg
|
H A D | spkguide.txt | 136 dmesg | more
|
/openbmc/linux/Documentation/usb/ |
H A D | gadget-testing.rst | 349 host: dmesg, see the USB drives appear (if system configured to automatically
|
/openbmc/linux/lib/ |
H A D | Kconfig.debug | 4 menu "printk and dmesg options" 209 endmenu # "printk and dmesg options" 1636 result in dmesg getting spammed for a surprisingly long
|
/openbmc/linux/arch/x86/ |
H A D | Kconfig | 1678 give you some hints here ["man dmesg"].) Everyone needs either a 2295 will be reported to dmesg, so that either old or 2505 a noisy dmesg about callthunks generation and call patching for
|
/openbmc/linux/Documentation/driver-api/ |
H A D | uio-howto.rst | 567 dmesg
|
/openbmc/linux/Documentation/kernel-hacking/ |
H A D | hacking.rst | 238 :c:func:`printk()` feeds kernel messages to the console, dmesg, and
|
/openbmc/linux/Documentation/translations/it_IT/kernel-hacking/ |
H A D | hacking.rst | 257 :c:func:`printk()` fornisce messaggi alla console, dmesg, e al demone syslog.
|
/openbmc/openbmc/poky/documentation/kernel-dev/ |
H A D | common.rst | 783 # dmesg | less 939 # dmesg | less
|
/openbmc/linux/Documentation/admin-guide/sysctl/ |
H A D | vm.rst | 867 as 0) and "fails" with EINVAL if any are found, with a warning in dmesg.
|
/openbmc/linux/Documentation/arch/s390/ |
H A D | vfio-ap.rst | 685 is logged to the kernel ring buffer which can be viewed with the 'dmesg'
|
/openbmc/linux/Documentation/admin-guide/cgroup-v1/ |
H A D | memory.rst | 689 and a warning printed to dmesg.
|
/openbmc/linux/arch/arm/ |
H A D | Kconfig.debug | 30 Look for a message in dmesg output like this:
|
/openbmc/linux/init/ |
H A D | Kconfig | 1706 "dmesg | grep kallsyms_selftest" to collect test results. "finish" is
|
/openbmc/qemu/tests/data/qobject/ |
H A D | qdict.txt | 4560 dmesg.c: 1657
|
/openbmc/openbmc/poky/meta/lib/oeqa/files/ |
H A D | buildhistory_filelist2.txt | 27 lrwxrwxrwx root root 21 ./bin/dmesg -> /bin/dmesg.util-linux 28 -rwxr-xr-x root root 84256 ./bin/dmesg.util-linux 180 -rwxr-xr-x root root 352 ./etc/init.d/dmesg.sh 229 -rw-r--r-- root root 121 ./etc/logrotate-dmesg.conf 323 lrwxrwxrwx root root 18 ./etc/rcS.d/S38dmesg.sh -> ../init.d/dmesg.sh 5602 -rw-r--r-- root root 59 ./usr/lib/opkg/alternatives/dmesg
|
H A D | buildhistory_filelist1.txt | 27 lrwxrwxrwx root root 21 ./bin/dmesg -> /bin/dmesg.util-linux 28 -rwxr-xr-x root root 84256 ./bin/dmesg.util-linux 180 -rwxr-xr-x root root 352 ./etc/init.d/dmesg.sh 229 -rw-r--r-- root root 121 ./etc/logrotate-dmesg.conf 323 lrwxrwxrwx root root 18 ./etc/rcS.d/S38dmesg.sh -> ../init.d/dmesg.sh 5601 -rw-r--r-- root root 59 ./usr/lib/opkg/alternatives/dmesg
|