8.0 regression: wired network slow to initialise ?

2010-01-08 Thread martinko

Hi,

$ grep sk0 /etc/rc.conf.local
ifconfig_sk0=DHCP

When booting up or netif restart:

Starting Network: lo0 sk0.
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384
options=3RXCSUM,TXCSUM
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff00
sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=bRXCSUM,TXCSUM,VLAN_MTU
ether 00:11:22:33:44:55
media: Ethernet autoselect (none)
status: no carrier
^^

Please note that on older versions of FreeBSD it printed 'status: 
active' and also IP address obtained via DHCP.  The same now happens 
whether booting up or restarting via /etc/rc.d/netif and is a bit 
confusing at best.  Other network services starting on boot seem to be 
not affected at least.


Regards,

Martin

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


[releng_8_0 tinderbox] failure on amd64/amd64

2010-01-08 Thread FreeBSD Tinderbox
TB --- 2010-01-08 07:49:25 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-01-08 07:49:25 - starting RELENG_8_0 tinderbox run for amd64/amd64
TB --- 2010-01-08 07:49:25 - cleaning the object tree
TB --- 2010-01-08 07:49:59 - cvsupping the source tree
TB --- 2010-01-08 07:49:59 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca 
/tinderbox/RELENG_8_0/amd64/amd64/supfile
TB --- 2010-01-08 07:50:28 - building world
TB --- 2010-01-08 07:50:28 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-01-08 07:50:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-01-08 07:50:28 - TARGET=amd64
TB --- 2010-01-08 07:50:28 - TARGET_ARCH=amd64
TB --- 2010-01-08 07:50:28 - TZ=UTC
TB --- 2010-01-08 07:50:28 - __MAKE_CONF=/dev/null
TB --- 2010-01-08 07:50:28 - cd /src
TB --- 2010-01-08 07:50:28 - /usr/bin/make -B buildworld
 World build started on Fri Jan  8 07:50:29 UTC 2010
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
 stage 4.2: building libraries
 stage 4.3: make dependencies
 stage 4.4: building everything
 stage 5.1: building 32 bit shim libraries
 World build completed on Fri Jan  8 09:16:06 UTC 2010
TB --- 2010-01-08 09:16:06 - generating LINT kernel config
TB --- 2010-01-08 09:16:06 - cd /src/sys/amd64/conf
TB --- 2010-01-08 09:16:06 - /usr/bin/make -B LINT
TB --- 2010-01-08 09:16:06 - building LINT kernel
TB --- 2010-01-08 09:16:06 - MAKEOBJDIRPREFIX=/obj
TB --- 2010-01-08 09:16:06 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2010-01-08 09:16:06 - TARGET=amd64
TB --- 2010-01-08 09:16:06 - TARGET_ARCH=amd64
TB --- 2010-01-08 09:16:06 - TZ=UTC
TB --- 2010-01-08 09:16:06 - __MAKE_CONF=/dev/null
TB --- 2010-01-08 09:16:06 - cd /src
TB --- 2010-01-08 09:16:06 - /usr/bin/make -B buildkernel KERNCONF=LINT
 Kernel build for LINT started on Fri Jan  8 09:16:06 UTC 2010
 stage 1: configuring the kernel
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3.1: making dependencies
 stage 3.2: building everything
