From: Alexander Nyberg <alexn@telia.com>
To: Danny ter Haar <dth@picard.cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rcX really this bad ?
Date: Sun, 14 Aug 2005 13:43:18 +0200 [thread overview]
Message-ID: <20050814114317.GA1365@localhost.localdomain> (raw)
In-Reply-To: <ddn5aa$glm$1@news.cistron.nl>
On Sun, Aug 14, 2005 at 10:10:18AM +0000 Danny ter Haar wrote:
> 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...
>
> 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.
>
Is the machine running X? We need some output from it so we can debug
what's going on, the info should be printed to the console. It would
be great if you could run the latest kernel and see if you get any
output. Also add nmi_watchdog=2 to the boot command line.
You can also set up a serial console or netconsole to capture the output
from the server with the help of another machine, described in
Documentation/serial-console.txt
Documentation/networking/netconsole.txt
next prev parent reply other threads:[~2005-08-14 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 10:10 Danny ter Haar
2005-08-14 11:43 ` Alexander Nyberg [this message]
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=20050814114317.GA1365@localhost.localdomain \
--to=alexn@telia.com \
--cc=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