Hi, I am really glad it resolves this long outstanding issue. It was kind of a hunch; I spotted some discussion on this as follows with respect to a very similar kernel panic at: http://faq.aslab.com/index.php?sid=6318&lang=en&action=artikel&cat=64&id=74&artlang=en
Quote: "NUMA requires both CPU memory banks to be populated. When only one CPU memory bank is populated, the NUMA-enabled kernel will panic during boot. To fix the problem, disable NUMA by passing the kernel parameter 'numa=off' to the GRUB boot loader. " If you are want to do a kernel rebuild for your 64 bit kernel, it's probably a good idea to set: CONFIG_NUMA=n CONFIG_X86_64_ACPI_NUMA=n CONFIG_ACPI_NUMA=n CONFIG_K8_NUMA=n in debian/configs/amd64/config However, just setting the option in the boot line is a sufficient workaround to stop this problem and re-building your kernel with NUMA turned is quite a bit of effort to get the same result. Also, I have not tested with NUMA turned off as a build option, so I cannot say for 100% sure if building with NUMA disabled will work, and building a custom kernel does mean it limits what we can do to support bugs found in a custom kernel in the future. As this workaround gets the desired result I think we can move this long outstanding issue as "Fixed". Colin -- Hardy AMD64 Alpha 5 server and desktop won't boot on IBM eServer 325 https://bugs.launchpad.net/bugs/195495 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
