RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 618946 - trace show returns no result
Summary: trace show returns no result
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: crash-trace-command
Version: 6.0
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Dave Anderson
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-28 06:26 UTC by Caspar Zhang
Modified: 2013-07-03 07:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-19 12:03:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Caspar Zhang 2010-07-28 06:26:26 UTC 
Description of problem:
As the help page describes, the `trace show' command should return function tracer, but I executed trace show and trace show -c <cpu>, none of them returns a result:

crash> trace show
crash> trace show
crash> trace show -c 0
crash> trace show
crash> trace show
crash> trace show -c 0-3
crash> trace show
crash> trace show
crash> 


Version-Release number of selected component (if applicable):
1.0-3.el6                                        

How reproducible:
always

Steps to Reproduce:
1. run crash /path/to/vmlinux /path/to/vmcore (or run crash directly)
2. extend /path/to/trace.so
3. run trace show
  
Actual results:
trace show returns no results

Expected results:
trace show should return tracer info according to right trace flags.

Additional info:
Comment 2 Dave Anderson 2010-08-09 14:40:21 UTC 
As I understand it, if there is no outstanding (unconsumed) trace event data
remaining in any of the kernel's per-cpu ring buffers, then the command shows
nothing.
Comment 3 Dave Anderson 2010-08-09 14:41:56 UTC 
Lai,

Can you assist Caspar in creating a QA test procedure to test the 
package?

Thanks,
  Dave
Comment 4 Caspar Zhang 2010-08-09 18:20:41 UTC 
(In reply to comment #2)
> As I understand it, if there is no outstanding (unconsumed) trace event data
> remaining in any of the kernel's per-cpu ring buffers, then the command shows
> nothing.    

Thank you Dave, I think that's the reason. I was using sysrq-trigger to create vmcore and then ran crash on live system. So a correct reproducer is needed :-)
Comment 5 Lai Jiangshan 2010-10-19 08:43:18 UTC 
(In reply to comment #4)
> (In reply to comment #2)
> > As I understand it, if there is no outstanding (unconsumed) trace event data
> > remaining in any of the kernel's per-cpu ring buffers, then the command shows
> > nothing.    
> 
> Thank you Dave, I think that's the reason. I was using sysrq-trigger to create
> vmcore and then ran crash on live system. So a correct reproducer is needed :-)

Hi, Caspar

When there is no event int the ringbuffers, "trace show" will not show any events to the stdout.(the tracer is not started or all the events are consumed).

-------------------------------------
To start a tracer:
# mount -t debugfs xx /mnt/
# cd /mnt/tracing/
# cat available_tracers 
function_graph function sched_switch nop
# echo function_graph > current_tracer      # start a tracer
# cat trace_pipe                            # consume some events
#  ^C                                       # stop consume
# echo c > /proc/sysrq-trigger
                                            # start to test ..
--------------------------------------

If there is no event in the ringbuffers, it is correct when "trace show" outputs nothing.

Thanks a lot.
Lai
Comment 6 Caspar Zhang 2010-10-19 12:03:46 UTC 
Thanks Lai, I'll close this bug.
Comment 7 Dave Anderson 2010-10-19 15:18:59 UTC 
Thanks Lai.

I note that you can essentially test this on a live system as well?

Although when doing so, I noticed that the "trace" command with no arguments
shows the tracer that was the "current_tracer" at the time the trace.so module
was loaded.  But if it gets changed subsequently while the crash session is
still active, that value is not updated.  However, the new tracer's data does
get displayed by "trace show".

But that's a minor issue, and if I'm not mistaken, this module is 
designed for use with crash dumps and not live systems.
Note You need to log in before you can comment on or make changes to this bug.