LKML Archive on
help / color / mirror / Atom feed
From: (Måns Rullgård)
Subject: Re: 2.6.0-preX causes memory corruption
Date: Tue, 25 Nov 2003 21:09:28 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1069789556.2115.16.camel@localhost>

Ali Akcaagac <> writes:

> After installing 2.6.0-pre9 the System seemed to work normally, all the

You mean 2.6.0-test9, don't you?

> stuff I did before worked normally but when doing large fileoperation
> including crunching stuff using bzip2 (e.g. checking out modules from
> CVS and tar'ing them up) the archives get corrupt. I was first assuming
> that this was a onetime mistake and thus I deleted the corrupt file and
> re-run my normal operations. But after a while I noticed that this
> problem occoured more and more and I was starting to worry. Archives are
> showing to be corrupted but after an reset these archives can be
> unpacked normally again.

Do you have preemptive kernel enabled (CONFIG_PREEMPT=y)?  There's
been some discussion about it possibly causing strange things in some
configurations.  If it helps to disable it, please post your .config,
so we can compare with others.

Måns Rullgård

  reply	other threads:[~2003-11-25 20:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25 19:45 Ali Akcaagac
2003-11-25 20:09 ` Måns Rullgård [this message]
2003-11-25 20:26 Ali Akcaagac
2003-11-26  9:33 ` Michael Buesch
2003-11-26  5:52 Ali Akcaagac
2003-11-26  6:00 Ali Akcaagac
2003-12-06 20:31 Ali Akcaagac

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: 2.6.0-preX causes memory corruption' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).