public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: 符永涛 <yongtaofu@gmail.com>
Cc: Ben Myers <bpm@sgi.com>, Eric Sandeen <sandeen@sandeen.net>,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22
Date: Fri, 12 Apr 2013 08:11:43 -0400	[thread overview]
Message-ID: <5167F9FF.40800@redhat.com> (raw)
In-Reply-To: <CADFMGuJLEChscGDtQjhxNf1EOhpAP2Mj+2BfQsVtef2MSphjZA@mail.gmail.com>

On 04/12/2013 02:00 AM, 符永涛 wrote:
> stap -e 'probe module("xfs").function("xfs_iunlink"){}'
> WARNING: cannot find module xfs debuginfo: No DWARF information found
> semantic error: no match while resolving probe point
> module("xfs").function("xfs_iunlink")
> Pass 2: analysis failed.  Try again with another '--vp 01' option.
> 

This is the error I get if I remove
kernel-debuginfo-2.6.32-279.el6.x86_64.rpm. Otherwise, the example
xfs_iunlink() probe works for me. The xfs.ko.debug module installed to
my system matches the path you've listed below, as well.

I suppose it couldn't hurt to try and remove/reinstall that module. Do
you get any output from 'objdump --dwarf .../xfs.ko.debug?'

I also notice that you have a newer kernel installed on this system. Are
you sure you're still running the -279 build? I'm not an stap expert,
but it would be nice to find out where it's looking for debug info at
runtime...

Brian

P.S., The commands you've listed in another mail:

sudo stap -L 'kernel.trace("*")'|grep xfs_iunlink
sudo stap -L 'kernel.trace("*")'|grep xfs_ifree

... don't print anything on my box either, but as mentioned, the
xfs_iunlink() probe works. I suspect these are not relevant. Perhaps you
are listing tracepoints here? The following command prints the probe
point info on my box:

stap -L 'module("xfs").function("xfs_iunlink")'

