public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlo <devel@integra-sc.it>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Ooops with kernel 2.4.22 and reiserfs
Date: Tue, 23 Dec 2003 19:17:18 +0100	[thread overview]
Message-ID: <1072203437.21198.101.camel@atena> (raw)
In-Reply-To: <20031223152014.GG2099@linuxhacker.ru>

Il mar, 2003-12-23 alle 16:20, Oleg Drokin ha scritto:

> Sounds like a list corruption to me.
> Are you sure the memory in that box is ok?
> 
This PC has never gave memory problems and we use it in extensive mode. 

> Run it through ksymoops and see if backtrace is different each time.
> Usually only first oops per boot is useful.
> If backtrace is different each time, perhaps list all unique oopses?
> 
I run it several time with the same result.
I think thah it's a bug that is hardware dependant, because the same
program on another PC with the same HW but different MainBoard run
without problems
> Thank you.
Thank you too
Saluti Carlo!
> 
> Bye,
>     Oleg


  reply	other threads:[~2003-12-23 18:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-22 21:01 Ooops with kernel 2.4.22 and reiserfs Carlo
2003-12-22 22:05 ` Oleg Drokin
2003-12-23 10:04   ` Carlo
2003-12-23 15:20     ` Oleg Drokin
2003-12-23 18:17       ` Carlo [this message]
2003-12-25 12:34     ` dan carpenter
2003-12-26  1:47       ` Bruce Allen
2003-12-27 12:52         ` Carlo
2003-12-27 19:38           ` Bruce Allen
  -- strict thread matches above, loose matches on Subject: below --
2003-12-22 18:49 Carlo
2003-12-23 10:39 ` Andre Hedrick
2003-12-23 17:45   ` Carlo

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=1072203437.21198.101.camel@atena \
    --to=devel@integra-sc.it \
    --cc=green@linuxhacker.ru \
    --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