Stable.
> > > more efficient in low mem conditions and this may well be the case you are
> > > running into. This means 2.4.17 standard + patch.
> > Is there a reasonable chance that martins patch will get mainlined
> > in the near future?
>
> I really can't know. But to me the results look interesting enough to
> give it a try on certain problem situations (like yours) to find out
> if it is any better than the stock version. If you and others can
> confirm that things get better then I have no real doubts that Marcelo
> can pick it up.
Out of ignorance and laziness, where is it again that I can get this
kernel?
> > One of the big reasons I chose to upgrade to a
> > later kernel version (from 2.4.8ac<something>+LVMpatches+...)
> was
> > to get away from having to apply patches (and document which
> > patches and where to get them etc).
>
> Well, there is really nothing wrong with upgrading mainline kernels,
Funny, I went from a working 2.4.8-ac<x> to a non-working
2.4.13+patches when I started getting these crashes. At first I
thought they were Mysql, so I called them. They said "Re-install
windows", er, I mean upgrade my kernel to 2.4.16, which would "fix
the problem", so I did, and it didn't. So they said to go to
2.4.17rc2 as that would fix my problem, only it didn't.
> as the are getting better with every release, so I would always
> suggest to take the releases up lets say a week after being out. Only
Yeah, and build a debian package, distribute it to (looks behind me)
100+ linux servers, including 6 mission critical heavily loaded DB
machines.
Not to be a complete asswipe, but no. While I like playing with
computers and all that, I don't have enough hours in the day to be
rolling out new kernels every couple weeks and still have time left
over to see my wife, shoot my guns, ride my motorcycles and drink my
scotch.
> your situation maybe can help to improve more, if you input some of
> your experiences in LKML with a patch like Martins. Feedback _is_
> required to find a solution to an existing problem.
I understand completely, I'm just trying to figure out a way to test
this that doesn't impact my site as drastically. See, we've only got
two databases that will cause this fault, and of course they are the
two most important ones, and the only way we can generate this fault
is to put them live and wait for them to crash.
> > If this is the route I have to go, I'll do it but, well, I'm
> not
> > that comfortable with it.
>
> Well, my suggestions: don't patch around too much, but try single
> patches on stock kernel and evaluate them here.
There are 2 other patches I need to apply, the first is the LVM
1.0.1 patch, and the second is the VFS-lock patch. We need these to
do snapshots. Which isn't bad, but I'm about the only one still here
who can do it (violates hit-by-a-bus rule).
-- Share and Enjoy. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/