Ok so I created a new node at Jun 29 18:08:06 UTC and at Jun 30 18:47:24 UTC the clock froze, this is without the changed clocksource.

I've changed the clocksource and will report back if it crashes.

Please note that for now I've reverted the "Latest Paravirt" entries to point back to 2.6.32. You'll need to select 2.6.34 specifically.

-Chris

I'm testing on 2.6.33 since that's the one I know I have issues on, I have it selected. "2.6.33-linode24"

07:13:33 up 4 days

That's with the change of clocksource, seems to be doing better. Anyone else had success/problems with tsc?

2.6.34-linode26, now up 17 days. (I had switched to the TSC clocksource on day 11 as per my earlier post in this thread.) No issues beyond my lighttpd process dying this morning, but I think that's entirely unrelated, and was solved without a reboot.

Good to hear that switching to tsc might be a solution!

It's still up

21:29:09 up 5 days, 1:37, 1 user, load average: 0.08, 0.02, 0.01

I've never had uptime that long on that kernel before so I'd say tsc seems to fix it.

Now it's up to the linode guys to figure out why!

Btw, I'm curious... is the tsc clocksource based on the RDTSC CPU instruction?

As what will hopefully be a conclusion to this thread:

2.6.34-linode26, now up 32 days. (I had switched to the TSC clocksource on day 11 as per my earlier post in this thread.)

Summary for those just joining this thread:
* use 2.6.34-linode26
* set clocksource to tsc
seems to avoid this issue!

2.6.34-linode27 solves another related issue, which might be even more stable for you.

_________________
Disclaimer: I am no longer employed by Linode; opinions are my own alone.

The correct fix is to run our "Latest 2.6 Paravirt" kernel - as you'll always get the latest and greatest working kernel.

Hard coding a specific kernel version in your config profile is just asking for trouble down the road.

-Chris

Hi guys.

Is there any progress when one can expect the "Latest 2.6 Paravirt" entry to point to a recent 32bit kernel? I've seen that you're already up to 2.6.35 for the x86_64 kernels. One _could_ run this on a 32bit system as well if carefully deployed but I'd rather avoid that.

Any update would be great.

Thanks a lot,
matthew

2.6.32 is a reasonably recent kernel. Is there something you need from a newer kernel?

Hi.

My main and only concern is security. There are is unfortunately too little official documentation/feedback from Linode about how they maintain their kernels wrt to security leaks.

I could naturally fight myself through countless git backlogs, security reports and so on to see if their 2.6.32.16 based kernel is reasonably safe or if there are open issues. But I honestly lack the time and I don't think that would be my job to do as I am not the maintainer of those kernels.

Don't get me wrong, I love Linode and I think their service is simply fabulous. It's just that I would like to get more insight on their kernel maintenance and see where we stand wrt to security. That's all.

So long,
matthew

Well, it doesn't look like the linode kernel has had any updates whatsoever in the better part of a year. Surely there's been vulnerabilities in the past 8 months...