Re: Frustrating network latency issue on NetBSD 6.1

2013-06-20 Thread Mayuresh
On Wed, Jun 19, 2013 at 11:53:42AM -0400, Greg Troxel wrote: Use ping, not ssh, to be able to have a more isolated test case and get quantitative data. In particular, separate loss from delay; both present as delay over TCP. 64 bytes from 192.168.169.1: icmp_seq=0 ttl=64 time=6.781 ms 64 bytes

Re: Frustrating network latency issue on NetBSD 6.1

2013-06-20 Thread Christos Zoulas
In article 20130620091543.ga29...@sdf.org, Mayuresh mayur...@acm.org wrote: On Wed, Jun 19, 2013 at 11:53:42AM -0400, Greg Troxel wrote: Use ping, not ssh, to be able to have a more isolated test case and get quantitative data. In particular, separate loss from delay; both present as delay

Re: Frustrating network latency issue on NetBSD 6.1

2013-06-20 Thread Martin S. Weber
On Thu, Jun 20, 2013 at 12:54:24PM +, Christos Zoulas wrote: In article 20130620091543.ga29...@sdf.org, Mayuresh mayur...@acm.org wrote: (...) 25 packets transmitted, 16 packets received, 36.0% packet loss round-trip min/avg/max/stddev = 1.937/2.639/6.781/1.253 ms I think 36% is a

Re: Frustrating network latency issue on NetBSD 6.1

2013-06-20 Thread David Lord
On 20 Jun 2013 at 20:36, Mayuresh wrote: On Thu, Jun 20, 2013 at 12:45:08PM -, David Lord wrote: I think 36% is a large number for packet loss? It is unless the link is very busy when icmp might be dropped. Ok, I'll check whether there is a way in this router to check its

Re: Frustrating network latency issue on NetBSD 6.1

2013-06-20 Thread Mayuresh
On Thu, Jun 20, 2013 at 04:55:17PM -, David Lord wrote: If the problems only started since you upgraded to NetBSD-6.1 that suggests either a misconfiguration or an incompatibility has been introduced. Have you compared /var/boot/dmesg.boot and /var/log/messages for errors from before

modular-xorg-server PLIST errors

2013-06-20 Thread Mayuresh
I am getting following warnings (particularly see the PLIST warnings at the bottom), with PKG_DEVELOPER option set. I got away by disabling above option. But perhaps this needs attention. libtool-fortran: install: warning: remember to run `libtool-fortran --finish

Re: issues running i386 6.1 under VirtualBox 4.2.12

2013-06-20 Thread Malcolm Herbert
On Fri, Jun 21, 2013, at 9:11, Malcolm Herbert wrote: Hi all - I'm trying to put together a small i386 6.1 host running under a 32-bit version of Windows 7 using VirtualBox 4.2.12. At the moment I can't boot the VM guest from the NetBSD-6.1-i386.iso image as the install kernel panics (all

Re: Lost touchpad support after upgrading to modular-xorg in current pkgsrc

2013-06-20 Thread OBATA Akio
No volunteer http://mail-index.netbsd.org/tech-pkg/2013/06/13/msg011553.html On Fri, 21 Jun 2013 04:03:18 +0900, Mayuresh mayur...@acm.org wrote: On NetBSD 6.1 i386, I was using modular-xorg so far. I did not intend to touch x11 installation until some package build forced it. Now after

Re: Lost touchpad support after upgrading to modular-xorg in current pkgsrc

2013-06-20 Thread Mayuresh
On Fri, Jun 21, 2013 at 09:18:27AM +0900, OBATA Akio wrote: No volunteer http://mail-index.netbsd.org/tech-pkg/2013/06/13/msg011553.html Any chance we can downgrade to the working state again? Mayuresh

Re: Lost touchpad support after upgrading to modular-xorg in current pkgsrc

2013-06-20 Thread Mayuresh
On Fri, Jun 21, 2013 at 12:33:18AM +0530, Mayuresh wrote: On NetBSD 6.1 i386, I was using modular-xorg so far. I did not intend to touch x11 installation until some package build forced it. Now after upgrading to current version my laptop touchpad which was working so far has stopped

Re: Frustrating network latency issue on NetBSD 6.1

2013-06-20 Thread Mayuresh
On Thu, Jun 20, 2013 at 09:38:34PM -0400, Greg Troxel wrote: The next thing I'd want to know is if the loss is in transmitted or received packets. To do that you'll need to be able to tcpdump on the target, or get at counters. (Look at netstat -s; it's often useful to capture netstat -s, do