Re: Slow network performance

2007-02-16 Thread Vinny Abello

This sounds like your switch and host settings are correct so I wouldn't spend 
too much more time looking at that at this point. I just wanted to mention it 
to be sure.

Good luck!

Dimuthu Parussalla BWEADM non-std-pwd wrote:

This is exactly what I did.
Managed Switch A (2950G)
1) both switch and bge/em card set for auto negeotiation
2) Both switch and bge/em set for 1000mb full-duplex.

Managed Switch B (Netgeat GSM7224)
1) both switch and bge/em card set for auto negeotiation
2) Both switch and bge/em set for 1000mb full-duplex.

I am seriously running out of options.
Thanks

Vinny Abello writes:
Although I don't think this is necessarily the cause of your dropouts 
as you put it, one must understand the way autonegotiation and manual 
speed and duplex work between network gear.
For autonegotiation to work, BOTH devices must support 
autonegotiation, OR both devices must be set to the same speed and 
duplex setting. If one only supports auto and the other does not, you 
must NOT set the device that you can manually configure to full 
duplex. The auto device will never negotiate at full duplex and fall 
back to half when autonegotiation fails, causing a duplex mismatch and 
horrible network performance and loss.

A very rough set of rules of thumb (YMMV):
When connecting to an unmanaged switch, use auto. If your host doesn't 
support auto, set it to half-duplex.
When connecting to a managed switch, make sure the port is set to auto 
and set your system to auto, otherwise force both the switch port and 
your host to the same settings. This is required especially if the 
host doesn't support auto negotiation and you want to run at full duplex.
When connecting to a managed switch, enable portfast or the equivalent 
spanning-tree command on the switch port your host is connected to so 
it forwards traffic immediately when getting link.


So to sum it up, auto only works if both sides speak auto. Auto 
negotiation failure falls back to half-duplex!
Of course there are all the horror stories where auto negotiation is 
evil and that different vendor's implementations don't play nice or 
are just completely broken, so always set things to manual or you and 
your family will suffer an untimely death... There are so many of 
these stories that one would think there has to be some truth to it. 
In my own experience, I have never had an issue with auto negotiation 
in some ten years of working with a dozen different vendors' 
networking gear so I guess I'm lucky... or I just understand how it 
interacts with other devices and their capabilities. I still don't 
know which exactly.


Hope this helps! :)

Dimuthu Parussalla wrote:

Hi All,
Apart from random dropout from the network. Our IBM X236 server 
suffers slow
network performance. I've changed the server from CISCO switch to a 
netgear
switch on a test platform. Also tried 1000m full-duplex setup with no 
auto

negotionation on both ends. Still after few days (3-4) server drops the
connection. And while its working I get 90KBps upload/download with ftp
transfers.
I have treid changing BGE network cards to EM (intel 100/1000) still the
same result. Any idea's to nail this problem?

/etc/sysctl.conf
kern.ipc.maxsockbuf=8388608
kern.ipc.somaxconn=2048
net.inet.tcp.sendspace=3217968
net.inet.tcp.recvspace=3217968
net.inet.tcp.rfc1323=1
#net.inet.tcp.rfc3042=0
net.inet.ip.portrange.hilast=65535
net.inet.ip.portrange.hifirst=49152
net.inet.ip.portrange.last=65535
net.inet.ip.portrange.first=1024
net.inet.tcp.inflight.enable=0
 


/boot/loader.conf
kern.ipc.nmbclusters=32768

Interfaces:
em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
options=bRXCSUM,TXCSUM,VLAN_MTU
inet 192.168.1.12 netmask 0xff00 broadcast 192.168.1.255
ether 00:0e:0c:d0:73:3c
media: Ethernet 1000baseTX full-duplex
status: active
em1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
options=bRXCSUM,TXCSUM,VLAN_MTU
inet 6x.xx.xx.xx netmask 0xffc0 broadcast xxx.xxx.xxx.255
ether 00:0e:0c:9f:f4:5e
media: Ethernet 100baseTX full-duplex
status: active
 


