| /openbmc/linux/arch/arm/boot/dts/broadcom/ |
| H A D | bcm47094-dlink-dir-890l.dts | 99 /* Called "factory reset" in the vendor dmesg */
|
| /openbmc/linux/tools/testing/ktest/ |
| H A D | ktest.pl | 169 my $dmesg;
1796 "dmesg" => $dmesg,
2168 open(DMESG, "> $dmesg") or
2169 dodie "unable to write to $dmesg";
4394 $dmesg = "$tmpdir/dmesg-$machine";
4452 unlink $dmesg;
|
| /openbmc/linux/Documentation/driver-api/dmaengine/ |
| H A D | dmatest.rst | 133 % dmesg | tail -n 1
144 % dmesg | tail -n 1
|
| /openbmc/linux/Documentation/networking/ |
| H A D | netconsole.rst | 235 dmesg -n 8
240 dmesg(8) man page and Documentation/admin-guide/kernel-parameters.rst
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | cxgb3i.rst | 85 would be logged to dmesg.
|
| /openbmc/linux/Documentation/input/devices/ |
| H A D | walkera0701.rst | 45 walkera0701 module, check dmesg for error messages. Connect TX to PC by
|
| H A D | yealink.rst | 209 in dmesg, it means that the hid driver has grabbed the device first. Try to
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | avermedia.rst | 80 dmesg and the system logs, it does not appear to affect the
|
| H A D | fimc.rst | 138 # dmesg | grep -i fimc
|
| /openbmc/linux/Documentation/power/ |
| H A D | s2ram.rst | 42 holding the power button down, and look at the dmesg output for things
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | abituguru.rst | 85 dmesg | grep abituguru
|
| H A D | sis5595.rst | 123 The driver will recognize this and print a message in dmesg.
|
| /openbmc/openbmc/poky/meta/recipes-extended/mdadm/ |
| H A D | mdadm_4.3.bb | 82 … -e '/die "dmesg prints errors when testing $_basename!"/i\\t\t\t\techo -ne "FAIL: $_script" &&' \
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/pensando/ |
| H A D | ionic.rst | 33 $ dmesg | grep ionic
|
| /openbmc/linux/Documentation/virt/hyperv/ |
| H A D | overview.rst | 164 A Linux guest on Hyper-V outputs in dmesg the version of Hyper-V
174 number is also output to dmesg during boot. This version number
|
| /openbmc/openbmc-test-automation/ffdc/ |
| H A D | ffdc_config.yaml | 63 - "dmesg >/tmp/BMC_dmesg.txt"
186 - "dmesg >/tmp/OS_dmesg.txt"
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | torture.rst | 14 status messages via printk(), which can be examined via the dmesg
33 The command "dmesg | grep torture:" will extract this information on
147 dmesg | grep torture:
|
| /openbmc/linux/Documentation/misc-devices/ |
| H A D | lis3lv02d.rst | 85 If your laptop model is not recognized (cf "dmesg"), you can send an
|
| /openbmc/openbmc-test-automation/systest/ |
| H A D | gpu_stress_test.robot | 104 # Post test loop look out for dmesg error logged.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | dev-kmsg | 127 Users: dmesg(1), userspace kernel log consumers
|
| H A D | debugfs-driver-habanalabs | 115 Description: Dumps all razwi events to dmesg if exist.
124 Description: Dumps all security violations to dmesg. This will also ack
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/neterion/ |
| H A D | s2io.rst | 37 # dmesg | tail -40
|
| /openbmc/linux/Documentation/dev-tools/kunit/ |
| H A D | run_wrapper.rst | 151 ./tools/testing/kunit/kunit.py parse /var/log/dmesg
153 dmesg | ./tools/testing/kunit/kunit.py parse
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | ramoops.rst | 139 files is ``dmesg-ramoops-N``, where N is the record number in memory. To delete
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/aquantia/ |
| H A D | atlantic.rst | 40 your console, set dmesg to eight by entering the following::
42 dmesg -n 8
|