All of lore.kernel.org
 help / color / mirror / Atom feed
* 2.6.7-mm5 - more ACPI/IRQ badness?
  2004-07-01  0:26 2.6.7-mm5 Andrew Morton
@ 2004-07-02 18:20 ` Jurgen Kramer
  0 siblings, 0 replies; 3+ messages in thread
From: Jurgen Kramer @ 2004-07-02 18:20 UTC (permalink / raw)
  To: linux-kernel

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..'

<snip>
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!
 [<c0108106>] __report_bad_irq+0x2a/0x8b
 [<c01081f0>] note_interrupt+0x6f/0x9f
 [<c0108473>] do_IRQ+0x10c/0x10e
 [<c0106850>] common_interrupt+0x18/0x20
handlers:
[<f8a646f6>] (SkGeIsrOnePort+0x0/0x176 [sk98lin])
Disabling IRQ #22
eth0: network connection down
Badness in remove_proc_entry at fs/proc/generic.c:681
 [<c0189e18>] remove_proc_entry+0xfa/0x134
 [<f8a814eb>] skge_cleanup_module+0xc3/0x1c7 [sk98lin]
 [<c01354d6>] __try_stop_module+0x0/0x53
 [<c0132c6b>] sys_delete_module+0x14f/0x1a0
 [<c014c798>] do_munmap+0x126/0x15c
 [<c0105e91>] 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!
 [<c0108106>] __report_bad_irq+0x2a/0x8b
 [<c01081f0>] note_interrupt+0x6f/0x9f
 [<c0108473>] do_IRQ+0x10c/0x10e
 [<c0106850>] common_interrupt+0x18/0x20
 [<c010401e>] default_idle+0x0/0x2c
 [<c0104047>] default_idle+0x29/0x2c
 [<c01040b0>] cpu_idle+0x33/0x3c
 [<c031684b>] start_kernel+0x1a0/0x1dd
 [<c0316309>] unknown_bootoption+0x0/0x149
handlers:
[<f8a636f6>] (SkGeIsrOnePort+0x0/0x176 [sk98lin])
Disabling IRQ #22

Jurgen



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2.6.7-mm5 - more ACPI/IRQ badness?
       [not found] <A6974D8E5F98D511BB910002A50A6647615FF5FD@hdsmsx403.hd.intel.com>
@ 2004-07-05 19:39 ` Len Brown
  2004-07-05 20:10   ` Jurgen Kramer
  0 siblings, 1 reply; 3+ messages in thread
From: Len Brown @ 2004-07-05 19:39 UTC (permalink / raw)
  To: Jurgen Kramer; +Cc: linux-kernel

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..'
> 
> <snip>
> 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!
>  [<c0108106>] __report_bad_irq+0x2a/0x8b
>  [<c01081f0>] note_interrupt+0x6f/0x9f
>  [<c0108473>] do_IRQ+0x10c/0x10e
>  [<c0106850>] common_interrupt+0x18/0x20
> handlers:
> [<f8a646f6>] (SkGeIsrOnePort+0x0/0x176 [sk98lin])
> Disabling IRQ #22
> eth0: network connection down
> Badness in remove_proc_entry at fs/proc/generic.c:681
>  [<c0189e18>] remove_proc_entry+0xfa/0x134
>  [<f8a814eb>] skge_cleanup_module+0xc3/0x1c7 [sk98lin]
>  [<c01354d6>] __try_stop_module+0x0/0x53
>  [<c0132c6b>] sys_delete_module+0x14f/0x1a0
>  [<c014c798>] do_munmap+0x126/0x15c
>  [<c0105e91>] 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!
>  [<c0108106>] __report_bad_irq+0x2a/0x8b
>  [<c01081f0>] note_interrupt+0x6f/0x9f
>  [<c0108473>] do_IRQ+0x10c/0x10e
>  [<c0106850>] common_interrupt+0x18/0x20
>  [<c010401e>] default_idle+0x0/0x2c
>  [<c0104047>] default_idle+0x29/0x2c
>  [<c01040b0>] cpu_idle+0x33/0x3c
>  [<c031684b>] start_kernel+0x1a0/0x1dd
>  [<c0316309>] unknown_bootoption+0x0/0x149
> handlers:
> [<f8a636f6>] (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?

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



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2.6.7-mm5 - more ACPI/IRQ badness?
  2004-07-05 19:39 ` 2.6.7-mm5 - more ACPI/IRQ badness? Len Brown
@ 2004-07-05 20:10   ` Jurgen Kramer
  0 siblings, 0 replies; 3+ messages in thread
From: Jurgen Kramer @ 2004-07-05 20:10 UTC (permalink / raw)
  To: Len Brown; +Cc: linux-kernel

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..'
> > 
> > <snip>
> > 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!
> >  [<c0108106>] __report_bad_irq+0x2a/0x8b
> >  [<c01081f0>] note_interrupt+0x6f/0x9f
> >  [<c0108473>] do_IRQ+0x10c/0x10e
> >  [<c0106850>] common_interrupt+0x18/0x20
> > handlers:
> > [<f8a646f6>] (SkGeIsrOnePort+0x0/0x176 [sk98lin])
> > Disabling IRQ #22
> > eth0: network connection down
> > Badness in remove_proc_entry at fs/proc/generic.c:681
> >  [<c0189e18>] remove_proc_entry+0xfa/0x134
> >  [<f8a814eb>] skge_cleanup_module+0xc3/0x1c7 [sk98lin]
> >  [<c01354d6>] __try_stop_module+0x0/0x53
> >  [<c0132c6b>] sys_delete_module+0x14f/0x1a0
> >  [<c014c798>] do_munmap+0x126/0x15c
> >  [<c0105e91>] 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!
> >  [<c0108106>] __report_bad_irq+0x2a/0x8b
> >  [<c01081f0>] note_interrupt+0x6f/0x9f
> >  [<c0108473>] do_IRQ+0x10c/0x10e
> >  [<c0106850>] common_interrupt+0x18/0x20
> >  [<c010401e>] default_idle+0x0/0x2c
> >  [<c0104047>] default_idle+0x29/0x2c
> >  [<c01040b0>] cpu_idle+0x33/0x3c
> >  [<c031684b>] start_kernel+0x1a0/0x1dd
> >  [<c0316309>] unknown_bootoption+0x0/0x149
> > handlers:
> > [<f8a636f6>] (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:
 [<c0189028>] remove_proc_entry+0x111/0x14b
 [<f8a7f4a7>] skge_cleanup_module+0xc3/0x1c3 [sk98lin]
 [<c0137957>] __try_stop_module+0x0/0x52
 [<c0135883>] sys_delete_module+0x136/0x16f
 [<c014ba32>] do_munmap+0x13a/0x18b
 [<c011a639>] do_page_fault+0x0/0x4cf
 [<c01091a9>] 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



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-07-05 20:08 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <A6974D8E5F98D511BB910002A50A6647615FF5FD@hdsmsx403.hd.intel.com>
2004-07-05 19:39 ` 2.6.7-mm5 - more ACPI/IRQ badness? Len Brown
2004-07-05 20:10   ` Jurgen Kramer
2004-07-01  0:26 2.6.7-mm5 Andrew Morton
2004-07-02 18:20 ` 2.6.7-mm5 - more ACPI/IRQ badness? Jurgen Kramer

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.