Project

General

Profile

Actions
Copy link

Bug #6913

closed

valgrind issues when running rgw tests

Added by Tamilarasi muthamizhan over 10 years ago. Updated about 10 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
Yehuda Sadeh
Target version:
-
% Done:

0%

Source:
Q/A
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

logs: ubuntu@teuthology:/a/teuthology-2013-11-27_04:15:17-rgw-next---basic-saya/120829

2013-11-27T06:55:31.199 INFO:teuthology.orchestra.run.err:[10.214.143.127]: 2013-11-27 08:55:31.199297 b1aff470  0 -- :/1017549 >> 10.214.143.129:6789/0 pipe(0xb17023b8 sd=7 :0 s=1 pgs=0 cs=0 l=1 c=0xb1702588).fault
2013-11-27T06:55:31.958 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: disInstr(thumb): unhandled instruction: 0xEE07 0x3FBA
2013-11-27T06:55:31.958 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: ==17569== valgrind: Unrecognised instruction at address 0x4c510f.
2013-11-27T06:55:31.959 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: ==17569== Your program just tried to execute an instruction that Valgrind
2013-11-27T06:55:31.959 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: ==17569== did not recognise.  There are two possible reasons for this.
2013-11-27T06:55:31.959 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: ==17569== 1. Your program has a bug and erroneously jumped to a non-code
2013-11-27T06:55:31.959 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: ==17569==    location.  If you are running Memcheck and you just saw a
2013-11-27T06:55:31.959 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: ==17569==    warning about a bad jump, it's probably your program's fault.
2013-11-27T06:55:31.959 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: ==17569== 2. The instruction is legitimate but Valgrind doesn't handle it,
2013-11-27T06:55:31.960 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: ==17569==    i.e. it's Valgrind's fault.  If you think this is the case or
2013-11-27T06:55:31.960 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: ==17569==    you are not sure, please let us know and we'll try to fix it.
2013-11-27T06:55:31.960 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: ==17569== Either way, Valgrind will now raise a SIGILL signal which will
2013-11-27T06:55:31.960 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: ==17569== probably kill your program.
2013-11-27T06:55:32.000 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: *** Caught signal (Illegal instruction) **
2013-11-27T06:55:32.000 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]:  in thread 401d320
2013-11-27T06:55:32.121 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]: disInstr(thumb): unhandled instruction: 0xE886 0x0060
2013-11-27T06:55:32.122 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]: ==17557== valgrind: Unrecognised instruction at address 0x4bfc25f.
2013-11-27T06:55:32.122 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]: ==17557== Your program just tried to execute an instruction that Valgrind
2013-11-27T06:55:32.122 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]: ==17557== did not recognise.  There are two possible reasons for this.
2013-11-27T06:55:32.122 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]: ==17557== 1. Your program has a bug and erroneously jumped to a non-code
2013-11-27T06:55:32.123 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]: ==17557==    location.  If you are running Memcheck and you just saw a
2013-11-27T06:55:32.123 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]: ==17557==    warning about a bad jump, it's probably your program's fault.
2013-11-27T06:55:32.123 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]: ==17557== 2. The instruction is legitimate but Valgrind doesn't handle it,
2013-11-27T06:55:32.123 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]: ==17557==    i.e. it's Valgrind's fault.  If you think this is the case or
2013-11-27T06:55:32.123 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]: ==17557==    you are not sure, please let us know and we'll try to fix it.
2013-11-27T06:55:32.124 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]: ==17557== Either way, Valgrind will now raise a SIGILL signal which will
2013-11-27T06:55:32.124 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]: ==17557== probably kill your program.
2013-11-27T06:55:32.159 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]: *** Caught signal (Illegal instruction) **
2013-11-27T06:55:32.159 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]:  in thread 401cc50
2013-11-27T06:55:32.296 INFO:teuthology.task.ceph.osd.3.err:[10.214.143.129]: disInstr(thumb): unhandled instruction: 0xEE07 0x3FBA
2013-11-27T06:55:32.297 INFO:teuthology.task.ceph.osd.3.err:[10.214.143.129]: ==32717== valgrind: Unrecognised instruction at address 0x4c510f.
2013-11-27T06:55:32.298 INFO:teuthology.task.ceph.osd.3.err:[10.214.143.129]: ==32717== Your program just tried to execute an instruction that Valgrind
2013-11-27T06:55:32.298 INFO:teuthology.task.ceph.osd.3.err:[10.214.143.129]: ==32717== did not recognise.  There are two possible reasons for this.
2013-11-27T06:55:32.298 INFO:teuthology.task.ceph.osd.3.err:[10.214.143.129]: ==32717== 1. Your program has a bug and erroneously jumped to a non-code
2013-11-27T06:55:32.298 INFO:teuthology.task.ceph.osd.3.err:[10.214.143.129]: ==32717==    location.  If you are running Memcheck and you just saw a
2013-11-27T06:55:32.298 INFO:teuthology.task.ceph.osd.3.err:[10.214.143.129]: ==32717==    warning about a bad jump, it's probably your program's fault.
2013-11-27T06:55:32.298 INFO:teuthology.task.ceph.osd.3.err:[10.214.143.129]: ==32717== 2. The instruction is legitimate but Valgrind doesn't handle it,
2013-11-27T06:55:32.298 INFO:teuthology.task.ceph.osd.3.err:[10.214.143.129]: ==32717==    i.e. it's Valgrind's fault.  If you think this is the case or
2013-11-27T06:55:32.299 INFO:teuthology.task.ceph.osd.3.err:[10.214.143.129]: ==32717==    you are not su:
....

