Hi Jason, On Tue, Jul 09, 2013 at 05:42:29PM +0000, Rich, Jason wrote: > Greetings, > I've recently encountered an issue where multiple hosts are failing to boot > up about 1/5 of the time. So far I have confirmed this > issue on three seperate host machines. The issue presents itself after > updating 2.6.32.39 to patch 50 and patch 61. > Both patch levels result in the failure described below. Since this occurs > on multiple hosts, I feel I can safely rule out hardware.
First, thank you for your very detailed report. Do you think you could narrow this down to a specific kernel version ? Given that there are exactly 10 versions between .39 and .50, I think that a version-level bisect would take 3 or 4 builds (so probably around 20 reboots). It would help us spot the faulty patch. Right now, there are 546 patches between .39 and .50 so it's quite hard to find the culprit, even with your full trace. That does not mean we'll immediately spot it, maybe a deeper bisect will be needed, but it should be easier. > It is also of note that I have not seen this behavior on the 3.4.26 kernel, > or on any of my 32bit hosts. This is a good news, because we're probably missing one fix from a more recent version that addressed a similar regression and that we might backport into 2.6.32.62. > That said, I have to support this software release (which runs on the 2.6 > kernel) for at least another two years. Be careful on this point, 2.6.32 is planned for EOL next year : https://www.kernel.org/category/releases.html You might want to consider migrating to a supported distro kernel or to 3.2 instead. That said, if you follow carefully the updates from later kernels, you might prefer to maintain your own backports of the patches that are relevant to your usage. Best regards, Willy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
