Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 119781

Summary:	bug in kernel compile with CONFIG_X86_UP_APIC enabled
Product:	Red Hat Enterprise Linux 3	Reporter:	Alex Lyashkov <shadow>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED NOTABUG	QA Contact:	Brian Brock <bbrock>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.0	CC:	petrides, riel
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-04-02 18:55:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alex Lyashkov 2004-04-02 05:08:24 UTC

Description of problem:
After enable CONFIG_X86_UP_APIC in kernel config file - kernel not
compile.

Version-Release number of selected component (if applicable):
2.4.21-9.0.1

How reproducible:
make menuconfig and enable 
Local APIC support on uniprocessors

Steps to Reproduce:
1. make menuconfig 
2. enable "Local APIC support on uniprocessors"
3. make dep bzImage

Actual results:
arch/i386/kernel/kernel.o(.text.init+0x5321): In function
`MP_processor_info':
: undefined reference to `xapic_support_disabled'


Expected results:
kernel compile fine.

Additional info:
-

Comment 1 Tim Burke 2004-04-02 18:55:16 UTC

Sorry, but Red Hat does not support custom kernel builds.  For the
following reasons:

- We are unable to effectively QA the infinite set of permutations and
combinations of every kernel option.  Consequently, it is impossible
for support to differentiate the implications of every option.
- There are a large set of 3rd party layered applications which have
dependencies on RH kernel versions.
- We produce periodic security errata, etc, which could then be
conflicting with custom builds.