From: Cristiano De Michele <demichel@na.infn.it>
To: Willy Tarreau <willy@w.ods.org>
Cc: linux kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.23 oops
Date: Sun, 04 Jan 2004 18:19:11 +0100 [thread overview]
Message-ID: <1073236750.2327.2.camel@cripat.acasa-tr.it> (raw)
In-Reply-To: <20040104143555.GF3728@alpha.home.local>
ok you were right it was the RAM, disabling the bank interleave and
increasing the CAS latency in the BIOS settings it seems
that now my system is pretty stable (using memtest86)
thx for your help
bye bye Cristiano
On Sun, 2004-01-04 at 15:35, Willy Tarreau wrote:
> Hi !
>
> On Sun, Jan 04, 2004 at 02:33:46PM +0100, Cristiano De Michele wrote:
>
> > Jan 3 04:39:42 cripat kernel: EFLAGS: 00010016
> > Jan 3 04:39:42 cripat kernel: eax: 616d7157 ebx: 6d6e6f72 ecx:
> > c8a5c000 edx: 73694400
>
> This is weird, eax, ebx and edx contain portions of text :
> eax="Wqma"
> ebx="ronm"
> edx="siD\0"
>
> Perhaps it's pure coincidence, but it may also be a part of a URL or
> temporary file name. Could you run memtest86 on you system to check
> that you don't have RAM defects ?
>
> Willy
--
Cristiano De Michele,
Department of Physics,
University "Federico II" of Naples
next prev parent reply other threads:[~2004-01-04 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 13:33 Cristiano De Michele
2004-01-04 14:35 ` Willy Tarreau
2004-01-04 17:19 ` Cristiano De Michele [this message]
2004-01-04 17:30 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2003-12-10 8:48 2.4.23 Oops in journal_try_to_free_buffers Frank van Maarseveen
2003-12-15 11:02 ` 2.4.23 Oops Frank van Maarseveen
2003-12-15 12:03 ` Marcelo Tosatti
2003-12-15 12:20 ` Frank van Maarseveen
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=1073236750.2327.2.camel@cripat.acasa-tr.it \
--to=demichel@na.infn.it \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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
all inboxes | Powered by JetHome®