From: Dave Jones <davej@suse.de>
To: Luca Montecchiani <luca.montecchiani@teamfab.it>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [OOPS] Linux 2.2.21pre[23]
Date: Thu, 7 Mar 2002 18:11:36 +0100 [thread overview]
Message-ID: <20020307181136.J29587@suse.de> (raw)
In-Reply-To: <E16j0fe-0002m9-00@the-village.bc.nu> <3C879558.A727E265@teamfab.it> <20020307173948.I29587@suse.de> <3C879E01.B2BFAFCD@teamfab.it>
In-Reply-To: <3C879E01.B2BFAFCD@teamfab.it>; from luca.montecchiani@teamfab.it on Thu, Mar 07, 2002 at 06:06:09PM +0100
On Thu, Mar 07, 2002 at 06:06:09PM +0100, Luca Montecchiani wrote:
> > Ok, this doesn't make any sense at all.
> You're right x86_serial_nr_setup() is c0278bc8
> while c0278bc1 didn't exist in my system.map sorry!
So we died in squash_the_stupid_serial_number()
static void __init squash_the_stupid_serial_number(struct cpuinfo_x86 *c)
{
if (c->x86_capability&(X86_FEATURE_PN) && disable_x86_serial_nr) {
/* Disable processor serial number */
unsigned long lo,hi;
rdmsr(0x119,lo,hi);
lo |= 0x200000;
wrmsr(0x119,lo,hi);
printk(KERN_NOTICE "CPU serial number disabled.\n");
c->x86_capability &= ~X86_FEATURE_PN;
c->cpuid_level = cpuid_eax(0);
}
}
Given that you see the printk, its one of the last two lines.
I can't see how this can happen.
Although the cpuid_eax function in include/asm-i386/processor.h
needs updating.
2.2 has
extern inline unsigned int cpuid_eax(unsigned int op)
{
unsigned int eax, ebx, ecx, edx;
__asm__("cpuid"
: "=a" (eax), "=b" (ebx), "=c" (ecx), "=d" (edx)
: "a" (op));
return eax;
}
2.4 has
unsigned int eax;
__asm__("cpuid"
: "=a" (eax)
: "0" (op)
: "bx", "cx", "dx");
return eax;
Though, that shouldn't make any noticable difference unless.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-03-07 17:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 12:07 Linux 2.2.21pre2 Alan Cox
2002-03-07 16:05 ` [OOPS] Linux 2.2.21pre[23] Luca Montecchiani
2002-03-07 16:23 ` Alan Cox
2002-03-07 16:17 ` Dave Jones
2002-03-07 16:29 ` Luca Montecchiani
2002-03-07 16:39 ` Dave Jones
2002-03-07 17:06 ` Luca Montecchiani
2002-03-07 17:11 ` Dave Jones [this message]
2002-03-07 17:26 ` SOLVED " Luca Montecchiani
2002-03-07 17:20 ` Alan Cox
2002-03-11 8:44 ` Ext2/3 uid/gid support Erik Meusel
2002-03-11 8:47 ` Mike Fedyk
2002-03-11 9:22 ` Erik Meusel
2002-03-11 15:21 ` Matthias Andree
2002-03-11 16:44 ` Andreas Dilger
2002-03-12 1:48 ` Andrew Hatfield
-- strict thread matches above, loose matches on Subject: below --
2002-03-07 19:42 [OOPS] Linux 2.2.21pre[23] Julian Anastasov
2002-03-07 19:48 ` Richard B. Johnson
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=20020307181136.J29587@suse.de \
--to=davej@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.montecchiani@teamfab.it \
/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