Bug 157908 – Oops in ACPI code when booting with hyperthreading on

This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours

Bug 157908 - Oops in ACPI code when booting with hyperthreading on

Summary:	Oops in ACPI code when booting with hyperthreading on

Status:	CLOSED NOTABUG

Aliases:	None

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

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

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-05-16 18:27 EDT by Manish Singh
Modified:	2015-01-04 17:19 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-05-18 20:33:33 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Manish Singh 2005-05-16 18:27:51 EDT

With 2.6.9-9.EL, the kernel crashes on boot with hyperthreading turned on. With
HT off, it boots fine. This happens on both x86_64 and ia32 (on the same
hardware, a dual 3.4 GHz Xeon). The same machine boots with 5.0.5.EL perfectly.

On x86_64, it gives the following errors:

ACPI-0292: *** Error: Looking up [_PCT] in namespace, AE_ALREADY_EXISTS
ACPI-1133: *** Error: [NULL NAME], AE_ALREADY_EXISTS

and then oopses with a NULL pointer dereference in acpi_ps_parse_aml.

Comment 1 Venkatesh Pallipadi 2005-05-18 00:00:28 EDT

This is a known BIOS issue. Same as this one..
http://bugme.osdl.org/show_bug.cgi?id=3147

I have seen this fixed in BIOS in various platforms. Can you make sure you are
running the latest BIOS.

What platform is this? 

-Venki

Comment 2 Manish Singh 2005-05-18 18:41:23 EDT

These boxes are EM64T capable, but the problem happens in both 64 and 32-bit modes.

These are prerelease systems on loan from Intel, so an old BIOS wouldn't be
surprising. I'll try to a find out an update through partner channels and let
you know the results.

Comment 3 Manish Singh 2005-05-18 20:33:33 EDT

BIOS update the did trick. Resolving accordingly.

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