Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 02 Oct 1998 09:57:32 -0700
From:      Mike Smith <mike@smith.net.au>
To:        Steve Price <sprice@hiwaay.net>
Cc:        current@FreeBSD.ORG
Subject:   Re: bizarre behavior with vx0 driver? 
Message-ID:  <199810021657.JAA00442@dingo.cdrom.com>
In-Reply-To: Your message of "Fri, 02 Oct 1998 10:23:51 CDT." <Pine.OSF.4.02.9810020958260.17547-100000@fly.HiWAAY.net> 

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> Anyone using the vx0 driver and seeing behavior like this?
> This is on a -current box CVSup'd and rebuilt yesterday.

This is classic "interrupts not happening, running on watchdog" 
behaviour.  If you're -current, it means you can't use the xl driver I 
guess.  Dump the card; it sucks and so does our driver for it.

> steve[~]$ ping 152.136.53.1
> PING 152.136.53.1 (152.136.53.1): 56 data bytes
> 64 bytes from 152.136.53.1: icmp_seq=0 ttl=128 time=766.484 ms
> 64 bytes from 152.136.53.1: icmp_seq=1 ttl=128 time=750.168 ms
> 64 bytes from 152.136.53.1: icmp_seq=2 ttl=128 time=740.206 ms
> 64 bytes from 152.136.53.1: icmp_seq=3 ttl=128 time=730.236 ms
> 64 bytes from 152.136.53.1: icmp_seq=4 ttl=128 time=720.217 ms
> ...
> 64 bytes from 152.136.53.1: icmp_seq=72 ttl=128 time=40.358 ms
> 64 bytes from 152.136.53.1: icmp_seq=73 ttl=128 time=30.149 ms
> 64 bytes from 152.136.53.1: icmp_seq=74 ttl=128 time=20.275 ms
> 64 bytes from 152.136.53.1: icmp_seq=75 ttl=128 time=10.170 ms
> 64 bytes from 152.136.53.1: icmp_seq=76 ttl=128 time=1000.241 ms
> 64 bytes from 152.136.53.1: icmp_seq=77 ttl=128 time=999.727 ms
> 64 bytes from 152.136.53.1: icmp_seq=78 ttl=128 time=980.251 ms
> 64 bytes from 152.136.53.1: icmp_seq=79 ttl=128 time=970.184 ms
> 64 bytes from 152.136.53.1: icmp_seq=80 ttl=128 time=960.158 ms
> 64 bytes from 152.136.53.1: icmp_seq=81 ttl=128 time=950.191 ms
> ...
> 64 bytes from 152.136.53.1: icmp_seq=172 ttl=128 time=40.162 ms
> 64 bytes from 152.136.53.1: icmp_seq=173 ttl=128 time=30.231 ms
> 64 bytes from 152.136.53.1: icmp_seq=174 ttl=128 time=20.129 ms
> 64 bytes from 152.136.53.1: icmp_seq=175 ttl=128 time=10.177 ms
> 64 bytes from 152.136.53.1: icmp_seq=176 ttl=128 time=1000.484 ms
> 64 bytes from 152.136.53.1: icmp_seq=177 ttl=128 time=998.454 ms
> 64 bytes from 152.136.53.1: icmp_seq=178 ttl=128 time=980.176 ms
> 64 bytes from 152.136.53.1: icmp_seq=179 ttl=128 time=970.329 ms
> 64 bytes from 152.136.53.1: icmp_seq=180 ttl=128 time=960.252 ms
> 64 bytes from 152.136.53.1: icmp_seq=181 ttl=128 time=950.236 ms
> 64 bytes from 152.136.53.1: icmp_seq=182 ttl=128 time=940.238 ms
> 64 bytes from 152.136.53.1: icmp_seq=183 ttl=128 time=930.245 ms
> 64 bytes from 152.136.53.1: icmp_seq=184 ttl=128 time=920.239 ms
> ^C
> --- 152.136.53.1 ping statistics ---
> 185 packets transmitted, 182 packets received, 1% packet loss
> round-trip min/avg/max/stddev = 10.170/480.184/1000.484/285.083 ms
> 
> Thanks,
> 
> Steve
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
\\  Sometimes you're ahead,       \\  Mike Smith
\\  sometimes you're behind.      \\  mike@smith.net.au
\\  The race is long, and in the  \\  msmith@freebsd.org
\\  end it's only with yourself.  \\  msmith@cdrom.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810021657.JAA00442>