< I don't think you ran out of mbufs (you would have noticed) so that
> rules out case #1. Checking cases #2 and #3 requires adding a little
> instrumentation to the driver. If the XL_RXSTAT_UP_ERROR bit is being
> detected in xl_rxeof(), you can print out the status word and see
> if any of the fo
> > > I would say the physical wire is probably bad. Seeing unidirectional
> > errors
> > > in this case wouldn't be uncommon; one of the pair of the receive
wires
> > may
> > > have issues. Have you swapped the cable? Most of the time you won't
see
> > > framing errors related to duplex mismatc
> > I would say the physical wire is probably bad. Seeing unidirectional
> errors
> > in this case wouldn't be uncommon; one of the pair of the receive wires
> may
> > have issues. Have you swapped the cable? Most of the time you won't see
> > framing errors related to duplex mismatching.
>
>
> >> Hello:
> >>
> >> Judging from your output I would say two things:
> >>
> >> 1) You have a bad cable. CRC and framing errors are usually a result
of
> > bad
> >> media.
> >> 2) You should set the port to auto/auto, not 100/Full hard set, unless
you
> >> have specifically set that up in rc.conf
> > Ok.. It is set hard to 100BT/FD on both ends. I don't know if you saw
this,
> > but since resetting the stats a few hours ago, it shows no errors at all
on
> > their end, but were still getting errors on our end... The CRC and frame
> > errors could have been from a media mismatch when things w
On 6/27/03 12:29 PM, "Shawn Ramsey" <[EMAIL PROTECTED]> wrote:
>> Hello:
>>
>> Judging from your output I would say two things:
>>
>> 1) You have a bad cable. CRC and framing errors are usually a result of
> bad
>> media.
>> 2) You should set the port to auto/auto, not 100/Full hard set, unless
> Hello:
>
> Judging from your output I would say two things:
>
> 1) You have a bad cable. CRC and framing errors are usually a result of
bad
> media.
> 2) You should set the port to auto/auto, not 100/Full hard set, unless you
> have specifically set that up in rc.conf. If one side is hard set a
Hello:
Judging from your output I would say two things:
1) You have a bad cable. CRC and framing errors are usually a result of bad
media.
2) You should set the port to auto/auto, not 100/Full hard set, unless you
have specifically set that up in rc.conf. If one side is hard set and the
other i
> Improperly negotiating 100-BT/FD and generating lots of late collisions,
> for one. Is the switch managed? What does it's syslog output or the
> local CLI say about the port(s) in question? In Cisco parlance, you may
> want to clear the interface counters and observe 'sh int...' output while
>
Mike Hoskins, the prominent pundit, on Wed, Jun 25, 2003 at 17:13
while half mumbling, half-witicized:
> On Wed, 25 Jun 2003, Shawn Ramsey wrote:
>
> > I don't know offhand, it connects to another company, as its
> > our internet connection. We will contact them and see if they
> > can tell us w
> (if any, I believe its a Cisco). The card is forced to 100BT/FD on our end,
> and im sure it is on the other end, though I will have them double check
If your card is forced to FD and the other end is not, this is "very
bad" (and according to the standard should fall back into SD).
Olivier
> Hmm. Definately try the NIC swap then, couldn't hurt. What's your `uname
> -a`? This is something recent, right?
4.7-RELEASE
> > Thats one idea I was planning on doing, just to be sure its not a NIC
issue.
> > I am also going to try replacing the motherboard with one with a 64-bit
bus,
> > a
On Wed, 25 Jun 2003, Shawn Ramsey wrote:
> I don't know offhand, it connects to another company, as its our internet
> connection. We will contact them and see if they can tell us what the stats
> (if any, I believe its a Cisco). The card is forced to 100BT/FD on our end,
> and im sure it is on the
> Improperly negotiating 100-BT/FD and generating lots of late collisions,
> for one. Is the switch managed? What does it's syslog output or the
> local CLI say about the port(s) in question? In Cisco parlance, you may
I don't know offhand, it connects to another company, as its our internet
co
On Wed, 25 Jun 2003, Shawn Ramsey wrote:
> > netstat -I xl0 -w 1
>input (xl0) output
> packets errs bytespackets errs bytes colls
> 6918228525822 5631 02770466 0
> 7317219262852 6041 02696855
> netstat -I xl0 -w 1
input (xl0) output
packets errs bytespackets errs bytes colls
6918228525822 5631 02770466 0
7317219262852 6041 02696855 0
783926 10090955 6426 0
16 matches
Mail list logo
