From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-kernel@vger.kernel.org
Subject: stable? quality assurance?
Date: Sun, 11 Jul 2010 09:18:41 +0200 [thread overview]
Message-ID: <201007110918.42120.Martin@lichtvoll.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2396 bytes --]
Hi!
2.6.34 was a desaster for me: bug #15969 - patch was availble before
2.6.34 already, bug #15788, also reported with 2.6.34-rc2 already, as well
as most important two complete lockups - well maybe just X.org and radeon
KMS, I didn't start my second laptop to SSH into the locked up one - on my
ThinkPad T42. I fixed the first one with the patch, but after the lockups I
just downgraded to 2.6.33 again.
I still actually *use* my machines for something else than hunting patches
for kernel bugs and on kernel.org it is written "Latest *Stable* Kernel"
(accentuation from me). I know of the argument that one should use a
distro kernel for machines that are for production use. But frankly, does
that justify to deliver in advance known crap to the distributors? What
impact do partly grave bugs reported on bugzilla have on the release
decision?
And how about people who have their reasons - mine is TuxOnIce - to
compile their own kernels?
Well 2.6.34.1 fixed the two reported bugs and it seemed to have fixed the
freezes as well. So far so good.
Maybe it should read "prerelease of stable" for at least 2.6.34.0 on the
website. And I just again always wait for .2 or .3, as with 2.6.34.1 I
still have some problems like the hang on hibernation reported in
hang on hibernation with kernel 2.6.34.1 and TuxOnIce 3.1.1.1
on this mailing list just a moment ago. But then 2.6.33 did hang with
TuxOnIce which apparently (!) wasn't a TuxOnIce problem either, since
2.6.34 did not hang with it anymore which was a reason for me to try
2.6.34 earlier.
I am quite a bit worried about the quality of the recent kernels. Some
iterations earlier I just compiled them, partly even rc-ones which I do
not expact to be table, and they just worked. But in the recent times .0,
partly even .1 or .2 versions haven't been stable for me quite some times
already and thus they better not be advertised as such on kernel.org I
think. I am willing to risk some testing and do bug reports, but these are
still production machines, I do not have any spare test machines, and
there needs to be some balance, i.e. the kernels should basically work.
Thus I for sure will be more reluctant to upgrade in the future.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-07-11 7:18 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 7:18 Martin Steigerwald [this message]
2010-07-11 8:39 ` stable? quality assurance? Eric Dumazet
2010-07-11 14:22 ` Martin Steigerwald
2010-07-11 14:52 ` Martin Steigerwald
2010-07-11 15:58 ` William Pitcock
2010-07-11 16:34 ` Eric Dumazet
2010-07-16 6:59 ` Greg KH
2010-08-05 3:27 ` Jeremy Fitzhardinge
2010-07-11 17:04 ` Heinz Diehl
2010-07-11 13:16 ` Ted Ts'o
2010-07-11 18:02 ` Anca Emanuel
2010-07-12 6:46 ` David Newall
[not found] ` <AANLkTilGjfx9sb66qVfZn1SeFPURHUrrdE7JCrild8VX@mail.gmail.com>
2010-07-12 12:35 ` Fwd: " Marcin Letyns
2010-07-12 12:42 ` Alexey Dobriyan
[not found] ` <AANLkTik64lxDiCN-eRo3i_-cTqAvCzbaRI4EEXoD44Vj@mail.gmail.com>
2010-07-12 12:52 ` Fwd: " Marcin Letyns
2010-07-12 14:57 ` Valdis.Kletnieks
2010-07-12 15:56 ` David Newall
2010-07-12 17:48 ` Marcin Letyns
2010-07-12 18:00 ` Stefan Richter
2010-07-12 19:58 ` David Newall
2010-07-12 21:11 ` Stefan Richter
2010-07-12 21:39 ` Martin Steigerwald
2010-07-12 22:44 ` Stefan Richter
2010-07-15 7:23 ` david
2010-07-13 16:50 ` Theodore Tso
2010-07-13 20:45 ` David Newall
2010-07-14 6:33 ` Theodore Tso
2010-09-04 17:12 ` Martin Steigerwald
2010-07-11 13:56 ` Lee Mathers
2010-07-11 14:51 ` Martin Steigerwald
2010-07-11 17:22 ` Willy Tarreau
2010-07-11 21:38 ` Rafael J. Wysocki
2010-07-12 4:17 ` Willy Tarreau
2010-07-12 9:56 ` Martin Steigerwald
2010-07-12 15:43 ` Martin Steigerwald
2010-07-12 17:36 ` Willy Tarreau
2010-07-12 19:56 ` Martin Steigerwald
2010-07-12 23:03 ` Stefan Richter
2010-07-13 10:30 ` Martin Steigerwald
2010-07-15 7:32 ` david
2010-07-12 17:55 ` Stefan Richter
2010-09-04 16:38 ` Martin Steigerwald
2010-09-04 18:46 ` Ted Ts'o
2010-09-04 19:11 ` Martin Steigerwald
2010-09-04 23:23 ` Ted Ts'o
2010-09-05 7:59 ` Martin Steigerwald
2010-09-04 19:24 ` Stefan Richter
2010-09-04 19:34 ` Stefan Richter
2010-09-04 20:21 ` Martin Steigerwald
2010-09-04 22:50 ` Stefan Richter
2010-09-04 23:16 ` Ted Ts'o
2010-09-05 8:35 ` Avi Kivity
2010-09-05 9:48 ` Martin Steigerwald
2010-07-11 19:49 ` Stefan Richter
2010-07-13 11:11 ` Alejandro Riveira Fernández
2010-07-13 12:50 ` rt2x00: slow wifi with correct basic rate bitmap (was Re: stable? quality assurance?) Stefan Richter
2010-07-13 15:35 ` John W. Linville
2010-07-13 18:19 ` Alejandro Riveira Fernández
2010-07-13 18:38 ` John W. Linville
2010-07-13 19:07 ` Alejandro Riveira Fernández
2010-07-13 18:06 ` Alejandro Riveira Fernández
2010-07-13 19:18 ` Stefan Richter
2010-07-12 19:46 ` stable? quality assurance? Nix
[not found] ` <AANLkTimEdVsmIgXBbmhsq75ElQvGAI8avsM8-wlDpm4z@mail.gmail.com>
2010-07-15 9:09 ` Valeo de Vries
2010-07-16 7:00 ` Greg KH
2010-07-16 7:19 ` Justin P. Mattock
2010-07-16 15:25 ` Randy Dunlap
2010-07-16 15:34 ` Valeo de Vries
-- strict thread matches above, loose matches on Subject: below --
2010-09-04 16:42 Martin Steigerwald
2010-09-04 17:22 ` Willy Tarreau
2010-09-04 19:33 ` Martin Steigerwald
2010-09-04 20:19 ` Willy Tarreau
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=201007110918.42120.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--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