Revision as of 15:54, 2 July 2009

Debugging

In all cases, the following should be mentioned and attached to your bug report:

The exact kernel command line used!

An copy of /etc/fstab

cp /etc/fstab ~USER/Desktop/fstab.txt

The output of dmsetup ls --tree.

 dmsetup ls --tree > ~USER/Desktop/dmsetup.txt

If using an raid device the output of cat /proc/mdstat.

 cat /proc/mdstat > ~USER/Desktop/mdstat.txt

Redirect all non-interactive stuff output to /dev/kmsg.

exec >/dev/kmsg 2>&1 </dev/console

rdinitdebug

set -x for the dracut shell

rdbreak=[pre-udev|pre-mount|mount|pre-pivot|]

drop the shell on defined breakpoint

rdudevinfo

set udev to loglevel info

dudevdebug

set udev to loglevel debug

rdnetdebug

debug network scripts in dracut

@@ Line 19: / Line 19: @@
 <pre> cat /proc/mdstat > ~USER/Desktop/mdstat.txt</pre>
+== Preparing your system for debugging ==
+Redirect all non-interactive stuff output to /dev/kmsg.
+<pre>exec >/dev/kmsg 2>&1 </dev/console</pre>
+<pre>rdinitdebug</pre>
+{{admon/note|set -x for the dracut shell}}
+<pre>rdbreak=[pre-udev|pre-mount|mount|pre-pivot|]</pre>
+{{admon/note|drop the shell on defined breakpoint}}
+<pre>rdudevinfo</pre>
+{{admon/note|set udev to loglevel info}}
+<pre>dudevdebug</pre>
+{{admon/note|set udev to loglevel debug}}
+<pre>rdnetdebug</pre>
+{{admon/note|debug network scripts in dracut}}