Bug 16229 - AMD Duron and Thunderbird Athlons incorrectly attempts to disable CPUID
Summary: AMD Duron and Thunderbird Athlons incorrectly attempts to disable CPUID
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel   
(Show other bugs)
Version: 6.2
Hardware: i686
OS: Linux
high
medium
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
URL:
Whiteboard:
Keywords:
: 14541 15878 16184 16465 17176 17184 17207 17259 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-08-15 13:56 UTC by Jp Robinson
Modified: 2008-05-01 15:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-20 18:01:22 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

Description Jp Robinson 2000-08-15 13:56:21 UTC 
There is a problem with some systems running an AMD Duron or Thunderbird
CPUS. When the i686 kernel attempts to boot up after installation, it bombs
out at the "Disabling CPUID". It is apparently mis-detecting it either
during install or during boot as a Pentium III. The Installer kernel seems
to work fine, as all reports have been post installation. The only
workaround we have been able to come up with is to boot with the root=
command and install the i386 kernel. 

Thanks,
Jp
Comment 1 Bill Nottingham 2000-08-15 15:58:49 UTC 
*** Bug 16184 has been marked as a duplicate of this bug. ***
Comment 2 Bill Nottingham 2000-08-15 16:00:22 UTC 
*** Bug 15878 has been marked as a duplicate of this bug. ***
Comment 3 Carl Mes 2000-08-16 08:12:34 UTC 
Take a look at this discussion board for more info ...

http://www.linuxtests.org/cgi-bin/UltraBoard/UltraBoard.cgi?
action=Read&BID=9&TID=7

Carl
Comment 4 Bill Nottingham 2000-08-17 20:41:35 UTC 
*** Bug 16465 has been marked as a duplicate of this bug. ***
Comment 5 Michael K. Johnson 2000-08-18 19:42:24 UTC 
The 2.2.16-3 errata kernel has been reported to fix this bug.
So when you have booted with root= and installed the 386 kernel,
you can then upgrade to the 2.2.16-3 errata kernel.
Comment 6 Trond Eivind Glomsrxd 2000-08-20 18:01:20 UTC 
*** Bug 14541 has been marked as a duplicate of this bug. ***
Comment 7 Alan Cox 2000-08-22 17:05:22 UTC 
6.2 errata fixes it,  pinstripe current rawhide kernel has been checked ok

Kernel panic to ground control signing off...
Comment 8 Michael K. Johnson 2000-09-01 20:34:12 UTC 
*** Bug 17176 has been marked as a duplicate of this bug. ***
Comment 9 Michael K. Johnson 2000-09-01 20:36:23 UTC 
*** Bug 17184 has been marked as a duplicate of this bug. ***
Comment 10 Bill Nottingham 2000-09-07 19:35:31 UTC 
*** Bug 17259 has been marked as a duplicate of this bug. ***
Comment 11 Bill Nottingham 2000-09-12 22:55:37 UTC 
*** Bug 17207 has been marked as a duplicate of this bug. ***
Comment 12 Dogar 2000-09-15 07:08:41 UTC 
easy way out
use
x86_serial_nr=1 
as kernel parameter during installation
or use
linux x86_serial_nr=1
from lilo after you have installed it, and then recomplie the kjernel after 
diabling cup_id
Note You need to log in before you can comment on or make changes to this bug.