[...]
objcopy --strip-debug if_ae.ko
=== age (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc   
-DHAVE_KERNEL_OPTION_HEADERS -include /obj/src/sys/LINT/opt_global.h -I. -I@ 
-I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000 -fno-common  -fno-omit-frame-pointer 
-I/obj/src/sys/LINT -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse 
-mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  -msoft-float 
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector 
-std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions -c 
/src/sys/modules/age/../../dev/age/if_age.c
/src/sys/modules/age/../../dev/age/if_age.c: In function 'age_attach':
/src/sys/modules/age/../../dev/age/if_age.c:468: internal compiler error: 
Segmentation fault: 11
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://gcc.gnu.org/bugs.html for instructions.
*** Error code 1

Stop in /src/sys/modules/age.
*** Error code 1

Stop in /src/sys/modules.
*** Error code 1

Stop in /obj/src/sys/LINT.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2010-01-08 09:29:48 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2010-01-08 09:29:48 - ERROR: failed to build lint kernel
TB --- 2010-01-08 09:29:48 - 4459.66 user 980.41 system 6022.95 real


http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8_0-amd64-amd64.full
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


8.0 regression: wireless network slow to initialise ?

2010-01-08 Thread martinko

Hi,

$ egrep 'sk0|wlan' /etc/rc.conf.local
ifconfig_sk0=DHCP
wlans_iwi0=wlan0
ifconfig_wlan0=WPA DHCP

When booting up or netif restart:

Starting Network: lo0 sk0.
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384
options=3RXCSUM,TXCSUM
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff00
sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=bRXCSUM,TXCSUM,VLAN_MTU
ether 00:11:22:33:44:55
media: Ethernet autoselect (none)
status: no carrier

Please note that iwi/wlan is not even mentioned. (!)
The same happens whether booting up or via /etc/rc.d/netif restart.

On older versions of FreeBSD iwi0 was turned up and associated.
With 8.0 I am getting errors from services started on boot that try to 
reach the network (e.g. ntpd).  It also seems to break lagg for me.


Regards,

Martin

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


driver bug: Unable to set devclass (devname: (null))

2010-01-08 Thread martinko

Hi,

This is 8.0-RELEASE-p2 and I see the following during boot:

Jan  8 09:38:46 mb-aw1n-bsd kernel: Timecounter TSC frequency 
1993542975 Hz quality 800

Jan  8 09:38:46 mb-aw1n-bsd kernel: Timecounters tick every 1.000 msec
Jan  8 09:38:46 mb-aw1n-bsd kernel: firewire0: 1 nodes, maxhop = 0 
cable IRM irm(0)  (me)

Jan  8 09:38:46 mb-aw1n-bsd kernel: firewire0: bus manager 0
Jan  8 09:38:46 mb-aw1n-bsd kernel: usbus0: 12Mbps Full Speed USB v1.0
Jan  8 09:38:46 mb-aw1n-bsd kernel: usbus1: 12Mbps Full Speed USB v1.0
Jan  8 09:38:46 mb-aw1n-bsd kernel: usbus2: 12Mbps Full Speed USB v1.0
Jan  8 09:38:46 mb-aw1n-bsd kernel: usbus3: 480Mbps High Speed USB v2.0
Jan  8 09:38:46 mb-aw1n-bsd kernel: driver bug: Unable to set devclass 
(devname: (null))

^^-- ???
Jan  8 09:38:46 mb-aw1n-bsd kernel: ad0: 76319MB HTS548080M9AT00 
MG4OA53A at ata0-master UDMA100


I'm not sure which driver spits it out -- perhaps new USB stack ?

Regards,

Martin

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


Re: driver bug: Unable to set devclass (devname: (null))

2010-01-08 Thread pluknet
2010/1/8 martinko gam...@users.sf.net:
 Hi,

 This is 8.0-RELEASE-p2 and I see the following during boot:

 Jan  8 09:38:46 mb-aw1n-bsd kernel: Timecounter TSC frequency 1993542975
 Hz quality 800
 Jan  8 09:38:46 mb-aw1n-bsd kernel: Timecounters tick every 1.000 msec
 Jan  8 09:38:46 mb-aw1n-bsd kernel: firewire0: 1 nodes, maxhop = 0 cable
 IRM irm(0)  (me)
 Jan  8 09:38:46 mb-aw1n-bsd kernel: firewire0: bus manager 0
 Jan  8 09:38:46 mb-aw1n-bsd kernel: usbus0: 12Mbps Full Speed USB v1.0
 Jan  8 09:38:46 mb-aw1n-bsd kernel: usbus1: 12Mbps Full Speed USB v1.0
 Jan  8 09:38:46 mb-aw1n-bsd kernel: usbus2: 12Mbps Full Speed USB v1.0
 Jan  8 09:38:46 mb-aw1n-bsd kernel: usbus3: 480Mbps High Speed USB v2.0
 Jan  8 09:38:46 mb-aw1n-bsd kernel: driver bug: Unable to set devclass
 (devname: (null))
                                    ^^-- ???
 Jan  8 09:38:46 mb-aw1n-bsd kernel: ad0: 76319MB HTS548080M9AT00 MG4OA53A
 at ata0-master UDMA100

 I'm not sure which driver spits it out -- perhaps new USB stack ?


There was a thread which might be helpful to identify a buggy driver:
http://lists.freebsd.org/pipermail/freebsd-current/2009-March/004272.html

-- 
wbr,
pluknet
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


in openpam_dispatch(): pam_nologin.so: no pam_sm_authenticate() / pam_sm_setcred()

2010-01-08 Thread martinko

Hi,

Since moving from 6.4 to 8.0 I see the following in /var/log/messages:

Jan  8 09:39:04 mb-aw1n-bsd : in openpam_dispatch(): pam_nologin.so: no 
pam_sm_authenticate()
Jan  8 09:39:04 mb-aw1n-bsd : in openpam_dispatch(): pam_nologin.so: no 
pam_sm_setcred()


It seems to be triggered by x11/wdm port.

$ grep wdm /etc/ttys
ttyv8   /usr/local/bin/wdm -nodaemon  xterm   on  secure

However I'm not sure who is to blame -- FreeBSD or WDM .. ?

Regards,

Martin

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


kernel: warning: attempt to domain_add(bluetooth) after domainfinalize()

2010-01-08 Thread martinko

Hi,

I've been seeing the following on 7.x and 8.0 during boot:

Jan  8 09:38:49 mb-aw1n-bsd kernel: WARNING: attempt to 
domain_add(bluetooth) after domainfinalize()


It did not happen on 6.x.  Is it a known issue ?

Regards,

Martin

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


Re: 8.0 regression: wired network slow to initialise ?

2010-01-08 Thread John Baldwin
On Friday 08 January 2010 4:23:09 am martinko wrote:
 Hi,
 
 $ grep sk0 /etc/rc.conf.local
 ifconfig_sk0=DHCP
 
 When booting up or netif restart:
 
 Starting Network: lo0 sk0.
 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384
  options=3RXCSUM,TXCSUM
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
  inet6 ::1 prefixlen 128
  inet 127.0.0.1 netmask 0xff00
 sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
  options=bRXCSUM,TXCSUM,VLAN_MTU
  ether 00:11:22:33:44:55
  media: Ethernet autoselect (none)
  status: no carrier
  ^^
 
 Please note that on older versions of FreeBSD it printed 'status: 
 active' and also IP address obtained via DHCP.  The same now happens 
 whether booting up or restarting via /etc/rc.d/netif and is a bit 
 confusing at best.  Other network services starting on boot seem to be 
 not affected at least.

SYNCDHCP would probably restore the old behavior but make your boot take 
longer.

-- 
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: 8.0 regression: wireless network slow to initialise ?

2010-01-08 Thread John Baldwin
On Friday 08 January 2010 4:38:40 am martinko wrote:
 Hi,
 
 $ egrep 'sk0|wlan' /etc/rc.conf.local
 ifconfig_sk0=DHCP
 wlans_iwi0=wlan0
 ifconfig_wlan0=WPA DHCP
 
 When booting up or netif restart:
 
 Starting Network: lo0 sk0.
 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384
  options=3RXCSUM,TXCSUM
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
  inet6 ::1 prefixlen 128
  inet 127.0.0.1 netmask 0xff00
 sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
  options=bRXCSUM,TXCSUM,VLAN_MTU
  ether 00:11:22:33:44:55
  media: Ethernet autoselect (none)
  status: no carrier
 
 Please note that iwi/wlan is not even mentioned. (!)
 The same happens whether booting up or via /etc/rc.d/netif restart.

Yes, the part of the netif script that prints out interfaces doesn't handle 
child interfaces like wlan or vlan devices currently.  I'm not fully sure of 
the best way to fix it.

 On older versions of FreeBSD iwi0 was turned up and associated.
 With 8.0 I am getting errors from services started on boot that try to 
 reach the network (e.g. ntpd).  It also seems to break lagg for me.

SYNCDHCP should fix the problems with ntpd.  I have no idea about lagg(4), you 
would probably need to ask a more specific question about what exact breakage 
you are seeing.

-- 
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: kernel: warning: attempt to domain_add(bluetooth) after domainfinalize()

2010-01-08 Thread John Baldwin
On Friday 08 January 2010 4:51:19 am martinko wrote:
 Hi,
 
 I've been seeing the following on 7.x and 8.0 during boot:
 
 Jan  8 09:38:49 mb-aw1n-bsd kernel: WARNING: attempt to 
 domain_add(bluetooth) after domainfinalize()
 
 It did not happen on 6.x.  Is it a known issue ?

I believe so.  You can make the warning go away by compiling the bluetooth 
modules into your kernel or loading them via loader.conf.

-- 
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: ssh+pam fails after 6.4 to 7.2 upgrade

2010-01-08 Thread Dag-Erling Smørgrav
Jordi Espasa Clofent jespa...@minibofh.org writes:
 - CONLUSION: As you can see, the sshd suffers a segmentation fault
 after 'sshpam_thread_cleanup entering'

Could you please get a core dump?  You'll have to add 'ulimit -c
unlimited' in the right place in /etc/rc.d/sshd, and probably also set
kern.sugid_coredump to 1.  If gdb shows only gibberish, you'll have to
rebuild world and pam_ldap with DEBUG_FLAGS=-g STRIP=.

DES
-- 
Dag-Erling Smørgrav - d...@des.no
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: kernel: warning: attempt to domain_add(bluetooth) after domainfinalize()

2010-01-08 Thread Masoom Shaikh
On Friday January 8 2010 13:43:21 John Baldwin wrote:
 On Friday 08 January 2010 4:51:19 am martinko wrote:
  Hi,
 
  I've been seeing the following on 7.x and 8.0 during boot:
 
  Jan  8 09:38:49 mb-aw1n-bsd kernel: WARNING: attempt to
  domain_add(bluetooth) after domainfinalize()
 
  It did not happen on 6.x.  Is it a known issue ?
 
 I believe so.  You can make the warning go away by compiling the bluetooth
 modules into your kernel or loading them via loader.conf.
 

I load the bluetooth netgraph node via loader.conf
ng_ubt_load=YES

I receive this warning as well, no idea with previous releases prior to 7.0 
but I have always observed this warning.

slightly off topic
how to compile ng_ubt in kernel, it is not mentioned in man page, never 
bothered to dig, as it not required but kind of nice to have
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: kernel: warning: attempt to domain_add(bluetooth) after domainfinalize()

2010-01-08 Thread martinko

Masoom Shaikh wrote:

On Friday January 8 2010 13:43:21 John Baldwin wrote:

On Friday 08 January 2010 4:51:19 am martinko wrote:

Hi,

I've been seeing the following on 7.x and 8.0 during boot:

Jan  8 09:38:49 mb-aw1n-bsd kernel: WARNING: attempt to
domain_add(bluetooth) after domainfinalize()

It did not happen on 6.x.  Is it a known issue ?


I believe so.  You can make the warning go away by compiling the bluetooth
modules into your kernel or loading them via loader.conf.



I load the bluetooth netgraph node via loader.conf
ng_ubt_load=YES

I receive this warning as well, no idea with previous releases prior to 7.0
but I have always observed this warning.


Indeed, I've done it always this way and I can confirm it worked on 6.x 
but prints warnings on 7.2 and 8.0 (I have at hands at the moment).


$ grep bt /boot/loader.conf.local
ng_ubt_load=YES

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


Re: 8.0 regression: wired network slow to initialise ?

2010-01-08 Thread martinko

John Baldwin wrote:

On Friday 08 January 2010 4:23:09 am martinko wrote:

Hi,

$ grep sk0 /etc/rc.conf.local
ifconfig_sk0=DHCP

When booting up or netif restart:

Starting Network: lo0 sk0.
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST  metric 0 mtu 16384
  options=3RXCSUM,TXCSUM
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
  inet6 ::1 prefixlen 128
  inet 127.0.0.1 netmask 0xff00
sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST  metric 0 mtu 1500
  options=bRXCSUM,TXCSUM,VLAN_MTU
  ether 00:11:22:33:44:55
  media: Ethernet autoselect (none)
  status: no carrier
  ^^

Please note that on older versions of FreeBSD it printed 'status:
active' and also IP address obtained via DHCP.  The same now happens
whether booting up or restarting via /etc/rc.d/netif and is a bit
confusing at best.  Other network services starting on boot seem to be
not affected at least.


SYNCDHCP would probably restore the old behavior but make your boot take
longer.



Thank you.  It's just a few seconds difference for me.  And I've found 
out that one can either use SYNCDHCP or synchronous_dhclient=YES.


Cheers,

Martin

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


Re: kernel: warning: attempt to domain_add(bluetooth) after domainfinalize()

2010-01-08 Thread martinko

martinko wrote:

Masoom Shaikh wrote:

On Friday January 8 2010 13:43:21 John Baldwin wrote:

On Friday 08 January 2010 4:51:19 am martinko wrote:

Hi,

I've been seeing the following on 7.x and 8.0 during boot:

Jan 8 09:38:49 mb-aw1n-bsd kernel: WARNING: attempt to
domain_add(bluetooth) after domainfinalize()

It did not happen on 6.x. Is it a known issue ?


I believe so. You can make the warning go away by compiling the
bluetooth
modules into your kernel or loading them via loader.conf.



I load the bluetooth netgraph node via loader.conf
ng_ubt_load=YES

I receive this warning as well, no idea with previous releases prior
to 7.0
but I have always observed this warning.


Indeed, I've done it always this way and I can confirm it worked on 6.x
but prints warnings on 7.2 and 8.0 (I have at hands at the moment).

$ grep bt /boot/loader.conf.local
ng_ubt_load=YES



Hm..  I've just realized that 4 modules are loaded via loader.conf:
131 0xc10cb000 6778 ng_ubt.ko
144 0xc10d2000 d9f4 netgraph.ko
152 0xc10e df6c ng_hci.ko
163 0xc10ee000 23a0 ng_bluetooth.ko

Yet there's still 1 loaded during boot via rc.conf:
271 0xc3ab9000 21000ng_btsocket.ko

Most likely because of the following:
bthidd_enable=YES

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


Re: ZFS performance degradation over time

2010-01-08 Thread Garrett Moore
No, I haven't isolated the cause to only be uptime related. In my original
email I mentioned that as suggested by someone in the thread, it's probably
not directly related to system uptime, but instead related to usage - the
more usage, the worse the performance.

I've been starting my system with different combinations of applications
running to see what access patterns cause the most slowdown. So far, I don't
have enough data to give anything concrete.

This weekend I'll try some tests such as the one you describe, and see what
happens. I have a strong suspicion that rTorrent is to blame, since I
haven't seen major slowdowns in the last few days with rTorrent not running.
rTorrent preallocates the space needed for the file download (and I'm
downloading large 4GB+ files using it), and then writes to them in an
unpredictable pattern, so maybe ZFS doesn't like being touched this way?



On Wed, Jan 6, 2010 at 2:21 PM, Ivan Voras ivo...@freebsd.org wrote:

 On 3.1.2010 17:42, Garrett Moore wrote:

  I'm having problems with ZFS performance. When my system comes up,
  read/write speeds are excellent (testing with dd if=/dev/zero
  of=/tank/bigfile and dd if=/tank/bigfile of=/dev/null); I get at least
  100MB/s on both reads and writes, and I'm happy with that.
 
  The longer the system is up, the worse my performance gets. Currently my
  system has been up for 4 days, and read/write performance is down to
 about
  10MB/s at best.

 Are you sure you have isolated the cause to be only the uptime of the
 machine? Is there no other change between the runs? E.g. did you stop
 all other services and applications on the machine before doing the test
 for the second time? Can you create a big file (2x memory size) when the
 machine boots, measure the time to read it, then read it again after a
 few days when you notice performance problems?


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

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


Re: kernel: warning: attempt to domain_add(bluetooth) after domainfinalize()

2010-01-08 Thread martinko

martinko wrote:

martinko wrote:

Masoom Shaikh wrote:


I load the bluetooth netgraph node via loader.conf
ng_ubt_load=YES

I receive this warning as well, no idea with previous releases prior
to 7.0
but I have always observed this warning.


Indeed, I've done it always this way and I can confirm it worked on 6.x
but prints warnings on 7.2 and 8.0 (I have at hands at the moment).

$ grep bt /boot/loader.conf.local
ng_ubt_load=YES



Hm.. I've just realized that 4 modules are loaded via loader.conf:
13 1 0xc10cb000 6778 ng_ubt.ko
14 4 0xc10d2000 d9f4 netgraph.ko
15 2 0xc10e df6c ng_hci.ko
16 3 0xc10ee000 23a0 ng_bluetooth.ko

Yet there's still 1 loaded during boot via rc.conf:
27 1 0xc3ab9000 21000 ng_btsocket.ko

Most likely because of the following:
bthidd_enable=YES


Well, either because of bthidd or hcsecd, they're started one after 
another and the warning is displayed close to them.


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


Re: 8.0 regression: wired network slow to initialise ?

2010-01-08 Thread martinko

John Baldwin wrote:

On Friday 08 January 2010 4:23:09 am martinko wrote:

Hi,

$ grep sk0 /etc/rc.conf.local
ifconfig_sk0=DHCP

When booting up or netif restart:

Starting Network: lo0 sk0.
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST  metric 0 mtu 16384
  options=3RXCSUM,TXCSUM
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
  inet6 ::1 prefixlen 128
  inet 127.0.0.1 netmask 0xff00
sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST  metric 0 mtu 1500
  options=bRXCSUM,TXCSUM,VLAN_MTU
  ether 00:11:22:33:44:55
  media: Ethernet autoselect (none)
  status: no carrier
  ^^

Please note that on older versions of FreeBSD it printed 'status:
active' and also IP address obtained via DHCP.  The same now happens
whether booting up or restarting via /etc/rc.d/netif and is a bit
confusing at best.  Other network services starting on boot seem to be
not affected at least.


SYNCDHCP would probably restore the old behavior but make your boot take
longer.



Please note that it displays status: no carrier.  Is this really 
dependent on DHCP ?  Even if I `netif stop` network interface status is 
active until I plug out network cable (only then it's no carrier).


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


Re: 8.0 regression: wireless network slow to initialise ?

2010-01-08 Thread martinko

John Baldwin wrote:

On Friday 08 January 2010 4:38:40 am martinko wrote:

Hi,

$ egrep 'sk0|wlan' /etc/rc.conf.local
ifconfig_sk0=DHCP
wlans_iwi0=wlan0
ifconfig_wlan0=WPA DHCP

When booting up or netif restart:

Starting Network: lo0 sk0.
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST  metric 0 mtu 16384
  options=3RXCSUM,TXCSUM
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
  inet6 ::1 prefixlen 128
  inet 127.0.0.1 netmask 0xff00
sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST  metric 0 mtu 1500
  options=bRXCSUM,TXCSUM,VLAN_MTU
  ether 00:11:22:33:44:55
  media: Ethernet autoselect (none)
  status: no carrier

Please note that iwi/wlan is not even mentioned. (!)
The same happens whether booting up or via /etc/rc.d/netif restart.


Yes, the part of the netif script that prints out interfaces doesn't handle
child interfaces like wlan or vlan devices currently.  I'm not fully sure of
the best way to fix it.


On older versions of FreeBSD iwi0 was turned up and associated.
With 8.0 I am getting errors from services started on boot that try to
reach the network (e.g. ntpd).  It also seems to break lagg for me.


SYNCDHCP should fix the problems with ntpd.  I have no idea about lagg(4), you
would probably need to ask a more specific question about what exact breakage
you are seeing.



Indeed, SYNCDHCP fixed ntpd and others.

Regarding lagg, please see my reply to your hint from week ago:
http://lists.freebsd.org/pipermail/freebsd-mobile/2009-December/011861.html

Even with explicit 'network_interfaces' it did not change/help.  And 
please note that lagg was listed twice when stopping and starting via 
netif script (pls see the link above for details).


With regards,

Martin

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


Question about imaging / migrating freebsd

2010-01-08 Thread kevin
Hello,

 

 

I have a quick question regarding moving freebsd from one server to another.
I have read and am exploring several methods for efficiently migrating one
freebsd server to newer hardware.

 

Without getting into too many details, it is preferable to migrate each
partition/slice in their entirety. I have read methods where utilizing
dump/restore in single user mode seems to be the way to go, however I would
like to know if anyone has any recommendations or has a tried  true method
(dd over ssh?) for accomplishing this kind of a task that may save me any
headaches, since the servers in question are production systems.

 

Both systems will be 7.1-PRERELEASE.  And I am unable to physically mount
the new server's disk in the old server, unfortunately.

 

 

Any help / suggestions is greatly appreciated.

 

 

Thanks,

 

Kevin 

 

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


Re: Question about imaging / migrating freebsd

2010-01-08 Thread Freddie Cash
On Fri, Jan 8, 2010 at 8:54 AM, kevin k...@kevinkevin.com wrote:

 I have a quick question regarding moving freebsd from one server to
 another.
 I have read and am exploring several methods for efficiently migrating one
 freebsd server to newer hardware.

 Without getting into too many details, it is preferable to migrate each
 partition/slice in their entirety. I have read methods where utilizing
 dump/restore in single user mode seems to be the way to go, however I would
 like to know if anyone has any recommendations or has a tried  true method
 (dd over ssh?) for accomplishing this kind of a task that may save me any
 headaches, since the servers in question are production systems.

 Both systems will be 7.1-PRERELEASE.  And I am unable to physically mount
 the new server's disk in the old server, unfortunately.

 Any help / suggestions is greatly appreciated.


In the past, we've used cpio piped through SSH to image servers booted from
a Linux LiveCD.

We've also used DAR (the Disk ARchiver) to do the same.

Recently, we've switched to using Rsync over SSH.  On the FreeBSD side, it's
as simple as:
  - boot from Frenzy LiveCD
  - partition/format disk(s)
  - mount filesystems under /root/mnt/ (or wherever)
  - rsync from other server (be sure to use --numeric-ids, --archive, and
--hard-links)
  - install boot blocks
  - reboot

We also use rsync to backup all our Linux and FreeBSD servers to a single
backup server (ZFS+Snapshots was made for this).  And then use that as the
source for imaging new harddrives.

-- 
Freddie Cash
fjwc...@gmail.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


nginx hanging with state zoneli

2010-01-08 Thread Steven Hartland

The first time in a while be we just had nginx get stuck in the zoneli
state:
51630 www 1 -160 16616K  9396K zoneli 2  24:33  0.00% nginx
51627 www 1 -160 16616K  9376K zoneli 1  24:22  0.00% nginx
51629 www 1 -160 16616K  9372K zoneli 3  24:09  0.00% nginx
51628 www 1 -160 16616K  9104K zoneli 0  24:05  0.00% nginx

Usually I would suspect an mbufs issue but that doesnt seem to have
caused the problem this time, going by the info below, anyone ideas?

Running: 7.0-RELEASE-p11 AMD64

== netstat -m ==
14829/11796/26625 mbufs in use (current/cache/total)
2240/1024/3264/262144 mbuf clusters in use (current/cache/total/max)
1449/727 mbuf+clusters out of packet secondary zone in use (current/cache)
12582/218/12800/12800 4k (page size) jumbo clusters in use 
(current/cache/total/max)
0/0/0/6400 9k jumbo clusters in use (current/cache/total/max)
0/0/0/3200 16k jumbo clusters in use (current/cache/total/max)
58515K/5869K/64384K bytes allocated to network (current/cache/total)
0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters)
0/0/0 requests for jumbo clusters denied (4k/9k/16k)
0/0/0 sfbufs in use (current/peak/max)
0 requests for sfbufs denied
0 requests for sfbufs delayed
3214 requests for I/O initiated by sendfile
0 calls to protocol drain routines


== /etc/sysctl.con ==
# Large amounts of files in directories fix
vfs.ufs.dirhash_maxmem=8379692

# Network performance tunning
net.inet.tcp.inflight.enable=0
net.inet.tcp.sendspace=65536
kern.ipc.maxsockbuf=16777216
net.inet.tcp.sendbuf_max=16777216
net.inet.tcp.recvbuf_max=16777216

# Prevent nginx issues:-
# Increase backlog max
kern.ipc.somaxconn=1024

# Prevent issue with pmap
vm.pmap.shpgperproc=500

# high server numbers tuning see:
# http://rerepi.wordpress.com/2008/04/19/tuning-freebsd-sysoev-rit/
kern.ipc.nmbclusters=262144
kern.ipc.maxsockets=204800
net.inet.tcp.msl=2

== /boot/loader.conf ==
accf_http_load=YES
net.inet.tcp.syncache.hashsize=1024
net.inet.tcp.syncache.bucketlimit=100
net.inet.tcp.tcbhashsize=4096
vm.kmem_size=768M
vm.kmem_size_max=768M
 



This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

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


Re: ZFS performance degradation over time

2010-01-08 Thread Artem Belevich
Keep an eye on ARC size and on active/inactive/cache/free memory lists:

sysctl kstat.zfs.misc.arcstats.size
sysctl vm.stats.vm.v_inactive_count
sysctl vm.stats.vm.v_active_count
sysctl vm.stats.vm.v_cache_count
sysctl vm.stats.vm.v_cache_count

ZFS performance does degrade a lot if ARC becomes too small. Writes
also get throttled if ZFS thinks the system is running low on memory.

One way to help the situation somewhat is to bump vfs.zfs.arc_min
tunable. It would make ZFS somewhal less eager to give up memory.
However, write throttling seems to rely on amount on memory on the
free list. FreeBSD appears to have somewhat different semantics for
'free compared to solaris and that makes ZFS think that we're running
low on memory while there's plenty of it sitting on inactive/cached
lists and could be used.

One rather crude way to get ZFS back in shape in this situation is to
temporarily cause real memory shortage on the system. That would force
trimming of active/inactive lists (and ARC, too) but once it's done,
ARC would be free to grow and that may restore ZFS performance for a
while.

Following command will allocate about 8G of memory on my system --
enough to start swapout:
perl -e '$x=xx30'

--Artem


On Fri, Jan 8, 2010 at 8:31 AM, Garrett Moore garrettmo...@gmail.com wrote:

 No, I haven't isolated the cause to only be uptime related. In my original
 email I mentioned that as suggested by someone in the thread, it's probably
 not directly related to system uptime, but instead related to usage - the
 more usage, the worse the performance.

 I've been starting my system with different combinations of applications
 running to see what access patterns cause the most slowdown. So far, I don't
 have enough data to give anything concrete.

 This weekend I'll try some tests such as the one you describe, and see what
 happens. I have a strong suspicion that rTorrent is to blame, since I
 haven't seen major slowdowns in the last few days with rTorrent not running.
 rTorrent preallocates the space needed for the file download (and I'm
 downloading large 4GB+ files using it), and then writes to them in an
 unpredictable pattern, so maybe ZFS doesn't like being touched this way?



 On Wed, Jan 6, 2010 at 2:21 PM, Ivan Voras ivo...@freebsd.org wrote:

  On 3.1.2010 17:42, Garrett Moore wrote:
 
   I'm having problems with ZFS performance. When my system comes up,
   read/write speeds are excellent (testing with dd if=/dev/zero
   of=/tank/bigfile and dd if=/tank/bigfile of=/dev/null); I get at least
   100MB/s on both reads and writes, and I'm happy with that.
  
   The longer the system is up, the worse my performance gets. Currently my
   system has been up for 4 days, and read/write performance is down to
  about
   10MB/s at best.
 
  Are you sure you have isolated the cause to be only the uptime of the
  machine? Is there no other change between the runs? E.g. did you stop
  all other services and applications on the machine before doing the test
  for the second time? Can you create a big file (2x memory size) when the
  machine boots, measure the time to read it, then read it again after a
  few days when you notice performance problems?
 
 
  ___
  freebsd-stable@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-stable
  To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
 
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: nginx hanging with state zoneli

2010-01-08 Thread Manish Vachharajani
Looks like you are out of jumbo clusters.

On Jan 8, 2010 10:34 AM, Steven Hartland kill...@multiplay.co.uk wrote:

The first time in a while be we just had nginx get stuck in the zoneli
state:
51630 www 1 -160 16616K  9396K zoneli 2  24:33  0.00% nginx
51627 www 1 -160 16616K  9376K zoneli 1  24:22  0.00% nginx
51629 www 1 -160 16616K  9372K zoneli 3  24:09  0.00% nginx
51628 www 1 -160 16616K  9104K zoneli 0  24:05  0.00% nginx

Usually I would suspect an mbufs issue but that doesnt seem to have
caused the problem this time, going by the info below, anyone ideas?

Running: 7.0-RELEASE-p11 AMD64

== netstat -m ==
14829/11796/26625 mbufs in use (current/cache/total)
2240/1024/3264/262144 mbuf clusters in use (current/cache/total/max)
1449/727 mbuf+clusters out of packet secondary zone in use (current/cache)
12582/218/12800/12800 4k (page size) jumbo clusters in use
(current/cache/total/max)
0/0/0/6400 9k jumbo clusters in use (current/cache/total/max)
0/0/0/3200 16k jumbo clusters in use (current/cache/total/max)
58515K/5869K/64384K bytes allocated to network (current/cache/total)
0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters)
0/0/0 requests for jumbo clusters denied (4k/9k/16k)
0/0/0 sfbufs in use (current/peak/max)
0 requests for sfbufs denied
0 requests for sfbufs delayed
3214 requests for I/O initiated by sendfile
0 calls to protocol drain routines


