search for: bit2

We connected an * box with an e100p to an E1/PRI from a telco here in Italy. After we had it working perfectly the telco told us that, despite the circuit appeared to work fine, and we could place calls on it, they had an "E-bit2 alarm indication constantly on that caused the circuit to be flagged as "faulty" every time. (The E-bit indication, is an alarm sent back from us to the telco, telling them we are getting CRC-errored data from them. It should be incrementing the "Far-End SES" on their side)...

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where