Home
last modified time | relevance | path

Searched refs:dmesg (Results 151 – 175 of 205) sorted by relevance

123456789

/openbmc/linux/Documentation/networking/devlink/
H A Dmlx5.rst225 On firmware error, the health buffer is dumped into the dmesg. The log
/openbmc/linux/security/
H A DKconfig15 syslog via dmesg(8).
/openbmc/linux/Documentation/admin-guide/
H A Dtainted-kernels.rst17 information about this to the logs ``dmesg`` outputs. It's also possible to
H A Dreporting-issues.rst148 (.config) and the output from ``dmesg`` available somewhere on the net and
978 …[user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh ./linux-5.10.5/vmlinux
985 [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh \
1075 (.config) and the output from ``dmesg`` available somewhere on the net and
1129 * the kernel's messages that you get from ``dmesg`` written to a file. Make
1135 issue and call ``dmesg`` right afterwards.
/openbmc/linux/Documentation/driver-api/media/drivers/
H A Dzoran.rst535 the output of dmesg at high verbosity (load zr36067.o with debug=2,
546 information that might possibly be of interest. Also provide the dmesg output
/openbmc/linux/mm/
H A DKconfig.debug173 Look for a message in dmesg output like this:
/openbmc/linux/Documentation/networking/
H A Dfilter.rst528 Example output from dmesg::
668 including timings in nsec can be found in the kernel log (dmesg).
/openbmc/u-boot/doc/
H A DREADME.odroid76 - check the device with "dmesg"
/openbmc/linux/Documentation/gpu/rfc/
H A Dxe.rst229 for better organization of the dumps, snapshot support, dmesg extra print,
/openbmc/linux/Documentation/networking/device_drivers/ethernet/intel/
H A Dice.rst109 your console, set dmesg to eight by entering the following::
111 # dmesg -n 8
603 system log using the dmesg command.
H A Di40e.rst306 your console, set dmesg to eight by entering the following::
308 dmesg -n 8
/openbmc/linux/kernel/power/
H A DKconfig271 dmesg -s 1000000 | grep 'hash matches'
/openbmc/linux/Documentation/PCI/
H A Dmsi-howto.rst276 be to examine your dmesg carefully to determine whether MSIs are enabled
/openbmc/linux/Documentation/power/
H A Dbasic-pm-debugging.rst111 dmesg obtained after the failing test). Failure at this level usually means
/openbmc/linux/Documentation/arch/x86/
H A Dsgx.rst234 When EPC page leaks happen, a WARNING like this is shown in dmesg:
/openbmc/linux/Documentation/gpu/
H A Dtodo.rst204 sure your work will be merged - not everyone agrees that the DRM dmesg macros
525 * Encoding the actual oops and preceding dmesg in a QR might help with the
/openbmc/linux/Documentation/admin-guide/sysctl/
H A Dkernel.rst245 from using ``dmesg(8)`` to view messages from the kernel's log
249 ``CAP_SYSLOG`` to use ``dmesg(8)``.
537 using `dmesg_restrict`_ to protect against uses of %pK in ``dmesg(8)``
/openbmc/linux/Documentation/translations/it_IT/process/
H A Ddeprecated.rst179 esponne un indirizzo di memoria in dmesg, proc, sysfs, eccetera. Per
H A Dsubmitting-patches.rst68 le circostanze che causano il problema, estratti da dmesg, descrizioni di
752 e ovvie. Copiare integralmente l'output di ``dmesg`` aggiunge tante
/openbmc/linux/Documentation/core-api/
H A Dprintk-formats.rst167 userspace from e.g. procfs or sysfs, not for dmesg. Please refer to the
/openbmc/linux/Documentation/process/
H A Ddeprecated.rst168 exposure flaws in dmesg, proc, sysfs, etc. Instead of leaving these to
/openbmc/linux/Documentation/userspace-api/
H A Dlandlock.rst22 looking for "landlock: Up and running" in kernel logs (as root): ``dmesg | grep
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-power123 dmesg -s 1000000 | grep 'hash matches'
/openbmc/linux/Documentation/translations/sp_SP/process/
H A Ddeprecated.rst183 resultaría en exponer esas direcciones en dmesg, proc, sysfs, etc. En vez
/openbmc/linux/drivers/auxdisplay/
H A DKconfig87 and execute "dmesg" or "cat /proc/ioports". You can see there how

123456789