Reliablility problem in current git?
Tim Ehlers
osmocom at ehlers.info
Mon Feb 20 19:44:21 CET 2012
On Mon, 20 Feb 2012, Jean-Pierre Szikora wrote:
Hi,
> I have the same problem (testing with a C123). When this problem occurs, I
> have also a lot of "DSP Error Status: 8" and afterwards "DSP Error Status:
> 24". With git bisect, I localize the first commit showing this issue as
> 7cc4a4b ( Improvement of neighbour cell power measurement task).
>
> Hope this help,
yes, very much. I had problems with bisect. It told me, that there are
more than 550 revisions to check and most of them where older than the bad
one... So you findings helped me to track the problem down to this:
--- mframe_sched.c 2012-02-20 19:37:42.000000000 +0100
+++ mframe_sched.c~ 2012-02-20 19:33:24.000000000 +0100
@@ -200,7 +200,11 @@
/* Measurement for MF 51 */
static const struct mframe_sched_item mf_neigh_pm51[] = {
- { .sched_set = NEIGH_PM , .modulo = 51, .frame_nr = 50 },
+ { .sched_set = NEIGH_PM , .modulo = 51, .frame_nr = 0 },
+ { .sched_set = NEIGH_PM , .modulo = 51, .frame_nr = 10 },
+ { .sched_set = NEIGH_PM , .modulo = 51, .frame_nr = 20 },
+ { .sched_set = NEIGH_PM , .modulo = 51, .frame_nr = 30 },
+ { .sched_set = NEIGH_PM , .modulo = 51, .frame_nr = 40 },
{ .sched_set = NULL }
};
in the changeset 7cc4a4b324bcf65b5d383faf2b3e727953c8df81.
Not that I would understand what this means... :)
Harald can you fix your changes with that info?
Thanks
Tim
More information about the baseband-devel
mailing list