public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Volkoff <vdb@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: [GOLDMINE!!!] Athlon optimisation bug (was Re: Duron kernel crash)
Date: Wed, 12 Sep 2001 08:29:35 +0400	[thread overview]
Message-ID: <20010912082935.A391@localhost> (raw)

>I don't have any problems with the kernel, but if I'm compiling (say) the
>kernel or any large program, user-mode apps like gcc, make, etc all
>randomly segfault on me.
>
>I'm running a Duron 800 on a Asus A7V133 mobo - and no bios version I've
>tried has made a bit of difference yet :p

Same things here. I'm also experiencing random segfaults with kernels 
2.4.10pre[47]. My motherbord is Chaintech CT-7AIA2 (kt133A/686A), Duron 600.
I did'nt see such things with kernels 2.4.[78]. The problem persists even 
after recompiling kernel with K6-III optimisation. Note, this motherboard
was rock solid and I never had any problems with athlon-optimised kernels
prior to 2.4.9.

-- 

    DV

             reply	other threads:[~2001-09-12  4:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-12  4:29 Dmitry Volkoff [this message]
2001-09-12  6:28 ` [GOLDMINE!!!] Athlon optimisation bug (was Re: Duron kernel crash) Peter Horton
2001-09-12  7:24   ` J.Brown (Ender/Amigo)
2001-09-12 10:06 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-09-11 11:21 Jonathan Morton
2001-09-11 11:27 ` Gergely Tamas
2001-09-11 11:32   ` Gergely Tamas
2001-09-11 11:53     ` Jonathan Morton
2001-09-11 14:59       ` Roberto Jung Drebes
2001-09-12 14:00   ` VDA
2001-09-12 17:59     ` Janne Pänkälä
2001-09-11 12:59 ` Nicholas Knight
2001-09-11 14:30   ` J.Brown (Ender/Amigo)
2001-09-11 16:21   ` Luigi Genoni
2001-09-13  2:30     ` Jonathan Morton
2001-09-13  3:44 ` Dwayne C. Litzenberger
2001-09-13 10:20   ` Alistair Phipps

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=20010912082935.A391@localhost \
    --to=vdb@mail.ru \
    --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