> 
> 2013/4/12 符永涛 <yongtaofu@gmail.com <mailto:yongtaofu@gmail.com>>
> 
>     ls -l
>     /usr/lib/debug/lib/modules/2.6.32-279.el6.x86_64/kernel/fs/xfs/xfs.ko.debug
>     -r--r--r-- 1 root root 21393024 Apr 12 12:08
>     /usr/lib/debug/lib/modules/2.6.32-279.el6.x86_64/kernel/fs/xfs/xfs.ko.debug
> 
>     rpm -qa|grep  kernel
>     kernel-headers-2.6.32-279.el6.x86_64
>     kernel-devel-2.6.32-279.el6.x86_64
>     kernel-2.6.32-358.el6.x86_64
>     kernel-debuginfo-common-x86_64-2.6.32-279.el6.x86_64
>     abrt-addon-kerneloops-2.0.8-6.el6.x86_64
>     kernel-firmware-2.6.32-358.el6.noarch
>     kernel-debug-2.6.32-358.el6.x86_64
>     kernel-debuginfo-2.6.32-279.el6.x86_64
>     dracut-kernel-004-283.el6.noarch
>     libreport-plugin-kerneloops-2.0.9-5.el6.x86_64
>     kernel-devel-2.6.32-358.el6.x86_64
>     kernel-2.6.32-279.el6.x86_64
> 
>     rpm -q kernel-debuginfo
>     kernel-debuginfo-2.6.32-279.el6.x86_64
> 
>     rpm -q kernel
>     kernel-2.6.32-279.el6.x86_64
>     kernel-2.6.32-358.el6.x86_64
> 
>     do I need to re probe it?
> 
> 
>     2013/4/12 Eric Sandeen <sandeen@sandeen.net
>     <mailto:sandeen@sandeen.net>>
> 
>         On 4/11/13 11:32 PM, 符永涛 wrote:
>         > Hi Brian,
>         > Sorry but when I execute the script it says:
>         > WARNING: cannot find module xfs debuginfo: No DWARF
>         information found
>         > semantic error: no match while resolving probe point
>         module("xfs").function("xfs_iunlink")
>         >
>         > uname -a
>         > 2.6.32-279.el6.x86_64
>         > kernel debuginfo has been installed.
>         >
>         > Where can I find the correct xfs debuginfo?
> 
>         it should be in the kernel-debuginfo rpm (of the same
>         version/release as the kernel rpm you're running)
> 
>         You should have:
> 
>         /usr/lib/debug/lib/modules/2.6.32-279.el6.x86_64/kernel/fs/xfs/xfs.ko.debug
> 
>         If not, can you show:
> 
>         # uname -a
>         # rpm -q kernel
>         # rpm -q kernel-debuginfo
> 
>         -Eric
> 
> 
> 
> 
> 
>     -- 
>     符永涛
> 
> 
> 
> 
> -- 
> 符永涛

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-04-12 12:14 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 12:53 need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22 符永涛
2013-04-09 13:03 ` 符永涛
2013-04-09 13:05   ` 符永涛
2013-04-09 14:52     ` Ben Myers
2013-04-09 15:00       ` 符永涛
2013-04-09 15:07       ` 符永涛
2013-04-09 15:10         ` 符永涛
2013-04-10 10:10           ` Emmanuel Florac
2013-04-10 12:52             ` Dave Chinner
2013-04-10 13:52             ` 符永涛
2013-04-11 19:11               ` 符永涛
2013-04-11 19:55                 ` 符永涛
2013-04-11 23:26                 ` Brian Foster
2013-04-12  0:45                   ` 符永涛
2013-04-12 12:50                     ` Brian Foster
2013-04-12 13:42                       ` 符永涛
2013-04-12 13:48                         ` 符永涛
2013-04-12 13:51                           ` 符永涛
2013-04-12 13:59                             ` 符永涛
2013-04-12  1:07                   ` Eric Sandeen
2013-04-12  1:36                     ` 符永涛
2013-04-12  1:38                       ` 符永涛
2013-04-12  6:15                     ` 符永涛
2013-04-12  4:32                   ` 符永涛
2013-04-12  5:16                     ` Eric Sandeen
2013-04-12  5:40                       ` 符永涛
2013-04-12  6:00                         ` 符永涛
2013-04-12 12:11                           ` Brian Foster [this message]
2013-04-12  7:44                         ` 符永涛
2013-04-12  8:32                           ` 符永涛
2013-04-12 12:41                             ` Brian Foster
2013-04-12 14:48                               ` 符永涛
2013-04-15  2:08                                 ` 符永涛
2013-04-15  5:04                                   ` 符永涛
2013-04-15 12:54                                     ` 符永涛
2013-04-15 13:33                                       ` 符永涛
2013-04-15 13:36                                         ` 符永涛
2013-04-15 13:45                                           ` 符永涛
2013-04-15 13:57                                             ` Eric Sandeen
2013-04-15 14:21                                               ` 符永涛
2013-04-15 15:24                                                 ` 符永涛
2013-04-15 19:34                                                 ` Eric Sandeen
2013-04-15 14:13                                       ` Brian Foster
2013-04-12  5:23                     ` 符永涛
2013-04-09 22:16   ` Michael L. Semon
2013-04-09 22:18     ` Eric Sandeen
2013-04-09 22:48       ` Ben Myers
2013-04-09 23:30         ` Dave Chinner
2013-04-09 15:06 ` Eric Sandeen
2013-04-09 15:18   ` 符永涛
2013-04-09 15:23     ` Eric Sandeen
2013-04-09 15:25       ` 符永涛
2013-04-09 15:23     ` 符永涛
2013-04-09 15:44       ` Eric Sandeen
2013-04-09 15:48         ` 符永涛
2013-04-09 15:49           ` 符永涛
2013-04-09 15:58           ` Brian Foster
2013-04-09 17:10     ` Eric Sandeen
2013-04-10  5:34       ` 符永涛
2013-04-10  5:36         ` 符永涛

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5167F9FF.40800@redhat.com \
    --to=bfoster@redhat.com \
    --cc=bpm@sgi.com \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.com \
    --cc=yongtaofu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox