LKML Archive on
help / color / mirror / Atom feed
From: Ali Akcaagac <>
Subject: Re: 2.6.0-preX causes memory corruption
Date: Sat, 06 Dec 2003 21:31:42 +0100	[thread overview]
Message-ID: <1070742702.1735.4.camel@localhost> (raw)


Around 2 weeks ago I made a bugreport about strange memory corruption
which have occoured with Kernel 2.6.0-pre9/10 on my system. As I told I
verified this problem on 2 different machines and today I wanted to give
feedback as I promised.

I was busy with private stuff for a couple of days and wasn't able to
check this any closer. Today I detected that even with PREEMPT DISABLED
in 2.6.0-pre11 the problem still exists. E.g. when unpacking some
tar.bz2 files I still get the message thrown out that there is a problem
and after reset the problem is gone. As reference I give you my previous
email to this list:

And another one which I think may (or may not) be related to this:

Again, this has problem exists on my old hardware as on my brand new
hardware. So basically 2 different plattforms.

Please CC to me.

             reply	other threads:[~2003-12-06 20:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-06 20:31 Ali Akcaagac [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-26  6:00 Ali Akcaagac
2003-11-26  5:52 Ali Akcaagac
2003-11-25 20:26 Ali Akcaagac
2003-11-26  9:33 ` Michael Buesch
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:

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

  git send-email \
    --in-reply-to=1070742702.1735.4.camel@localhost \ \ \
    --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).