....
2013-11-27T06:55:32.339 INFO:teuthology.task.ceph.osd.3.err:[10.214.143.129]: *** Caught signal (Illegal instruction) **
2013-11-27T06:55:32.339 INFO:teuthology.task.ceph.osd.3.err:[10.214.143.129]:  in thread 401d320
2013-11-27T06:55:32.376 INFO:teuthology.task.ceph.mds.a.err:[10.214.143.129]: *** Caught signal (Illegal instruction) **
2013-11-27T06:55:32.376 INFO:teuthology.task.ceph.mds.a.err:[10.214.143.129]:  in thread 401c530
2013-11-27T06:55:32.385 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]:  ceph version 0.72-225-gff60c36 (ff60c364d3d32bff65d4f20b762c379885e7869a)
2013-11-27T06:55:32.386 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]:  1: ceph-osd() [0x45a5e6]
2013-11-27T06:55:32.386 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]:  2: (__default_sa_restorer_v2()+0) [0x4d859d0]
2013-11-27T06:55:32.386 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]:  3: (Throttle::Throttle(CephContext*, std::string, long long, bool)+0x199) [0x4c510e]
2013-11-27T06:55:32.386 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]:  4: (SimpleMessenger::SimpleMessenger(CephContext*, entity_name_t, std::string, unsigned long long)+0x29d) [0x4c01de]
2013-11-27T06:55:32.386 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]:  5: (Messenger::create(CephContext*, entity_name_t, std::string, unsigned long long)+0x51) [0x49250e]
2013-11-27T06:55:32.386 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]:  6: (main()+0xeb3) [0x2b09f4]
2013-11-27T06:55:32.386 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]:  7: (__libc_start_main()+0x99) [0x4d76f42]
2013-11-27T06:55:32.409 INFO:teuthology.task.ceph.osd.1.err:[10.214.143.127]: 2013-11-27 08:55:32.387157 

