On Mon, 2017-12-18 at 18:40 +0000, Thomas Patrick Downes wrote: > Is there going to be any kind of post-mortem analysis of how this > happened?
I think it would be good to do this, but it doesn't seem to be something that Debian does as a matter of course, and I'm unlikely to be the right person to lead such an analysis. It might be worth proposing this to the release team (debian-release mailing list). [...] > It would also be helpful if you clearly stated whether this (a) > affects all multi-socket systems and (b) whether it affected any > single-socket systems. Between the sample bias of bug reports > themselves and the “fog of war” neither conclusion is clear. I'm afraid I still don't have a deep enough understanding of the bug to say for sure. Given that 'numa=off' appears to be a workaround, I suspect that it is triggered by multiple NUMA nodes. That would imply that older multi-socket systems with a shared memory controller would not be affected, while some single-socket systems with multiple memory controllers would be affected. Ben. -- Ben Hutchings I say we take off; nuke the site from orbit. It's the only way to be sure.
signature.asc
Description: This is a digitally signed message part
