net card
Nicholas J Kreucher
kreucher@msu.edu
Tue Sep 21 19:51:35 1999
actually right now i am using the 3com linux drivers. the drivers that
were talked about on donald becker's mailing list. i'm having the same
problem with those drivers also. i wasn't having these problems before
(like a month ago) either.... so i dunno. i think i might call 3com and
see if it is still under warranty, and maybe get a new one.
let me know if you think you might have a software fix...
- nick
On 21-Sep-99 Mike Cappella wrote:
> Nick - You have confirmed what I suspected. The problem that you are
> experiencing MAY be that the driver isn't taking care of a certain
> issue
> with the hardware. I've sent the appropriate information to Donald
> Becker,
> requesting that he update his driver to accomodate this problem.
>
> I'll update you as I can ... for now hold tight.
>
> Mike
>
>> -----Original Message-----
>> From: nick@c523198-a.elnsng1.mi.home.com
>> [mailto:nick@c523198-a.elnsng1.mi.home.com]On Behalf Of Nicholas J
> Kreucher
>> Sent: Monday, September 20, 1999 8:34 PM
>> To: Mike Cappella
>> Subject: RE: Rx error: status 08 and 8c
>>
>> hello... i finally opened my computer up to look. here's the info on
>> the chip:
>>
>> Parallel Tasking II
>> PERFORMANCE
>> 3Com 40-0483-001
>> 9816K 13522-432
>> LUCENT 40-04831
>>
>> what do you know?
>>
>> - nick
>>
>>
>> On 09-Sep-99 Mike Cappella wrote:
>> > Nicholas,
>> >
>> > I might be able to help, but need some information first.
>> > Can
>> you
>> > look at
>> > the Chip on the 3c905B and give me the numbers on it? It's the
>> > large
>> > chip
>> > on the card, either manufactured by Lucent, Broadcom, or another
>> > manufacturer who I forget. No promises...
>> >
>> > Mike
>> >
>> > ----
>> > Mike Cappella
>> > cappella@pacbell.net
>> >
>> > -----Original Message-----
>> > From: Nicholas J Kreucher [mailto:kreucher@msu.edu]
>> > Sent: Thursday, September 09, 1999 12:56 AM
>> > To: linux-vortex-bug@beowulf.gsfc.nasa.gov
>> > Subject: Re: Rx error: status 08 and 8c
>> >
>> >
>> >
>> >
>> > hello again. i double checked my cables etc. i used a cable from a
>> > 100% working computer, and i even used that hub port too. still
>> > got
>> > the
>> > crc errors. i then thought it might be something in the connector
>> > on
>> > the card. so i turned off my computer (a rare thing!) and yanked
>> > the
>> > 3com card. everything looked ok... nothing seemed jammed in the
>> > Twisted
>> > pair connector anywhere. i even put it back in a different PCI
>> > slot,
>> > booted up, and still -- errors and bad pings.
>> >
>> > On 08-Sep-99 Donald Becker wrote:
>> >> On Wed, 8 Sep 1999, Nicholas J Kreucher wrote:
>> >>
>> >>> hello... i am getting performance problems with my 3c905B card.
>> >>> pings
>> >>> are about 5-20% loss... and i get Rx errors in /sbin/ifconfig. i
>> >>> changed
>> >>> the debug for the module to 4 and the Rx error messages i get
>> >>> are:
>> >>>
>> >>> Rx error: status 08
>> >>> Rx error: status 0c
>> >>
>> >> You are getting CRC errors.
>> >> This should be reported in /proc/net/dev.
>> >
>> > ok, i checked it out and here it is:
>> >
>> > Inter-| Receive |
>> > Transmit
>> > face |bytes packets errs drop fifo frame compressed
>> > multicast|bytes
>> > packets errs drop fifo colls carrier compressed
>> > lo: 11393 164 0 0 0 0 0 0
>> > 11393 164 0 0 0 0 0 0
>> > eth0:64502151 177569 3447 0 0 5181 0 0
>> > 3557485 27270 0 0 0 0 0 0
>> >
>> > sorry it looks kinda gumbled, but it's readable still... kinda. ;)
>> > i
>> > guess the thing noticing is the Rx errors (and maybe frames too?)
>> >
>> >
>> >>> i was looking though the mailing list archive and a suggestion
>> >>> for
>> >>> Rx
>> >>> errors for the 2.2.5-22 redhat 6.0 kernel was to add a route the
>> >>> main
>> >>> interface route with a window of 2048. i did this and the errors
>> >>> became
>> >>> less frequent, but pings were still pretty bad (~15%).
>> >>
>> >> ????
>> >> This will speed up retransmission, but it's just papering over
>> >> the
>> >> underlying problem. It won't help the packet loss rate.
>> >
>> >
>> > hmmm ok makes sence...
>> >
>> >
>> >>> i tried a different cable, port etc and still no improvement. i
>> >>> tried a
>> >>> different computer (windows & different net card though) and
>> >>> pings
>> >>> were
>> >>> 100% using same port and cable.
>> >>
>> >> Double check that. CRC errors are usually the result of the
>> >> cable
>> >> or
>> >> connector.
>> >> (I'm assuming that you are using twisted pair.)
>> >>
>> >>> i also tried putting full_duplex in 1 and 0, nothing really
>> >>> changed much between the two. also tried options=8, but nothing
>> >>> really
>> >>> changed much either...
>> >>
>> >> Normally I would blame a duplex mismatch.
>> >> Never force full duplex unless you are talking to an ancient
>> >> switch.
>> >
>> > ok... i reloaded the module with no options now...
>> >
>> > have any other ideas? i am afraid my card might be going bad... i
>> > bought this card because i thought it would last longer than any
>> > of
>> > the
>> > el-cheapo brands. (about a year old now) kinda sad if it does turn
>> > out
>> > to be bad...
>> >
>> > pings are around 10% loss at the time of my writing this...
>> >
>> > thanks again.
>> >
>> > - nick
>>
>>
>
>
>
>
>
> ----
> Mike Cappella
> cappella@pacbell.net
>