...
...
2013-11-27T06:55:32.538 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]:  ceph version 0.72-225-gff60c36 (ff60c364d3d32bff65d4f20b762c379885e7869a)
2013-11-27T06:55:32.538 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]:  1: ceph-mon() [0x37dd92]
2013-11-27T06:55:32.538 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]:  2: (__default_sa_restorer_v2()+0) [0x4d709d0]
2013-11-27T06:55:32.538 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]:  3: (leveldb::VersionSet::Recover()+0x7f1) [0x4bfc25e]
2013-11-27T06:55:32.538 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]:  4: (leveldb::DBImpl::Recover(leveldb::VersionEdit*)+0xe5) [0x4bf2e3e]
2013-11-27T06:55:32.538 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]:  5: (leveldb::DB::Open(leveldb::Options const&, std::string const&, leveldb::DB**)+0x67) [0x4bf3220]
2013-11-27T06:55:32.538 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]:  6: (LevelDBStore::init(std::ostream&, bool)+0x8f) [0x3615dc]
2013-11-27T06:55:32.538 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]:  7: (main()+0x179) [0x1c71c6]
2013-11-27T06:55:32.539 INFO:teuthology.task.ceph.mon.a.err:[10.214.143.127]:  8: (__libc_start_main()+0x99) [0x4d61f42]
2013-11-27T06:55:32.542 INFO:teuthology.task.ceph.osd.0.err:[10.214.143.127]: disInstr(thumb): unhandled instruction: 0xEE07 0x3FBA
2013-11-27T06:55:32.542 INFO:teuthology.task.ceph.osd.0.err:[10.214.143.127]: ==17563== valgrind: Unrecognised instruction at address 0x4c510f.
2013-11-27T06:55:32.543 INFO:teuthology.task.ceph.osd.0.err:[10.214.143.127]: ==17563== Your program just tried to execute an instruction that Valgrind
2013-11-27T06:55:32.543 INFO:teuthology.task.ceph.osd.0.err:[10.214.143.127]: ==17563== did not recognise.  There are two possible reasons for this.
2013-11-27T06:55:32.543 INFO:teuthology.task.ceph.osd.0.err:[10.214.143.127]: ==17563== 1. Your program has a bug and erroneously jumped to a non-code
2013-11-27T06:55:32.544 INFO:teuthology.task.ceph.osd.0.err:[10.214.143.127]: ==17563==    location.  If you are running Memcheck and you just saw a
2013-11-27T06:55:32.544 INFO:teuthology.task.ceph.osd.0.err:[10.214.143.127]: ==17563==    warning about a bad jump, it's probably your program's fault.
2013-11-27T06:55:32.544 INFO:teuthology.task.ceph.osd.0.err:[10.214.143.127]: ==17563== 2. The instruction is legitimate but Valgrind doesn't handle it,
2013-11-27T06:55:32.544 INFO:teuthology.task.ceph.osd.0.err:[10.214.143.127]: ==17563==    i.e. it's Valgrind's fault.  If you think this is the case or
2013-11-27T06:55:32.544 INFO:teuthology.task.ceph.osd.0.err:[10.214.143.127]: ==17563==    you are not sure, please let us know and we'll try to fix it

Related issues 1 (0 open — 1 closed)

Is duplicate of rgw - Bug #6801: RGW on arm: 'saw valgrind issues'RejectedYehuda Sadeh11/19/2013

Actions
Actions
Copy link
 #1

Updated by Tamilarasi muthamizhan over 10 years ago

  • Project changed from Ceph to rgw
  • Assignee set to Yehuda Sadeh
  • Source changed from other to Q/A

not sure, if it is a issue with the test or valgrind. filing this bug to just keep track of it.

Actions
Copy link
 #2

Updated by Tamilarasi muthamizhan over 10 years ago

the following one appears to be similar.

logs: ubuntu@teuthology:/a/teuthology-2013-11-27_04:15:17-rgw-next---basic-saya/120832

