mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Wilson" <davew@sai.co.za>
To: "Mark Hahn" <hahn@coffee.psychology.mcmaster.ca>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: FW: I think I've found a serious bug in AMD Athlon page_alloc.c routines, where do I mail the developer(s) ?
Date: Wed, 16 May 2001 10:05:50 +0200	[thread overview]
Message-ID: <NEBBJFIIGKGLPEBIJACLAEHKDMAA.davew@sai.co.za> (raw)
In-Reply-To: <Pine.LNX.4.10.10105151853040.15328-100000@coffee.psychology.mcmaster.ca>

Hi Mark,

Thanks for getting back to me, yea I'm running my fsb at 100
already....still seems to be the same problem.
I donno, I'm just gonna have to mess around with things till I get it right
;-)

Thanks for the guidance anyways.


Regards
David Wilson
Technical Support Centre
The S.A Internet
0860 100 869
http://www.sai.co.za



-----Original Message-----
From: Mark Hahn [mailto:hahn@coffee.psychology.mcmaster.ca]
Sent: 16 May 2001 01:01
To: David Wilson
Cc: linux-kernel@vger.kernel.org
Subject: Re: FW: I think I've found a serious bug in AMD Athlon
page_alloc.c routines, where do I mail the developer(s) ?


> I think I've found a serious bug in AMD Athlon page_alloc.c routines in

there's nothing athlon-specific there.

> correct on the DFI AK75-EC motherboard, if I set the CPU kernel type to
586
> everything is 100%, if I use "Athlon" kernel type I get:
> kernel BUG at page_alloc.c:73

when you select athlon at compile time, you're mainly
getting Arjan's athlon-specific page-clear and -copy functions
(along with some relatively trivial alignment changes).
these functions are ~3x as fast as the generic ones,
and seem to cause dram/cpu-related oopes on some machines.

in short: faster code pushes the hardware past stability.
there's no reason, so far, to think that there's anything
wrong with the code - Alan had a possible issue with prefetching
and very old Atlons, but the people reporting problems like this
are actually running kt133a and new fsb133 Athlons.

> I've changed RAM, Motherboard etc... still the same.

changed to a non-kt133a board?  how about running fsb and/or dram
at 100, rather than 133?

> Also the same system runs linux-2.2.16 100%

2.2 doesn't have the fast page-clear and -copy code afaik.

afaik, there are *no* problems on kt133 machines,
and haven't heard any pain from people who might have
Ali Magic1, AMD 760 or KT266 boards, but they're still rare.



  reply	other threads:[~2001-05-16  8:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-15 22:47 David Wilson
2001-05-15 23:01 ` Mark Hahn
2001-05-16  8:05   ` David Wilson [this message]
     [not found] <E14znhi-0003HR-00@the-village.bc.nu>
2001-05-15 23:12 ` David Wilson
2001-05-16 20:35   ` Alan Cox
2001-05-17  9:20     ` David Wilson

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=NEBBJFIIGKGLPEBIJACLAEHKDMAA.davew@sai.co.za \
    --to=davew@sai.co.za \
    --cc=hahn@coffee.psychology.mcmaster.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®