Regards
Dimuthu Parussalla


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to 
[EMAIL PROTECTED]

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


syncer page fault

2007-02-16 Thread Pietro Cerutti

Hello list,
this morning my laptop had a kernel fault:

# uname -a
FreeBSD gahrtop.localhost 6.2-STABLE FreeBSD 6.2-STABLE #8: Tue Feb 13
11:23:37 CET 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GAHRTOP  i386

# kgdb kernel.debug /var/crash/vmcore.0
[GDB will not be able to debug user-mode threads:
/usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as i386-marcel-freebsd.

Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address   = 0x478b4d31
fault code  = supervisor read, page not present
instruction pointer = 0x20:0xc06402af
stack pointer   = 0x28:0xe69b4b90
frame pointer   = 0x28:0xe69b4bcc
code segment= base 0x0, limit 0xf, type 0x1b
   = DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 41 (syncer)
trap number = 12

panic: page fault
cpuid = 1
Uptime: 9h36m3s
Dumping 2039 MB (2 chunks)
 chunk 0: 1MB (159 pages) ... ok
 chunk 1: 2039MB (521936 pages) 2023 2007 1991 1975 1959 1943 1927
1911 1895 1879 1863 1847 1831 1815 1799 1783
1767 1751 1735 1719 1703 1687 1671 1655 1639 1623 1607 1591 1575 1559
1543 1527 1511 1495 1479 1463 1447 1431 141
5 1399 1383 1367 1351 1335 1319 1303 1287 1271 1255 1239 1223 1207
1191 1175 1159 1143 1127  1095 1079 1063 1
047 1031 1015 999 983 967 951 935 919 903 887 871 855 839 823 807 791
775 759 743 727 711 695 679 663 647 631 615
599 583 567 551 535 519 503 487 471 455 439 423 407 391 375 359 343
327 311 295 279 263 247 231 215 199 183 167
151 135 119 103 87 71 55 39 23 7

#0  doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) bt
#0  doadump () at pcpu.h:165
#1  0xc0531e31 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2  0xc0532224 in panic (fmt=0xc06f07d3 %s) at
/usr/src/sys/kern/kern_shutdown.c:565
#3  0xc06c252c in trap_fatal (frame=0xe69b4b50, eva=0) at
/usr/src/sys/i386/i386/trap.c:837
#4  0xc06c21d2 in trap_pfault (frame=0xe69b4b50, usermode=0, eva=1200311601)
   at /usr/src/sys/i386/i386/trap.c:745
#5  0xc06c1d8f in trap (frame=
 {tf_fs = -1065943032, tf_es = -966000600, tf_ds = -426049496,
tf_edi = 0, tf_esi = 4, tf_ebp = -426030132,
tf_isp = -426030212, tf_ebx = -924676096, tf_edx = 3, tf_ecx =
1200311553, tf_eax = 0, tf_trapno = 12, tf_err = 0
, tf_eip = -1067187537, tf_cs = 32, tf_eflags = 66050, tf_esp =
-1067831784, tf_ss = -934932208})
   at /usr/src/sys/i386/i386/trap.c:435
#6  0xc06ab40a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7  0xc06402af in ffs_syncvnode (vp=0xc8461110, waitfor=3) at
/usr/src/sys/ufs/ffs/ffs_vnops.c:198
#8  0xc063ed28 in ffs_sync (mp=0xc66c6a60, waitfor=3, td=0xc647fc00)
at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1173
#9  0xc05a562c in sync_fsync (ap=0x3) at /usr/src/sys/kern/vfs_subr.c:3120
#10 0xc06deb0e in VOP_FSYNC_APV (vop=0x0, a=0x3) at vnode_if.c:1020
#11 0xc05a2184 in sync_vnode (bo=0xc6714e90, td=0xc647fc00) at vnode_if.h:537
#12 0xc05a256f in sched_sync () at /usr/src/sys/kern/vfs_subr.c:1698
#13 0xc0514c30 in fork_exit (callout=0xc05a2280 sched_sync, arg=0x0,
frame=0x0)
   at /usr/src/sys/kern/kern_fork.c:821
