* Major problem with PCMCIA/Yenta system
@ 2005-03-20 23:53 Ron Gage
2005-03-21 6:40 ` Jonas Oreland
0 siblings, 1 reply; 2+ messages in thread
From: Ron Gage @ 2005-03-20 23:53 UTC (permalink / raw)
To: linux-kernel
Greetings:
I have been trying to get a recently acquired Cardbus based USB 2.0 card
working under 2.6 for the past weekend. It's not going well.
Everytime I plug the card into the computer, the entire PCMCIA system just
dies, taking my network connectivity with it. I have to do a power off reset
to recover.
The cardbus card is based on the ALI USB chipset. This shows up as both an
EHCI and an OHCI device under 2.6.11.5. My laptop, an older HP Pavilion
N5150 has a UHCI based chipset:
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev
03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev
03)
00:04.0 CardBus bridge: Texas Instruments PCI1420
00:04.1 CardBus bridge: Texas Instruments PCI1420
00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:08.0 Multimedia audio controller: ESS Technology ES1988 Allegro-1 (rev 12)
01:01.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/IX-MV (rev 11)
02:00.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43
(rev 41)
My ethernet card is a generic cardbus device.
When I insert the new USB 2.0 card, the kernel reports that it's killing off
IRQ 11. Here is the actual dump from dmesg:
Mar 20 18:38:13 port2 kernel: irq 11: nobody cared!
Mar 20 18:38:13 port2 kernel: [<c013089a>] __report_bad_irq+0x2a/0xa0
Mar 20 18:38:13 port2 kernel: [<c01303a0>] handle_IRQ_event+0x30/0x70
Mar 20 18:38:13 port2 kernel: [<c01309a0>] note_interrupt+0x70/0xb0
Mar 20 18:38:13 port2 kernel: [<c01304c1>] __do_IRQ+0xe1/0xf0
Mar 20 18:38:13 port2 kernel: [<c0104a69>] do_IRQ+0x19/0x30
Mar 20 18:38:13 port2 kernel: [<c0103182>] common_interrupt+0x1a/0x20
Mar 20 18:38:13 port2 kernel: [<c011b2be>] __do_softirq+0x2e/0xa0
Mar 20 18:38:13 port2 kernel: [<c011b356>] do_softirq+0x26/0x30
Mar 20 18:38:13 port2 kernel: [<c0104a6e>] do_IRQ+0x1e/0x30
Mar 20 18:38:13 port2 kernel: [<c0103182>] common_interrupt+0x1a/0x20
Mar 20 18:38:13 port2 kernel: [<c025e229>] acpi_processor_idle+0x238/0x288
Mar 20 18:38:13 port2 kernel: [<c0101030>] default_idle+0x0/0x30
Mar 20 18:38:13 port2 kernel: [<c01010ec>] cpu_idle+0x4c/0x60
Mar 20 18:38:13 port2 kernel: [<c04547ac>] start_kernel+0x13c/0x160
Mar 20 18:38:13 port2 kernel: [<c0454340>] unknown_bootoption+0x0/0x200
Mar 20 18:38:13 port2 kernel: handlers:
Mar 20 18:38:13 port2 kernel: [<e085a8e0>] (yenta_interrupt+0x0/0x40
[yenta_socket])
Mar 20 18:38:13 port2 kernel: [<e085a8e0>] (yenta_interrupt+0x0/0x40
[yenta_socket])
Mar 20 18:38:13 port2 kernel: [<c02baa70>] (tulip_interrupt+0x0/0x9c0)
Mar 20 18:38:13 port2 kernel: Disabling IRQ #11
Mar 20 18:38:14 port2 kernel: PCI: Enabling device 0000:06:00.0 (0000 -> 0002)
Mar 20 18:38:14 port2 kernel: PCI: Enabling device 0000:06:00.3 (0000 -> 0002)
Mar 20 18:38:16 port2 kernel: ohci_hcd 0000:06:00.0: Unlink after no-IRQ?
Controller is probably using the wrong IRQ.
Again, when the USB card in inserted, the entire PCMCIA system shuts down and
remains unusuable until powered off.
Kernel is stock 2.6.11.5. I also tried with 2.6.11, 2.6.10, 2.6.9 and 2.6.7 -
same result. Distribution is Slackware 9.1 - gcc is 3.2.3
HELP!!!
--
Ron Gage - Pontiac, Michigan
(MCP, LPIC1, A+, Net+)
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Major problem with PCMCIA/Yenta system
2005-03-20 23:53 Major problem with PCMCIA/Yenta system Ron Gage
@ 2005-03-21 6:40 ` Jonas Oreland
0 siblings, 0 replies; 2+ messages in thread
From: Jonas Oreland @ 2005-03-21 6:40 UTC (permalink / raw)
To: Ron Gage; +Cc: linux-kernel
Hi,
I recently had a similar problem, but with a netgear-wg511t
However, a kind gentleman called daniel.ritz@gmx.ch supplied with me a patch that
solved the problem.
Not sure if it will work with your card, but you can always try.
You should find it on this list,
thread topic is "yenta_socket "nobody cared - Disabling IRQ #4""
/Jonas
Ron Gage wrote:
> Greetings:
>
> I have been trying to get a recently acquired Cardbus based USB 2.0 card
> working under 2.6 for the past weekend. It's not going well.
>
> Everytime I plug the card into the computer, the entire PCMCIA system just
> dies, taking my network connectivity with it. I have to do a power off reset
> to recover.
>
> The cardbus card is based on the ALI USB chipset. This shows up as both an
> EHCI and an OHCI device under 2.6.11.5. My laptop, an older HP Pavilion
> N5150 has a UHCI based chipset:
>
> 00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev
> 03)
> 00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev
> 03)
> 00:04.0 CardBus bridge: Texas Instruments PCI1420
> 00:04.1 CardBus bridge: Texas Instruments PCI1420
> 00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
> 00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
> 00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
> 00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 03)
> 00:08.0 Multimedia audio controller: ESS Technology ES1988 Allegro-1 (rev 12)
> 01:01.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/IX-MV (rev 11)
> 02:00.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43
> (rev 41)
>
>
> My ethernet card is a generic cardbus device.
>
> When I insert the new USB 2.0 card, the kernel reports that it's killing off
> IRQ 11. Here is the actual dump from dmesg:
>
> Mar 20 18:38:13 port2 kernel: irq 11: nobody cared!
> Mar 20 18:38:13 port2 kernel: [<c013089a>] __report_bad_irq+0x2a/0xa0
> Mar 20 18:38:13 port2 kernel: [<c01303a0>] handle_IRQ_event+0x30/0x70
> Mar 20 18:38:13 port2 kernel: [<c01309a0>] note_interrupt+0x70/0xb0
> Mar 20 18:38:13 port2 kernel: [<c01304c1>] __do_IRQ+0xe1/0xf0
> Mar 20 18:38:13 port2 kernel: [<c0104a69>] do_IRQ+0x19/0x30
> Mar 20 18:38:13 port2 kernel: [<c0103182>] common_interrupt+0x1a/0x20
> Mar 20 18:38:13 port2 kernel: [<c011b2be>] __do_softirq+0x2e/0xa0
> Mar 20 18:38:13 port2 kernel: [<c011b356>] do_softirq+0x26/0x30
> Mar 20 18:38:13 port2 kernel: [<c0104a6e>] do_IRQ+0x1e/0x30
> Mar 20 18:38:13 port2 kernel: [<c0103182>] common_interrupt+0x1a/0x20
> Mar 20 18:38:13 port2 kernel: [<c025e229>] acpi_processor_idle+0x238/0x288
> Mar 20 18:38:13 port2 kernel: [<c0101030>] default_idle+0x0/0x30
> Mar 20 18:38:13 port2 kernel: [<c01010ec>] cpu_idle+0x4c/0x60
> Mar 20 18:38:13 port2 kernel: [<c04547ac>] start_kernel+0x13c/0x160
> Mar 20 18:38:13 port2 kernel: [<c0454340>] unknown_bootoption+0x0/0x200
> Mar 20 18:38:13 port2 kernel: handlers:
> Mar 20 18:38:13 port2 kernel: [<e085a8e0>] (yenta_interrupt+0x0/0x40
> [yenta_socket])
> Mar 20 18:38:13 port2 kernel: [<e085a8e0>] (yenta_interrupt+0x0/0x40
> [yenta_socket])
> Mar 20 18:38:13 port2 kernel: [<c02baa70>] (tulip_interrupt+0x0/0x9c0)
> Mar 20 18:38:13 port2 kernel: Disabling IRQ #11
> Mar 20 18:38:14 port2 kernel: PCI: Enabling device 0000:06:00.0 (0000 -> 0002)
> Mar 20 18:38:14 port2 kernel: PCI: Enabling device 0000:06:00.3 (0000 -> 0002)
> Mar 20 18:38:16 port2 kernel: ohci_hcd 0000:06:00.0: Unlink after no-IRQ?
> Controller is probably using the wrong IRQ.
>
> Again, when the USB card in inserted, the entire PCMCIA system shuts down and
> remains unusuable until powered off.
>
> Kernel is stock 2.6.11.5. I also tried with 2.6.11, 2.6.10, 2.6.9 and 2.6.7 -
> same result. Distribution is Slackware 9.1 - gcc is 3.2.3
>
> HELP!!!
>
>
--
Jonas Oreland, Software Engineer
MySQL AB, www.mysql.com
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-03-21 6:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-20 23:53 Major problem with PCMCIA/Yenta system Ron Gage
2005-03-21 6:40 ` Jonas Oreland
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox