tags 403614 + confirmed merge 403614 367629 thanks Hi Ingo,
> Addition: a short test on another Xen box (i386) shows the same behaviour, > so this doesn't seem to be restricted to amd64. After some debugging, this looks like a memory management error in ip-mib code. It looks like an container entry is freed, but still used in another container. As soon as the memory is reused, the entry is corrupted and accessing the second container will cause a crash. I'll check how to fix this (maybe by using some updated mib code from upstream). Thanks, Jochen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
