Displaying 11 results from an estimated 11 matches for "misorderings".
Did you mean:
misordering
2004 Jan 15
3
Voicemail Sequence Bug?
I have a user, running CVS a/o 11/23/03, who has complained about
"phantom" messages showing up days or even weeks after she has deleted them.
So I asked her to let me know when it happened again, and she called a
few minutes ago.
The directory listing below shows a listing of the
/var/spool/asterisk/voicemail/default/XXXX/Old directory, and to my
surprise the messages are indeed
2008 Dec 10
3
How to fix broken ogg/theora files
Hi there,
I haven't been on this list until now, so I wasn't aware of this problem until last night ;-) - sorry for that.
I am working on a patch for oggCut for that issue (looks good actually but I would like to do some testing befor I can release a patch.)
Normal players are not effected by the page time misordering, so I took this issue as "minor". The reason for the
2020 Jul 02
0
[PATCH 04/18] alpha: Override READ_ONCE() with barriered implementation
...t; here, otherwise alpha will again break right? Looking forward to the
> future fix you mentioned.
Yeah, sorry about that. It went missing somehow during the rebase, it seems.
> BTW, do you know any architecture where speculative execution of
> address-dependent loads can cause similar misorderings? That would be
> pretty insane though. In Alpha's case it is not speculation but rather
> the split local cache design as the docs mention. The reason I ask
> is it is pretty amusing that control-dependent loads do have such
> misordering issues due to speculative branch execution...
2008 Mar 11
1
Ordering pages by granulepos or presentation time
Hi,
I'm hacking on and off on oggmerge (from ogg-tools).
I've added support for Theora, Speex, and Kate, as well as a few other fixes
and changes.
Now, I've got an issue relating to the ordering of pages as done by oggmerge,
and the way oggz-validate tests for presentation time ordering.
oggmerge, when deciding what timestamp to assign to a page, uses the previous
page's
2020 Oct 21
2
xapian-check sorted order error
Hi,
We were running xapian-check on one of our Xapian indexes and it
returns the following error:
position:
baseB blocksize=8K items=809896869 lastblock=2090419 revision=3161
levels=3 root=2084903
Failed to check B-tree: DatabaseError: Items not in sorted order
The other tables verify without issue. It looks like our oldest backup
of this database (a month old) has the same issue. Searching and
2011 Jun 10
4
Connected Line ID
Hai,
Does anybody have problems with a wrong Connected Line ID with asterisk version 1.6
The following bug was for version 1.4, but I cannot make up if this bug is still in version 1.6
http://forums.digium.com/viewtopic.php?t=7780
In version 1.8 it is possible to change the Connected Line ID, but this isn't the case in version 1.6
Regards,
Arjan Kroon
Mobillion BV
2010 Nov 16
23
[PATCH 00/14] PV ticket locks without expanding spinlock
From: Jeremy Fitzhardinge <jeremy.fitzhardinge at citrix.com>
Hi all,
This is a revised version of the pvticket lock series.
The early part of the series is mostly unchanged: it converts the bulk
of the ticket lock code into C and makes the "small" and "large"
ticket code common. The only changes are the incorporation of various
review comments.
The latter part of
2010 Nov 16
23
[PATCH 00/14] PV ticket locks without expanding spinlock
From: Jeremy Fitzhardinge <jeremy.fitzhardinge at citrix.com>
Hi all,
This is a revised version of the pvticket lock series.
The early part of the series is mostly unchanged: it converts the bulk
of the ticket lock code into C and makes the "small" and "large"
ticket code common. The only changes are the incorporation of various
review comments.
The latter part of
2010 Nov 16
23
[PATCH 00/14] PV ticket locks without expanding spinlock
From: Jeremy Fitzhardinge <jeremy.fitzhardinge at citrix.com>
Hi all,
This is a revised version of the pvticket lock series.
The early part of the series is mostly unchanged: it converts the bulk
of the ticket lock code into C and makes the "small" and "large"
ticket code common. The only changes are the incorporation of various
review comments.
The latter part of
2020 Jun 30
32
[PATCH 00/18] Allow architectures to override __READ_ONCE()
Hi everyone,
This is the long-awaited version two of the patches I previously
posted in November last year:
https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/
I ended up parking the series while the READ_ONCE() implementation was
being overhauled, but with that merged during the recent merge window
and LTO patches being posted again [1], it was time for a refresh.
The
2020 Jun 30
32
[PATCH 00/18] Allow architectures to override __READ_ONCE()
Hi everyone,
This is the long-awaited version two of the patches I previously
posted in November last year:
https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/
I ended up parking the series while the READ_ONCE() implementation was
being overhauled, but with that merged during the recent merge window
and LTO patches being posted again [1], it was time for a refresh.
The