Kernel Panic - My eternal problem

BlueH2O · #1 18th April 2006, 03:00 PM

This happens to me anywhere from 1 hour to 1 week after boot up.. My system stops responding and when I get a chance to go to the console and take a look I'm greeted with this:

Code:

1
	e04371a0 0000000a bfde04c8 c01211fb f689af98 00200046 00000000 c01050e6
Call Trace:
 [<c02e597d>] tcp_write_timer+0x0/0x5fc      [<c01211fb>] __do_softirq+0x3e/0x8a
 [<c01050e6>] do_softirq+0x3e/0x48    <0> ========================
 [<c0105077>] do_IRQ+0x51/0x82
 [<c01036e2>] common_interrupt+0x1a/0x20     <0>Code: e8 a2 d9 1e 00 0b 75 14 89
d8 ff d7 8b 45 14 39 c6 74 20 89 44 24 0c 89 74 24 08 89 7c 24 04 c7 04 24 14 e5
 32 c0 e0 44 85 ff ff <0f> 0b d8 01 8a d9 32 c0 b8 80 84 43 c0 e8 39 1e 00 8b
 4c 24
Continuing in 1 seconds.
 <0>Kernel panic - not syncing: Fatal exception in interrupt
 [<c011c0cc>] panic+0x45/0x1c9
 [<c0312472>] _spin_unlock_irqrestore+0xa/0xc     [<c0104420>] die+0x22b/0235
 [<c0104702>] do_invalid_op+0x0/0xab     [<c01047a4>] do_invalid_op+0xa2/0xab
 [<c0124aec>] run_timer_softirq+0xfc/0x1c8     [<c011cf79>] vprintk+0x2bb/0x372
 [<c0312433>] _spin_lock_irqsave+0x9/0xd     [<c0124173>] lock_timer_base+0x15/0
x2f
 [<c0124c3a>] __mod_timer+0x82/0x99     [<c01037cf>] error_code+0x4f/0x54
 [<c02e597d>] tcp_write_timer+0x0/0x5fx     [<c0124aec>] run_timer_softirq+0xfc/
0x1c8
 [<c02e597d>] tcp_write_timer+0x0/0x5fc     [<c01211fb>] __do_softirq+0x3e/0x8a
 [<c01050e6>] do_softirq+0x3e/0x48     =======================
 [<c0105077>] do_IRQ+0x51/0x82
 [<c01036e2>] common_interrupt+0x1a/0x20

Does anyone have any insight into this?

This has happened to me with different RAM, and three different NIC cards.

Fedora Core 4 kernel 2.6.16 on AMD Athlon

tashirosgt · #2 18th April 2006, 04:27 PM

It's still worth running memtest86 since you might have some BIOS setting that is incompatible with the type of memory. Do the logs show anything (e.g. /var/log/messages)?

BlueH2O · #3 18th April 2006, 04:29 PM

I have already run memtest86 and found no problems. There's nothing in the logs except the reboot message when the system comes back up.

BlueH2O · #4 20th April 2006, 07:23 PM

Does anyone have any additional thoughts on this, or perhaps a way I might gather more useful information if (and when) this occurs again?

VictorienSardou · #5 20th April 2006, 07:31 PM

what type of machine are you running it on?
have you unplugged and replugged all the cables in the pc?
have you done 'cat /proc/interrupts' to see what hardware is sharing which interrupt?

BlueH2O · #6 20th April 2006, 07:43 PM

Cables are all good, everything firmly seated.

Code:

[root@arturo ~]# uname -a
Linux arturo 2.6.16-1.2069_FC4 #1 Tue Mar 28 12:19:10 EST 2006 i686 athlon i386 GNU/Linux
[root@arturo ~]# cat /proc/interrupts
           CPU0
  0:   48475937          XT-PIC  timer
  1:         14          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  5:          0          XT-PIC  uhci_hcd:usb1, uhci_hcd:usb2
  7:          0          XT-PIC  parport0
  8:          1          XT-PIC  rtc
 10:    4038959          XT-PIC  eth0
 11:         26          XT-PIC  aic7xxx
 12:        104          XT-PIC  i8042
 14:     126329          XT-PIC  ide0
 15:    1736055          XT-PIC  ide1
