Bug 25174

Summary: kernel panic after first boot
Product: [Retired] Red Hat Linux Reporter: maikcat
Component: kernelAssignee: Michael K. Johnson <johnsonm>
Status: CLOSED ERRATA QA Contact: Brock Organ <borgan>
Severity: high Docs Contact:
Priority: medium    
Version: 6.2CC: tjc
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: 2001-02-19 10:06:11 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 maikcat 2001-01-29 09:54:28 UTC
after installing RH6.2 on a AMD based computer
after reboot and in the very beggining of the
loading proccess (trying to disable CPUID feature..)
i get Kernel panic and a mem dump and i can do nothing else...
my CFG is
AMD athlon 900 MHz
ASUS A7V motherboard BIOS 1004D
128MB dimm 133
Creative geforce2
HDD western digital 20GB (ata100,7200rpm)
thank you in advance,michael

Comment 1 Need Real Name 2001-02-19 08:45:35 UTC
work around coming up with another system (try a small 6.1), mount your 6.2
system, build a new kernel without feature _cpu id disable_ (from 6.1 2.2.12 or
6.2 2.2.14), copy the kernel, the corresponding modules and all boot stuff to
the 6.2 hard disk and make a bootdisk (mkbootdisk). then, boot your 6.2 from
floppy disk with the new kernel, rebuild your 2.2.14 kernel, edit /etc/lilo.conf
and run lilo.
rem: with kernel 2.2.14 i wasn't able to get a working nfs server yet (nfs
modules failed). with kernel versions higher than 2.2.14 (2.2.16 up to 2.4) the
kernel panics with aic78xxx module (on 64 bit 29160 host adapter)

Comment 2 Need Real Name 2001-02-19 10:06:08 UTC
looking around in kernel faq results in:
http://www.redhat.com/support/docs/tips/ThunderBird-Duron.html


Comment 3 Michael K. Johnson 2001-02-21 16:28:22 UTC
Since this is fixed in errata and in 7.0 and has a web page at Red Hat
explaining how to work around it to get 6.2 running, I'm going to
resolve this as fixed in errata.