-----BEGIN PGP SIGNED MESSAGE-----
On 19 Apr 00, at 7:59, Jean-Louis Debert wrote:
> "D. R. Evans" wrote:
> > So I'm wondering, is there any way to get a device-by-device listing of
> > what's occupying the various IRQs? (One hypothesis being that something
> > else was sitting on IRQ 5 and moved to IRQ 10 when the network card
> > appeared and occupied IRQ 5. I know that the PCI bus is not supposed to
> > allow two devices to occupy the same IRQ, but I'm grasping at straws.)
>
>
> You have that under /proc
>
Here is what I see in /proc/interrupts
CPU0
0: 152398 XT-PIC timer
1: 493 XT-PIC keyboard
2: 0 XT-PIC cascade
3: 0 XT-PIC es1371
8: 1 XT-PIC rtc
12: 11288 XT-PIC PS/2 Mouse
13: 1 XT-PIC fpu
14: 100956 XT-PIC ide0
15: 251 XT-PIC ide1
NMI: 0
Interestingly, no IRQ 10 (for the modem) or IRQ 5 (for the network card).
I imagine, though, that these are the interrupts that have actually
occurred since booting. I hadn't brought up the network card, so no IRQ 5;
and since I can't get to the modem I suppose I shouldn't be surprised
(should I?) that IRQ 10 doesn't appear.
FWIW, here is /proc/ioports:
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
d000-d007 : ide0
d008-d00f : ide1
d800-d83f : es1371
dc00-dc1f : eth0
ec00-ec07 : serial(set)
The last entry comes from this in my rc.local file:
# DRE
setserial -v /dev/ttyS4 port 0xec00 uart 16550A irq 10 ^fourport
- -----
What is the name of the serial driver? When I look at the loaded modules I
see:
ne2k-pci 4256 0 (autoclean) (unused)
8390 6020 0 (autoclean) [ne2k-pci]
lockd 33256 1 (autoclean)
sunrpc 56612 1 (autoclean) [lockd]
nls_iso8859-1 2052 2 (autoclean)
nls_cp437 3580 2 (autoclean)
vfat 11004 2 (autoclean)
fat 32640 2 (autoclean) [vfat]
ide-scsi 7584 1
supermount 14880 3 (autoclean)
es1371 26308 0
soundcore 3524 4 [es1371]
(this was after bringing up the eth0 interface, which is why it's listed).
I expected to see something I could identify as a serial driver, but it's
not obvious.
One other thing that probably doesn't mean anything, at boot time I see a
message that sits on my screen for about 1 millisecond, so I can't read it,
but it contains the string "ttyS4". Looking in the log in dmesg or
/var/tmp/messages doesn't help, because that particular message doesn't
appear; maybe there's some other place I could look so I can get a chance
to read the message? I don't think it's an error message, but it would be
nice to be sure.
> Note that PCI bus _IS_ supposed to allow to devices to occupy
> the same IRQ (there is arbitration _if needed_, i.e. if either
> of the devices indicates that it _CAN'T_ share a resource,
> which would probably be the case for either modem or ethernet,
> because of timing considerations).
>
I'd forgotten that, but of course you're right. (It's been a couple of
years since I last looked at the PCI specs.)
> Besides, did you consider that it might _NOT_ be the IRQ,
> but also a possible I/O (including memory mapped I/O) port
> or address, that could cause the conflict, and/or confuse
> the driver because the wrong device would answer ?
Yes. But the ioports look OK as well, per the list above.
Doc Evans
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60
Comment: Key obtainable from servers: ID 0x6184B81D
iQCVAwUBOP93Yf2CFbFhhLgdAQHw8AP+PnpU/D1WQWLd9uOXD3zueBi210gLvu2h
KzjexG1GtrZIp5ZNfrvNDG1A7vZCPg0qTBnqeiG+UEJNrXX+j6ATNhyGjAKSm/uz
t/3FMqyn+y7De3OnQfBExnAyRYqJ1wvCw7sVaM34q1TuUNbqVSsH4Oh0wyfA2bzJ
IzoXN0za8qc=
=2vOP
-----END PGP SIGNATURE-----
----------------------------------------------------------
D.R. Evans N7DR / G4AMJ [EMAIL PROTECTED]
"Palindor Chronicles" information and extracts:
http://www.sff.net/people/N7DR/drevans.htp
----------------------------------------------------------
