On Mon, Jul 25, 2016 at 11:38:20AM +0200, Ingo Jürgensmann wrote: > On 22.07.2016 12:21, Ingo Jürgensmann wrote: > >On 22.07.2016 11:03, Ingo Jürgensmann wrote: > > > >>In the meanwhile, I activated IPv6 again on Tuesday evening and today > >>the server crashed again some minutes ago. Here's the output from > >>netconsole: > >... and the second subsequent crash: > > ... and another crash below... > > But in the meanwhile, I wonder if anyone except Andreas and I has some > interest in fixing this issue, as there were absolutely no comments or > feedback on my previous mails. Quite disappointing. :-/ >
I did skim your emails. But the oops was happening in memcpy+0x6 which indicated it came back to the origin question why would it got an exception there. Just by staring at the code doesn't get me anywhere. Without a concrete reproduction of the issue, I'm afraid I can't provide more input here. There are several moving parts: 0. Hardware 1. Xen hypervisor 2. Dom0 kernel Your report and the debian report suggested that Dom0 kernel is less likely to be the culprit because you've tried different Dom0 kernels. As for Xen, not sure if you would be up for trying a debug build from source tree. That would help provide information on whether this is a bug in Xen or not. As for hardware, it would be worth trying whether this issue happens on other hardware platform. Wei. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
