Hello,
On 12.03.2015 19:17, Oleg Nesterov wrote:
> On 03/12, Philipp Hahn wrote:
>>
>> Have you seen any other corruption
>
> No,
>
>> or is one of your patches likely to
>> fix something like the issue mentioned above:
>
> I am not sure I even understand the problem above ;) I mean, after the q
On 03/12, Philipp Hahn wrote:
>
> Have you seen any other corruption
No,
> or is one of your patches likely to
> fix something like the issue mentioned above:
I am not sure I even understand the problem above ;) I mean, after the quick
look I do not see how this connects to FPU. $rdi == 2 looks
Hello,
On 06.01.2015 08:19, Philipp Hahn wrote:
> On 19.12.2014 13:36, Philipp Hahn wrote:
>> On 18.12.2014 11:17, Ian Campbell wrote:
>>> On Tue, 2014-12-16 at 16:13 +, Frediano Ziglio wrote:
Do we have a bug in Xen that affect SSE instructions (possibly already
fixed after Philipp
Hello,
happy new year to everyone.
On 19.12.2014 13:36, Philipp Hahn wrote:
> On 18.12.2014 11:17, Ian Campbell wrote:
>> On Tue, 2014-12-16 at 16:13 +, Frediano Ziglio wrote:
>>> Do we have a bug in Xen that affect SSE instructions (possibly already
>>> fixed after Philipp version) ?
>>
>> I
On Thu, Dec 18, 2014 at 10:25:15AM +, David Vrabel wrote:
> On 18/12/14 10:17, Ian Campbell wrote:
> > On Tue, 2014-12-16 at 16:13 +, Frediano Ziglio wrote:
> >> Do we have a bug in Xen that affect SSE instructions (possibly already
> >> fixed after Philipp version) ?
> >
> > I've had a ni
Hello Ian,
On 18.12.2014 11:17, Ian Campbell wrote:
> On Tue, 2014-12-16 at 16:13 +, Frediano Ziglio wrote:
>> Do we have a bug in Xen that affect SSE instructions (possibly already
>> fixed after Philipp version) ?
>
> I've had a niggling feeling of Deja Vu over this which I'd been putting
>
On Thu, 2014-12-18 at 10:49 +, Jan Beulich wrote:
> >>> On 18.12.14 at 11:17, wrote:
> > On Tue, 2014-12-16 at 16:13 +, Frediano Ziglio wrote:
> >> Do we have a bug in Xen that affect SSE instructions (possibly already
> >> fixed after Philipp version) ?
> >
> > I've had a niggling feelin
>>> On 18.12.14 at 11:17, wrote:
> On Tue, 2014-12-16 at 16:13 +, Frediano Ziglio wrote:
>> Do we have a bug in Xen that affect SSE instructions (possibly already
>> fixed after Philipp version) ?
>
> I've had a niggling feeling of Deja Vu over this which I'd been putting
> down to an old Xen
On 18/12/14 10:17, Ian Campbell wrote:
> On Tue, 2014-12-16 at 16:13 +, Frediano Ziglio wrote:
>> Do we have a bug in Xen that affect SSE instructions (possibly already
>> fixed after Philipp version) ?
>
> I've had a niggling feeling of Deja Vu over this which I'd been putting
> down to an ol
Hello,
On 17.12.2014 10:14, Frediano Ziglio wrote:
> 2014-12-16 16:44 GMT+00:00 Frediano Ziglio :
>> 2014-12-16 16:23 GMT+00:00 Ian Campbell :
...
>> First we (I'll try when I reach home) can check if memset in glibc (or
>> the version called from talloc_zero) can use SSE. A possible dmesg
>> outp
On Tue, 2014-12-16 at 16:13 +, Frediano Ziglio wrote:
> Do we have a bug in Xen that affect SSE instructions (possibly already
> fixed after Philipp version) ?
I've had a niggling feeling of Deja Vu over this which I'd been putting
down to an old Xen on ARM bug in the area of FPU register swit
2014-12-16 16:44 GMT+00:00 Frediano Ziglio :
> 2014-12-16 16:23 GMT+00:00 Ian Campbell :
>> On Tue, 2014-12-16 at 16:13 +, Frediano Ziglio wrote:
>>> What does "info all-registers" gdb command say about SSE registers?
>>
>> All zeroes. No ffs anywhere.
>>
>
> Could be that core does not dump th
2014-12-16 16:23 GMT+00:00 Ian Campbell :
> On Tue, 2014-12-16 at 16:13 +, Frediano Ziglio wrote:
>> What does "info all-registers" gdb command say about SSE registers?
>
> All zeroes. No ffs anywhere.
>
Could be that core does not dump these registers for some reasons? On
my machine I got som
On Tue, 2014-12-16 at 16:13 +, Frediano Ziglio wrote:
> What does "info all-registers" gdb command say about SSE registers?
All zeroes. No ffs anywhere.
> Do we have a bug in Xen that affect SSE instructions (possibly already
> fixed after Philipp version) ?
Possibly. When this was thought t
2014-12-16 12:23 GMT+00:00 Ian Campbell :
> On Tue, 2014-12-16 at 11:30 +, Frediano Ziglio wrote:
>> 2014-12-16 11:06 GMT+00:00 Ian Campbell :
>> > On Tue, 2014-12-16 at 10:45 +, Ian Campbell wrote:
>> >> On Mon, 2014-12-15 at 23:29 +0100, Philipp Hahn wrote:
>> >> > > I notice in your bugz
On Tue, 2014-12-16 at 11:30 +, Frediano Ziglio wrote:
> 2014-12-16 11:06 GMT+00:00 Ian Campbell :
> > On Tue, 2014-12-16 at 10:45 +, Ian Campbell wrote:
> >> On Mon, 2014-12-15 at 23:29 +0100, Philipp Hahn wrote:
> >> > > I notice in your bugzilla (for a different occurrence, I think):
> >>
Hello,
On 16.12.2014 11:45, Ian Campbell wrote:
> On Mon, 2014-12-15 at 23:29 +0100, Philipp Hahn wrote:
>>> I notice in your bugzilla (for a different occurrence, I think):
[2090451.721705] univention-conf[2512]: segfault at ff ip
0045e238 sp 768dfa30 error 6 in
2014-12-16 11:06 GMT+00:00 Ian Campbell :
> On Tue, 2014-12-16 at 10:45 +, Ian Campbell wrote:
>> On Mon, 2014-12-15 at 23:29 +0100, Philipp Hahn wrote:
>> > > I notice in your bugzilla (for a different occurrence, I think):
>> > >> [2090451.721705] univention-conf[2512]: segfault at ff
On Tue, 2014-12-16 at 10:45 +, Ian Campbell wrote:
> On Mon, 2014-12-15 at 23:29 +0100, Philipp Hahn wrote:
> > > I notice in your bugzilla (for a different occurrence, I think):
> > >> [2090451.721705] univention-conf[2512]: segfault at ff ip
> > >> 0045e238 sp 768dfa3
On Mon, 2014-12-15 at 23:29 +0100, Philipp Hahn wrote:
> > I notice in your bugzilla (for a different occurrence, I think):
> >> [2090451.721705] univention-conf[2512]: segfault at ff ip
> >> 0045e238 sp 768dfa30 error 6 in python2.6[40+21e000]
> >
> > Which appears to
On Mon, 2014-12-15 at 23:29 +0100, Philipp Hahn wrote:
> (gdb) print *tdb
> $1 = {name = 0x0, map_ptr = 0x0, fd = 47, map_size = 65280, read_only =
> 16711680,
> locked = 0xff00, ecode = 16711680, header = {
> magic_food =
> "\000\000\000\000\000\000\000\000\000\377\000\000\000\000\37
On Mon, 2014-12-15 at 23:29 +0100, Philipp Hahn wrote:
> Hello Ian,
>
> On 15.12.2014 18:45, Ian Campbell wrote:
> > On Mon, 2014-12-15 at 14:50 +, Ian Campbell wrote:
> >> On Mon, 2014-12-15 at 15:19 +0100, Philipp Hahn wrote:
> >>> I just noticed something strange:
> >>>
> #3 0x000
Hello Ian,
On 15.12.2014 18:45, Ian Campbell wrote:
> On Mon, 2014-12-15 at 14:50 +, Ian Campbell wrote:
>> On Mon, 2014-12-15 at 15:19 +0100, Philipp Hahn wrote:
>>> I just noticed something strange:
>>>
#3 0x0040a684 in tdb_open (name=0xff >>> 0xff out of bounds
On Mon, 2014-12-15 at 14:50 +, Ian Campbell wrote:
> On Mon, 2014-12-15 at 15:19 +0100, Philipp Hahn wrote:
> > I just noticed something strange:
> >
> > > #3 0x0040a684 in tdb_open (name=0xff > > 0xff out of bounds>, hash_size=0,
> > > tdb_flags=4254928, open_fla
On Mon, 2014-12-15 at 15:19 +0100, Philipp Hahn wrote:
> Hello Ian,
>
> On 15.12.2014 14:17, Ian Campbell wrote:
> > On Fri, 2014-12-12 at 17:58 +, Ian Campbell wrote:
> >> On Fri, 2014-12-12 at 18:20 +0100, Philipp Hahn wrote:
> >>> On 12.12.2014 17:56, Ian Campbell wrote:
> On Fri, 201
Hello Ian,
On 15.12.2014 14:17, Ian Campbell wrote:
> On Fri, 2014-12-12 at 17:58 +, Ian Campbell wrote:
>> On Fri, 2014-12-12 at 18:20 +0100, Philipp Hahn wrote:
>>> On 12.12.2014 17:56, Ian Campbell wrote:
On Fri, 2014-12-12 at 17:45 +0100, Philipp Hahn wrote:
> On 12.12.2014 17:32
On Fri, 2014-12-12 at 17:58 +, Ian Campbell wrote:
> (adding Ian J who knows a bit more about C xenstored than me...)
>
> On Fri, 2014-12-12 at 18:20 +0100, Philipp Hahn wrote:
> > Hello Ian,
> >
> > On 12.12.2014 17:56, Ian Campbell wrote:
> > > On Fri, 2014-12-12 at 17:45 +0100, Philipp Ha
(adding Ian J who knows a bit more about C xenstored than me...)
On Fri, 2014-12-12 at 18:20 +0100, Philipp Hahn wrote:
> Hello Ian,
>
> On 12.12.2014 17:56, Ian Campbell wrote:
> > On Fri, 2014-12-12 at 17:45 +0100, Philipp Hahn wrote:
> >> On 12.12.2014 17:32, Ian Campbell wrote:
> >>> On Fri,
Hello Ian,
On 12.12.2014 17:56, Ian Campbell wrote:
> On Fri, 2014-12-12 at 17:45 +0100, Philipp Hahn wrote:
>> On 12.12.2014 17:32, Ian Campbell wrote:
>>> On Fri, 2014-12-12 at 17:14 +0100, Philipp Hahn wrote:
We did enable tracing and now have the xenstored-trace.log of one crash:
It
On Fri, 2014-12-12 at 17:45 +0100, Philipp Hahn wrote:
> Hello Ian,
>
> On 12.12.2014 17:32, Ian Campbell wrote:
> > On Fri, 2014-12-12 at 17:14 +0100, Philipp Hahn wrote:
> >> We did enable tracing and now have the xenstored-trace.log of one crash:
> >> It contains 1.6 billion lines and is 83 GiB
Hello Ian,
On 12.12.2014 17:32, Ian Campbell wrote:
> On Fri, 2014-12-12 at 17:14 +0100, Philipp Hahn wrote:
>> We did enable tracing and now have the xenstored-trace.log of one crash:
>> It contains 1.6 billion lines and is 83 GiB.
>> It just shows xenstored to crash on TRANSACTION_START.
>>
>> I
On Fri, 2014-12-12 at 17:14 +0100, Philipp Hahn wrote:
> Hello,
>
> On 13.11.2014 10:12, Ian Campbell wrote:
> > On Thu, 2014-11-13 at 08:45 +0100, Philipp Hahn wrote:
> >> To me this looks like some memory corruption by some unknown code
> >> writing into some random memory space, which happens t
Hello,
On 13.11.2014 10:12, Ian Campbell wrote:
> On Thu, 2014-11-13 at 08:45 +0100, Philipp Hahn wrote:
>> To me this looks like some memory corruption by some unknown code
>> writing into some random memory space, which happens to be the tdb here.
>
> I wonder if running xenstored under valgrin
On Thu, 2014-11-13 at 08:45 +0100, Philipp Hahn wrote:
> To me this looks like some memory corruption by some unknown code
> writing into some random memory space, which happens to be the tdb here.
I wonder if running xenstored under valgrind would be useful. I think
you'd want to stop xenstored f
Hello,
for some time we observed several host where xenstored crashes. We
observed the following crash two times by now:
> #0 talloc_chunk_from_ptr (ptr=0xff00) at talloc.c:116
> 116 if ((tc->flags & ~0xF) != TALLOC_MAGIC) {
> warning: not using untrusted file
> "/root/xen-4
35 matches
Mail list logo