== /etc/sysctl.con ==
# Large amounts of files in directories fix
vfs.ufs.dirhash_maxmem=8379692

# Network performance tunning
net.inet.tcp.inflight.enable=0
net.inet.tcp.sendspace=65536
kern.ipc.maxsockbuf=16777216
net.inet.tcp.sendbuf_max=16777216
net.inet.tcp.recvbuf_max=16777216

# Prevent nginx issues:-
# Increase backlog max
kern.ipc.somaxconn=1024

# Prevent issue with pmap
vm.pmap.shpgperproc=500

# high server numbers tuning see:
# http://rerepi.wordpress.com/2008/04/19/tuning-freebsd-sysoev-rit/
kern.ipc.nmbclusters=262144
kern.ipc.maxsockets=204800
net.inet.tcp.msl=2

== /boot/loader.conf ==
accf_http_load=YES
net.inet.tcp.syncache.hashsize=1024
net.inet.tcp.syncache.bucketlimit=100
net.inet.tcp.tcbhashsize=4096
vm.kmem_size=768M
vm.kmem_size_max=768M


This e.mail is private and confidential between Multiplay (UK) Ltd. and the
person or entity to whom it is addressed. In the event of misdirection, the
recipient is prohibited from using, copying, printing or otherwise
disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

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


