Following my request below. Can anyone point me in the right direction to help me debug this?
I'm concerned that once the kernel upgrade bug is fixed I will be forced onto the new kernel and have two broken servers. Thanks Jason -----Original Message----- Sent: 21 October 2012 15:58 To: [email protected] Subject: [BlueOnyx:11567] Serious issues with Kernel 2.6.32-279.11.1.el6 Serious issues with Kernel 2.6.32-279.11.1.el6 on two different servers If anyone can help I would be most appreciative. Currently running: 5107R Kernel Version: 2.6.32-279.9.1.el6.i686 (SMP) i686 As a Hyper-V virtual guest with MS Hyper-V components installed (Linux Integration Services Version 3.4 for Hyper-V) At the moment 5107R still has the kernel upgrade bug where a kernel upgrade does not take effect unless you manually change /boot/grub/grub.conf So I noticed that Kernel 2.6.32-279.11.1.el6 had been installed and thus I edited /boot/grub/grub.conf in 3 places to use this new Kernel. Booting into the Kernel works and the server becomes responsive on the network for a few seconds then something major crashes and takes the server down. The console shows all sorts of strange output but the last two lines are: [<c052e0a1>] ? sys_read+0x41/0x70 [<c0409a9f>] ? sysenter_do_call+0x12/0x28 A screenshot of the console output is here: http://www2.ozin.com/boot.png I can't see anything particular in dmesg but if you want to take a look it is here: http://www2.ozin.com/dmesg.txt Editing /boot/grub/grub.conf to use 2.6.32-279.9.1.el6.i686 (SMP) i686 fixes the issue so it seems to be something about this new Kernel. Any ideas where I should start looking? Thanks in advance Jason _______________________________________________ Blueonyx mailing list [email protected] http://mail.blueonyx.it/mailman/listinfo/blueonyx
