From: Paul Dickson <dickson@permanentmail.com>
To: linux-kernel@vger.kernel.org
Subject: Missing cardbus label in /proc/interrupts
Date: Fri, 15 Aug 2003 16:18:19 -0700 [thread overview]
Message-ID: <20030815161819.4ff4ad0a.dickson@permanentmail.com> (raw)
Seen in 2.6.0-test3's /proc/interrupts:
CPU0
0: 179268180 XT-PIC timer
1: 36175 XT-PIC i8042
2: 0 XT-PIC cascade
3: 1248 XT-PIC ide2
5: 820479 XT-PIC ESS Maestro 2
8: 1 XT-PIC rtc
11: 3548209 XT-PIC uhci-hcd, , , eth0
14: 518106 XT-PIC ide0
15: 714841 XT-PIC ide1
NMI: 0
ERR: 18176
The cardbus devices aren't listed. I'm using the network card in one and
the CF card is readable in the other. This is probably a trivial bug.
[root@violet 16:08:54 root]# lspci -v
...
00:04.0 CardBus bridge: Texas Instruments PCI1220 (rev 02)
Subsystem: Dell Computer Corporation: Unknown device 0085
Flags: bus master, medium devsel, latency 168, IRQ 11
Memory at 10000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
Memory window 0: 10400000-107ff000 (prefetchable)
Memory window 1: 10800000-10bff000
I/O window 0: 00001000-000010ff
I/O window 1: 00001400-000014ff
16-bit legacy interface ports at 0001
00:04.1 CardBus bridge: Texas Instruments PCI1220 (rev 02)
Subsystem: Dell Computer Corporation: Unknown device 0085
Flags: bus master, medium devsel, latency 168, IRQ 11
Memory at 10001000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=06, subordinate=09, sec-latency=176
Memory window 0: 10c00000-10fff000 (prefetchable)
Memory window 1: 11000000-113ff000
I/O window 0: 00001800-000018ff
I/O window 1: 00001c00-00001cff
16-bit legacy interface ports at 0001
...
I noticed this after several card insertions, so I rebooted the system,
but this seems to be constant.
-Paul
next reply other threads:[~2003-08-15 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 23:18 Paul Dickson [this message]
2003-08-27 10:06 ` Missing cardbus label in /proc/interrupts Paul Dickson
2003-09-06 21:44 ` Russell King
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=20030815161819.4ff4ad0a.dickson@permanentmail.com \
--to=dickson@permanentmail.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;
as well as URLs for NNTP newsgroup(s).