From: dth@picard.cistron.nl (Danny ter Haar)
To: linux-kernel@vger.kernel.org
Subject: 2.6.13-rcX really this bad ?
Date: Sun, 14 Aug 2005 10:10:18 +0000 (UTC) [thread overview]
Message-ID: <ddn5aa$glm$1@news.cistron.nl> (raw)
I've posted a couple of times than my newsserver is not stable
with any 2.6.13-rcX kernels.
Last kernel that survived is 2.6.12-mm1 (18+days)
Of course i can just stick with that kernel, but i thought it would
be wise to live on the edge and run a reasonable loaded server with
the latest/greatest. This ends in disaster though...
These are last uptimes, all reset by panic on reset.
reboot system boot 2.6.13-rc6-git5 Sun Aug 14 02:56 (09:07)
reboot system boot 2.6.13-rc6-git4 Fri Aug 12 16:50 (1+19:13)
reboot system boot 2.6.13-rc6-git3 Fri Aug 12 12:32 (04:16)
reboot system boot 2.6.13-rc6-git3 Thu Aug 11 13:18 (1+03:29)
reboot system boot 2.6.13-rc6-git2 Thu Aug 11 12:40 (00:35)
reboot system boot 2.6.13-rc6-git1 Wed Aug 10 13:24 (23:52)
reboot system boot 2.6.13-rc6 Wed Aug 10 02:46 (10:35)
reboot system boot 2.6.13-rc6 Mon Aug 8 16:52 (1+20:29)
reboot system boot 2.6.13-rc6 Sun Aug 7 22:07 (2+15:14)
Since i got no feedback on my previous posts, i either bring it
the wrong way, or people don't care and i ought to shut up.
I think however that just before releasing a new stable kernel these
kind of feedback could be healthy to ironout some bugs.
For now i'll switch back to 2.6.12-mm1 and follow this mailling list
and try again when i the problems seem to have been solved.
Danny
next reply other threads:[~2005-08-14 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 10:10 Danny ter Haar [this message]
2005-08-14 11:43 ` Alexander Nyberg
2005-08-14 12:30 ` Alexey Dobriyan
2005-08-14 17:02 ` Danny ter Haar
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='ddn5aa$glm$1@news.cistron.nl' \
--to=dth@picard.cistron.nl \
--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
Powered by JetHome