From: "Michael A. Kangin" <mak@complife.ru> To: ALT Linux Community general discussions <community@lists.altlinux.org> Subject: [Comm] IRQ handler type mismatch Date: Fri, 26 Dec 2008 10:57:26 +0300 Message-ID: <200812261057.26503.mak@complife.ru> (raw) Добрый день. При очередной перезагрузке подготавливаемого для работы рутера получил вдруг неподнятую сеть и ругань в логах: e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0 e1000e: Copyright (c) 1999-2007 Intel Corporation. ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 217 PCI: Setting latency timer of device 0000:00:19.0 to 64 Intel(R) PRO/1000 Network Driver - version 7.2.7-k2-NAPI Copyright (c) 1999-2006 Intel Corporation. .... 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:15:17:28:89:5c 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection 0000:00:19.0: eth0: MAC: 5, PHY: 6, PBA No: 0070ff-0ff .... ACPI: PCI Interrupt 0000:03:02.0[A] -> <6>ACPI: PCI Interrupt 0000:00:1a.0 [A] -> GSI 18 (level, low) -> IRQ 225 GSI 18 (level, low) -> IRQ 0 ... e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection .... IRQ handler type mismatch for IRQ 0 [<c0104612>] dump_trace+0x69/0x1af [<c0104770>] show_trace_log_lvl+0x18/0x2c [<c0104d24>] show_trace+0xf/0x11 [<c0104e23>] dump_stack+0x17/0x2f [<c014c395>] setup_irq+0x175/0x188 [<c014c424>] request_irq+0x7c/0x98 [<f8bdf258>] e1000_request_irq+0x97/0xd0 [e1000] [<f8bdfff8>] e1000_open+0x8a/0xd8 [e1000] [<c02429c0>] dev_open+0x2b/0x62 [<c0241377>] dev_change_flags+0x46/0xe3 [<c02807f6>] devinet_ioctl+0x250/0x553 [<c023815d>] sock_ioctl+0x198/0x1bc [<c017bd27>] do_ioctl+0x1f/0x63 [<c017bfb5>] vfs_ioctl+0x24a/0x25c [<c017bffa>] sys_ioctl+0x33/0x4d [<c0102d57>] syscall_call+0x7/0xb DWARF2 unwinder stuck at syscall_call+0x7/0xb Leftover inexact backtrace: ======================= e1000: lan: e1000_request_irq: Unable to allocate interrupt Error: -16 После rmmod/повторного modprobe сеть вроде заработала. Следующая перезагрузка прошла нормально. Как с таким бороться? 2.6.18-ovz-smp-alt26.M40.2 00:19.0 Ethernet controller: Intel Corporation Unknown device 10bd (rev 02) Subsystem: Intel Corporation Unknown device 34d0 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 Interrupt: pin A routed to IRQ 217 Region 0: Memory at 81a00000 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at 81a20000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at 20e0 [size=32] Capabilities: [c8] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [e0] #13 [0306] 03:02.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet Controller (rev 05) Subsystem: Intel Corporation Unknown device 34d0 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 (63750ns min), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 225 Region 0: Memory at 81920000 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at 81900000 (32-bit, non-prefetchable) [size=128K] Region 2: I/O ports at 1000 [size=64] Expansion ROM at fffe0000 [disabled] [size=128K] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [e4] PCI-X non-bridge device Command: DPERE- ERO+ RBC=512 OST=1 Status: Dev=00:00.0 64bit- 133MHz- SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=8 RSCEM- 266MHz- 533MHz- # ethtool -i lan driver: e1000 version: 7.2.7-k2-NAPI firmware-version: N/A bus-info: 0000:03:02.0 # ethtool -i inet driver: e1000e version: 0.2.0 firmware-version: 1.3-0 bus-info: 0000:00:19.0 -- wbr, Michael A. Kangin
reply other threads:[~2008-12-26 7:57 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=200812261057.26503.mak@complife.ru \ --to=mak@complife.ru \ --cc=community@lists.altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux Community general discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 community community/ http://lore.altlinux.org/community \ mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com public-inbox-index community Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.community AGPL code for this site: git clone https://public-inbox.org/public-inbox.git