#14 0xc06ab46c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208
(kgdb)

--

What info

Pietro Cerutti

- ASCII Ribbon Campaign -
against HTML e-mail and
proprietary attachments
  www.asciiribbon.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Slow network performance

2007-02-16 Thread Sten Daniel Soersdal
Dimuthu Parussalla BWEADM non-std-pwd wrote:
 This is exactly what I did.
 Managed Switch A (2950G)
 1) both switch and bge/em card set for auto negeotiation
 2) Both switch and bge/em set for 1000mb full-duplex.
 
 Managed Switch B (Netgeat GSM7224)
 1) both switch and bge/em card set for auto negeotiation
 2) Both switch and bge/em set for 1000mb full-duplex.
 
 I am seriously running out of options.
 Thanks

What have you done to rule out if it's a faulty cable or noise on the
cable? What kind of cable is it?

net.inet.tcp.sendspace=3217968
net.inet.tcp.recvspace=3217968

Are you sure these two should be set to the millions?
Try reducing them to ~32k or so.

-- 
Sten Daniel Soersdal
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Failed to mount umass with Motorola Razr V3x

2007-02-16 Thread Eric L. Chen
Hi Sergey,
Thanks!
Other umass devices like USB stick flash will no problem to mount.
So, I think my pass is already fine.
And I cvsuped today then it can mount V3x umass device!
Even I did not change my kernel config file.

/Eric