NMI:          0
LOC:          0
ERR:          0
MIS:          0

tashirosgt · #7 21st April 2006, 04:55 AM

This is probably a digression, but it seems a good time to ask what is the different in interrupt "types" between XT_PIC and IO_APIC? On my single processor Athlon Nforce 4 based system
(uname -a
autry.myhouse.org 2.6.16-1.2080_FC5 #1 Tue Mar 28 03:38:34 EST 2006 i686 athlon i386 GNU/Linux)
all my interrupts are type IO_APIC.

[I'll edit-in the answer to this question]
According to:
http://72.14.203.104/search?q=cache:...ns/sa-wiet.pdf
"Two types of interrupt controllers are available on x86 platforms:
the PIC (Intel 8259A, or XT-PIC) and
the Advanced PIC (APIC) system. "

VictorienSardou · #8 21st April 2006, 02:29 PM

well, there are no obvious IRQ conficts.
doing '/sbin/lspci -vv' will enable identification of memory range and IO port conflicts but i think is unlikely thats the problem.
can irq 10 be disabled in the BIOS to force the ethernet card to be assigned to a different IRQ?

BlueH2O · #9 21st April 2006, 02:45 PM

Code:

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,x4
                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: d4000000-d5ffffff
        Prefetchable memory behind bridge: d6000000-d6ffffff
        Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
        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:03.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U
        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 (2000ns min, 2000ns max), Cache Line Size 08
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at d000 [disabled] [size=256]
        Region 1: Memory at d8101000 (32-bit, non-prefetchable) [size=4K]
        [virtual] Expansion ROM at 50100000 [disabled] [size=64K]

00:04.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 05)
        Subsystem: Intel Corporation EtherExpress PRO/100+
        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 (2000ns min, 14000ns max), Cache Line Size 08
        Interrupt: pin A routed to IRQ 10
        Region 0: Memory at d8100000 (32-bit, prefetchable) [size=4K]
        Region 1: I/O ports at d400 [size=32]
        Region 2: Memory at d8000000 (32-bit, non-prefetchable) [size=1M]
        [virtual] Expansion ROM at 50000000 [disabled] [size=1M]
        Capabilities: [dc] 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-

00:14.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:14.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 d800 [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:14.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10) (prog-if 00 [UHCI])
        Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
        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, Cache Line Size 08
        Interrupt: pin D routed to IRQ 5
        Region 4: I/O ports at dc00 [size=32]
        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:14.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10) (prog-if 00 [UHCI])
        Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
        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, Cache Line Size 08
        Interrupt: pin D routed to IRQ 5
        Region 4: I/O ports at e000 [size=32]
        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:14.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-
        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-

01:00.0 VGA compatible controller: nVidia Corporation NV4 [RIVA TNT] (rev 04) (prog-if 00 [VGA])
        Subsystem: Creative Labs Graphics Blaster CT6710
        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 11
        Region 0: Memory at d4000000 (32-bit, non-prefetchable) [size=16M]
        Region 1: Memory at d6000000 (32-bit, prefetchable) [size=16M]
        [virtual] Expansion ROM at d5000000 [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 1.0
                Status: RQ=16 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>

I'm currently 9 miles away from this machine so I'll take a look at the BIOS later.

VictorienSardou · #10 22nd April 2006, 03:56 PM

i'm not sure why the Nvidia TNT card on irq 11 was not included in the list of interrupts earlier.
anyway, which release of FC are you using?
which Intel module are you using e100 or eepro100?

***Firewing1*** · #11 22nd April 2006, 04:11 PM

Have you tried installing FC5? Maybe it fixes the issue, it has newer kernels.
Firewing1

BlueH2O · #12 22nd April 2006, 06:45 PM

Well I've been meaning to do the update to core 5, mabye I should just get it over with.

VictorienSardou · #13 23rd April 2006, 09:04 PM

Ahh... sounds like a windows 'support' response.
"oooo... not running XP, thats your problem mate."