From Fedora Project Wiki

Revision as of 10:44, 15 March 2011 by Mnowak (talk | contribs)


This test case tests the functionality of the ABRT kerneloops feature.

How to test

Warning: This test abuses syslog a bit - don't forget to restart it at the end of the test case.

  1. We will check that the abrt-dump-oops works and provides correct amount of crashes detected.
  2. Download files:
  3. Test that stand-alone detector tool works properly; Do as a root for both files:
    $ abrt-dump-oops -d -o oops1.test
    abrt-dump-oops: Found oopses: 1
    Version: #1
    BUG: unable to handle kernel NULL pointer dereference at 00000000
    EIP: [<f88dec25>] radeon_cp_init_ring_buffer+0x90/0x302 [radeon] SS:ESP 0068:f0a0cf08
    abrt-dump-oops: Creating dump directories
  4. Open abrt-gui and look for the crash.
  5. And now test if ABRT's scanning of /var/log/messages works, you'll need a root privs for this
  6. Make sure /etc/abrt/abrt_event.conf contains EVENT=post-create analyzer=Kerneloops abrt-action-analyze-oops and EVENT=report analyzer=Kerneloops abrt-action-kerneloops. If changed anything, restart abrtd: service abrtd restart.
  7. cat the downloaded file to /var/log/messages e.g.:
    cat oops1.test >> /var/log/messages
  8. If you are logged as a root: Wait for abrt-applet (make sure it's running) and notification to popup to show the notification about the detected kerneloops. Otherwise open abrt-gui as a root instead.

Expected Results

  1. After running abrt-dump-oops on oops1.test crash should be craeted and visible via abrt-gui and in the terminal. Running the same command on not_oops3.test should not create crash case.
  2. After finishing the second part: oops was detected and is visible in abrt-gui.

Now restart rsyslog service so writing to /var/log/messages works correctly again.