From: Michael Buesch <mbuesch@freenet.de>
To: Joshua Kwan <joshk@triplehelix.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Serious stability issues with 2.6.10-rc1
Date: Mon, 25 Oct 2004 11:39:19 +0200 [thread overview]
Message-ID: <200410251139.24509.mbuesch@freenet.de> (raw)
In-Reply-To: <pan.2004.10.25.01.20.55.763270@triplehelix.org>
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
Quoting Joshua Kwan <joshk@triplehelix.org>:
> Hello,
>
> 2.6.10-rc1 seems to have a tendency to lock up after about 8 hours or so
> of uptime. Usually, I am in X, listening to music, and working on
> something when this happens out of the blue. It's a hard hang and there is
> no network response or ability to switch back to a tty so i can get
> sysrq-t output. It just dies. This has happened twice in the past 48 or
> so hours.
>
> I can't really provide much debugging info though, due to the nature of
> the hang. Is there anything that pops into mind that I should try to nail
> this problem?
>
> 2.6.9 seems to be a lot better at staying alive.
I saw exactly the same problem in 2.6.9-rcX and 2.6.9.
I didn't try 2.6.10-rc1, yet.
The last stable kernel was 2.6.8.1 for me.
> Thanks
>
--
Regards Michael Buesch [ http://www.tuxsoft.de.vu ]
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-25 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 1:20 Serious stability issues with 2.6.10-rc1 Joshua Kwan
2004-10-25 6:12 ` Jeff Garzik
2004-10-25 6:25 ` Joshua Kwan
2004-10-25 10:44 ` richard juckes
2004-11-11 4:03 ` Joshua Kwan
2004-10-25 9:39 ` Michael Buesch [this message]
2004-10-25 10:59 ` Meelis Roos
2004-10-25 19:56 ` Serious stability issues with 2.6.10-rc1 - more info Meelis Roos
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=200410251139.24509.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox