[Fwd: irq 9: nobody cared! after moving from 2.4.19 to 2.6.11.5]

[Daniel Ritz]

On Thursday 14 April 2005 18:56, Scott Waye wrote:
> Hi,
> 
> Daniel Ritz wrote:
> 
> >hi
> >
> >strange enough. the interrupt is even coming in on the right line. but
> >please try the attached patch. it should fix the problem. (also strange
> >enough the problem has not been reported before. but i saw similar
> >reports more than once this week. i think all from debian users. looks
> >like they upgraded the kernel so we have a lot more testers :)
> >
> >dominik please push this for 2.6.12 anyway. it can't hurt :)
> >
> >  
> >
> Thanks for the patch.  I applied it onto 2.6.11.5 with the ti113x.h 
> patch already applied (not sure if that makes any difference).  I still 
> have a problem and get the following output in dmesg/lspci -vv :  Oh, 
> FWIW this laptop was intially built from Slackware (I've always used 
> that right since a.out days)
> 
[snip]
> ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 9 (level, low) -> IRQ 9
> Yenta: CardBus bridge found at 0000:00:0a.0 [104d:80f6]
> Yenta: Using CSCINT to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI
> Yenta TI: socket 0000:00:0a.0, mfunc 0x012c1222, devctl 0x66
> irq 9: nobody cared!
>  [<c013022a>] __report_bad_irq+0x2a/0x90
>  [<c012fb20>] handle_IRQ_event+0x30/0x70
>  [<c013031c>] note_interrupt+0x6c/0xd0
>  [<c012fcae>] __do_IRQ+0x14e/0x160
>  [<c01044a3>] do_IRQ+0x23/0x40
>  [<c0102a3a>] common_interrupt+0x1a/0x20
>  [<c0119ab0>] __do_softirq+0x30/0x90
>  [<c0119b36>] do_softirq+0x26/0x30
>  [<c0119c15>] irq_exit+0x35/0x40
>  [<c01044a8>] do_IRQ+0x28/0x40
>  [<c0102a3a>] common_interrupt+0x1a/0x20
>  [<c027b5d7>] yenta_probe_cb_irq+0xb7/0x140
>  [<c027a4ef>] ti12xx_irqroute_func0+0x8f/0x380
>  [<c027ad11>] ti12xx_override+0x101/0x1a0
>  [<c027ba77>] yenta_probe+0x237/0x250
>  [<c01ea532>] pci_device_probe_static+0x52/0x70
>  [<c01ea58c>] __pci_device_probe+0x3c/0x50
>  [<c01ea5cc>] pci_device_probe+0x2c/0x50
>  [<c023dcef>] driver_probe_device+0x2f/0x70
>  [<c023de29>] driver_attach+0x59/0x90
>  [<c023e2f8>] bus_add_driver+0x98/0xd0
>  [<c023e91f>] driver_register+0x2f/0x40
>  [<c025a11c>] ide_register_driver+0x10c/0x130
>  [<c01ea842>] pci_register_driver+0x62/0x80
>  [<c03f206f>] yenta_socket_init+0xf/0x20
>  [<c03da81b>] do_initcalls+0x2b/0xc0
>  [<c03f37aa>] sock_init+0x2a/0x40
>  [<c01002c0>] init+0x0/0x110
>  [<c01002ef>] init+0x2f/0x110
>  [<c010086c>] kernel_thread_helper+0x0/0x14
>  [<c0100871>] kernel_thread_helper+0x5/0x14
> handlers:
> [<c01f01d0>] (acpi_irq+0x0/0x16)
> [<c027b4e0>] (yenta_probe_handler+0x0/0x40)
> Disabling IRQ #9
> [ACPI Debug] String: [0x24] "------------------------ _Q09 : test"
> Yenta TI: socket 0000:00:0a.0 probing PCI interrupt failed, trying to fix
> Yenta TI: socket 0000:00:0a.0 falling back to parallel PCI interrupts
> Yenta TI: socket 0000:00:0a.0 no PCI interrupts. Fish. Please report.
> Yenta: ISA IRQ mask 0x0c00, PCI irq 0
> Socket status: 30000019

he he. it's better now, the yent_probe_handler is there at least :)

so can you try these two things?
- make sure no card is inserted when yenta is loading. insert it when the
  whole pcmcia thingy is up
- try to just remove the followin code in yenta_probe_cb_irq() in yenta.c:
        /* disable ISA interrupts */
        bridge_ctrl = config_readw(socket, CB_BRIDGE_CONTROL);
        bridge_ctrl &= ~CB_BRIDGE_INTR;
        config_writew(socket, CB_BRIDGE_CONTROL, bridge_ctrl);

now that i think about it i can't remember why i put it there in the
first place...it's not needed as far as i can see. also the opposite in
yenta_probe_irq() is not needed...this thingy is only for the functional
interrupt, not for the CSC.


rgds
-daniel