frame value too large by ifconfig!!!!

KoRiR · 02-22-2008, 11:11 PM

my NIC doesn't work .My os is RHEL5.1/32bit/dual core intel cpu. the ifconfig output:

eth2 Link encap:Ethernet HWaddr 00:55:7B:B5:7D:F7
inet addr:192.168.1.22 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::255:7bff:feb5:7df7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:21668
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:60 (60.0 b) TX bytes:0 (0.0 b)
Interrupt:169

why the frame value(21668) so large?

and that,it doesn't show Base address info.

why?

jschiwal · 02-22-2008, 11:32 PM

I think your problems is with the interupt. It should be something like 11. You should re-install this interface. Something may have happened to a modprobe.conf entry. I don't think any machine has that many interrupt lines.

You might want to post the "lspci -v" entry for your NIC device.
example:

Code:

03:00.0 Ethernet controller: Linksys 21x4x DEC-Tulip compatible 10/100 Ethernet (rev 11)
        Subsystem: Linksys 21x4x DEC-Tulip compatible 10/100 Ethernet
        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 (63750ns min, 63750ns max)
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at 3000 [size=256]
        Region 1: Memory at e0400000 (32-bit, non-prefetchable) [size=1K]
        [virtual] Expansion ROM at 60000000 [disabled] [size=128K]
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Code:

eth2      Link encap:Ethernet  HWaddr 00:04:5A:9D:D6:E8
          inet addr:192.168.1.101  Bcast:192.168.1.127  Mask:255.255.255.128
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:80438522 errors:121 dropped:0 overruns:121 frame:121
          TX packets:51228100 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:97017145468 (92522.7 Mb)  TX bytes:6764000964 (6450.6 Mb)
          Interrupt:11 Base address:0x3000

Code:

grep tulip /etc/modprobe.conf
# options tulip          options=0

Determine the kernel module this device uses and check for an "irq" option for that driver.

Code:

# options 3c509          irq=10

Yours may say "irq=169".

KoRiR · 02-23-2008, 09:38 AM

ps,my other Intel NIC interrupt is 185. it works well.

lspci -vvv

03:00.0 Ethernet controller: ABC Networks Inc Unknown device 0003 (rev 01)
Subsystem: Airgo Networks Inc Unknown device 0003
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 169
Region 0: Memory at b8900000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at 40000000 [disabled] [size=64K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express Legacy Endpoint IRQ 0
Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <1us, L1 <8us
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
Link: Latency L0s <512ns, L1 <64us
Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x1

jschiwal · 02-25-2008, 03:59 AM

Do you have the /usr/sbin/hwinfo program? If so could you post the results of "sudo /usr/sbin/hwinfo --netcard"?

Which kernel module does it use? Are both cards using the same kernel module?

There are some instances where if you have a second identical device, you need to change the base io address or the irq. For example, from /etc/modprobe.conf:

Code:

# options ne             io=0x300 irq=5

# Use this if you have two cards:
# options ne             io=0x300,0x320 irq=5,7

Usually the best information on this is to locate your kernel module in /etc/modprobe.conf and to locate documentation on it in the kernel source documentation. For example in /usr/src/linux/Documentation/networking/net-modules.txt. ( note: You may need to install the kernel-documenation package.)

Here is an excerpt to give you an idea.

Code:

ewrk3.c:
        io = 0x300
        irq = 5
        (With module no autoprobing!
         On EISA-bus does EISA probing.
         Static linkage probes ports on ISA bus:
                0x100, 0x120, 0x140, 0x160, 0x180, 0x1A0, 0x1C0,
                0x200, 0x220, 0x240, 0x260, 0x280, 0x2A0, 0x2C0, 0x2E0,
                0x300,        0x340, 0x360, 0x380, 0x3A0, 0x3C0)

hp-plus.c:
        io = 0          (It will complain if you don't supply an "io=0xNNN")
        irq = 0         (IRQ read from configuration register)
        (Probes ports: 0x200, 0x240, 0x280, 0x2C0, 0x300, 0x320, 0x340)

hp.c:
        io = 0          (It will complain if you don't supply an "io=0xNNN")
        irq = 0         (IRQ software selected by driver using autoIRQ)
        (Probes ports: 0x300, 0x320, 0x340, 0x280, 0x2C0, 0x200, 0x240)