[openib-general] how to turn on kernel level tracing (mtl_log )

[Tziporet Koren]

Regarding the low level driver (VAPI) only:
The kernel debug messages can be generated only at compile time.
to generate them one need to compile with the variable MTCONF set to debug.
Once it is compiled you can decide which modules to see by the command:
logset <module_name> trace:1234 (or all)

To see use level errors/traces once should 
export MTL_LOG="error:1234"
If you compiled with debug enables you can also do:
export MTL_LOG="error:1234 debug:1234 trace:1234"

Tziporet

-----Original Message-----
From: mark kowalski [mailto:mkowalski01 at gmail.com]
Sent: Thursday, March 17, 2005 1:16 AM
To: openib-general at openib.org
Subject: [openib-general] how to turn on kernel level tracing (mtl_log)


I've been trying, without success unfortunately to turn on  tracing
within the kernel components of openib.  I've used the logset
mtl_log_dbg_print command to toggle the "debug_print" variable used in
the mtl_log command. I've also used logset to set the list of
severities to be printed to 8 (12345678).  I've also turned on
printing for any debug or error messages (MTL_DEBUG and MTL_ERROR).  I
even went so far as to add print info structure records for every
module_name I could grep in the source code (VIP, HCA, VIPKL, etc). 
None of this had any affect on getting any kind of trace records
printed out of the kernel.  the only messages I got were sev 1
messages when I shut the system down.

 <4>***** mtl_log:DEBUG: layer 'VIPKL', type 2, sev '1'
<4>***** mtl_log:DEBUG: Found layer 'VIPKL', Name="error", sev="12345678"
<4>***** mtl_log:DEBUG: print string
<1> VIPKL(1):
var/tmp/IBGD/lib/modules/2.6.4-52-smp/build/drivers/infiniband/hw/mellanox-h
ca/vipkl/em.c[87]:
EM delete:found unreleased async object

<4>***** mtl_log:DEBUG: layer 'VIPKL', type 2, sev '1'
<4>***** mtl_log:DEBUG: Found layer 'VIPKL', Name="error", sev="12345678"
<4>***** mtl_log:DEBUG: print string
<1> VIPKL(1):
var/tmp/IBGD/lib/modules/2.6.4-52-smp/build/drivers/infiniband/hw/mellanox-h
ca/vipkl/em.c[87]:
EM delete:found unreleased async object

Is the code originally compiled with the MAX_TRACE variable set to 1? 
Is there a way this could be changed  or bypassed without recompiling
the source?  I also added the MTL_LOG environment variable to get
non-kernel messages but that didn't produce any messages either.

any help would be appreciated.
Thanks
Mark
_______________________________________________
openib-general mailing list
openib-general at openib.org
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit
http://openib.org/mailman/listinfo/openib-general
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20050317/a7a782ff/attachment.html>