All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ali Akcaagac <aliakc@web.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-preX causes memory corruption
Date: Tue, 25 Nov 2003 21:26:07 +0100	[thread overview]
Message-ID: <1069791966.2343.4.camel@localhost> (raw)

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

> You mean 2.6.0-test9, don't you?

Yes

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

Yes

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

Yes, saw it after I've posted my mail. But here is my config.

http://www.akcaagac.com/.config

Hope it helps.


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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25 20:26 Ali Akcaagac [this message]
2003-11-26  9:33 ` 2.6.0-preX causes memory corruption Michael Buesch
  -- strict thread matches above, loose matches on Subject: below --
2003-12-06 20:31 Ali Akcaagac
2003-11-26  6:00 Ali Akcaagac
2003-11-26  5:52 Ali Akcaagac
2003-11-25 19:45 Ali Akcaagac
2003-11-25 20:09 ` Måns Rullgård

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=1069791966.2343.4.camel@localhost \
    --to=aliakc@web.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.