public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Riley <oscar@the-rileys.net>
To: Martin Macok <martin.macok@underground.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test12 randomly hangs up
Date: Wed, 13 Dec 2000 17:27:03 -0500	[thread overview]
Message-ID: <3A37F7B7.1A207AB7@the-rileys.net> (raw)
In-Reply-To: <20001213105153.A6624@sarah.kolej.mff.cuni.cz>

Martin Macok wrote:
> 
> Hi,
> after 1-3 hours with -test12 system hangs up with
>  - no response from mouse
>  - no response from keyboard (no sysrq, only sysrq+'b' works ...)
>  - no response from network (ICMP, TCP)
>  - nothing on console, nothing in logs (ie. nothing interesting or relevant
>    to crash).
> 
> System was not under load (1 user, X, no swapping ...)
> 
> ( -test11 was up for 3 weeks with no problems and so do 2.2.17 ... )
> 
> slightly modified Red Hat 7.0:
> 
> Linux sarah.xxxxxxxxxxxxxxxxx 2.4.0-test11 #4 Sat Dec 9 14:24:20 CET
> 2000 i586 unknown
> Kernel modules         2.3.21
> Gnu C                  2.96
> Gnu Make               3.79.1
> Binutils               2.10.0.18
> Linux C Library        > libc.2.2
> Dynamic linker         ldd (GNU libc) 2.2
> Procps                 2.0.7
> Mount                  2.10m
> Net-tools              1.56
> Console-tools          0.3.3
> Sh-utils               2.0
> Modules Loaded         nls_iso8859-2 nls_cp852 vfat mad16 ad1848 sb_lib
>                         uart401
> 
> DMESG:   http://kocour.ms.mff.cuni.cz/~macok/kernel/dmesg
> (Abit PX5, P166 (ovrclckd to 166), 128MB RAM, 2x IDE HDD, 3com509b ISA, Opti931)

Overclocking is a guaranteed way to get random hangups.  Put it back to
its recommended clock and it might work fine.  Keep in mind that while
this may not have shown up before, overclocking gradually degrades a
processor's stability (trust me, I ran several 486 and pentiums and even
a k6-2 down to where they wouldn't even work at the normal clock).  Try
sticking it back to normal.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-12-13 22:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-13  9:51 2.4.0-test12 randomly hangs up Martin Macok
2000-12-13 11:01 ` Petr Sebor
2000-12-13 11:13   ` Martin Macok
2000-12-13 22:47     ` Lukasz Trabinski
2000-12-14  3:10       ` Byron Stanoszek
2000-12-14  5:08         ` Matthew Vanecek
2000-12-14  6:53           ` Petr Sebor
2000-12-14  4:49       ` Mike Galbraith
2000-12-13 11:36   ` Jani Monoses
2000-12-13 22:27 ` David Riley [this message]
2000-12-14 15:00   ` Martin Macok
  -- strict thread matches above, loose matches on Subject: below --
2000-12-15 14:13 a.airaghi

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=3A37F7B7.1A207AB7@the-rileys.net \
    --to=oscar@the-rileys.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.macok@underground.cz \
    /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