Bug #4876
closed
proper naming / identification of NS-VC FSMs
Added by laforge over 3 years ago.
Updated about 3 years ago.
Description
I have a system with many NS-VCs. I'm seeing:
<0024> gprs_ns2_vc_fsm.c:692 GPRS-NS2-VC[0x612000001720]{UNBLOCKED}: Received Event UNBLOCK_ACK
<0024> gprs_ns2_vc_fsm.c:692 GPRS-NS2-VC[0x612000001720]{UNBLOCKED}: Event UNBLOCK_ACK not permitted
and the log output gives me no kind of context which NS-VC that relates to. I would expect to see the NSE and the NSVCI of the lelated NS-VC. I don't care about the memory address.
- Status changed from New to In Progress
- Assignee changed from lynxis to laforge
- Priority changed from High to Urgent
- % Done changed from 0 to 90
<0024> gprs_ns2_vc_fsm.c:692 GPRS-NS2-VC(FR-hdlcnet1-DLCI16-NSEI1-NSVCI1)[0x6120000018a0]{BLOCKED}: Received Event UNBLOCK_ACK
<0024> gprs_ns2_vc_fsm.c:306 GPRS-NS2-VC(FR-hdlcnet1-DLCI16-NSEI1-NSVCI1)[0x6120000018a0]{BLOCKED}: state_chg to UNBLOCKED
- Status changed from In Progress to Stalled
- Status changed from Stalled to Feedback
remaining FIXME in patch has been addressed; patch is waiting for review.
- Status changed from Feedback to Resolved
- % Done changed from 90 to 100
patch was merged 2 months ago.
Also available in: Atom
PDF
