From: Jim Nelson <james4765@verizon.net>
To: David Jez <dave.jez@seznam.cz>
Cc: Martin Mares <mj@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: PCI & IRQ problems on TI Extensa 600CD
Date: Sat, 23 Oct 2004 15:53:02 -0400 [thread overview]
Message-ID: <417AB69E.8010709@verizon.net> (raw)
In-Reply-To: <20041023142906.GA15789@stud.fit.vutbr.cz>
David Jez wrote:
> Hi Martin,
>
> i spent few last nights with my Extensa. This notebook has PCI 2.1 wich
> works only under m$ window$ :-(. I tried many version of kernel, 2.2,
> 2.4 and 2.6 tree and nothing helps me. I tried pci=bios pci=bios,biosirq
> kernel options, PCI=BIOS instead of ANY...
> Result is always same:
> PCI: No IRQ known for interrupt pin A of device 00:04.0.
> this cause for example that PCMCIA doesn't work. See attached dmesg log
> and other files for details.
> In Window$ everythink works OK and IRQ routing table is get from PCI
> BIOS.
>
> Any ideas?
>
I've got the same problem with the Cardbus bridge on my old Thinkpad 760ED - I
think your laptop is as old as mine (Pentium 166 - 1996 or thereabouts).
The problem with mine is that the Cardbus bridge doesn't get a vaild IRQ written
into the chip by the BIOS, and Linux relies on the BIOS to do it on older
machines. I haven't found an answer yet - I'm just getting into this stuff
myself, and don't understand PCI well enough to code a fix. It is good to know
that it is not an IBM-only problem.
> 00:00.0 Host bridge: Acer Laboratories Inc. [ALi] M1521 [Aladdin III] (rev 1c)
> 00:02.0 ISA bridge: Acer Laboratories Inc. [ALi] M1523 (rev 07)
> 00:02.1 IDE interface: Acer Laboratories Inc. [ALi] M5219 (rev 20)
> 00:04.0 CardBus bridge: Texas Instruments PCI1130 (rev 04)
> 00:04.1 CardBus bridge: Texas Instruments PCI1130 (rev 04)
> 00:06.0 VGA compatible controller: Chips and Technologies F65550 (rev 45)
>
> 00:02.1 Class 0101: 10b9:5219 (rev 20) (prog-if fa)
> Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64 (500ns min, 1000ns max)
> Interrupt: pin A routed to IRQ 0
> Region 4: I/O ports at fcf0 [size=16]
> 00: b9 10 19 52 05 00 80 02 20 fa 01 01 00 40 80 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: f1 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 01 02 04
>
> 00:04.0 Class 0607: 104c:ac12 (rev 04)
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64, cache line size 04
> Interrupt: pin A routed to IRQ 0
> Region 0: Memory at 02800000 (32-bit, non-prefetchable) [size=4K]
> Bus: primary=00, secondary=01, subordinate=05, sec-latency=176
> Memory window 0: fffff000-00000000
> Memory window 1: fffff000-00000000
> I/O window 0: 0000fffc-00000003
> I/O window 1: 0000fffc-00000003
> BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite-
> 16-bit legacy interface ports at 0001
> 00: 4c 10 12 ac 07 00 00 02 04 00 07 06 04 40 82 00
> 10: 00 00 80 02 00 00 00 02 00 01 05 b0 00 f0 ff ff
> 20: 00 00 00 00 00 f0 ff ff 00 00 00 00 fc ff 00 00
> 30: 00 00 00 00 fc ff 00 00 00 00 00 00 ff 01 c0 00
> 40: 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
> 00:04.1 Class 0607: 104c:ac12 (rev 04)
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64, cache line size 04
> Interrupt: pin B routed to IRQ 0
> Region 0: Memory at 02802000 (32-bit, non-prefetchable) [size=4K]
> Bus: primary=00, secondary=06, subordinate=0a, sec-latency=176
> Memory window 0: 00000000-00000000
> Memory window 1: fffff000-00000000
> I/O window 0: 0000fffc-00000003
> I/O window 1: 0000fffc-00000003
> BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite-
> 16-bit legacy interface ports at 0001
> 00: 4c 10 12 ac 07 00 00 02 04 00 07 06 04 40 82 00
> 10: 00 20 80 02 00 00 00 22 00 06 0a b0 00 00 00 00
> 20: 00 00 00 00 00 f0 ff ff 00 00 00 00 fc ff 00 00
> 30: 00 00 00 00 fc ff 00 00 00 00 00 00 ff 02 c0 00
> 40: 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
Just out of curiosity - does lspci -vvb show the interrupt pins on the Cardbus
bridge routed to IRQ 255?
If so, it might be a problem with the TI bridge chip. IIRC, that's the same model
chip as in my laptop.
next prev parent reply other threads:[~2004-10-23 19:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 14:29 PCI & IRQ problems on TI Extensa 600CD David Jez
2004-10-23 19:53 ` Jim Nelson [this message]
2004-10-25 16:19 ` David Jez
2004-10-29 8:18 ` David Jez
2004-10-29 9:50 ` Jim Nelson
2004-10-29 10:14 ` David Jez
2004-11-01 8:42 ` David Jez
2004-11-01 12:59 ` Jim Nelson
2004-11-01 20:27 ` David Jez
2004-11-02 14:15 ` Jim Nelson
2004-11-02 16:24 ` Jim Nelson
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=417AB69E.8010709@verizon.net \
--to=james4765@verizon.net \
--cc=dave.jez@seznam.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).