The regular behaviour of a DSL modem. It is the normal behaviour of DSL to trigger a resync to stabilise the line too.
A resync will happen if SNRM goes out of bounds; while we don't know what the bounds are, the values are defined as part of the line profile. It wouldn't be a surprise if the threshold was set to 0dB.
A resync will also occur if one ends loses track of the framing data that surrounds the user-data. If the modem loses confidence that it can even work out where the start and end of the user data lies in the bitstream, it will give up and force a resync.
When lines are being problematic, these types of resync are *much* more likely than a DLM intervention. Oh, somewhere in amongst the sequence of resyncs, you might *also* see a DLM-induced resync - as it tries to stop all the other ones from happening. I don't think your line has seen one yet - you would see INP/delay value changes.
People have a habit of looking at the resync reason code, seeing a value of 1, and assuming it means DLM. Unfortunately, it really signifies "RDI", or "remote defect indicator" ... which tells you that the DSLAM didn't like the bitstream it was receiving from you.