From: Roberto Jung Drebes <drebes@inf.ufrgs.br>
To: VDA <VDA@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Duron kernel crash (i686 works)
Date: Tue, 11 Sep 2001 16:38:32 -0300 (EST) [thread overview]
Message-ID: <Pine.GSO.4.21.0109111623500.13708-100000@jacui> (raw)
In-Reply-To: <154763769.20010911115644@port.imtp.ilyichevsk.odessa.ua>
On Tue, 11 Sep 2001, VDA wrote:
> Please report to lkml as much details about your BIOSes (both older
> and newer) as you can.
>
> You may be interesting in this msg:
> --------------------------------------------------------------
> ...
> kernel_fpu_end();
> + from-=4096;
> + to-=4096;
> + if(memcmp(from,to,4096)!=0) {
> + printk("Athlon bug!"); //add printout of from,to,...?
> + memcpy(to,from,4096);
> + }
> }
I then get 'Athlon bug!' Still oopses.
>
> Comparing K7 and MMX fast_copy_page...
>
> Does replacing movntq->movq fix makes oops go avay?
Yes, it does! Didn't tested exaustively, but it seems to go away!
As said earlier, this happens after upgrading from BIOS YH to 3R in the
KT7A-RAID. The processor is a Duron 800 not overclocked.
--
Roberto Jung Drebes <drebes@inf.ufrgs.br>
Porto Alegre, RS - Brasil
http://www.inf.ufrgs.br/~drebes/
next parent reply other threads:[~2001-09-11 19:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <154763769.20010911115644@port.imtp.ilyichevsk.odessa.ua>
2001-09-11 19:38 ` Roberto Jung Drebes [this message]
2001-09-12 6:56 ` Liakakis Kostas
2001-09-12 8:21 ` Morten Helgesen
2001-09-11 1:11 Roberto Jung Drebes
2001-09-11 3:30 ` Roberto Jung Drebes
2001-09-11 14:47 ` Alan Cox
2001-09-12 6:59 ` VDA
2001-09-12 10:51 ` Steffen Persvold
2001-09-12 11:08 ` VDA
2001-09-12 11:23 ` Arjan van de Ven
2001-09-12 12:48 ` Alan Cox
2001-09-12 13:48 ` VDA
2001-09-12 18:09 ` Mike Fedyk
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=Pine.GSO.4.21.0109111623500.13708-100000@jacui \
--to=drebes@inf.ufrgs.br \
--cc=VDA@port.imtp.ilyichevsk.odessa.ua \
--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®