Re: 8.0 regression: wired network slow to initialise ?

2010-01-08 Thread Pyun YongHyeon
On Fri, Jan 08, 2010 at 06:00:10PM +0100, martinko wrote:
 John Baldwin wrote:
 On Friday 08 January 2010 4:23:09 am martinko wrote:
 Hi,
 
 $ grep sk0 /etc/rc.conf.local
 ifconfig_sk0=DHCP
 
 When booting up or netif restart:
 
 Starting Network: lo0 sk0.
 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST  metric 0 mtu 16384
   options=3RXCSUM,TXCSUM
   inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
   inet6 ::1 prefixlen 128
   inet 127.0.0.1 netmask 0xff00
 sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST  metric 0 mtu 1500
   options=bRXCSUM,TXCSUM,VLAN_MTU
   ether 00:11:22:33:44:55
   media: Ethernet autoselect (none)
   status: no carrier
   ^^
 
 Please note that on older versions of FreeBSD it printed 'status:
 active' and also IP address obtained via DHCP.  The same now happens
 whether booting up or restarting via /etc/rc.d/netif and is a bit
 confusing at best.  Other network services starting on boot seem to be
 not affected at least.
 
 SYNCDHCP would probably restore the old behavior but make your boot take
 longer.
 
 
 Please note that it displays status: no carrier.  Is this really 
 dependent on DHCP ?  Even if I `netif stop` network interface status is 
 active until I plug out network cable (only then it's no carrier).
 

I think link state handling of sk(4) needs more code.
dhclient(8) wants to see an established link before sending DHCP
request so driver should maintain correct link state to make
dhclient(8) happy. Due to hardware bugs of PHY sk(4) used several
workarounds but that made it harder to keep track of link state
changes.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


ndis(4) on amd64

2010-01-08 Thread Paul B Mahol
Hi,

I'm looking for users of NDISulator on amd64.

Have anyone managed to get working ndis(4) on amd64?

-- 
Paul B Mahol
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: State of igb on FreeBSD 8 stable?

2010-01-08 Thread Jack Vogel
I am incorporating some of Pyun's ideas into my new version, although some
changes I
am unconvinced about... There will always be later :)

Jack


On Thu, Jan 7, 2010 at 12:26 PM, Mike Tancsa m...@sentex.net wrote:

 At 03:19 PM 1/7/2010, Pyun YongHyeon wrote:

 On Thu, Jan 07, 2010 at 09:46:14AM -0800, alan bryan wrote:
  I did some searching last night and found others using igb on Intel
 Cards having high interrupts and other strange issues and some comments to
 the effect that igb is soon going to have a lot of work done to it (I
 believe Jack Vogel is working on it).  So, can someone give an estimation as
 to how soon that may be and how soon it may make it to 8-stable?  If it's
 going to be a while I may look into adding a card using a different driver
 to test.
 
 http://people.freebsd.org/~yongari/igb/igb.buf.patch6http://people.freebsd.org/%7Eyongari/igb/igb.buf.patch6

 The patch would fix unresponsive system under high network load as
 well as reducing number of interrupts. The patch also contains
 bus_dma(9) and watchdog timeout fix.


 FYI, with the above patch, the driver is quite stable for me on a box I use
 in my lab.

---Mike



 
 Mike Tancsa,  tel +1 519 651 3400
 Sentex Communications,m...@sentex.net
 Providing Internet since 1994www.sentex.net
 Cambridge, Ontario Canada www.sentex.net/mike


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

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


Re: ZFS performance degradation over time

2010-01-08 Thread Jonathan Noack
On Fri, January 8, 2010 11:31, Garrett Moore wrote:
 No, I haven't isolated the cause to only be uptime related. In my original
 email I mentioned that as suggested by someone in the thread, it's
 probably
 not directly related to system uptime, but instead related to usage - the
 more usage, the worse the performance.

 I've been starting my system with different combinations of applications
 running to see what access patterns cause the most slowdown. So far, I
 don't
 have enough data to give anything concrete.

 This weekend I'll try some tests such as the one you describe, and see
 what
 happens. I have a strong suspicion that rTorrent is to blame, since I
 haven't seen major slowdowns in the last few days with rTorrent not
 running.
 rTorrent preallocates the space needed for the file download (and I'm
 downloading large 4GB+ files using it), and then writes to them in an
 unpredictable pattern, so maybe ZFS doesn't like being touched this way?

Probably unrelated, but this prefetch issue results in a slowdown:
http://lists.freebsd.org/pipermail/freebsd-fs/2009-December/007481.html

-Jonathan

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


New LOR: allproc/zfs

2010-01-08 Thread Peter Jeremy
Just found a new LOR on 8-STABLE/amd64 from 30-Nov.  It's possible that
it was associated with 'vmstat -m'.  Reported as kern/142489

lock order reversal:
 1st 0x807417c0 allproc (allproc) @ /usr/src/sys/vm/vm_meter.c:130
 2nd 0xff002c263ba8 zfs (zfs) @ /usr/src/sys/kern/vfs_subr.c:2188
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
_witness_debugger() at _witness_debugger+0x2c
witness_checkorder() at witness_checkorder+0x66f
__lockmgr_args() at __lockmgr_args+0x475
vop_stdlock() at vop_stdlock+0x39
VOP_LOCK1_APV() at VOP_LOCK1_APV+0x52
_vn_lock() at _vn_lock+0x47
vrele() at vrele+0xc3
vm_object_deallocate() at vm_object_deallocate+0x1ad
_vm_map_unlock() at _vm_map_unlock+0x70
vm_map_remove() at vm_map_remove+0x6f
vmspace_free() at vmspace_free+0x56
vmtotal() at vmtotal+0x3d5
sysctl_root() at sysctl_root+0xa1
userland_sysctl() at userland_sysctl+0x158
__sysctl() at __sysctl+0xaa
syscall() at syscall+0x1ac
Xfast_syscall() at Xfast_syscall+0xe1
--- syscall (202, FreeBSD ELF64, __sysctl), rip = 0x800bc5a9c, rsp = 
0x7fffdaf8, rbp = 0x7fffdb08 ---

-- 
Peter Jeremy


pgpLY23ALYtRM.pgp
Description: PGP signature


ntpd not removed; WITHOUT_NTP enabled in src.conf

2010-01-08 Thread Henrik Hudson
Hey List,

Among other things I have in my /etc/src.conf
WITHOUT_NTP=yes

which from my understanding should not build ntpd, etc...

However, after doing:
make buildworld
make buildkernel
make installkernel
reboot
mergemaster -p
make installworld
mergemaster
reboot
make delete-old
make delete-old-libs

ntpd still exists in /usr/sbin and the man pages, etc... seem to
still be hanging around. Did I miss something?

It also seems that
WITHOUT_MAILWRAPPER
WITHOUT_SENDMAIL

are also ignored. However, 
WITHOUT_RCMDS
WITHOUT_LPR
seems to work as rlogin, etc... are not to be found and neither is
lpr.

Thanks.

Henrik
-- 
Henrik Hudson
li...@rhavenn.net
-
God, root, what is difference? Pitr; UF 

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


USB problems on 8.0-STABLE

2010-01-08 Thread Frank
I am having problems with mouse, keyboard and APC UPS.  When attempting to 
start apcupsd I get the following error:


Jan  8 17:42:06 Ace apcupsd[1606]: apcupsd FATAL ERROR in generic-usb.c at 
line 636 Cannot find UPS device -- For a link to detailed USB trouble 
shooting information, please see http://www.apcupsd.com/support.html.

Jan  8 17:42:06 Ace apcupsd[1606]: apcupsd error shutdown completed

In X, I must move the mouse to get anything to update.  For example, if I 
type in an xterm nothing will display or happen until the mouse is moved. 
This also happens using a browser or any other app.


# dmesg | grep usb 
usbus0: OHCI (generic) USB controller on ohci0 usbus1: EHCI version 1.0

usbus1: EHCI (generic) USB 2.0 controller on ehci0
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 480Mbps High Speed USB v2.0
ugen0.1: nVidia at usbus0
uhub0: nVidia OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on 
usbus0

ugen1.1: nVidia at usbus1
uhub1: nVidia EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on 
usbus1

Root mount waiting for: usbus1
Root mount waiting for: usbus1
Root mount waiting for: usbus1
Root mount waiting for: usbus1
ugen0.2: American Power Conversion at usbus0
ugen0.3: vendor 0x0461 at usbus0
ums0: vendor 0x0461 USB Optical Mouse, class 0/0, rev 2.00/2.00, 
addr 3 on usbus0

ugen0.4: Dell at usbus0
ukbd0: Dell Dell USB Keyboard, class 0/0, rev 1.10/3.01, addr 4 on 
usbus0


Ace /usr/ports # usbdevs -d -v
usbdevs: no USB controllers found

Ace /usr/ports # usbconfig
ugen0.1: OHCI root HUB nVidia at usbus0, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON
ugen1.1: EHCI root HUB nVidia at usbus1, cfg=0 md=HOST spd=HIGH 
(480Mbps) pwr=ON
ugen0.2: Back-UPS XS 1200 FW:8.g1 .D USB FW:g1 American Power 
Conversion at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON
ugen0.3: USB Optical Mouse vendor 0x0461 at usbus0, cfg=0 md=HOST 
spd=LOW (1.5Mbps) pwr=ON
ugen0.4: Dell USB Keyboard Dell at usbus0, cfg=0 md=HOST spd=LOW 
(1.5Mbps) pwr=ON


World and kernel built last night.

--
Frank
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: ZFS performance degradation over time

2010-01-08 Thread Jeremy Chadwick
On Fri, Jan 08, 2010 at 04:23:03PM -0500, Jonathan Noack wrote:
 On Fri, January 8, 2010 11:31, Garrett Moore wrote:
  No, I haven't isolated the cause to only be uptime related. In my original
  email I mentioned that as suggested by someone in the thread, it's
  probably
  not directly related to system uptime, but instead related to usage - the
  more usage, the worse the performance.
 
  I've been starting my system with different combinations of applications
  running to see what access patterns cause the most slowdown. So far, I
  don't
  have enough data to give anything concrete.
 
  This weekend I'll try some tests such as the one you describe, and see
  what
  happens. I have a strong suspicion that rTorrent is to blame, since I
  haven't seen major slowdowns in the last few days with rTorrent not
  running.
  rTorrent preallocates the space needed for the file download (and I'm
  downloading large 4GB+ files using it), and then writes to them in an
  unpredictable pattern, so maybe ZFS doesn't like being touched this way?
 
 Probably unrelated, but this prefetch issue results in a slowdown:
 http://lists.freebsd.org/pipermail/freebsd-fs/2009-December/007481.html

With the introduction of 8.0-RC1, FreeBSD explicitly disables prefetch
if your system has less than 4GB usable[1] memory.  The code does print
a warning/FYI message when this condition is met[2].

You can disable the warning message by setting prefetch_disable=1 in
loader.conf (and this naturally means prefetch is disabled).  You can
also explicitly enable prefetch by setting the value to 1, and this
trumps the how-much-usable-RAM check.

The OP doesn't disclose if he's enabled prefetch, so I assume he hasn't,
which means he shouldn't be susceptible to the bug described above.

All that said -- I know what the OP is referring to, as I've seen it
myself (on RELENG_7, and possibly early releases of 8.0).  The only
way to relieve the pain, AFAIK, is to reboot.

I do see some MFC's done about 13 hours ago to RELENG_7 and RELENG_8
that talk about the ARC and paging pressure, which to me means
decreased performance when it occurs... or maybe it helps with the kmem
exhaustion problem?  The brief description in the commit is simply not
enough to suffice; it's almost like we need a FreeBSD ZFS Newsletter
that documents what all the changes are that get committed, what they
fix, and what's being worked on/tested in HEAD (for potential MFC).

It would also be good to get some concise documentation with regards to
what all the kstat.zfs.misc.arcstats.* counters mean and represent;
admins like myself would love to track/graph these for helping correlate
performance or stability issues, but we don't even know what they
represent.  For example, just earlier this week I read a semi-recent
message talking about how a large kstat.zfs.misc.arcstats.evict_skip
counter indicates something bad, yet I have no idea what evict skip
means in reference to the ZFS core/model itself.


[1]: Because of #2 (see above/below), I had to analyse the code.  My
system was amd64 + 4GB RAM yet ZFS was telling me the system did not
have 4GB of RAM thus had disabled prefetch.  My analysis is near the
bottom of my blog post:

http://koitsu.wordpress.com/2009/10/12/testing-out-freebsd-8-0-rc1/

[2]: The grammar of the message printed has gone through numerous
revisions (I forget the exact number, but *at least* 2), and the most
recent one is still too ambiguous, resulting in reader confusion.  In my
above blog post, I propose what the kernel message should read (in my
opinion), which is significantly less ambiguous and hopefully won't
cause but I do have 4GB! confusion.

[3]: src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c

http://freshbsd.org/2010/01/08/09/59/13 -- RELENG_8
http://freshbsd.org/2010/01/08/11/06/13 -- RELENG_7

It sure would be useful if these source files had $FreeBSD$ ID tags in
them, rather than having to grep /var/db/sup.  I swore there was some
command which did this, but I might be thinking of object files.

-- 
| Jeremy Chadwick   j...@parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: ZFS performance degradation over time

2010-01-08 Thread Jeremy Chadwick
On Fri, Jan 08, 2010 at 03:05:06PM -0800, Jeremy Chadwick wrote:
 ... You can also explicitly enable prefetch by setting the
 value to 1, and this trumps the how-much-usable-RAM check.

This should have read 'setting the value to 0'; sorry.

-- 
| Jeremy Chadwick   j...@parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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


Re: ntpd not removed; WITHOUT_NTP enabled in src.conf

2010-01-08 Thread Roland Smith
On Fri, Jan 08, 2010 at 01:38:49PM -0900, Henrik Hudson wrote:
 Hey List,
 
 Among other things I have in my /etc/src.conf
 WITHOUT_NTP=yes
 
 which from my understanding should not build ntpd, etc...
 
 However, after doing:
 make buildworld
...
 make installworld
...
 ntpd still exists in /usr/sbin and the man pages, etc... seem to
 still be hanging around. Did I miss something?

Adding options to `/etc/src.conf` does not remove old binaries, libraries or
manpages! It just prevents the system from building newer ones.  The best way
to deal with this is to use find(1) to locate binaries and libraries that are
older than the most recent installworld. It might be a good idea to make a
backup first, in case you screw up the system! Now, supposing the latest
installworld (with the new options in `/etc/src.conf`) was December
3rd. Running the following command will reveal all older files;

find /bin -type f -and -not -newermt 'Dec 3' -ls

After checking that you've *really* only found old binaries, replace `-ls`
with `-delete` to remove them. Next, repeat this for the directories `/sbin`,
`/usr/bin`, `/usr/sbin`, `/lib`, `/libexec`, `/usr/lib`, `/usr/libexec`,
`/usr/share/man/man*` and `/rescue`.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgp4kfGyvUA6X.pgp
Description: PGP signature


Re: ntpd not removed; WITHOUT_NTP enabled in src.conf

2010-01-08 Thread Kenyon Ralph
On 2010-01-08T13:38:49-0900, Henrik Hudson li...@rhavenn.net wrote:
 Among other things I have in my /etc/src.conf
 WITHOUT_NTP=yes
 
 which from my understanding should not build ntpd, etc...
[...]
 ntpd still exists in /usr/sbin and the man pages, etc... seem to
 still be hanging around. Did I miss something?

There were discussions about this recently. What you are seeing is how
it works -- WITHOUT doesn't delete old stuff, just doesn't build it next
time.

