public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Seth Goldberg <bergsoft@home.com>
To: Gordon Sadler <gbsadler1@lcisp.com>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Athlon/VIA Kernel Experimentation (mmx.c)
Date: Fri, 04 May 2001 02:54:01 -0700	[thread overview]
Message-ID: <3AF27C39.9BD7EC99@home.com> (raw)
In-Reply-To: <20010503150346.A18141@debian-home.lcisp.com>

Hi,

  I implemented a small check loop at the end of the fast_page_copy
routine in mmx.c for the Athlon.  Booting the resulting kernel
yields an interesting result. Every single time, the kernel
panics RIGHT AFTER it frees unused kernel memory from bootup.
I encourage those of you with the same problem to try this and report
when it panics.

Here is my patch to mmx.c: (sorry about the long lines)
-----------------------------------------------------cut here
diff -r linux-ref/arch/i386/lib/mmx.c linux/arch/i386/lib/mmx.c
204a205,216
>
>       {
>               register int x = 0;
>               /* do mem compares to ensure written == read */
>               for ( /* initted above */; x < (4096/sizeof(int)); x++ )
>               {
>                       if ( ((int *)to)[x] != ((int *)from)[x] ) {
>                               panic("fast_page_copy: dest value @ 0x%lx (%x) does not equal source value @ %lx (%x)!\n",
>                                               (long) to, ((int *)to)[x], (long) from, ((int *) from)[x] );
>                       }
>               }
>       }                                                                          
-----------------------------------------------------cut here

  Wouldn't it be correct to say that because it is panicking, the
page copy was not completed properly?  If that is so, the next step
is to find out why this copy is not working properly...

For me the output is:

...
Freeing unused kernel memory: 188k freed     
Kernel panic: fast_page_copy: dest value @ 0xcfed1000 (39312036) does
not equal source value @ cfed4000(79005b)!

--------

It is interesting to note that these addresses are page aligned, meaning
that the copy of even
the first byte failed!

 --Seth

  parent reply	other threads:[~2001-05-04  9:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-03 20:03 Info on Athlon/Duron failure as requested Gordon Sadler
2001-05-04  8:40 ` Idea for Athlon/Duron failure testing Seth Goldberg
2001-05-04  9:54 ` Seth Goldberg [this message]
2001-05-04 13:21   ` Athlon/VIA Kernel Experimentation (mmx.c) Brian Gerst
2001-05-04 16:57     ` Seth Goldberg
2001-05-04 14:09   ` Alan Cox

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=3AF27C39.9BD7EC99@home.com \
    --to=bergsoft@home.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gbsadler1@lcisp.com \
    --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