From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Description of problem:
Fedora Core 3 test 1 installs fine off CD-ROM; after reboot the kernel
immediately panics with a Kernel Oops. Install CD kernel ran fine.
Machine is a Viglen Genie Pentium-4 machine based on the intel i865G
chipset (intel D865GLC motherboard, Pentium-4 2.8E GHz (800MHz FSB),
512MB DDR400 RAM).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Fedora Core 3 test 1
2. Boot from HD
Actual Results: Kernel oops at very early stage of boot. Machine
Expected Results: Kernel boots...
The following is the output (written down by hand, but checked
carefully against printout before clearing):
[Linux-initrd @ 0x1eef1000, 0x2e654 bytes]
Uncompressing Linux.... OK, booting the kernel
ACPI: S3 and PAE do not like each other for now, S3 disabled
Unable to handle kernel NULL pointer dereference at virtual address
*pde = 00003001
Oops: 0000 [#1]
Modules linked in:
EIP: 0060:[<00000008>] Not tainted
EFLAGS: 00010202 (2.6.7-1.478smp)
EIP is at 0x8
eax: 00000000 ebx: 00000000 ecx: 00000000 edx: 00000000
esi: 000003e8 edi: 021c4e55 edp: 021cdfd4 esp: 20ebaf9c
ds: 0060 es: 0287 ss: 0068
Process swapper: (pid: 1, threadinfo=20eba000 task=20e8b730)
Stack: 00000001 021d8c0c 00000000 00000000 00000000 021d1dfb
023ae028 0239b64e 000000f4 02436c40 0239b72b 023897ea
021004dd 00000000 00000000 02100419 00000000 021041f1
[<021d8c0c>]<1>Unable to handle kernel NULL pointer dereference
I've just seen an identical fault (same EIP etc) on an Intel i875PBZ
based motherboard. Really not having much luck with these intel
chipsets and Fedora Core 3 test 1. I'm currently trying the 2.6.8-520
kernel on that machine....
Added Kernel 2.6.8-520 to the kickstart install and once rekicked it
now boots correctly and normally on the i875PBZ machine; however the
system remains unusable due to bug #130004 (NFS client Oops).
please close this bug
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
As mentioned in comment #2, the 2.6.8-520 kernel fixed this bug. The machines
concerned are currently operational with production FC3 with no problems.