public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Igor Podlesny <for.poige+linux@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hi! I've noticed that kernel.org advertises 2.6.28 as "The latest stable version of the Linux kernel is".
Date: Mon, 29 Dec 2008 07:04:45 +0100	[thread overview]
Message-ID: <20081229060445.GD6800@1wt.eu> (raw)
In-Reply-To: <43d009740812282139x7597aafbn4474455c1aa1e0e8@mail.gmail.com>

On Mon, Dec 29, 2008 at 12:39:55PM +0700, Igor Podlesny wrote:
> Actually that's either a mistake or I don't know what you guys call "a
> stable version".
> 
> Since 2.6.24 there're serious regressions in all the following
> "stable" releases. Both my own experience + http://www.kerneloops.org/
> proves that.
> 
> Just to bring in some examples:
> 
> -- using 2.6.25.x I started to notice "oops"es in dmesg (what hadn't
> been happening for a long time).
> 
> -- since 2.6.26 mine desktop system can't go suspend or hibernate. It
> tries, but immediately returns from that trying.
> 
> -- Copying several rather big files (~ 25--45 GiB) from XFS on LVM-2
> on MDraid partition to another one, I had the system rebooted both
> with 2.6.28 and 2.6.27.10 (accomplished using 2.6.24.7-rt(sic!)25). As
> you probably understand, that's the case you even can't trace where's
> the problem, at least on a desktop with GUI, not on server with plain
> text display. Although, I'm afraid even text display wouldn't had a
> chance to show anything, tracing that problem.
> 
> So, I don't feel Linux is stable since 2.6.24. Do you?

Well, I won't say that I find them 100% rock solid, but you seem to be
able to reproduce a lot of serious issues. Have you filed bug reports
to get them fixed ? You cannot expect people to fix bugs they're not
aware of !

Also it would be a good idea to get all those issues fixed soon, because
2.6.27-stable will be maintained for a long time.

Willy


  reply	other threads:[~2008-12-29  6:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29  5:39 Hi! I've noticed that kernel.org advertises 2.6.28 as "The latest stable version of the Linux kernel is" Igor Podlesny
2008-12-29  6:04 ` Willy Tarreau [this message]
2008-12-29  9:21 ` Christoph Hellwig
2008-12-29 10:01   ` Igor Podlesny
2008-12-29 14:02   ` David Newall
2008-12-29 11:50 ` Éric Piel
2008-12-29 12:51   ` Paul Komkoff
2008-12-29 13:39     ` Igor Podlesny
     [not found] <fa.AyhwSGaa29qThLZ5OhBSbACDzmI@ifi.uio.no>
     [not found] ` <fa.O2INIKnSvQY5+2WFbCRxoh8xutg@ifi.uio.no>
     [not found]   ` <fa.fGgFQweuOQlZ5w9soKo4267nPkc@ifi.uio.no>
     [not found]     ` <4958AF9E.7070005@yahoo.com>
2008-12-29 11:16       ` Igor Podlesny

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=20081229060445.GD6800@1wt.eu \
    --to=w@1wt.eu \
    --cc=for.poige+linux@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox