*SOLVED* 2.6.8 lifetime [message #3788] |
Thu, 15 June 2006 21:43 |
John Kelly
Messages: 97 Registered: May 2006 Location: Palmetto State
|
Member |
|
|
Since debian sarge uses a 2.6.8 kernel, I was thinking of trying to patch it with the 2.6.8 openvz patch, for use as my HN kernel.
I am uncertain about stability of the 2.6.16 or 2.6.17 kernels, and want to use 2.6.8 as long as possible. So I wonder, how much longer will the 2.6.8 openvz patch be maintained, before rebasing the openvz patch to a more recent kernel?
[Updated on: Mon, 10 July 2006 21:36] by Moderator Report message to a moderator
|
|
|
|
|
|
|
|
Re: 2.6.8 lifetime [message #3831 is a reply to message #3788] |
Tue, 20 June 2006 19:24 |
John Kelly
Messages: 97 Registered: May 2006 Location: Palmetto State
|
Member |
|
|
I used 2.6.16 openvz test kernel for several weeks with no problem. But I wanted to use openvz on a production box, so I decided to use the 2.6.8 kernel for stability.
In just a few days, the 2.6.8 openvz kernel locked my keyboard after booting, and I could not log in. So in my case, the 2.6.16 openvz test kernel proved more stable than 2.6.8.
After looking into this, I see Debian 2.6.8 patches include Alan Cox's tty locking cleanups, which conflict with 2.6.8 openvz patch. Seems you attempted some tty locking fixups too, in 2.6.8 openvz patch. Maybe that's why I had the keyboard lockup with 2.6.8.
All things considered, I will wait and see how the 2.6.16 or 2.6.17 kernels shape up, before I try again to merge the openvz patch with debian patches.
Thanks for the offer to study this, but I believe now is not the best time. Investing the time in newer kernels seems better.
|
|
|
|
Re: 2.6.8 lifetime [message #4208 is a reply to message #3841] |
Sun, 02 July 2006 20:33 |
John Kelly
Messages: 97 Registered: May 2006 Location: Palmetto State
|
Member |
|
|
dev wrote on Wed, 21 June 2006 04:05 | How did it lock the keyboard? do you use PS/2 or USB keyboard ... Yes, we have the fixes for tty locking. It should not be a problem though...
|
I attached the keyboard to a different computer, and the problem occurred there, without openvz. So it's a defective keyboard, having an intermittent problem.
Sorry for the false alarm.
|
|
|