diff options
| author | Harald Welte <laforge@gnumonks.org> | 2010-12-24 13:06:11 +0100 |
|---|---|---|
| committer | Harald Welte <laforge@gnumonks.org> | 2010-12-24 15:42:22 +0100 |
| commit | 2cafc4b30910f244e610e4cf75f72ba360df6ace (patch) | |
| tree | ebad59bc7665d956b617a0c9185a926649a35d05 /openbsc | |
| parent | 3a3c277b70df3a09b20fa1f985b29445783959b1 (diff) | |
BSC API: Make 'Got data in non active state' message as LOGL_INFO
LOGL_ERROR will make this message shpw up in everey default log
config. However, as it seems, this is commonly observed in case
a MS still sends a MS STATUS (in respons to the MM INFO) at the
end of a location area update.
It might be best to actually change the channel release procedure
to make sure we can still pass such 'late' data to the MSC until
the time the Layer2 has been completely released.
Diffstat (limited to 'openbsc')
| -rw-r--r-- | openbsc/src/bsc_api.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/openbsc/src/bsc_api.c b/openbsc/src/bsc_api.c index 0a7c94b75..267998fa6 100644 --- a/openbsc/src/bsc_api.c +++ b/openbsc/src/bsc_api.c @@ -477,7 +477,8 @@ int gsm0408_rcvmsg(struct msgb *msg, uint8_t link_id) lchan = msg->lchan; if (lchan->state != LCHAN_S_ACTIVE) { - LOGP(DRSL, LOGL_ERROR, "Got data in non active state. discarding.\n"); + LOGP(DRSL, LOGL_INFO, "Got data in non active state(%s), " + "discarding.\n", gsm_lchans_name(lchan->state)); return -1; } |