See threads some options in src.conf has no effect (RELENG_8) and
RELENG_8 buildworld broken? starting here:
http://lists.freebsd.org/pipermail/freebsd-stable/2009-December/thread.html#53291

-- 
Kenyon Ralph


signature.asc
Description: Digital signature


Re: USB problems on 8.0-STABLE

2010-01-08 Thread Steven Friedrich
On Friday 08 January 2010 05:47:55 pm Frank wrote:
 I am having problems with mouse, keyboard and APC UPS.  When attempting to
 start apcupsd I get the following error:
 
 Jan  8 17:42:06 Ace apcupsd[1606]: apcupsd FATAL ERROR in generic-usb.c at
 line 636 Cannot find UPS device -- For a link to detailed USB trouble
 shooting information, please see http://www.apcupsd.com/support.html.
 Jan  8 17:42:06 Ace apcupsd[1606]: apcupsd error shutdown completed
 
 In X, I must move the mouse to get anything to update.  For example, if I
 type in an xterm nothing will display or happen until the mouse is moved.
 This also happens using a browser or any other app.
 
 # dmesg | grep usb
 usbus0: OHCI (generic) USB controller on ohci0 usbus1: EHCI version 1.0
 usbus1: EHCI (generic) USB 2.0 controller on ehci0
 usbus0: 12Mbps Full Speed USB v1.0
 usbus1: 480Mbps High Speed USB v2.0
 ugen0.1: nVidia at usbus0
 uhub0: nVidia OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on
 usbus0
 ugen1.1: nVidia at usbus1
 uhub1: nVidia EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on
 usbus1
 Root mount waiting for: usbus1
 Root mount waiting for: usbus1
 Root mount waiting for: usbus1
 Root mount waiting for: usbus1
 ugen0.2: American Power Conversion at usbus0
 ugen0.3: vendor 0x0461 at usbus0
 ums0: vendor 0x0461 USB Optical Mouse, class 0/0, rev 2.00/2.00,
 addr 3 on usbus0
 ugen0.4: Dell at usbus0
 ukbd0: Dell Dell USB Keyboard, class 0/0, rev 1.10/3.01, addr 4 on
 usbus0
 
 Ace /usr/ports # usbdevs -d -v
 usbdevs: no USB controllers found
 
 Ace /usr/ports # usbconfig
 ugen0.1: OHCI root HUB nVidia at usbus0, cfg=0 md=HOST spd=FULL
 (12Mbps) pwr=ON
 ugen1.1: EHCI root HUB nVidia at usbus1, cfg=0 md=HOST spd=HIGH
 (480Mbps) pwr=ON
 ugen0.2: Back-UPS XS 1200 FW:8.g1 .D USB FW:g1 American Power
 Conversion at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON
 ugen0.3: USB Optical Mouse vendor 0x0461 at usbus0, cfg=0 md=HOST
 spd=LOW (1.5Mbps) pwr=ON
 ugen0.4: Dell USB Keyboard Dell at usbus0, cfg=0 md=HOST spd=LOW
 (1.5Mbps) pwr=ON
 
 World and kernel built last night.
 
 --
 Frank
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
 
Check your /etc/X11/xorg.conf

Make sure Option AllowEmptyInput is not on, 1, true, etc.  We needed this 
option as a temporary work-around when a bug existed during the code freeze 
during the FreeBSD8.0 release process. So if you install FreeBSD 8.0-RELEASE 
from any media, to get Xorg to see your mouse, you'll have to add this 
option to the ServerOptions section of xorg.conf.
If you then update your ports, you'll get a newer Xorg than was frozen for the 
8.0 RELEASE, and you'll have to remove the option.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: USB problems on 8.0-STABLE

2010-01-08 Thread Frank

On Fri, 8 Jan 2010, Steven Friedrich wrote:




Check your /etc/X11/xorg.conf

Make sure Option AllowEmptyInput is not on, 1, true, etc.  We needed this
option as a temporary work-around when a bug existed during the code freeze
during the FreeBSD8.0 release process. So if you install FreeBSD 8.0-RELEASE
from any media, to get Xorg to see your mouse, you'll have to add this
option to the ServerOptions section of xorg.conf.
If you then update your ports, you'll get a newer Xorg than was frozen for the
8.0 RELEASE, and you'll have to remove the option.


This is what I have in /etc/X11/xorg.conf:

Section ServerLayout
Identifier X.org Configured
Screen Screen0
InputDeviceMouse0 CorePointer
InputDeviceKeyboard0 CoreKeyboard
Option  AutoAddDevices on
Option  AutoEnableDevices on
Option  AllowEmptyInput off
EndSection

--
Frank
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: USB problems on 8.0-STABLE

2010-01-08 Thread Steven Friedrich
On Friday 08 January 2010 07:25:04 pm Frank wrote:
 On Fri, 8 Jan 2010, Steven Friedrich wrote:
  Check your /etc/X11/xorg.conf
 
  Make sure Option AllowEmptyInput is not on, 1, true, etc.  We needed
  this option as a temporary work-around when a bug existed during the code
  freeze during the FreeBSD8.0 release process. So if you install FreeBSD
  8.0-RELEASE from any media, to get Xorg to see your mouse, you'll have
  to add this option to the ServerOptions section of xorg.conf.
  If you then update your ports, you'll get a newer Xorg than was frozen
  for the 8.0 RELEASE, and you'll have to remove the option.
 
 This is what I have in /etc/X11/xorg.conf:
 
 Section ServerLayout
  Identifier X.org Configured
  Screen Screen0
  InputDeviceMouse0 CorePointer
  InputDeviceKeyboard0 CoreKeyboard
  Option  AutoAddDevices on
  Option  AutoEnableDevices on
  Option  AllowEmptyInput off
 EndSection
 
 --
 Frank
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
 
Comment out the line containing AllowEmptyInput.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: ZFS performance degradation over time

2010-01-08 Thread Andrew Snow

Ivan Voras wrote:
It is true that ZFS in theory doesn't do very well with random writes of 
any kind - the kind that torrent clients do should actually be the worst 
case for ZFS, *but*, this very much depends on the actual workload.



ZFS has aggressive read-ahead for sequential read-aheads, so its worth 
noting that the performance problem can be mitigated by having lots of 
RAM free for read-ahead, as well as multiple vdevs in the zpool (so that 
it can be seeking all disks at once)



- Andrew
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: USB problems on 8.0-STABLE

2010-01-08 Thread Frank

On Fri, 8 Jan 2010, Steven Friedrich wrote:


 Option  AllowEmptyInput off
EndSection



Comment out the line containing AllowEmptyInput.


OK, this took care of the nothing-works-unless-mouse-is-moved problem but 
why do I get this?  It's keeping apcupsd from starting.


Ace /usr/ports # usbdevs -d -v
usbdevs: no USB controllers found

Ace /usr/ports # usbconfig
ugen0.1: OHCI root HUB nVidia at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) 
pwr=ON

ugen1.1: EHCI root HUB nVidia at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) 
pwr=ON
ugen0.2: Back-UPS XS 1200 FW:8.g1 .D USB FW:g1 American Power Conversion 
at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON
ugen0.3: USB Optical Mouse vendor 0x0461 at usbus0, cfg=0 md=HOST 
spd=LOW (1.5Mbps) pwr=ON

ugen0.4: Dell USB Keyboard Dell at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) 
pwr=ON


From dmesg:


usbus0: OHCI (generic) USB controller on ohci0
usbus1: EHCI version 1.0
usbus1: EHCI (generic) USB 2.0 controller on ehci0
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 480Mbps High Speed USB v2.0
ugen0.1: nVidia at usbus0
uhub0: nVidia OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0
ugen1.1: nVidia at usbus1
uhub1: nVidia EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on usbus1
Root mount waiting for: usbus1
Root mount waiting for: usbus1
ugen0.2: American Power Conversion at usbus0
ugen0.3: vendor 0x0461 at usbus0
ums0: vendor 0x0461 USB Optical Mouse, class 0/0, rev 2.00/2.00, addr 3 on 
usbus0
ugen0.4: Dell at usbus0
ukbd0: Dell Dell USB Keyboard, class 0/0, rev 1.10/3.01, addr 4 on usbus0

I don't understand why usbdevs can't find any controllers and apcupsd 
can't find any device while the kernel and usbconfig can find it all.


Thanks.
--
Frank
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: USB problems on 8.0-STABLE

