mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: Michael Ulbrich <mul@rentapacs.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.20 - yenta, i82365 PCI / ISA irq problem
Date: Wed, 28 May 2003 12:59:04 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.55.0305281256100.2721@bigblue.dev.mcafeelabs.com> (raw)
In-Reply-To: <3ED512F8.3700891A@rentapacs.de>

On Wed, 28 May 2003, Michael Ulbrich wrote:

> Hi there,
>
> for quite some time now, I'm fiddling around with an annoying problem on
> my Fujitsu-Siemens S6010 laptop together with a Dell TrueMobile 1150
> WLAN mini PCI card (orinoco chipset). Searching both the pcmcia_cs and
> orinoco mailing list archives pointed to a deeper, irq related problem.
> Excuse me if this is still the wrong forum, but probably someone out
> here may have some clue.
>
> So here we go - Booting with in-kernel pcmcia gives the following
> output:
>
> ...
> pcmcia: Starting PCMCIA services:
> kernel: Linux Kernel Card Services 3.1.22
> kernel:   options:  [pci] [cardbus] [pm]
> kernel: PCI: Found IRQ 11 for device 01:0a.0
> kernel: PCI: Sharing IRQ 11 with 00:02.0
> kernel: PCI: Sharing IRQ 11 with 00:1d.0
> kernel: PCI: Found IRQ 11 for device 01:0a.1
> kernel: PCI: Sharing IRQ 11 with 00:1f.3
> kernel: PCI: Sharing IRQ 11 with 00:1f.5
> kernel: PCI: Enabling device 01:0d.0 (0000 -> 0002)
> kernel: PCI: Found IRQ 11 for device 01:0d.0
> kernel: PCI: Sharing IRQ 11 with 00:1f.1
> kernel: Yenta IRQ list 06b8, PCI irq11
> kernel: Socket status: 30000006
> kernel: Yenta IRQ list 06b8, PCI irq11
> network: Setting network parameters:  succeeded
> kernel: Socket status: 30000006
> network: Bringing up interface lo:  succeeded
> pcmcia: using yenta_socket instead of i82365
> kernel: Yenta IRQ list 0000, PCI irq11
> kernel: Socket status: 30000010
> pcmcia: cardmgr[786]: watching 3 sockets
> cardmgr[786]: watching 3 sockets
> kernel: cs: IO port probe 0x0c00-0x0cff: clean.
> kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f
> 0x400-0x407 0x4d0-0x4d7
> kernel: cs: IO port probe 0x0a00-0x0aff: clean.
> cardmgr[787]: starting, version is 3.2.4
> kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
> cardmgr[787]: socket 2: Orinoco or Intersil Prism 2 Wireless
> pcmcia: done.
> rc: Starting pcmcia:  succeeded
> cardmgr[787]: executing: 'modprobe hermes'
> cardmgr[787]: executing: 'modprobe orinoco'
> cardmgr[787]: executing: 'modprobe orinoco_cs'
> cardmgr[787]: executing: './network start eth0'
> ...
> kernel: NETDEV WATCHDOG: eth0: transmit timed out
> kernel: eth0: Tx timeout! Resetting card. ALLOCFID=01f7,
> TXCOMPLFID=0000, EVSTAT=8080
> ...
> last message repeating
>
> The same with in-kernel pcmcia disabled and pcmcia_cs as modules:
>
> ...
> kernel: Linux PCMCIA Card Services 3.2.4
> kernel:   kernel build: 2.4.20-RAP-LL-03 #18 Sun May 18 18:13:34 CEST
> 2003
> kernel:   options:  [pci] [cardbus] [apm]
> kernel: Intel ISA/PCI/CardBus PCIC probe:
> kernel: PCI: Found IRQ 11 for device 01:0a.0
> kernel: PCI: Sharing IRQ 11 with 00:02.0
> kernel: PCI: Sharing IRQ 11 with 00:1d.0
> kernel: PCI: Found IRQ 11 for device 01:0a.1
> kernel: PCI: Sharing IRQ 11 with 00:1f.3
> kernel: PCI: Sharing IRQ 11 with 00:1f.5
> kernel:   O2Micro OZ6933 rev 02 PCI-to-CardBus at slot 01:0a, mem
> 0x20000000
> kernel:     host opts [0]: [pci only] [pci irq 11] [lat 168/176] [bus
> 2/2]
> kernel:     host opts [1]: [pci only] [pci irq 11] [lat 168/176] [bus
> 3/3]
> kernel:     PCI card interrupts, PCI status changes
> kernel: PCI: Enabling device 01:0d.0 (0000 -> 0002)
> kernel: PCI: Found IRQ 11 for device 01:0d.0
> kernel: PCI: Sharing IRQ 11 with 00:1f.1
> kernel:   TI 1410 rev 01 PCI-to-CardBus at slot 01:0d, mem 0x20002000
> kernel:     host opts [0]: [serial pci & irq] [pci irq 11] [lat 168/176]
> [bus 4/4]
> kernel:     PCI irq 11 test failed
> kernel:     ISA irqs (scanned) = none!<6>    *NO* card interrupts,
> polling interval = 1000 ms
> network: Setting network parameters:  succeeded
> pcmcia: cardmgr[764]: watching 3 sockets
> cardmgr[764]: watching 3 sockets
> cardmgr[765]: starting, version is 3.2.4
> pcmcia: done.
> rc: Starting pcmcia:  succeeded
> kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
> cardmgr[765]: socket 2: Orinoco or Intersil Prism 2 Wireless
> ...
> cardmgr[765]: executing: 'modprobe hermes'
> cardmgr[765]: executing: 'modprobe orinoco'
> cardmgr[765]: executing: 'modprobe orinoco_cs'
> kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f
> 0x3c0-0x3df 0x400-0x407 0x4d0-0x4d7
> kernel: cs: IO port probe 0x0380-0x03bf: clean.
> kernel: cs: IO port probe 0x03e0-0x03ff: clean.
> kernel: cs: IO port probe 0x0408-0x04cf: clean.
> kernel: cs: IO port probe 0x04d8-0x04ff: clean.
> kernel: cs: IO port probe 0x0a00-0x0aff: clean.
> kernel: cs: IO port probe 0x0c00-0x0cff: clean.
> kernel: orinoco_cs: RequestIRQ: Resource in use

I had lamost the same problem with my CPQ Presario. Time to time the card
did not get the IRQ (RequestIRQ: Resource in use). I have a patch that
fixes that on my machine at home. If you want tomorrow I'll post it.




- Davide


      reply	other threads:[~2003-05-28 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 19:50 Michael Ulbrich
2003-05-28 19:59 ` Davide Libenzi [this message]

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=Pine.LNX.4.55.0305281256100.2721@bigblue.dev.mcafeelabs.com \
    --to=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mul@rentapacs.de \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®