Re: LTTng usage issue

* Srinivasa Reddy ([email protected]) wrote:
> *****************************************************************
> 
> [Mathieu] Is it a kernel.org vanilla kernel ? 
> 
> [Srinivas] Don't know.. The version of the kernel is 2.6.19. How to know
> whether it is vanilla or something else?
> 

Did you get the tarball from kernel.org or from a distribution ? But
since the patch applies correctly, it seems that it is a vanilla kernel,
a "real" 2.6.19.


> 
> [Mathieu] Could you recompile ltt-control with:
> make -DDEBUG and give me the output when running it?
> 
> [Srinivas]Yes. But it's not taking that command (-DDEBUG). Please see
> the below message:
> 

Sorry.. make CFLAGS=-DDEBUG

> [sreddy@l-blr-sddeg03 ltt-control-0.32-05122006]$ make -DDEBUG
> make: invalid option -- D
> make: invalid option -- D
> make: invalid option -- E
> make: invalid option -- U
> make: invalid option -- G
> Usage: make [options] [target] ...
> Options:
>   -b, -m                      Ignored for compatibility.
>   -B, --always-make           Unconditionally make all targets.
>   -C DIRECTORY, --directory=DIRECTORY
>                               Change to DIRECTORY before doing anything.
>   -d                          Print lots of debugging information.
>   --debug[=FLAGS]             Print various types of debugging
> information.
>   -e, --environment-overrides
>                               Environment variables override makefiles.
>   -f FILE, --file=FILE, --makefile=FILE
>                               Read FILE as a makefile.
>   -h, --help                  Print this message and exit.
>   -i, --ignore-errors         Ignore errors from commands.
>   -I DIRECTORY, --include-dir=DIRECTORY
>                               Search DIRECTORY for included makefiles.
>   -j [N], --jobs[=N]          Allow N jobs at once; infinite jobs with
> no arg.
>   -k, --keep-going            Keep going when some targets can't be
> made.
>   -l [N], --load-average[=N], --max-load[=N]
>                               Don't start multiple jobs unless load is
> below N.
>   -n, --just-print, --dry-run, --recon
>                               Don't actually run any commands; just
> print them.
>   -o FILE, --old-file=FILE, --assume-old=FILE
>                               Consider FILE to be very old and don't
> remake it.
>   -p, --print-data-base       Print make's internal database.
>   -q, --question              Run no commands; exit status says if up to
> date.
>   -r, --no-builtin-rules      Disable the built-in implicit rules.
>   -R, --no-builtin-variables  Disable the built-in variable settings.
>   -s, --silent, --quiet       Don't echo commands.
>   -S, --no-keep-going, --stop
>                               Turns off -k.
>   -t, --touch                 Touch targets instead of remaking them.
>   -v, --version               Print the version number of make and exit.
>   -w, --print-directory       Print the current directory.
>   --no-print-directory        Turn off -w, even if it was turned on
> implicitly.
>   -W FILE, --what-if=FILE, --new-file=FILE, --assume-new=FILE
>                               Consider FILE to be infinitely new.
>   --warn-undefined-variables  Warn when an undefined variable is
> referenced.
> 
> This program built for x86_64-redhat-linux-gnu
> Report bugs to <[email protected]>
> [sreddy@l-blr-sddeg03 ltt-control-0.32-05122006]$
> 
> ************************************************************************
> 
> [Mathieu] And also I think trying to use a different kernel version
> could help finding the problem more quickly,
> 
> [Srinivas]Ok, then I can try with 2.6.21. But I am facing some problems
> with this version while patching LTTng. That is posted as different
> message.
> 
> 
> [Mathieu] since it seems to be related to kernel/relay.c, and its
> version depends on the kernel you are compiling. Trying 2.6.20 kernels
> with LTTng 0.9.0 would tell us much more. And then you could even try a
> backport from the 0.9.0 patches to you 2.6.19 kernel. You would have to
> update the userspace tools too.
> 
> [Srinivas] Back-porting from 0.9.0 will be more difficult I feel. And I
> don't know how to do that also. :-( 
> Since there is no problem while patching and building the kernel, why
> that relay is not able to create the channel files?
> Please send me that LTTng patch from git repository for 2.6.19 kernel.
> That would help me to fix this problem.
> 

I would prefer to help you clone the repository, since extracting
patches from git is precisely the step I suppose is flawed. Can you be
more explicit about the git error, i.e. by giving the error message ?

Mathieu


> Regards,
> Srinivas. 
> 

-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68