Bad EIP value

I configed and built a new 2.6.3 kernel today and when I attempt to boot with it I get a message:
"Code: Bad EIP value <0> kernel panic". I scouted around I can't seem to find an obvious explanation. I don't believe that I made any horrendous decisions configuring the kernel, but I can't discount that. But can anyone provide an off the cuff take on what could be wrong?

http://www.linuxforums.org/forum/viewtopic.php?t=5321

http://216.239.41.104/linux?q=cache:...ng_en&ie=UTF-8


Sounds like a toughie. Good luck.


John

Hmmm, the only time I got this particular error message........

Bad EIP value

I was preparing to install Slackware 9.1 on a P4 1.5 GHZ box, My Wingman Joystick was plugged into a USB port........Slack would not install until I un-plugged the joystick........kinda weird......

Originally posted by 320mb Hmmm, the only time I got this particular error message........ Bad EIP value I was preparing to install Slackware 9.1 on a P4 1.5 GHZ box, My Wingman Joystick was plugged into a USB port........Slack would not install until I un-plugged the joystick........kinda weird......

Hmpf.. I just had almost the exact same problem!
Differences were that the device Slack didn't like was a Logitech optical USB mouse, and that I run on a AMD box. Well it works now since I saw your post and unplugged the mouse first thing I tried

I have had problems with certain devices plugged into the USB port when booting too.


John

Unable to handle kernel paging request at virtual address d4829ac4
printing eip:
d4829ac4
*pde = 13c8b067
*pte = 00000000
0ops: 0000
CPU: 0
EIP: 0010:[<d4829ac4>] Not tainted
EFLAGS: 0001086
eax: ffffff92 ebx: c138f600 ecx: 00000005 edx: c13b5560
esi: ffffffff edi: c139b900 ebp: d3d6ee0 esp: d3d6fea4
ds: 0018 es:0018 ss:0010
Process khubd (pid: 23, stackpage=d3d6f000)
Stack: c138f600 00000004 c13aa920 0000003f 00000000 d3d6feba c13aa920 00000072
00000000 c138c000 c13933f0 c139b920 d482c600 d482c660 c138f600 00000000
d4829cd3 c138f600 00000000 d482c600 d482c660 c139b920 00000000 d482dde9
Call Trace: [<d480dde9>] [<d481ad60>] [<d480e167>] [<d48100fc>] [<d4811a47>]
[<d4819440>] [<d4811de5>] [<d4811e65>] [<c0107416>] [<d4811e30>]

Code: Bad EIP value.

Ill try to unplug all usb devices and try a install on

HP Pavilion 6830
700Mhz
384Mb pc133 Sdram
20GB HD WD

let you know what happens

ty all

thats it darn those usb devices

Is there anyway to change a BIOS setting in order to have this not happen
on a Slackware install + usb devices
??????

ty all

Does booting it with the kernel option "nousb" do anything?

unpluging usb devices allowed OS install...


I just got to remember this LOL


sry all ty

A bad EIP value could be as little as a jumper piece in the wrong slot or removed...

If all else fails look inside the computer for the CMOS memory on the motherboard. Somewhere near there you should find 3 poles and a jumper piece. If there isn't a jumper piece that may be your problem. If there is one try switching it between the poles.

This may reset your CMOS memory doing so... Someone with better a computer backround back me up on this one.

I see little pattern with this error. Mandrake/Laptop users encounter a problem with the PNP module of the BIOS, requiring the BIOS setting for PNP OS to be set to "NO". The others of you here seem to have a USB problem.

I have no USB ports, and I have no option in the BIOS to disable PNP. I can individually set information to ISA or PCI or PCI/ISA PNP and I have made sure none of these are PNP enabled, however I still encounter the problem.

I have a very old P166, in a Amptron PM8600 motherboard with 64MB of RAM. A 40GB HDD, CD Burner, and CD-ROM drive. TSENG Labs 4000 (4100??) video card (PCI), SMC1211(TX) PCI Ethernet Card, and standard ISA 16-bit SoundBlaster (yup, an original).

Install goes fine as with the Mandrake installs of the same error, but during boot-up it hangs at "Enabling local Filesystem quotas". After 10mins (and the rest) it finally spits out a whole lot of garble ending with Bad EIP Value.

I do get ACPI: Unable to locate RSDP" at the beginning of the boot-up. But other than that nothing appears to go wrong until the local filesystem quotas are supposed to be enabled.