From: Samuel Flory <sflory@rackable.com>
To: "Cornelius Kölbel" <cornelius.koelbel@gmx.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: Bug in Kernel 2.4.20-8]
Date: Wed, 02 Jul 2003 14:17:39 -0700 [thread overview]
Message-ID: <3F034BF3.3010705@rackable.com> (raw)
In-Reply-To: <3F01F052.8070307@gmx.de>
Cornelius Kölbel wrote:
> Alan Cox wrote:
>
>> On Maw, 2003-07-01 at 08:35, Cornelius Kölbel wrote:
>>
>>
>>> I am using Kernel 2.4.20. I admit, it is the kernel of RedHat 9.
>>> I hope this is not, because RedHat did so much changes to the Kernel
>>>
>>
>>
>> Always hard to tell. It is worth filing Red Hat kernel bugs in
>> https://bugzilla.redhat.com/bugzilla and picking up current errata
>> kernels if there are newer ones
>>
>>
>>
>>> I was just typing a mail, when the caps lock light and the scroll
>>> lock light went on.
>>> Nothing happend anymore. No mouse, no keyboard.
>>> I resetted the computer.
>>>
>>
>>
>> This is a panic - the machine got itself into a state that could not
>> continue. The flashing lights are giving data in morse (useful for those
>> truely desperate debugging situations only 8))
>>
>>
>>
> After having watched some other problems, I guess it is due to a bad
> memory module. (Can this be?)
> I removed this module and since then, I had no proplems anymore.
>
You might want to try a memory tester. I recommend either memtst86,
or ctcs's memtst.
http://www.memtest86.com/
http://sourceforge.net/projects/va-ctcs/
--
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
prev parent reply other threads:[~2003-07-02 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 7:35 [Fwd: Bug in Kernel 2.4.20-8] Cornelius Kölbel
2003-07-01 18:54 ` Alan Cox
2003-07-01 20:34 ` Cornelius Kölbel
2003-07-02 21:09 ` Alan Cox
2003-07-02 21:17 ` Samuel Flory [this message]
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=3F034BF3.3010705@rackable.com \
--to=sflory@rackable.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cornelius.koelbel@gmx.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