search for: misord

Displaying 11 results from an estimated 11 matches for "misord".

Did you mean: minord
2004 Jan 15
3
Voicemail Sequence Bug?
...wing 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 misordered. I assume this is a bug, can't find anything on it on the bugtracker, but wonder if anyone else knows anything about this before I report it. . . Thanks. None of the files in question is empty, btw. B. msg0000.WAV msg0001.WAV msg0002.WAV msg0006.WAV msg0010.WAV msg0000.gsm msg000...
2008 Dec 10
3
How to fix broken ogg/theora files
...39;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 misordering is that oggCut works on per-packet basis. Therefor there is usually a small time offset between the audio and video. The packet are delivered to the muxer in the way they are received from the demuxer, so in some cases,...
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 exe...
2008 Mar 11
1
Ordering pages by granulepos or presentation time
...in that order. However, when oggz-validate scans this file, it doesn't know Kate is timed by start time, so will see the last packet in the Vorbis page at 0.7 seconds, and will also see the Kate event at 0.6 seconds in a subsequent page, and will then proceed to moan about it, as it sees pages misordered. Note that since the misordering happens in different streams, it is still a valid Ogg stream. There can be two ways to fix this that I can see: - change oggmerge to sort by the page's granulepos -> this will mean a less optimal ordering from a player's point of view - chang...
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
...ins in slowpath state until the last unlock happens (ie there are no more queued lockers). This code survives for a while with moderate testing, (make -j 100 on 8 VCPUs on a 4 PCPU system), but locks up after about 20 iterations, so there's still some race/deadlock in there (probably something misordered), but I think the basic approach is sound. Thanks, J Jeremy Fitzhardinge (14): x86/ticketlock: clean up types and accessors x86/ticketlock: convert spin loop to C x86/ticketlock: Use C for __ticket_spin_unlock x86/ticketlock: make large and small ticket versions of spin_lock the...
2010 Nov 16
23
[PATCH 00/14] PV ticket locks without expanding spinlock
...ins in slowpath state until the last unlock happens (ie there are no more queued lockers). This code survives for a while with moderate testing, (make -j 100 on 8 VCPUs on a 4 PCPU system), but locks up after about 20 iterations, so there's still some race/deadlock in there (probably something misordered), but I think the basic approach is sound. Thanks, J Jeremy Fitzhardinge (14): x86/ticketlock: clean up types and accessors x86/ticketlock: convert spin loop to C x86/ticketlock: Use C for __ticket_spin_unlock x86/ticketlock: make large and small ticket versions of spin_lock the...
2010 Nov 16
23
[PATCH 00/14] PV ticket locks without expanding spinlock
...ins in slowpath state until the last unlock happens (ie there are no more queued lockers). This code survives for a while with moderate testing, (make -j 100 on 8 VCPUs on a 4 PCPU system), but locks up after about 20 iterations, so there's still some race/deadlock in there (probably something misordered), but I think the basic approach is sound. Thanks, J Jeremy Fitzhardinge (14): x86/ticketlock: clean up types and accessors x86/ticketlock: convert spin loop to C x86/ticketlock: Use C for __ticket_spin_unlock x86/ticketlock: make large and small ticket versions of spin_lock 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
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