Bug 206069 – Unable to boot without noapic kernel parameter

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 206069 - Unable to boot without noapic kernel parameter

Summary:	Unable to boot without noapic kernel parameter

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Enterprise Linux 5
Classification:	Red Hat
Component:	kernel (Show other bugs)
Sub Component:
Version:	5.0
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Brian Maly
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2006-09-11 15:34 EDT by Milan Kerslager
Modified:	2007-11-30 17:07 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:	5.0
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-09-07 09:16:12 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
full boot - dmesg (noapic used) (16.00 KB, text/plain) 2006-09-11 15:47 EDT, Milan Kerslager	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Milan Kerslager 2006-09-11 15:34:43 EDT

I'm unable to boot installation or rescue CD without noapic parameter. The
system hangs even after update from 0303 BIOS to the latest 0405 version.

Last message is "io scheduler cfq registered (default)"

Motherboard: ASUS M2NPV-MX, both x86_64 and i386, kernel 2.6.17-1.2519.4.21.el5

Up-to-date Fedora Core 6 Test3 kernel boots fine (HDD from another machine).

Comment 1 Milan Kerslager 2006-09-11 15:47:30 EDT

Created attachment 136031 [details]
full boot - dmesg (noapic used)

Comment 2 Adam Kropelin 2006-12-18 18:48:23 EST

Same here on a Dell E521 which uses the NForce 430 chipset. Booting stock RHEL5
kernels with 'noapic' cures the problem, as does using 2.6.19 where no special
kernel parameters are needed.

Comment 3 Ernie Petrides 2007-09-05 15:31:11 EDT

Hello, Milan.  Does this problem still exist with the RHEL5.1 beta kernel?

Comment 4 Milan Kerslager 2007-09-07 09:01:25 EDT

No. There was a BIOS update so I'm now able to boot version 5 and 5.1 Beta too.

Comment 5 Ernie Petrides 2007-09-07 16:28:10 EDT

Changing resolution from CURRENTRELEASE to NOTABUG (since there
was no kernel bug to fix).

Note You need to log in before you can comment on or make changes to this bug.