My desktop has two identical twin boxes.  I've been building my
(B)LFS-7.2 on one of them.  I think it's ready to be clonable,
distributable.  I packaged it up (using the as-built binaries tarballs
made by my package manager immediately after compiling each package (a
basic process I've used through 4 previous builds and dozens of
clones)), and installed it on the other box.  It runs.  It has the
original LFS 3.5.2 kernel, and before I "got into" BLFS I'd patched the
kernel up to 3.9.11.  But both kernels were configured for starting on a
generic box, with the intent that once "up" one would soon rebuild the
kernel for the specific box.  I'm to that point.  I brought the working
config file from the development box, and get the following:

___8<...
  CC      arch/x86/kernel/acpi/cstate.o
  LD      arch/x86/kernel/acpi/built-in.o
  CC      arch/x86/kernel/apic/apic.o
arch/x86/kernel/apic/apic.c: In function 'lapic_next_deadline':
arch/x86/kernel/apic/apic.c:475:2: error: 'MSR_IA32_TSC_DEADLINE'
undeclared (first use in this function)
arch/x86/kernel/apic/apic.c:475:2: note: each undeclared identifier is
reported only once for each function it appears in
make[3]: *** [arch/x86/kernel/apic/apic.o] Error 1
make[2]: *** [arch/x86/kernel/apic] Error 2
make[1]: *** [arch/x86/kernel] Error 2
make: *** [arch/x86] Error 2

I've gone back to the "development" box run md5sums on /usr/src/linux-
3.9.11 and "checked" them on the new box.  They all match.  I _think_
I've got a good copy.  I try to be real careful when updating my build
chain to keep everything kosher.  

So if the new box has all the kernel files of the development box, does
it possibly have something extra?  I had this problem when I first tried
cloning--one of the patches between 3.5.2 and 3.9.11, "patched" one of
the routines with nothing, effectively deleting it.  I hazily remember
it may have had something to do with this area of code, but I could be
wrong.  I fixed my use of my package manager to avoid that.  Since I had
a list of the development box's kernel files with the md5sums, and
easily made one for the new box, I sorted both and ran comm -13 and
comm -23, and found no extra code--the new package management scheme
worked.  AFAICT, /usr/src/linux-3.9.11 is the same on both boxes.

Both systems have just two files that have that variable name:
[15:44 linux-3.9.11]$ grep -r MSR_IA32_TSC_DEADLINE *
arch/x86/include/uapi/asm/msr-index.h:#define MSR_IA32_TSC_DEADLINE     
      0x000006E0
arch/x86/kernel/apic/apic.c:    wrmsrl(MSR_IA32_TSC_DEADLINE, tsc +
(((u64) delta) * TSC_DIVISOR));
[15:45 linux-3.9.11]$ 

I started a make on the development box, and it compiles through acpi
without error.

I'm out of ideas.  I need new ideas.

Anybody got a cogent idea of something else I can look for?  Maybe even
"off the wall"?
-- 
Paul Rogers
[email protected]
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL
:-)

        

-- 
http://www.fastmail.com - Email service worth paying for. Try it for free

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to