Plantage lie aux IRQ ... ?

Startseite

Nachricht beantworten
Autor: Jerome Kieffer
Datum:  
To: guilde
Betreff: Plantage lie aux IRQ ... ?

Salut à tous,

je suis bien embêté avec une machine neuve qui plante très
régulièrement avec des problèmes d'IRQ. Le plus surprenant
c'est qu'eth0 ne partage pas son IRQ. C'est une interface reseau
intégrée sur la carte mère, avec un chip nForce3 (driver forcedeth)

NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out, tx_status 00 status e601.
diagnostics: net 0cd8 media 8880 dma 0000003a fifo 8000
eth0: Interrupt posted but not delivered -- IRQ blocked by another device?
Flags; bus-master 1, dirty 6678310(6) current 6678310


Si vous avez des idées ou des pistes, je suis preneur car la-dite
machine est en production :(
Merci de vos lumières (les miennes sont éteintes)


Autres infos :

kernel 2.6.20 compilé à la main,

/proc/interrupts 
           CPU0       
  0:      33627   IO-APIC-edge      timer
  1:         10   IO-APIC-edge      i8042
  6:          3   IO-APIC-edge      floppy
  8:          1   IO-APIC-edge      rtc
  9:          0   IO-APIC-fasteoi   acpi
 12:          4   IO-APIC-edge      i8042
 14:      11911   IO-APIC-edge      ide0
 15:      49023   IO-APIC-edge      ide1
 16:          0   IO-APIC-fasteoi   ehci_hcd:usb3
 17:      11858   IO-APIC-fasteoi   ohci_hcd:usb1, eth2
 18:          0   IO-APIC-fasteoi   ohci_hcd:usb2
 19:        233   IO-APIC-fasteoi   ohci1394
 20:       1799   IO-APIC-fasteoi   eth0
 21:        110   IO-APIC-fasteoi   eth1
NMI:          0 
LOC:      33596 
ERR:          1
MIS:          0


lspci :
00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1)
00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1)
00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2)
00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2)
00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2)
00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2)
00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
02:06.0 Mass storage controller: Triones Technologies, Inc. HPT366/368/370/370A/372/372N (rev 03)
02:07.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 30)
02:08.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev 86)
02:09.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev 5c)
02:0a.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link)


logs:
May 19 21:15:52 islay kernel: NETDEV WATCHDOG: eth0: transmit timed out
May 19 21:15:52 islay kernel: eth0: transmit timed out, tx_status 00 status e601.
May 19 21:15:52 islay kernel: diagnostics: net 0cd8 media 8880 dma 0000003a fifo 8000
May 19 21:15:52 islay kernel: eth0: Interrupt posted but not delivered -- IRQ blocked by another device?
May 19 21:15:52 islay kernel: Flags; bus-master 1, dirty 6678310(6) current 6678310(6)
May 19 21:15:52 islay kernel: Transmit list 00000000 vs. dfa415c0.
May 19 21:15:52 islay kernel: 0: @dfa41200 length 80000067 status 00010067
May 19 21:15:52 islay kernel: 1: @dfa412a0 length 80000067 status 00010067
May 19 21:15:52 islay kernel: 2: @dfa41340 length 80000067 status 00010067
May 19 21:15:52 islay kernel: 3: @dfa413e0 length 80000067 status 00010067
May 19 21:15:52 islay kernel: 4: @dfa41480 length 80000067 status 80010067
May 19 21:15:52 islay kernel: 5: @dfa41520 length 80000067 status 80010067
May 19 21:15:52 islay kernel: 6: @dfa415c0 length 80000067 status 00010067
May 19 21:15:52 islay kernel: 7: @dfa41660 length 80000067 status 00010067
May 19 21:15:52 islay kernel: 8: @dfa41700 length 80000067 status 00010067
May 19 21:15:52 islay kernel: 9: @dfa417a0 length 80000067 status 00010067
May 19 21:15:52 islay kernel: 10: @dfa41840 length 80000067 status 00010067
May 19 21:15:52 islay kernel: 11: @dfa418e0 length 80000067 status 00010067
May 19 21:15:52 islay kernel: 12: @dfa41980 length 80000067 status 00010067
May 19 21:15:52 islay kernel: 13: @dfa41a20 length 80000067 status 00010067
May 19 21:15:52 islay kernel: 14: @dfa41ac0 length 80000067 status 00010067
May 19 21:15:52 islay kernel: 15: @dfa41b60 length 80000067 status 00010067
May 19 21:15:52 islay kernel: eth0: Resetting the Tx ring pointer.

A++



--
Jérôme KIEFFER : http://www.terre-adelie.org
À vélo, prendre une rue à contre-sens est moins dangeureux
que prendre un boulevard dans le sens légal. À qui la faute ?