HI all,
I have an FC4 machine that been running fine for several months using only eth0 and eth1. Today I tried to bring up eth2 for the first time and I got the messages below. Can someone tell what is going on here and more importantly how to fix it?
This is an FC4 machine running 2.6.12-1.1456_FC4 kernel.
Sep 28 20:50:24 taz kernel: irq 10: nobody cared! Sep 28 20:50:24 taz kernel: [<c0151e74>] __report_bad_irq+0x24/0x7f Sep 28 20:50:24 taz kernel: [<c0151f46>] note_interrupt+0x59/0x83 Sep 28 20:50:24 taz kernel: [<c0151220>] __do_IRQ+0x1f7/0x347 Sep 28 20:50:24 taz kernel: [<c0105b2d>] do_IRQ+0x4a/0x82 Sep 28 20:50:24 taz kernel: ======================= Sep 28 20:50:24 taz kernel: [<c0103c1e>] common_interrupt+0x1a/0x20 Sep 28 20:50:24 taz kernel: [<c01286ec>] __do_softirq+0x2c/0x8a Sep 28 20:50:24 taz kernel: [<c0105c39>] do_softirq+0x3e/0x42 Sep 28 20:50:24 taz kernel: ======================= Sep 28 20:50:24 taz kernel: [<c0105b34>] do_IRQ+0x51/0x82 Sep 28 20:50:24 taz kernel: [<c0103c1e>] common_interrupt+0x1a/0x20 Sep 28 20:50:24 taz kernel: [<c024c6fe>] acpi_processor_idle+0x10e/0x272 Sep 28 20:50:24 taz kernel: [<c01010a6>] cpu_idle+0x34/0x4c Sep 28 20:50:24 taz kernel: [<c04256ea>] start_kernel+0x164/0x1be Sep 28 20:50:24 taz kernel: [<c04252e5>] unknown_bootoption+0x0/0x1b6 Sep 28 20:50:24 taz kernel: handlers: Sep 28 20:50:24 taz kernel: [<c02d3dde>] (usb_hcd_irq+0x0/0x52) Sep 28 20:50:24 taz kernel: [<de8868f8>] (rhine_interrupt+0x0/0x25c [via_rhine]) Sep 28 20:50:24 taz kernel: Disabling IRQ #10 Sep 28 20:50:28 taz kernel: printk: 1 messages suppressed. Sep 28 20:50:28 taz kernel: martian source 67.62.182.165 from 67.62.182.1, on dev eth2 Sep 28 20:50:28 taz kernel: ll header: ff:ff:ff:ff:ff:ff:00:09:43:10:be:80:08:06 Sep 28 20:50:30 taz kernel: NETDEV WATCHDOG: eth1: transmit timed out Sep 28 20:50:30 taz kernel: eth1: Transmit timed out, status 1003, PHY status 786d, resetting... Sep 28 20:50:30 taz kernel: eth1: link up, 100Mbps, full-duplex, lpa 0x45E1 Sep 28 20:50:34 taz kernel: martian source 67.62.181.186 from 67.62.181.1, on dev eth2 Sep 28 20:50:34 taz kernel: ll header: ff:ff:ff:ff:ff:ff:00:09:43:10:be:80:08:06 Sep 28 20:50:37 taz kernel: loop: loaded (max 8 devices) Sep 28 20:50:37 taz kernel: martian source 67.62.181.186 from 67.62.181.1, on dev eth2 Sep 28 20:50:37 taz kernel: ll header: ff:ff:ff:ff:ff:ff:00:09:43:10:be:80:08:06 Sep 28 20:50:41 taz kernel: irq 10: nobody cared!
I am not sure what information to include but lspci -vv shows the following:
(taz pts1) # lspci -vv 00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266] Subsystem: VIA Technologies, Inc.: Unknown device aa01 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: 8 Region 0: Memory at d0000000 (32-bit, prefetchable) [size=128M] 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=x4 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. VT8633 [Apollo Pro266 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: dc000000-ddffffff Prefetchable memory behind bridge: d8000000-dbffffff Secondary status: 66Mhz+ FastB2B- ParErr- DEVSEL=medium >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:0f.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev 8b) Subsystem: VIA Technologies, Inc.: Unknown device 0106 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 (750ns min, 2000ns max), Cache Line Size 08 Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at d000 [size=256] Region 1: Memory at df003000 (32-bit, non-prefetchable) [size=256] Capabilities: [44] 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:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc.: Unknown device aa01 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 A routed to IRQ 10 Region 4: I/O ports at d400 [size=32] Capabilities: [80] 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-
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc.: Unknown device aa01 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 B routed to IRQ 15 Region 4: I/O ports at d800 [size=32] Capabilities: [80] 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-
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc.: Unknown device aa01 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 C 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=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI]) Subsystem: VIA Technologies, Inc. USB 2.0 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 11 Region 0: Memory at df000000 (32-bit, non-prefetchable) [size=256] Capabilities: [80] 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-
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge Subsystem: VIA Technologies, Inc.: Unknown device aa01 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 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:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) Subsystem: VIA Technologies, Inc.: Unknown device aa01 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 Interrupt: pin A routed to IRQ 10 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:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235 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 (750ns min, 2000ns max), Cache Line Size 08 Interrupt: pin A routed to IRQ 10 Region 0: I/O ports at e400 [size=256] Region 1: Memory at df001000 (32-bit, non-prefetchable) [size=256] Capabilities: [40] 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:13.0 Ethernet controller: Linksys NC100 Network Everywhere Fast Ethernet 10/100 (rev 11) 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 A routed to IRQ 11 Region 0: I/O ports at e800 [size=256] Region 1: Memory at df002000 (32-bit, non-prefetchable) [size=1K]
00:14.0 Ethernet controller: Linksys NC100 Network Everywhere Fast Ethernet 10/100 (rev 11) Subsystem: Linksys: Unknown device 0574 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 (16000ns min, 32000ns max), Cache Line Size 08 Interrupt: pin A routed to IRQ 15 Region 0: I/O ports at ec00 [size=256] Region 1: Memory at df004000 (32-bit, non-prefetchable) [size=1K] Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=100mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics (rev 03) (prog-if 00 [VGA]) Subsystem: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics 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 (500ns min) Interrupt: pin A routed to IRQ 10 Region 0: Memory at d8000000 (32-bit, prefetchable) [size=64M] Region 1: Memory at dc000000 (32-bit, non-prefetchable) [size=16M] Capabilities: [60] 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- Capabilities: [70] 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>
(taz pts1) #
Is this indicative of some kind of hardware conflict or a bug? I do not understand what is going on here, so any help would be appreciated.
Regards,
Tom Diehl tdiehl@rogueind.com Spamtrap address mtd123@rogueind.com
On Wed, 28 Sep 2005, Peter Arremann wrote:
On Wednesday 28 September 2005 21:11, Tom Diehl wrote:
Sep 28 20:50:24 taz kernel: irq 10: nobody cared!
Does this happen without acpi? what if you force pci irq routing?
Not sure. Will try it but please tell me the proper incantation for force pci irq routing? IIRC acpi=off will turn acpi off, right??
Regards,
Tom Diehl tdiehl@rogueind.com Spamtrap address mtd123@rogueind.com
On Wed, 28 Sep 2005, Peter Arremann wrote:
On Wednesday 28 September 2005 21:11, Tom Diehl wrote:
Sep 28 20:50:24 taz kernel: irq 10: nobody cared!
Does this happen without acpi? what if you force pci irq routing?
If by that you mean, boot with acpi=off or pci=noacpi then yes I still get the above error. Since I am not using eth3 I rm'd it and the irq switched to 11 but I think that is to be expected.
If there is some other boot parameter you would like me to try please let me know.
Regards,
Tom Diehl tdiehl@rogueind.com Spamtrap address mtd123@rogueind.com