| To: | Simon Matter <simon.matter@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Processes stuck in D state.. |
| From: | Michael Loftis <mloftis@xxxxxxxxx> |
| Date: | Wed, 06 Aug 2003 13:25:40 -0600 |
| Cc: | Gordon Henderson <gordon@xxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <38207.213.173.165.140.1060197333.squirrel@imap01.ch.sauter-bc.com> |
| References: | <3F283E36.778CC934@mvista.com><3F28E34D.3EE2CF4A@ch.sauter-bc.com> <3F2920A4.575A310A@mvista.com> <Pine.LNX.4.56.0308060851570.25677@unicorn.drogon.net> <198095225.1060163866@[10.1.2.77]> <38207.213.173.165.140.1060197333.squirrel@imap01.ch.sauter-bc.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
|
The whole redhat 2.4.20 kernel is crap. I've had a number of boxes lockup
on it. Initially it was the firewall, but then at home I've had other
boxes lock up under load with it. 2.4.20-19.x got a little better but was
still totally screwed up. Going to a stock 2.4.20 fixed all the issues
I've been having. The root of this one is IMHO RH 2.4.20 is actually 2.4.21-pre3 plus a mass of patches. --On Wednesday, August 06, 2003 21:15 +0200 Simon Matter <simon.matter@xxxxxxxxxxxxxxxx> wrote: Yah for production go with a kernel as close to stock as posible. Avoid anything by redhat in the 2.4.20 series, and you should be fine. In other words go get a fresh treee, patch in ONLY the XFS stuff. Don't put in low latency/preeempt patches, they still screw everything up. And just stay away from RedHate kernels. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Processes stuck in D state.., Simon Matter |
|---|---|
| Next by Date: | Re: Processes stuck in D state.., Simon Matter |
| Previous by Thread: | Re: Processes stuck in D state.., Simon Matter |
| Next by Thread: | Re: Processes stuck in D state.., Simon Matter |
| Indexes: | [Date] [Thread] [Top] [All Lists] |