mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joshua Kwan <joshk@ludicrus.ath.cx>
To: linux-kernel@vger.kernel.org
Subject: [2.5.58-bk] link failure in intel.c
Date: Wed, 15 Jan 2003 00:50:28 -0800	[thread overview]
Message-ID: <20030115085028.GA27568@ludicrus.ath.cx> (raw)

[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]

Bad things during the final link process:

arch/i386/kernel/built-in.o(.init.text+0x34e4): In function `P2_enable_L2':
: undefined reference to `read_cr0'
arch/i386/kernel/built-in.o(.init.text+0x34f4): In function `P2_enable_L2':
: undefined reference to `write_cr0'
arch/i386/kernel/built-in.o(.init.text+0x3510): In function `P2_enable_L2':
: undefined reference to `write_cr0'
arch/i386/kernel/built-in.o(.init.text+0x3515): In function `P2_enable_L2':
: undefined reference to `wbinvd'
make[1]: *** [vmlinux] Error 1
make: *** [vmlinux] Error 2

I'm quite sure it is because of this changeset:

davej@codemonkey.org.uk|arch/i386/kernel/cpu/intel.c|20030115022821|46315

======== intel.c 1.1..1.18 ========
D 1.18 03/01/15 01:28:21-01:00 davej@codemonkey.org.uk 38 37 29/0/430
P arch/i386/kernel/cpu/intel.c
C Some 'overdrive' boards, such as those from Powerleap don't have
C the L2 cache enabled, and the BIOS doesn't know about it, so we
C introduce a boot option to 'force' it on.

Dave forgot to include system.h in his revised intel.c, so here is a 
quick patch for it.

--- arch/i386/kernel/cpu/intel.c        2003-01-15 00:48:43.000000000 -0800
+++ arch/i386/kernel/cpu/intel.new.c    2003-01-15 00:41:53.000000000 -0800
@@ -8,6 +8,7 @@
 #include <asm/processor.h>
 #include <asm/msr.h>
 #include <asm/uaccess.h>
+#include <asm/system.h>
 
 #include "cpu.h"

With this patch the kernel compiles cleanly.

Regards
Josh

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2003-01-15  8:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030115085028.GA27568@ludicrus.ath.cx \
    --to=joshk@ludicrus.ath.cx \
    --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®