From: Oleg Drokin <firstname.lastname@example.org>
Subject: Re: lots of oopses with recent kernels
Date: Thu, 17 Jul 2003 14:13:38 +0400 [thread overview]
Message-ID: <20030717101338.GA14381@namesys.com> (raw)
On Wed, Jul 16, 2003 at 11:35:55PM +0000, email@example.com wrote:
> I am using gcc version 3.3 20030623 (Red Hat Linux 3.3-12)
> so that may be to blame...
> ...but I have received the bellow oopses while copying files to a "Device-Mapper" striped device with
> 'tar cf - . | tar - -C /mnt/tmp'
> oops1: reiserfs format device (with BadRAM patch)
> oops2: ext2/3 format device (with BadRAM patch)
> oops3: reiserfs format device (with mem=320M BadRAM patch
Sigh, I see lots of times your kernel jumps at random addresses for no good reason.
(like in 2 out of your four oopses you attached).
Have you tried to compile without CONFIG_PREEMPT just to see if it will be any better?
prev parent reply other threads:[~2003-07-17 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 23:35 lots of oopses with recent kernels steven.newbury1
2003-07-17 10:13 ` Oleg Drokin [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).