Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 594079 - systemtap cannot probe 'scsi.ioentry'
Summary: systemtap cannot probe 'scsi.ioentry'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: systemtap
Version: 6.0
Hardware: All
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Frank Ch. Eigler
QA Contact: Petr Muller
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-20 14:00 UTC by Jeff Bastian
Modified: 2018-10-27 15:19 UTC (History)
5 users (show)

Fixed In Version: systemtap-1.2-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-02 19:54:28 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jeff Bastian 2010-05-20 14:00:09 UTC 
Description of problem:
The scsi.ioentry event never fires on RHEL 6.0.

Version-Release number of selected component (if applicable):
kernel-2.6.32-25.el6.x86_64
systemtap-1.2-1.el6.x86_64

How reproducible:
every time

Steps to Reproduce:
1. stap -e 'probe scsi.ioentry { print("scsi.ioentry fired\n") }'
2. hurry up and wait
  
Actual results:
it never prints any "scsi.ioentry fired" messages

Expected results:
it should print "scsi.ioentry fired" fairly often and rapidly

Additional info:
This works fine on RHEL 5.5
Comment 2 Frank Ch. Eigler 2010-05-21 17:34:43 UTC 
upstream systemtap commit #6fa8e03 appears to correct this; ready for backporting.
Comment 6 releng-rhel@redhat.com 2010-07-02 19:54:28 UTC 
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Note You need to log in before you can comment on or make changes to this bug.