2013-11-27T06:47:59.792 INFO:teuthology.task.swift:Creating rgw users...
2013-11-27T06:47:59.792 DEBUG:teuthology.orchestra.run:Running [10.214.143.118]: "adjust-ulimits ceph-coverage /home/ubuntu/cephtest/archive/coverage radosgw-admin -n client.0 user create --subuser foo.client.0:foo --display-name 'Mr. foo.client.0 foo' --secret i0uzBoHd8h5loE1pGyHCA4PDXQw1J10UOFVYoONjEXQ4vLk5bC41Ig== --email foo.client.0+test@test.test --key-type swift" 
2013-11-27T06:47:59.887 INFO:teuthology.orchestra.run.err:[10.214.143.118]: 2013-11-27 08:47:59.886560 b5ba7000  0 couldn't find old data placement pools config, setting up new ones for the zone
2013-11-27T06:48:02.901 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]: 2013-11-27 08:48:02.637661 5beaa10 -1 WARNING: libcurl doesn't support curl_multi_wait()
2013-11-27T06:48:02.906 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]: 2013-11-27 08:48:02.643234 5beaa10 -1 WARNING: cross zone / region transfer performance may be affected
2013-11-27T06:48:03.996 INFO:teuthology.task.rgw.client.0.err:[10.214.143.118]: disInstr(thumb): unhandled instruction: 0xEE07 0x3FBA
2013-11-27T06:48:03.997 INFO:teuthology.task.rgw.client.0.err:[10.214.143.118]: ==4532== valgrind: Unrecognised instruction at address 0x4ac34c7.
2013-11-27T06:48:03.997 INFO:teuthology.task.rgw.client.0.err:[10.214.143.118]: ==4532== Your program just tried to execute an instruction that Valgrind
2013-11-27T06:48:03.997 INFO:teuthology.task.rgw.client.0.err:[10.214.143.118]: ==4532== did not recognise.  There are two possible reasons for this.
2013-11-27T06:48:03.997 INFO:teuthology.task.rgw.client.0.err:[10.214.143.118]: ==4532== 1. Your program has a bug and erroneously jumped to a non-code
2013-11-27T06:48:03.997 INFO:teuthology.task.rgw.client.0.err:[10.214.143.118]: ==4532==    location.  If you are running Memcheck and you just saw a
2013-11-27T06:48:03.997 INFO:teuthology.task.rgw.client.0.err:[10.214.143.118]: ==4532==    warning about a bad jump, it's probably your program's fault.
2013-11-27T06:48:03.997 INFO:teuthology.task.rgw.client.0.err:[10.214.143.118]: ==4532== 2. The instruction is legitimate but Valgrind doesn't handle it,
2013-11-27T06:48:03.998 INFO:teuthology.task.rgw.client.0.err:[10.214.143.118]: ==4532==    i.e. it's Valgrind's fault.  If you think this is the case or
2013-11-27T06:48:03.998 INFO:teuthology.task.rgw.client.0.err:[10.214.143.118]: ==4532==    you are not sure, please let us know and we'll try to fix it.
2013-11-27T06:48:03.998 INFO:teuthology.task.rgw.client.0.err:[10.214.143.118]: ==4532== Either way, Valgrind will now raise a SIGILL signal which will
2013-11-27T06:48:03.998 INFO:teuthology.task.rgw.client.0.err:[10.214.143.118]: ==4532== probably kill your program.
2013-11-27T06:48:04.006 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]: *** Caught signal (Illegal instruction) **
2013-11-27T06:48:04.006 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]:  in thread 5beaa10
2013-11-27T06:48:04.368 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]:  ceph version 0.72-225-gff60c36 (ff60c364d3d32bff65d4f20b762c379885e7869a)
2013-11-27T06:48:04.368 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]:  1: radosgw() [0x10b282]
2013-11-27T06:48:04.368 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]:  2: (__default_sa_restorer_v2()+0) [0x55cf9d0]
2013-11-27T06:48:04.368 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]:  3: (Throttle::Throttle(CephContext*, std::string, long long, bool)+0x199) [0x4ac34c6]
2013-11-27T06:48:04.368 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]:  4: (SimpleMessenger::SimpleMessenger(CephContext*, entity_name_t, std::string, unsigned long long)+0x29d) [0x4b8988e]
2013-11-27T06:48:04.368 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]:  5: (librados::RadosClient::connect()+0xbb) [0x4a60a70]
2013-11-27T06:48:04.368 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]:  6: (RGWRados::init_rados()+0x2b) [0xc0bb8]
2013-11-27T06:48:04.369 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]:  7: (RGWCache<RGWRados>::init_rados()+0xd) [0xd0ed2]
2013-11-27T06:48:04.369 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]:  8: (RGWRados::initialize()+0x9) [0xc3a2e]
2013-11-27T06:48:04.369 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]:  9: (RGWStoreManager::init_storage_provider(CephContext*, bool)+0x2b) [0xc0544]
2013-11-27T06:48:04.369 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]:  10: (main()+0x253) [0x6f648]
2013-11-27T06:48:04.369 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]:  11: (__libc_start_main()+0x99) [0x55c0f42]
2013-11-27T06:48:04.378 INFO:teuthology.task.rgw.client.0.out:[10.214.143.118]: 2013-11-27 08:48:04.368957 5beaa10 -1 *** Caught signal (Illegal instruction) **
Actions
Copy link
 #3

Updated by Tamilarasi muthamizhan over 10 years ago

logs: ubuntu@teuthology:/a/teuthology-2013-12-02_04:10:14-rgw-master---basic-saya/127068

Actions
Copy link
 #4

Updated by Sage Weil about 10 years ago

  • Status changed from New to Duplicate
Actions
Copy link

Also available in: Atom PDF