[Cialug] EIP Value
morej at alliancetechnologies.net
Thu Jan 19 10:35:20 CST 2006
I can't tell you what the likely culprit is, but instead of moving them
in and out I suggest the following:
1) Remove all cards and try the live CD.
2a) If this does not solve the problem, replace your CMOS battery, reset
BIOS to defaults, and retry.
2b) If this does solve the problem, add the cards in one by one and
3a) If this does not solve the problem start disable all on-board items
3b) If this does solve the problem, put all the cards back in and test
4a) If this does not solve the problem, get a new mother board.
4b) If this does solve the problem, start enabling items one by one and
Hope this helps,
-Josh More, RHCE, CISSP, NCLP
morej at alliancetechnologies.net
>>>sthiessen at passitonservices.org 01/19/06 9:34 am >>>
-----BEGIN PGP SIGNED MESSAGE-----
I took out the network card and the EIP error is still there.
It is before the BIOS driver is detected and just after the
autoconfiguring of devices. This is a Linux bootable CD that has
imaging software setup. I just used it on another Windows computer and
started working on a generic home-built computer that we had donated
to us. I wanted to back up the partition of this other clone computer
before playing around with it so I could restore it if needed. It has
Win 98 with some files. We had used it for any odds and ends Windows
stuff. Now, I am planning to put Linux on it, but I wanted to be able
to restore it to Win98 if needed.
But if I can't seem to get it up with a CD Linux, how would a regular
Anyway, it seems to be related to modprobe.old. It has EFLAGS then a
set of values for eax, ebx, ecx, edx, esi, edi, dbp, esp, ds, es, ss.
Then mentions Process modprobe.old Then Stack: with 8x3 matrix of hex
values and then a Call Trace section with Code: Bad EIP value after it.
The NIC is out. I have a video card, TV card, sound card, and SCSI
card still in the system. Would you guys have any idea which is most
likely to be the problem? If not, I will just move them in and out to
see what happens.
On Jan 19, 2006, at 9:14, Paul Gray wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>On Thu, Jan 19, 2006 at 08:58:25AM -0600, Stuart Thiessen wrote:
>>-----BEGIN PGP SIGNED MESSAGE-----
>>What would cause a bootup sequence to fail during an autoconfiguring
>>process and end up with a call trace and a CODE: Bad EIP value? Does
>>that have anything to do with the network card?
>The Bad EIP message is just a symptom. It indicates that the CPU
>to store the executable instruction pointer for some reason. Where is
>bootup process just before the system goes into panic?
>Typically, a bad EIP message means that the system can't initialize a
>piece of hardware, so I wouldn't ruled out your network card. Can you
>and boot up successfully?
>Paul Gray -o)
>323 Wright Hall /\\
>University of Northern Iowa \_V
>Message void if penguin violated ... Don't mess with the penguin
>No one says, Hey, I can't read that ASCII attachment ya sent me.
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.1 (GNU/Linux)
>-----END PGP SIGNATURE-----
>Cialug mailing list
>Cialug at cialug.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
-----END PGP SIGNATURE-----
Cialug mailing list
Cialug at cialug.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cialug