LKML Archive on
help / color / mirror / Atom feed
From: Ali Akcaagac <>
Subject: Re: 2.6.0-preX causes memory corruption
Date: Wed, 26 Nov 2003 07:00:10 +0100	[thread overview]
Message-ID: <1069826410.907.12.camel@localhost> (raw)

> > to go for new stuff 2 days later). So I bought brand new mobo,
> > ram, harddisk and stuff like that and build the system up:

> new power supply?

Yes that was the first thing I've replaced. My old 250W for a new 433W
although I must admit that the old PSU still works fine as it did for
the past 3.5 years for my old Gigabyte BX2000 and old Elitegroup K7S5A
(including all the stuff like HD, CD, GRAKA etc.) it consumed less than
250W. I'm educated electronics guy and tested the old PSU under stress
conditions e.g. with consumer connected only to check whether the
voltage or current break down or something. The new PSU should satisfy
my system more than one time.

> > really worried what the cause of this problem could be. I know
> > there could be dozen of reasons such as compiler used, stuff
> > compiled ...

> and which compiler did you use?

gcc (GCC) 3.3.2

But I doubt that this is Compiler related since I use this one even
before pre9 (where the system worked stable). This problem showed up the
first time within pre9 and still exists in pre10 and now that other
folks confirmed that there is some 'strange magic' inside the Kernel I
now feel more that this may be the case. It's no permanent thing or
something it happens every now and then.

I now gonna disable preempt and report back.

             reply	other threads:[~2003-11-26  6:00 UTC|newest]

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