2010-01-08 Thread Steven Friedrich
On Friday 08 January 2010 08:47:54 pm Frank wrote:
 On Fri, 8 Jan 2010, Steven Friedrich wrote:
   Option  AllowEmptyInput off
  EndSection
 
  Comment out the line containing AllowEmptyInput.
 
 OK, this took care of the nothing-works-unless-mouse-is-moved problem but
 why do I get this?  It's keeping apcupsd from starting.
 
 Ace /usr/ports # usbdevs -d -v
 usbdevs: no USB controllers found
 
 Ace /usr/ports # usbconfig
 ugen0.1: OHCI root HUB nVidia at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
 pwr=ON
 ugen1.1: EHCI root HUB nVidia at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps)
  pwr=ON ugen0.2: Back-UPS XS 1200 FW:8.g1 .D USB FW:g1 American Power
  Conversion at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON
 ugen0.3: USB Optical Mouse vendor 0x0461 at usbus0, cfg=0 md=HOST
 spd=LOW (1.5Mbps) pwr=ON
 ugen0.4: Dell USB Keyboard Dell at usbus0, cfg=0 md=HOST spd=LOW
  (1.5Mbps) pwr=ON
 
 From dmesg:
 
 usbus0: OHCI (generic) USB controller on ohci0
 usbus1: EHCI version 1.0
 usbus1: EHCI (generic) USB 2.0 controller on ehci0
 usbus0: 12Mbps Full Speed USB v1.0
 usbus1: 480Mbps High Speed USB v2.0
 ugen0.1: nVidia at usbus0
 uhub0: nVidia OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0
 ugen1.1: nVidia at usbus1
 uhub1: nVidia EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on usbus1
 Root mount waiting for: usbus1
 Root mount waiting for: usbus1
 ugen0.2: American Power Conversion at usbus0
 ugen0.3: vendor 0x0461 at usbus0
 ums0: vendor 0x0461 USB Optical Mouse, class 0/0, rev 2.00/2.00, addr 3
  on usbus0 ugen0.4: Dell at usbus0
 ukbd0: Dell Dell USB Keyboard, class 0/0, rev 1.10/3.01, addr 4 on usbus0
 
 I don't understand why usbdevs can't find any controllers and apcupsd
 can't find any device while the kernel and usbconfig can find it all.
 
 Thanks.
 --
 Frank
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
 
OK, first a disclaimer.  I am not a FreeBSD developer, but I have been 
admin'ing my own *nix systems for decades.

I think this is weird: ugen0.2: American Power Conversion at usbus0
What device or port was this on previous to 8-Stable?

Is it connected via serial cable (rs232) or USB?  I'm betting USB and I'm 
thinking that maybe the driver you used to use hasn't been converted to the 
new USB system in 8-Stable.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: USB problems on 8.0-STABLE

2010-01-08 Thread Warren Block

On Fri, 8 Jan 2010, Frank wrote:


On Fri, 8 Jan 2010, Steven Friedrich wrote:


 Option  AllowEmptyInput off
EndSection



Comment out the line containing AllowEmptyInput.


OK, this took care of the nothing-works-unless-mouse-is-moved problem but why 
do I get this?  It's keeping apcupsd from starting.


Ace /usr/ports # usbdevs -d -v
usbdevs: no USB controllers found


I'd guess that usbdevs is obsolete, part of the old USB system.


Ace /usr/ports # usbconfig
ugen0.1: OHCI root HUB nVidia at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) 
pwr=ON
ugen1.1: EHCI root HUB nVidia at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) 
pwr=ON
ugen0.2: Back-UPS XS 1200 FW:8.g1 .D USB FW:g1 American Power Conversion at 
usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON
ugen0.3: USB Optical Mouse vendor 0x0461 at usbus0, cfg=0 md=HOST spd=LOW 
(1.5Mbps) pwr=ON
ugen0.4: Dell USB Keyboard Dell at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) 
pwr=ON


Do you have DEVICE /dev/ugen0.2 in apcupsd.conf?

I don't understand why usbdevs can't find any controllers and apcupsd can't 
find any device while the kernel and usbconfig can find it all.


upsdevs: probably obsolete.  As for apcupsd, I don't think it can 
auto-scan for USB devices, but haven't used it with USB.


-Warren Block * Rapid City, South Dakota USA
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


apache hanging on 8.0 AMD64

2010-01-08 Thread Rainer Duffner
Hi,

we have an interesting problem with FreeBSD 8.0 AMD64:

The server is a HP DL380G5 with two Harpertown-class CPUs and 8 GB RAM.
It is running MySQL, Apache (worker MPM) and PHP as CGI with Fast-CGI
and SUEXEC.
It has over 500 ZFS filesystems that  comprise various customers
websites, each running PHP as their own user.

Soon after we put this system into production, we saw httpd-processes
being stalled in the ucond state, leading to a total stand-still of
the apache-server (apache blocked itself somehow).
I disabled ZFS prefetching and the problem went away for a couple of
days - until yesterday, when it happened again.
Swap was unused when it happened the last time.
I switched top into thread-mode (M) and saw that the processes
actually seemed to be in different state (zio-i, arc_mr, tx_tx, RUN).
I cannot get any info from kstat, because when the problem happens and I
attach to one of the processes, I don't get anything back - it just sits
there.

If there anything I can take a look at to further debug this problem?
At the time of the hang, no swap was used:

last pid:  6450;  load averages: 36.32, 30.17,
17.75   
 
up 4+11:15:44  20:11:01
482 processes: 28 running, 452 sleeping, 1 zombie, 1 lock
CPU: % user, % nice, % system, % interrupt, % idle
Mem: 1619M Active, 3829M Inact, 2066M Wired, 211M Cache, 827M Buf, 188M Free
Swap: 8192M Total, 8192M Free

  PID USERNAME  PRI NICE   SIZERES STATE   C   TIME   WCPU COMMAND
 6011 user1  440 24960K  3432K RUN 1   2:50  7.08% pure-ftpd
 6038 user2  660   161M 18856K RUN 3   1:26  3.47% php-cgi
  716 root   460 32452K 13776K select  5 104:53  3.08% snmpd
 6021 user3  630   163M 20232K RUN 7   1:28  2.49% php-cgi
 6009 www440   103M 26952K tx-tx  3   0:55  1.76% {httpd}
 6030 www440   101M 26168K CPU47   0:57  1.66% {httpd}
 6028 www440   101M 26476K tx-tx  2   0:55  1.66% {httpd}
 6030 www440   101M 26168K zio-i  5   0:55  1.66% {httpd}
 6008 www440   102M 26640K RUN 2   1:23  1.56% {httpd}
 6009 www460   103M 26952K tx-tx  3   1:22  1.56% {httpd}
 6016 www440   102M 26636K tx-tx  2   1:17  1.56% {httpd}
 6024 www440   106M 26568K RUN 1   1:07  1.56% {httpd}
 5978 www440   102M 26960K RUN 0   1:00  1.56% {httpd}
 6008 www440   102M 26640K zio-i  7   0:55  1.56% {httpd}
 5970 www440   108M 27700K arc_mr  4   0:59  1.46% {httpd}
 6024 www440   106M 26568K tx-tx  5   0:50  1.46% {httpd}
 5979 www450   102M 26904K zio-i  1   1:14  1.37% {httpd}
 6009 www470   103M 26952K zio-i  7   1:11  1.37% {httpd}


I disabled all the apache-modules we don't need.

This is the only system of its kind we have, currently, but we would
really like to get this fixed so we can move more of our
hosting-customers to similar setup servers.

Another detail: due to the fact that every user has a access- and
error-logfile, we had to bump FD_SETSIZE to 16384U.
We tried bumping kern.maxvnodes to larger and larger values (now at
40, 200k are used), but it didn't really help that much. Disabling
prefetching helped a lot (only one crash in 5 days) - but we would like
to know why it actually happens and then fix it forever ;-)




Best Regards,
Rainer
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: mounting ext3 for rw

2010-01-08 Thread Zoran Kolic
Late reply. Bussy week.
After more reading, I changed my mind and
decided to go with e2fsprogs to manage ext3
formatted usb hard drive. I still have no
sheevaplug and no hdd, but I like to prepare
everything and be ready for every surprise.
I always recompile kernel and have no ext2fs
in it. I should probably kldload ext2fs.ko
first to have support. But, I still do not
see the way to manage ext3 in a different way,
since in the list of apps of e2fsprogs does
not exist one to have it. What to do otherwise:
mount -t ext2fs /dev/da0s1 /storage
Or, did I misunderstand the way it works?
Maybe I should not load the module and use
something I'm still not aware of?
Best regards

Zoran

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