public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Darryl Dixon - Winterhouse Consulting" <darryl.dixon@winterhouseconsulting.com>
To: systemtap@sourceware.org
Subject: Re: Assertion failed in offline.c for scsi tapset
Date: Thu, 29 Nov 2007 03:12:00 -0000	[thread overview]
Message-ID: <37952.203.97.62.217.1196305946.squirrel@services.directender.co.nz> (raw)
In-Reply-To: <55872.203.97.62.217.1196290608.squirrel@services.directender.co.nz>

> Hi All,
>
> Running RHEL5 and attempting to invoke the scsi.stp library at
> /usr/share/systemtap/tapset/scsi.stp with a simple empty script generates
> an Assertion error:
> [root@box ~]# stap -ve "probe scsi.iodone {}"
> Pass 1: parsed user script and 53 library script(s) in 190usr/0sys/200real
> ms.
> stap: offline.c:78: dwfl_offline_section_address: Assertion
> `main_shdr->sh_flags == shdr->sh_flags' failed.
> Aborted
>
> Info about this install:
> [root@box ~]# rpm -qa "*systemt*"
> systemtap-0.5.12-1.el5
> systemtap-runtime-0.5.12-1.el5
> [root@box ~]# rpm -qa "*kernel*"
> kernel-2.6.18-8.el5
> kernel-debuginfo-2.6.18-8.el5
> kernel-headers-2.6.18-8.el5
> kernel-devel-2.6.18-8.el5
> kernel-debuginfo-common-2.6.18-8.el5
[...snip...]

Ok,

Further info, I believe I may have managed to answer my own question on
this one with the help of some good'ol'fashioned strace. Running:
strace -f stap -ve 'probe scsi.iodone{}'
shows:
[...many lines of output snipped...]
fcntl(4, F_GETFL)                       = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(4, {st_mode=S_IFREG|0744, st_size=370632, ...}) = 0
mmap(NULL, 370632, PROT_READ|PROT_WRITE, MAP_PRIVATE, 4, 0) = 0x2aaabda11000
close(4)                                = 0
open("/lib/modules/2.6.18-8.el5/kernel/drivers/scsi/qla2xxx/qla2xxx.ko.debug",
O_RDONLY) = -1 ENOENT (No such file or directory)
open("/lib/modules/2.6.18-8.el5/kernel/drivers/scsi/qla2xxx/.debug/qla2xxx.ko.debug",
O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/lib/debug/lib/modules/2.6.18-8.el5/kernel/drivers/scsi/qla2xxx/qla2xxx.ko.debug",
O_RDONLY) = 4
fcntl(4, F_GETFL)                       = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(4, {st_mode=S_IFREG|0744, st_size=2193280, ...}) = 0
mmap(NULL, 2193280, PROT_READ|PROT_WRITE, MAP_PRIVATE, 4, 0) = 0x2aaabda6c000
write(2, "stap: offline.c:78: dwfl_offline"..., 108stap: offline.c:78:
dwfl_offline_section_address: Assertion `main_shdr->sh_flags ==
shdr->sh_flags' failed.
) = 108
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
tgkill(1123, 1123, SIGABRT)             = 0
--- SIGABRT (Aborted) @ 0 (0) ---
+++ killed by SIGABRT +++
Process 1123 detached

Which reminded me that we are using a qla2xxx driver supplied by HP,
rather than the stock RHEL qla2xxx... I doubt that HP will supply
debuginfo in a hurry, so I will probably migrate back to the stock RHEL
qla2xxx module temporarily, and see if I get some better results.

thanks list :)

regards,
Darryl Dixon
Winterhouse Consulting Ltd
http://www.winterhouseconsulting.com

      reply	other threads:[~2007-11-29  3:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28 22:57 Darryl Dixon - Winterhouse Consulting
2007-11-29  3:12 ` Darryl Dixon - Winterhouse Consulting [this message]

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=37952.203.97.62.217.1196305946.squirrel@services.directender.co.nz \
    --to=darryl.dixon@winterhouseconsulting.com \
    --cc=systemtap@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).