All of lore.kernel.org
 help / color / mirror / Atom feed
From: Atom2 <ariel.atom2@web2web.at>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Doug Goldstein <cardoe@cardoe.com>,
	xen-devel@lists.xen.org
Subject: Re: HVM domains crash after upgrade from XEN 4.5.1 to 4.5.2
Date: Fri, 27 Nov 2015 23:51:52 +0100	[thread overview]
Message-ID: <5658DE88.1060104@web2web.at> (raw)
In-Reply-To: <56544D5E02000078000B851F@prv-mh.provo.novell.com>

Am 24.11.15 um 11:43 schrieb Jan Beulich:
> Taking a random object out of that log, I can't see any non-standard
> option passed to the compiler, so I have to assume this is its default
> behavior (i.e. determined at build time, or established by extra
> patches). Did you check the result of a random, non-trivial C file from
> other than the Xen tree?
Hi Jan,
today I update a few packages like net-tools, curl, lipcre, and python 
and none of these packages did have any strange compiler options. It 
appeared that actually all had "-march=native -O2 -pipe 
-fomit-frame-pointer" which is the globally defined standard on my 
system and thus fully expected. A few obviously had package specific 
additions (i.e. python added -fPIC -fwrapv), but nothing really strange 
in my view.

Any more information you require or would you want to see any such build 
log for yourself?

Thanks Atom2

  reply	other threads:[~2015-11-27 22:51 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12  1:08 HVM domains crash after upgrade from XEN 4.5.1 to 4.5.2 Atom2
2015-11-12 12:52 ` Jan Beulich
2015-11-12 13:01   ` Andrew Cooper
2015-11-12 14:29     ` Atom2
2015-11-12 15:32       ` Jan Beulich
2015-11-12 16:43       ` Andrew Cooper
2015-11-12 23:00         ` Atom2
2015-11-13  7:25           ` Jan Beulich
2015-11-13 10:09             ` Andrew Cooper
2015-11-14  0:16               ` Atom2
2015-11-14 20:32                 ` Andrew Cooper
2015-11-15  0:14                   ` Atom2
2015-11-15 15:12                     ` Andrew Cooper
2015-11-16  0:39                       ` Atom2
2015-11-16 10:02                         ` Andrew Cooper
2015-11-15 20:12                     ` Doug Goldstein
2015-11-16  1:05                       ` Atom2
2015-11-16 15:31                         ` Konrad Rzeszutek Wilk
2015-11-16 19:16                           ` Atom2
2015-11-16 19:25                             ` Konrad Rzeszutek Wilk
2015-11-16 19:39                               ` Doug Goldstein
2015-11-16 19:47                                 ` Konrad Rzeszutek Wilk
2015-11-16 19:45                               ` Atom2
2015-11-16 23:01                             ` Andrew Cooper
2015-11-16 23:10                               ` Atom2
2015-11-18 22:51                                 ` Atom2
2015-11-18 23:17                                   ` Andrew Cooper
2015-11-19  0:31                                     ` Atom2
2015-11-19  1:06                                       ` Andrew Cooper
2015-11-19 20:02                                         ` Atom2
2015-11-19 23:53                                           ` Andrew Cooper
2015-11-24 11:53                                             ` Atom2
2015-11-19 10:24                                     ` Jan Beulich
2015-11-19 10:38                                       ` Andrew Cooper
2015-11-19 19:51                                         ` Atom2
2015-11-20  7:57                                           ` Jan Beulich
2015-11-24 10:32                                             ` Atom2
2015-11-24 10:43                                               ` Jan Beulich
2015-11-27 22:51                                                 ` Atom2 [this message]
2015-11-30  9:04                                                   ` Jan Beulich
2015-11-16 19:47                         ` Doug Goldstein
2015-11-16 20:14                           ` Atom2
2015-11-12 14:12   ` Atom2

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=5658DE88.1060104@web2web.at \
    --to=ariel.atom2@web2web.at \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=xen-devel@lists.xen.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 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.