All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>,
	nikola.ciprich@linuxbox.cz, krucina@linuxbox.cz
Subject: Re: applications running in KVM crashing?
Date: Wed, 14 Jul 2010 11:45:53 +0200	[thread overview]
Message-ID: <20100714094553.GA10153@develbox.linuxbox.cz> (raw)
In-Reply-To: <20100609121800.GA5390@develbox.linuxbox.cz>

On Wed, Jun 09, 2010 at 02:18:00PM +0200, Nikola Ciprich wrote:
> > backtrace / disassembly of the failing instructions will help.  Do
> > the failures always occur in the same ip or random ips?

Hello Avi,
FINALLY I got another crash, so I can provide proper backtrace.
[1170486.891280] postmaster[3594] trap invalid opcode ip:7f6391472273 sp:7fff48ce2158 error:0 in libpthread-2.5.so[7f6391468000+16000]

bt full:

Core was generated by `/usr/bin/postmaster -p 5432 -D /home/pgsql/data'.
Program terminated with signal 4, Illegal instruction.
#0  0x00007f6391472273 in pthread_rwlock_rdlock () from /lib64/libpthread.so.0
#0  0x00007f6391472273 in pthread_rwlock_rdlock () from /lib64/libpthread.so.0
No symbol table info available.
#1  0x00007f6392bde166 in __dcigettext (domainname=0x0, msgid1=0x7a5bf4 "server process", msgid2=0x0, plural=0, n=0, category=5)
    at dcigettext.c:452
        domain = <value optimized out>
        binding = <value optimized out>
        categoryname = <value optimized out>
        categoryvalue = <value optimized out>
        dirname = <value optimized out>
        xdomainname = <value optimized out>
        single_locale = <value optimized out>
        retval = 0x0
        retlen = <value optimized out>
        saved_errno = <value optimized out>
        search = <value optimized out>
        foundp = 0x0
        msgid_len = 6836378
        localename = <value optimized out>
        domainname_len = <value optimized out>
        tree_lock = {__data = {__lock = 0, __nr_readers = 0, __readers_wakeup = 0, __writer_wakeup = 0, __nr_readers_queued = 0,
            __nr_writers_queued = 0, __writer = 0, __shared = 0, __pad1 = 0, __pad2 = 0, __flags = 0},
          __size = '\000' <repeats 55 times>, __align = 0}
#2  0x00000000005b2bbc in CleanupBackend (postgres_signal_arg=<value optimized out>) at postmaster.c:2490
No locals.
#3  reaper (postgres_signal_arg=<value optimized out>) at postmaster.c:2463
        save_errno = 4
        pid = 3545
        exitstatus = 0
        status = 0
        __func__ = "reaper"
#4  <signal handler called>
No symbol table info available.
#5  0x00007f6392c7ffa3 in __select_nocancel () from /lib64/libc.so.6
No symbol table info available.
#6  0x00000000005b02f7 in ServerLoop () at postmaster.c:1347
        timeout = {tv_sec = 59, tv_usec = 32718}
        rmask = {fds_bits = {56, 0 <repeats 15 times>}}
        selres = <value optimized out>
        readmask = {fds_bits = {56, 0 <repeats 15 times>}}
        nSockets = 6
        now = 1279098771
        last_touch_time = 1279097691
        __func__ = "ServerLoop"
#7  0x00000000005b18ac in PostmasterMain (argc=5, argv=0x1bac9d0) at postmaster.c:1040
        opt = <value optimized out>
        status = <value optimized out>
        userDoption = <value optimized out>
        __func__ = "PostmasterMain"
#8  0x000000000055f56e in main (argc=5, argv=<value optimized out>) at main.c:188
No locals.


I'm not sure if this is exactly what You need, so please feel free to demand further information.
I've got corefile here, so hopefully I can dig more from gdb if You need (and tell me what to do).
have a nice day!
nik

> 
> > 
> > -- 
> > error compiling committee.c: too many arguments to function
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> 
> -- 
> -------------------------------------
> Ing. Nikola CIPRICH
> LinuxBox.cz, s.r.o.
> 28. rijna 168, 709 01 Ostrava
> 
> tel.:   +420 596 603 142
> fax:    +420 596 621 273
> mobil:  +420 777 093 799
> www.linuxbox.cz
> 
> mobil servis: +420 737 238 656
> email servis: servis@linuxbox.cz
> -------------------------------------
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799
www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

  reply	other threads:[~2010-07-14  9:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09  4:14 applications running in KVM crashing? Nikola Ciprich
2010-06-09 12:00 ` Avi Kivity
2010-06-09 12:18   ` Nikola Ciprich
2010-07-14  9:45     ` Nikola Ciprich [this message]
2010-07-14 12:51       ` Avi Kivity
2010-07-14 13:41         ` Nikola Ciprich
2010-07-14 14:00           ` Avi Kivity
2010-07-14 14:32             ` Nikola Ciprich
2010-07-14 14:01           ` Gleb Natapov
2010-07-14 14:16             ` Nikola Ciprich
2010-07-14 14:26               ` Gleb Natapov

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=20100714094553.GA10153@develbox.linuxbox.cz \
    --to=extmaillist@linuxbox.cz \
    --cc=avi@redhat.com \
    --cc=krucina@linuxbox.cz \
    --cc=kvm@vger.kernel.org \
    --cc=nikola.ciprich@linuxbox.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.