From: Brad F. <br...@fr...> - 2002-04-29 04:22:43
|
David, one of my firewalls is very similar to the setup you have Maybe the information I've included inline will help a bit... On Fri, 26 Apr 2002 17:20:11 PDT David Smead wrote: > Jacques, > > Thanks for the input. I'm not showing interrupts, but the drivers seem to > load, and I/O space is assigned. This is similar to the behavior I have seen with the 3c509b NICs that are not active. I have a 6 NIC setup where eth0-eth2 are up and have addresses assigned and eth3-eth5 inactive. Interrupts are assigned to eth0-eth2 but not eth3-eth5: firewall: -root- # cat /proc/interrupts CPU0 0: 12813706 XT-PIC timer 1: 2 XT-PIC keyboard 2: 0 XT-PIC cascade 3: 6 XT-PIC serial 4: 6 XT-PIC serial 5: 279574 XT-PIC eth0 7: 6574 XT-PIC eth1 8: 2 XT-PIC rtc 9: 1061 XT-PIC eth2 13: 1 XT-PIC fpu NMI: 0 firewall: -root- # ip addr 1: lo: <LOOPBACK,UP> mtu 3924 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope global lo 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:a0:24:2a:e6:75 brd ff:ff:ff:ff:ff:ff inet aa.bb.cc.dd/22 brd 255.255.255.255 scope global eth0 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:a0:24:2a:e6:e6 brd ff:ff:ff:ff:ff:ff inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1 4: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:a0:24:2a:e6:eb brd ff:ff:ff:ff:ff:ff inet 192.168.2.254/24 brd 192.168.2.255 scope global eth2 5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 100 link/ether 00:a0:24:2a:e6:f5 brd ff:ff:ff:ff:ff:ff 6: eth4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 100 link/ether 00:a0:24:2a:e6:fa brd ff:ff:ff:ff:ff:ff 7: eth5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 100 link/ether 00:a0:24:2a:e7:13 brd ff:ff:ff:ff:ff:ff > From dmesg: > eth0: 3c5x9 at 0x300, 10baseT port, address 00 50 04 04 7c 94, IRQ 15. > 3c509.c:1.18a 17N...@sc... > http://www.scyld.com/network/3c509.html > eth1: 3c5x9 at 0x310, 10baseT port, address 00 60 97 79 11 7b, IRQ 3. > 3c509.c:1.18a 17N...@sc... > http://www.scyld.com/network/3c509.html [ remaining examples snipped ] That's very similar to what I'm seeing: firewall: -root- # dmesg | grep 3c509 eth0: 3c509 at 0x300 tag 1, 10baseT port, address 00 a0 24 2a e6 75, IRQ 5. 3c509.c:1.16 (2.2) 2/3/98 be...@ce.... eth1: 3c509 at 0x310 tag 2, 10baseT port, address 00 a0 24 2a e6 e6, IRQ 7. 3c509.c:1.16 (2.2) 2/3/98 be...@ce.... eth2: 3c509 at 0x320 tag 3, 10baseT port, address 00 a0 24 2a e6 eb, IRQ 9. 3c509.c:1.16 (2.2) 2/3/98 be...@ce.... eth3: 3c509 at 0x330 tag 4, 10baseT port, address 00 a0 24 2a e6 f5, IRQ 10. 3c509.c:1.16 (2.2) 2/3/98 be...@ce.... eth4: 3c509 at 0x340 tag 5, 10baseT port, address 00 a0 24 2a e6 fa, IRQ 11. 3c509.c:1.16 (2.2) 2/3/98 be...@ce.... eth5: 3c509 at 0x350 tag 6, 10baseT port, address 00 a0 24 2a e7 13, IRQ 12. 3c509.c:1.16 (2.2) 2/3/98 be...@ce.... > From /proc/interrupts: > > CPU0 > 0: 8241668 XT-PIC timer > 1: 400 XT-PIC keyboard > 2: 0 XT-PIC cascade > NMI: 0 > ERR: 0 > > Any ideas about how this happens are appreciated. This is running on a > Dell Optiplex 575 - P75 with 24 MB ram, no ide cables plugged in. All > nics have pnp disabled and were configured as the dmesg shows. Are any of your interfaces up? If not, the /proc/interrupts output you are seeing is inline with what I'm seeing on my firewall. (Not that it matters, but it's a Dell Optiplex GMT 5133.) My guess is that everything is normal and the interrupts will show up in /proc/interrupts when the interfaces are brought up. --Brad > Sincerely, > > David Smead > http://www.amplepower.com. |