On Fri, 2007-02-16 at 10:24 +0300, AstraSerg wrote:
  xptioctl: pass driver is not in the kernel 
  xptioctl: put device pass0 in your kernel config 
 
 
 On Friday 16 February 2007 05:33, Eric L. Chen wrote:
  Hi,
  I have a Motorola V3x phone with 1GB T-Flash memory card.
  It can mount as a removal drive on Windows XP and Ubuntu, but on FreeBSD
  (6.2 stable) will cause these message (see below) and failed to mount.
  Does any one know how to fix it?
  BTW, If I switch V3x USB as UMTS modem, FreeBSD still cannot use it as
  modem device.
 
  /Eric
 
  --
  umass0: Motorola Inc. Motorola Phone (RAZRV3x), rev 1.10/0.01, addr 2
  umass0: Get Max Lun not supported (SHORT_XFER)
  xptioctl: pass driver is not in the kernel
  xptioctl: put device pass0 in your kernel config filexptioctl: put 
  device 
 pass0 in your kernel config file
  da0 at umass-sim0 bus 0 target 0 lun 0
  da0: Motorola Motorola Phone 2.31 Removable Direct Access SCSI-2
  device
  da0: 1.000MB/s transfers
  da0: 952MB (1950721 512 byte sectors: 64H 32S/T 952C)
  (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1d c4 0 0 0 1 0
  (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
  (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
  (da0:umass-sim0:0:0:0): MEDIUM ERROR asc:0,0
  (da0:umass-sim0:0:0:0): No additional sense information
  (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
  (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1d c4 0 0 0 1 0
  (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
  (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
  (da0:umass-sim0:0:0:0): MEDIUM ERROR asc:0,0
  (da0:umass-sim0:0:0:0): No additional sense information
  (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
  (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1d c4 0 0 0 1 0
  (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
  (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
  (da0:umass-sim0:0:0:0): MEDIUM ERROR asc:0,0
  (da0:umass-sim0:0:0:0): No additional sense information
  (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
  (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1d c4 0 0 0 1 0
  (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
  (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
  (da0:umass-sim0:0:0:0): MEDIUM ERROR asc:0,0
  (da0:umass-sim0:0:0:0): No additional sense information
  (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
  (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1d c4 0 0 0 1 0
  (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
  (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
  (da0:umass-sim0:0:0:0): MEDIUM ERROR asc:0,0
  (da0:umass-sim0:0:0:0): No additional sense information
  (da0:umass-sim0:0:0:0): Retries Exhausted
  --
 


signature.asc
Description: This is a digitally signed message part


Re: Failed to mount umass with Motorola Razr V3x

2007-02-16 Thread Eric L. Chen
Hi All,
I am sorry for that I forgot I modified /usr/src/sys/dev/usb/usbdevs to
make V3x umass device work.
If anyone need mount V3x umass device please use this patch.
/Eric

--- /usr/src/sys/dev/usb/usbdevsThu Feb 15 03:57:15 2007
+++ /usr/src/sys/dev/usb/usbdevsSat Feb 17 00:46:48 2007
@@ -1297,6 +1297,7 @@
 product MOTOROLA SB41000x4100  SB4100 USB Cable Modem
 product MOTOROLA2 A41XV32X  0x2a22  A41x/V32x Mobile Phones
 product MOTOROLA2 E398 0x4810  E398 Mobile Phone
+product MOTOROLA2 RAZRV3X  0x3010  Razr V3x Mobile Phone
 
 /* MultiTech products */
 product MULTITECH ATLAS0xf101  MT5634ZBA-USB modem


On Sat, 2007-02-17 at 00:38 +0800, Eric L. Chen wrote:
 Hi Sergey,
 Thanks!
 Other umass devices like USB stick flash will no problem to mount.
 So, I think my pass is already fine.
 And I cvsuped today then it can mount V3x umass device!
 Even I did not change my kernel config file.
 
 /Eric
 
 On Fri, 2007-02-16 at 10:24 +0300, AstraSerg wrote:
   xptioctl: pass driver is not in the kernel 
   xptioctl: put device pass0 in your kernel config 



signature.asc
Description: This is a digitally signed message part


security issues of aio

2007-02-16 Thread Nicolas Rachinsky
Hallo,

in /sys/conf/NOTES there is a comment
| # Use real implementations of the aio_* system calls.  There are numerous
| # stability and security issues in the current aio code that make it
| # unsuitable for inclusion on machines with untrusted local users.
| options VFS_AIO

Are there still problems with aio?

I only found http://xforce.iss.net/xforce/xfdb/7693, but no
advisory or other hint that this was fixed (I think I must have missed
that somehow). And some closed PRs about fixed problems.

Do these affect aio.ko as well?

Thanks,
Nicolas

-- 
http://www.rachinsky.de/nicolas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: Slow network performance

2007-02-16 Thread Dimuthu Parussalla
Hi Sten,

I have ruled out the faulty cable. Also no errors reporting on the managed
switch. Doing a test with a reduced parameters to 32k.



-Original Message-
From: Sten Daniel Soersdal [mailto:[EMAIL PROTECTED]
Sent: Saturday, 17 February 2007 2:33 AM
To: Dimuthu Parussalla BWEADM non-std-pwd
Cc: Vinny Abello; freebsd-stable@freebsd.org
Subject: Re: Slow network performance


Dimuthu Parussalla BWEADM non-std-pwd wrote:
 This is exactly what I did.
 Managed Switch A (2950G)
 1) both switch and bge/em card set for auto negeotiation
 2) Both switch and bge/em set for 1000mb full-duplex.

 Managed Switch B (Netgeat GSM7224)
 1) both switch and bge/em card set for auto negeotiation
 2) Both switch and bge/em set for 1000mb full-duplex.

 I am seriously running out of options.
 Thanks

What have you done to rule out if it's a faulty cable or noise on the
cable? What kind of cable is it?

net.inet.tcp.sendspace=3217968
net.inet.tcp.recvspace=3217968

Are you sure these two should be set to the millions?
Try reducing them to ~32k or so.

--
Sten Daniel Soersdal



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]