Bad EIP value, IRQ conflicts, and Kernel Panics, oh my!
I have this problem which is causing me huge amounts of nausea:
I'm constantly getting kernel panics indicating a 'bad eip value' and segmentation faults...which probably originate from the same source. It basically says that it can't sync. The reason I've isolated after googling and confirming that my ram is in perfect shape (with memtest86) is that my motherboard and cpu, an amd duron k7 (tbird) assign the irq values in a weird way that the linux kernel doesn't like. So there may be conflicts when two pieces of hardware share an irq value which causes this to happen. The advice was to turn acpi on, PnP off, and use a newer kernel. All of which I tried. I'm getting the problem less frequently, but its still a huge problem. I've also unplugged the floppy drive, left only a single stick of ram inside, and moved the network card to a different pci slot to minimize irq conlicts, but the problem remains. Do any of you have experience with this sort of thing, and if so, what would you do to remedy it? I know very little about what irq is or how to make linux play fair with them. All I know is that 4 different distros, spanning many different kernels, including freeBSD have failed. The only ones I could get running on the machine were gentoo and tinysofa, and tinysofa gave me the fewest problems. Oh - and if it is a dying hardware problem, and not the way linux is interacting with the hardware, I'm curious about replacing the motherboard/cpu. Do most motherboards screw in perfectly with the case (basically, are the dimensions the same on all of them.) Or would I need to buy a case tailoired to the motherboard/cpu, since I'd like to hang on to the other pieces, (with the possibly excpetion of the power supply.) Where is a good place to get one if I'm not interested in something top of the line and electron hungry (this is a server) The amd tbird would be perfect if only I could get it to work... (if it helps, the bios is a spacewalker 'award' one) -thanks |
This is usually caused by a bad memory stick.
|
can you run lspci -vv and post the output? Maybe track down the irq conflict...
Quote:
|
Code:
[root@asdf flamesrock]# lspci -vv Quote:
-thanks |
No IRQ conflicts there... you can also try "cat /proc/interrupts" and see if any of them are there twice.
Did you try adding "nobiospnp" to the kernel command line? If that doesn't work I'm out of ideas...sorry. |
Thanks
I've got half of my reply in this thread http://www.linuxquestions.org/questi...03#post1446903 Sorry if this sounds clueless, but could it be that on certain boots, the irq values are in greater conflict with eachother than on other boots? Reason I ask is because most of the 'Bad EIP's' happen at bootup. Anyways, thanks again for your help. Its behaving much better now. |
All times are GMT -5. The time now is 07:28 PM. |