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: Sat, 06 Dec 2003 21:31:42 +0100	[thread overview]
Message-ID: <1070742702.1735.4.camel@localhost> (raw)

Hello,

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:

http://www.ussg.iu.edu/hypermail/linux/kernel/0311.3/0386.html

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

http://www.ussg.iu.edu/hypermail/linux/kernel/0311.3/0122.html

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 2.6.0-preX causes memory corruption 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:
  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=1070742702.1735.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.