All of lore.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <joe@tmsusa.com>
To: Joshua Kwan <joshk@triplehelix.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Bug: slab corruption in 2.5.67-mm1
Date: Sat, 12 Apr 2003 16:47:35 -0700	[thread overview]
Message-ID: <3E98A597.6000507@tmsusa.com> (raw)
In-Reply-To: 20030412232425.GA24920@triplehelix.org

Joshua Kwan wrote:

>On Sat, Apr 12, 2003 at 03:05:22PM -0700, J Sloan wrote:
>  
>
>>I had run 2.5.67-mm1 for some days and for
>>the most part it ran well in it's duties as dns,
>>squid, vpn/firewall and postfix server, with
>>the only oddity being the ide messages which
>>I reported earlier.
>>    
>>
>
>You're insane running a -mm kernel on a production machine, IMHO.
>
Oh please.

This is my network, and there is nothing
insane about it - FYI the stock 2.4.18 RH
kernel had severe stability problems on
this system - OTOH 2.5.67-mm1 is like
the rock of gibraltar in comparison.

:-)

>They're good for desktop use but in my experience anything that needs to
>stay up for more than a few days should at LEAST use one of the
>stability-oriented patches like -mjb or -osdl, if not the vanilla
>kernel.
>
Sorry,  -mm fixes a number of bugs that
render the vanilla kernel unusable for me.

>2.5-mm typically goes nuts with such errors as you described after a
>few days of uptime, as far as I've seen and noticed. These bugs will
>probably eventually be fixed, but at this time, it's still unstable.
>
By running 2.5 and reporting, maybe we
can help expose those bugs - but since .65
or so, I haven't really seen any show stopper
issues - everything works, and works well,
on my particular hardware, and workload.

>
>I wouldn't run anything above 2.4.20 on a box that does what you
>describe..
>  
>
My clients get official vendor kernels, but
in the sanctity of my own domain I run the
latest and greatest and take a look at what's
coming - what I'm running today is a sneak
preview of what my clients will be running
tomorrow.

Joe


  reply	other threads:[~2003-04-12 23:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-12 22:05 Bug: slab corruption in 2.5.67-mm1 J Sloan
2003-04-12 23:24 ` Joshua Kwan
2003-04-12 23:47   ` J Sloan [this message]
2003-04-13  1:18 ` Andrew Morton
2003-04-14 17:01   ` Szonyi Calin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E98A597.6000507@tmsusa.com \
    --to=joe@tmsusa.com \
    --cc=joshk@triplehelix.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.