Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Han Pingtian <hanpt@linux.vnet.ibm.com>
Cc: Erwan Velu <erwan@enovance.com>, fio@vger.kernel.org
Subject: Re: segmentation fault on power system
Date: Fri, 09 Aug 2013 09:02:59 -0600	[thread overview]
Message-ID: <520504A3.7070505@kernel.dk> (raw)
In-Reply-To: <20130809083905.GA9877@localhost.localdomain>

On 08/09/2013 02:39 AM, Han Pingtian wrote:
> On Thu, Jul 25, 2013 at 08:34:41AM -0600, Jens Axboe wrote:
>> On 07/24/2013 12:21 AM, Han Pingtian wrote:
>>> I think I have found what's wrong. After 'make distclean' then 'make',
>>> the problem of segfault has gone. There were some object files 
>>> compiled on another machine. The recompilation fixed it. But looks like
>>> the ATBU call dosen't work on power7 system.
>>
>> So the recompilation fixed the segfault, but not the illegal instruction
>> due to ATBU?
> 
> Yes. If we set unlimit core dump, fio will generate a core with 
> backtrace like this one:
> 
> #0  mfspr (envp=<value optimized out>) at arch/arch-ppc.h:55
> 55              asm volatile("mfspr %0,%1": "=r" (val) : "K" (reg));
> Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.107.el6.ppc64 libaio-0.3.107-10.el6.ppc64
> (gdb) bt
> #0  mfspr (envp=<value optimized out>) at arch/arch-ppc.h:55
> #1  get_cpu_clock (envp=<value optimized out>) at arch/arch-ppc.h:71
> #2  atb_child (envp=<value optimized out>) at arch/arch-ppc.h:88
> #3  atb_clocktest (envp=<value optimized out>) at arch/arch-ppc.h:98
> #4  arch_init (envp=<value optimized out>) at arch/arch-ppc.h:116
> #5  initialize_fio (envp=<value optimized out>) at libfio.c:248
> #6  0x0000000010067294 in main (argc=<value optimized out>, argv=<value optimized out>,
>     envp=<value optimized out>) at fio.c:33
> 
> 
> Apologize for late to reply.

Alright, I'll have PPC default to the normal clock until we can improve
and detect this properly.

-- 
Jens Axboe


  reply	other threads:[~2013-08-09 15:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23 10:13 segmentation fault on power system Han Pingtian
2013-07-23 10:23 ` Erwan Velu
2013-07-23 15:15   ` Jens Axboe
2013-07-24  2:10     ` Han Pingtian
2013-07-24  6:21       ` Han Pingtian
2013-07-25 14:34         ` Jens Axboe
2013-08-09  8:39           ` Han Pingtian
2013-08-09 15:02             ` Jens Axboe [this message]
2013-07-24  1:40   ` Han Pingtian
  -- strict thread matches above, loose matches on Subject: below --
2013-10-10  6:30 Saritha Vinod
2013-10-11 16:28 ` Jens Axboe

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=520504A3.7070505@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=erwan@enovance.com \
    --cc=fio@vger.kernel.org \
    --cc=hanpt@linux.vnet.ibm.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