public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: David Smith <dsmith@redhat.com>
To: Wenji Huang <wenji.huang@oracle.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: memory1.stp failed on x86_64 2.6.31-rc6
Date: Mon, 17 Aug 2009 14:40:00 -0000	[thread overview]
Message-ID: <4A896BED.1070902@redhat.com> (raw)
In-Reply-To: <4A8926B5.4040601@oracle.com>

On 08/17/2009 04:45 AM, Wenji Huang wrote:
> Hi,
> 
> I found memory1.stp failed on x86_64 2.6.31-rc6, but works
> fine on x86_64 2.6.31-rc5 and x86 2.6.31-rc6.
> 
> $ stap -v systemtap.printf/memory1.stp
> Pass 1: parsed user script and 59 library script(s) in
> 310usr/60sys/369real ms.
> Pass 2: analyzed script: 2 probe(s), 6 function(s), 14 embed(s), 0
> global(s) in 780usr/380sys/1165real ms.
> Pass 3: translated to C into
> "/tmp/stapp5DGZt/stap_87fc0586871670d76847178631c22a98_21602.c" in
> 800usr/100sys/895real ms.
> Pass 4: compiled C into "stap_87fc0586871670d76847178631c22a98_21602.ko"
> in 8370usr/6570sys/14450real ms.
> Pass 5: starting run.
> ERROR: percpu context (size 103912) allocation failed
> Pass 5: run completed in 10usr/100sys/141real ms.
> 
> This is a VMware box with two cpus. Dmesg said,
> 
> [258068.721067] WARNING: at mm/percpu.c:786 pcpu_alloc+0x55/0x3d8()
> [258068.722067] Hardware name: VMware Virtual Platform
> [258068.723067] illegal size (103912) or align (8) for percpu allocation
... stuff deleted ...

Wenji,

Could you add this information to bug #10516?

-- 
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)

      reply	other threads:[~2009-08-17 14:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17  9:49 Wenji Huang
2009-08-17 14:40 ` David Smith [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=4A896BED.1070902@redhat.com \
    --to=dsmith@redhat.com \
    --cc=systemtap@sources.redhat.com \
    --cc=wenji.huang@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).