All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Trevor Turner <turn3r.tr3v0r@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: K7/Athlon Optimization Causes Build Fail on Kernel 3.3 i686
Date: Wed, 28 Mar 2012 13:19:58 +0200	[thread overview]
Message-ID: <20120328111957.GA6765@x1.osrc.amd.com> (raw)
In-Reply-To: <CANYHJ6jjuO7yV_kbPsnJ6X+KXrsz2PRPPXHN4Rkr-vgoSG-E4A@mail.gmail.com>

On Tue, Mar 27, 2012 at 06:56:51AM -0700, Trevor Turner wrote:
> Hi,
> The other day when I was compiling 3.3 on my home server, enabling the
> K7/Athlon family optimizations seems to cause the build to fail.

I'm assuming with this you mean

CONFIG_MK7, i.e. "Athlon/Duron/K7" in "Processor Family" under
"Processor Type and Features" in the kernel configurator? At least it
looks like this from your other mail with the failing .config.

> It fails without any erroneous output at the very end of the build and
> has been reproducible every time I've built with it enabled. This
> machine has a pair of Athlon 2000+ MP's and I'm using Arch Linux's
> makepkg system (which calls make localmodconfig, make nconfig, and
> make -j3 bzImage modules) to build my kernels. I have experienced
> this issue on both the stock -ARCH kernel, and the -CK kernel under a
> number of different configurations.

Right, can you try this with the upstream kernel, i.e.

1. get one from kernel.org
2. copy the .config into the directory where you've unpacked the sources
3. do 'make oldconfig' and then 'make menuconfig' and go and select Athlon build
4. do 'make -j3 > w.log 2>&1' so that you can catch the build output into w.log
which you can send later

Also, which build tools are you using, simply do

./scripts/ver_linux

in the kernel source directory, catch the output and send it on pls.

This should be all for now, thanks.

-- 
Regards/Gruss,
Boris.

  parent reply	other threads:[~2012-03-28 11:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 13:56 K7/Athlon Optimization Causes Build Fail on Kernel 3.3 i686 Trevor Turner
2012-03-27 17:29 ` Randy Dunlap
2012-03-28  0:03   ` Trevor Turner
2012-03-28 11:19 ` Borislav Petkov [this message]
2012-03-28 16:33   ` Trevor Turner
2012-03-28 17:10     ` Borislav Petkov
2012-03-28 17:13       ` Randy Dunlap
2012-03-28 17:27         ` Borislav Petkov
2012-03-29  7:48           ` Borislav Petkov
2012-03-29  8:14             ` Matt Fleming
2012-03-29 10:48               ` Borislav Petkov
2012-03-29 18:21                 ` Trevor Turner
2012-03-29 18:28                 ` H. Peter Anvin
2012-03-29 20:46                   ` Borislav Petkov
2012-03-29 20:49                     ` H. Peter Anvin
2012-03-30  7:47                       ` Borislav Petkov

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=20120328111957.GA6765@x1.osrc.amd.com \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=turn3r.tr3v0r@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.