Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 22806 - gs-sources 2.4.21_rc8 will not compile on SMP machine. Error in sched.c line 961.
Summary: gs-sources 2.4.21_rc8 will not compile on SMP machine. Error in sched.c line ...
Status: RESOLVED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Bob Johnson (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-14 03:08 UTC by Trey Stout
Modified: 2003-12-05 23:29 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Trey Stout 2003-06-14 03:08:04 UTC
I emerged gs-sources on a fresh install today. It emerged and patched just 
fine. After doing a make config and enabling SMP+enhanced real time clock, I 
did the standard 'make dep && make clean bzImage modules modules_install' This 
does make dep just fine, the fails during the compile of sched.c at line 961.

Here is the error:
sched.c:961: redefinition of 'set_cpus_allowed'
sched.c:922: 'set_cpus_allowed' previously defined here

It looks like set_cpus_allowed was declared twice in the file. I removed the 
duplicate entry (they are right next to eachother) and restarted the 
compilation. This worked, but produced a kernel panic on boot. There must be 
more to this problem, but I am no kernel hacker.

Reproducible: Always
Steps to Reproduce:
1. emerge gs-sources
2. make menuconfig (enable SMP+enhanced real time clock)
3. make dep && make clean bzImage modules modules_install

Actual Results:  
It failed to make the kernel. See error above.

Expected Results:  
Made the kernel.

Since this box has never booted anything but a livecd, I have no idea how to 
get that info pasted into here without typing it out by hand.

It is a fresh install and portage is version 2.0.48
Comment 1 Bob Johnson (RETIRED) gentoo-dev 2003-06-14 17:20:31 UTC
ill do a test on this, a quick glance shows it might be cpu_frequency 
 
a "KERNEL_EXCLUDE=cpu_freq emerge gs-sources" will 
probaly take care of it, ill make sure its fixed for the 2.4.21 release  
by monday 
Comment 2 Trey Stout 2003-06-14 20:49:43 UTC
'KERNEL_EXCLUDE=cpu_freq emerge gs-sources'

That worked. Sort of. It emerged again just fine, let me compile. Then kernel paniced on boot. 
Comment 3 Bob Johnson (RETIRED) gentoo-dev 2003-06-14 20:56:55 UTC
ill need a little more info on the panic, it should give a process  at least 
Comment 4 Donnie Berkholz (RETIRED) gentoo-dev 2003-06-16 09:58:07 UTC
I'm having the same problem. Haven't bothered re-emerging, but I can if you need more troubleshooting.
Comment 5 Walt H 2003-06-17 18:30:52 UTC
Just wanted to add that I too had the compile error. After backing out the duplicate 'set_cpus_allowed' the compile completed successfully. However, I experienced filesystem corruption a short while later for the first time in over 2 years. I'm using XFS for my filesystems on / /usr and /home. The root and home mount points were both corrupted quite nicely. I've since backed to gs-sources-rc2 and all is well again. I used the same .config for both rc2 and rc8, however, I did change cpu type to athlon-mp in rc8. Not sure if that runs a significantly different code path to cause the corruption. 
Comment 6 Martin Diers 2003-06-24 12:36:44 UTC
After turning off SMP support, when I attempt to compile this kernel, I get numerous duplicate definitions, which cause the compile to abort. This is after a fresh make menuconfig / make dep / make clean / make bzImage.
Comment 7 Craig Bradney 2003-06-29 04:21:17 UTC
I removed the duplicate section and I can run stable with the resulting kernel.. no issues (except for 
bug 23093). 
Comment 8 Bob Johnson (RETIRED) gentoo-dev 2003-06-29 18:36:31 UTC
just got back from vacation, updated gs-sources to 2.4.22_pre2  
removed cpu_freq . This should fix most issues. 
Comment 9 Andrew Cooks (RETIRED) gentoo-dev 2003-12-05 23:29:34 UTC
This bug has been inactive for a while. 

Please test again with the latest version and reopen this bug if the problem persists.