public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.0-t12pre6: PCI IRQ messages [PCMCIA]
Date: Wed, 06 Dec 2000 12:26:06 +0100	[thread overview]
Message-ID: <3A2E224E.B96CF48E@oracle.com> (raw)

Everything seems to work, though. Didn't happen in t12pre5.

 Excerpt from dmesg:

Linux PCMCIA Card Services 3.1.22
  options:  [pci] [cardbus] [pm]
PCI: Found IRQ 11 for device 00:03.0
PCI: The same IRQ used for device 00:03.1
PCI: The same IRQ used for device 00:07.2
PCI: Found IRQ 11 for device 00:03.1
PCI: The same IRQ used for device 00:03.0
PCI: The same IRQ used for device 00:07.2
Yenta IRQ list 0618, PCI irq11
Socket status: 30000020
Yenta IRQ list 0618, PCI irq11
Socket status: 30000006
cs: cb_alloc(bus 5): vendor 0x115d, device 0x0003
  got res[1800:187f] for resource 0 of PCI device 115d:0003
  got res[11000000:110007ff] for resource 1 of PCI device 115d:0003
  got res[11000800:11000fff] for resource 2 of PCI device 115d:0003
  got res[10c00000:10c03fff] for resource 6 of PCI device 115d:0003
PCI: Enabling device 05:00.0 (0000 -> 0003)
IRQ routing conflict in pirq table! Try 'pci=autoirq'
  got res[1880:1887] for resource 0 of PCI device 115d:0103
  got res[11001000:110017ff] for resource 1 of PCI device 115d:0103
  got res[11001800:11001fff] for resource 2 of PCI device 115d:0103
  got res[10c04000:10c07fff] for resource 6 of PCI device 115d:0103
PCI: Enabling device 05:00.1 (0000 -> 0003)
IRQ routing conflict in pirq table! Try 'pci=autoirq'
tulip_attach(05:00.0)
PCI: Found IRQ 11 for device 05:00.0
PCI: The same IRQ used for device 00:03.0
PCI: The same IRQ used for device 00:03.1
PCI: The same IRQ used for device 00:07.2
PCI: The same IRQ used for device 05:00.1
PCI: Setting latency timer of device 05:00.0 to 64
xircom_tulip_cb.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford)
eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x1800, 00:10:A4:F9:19:A0, IRQ 11.
eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1.
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x210-0x217 0x290-0x297 0x378-0x37f 0x388-0x38f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
PCI: Found IRQ 11 for device 05:00.1
PCI: The same IRQ used for device 00:03.0
PCI: The same IRQ used for device 00:03.1
PCI: The same IRQ used for device 00:07.2
PCI: The same IRQ used for device 05:00.0



This is a Dell Latitude CPi D300XT with a:

PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
  got res[10000000:10000fff] for resource 0 of Texas Instruments PCI1131
  got res[10001000:10001fff] for resource 0 of Texas Instruments PCI1131 (#2)


Thanks & ciao,
-- 
--alessandro      <alessandro.suardi@oracle.com> <asuardi@uninetcom.it>

Linux:  kernel 2.2.18p24/2.4.0-t12p6 glibc-2.2 gcc-2.95.2 binutils-2.10.1.0.2
Oracle: Oracle8i 8.1.7.0.0 Enterprise Edition for Linux
motto:  Tell the truth, there's less to remember.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~2000-12-06 11:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3A2E224E.B96CF48E@oracle.com \
    --to=alessandro.suardi@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    /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