From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261422AbUGEUIg (ORCPT ); Mon, 5 Jul 2004 16:08:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261451AbUGEUIg (ORCPT ); Mon, 5 Jul 2004 16:08:36 -0400 Received: from slimnet.xs4all.nl ([194.109.194.192]:53210 "EHLO slimnas.slim") by vger.kernel.org with ESMTP id S261422AbUGEUIc (ORCPT ); Mon, 5 Jul 2004 16:08:32 -0400 Subject: Re: 2.6.7-mm5 - more ACPI/IRQ badness? From: Jurgen Kramer To: Len Brown Cc: linux-kernel@vger.kernel.org In-Reply-To: <1089056349.15660.69.camel@dhcppc4> References: <1089056349.15660.69.camel@dhcppc4> Content-Type: text/plain Message-Id: <1089058218.2496.1.camel@paragon.slim> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 05 Jul 2004 22:10:18 +0200 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2004-07-05 at 21:39, Len Brown wrote: > On Fri, 2004-07-02 at 14:20, Jurgen Kramer wrote: > > After the issues with my EHCI controller I now hit another related > > problem. This time the IRQ of my onboard ethernet controller is being > > silenced. It happened when I removed the 3w-9xxx module which share > > interrupts. I tried bringing the ethernet connection back to live by > > doing a rmmod & insmod but that brought another 'Disabling IRQ..' > > > > > > Synchronizing SCSI cache for disk sde: > > FAILED > > status = 0, message = 00, host = 1, driver = 00 > > <4>3w-9xxx: Shutting down host 1. > > 3w-9xxx: Shutdown complete. > > irq 22: nobody cared! > > [] __report_bad_irq+0x2a/0x8b > > [] note_interrupt+0x6f/0x9f > > [] do_IRQ+0x10c/0x10e > > [] common_interrupt+0x18/0x20 > > handlers: > > [] (SkGeIsrOnePort+0x0/0x176 [sk98lin]) > > Disabling IRQ #22 > > eth0: network connection down > > Badness in remove_proc_entry at fs/proc/generic.c:681 > > [] remove_proc_entry+0xfa/0x134 > > [] skge_cleanup_module+0xc3/0x1c7 [sk98lin] > > [] __try_stop_module+0x0/0x53 > > [] sys_delete_module+0x14f/0x1a0 > > [] do_munmap+0x126/0x15c > > [] sysenter_past_esp+0x52/0x71 > > ACPI: PCI interrupt 0000:02:05.0[A] -> GSI 22 (level, low) -> IRQ 22 > > sk98lin: Network Device Driver v6.23 > > (C)Copyright 1999-2004 Marvell(R). > > ACPI: PCI interrupt 0000:02:05.0[A] -> GSI 22 (level, low) -> IRQ 22 > > eth0: 3Com Gigabit LOM (3C940) > > PrefPort:A RlmtMode:Check Link State > > irq 22: nobody cared! > > [] __report_bad_irq+0x2a/0x8b > > [] note_interrupt+0x6f/0x9f > > [] do_IRQ+0x10c/0x10e > > [] common_interrupt+0x18/0x20 > > [] default_idle+0x0/0x2c > > [] default_idle+0x29/0x2c > > [] cpu_idle+0x33/0x3c > > [] start_kernel+0x1a0/0x1dd > > [] unknown_bootoption+0x0/0x149 > > handlers: > > [] (SkGeIsrOnePort+0x0/0x176 [sk98lin]) > > Disabling IRQ #22 > > Did this work in previous releases and broke in 2.6.7-mm5, > or has it always not worked? Normally I would not try to do this. With 2.6.5 I get this when I do a 'ifdown eth0 and rmmod sk98lin': eth0: network connection down Badness in remove_proc_entry at fs/proc/generic.c:660 Call Trace: [] remove_proc_entry+0x111/0x14b [] skge_cleanup_module+0xc3/0x1c3 [sk98lin] [] __try_stop_module+0x0/0x52 [] sys_delete_module+0x136/0x16f [] do_munmap+0x13a/0x18b [] do_page_fault+0x0/0x4cf [] sysenter_past_esp+0x52/0x71 After insmodding it again it works as normal. sk98lin: Network Device Driver v6.23 (C)Copyright 1999-2004 Marvell(R). eth0: 3Com Gigabit LOM (3C940) PrefPort:A RlmtMode:Check Link State eth0: network connection up using port A speed: 1000 autonegotiation: yes duplex mode: full flowctrl: symmetric role: slave irq moderation: disabled scatter-gather: enabled > > It appears that the ethernet device is still pulling on > the interrupt line even after its driver is unloaded. > The resulting interrutps are killing the other device > which is trying to service that IRQ. > > -Len > Jurgen