Welcome to the Reiser4 Wiki, the Wiki for users and developers of the ReiserFS and Reiser4 filesystems.

For now, most of the documentation is just a snapshot of the old Namesys site (archive.org, 2007-09-29).

There was also a Reiser4 Wiki (archive.org, 2007-07-06) once on pub.namesys.com.

Debug Reiser4

From Reiser4 FS Wiki
Revision as of 23:25, 20 June 2017 by Chris goe (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

How to collect kernel oops messages


Testing machine is a machine where you test Reiser4;

Control machine is a machine where you collect oops messages.

NOTE: testing machine and control machine should be different machines.


1. Connect testing and control machines with a serial (null-modem) cable.

2. Find out device names for the used serial ports on the testing and control machines. Suppose it is /dev/ttyS0 for the testing machine and /dev/ttyS1 for the control machine.

3. On the control machine open a console and type the following (as root):

   # stty ispeed 115200 ospeed 115200 -F /dev/ttyS1
   # cat /dev/ttyS1

4. Restart the testing machine passing "console=ttyS0,115200" along with other kernel parameters to the boot loader (for example by editing grub.cfg file). You should be able to see boot messages on the console opened at step (3) on the control machine.

5. Run any stress tests on the testing machine. On the console opened at step (3) you will be able to collect any system information including oops messages, etc.

6. Send the oops messages to reiserfs-devel mailing list.

Comment. If testing, and(or) control machine machine doesn't have a serial port, then it is possible to use USB-to-serial adapter(s). In this case the name of device will look like /dev/ttyUSB0.

Comment. You can also use minicom utility on the control machine to collect oops messages.

Personal tools