Intel Gigabit NIC problem
I'm posting this to a few lists that I hope I might get some info from. I have been using the fxp driver for quite a while with good results, so when it came time to get some gigabit stuff I looked and saw the wx driver. I decided it would be convenient to stick with Intel for several reasons. So now I have a handful of Compaq NC3131 boards with NC6132 modules. The NC3131 is a 64bit PCI card with a DEC 21154 (later revs have a chip stamped Intel but its id is the same as the DEC) PCI bridge and a couple Intel 82558 chips. It also has an expansion connector. The NC6132 module plugs onto this card to add a gigabit fiber port. The docs say its an Intel 82542 chip, though the actual chip on the boards are stamped LSI. I put them in a few machines here. A couple are x86 boxes with Windows 2000 and/or Linux, for which the Intel drivers work and they interconnect fine. The other is an Alpha running FreeBSD 4.2. The fxp and wx drivers load fine, but I have problems when I connect the gigabit port to another one of the machines. The FreeBSD machine repeated prints "wx0: receive sequence error" while the other machine is overwhelmed with 100% kernel/system CPU usage such that its barely responsive. Does anyone have any idea what's going on, if there's any hope of fixing this, and what the solution would be? Thanks. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Alteon gigE NIC (if_ti) problems
I recent gave up truing to make a Intel gigE NIC work in my Alpha so I got an Alteon board. It works without the severe problem of the Intel card. However, its acting a little weird. I see messages saying the link went down and up quite often. I've tried both 4.3 and 4.4 and have the same thing. I increased NMBCLUSTERS significantly and still see the same thing. I made the switch from 4.3 to 4.4 at the same time I incrased NMBCLUSTERS from 8192 to 32767 so I can't say which, but one (or both) of those changes increased the rate at which I see the link status change message. Before I saw it every once in a while reguardless of whether there was heavy traffic or not. Now it shows up every few seconds when there is any traffic at all. Anyone have any ideas what's going on? BTW, I would include my dmesg but its full of "ti0: link down" and "ti0: gigabit link up" so here's there pertinent info. Alpha 21164PC 533 on PC164SX Alteon gigE card in 64bit PCI slot with IRQ 11 which is not shared If any other info would help, just ask and I'll get it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
RE: Alteon gigE NIC (if_ti) problems
The Intel NIC flooded the remote end (computer or switch) with trash such that the device was unable to process anything as long as the link was up. This occured as long as the computer was on, before the driver loaded or the OS booted, so it wasn't a driver problem. I tried both the wx and gx driver and neither seemed to initialize it in any way that allowed it to work properly. Traffic could pass through the link but the remote end couldn't do much since it was flooded with junk that appeared to be flow-control stuff. With this Alteon card, the remote end is just fine and all traffic passes through. The disconnect appears on the computer. The link light on the switch never goes off when the computer says its link is continously going down and up. I suspect that when it thinks the link drops, all trafffic gets delayed until some timeout period after the link is back, which is why I'm seeing slowdowns. On Tue, 25 Sep 2001 18:36:15 -0400, Jim McGrath wrote: >What kind of problems were you having with the Intel GigE NIC? I've got it >running in an Intel box, the only recent problems have been of my own >making. I found a bug in the code for the copper version of the NIC. Were >you running a fiber or copper NIC? > >I'm not as familiar with the ti driver, but it sounds like a watchdog timer >problem. That will cause a reset of the NIC. > >Jim > >-Original Message- >From: Matthew Rezny [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, September 25, 2001 2:17 PM >To: [EMAIL PROTECTED] >Subject: Alteon gigE NIC (if_ti) problems > > >I recent gave up truing to make a Intel gigE NIC work in my Alpha so I >got an Alteon board. It works without the severe problem of the Intel >card. However, its acting a little weird. I see messages saying the >link went down and up quite often. I've tried both 4.3 and 4.4 and have >the same thing. I increased NMBCLUSTERS significantly and still see the >same thing. I made the switch from 4.3 to 4.4 at the same time I >incrased NMBCLUSTERS from 8192 to 32767 so I can't say which, but one >(or both) of those changes increased the rate at which I see the link >status change message. Before I saw it every once in a while >reguardless of whether there was heavy traffic or not. Now it shows up >every few seconds when there is any traffic at all. Anyone have any >ideas what's going on? > >BTW, I would include my dmesg but its full of "ti0: link down" and >"ti0: gigabit link up" so here's there pertinent info. >Alpha 21164PC 533 on PC164SX >Alteon gigE card in 64bit PCI slot with IRQ 11 which is not shared >If any other info would help, just ask and I'll get it. > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Alteon gigE NIC (if_ti driver) problems
I have some more information since my initial posting yesterday. I set the NMBCLUSTERS back to default, which made no difference. Therefore, moving from 4.3 to 4.4 is what drastically increased the frequency at which the link goes down and back up. I also captured dmesg now I case there is any useful information in it. The fluctuation of the link occurs multiple times a second with the new kernel when attempting to use the network with this machine. Any suggestions would be greatly appreciated. Thanks. Unrecognized boot flag '0'. Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.4-RELEASE #1: Tue Sep 25 22:54:14 CDT 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/CUSTOM EB164 Digital AlphaPC 164SX 533 MHz, 531MHz 8192 byte page size, 1 processor. CPU: PCA56 (21164PC) major=9 minor=2 extensions=0x101 OSF PAL rev: 0x1000600020117 real memory = 400474112 (391088K bytes) avail memory = 383492096 (374504K bytes) Preloaded elf kernel "kernel" at 0xfc6d4000. ccd0-3: Concatenated disk drivers md0: Malloc disk cia0: Pyxis, pass 1 cia0: extended capabilities: 1 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 atapci0: port 0x1000-0x10ff,0x1320-0x1323,0x1310-0x1317 irq 9 at device 5.0 on pci0 ata2: at 0x1310 on atapci0 atapci0: interrupting at CIA irq 9 atapci1: port 0x1100-0x11ff,0x1324-0x1327,0x1318-0x131f irq 9 at device 5.1 on pci0 ata3: at 0x1318 on atapci1 atapci1: interrupting at CIA irq 9 ti0: mem 0x8285-0x82853fff irq 11 at device 6.0 on pci0 ti0: interrupting at CIA irq 11 ti0: Ethernet address: 00:60:cf:20:1e:99 sym0: <875> port 0x1200-0x12ff mem 0x82858000-0x82858fff,0x8285a000-0x8285a0ff irq 10 at device 7.0 on pci0 sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking sym0: interrupting at CIA irq 10 isab0: at device 8.0 on pci0 isa0: on isab0 atapci2: port 0x1300-0x130f,0x3f4-0x3f7,0x1f0-0x1f7 at device 8.1 on pci0 atapci3: port 0x374-0x377,0x170-0x177 at device 8.2 on pci0 atapci3: Busmastering DMA not configured pci0: at 8.3 pci0: at 9.0 irq 8 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd0: interrupting at ISA irq 1 psm0: irq 12 on atkbdc0 psm0: interrupting at ISA irq 12 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o ppc0: at port 0x3bc-0x3bf irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: cannot reserve interrupt, failed. ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Polled port ppc0: interrupting at ISA irq 7 sbc0: at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 sbc0: interrupting at ISA irq 5 pcm0: on sbc0 Timecounter "alpha" frequency 533166528 Hz IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging disabled ad0: 34837MB [70780/16/63] at ata2-master UDMA66 ad1: 34837MB [70780/16/63] at ata3-master UDMA66 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0a da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4339MB (8887200 512 byte sectors: 255H 63S/T 553C) cd0 at sym0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up ti0: link down ti0: gigabit link up To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: Alteon gigE NIC (if_ti driver) problems
Thanks for the suggestion, it set me in the right direction. I checked my fibre before but went ahead and checked it again. In doing so, I rearranged the cables at the switch to check if that made a difference. Sure enough, one port on the switch makes the connection drop often. I hope its just dust in the port and not something more serious. The important thing is it looks like everything is working now. On Thu, 27 Sep 2001 09:25:52 -0600, Kenneth D. Merry wrote: >On Wed, Sep 26, 2001 at 15:55:30 -0500, Matthew Rezny wrote: >> I have some more information since my initial posting yesterday. I set >> the NMBCLUSTERS back to default, which made no difference. Therefore, >> moving from 4.3 to 4.4 is what drastically increased the frequency at >> which the link goes down and back up. I also captured dmesg now I case >> there is any useful information in it. The fluctuation of the link >> occurs multiple times a second with the new kernel when attempting to >> use the network with this machine. Any suggestions would be greatly >> appreciated. Thanks. > >[ ... ] > >> ti0: mem >> 0x8285-0x82853fff irq 11 at device 6.0 on pci0 >> ti0: interrupting at CIA irq 11 >> ti0: Ethernet address: 00:60:cf:20:1e:99 > >[ ... ] > >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >> ti0: link down >> ti0: gigabit link up >[ ... ] > >The most likely explanation for this is that you've got a bad/dirty >piece of fiber. The number of mbuf clusters probably isn't going to >affect this at all, unless you're dumping a lot of traffic over the >NIC and increasing the number of mbufs allows you to dump more >packets. > >So I'd say replace your fiber. > >Ken >-- >Kenneth Merry >[EMAIL PROTECTED] > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
