LinuxQuestions.org - Bad EIP value, IRQ conflicts, and Kernel Panics, oh my!

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - Bad EIP value, IRQ conflicts, and Kernel Panics, oh my! (https://www.linuxquestions.org/questions/linux-hardware-18/bad-eip-value-irq-conflicts-and-kernel-panics-oh-my-284319/)

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:

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...

Pretty much every Intel/Amd cpu MoBo uses ATX form factor. Since this is probably 90-95% of the cpu market almost every case is designed to hold ATX form factor mobos. Pretty much the only variation is mini-ATX (used for those little 'cube' shaped mini-computers)

Code:

[root@asdf flamesrock]# lspci -vv

00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 02)

        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-

        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-

        Latency: 0

        Region 0: Memory at d0000000 (32-bit, prefetchable) [size=64M]

        Capabilities: [a0] AGP version 2.0

                Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2

                Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>

        Capabilities: [c0] Power Management version 2

                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

                Status: D0 PME-Enable- DSel=0 DScale=0 PME-



00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (prog-if 00 [Normal decode])

        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-

        Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-

        Latency: 0

        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0

        Memory behind bridge: d6000000-d7ffffff

        Prefetchable memory behind bridge: d4000000-d5ffffff

        BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-

        Capabilities: [80] Power Management version 2

                Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

                Status: D0 PME-Enable- DSel=0 DScale=0 PME-



00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)

        Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge

        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-

        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-

        Latency: 0



00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10) (prog-if 8a [Master SecP PriP])

        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-

        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-

        Latency: 32

        Region 4: I/O ports at e000 [size=16]

        Capabilities: [c0] Power Management version 2

                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

                Status: D0 PME-Enable- DSel=0 DScale=0 PME-



00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)

        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-

        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-

        Interrupt: pin ? routed to IRQ 12

        Capabilities: [68] Power Management version 2

                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

                Status: D0 PME-Enable- DSel=0 DScale=0 PME-



00:0b.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)

        Subsystem: D-Link System Inc DFE-538TX 10/100 Ethernet Adapter

        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-

        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-

        Latency: 32 (8000ns min, 16000ns max)

        Interrupt: pin A routed to IRQ 11

        Region 0: I/O ports at ec00 [size=256]

        Region 1: Memory at d8000100 (32-bit, non-prefetchable) [size=256]

        Capabilities: [50] Power Management version 2

                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)

                Status: D0 PME-Enable- DSel=0 DScale=0 PME-



01:00.0 VGA compatible controller: nVidia Corporation NV5 [RIVA TNT2/TNT2 Pro] (rev 15) (prog-if 00 [VGA])

        Subsystem: nVidia Corporation RIVA TNT2 Pro

        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop+ ParErr- Stepping- SERR- FastB2B-

        Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-

        Latency: 32 (1250ns min, 250ns max)

        Interrupt: pin A routed to IRQ 10

        Region 0: Memory at d6000000 (32-bit, non-prefetchable) [size=16M]

        Region 1: Memory at d4000000 (32-bit, prefetchable) [size=32M]

        Expansion ROM at <unassigned> [disabled] [size=64K]

        Capabilities: [60] Power Management version 1

                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

        Capabilities: [44] AGP version 2.0

                Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4

                Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>

:confused: This must contain some useful information. Any ideas? :D

Quote:

Awesome :) I'd hate to replace a perfectly good motherboard, but its good to know that I can. The case is very nice.

-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.