Athlon 64X2 dual-core, MSI K8N Nforce4 Platinum, 4GB RAM, WD 10KRPM SATA 76GB Kernel version 2.6.14 Kernel compiles normally, however the Panic seems to occur anywhere from stage1 to early in stage 3 loading. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Is this problem new to 2.6.14? When you say stage1/3, are you referring to Gentoo installation?
Not anywhere from after detecting the initial hardware to stage 3 after initializing & mounting the file systems and starting to load other drivers. The system is fully functional with 2.6.13-r4, I was just trying to upgrade the kernel to 2.6.14
I'm sorry, that last response might be confusing... it should have read No, it's not during installation, but anywhere from stage 1 to stage 3 booting the system. Also, I'm using make menuconfig not genkernel if that makes any difference.
Still not really sure what you mean by stage1/3 while booting, are you using an initrd or something?
You should ensure that your BIOS is fully up-to-date. You can also try booting with kernel parameter "iommu=off"
I've updated to the latest bios, and recompiled the kernel, also I've tried the 2.6.14-ck1 kernel. Now it's consistant (with either of the 2.4.14 kernels that the error occurs right after "Mounting Local File Systems"
After some more testing here I've discovered if I pass mem=2048M to the kernel the system will boot. Also if I change the "H/W Memory Hold Remapping" and "S/W Memory Hole Remapping" to disabled in the BIOS to disabled the sytem will boot. (Either the HW or SW remapping needs to be turned on for the system to recognize all 4GB Ram, without it the POST test returns 3. something (varies) and the system once booted returns something between 2 and 3GB) In both cases, however, the mouse, once booted into X does not work properly. Moving the mouse produces what appear to be random clicks of the buttons along with sporadic movement of the cursor. (X11.org/KDE with a Logitech wireless keyboard/mouse combo hooked to the USB port.)
Please test vanilla-sources-2.6.14 if you haven't already, and then file a bug at http://bugzilla.kernel.org against Linux 2.6.14. Make clear that this problem is new to 2.6.14 (did not occur in 2.6.13), occurs on bootup and prevents the system from booting, and the workaround which you have found. Post the new bug URL here and we'll track it. Thanks.
