From owner-freebsd-stable@FreeBSD.ORG Sun Nov 9 08:20:54 2008 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62D48106564A for ; Sun, 9 Nov 2008 08:20:54 +0000 (UTC) (envelope-from lehmann@ans-netz.de) Received: from avocado.salatschuessel.net (avocado.salatschuessel.net [78.111.72.186]) by mx1.freebsd.org (Postfix) with SMTP id CB1BA8FC16 for ; Sun, 9 Nov 2008 08:20:53 +0000 (UTC) (envelope-from lehmann@ans-netz.de) Received: (qmail 93417 invoked by uid 89); 9 Nov 2008 08:20:51 -0000 Received: from unknown (HELO kartoffel.salatschuessel.net) (78.111.72.187) by avocado.salatschuessel.net with SMTP; 9 Nov 2008 08:20:51 -0000 Date: Sun, 9 Nov 2008 09:20:51 +0100 From: Oliver Lehmann To: stable@FreeBSD.org Message-Id: <20081109092051.99e8d97c.lehmann@ans-netz.de> X-Mailer: Sylpheed 2.5.0 (GTK+ 2.12.11; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: libzfs: vmem.h missing X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Nov 2008 08:20:54 -0000 Hi, when I try to compile an actual 7 STABLE Im getting: ===> cddl/lib/libzfs (depend) rm -f .depend mkdep -f .depend -a -DZFS_NO_ACL -I/usr/src/cddl/lib/libzfs/../../../sbin/mount -I/usr/src/cddl/lib/libzfs/../../../cddl/lib/libumem -I/usr/src/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris -I/usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/include -I/usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/lib/libumem -I/usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzpool/common -I/usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/common/zfs -I/usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs -I/usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/uts/common/sys -I/usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/head -I/usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/uts/common -I/usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libnvpair -I/usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libuutil/common -I/usr/src/cddl/lib/libzfs/../.. /../cddl/contrib/opensolaris/lib/libzfs/common -D_SOLARIS_C_SOURCE /usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/misc/deviceid.c /usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/misc/mnttab.c /usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/misc/mkdirp.c /usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/misc/zmount.c /usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/misc/fsshare.c /usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/misc/zone.c /usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/common/zfs/zfs_namecheck.c /usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/common/zfs/zfs_prop.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_util.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_graph.c /usr/src/cddl/lib/libzfs/../../../cdd l/contrib/opensolaris/lib/libzfs/common/libzfs_mount.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_pool.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_changelist.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_config.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_import.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_status.c In file included from /usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zio.h:32, from /usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/common/zfs/zfs_prop.c:50: /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzpool/common/sys/zfs_context.h:64:18: error: vmem.h: No such file or directory In file included from /usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/spa.h:32, from /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c:44: /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzpool/common/sys/zfs_context.h:64:18: error: vmem.h: No such file or directory ..... why is vmem.h missing? -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ From owner-freebsd-stable@FreeBSD.ORG Sun Nov 9 11:00:33 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A3841065670 for ; Sun, 9 Nov 2008 11:00:33 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (gate6.infracaninophile.co.uk [IPv6:2001:8b0:151:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id AC5128FC08 for ; Sun, 9 Nov 2008 11:00:32 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from happy-idiot-talk.infracaninophile.co.uk (localhost [IPv6:::1]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.3/8.14.3) with ESMTP id mA9B0Gmk007793; Sun, 9 Nov 2008 11:00:26 GMT (envelope-from m.seaman@infracaninophile.co.uk) X-DKIM: Sendmail DKIM Filter v2.7.2 smtp.infracaninophile.co.uk mA9B0Gmk007793 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=infracaninophile.co.uk; s=200708; t=1226228427; bh=rvyiVh4+hNyvQe qEY8MhJDKEgAh1WqDbjiiiixxjYFQ=; h=Message-ID:Date:From:MIME-Version: To:CC:Subject:References:In-Reply-To:Content-Type:Cc:Content-Type: Date:From:In-Reply-To:Message-ID:Mime-Version:References:To; z=Mes sage-ID:=20<4916C2B8.6080702@infracaninophile.co.uk>|Date:=20Sun,=2 009=20Nov=202008=2011:00:08=20+0000|From:=20Matthew=20Seaman=20|Organization:=20Infracaninophile|User -Agent:=20Thunderbird=202.0.0.17=20(X11/20080929)|MIME-Version:=201 .0|To:=20mdh_lists@yahoo.com|CC:=20freebsd-stable@freebsd.org|Subje ct:=20Re:=20host(1)=20problem=20with=20-6=20option|References:=20<9 4894.60594.qm@web56805.mail.re3.yahoo.com>|In-Reply-To:=20<94894.60 594.qm@web56805.mail.re3.yahoo.com>|X-Enigmail-Version:=200.95.6|Co ntent-Type:=20multipart/signed=3B=20micalg=3Dpgp-sha256=3B=0D=0A=20 protocol=3D"application/pgp-signature"=3B=0D=0A=20boundary=3D"----- -------enig652B9874FDC5FDBAB40BEB7D"; b=F1tz4urRz8fDcvqYQInwfFkVSG4 PnQwuLqsE0QtL98M3OlvZmiCKYTb5kyHherhX9N48gLHqF2VuLlirTW30T6HGVG9cj6 Nu3k+nvwam8atD6atYcVJR+W4ezO/iLPUnOjCqYEo831Hdg/LbiQEhn8Qd+fvYsU7/S z3UNe4Z1eU= Message-ID: <4916C2B8.6080702@infracaninophile.co.uk> Date: Sun, 09 Nov 2008 11:00:08 +0000 From: Matthew Seaman Organization: Infracaninophile User-Agent: Thunderbird 2.0.0.17 (X11/20080929) MIME-Version: 1.0 To: mdh_lists@yahoo.com References: <94894.60594.qm@web56805.mail.re3.yahoo.com> In-Reply-To: <94894.60594.qm@web56805.mail.re3.yahoo.com> X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig652B9874FDC5FDBAB40BEB7D" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (smtp.infracaninophile.co.uk [IPv6:::1]); Sun, 09 Nov 2008 11:00:27 +0000 (GMT) X-Virus-Scanned: ClamAV version 0.94.1, clamav-milter version 0.94.1 on happy-idiot-talk.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VERIFIED,NO_RELAYS autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on happy-idiot-talk.infracaninophile.co.uk Cc: freebsd-stable@freebsd.org Subject: Re: host(1) problem with -6 option X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Nov 2008 11:00:33 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig652B9874FDC5FDBAB40BEB7D Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable mdh wrote: > Howdy folks, > I'm having a little trouble understanding a problem that the `host` > command in RELENG_7_0 (very recent) is having. This is by and large > my first time working with IPv6, which I've been meaning to learn for > some time. First off, I've got my zone file configured to return a > AAAA record for x1.mydomain and named isn't complaining. However, > when I run `host -6 x1.mydomain`, host returns the following output: > > (root@rapier) [/etc/namedb]: host -6 x1.mydomain > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179= : internal_send: ::ffff:127.0.0.1#53: Invalid argument > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179= : internal_send: ::ffff:IP.IP.IP.8#53: Invalid argument > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179= : internal_send: ::ffff:127.0.0.1#53: Invalid argument > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179= : internal_send: ::ffff:IP.IP.IP.8#53: Invalid argument > ;; connection timed out; no servers could be reached It's the way resolv.conf works. Consider this -- happy-idiot-talk:~:% cat /etc/resolv.conf=20 domain infracaninophile.co.uk nameserver ::1 nameserver 127.0.0.1 Which is all fine and dandy when told to use IPv6: happy-idiot-talk:~:% host -6 h-i-t.infracaninophile.co.uk h-i-t.infracaninophile.co.uk is an alias for happy-idiot-talk.infracanino= phile.co.uk. happy-idiot-talk.infracaninophile.co.uk has address 81.187.76.162 happy-idiot-talk.infracaninophile.co.uk has IPv6 address 2001:8b0:151:1:2= 40:5ff:fea5:8db7 happy-idiot-talk.infracaninophile.co.uk mail is handled by 10 smtp.infrac= aninophile.co.uk. but goes tits-up when told to use IPv4: happy-idiot-talk:~:% host -4 h-i-t.infracaninophile.co.uk host: couldn't get address for '::1': address family not supported nameserver entries in resolv.conf are tried in the order given. Using the -4 or -6 switches to host(1) forces it to try each of the listed nameserver addresses by the stated protocol. It makes no sense at all=20 to try and access an IPv6 address using IPv4 transport, and trying the=20 converse: an IPv4 address via IPv6, will either fail or try and use=20 IPv4-mapped addresses. You might think that the '-4' and '-6' flags to host(1) are pretty much useless in that case, but they work fine=20 when you also tell host(1) the domain name of a nameserver to use[*]: happy-idiot-talk:~:% host -4 h-i-t.infracaninophile.co.uk localhost=20 Using domain server: Name: localhost Address: 127.0.0.1#53 Aliases:=20 h-i-t.infracaninophile.co.uk is an alias for happy-idiot-talk.infracanino= phile.co.uk. happy-idiot-talk.infracaninophile.co.uk has address 81.187.76.162 happy-idiot-talk.infracaninophile.co.uk has IPv6 address 2001:8b0:151:1:2= 40:5ff:fea5:8db7 happy-idiot-talk.infracaninophile.co.uk mail is handled by 10 smtp.infrac= aninophile.co.uk. happy-idiot-talk:~:% host -6 h-i-t.infracaninophile.co.uk localhost Using domain server: Name: localhost Address: ::1#53 Aliases:=20 h-i-t.infracaninophile.co.uk is an alias for happy-idiot-talk.infracanino= phile.co.uk. happy-idiot-talk.infracaninophile.co.uk has address 81.187.76.162 happy-idiot-talk.infracaninophile.co.uk has IPv6 address 2001:8b0:151:1:2= 40:5ff:fea5:8db7 happy-idiot-talk.infracaninophile.co.uk mail is handled by 10 smtp.infrac= aninophile.co.uk. Arguably it is a bug for host(1) to give up on the first entry in /etc/resolv.conf when told to use a conflicting address type.=20 However, that should be reported to ISC rather than the FreeBSD=20 project. When allowed to determine the transport type automatically everything works as expected. Cheers, Matthew [*] but only if the domain name of the nameserver you want to query can be resolved by means that don't fall foul of the same IPv4 vs IPv6 problem. Which boils down to using other than the DNS -- eg.=20 /etc/hosts -- to find the nameserver address. --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW --------------enig652B9874FDC5FDBAB40BEB7D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkWwsAACgkQ8Mjk52CukIwQzwCgj9bhTywi8h6xyRkfOxtfxrAh JAIAn3Eo1Ccp+lmigvJgxi8+UJpHDlfA =be5o -----END PGP SIGNATURE----- --------------enig652B9874FDC5FDBAB40BEB7D-- From owner-freebsd-stable@FreeBSD.ORG Sun Nov 9 18:27:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F9E1106564A for ; Sun, 9 Nov 2008 18:27:30 +0000 (UTC) (envelope-from lists@lozenetz.org) Received: from mail.webreality.org (mailserver.webreality.org [217.75.141.5]) by mx1.freebsd.org (Postfix) with ESMTP id 3BF568FC18 for ; Sun, 9 Nov 2008 18:27:28 +0000 (UTC) (envelope-from lists@lozenetz.org) Received: from [192.168.3.23] (78-83-112-11.spectrumnet.bg [78.83.112.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.webreality.org (Postfix) with ESMTP id 2CE801522CCD; Sun, 9 Nov 2008 20:07:59 +0200 (EET) Message-ID: <491726F4.4040808@lozenetz.org> Date: Sun, 09 Nov 2008 20:07:48 +0200 From: Anton - Valqk User-Agent: Icedove 1.5.0.14eol (X11/20080724) MIME-Version: 1.0 To: Ken Chen References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-HostIT-MailScanner-Information: Please contact the ISP for more information X-HostIT-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details X-HostIT-MailScanner-From: lists@lozenetz.org Cc: freebsd-stable@freebsd.org Subject: Re: php-cgi frozen with sbwait when SMP enable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Nov 2008 18:27:30 -0000 You can try taking look to lighttpd status and fcgi processes status like this: server.modules += ( "mod_status" ) status.status-url = "/server-status" status.statistics-url = "/sstatus1" status.statistics-url gives info for each fastcgi like this: fastcgi.active-requests: 0 fastcgi.backend.backend1.0.connected: 12493970 fastcgi.backend.backend1.0.died: 0 fastcgi.backend.backend1.0.disabled: 0 fastcgi.backend.backend1.0.load: 0 fastcgi.backend.backend1.0.overloaded: 0 fastcgi.backend.backend1.load: 1 fastcgi.requests: 19479062 etc... read what each means on lighttpd site... pls tell what caused this, it'd be very interesting to me! cheers, valqk. Ken Chen wrote: > I capture something. > > Please check the PID 57776. It's CPU time never change since my previous > mail here. > > web4# ps alx | grep php-cgi | grep -v grep | grep sbwait > 65534 57776 47240 0 4 0 182328 84984 sbwait I ?? 2:02.12 > /usr/local/bin/php-cgi > 65534 57801 47240 0 4 0 182328 82408 sbwait I ?? 0:19.97 > /usr/local/bin/php-cgi > 65534 57809 47240 0 4 0 182328 84096 sbwait I ?? 1:12.03 > /usr/local/bin/php-cgi > 65534 57823 47240 0 4 0 182328 84492 sbwait I ?? 2:04.21 > /usr/local/bin/php-cgi > 65534 57833 47240 0 4 0 183352 83316 sbwait I ?? 0:28.62 > /usr/local/bin/php-cgi > 65534 57866 47240 0 4 0 182328 79952 sbwait I ?? 0:05.92 > /usr/local/bin/php-cgi > 65534 57870 47240 0 4 0 182328 83184 sbwait I ?? 0:56.83 > /usr/local/bin/php-cgi > 65534 57871 47240 0 4 0 182328 83388 sbwait I ?? 0:54.96 > /usr/local/bin/php-cgi > 65534 57891 47240 0 4 0 182328 84436 sbwait I ?? 1:58.32 > /usr/local/bin/php-cgi > 65534 57925 47240 0 4 0 182328 84380 sbwait I ?? 2:03.53 > /usr/local/bin/php-cgi > 65534 65944 47240 0 4 0 182328 84184 sbwait I ?? 0:39.97 > /usr/local/bin/php-cgi > 65534 65952 47240 0 4 0 182328 84408 sbwait I ?? 0:21.37 > /usr/local/bin/php-cgi > 65534 66007 47240 0 4 0 183352 90960 sbwait I ?? 1:16.81 > /usr/local/bin/php-cgi > 65534 66014 47240 5 4 0 182328 92748 sbwait S ?? 1:41.23 > /usr/local/bin/php-cgi > 65534 66038 47240 1 4 0 182328 91900 sbwait I ?? 1:38.04 > /usr/local/bin/php-cgi > 65534 66060 47240 0 4 0 182328 90048 sbwait I ?? 1:15.46 > /usr/local/bin/php-cgi > 65534 66078 47240 3 4 0 182328 92224 sbwait S ?? 1:39.66 > /usr/local/bin/php-cgi > web4# top -b > last pid: 70768; load averages: 1.62, 1.65, 1.43 up 4+15:56:06 > 22:53:48 > 85 processes: 1 running, 84 sleeping > > Mem: 492M Active, 1204M Inact, 218M Wired, 60M Cache, 112M Buf, 27M Free > Swap: 2019M Total, 20K Used, 2019M Free > > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 69544 nobody 1 8 0 203M 38500K nanslp 1 6:31 11.33% php > 47290 nobody 1 4 0 101M 98M kqread 1 30:42 2.98% lighttpd > 66526 nobody 1 4 0 178M 92796K accept 1 1:40 1.12% php-cgi > 66077 nobody 1 4 0 178M 92512K accept 0 1:49 1.07% php-cgi > 65921 nobody 1 4 0 178M 92696K accept 0 1:43 0.98% php-cgi > 65968 nobody 1 4 0 178M 92484K accept 0 1:43 0.93% php-cgi > 66017 nobody 1 4 0 178M 92444K accept 0 1:50 0.88% php-cgi > 65979 nobody 1 4 0 178M 92676K accept 1 1:44 0.88% php-cgi > 66424 nobody 1 4 0 178M 92928K accept 1 1:36 0.88% php-cgi > 65938 nobody 1 4 0 178M 92336K accept 1 1:52 0.73% php-cgi > 65951 nobody 1 4 0 178M 92704K accept 0 1:48 0.73% php-cgi > 66016 nobody 1 4 0 178M 92232K accept 1 1:41 0.73% php-cgi > 65950 nobody 1 4 0 178M 93192K accept 0 1:51 0.68% php-cgi > 65999 nobody 1 4 0 178M 92940K accept 1 1:46 0.63% php-cgi > 66008 nobody 1 4 0 178M 93000K accept 1 1:46 0.63% php-cgi > 69286 nobody 1 4 0 178M 92208K accept 1 0:37 0.63% php-cgi > 47289 nobody 1 4 0 73400K 70640K kqread 1 12:02 0.59% lighttpd > 65980 nobody 1 4 0 178M 93156K accept 1 1:51 0.59% php-cgi > 2008/11/7 Ivan Voras > > >> Ken Chen wrote: >> >>> Oh.. sorry, I forgot to provide the information of my environment. >>> >>> web4# php-cgi -v >>> PHP 5.2.6 (cgi-fcgi) (built: Nov 2 2008 11:16:30) >>> Copyright (c) 1997-2008 The PHP Group >>> Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies >>> with XCache v1.2.2, Copyright (c) 2005-2007, by mOo >>> web4# /usr/local/lighttpd/sbin/lighttpd -v >>> lighttpd-1.4.19 - a light and fast webserver >>> Build-Date: Sep 1 2008 16:58:51 >>> web4# uname -a >>> FreeBSD web4.xxxx.com 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #11: Mon Nov >>> >> 3 >> >>> 01:10:36 CST 2008 root@web4.xxxx.com:/usr/obj/usr/src/sys/WEB4 i386 >>> web4# ps alx | grep php-cgi | grep -v grep | grep sbwait >>> 65534 57776 47240 0 4 0 182328 84984 sbwait I ?? 2:02.12 >>> /usr/local/bin/php-cgi >>> 65534 57801 47240 0 4 0 182328 82408 sbwait I ?? 0:19.97 >>> /usr/local/bin/php-cgi >>> 65534 57809 47240 0 4 0 182328 84096 sbwait I ?? 1:12.03 >>> /usr/local/bin/php-cgi >>> 65534 57823 47240 0 4 0 182328 84492 sbwait I ?? 2:04.21 >>> /usr/local/bin/php-cgi >>> 65534 57833 47240 0 4 0 183352 83316 sbwait I ?? 0:28.62 >>> /usr/local/bin/php-cgi >>> 65534 57866 47240 0 4 0 182328 79952 sbwait I ?? 0:05.92 >>> /usr/local/bin/php-cgi >>> 65534 57870 47240 0 4 0 182328 83184 sbwait I ?? 0:56.83 >>> /usr/local/bin/php-cgi >>> 65534 57871 47240 0 4 0 182328 83388 sbwait I ?? 0:54.96 >>> /usr/local/bin/php-cgi >>> 65534 57891 47240 0 4 0 182328 84436 sbwait I ?? 1:58.32 >>> /usr/local/bin/php-cgi >>> 65534 57925 47240 0 4 0 182328 84380 sbwait I ?? 2:03.53 >>> /usr/local/bin/php-cgi >>> 65534 65944 47240 0 4 0 182328 84184 sbwait I ?? 0:39.97 >>> /usr/local/bin/php-cgi >>> 65534 65952 47240 0 4 0 182328 84408 sbwait I ?? 0:21.37 >>> /usr/local/bin/php-cgi >>> >> This does seem a bit unusual, but seeing that your execution times are >> not null it might that the PHP servers are actually doing some useful >> work. You should have a mixture of various states in PHP - do they show >> up in top? >> >> My own example is: >> >> last pid: 77421; load averages: 2.82, 2.59, 2.13 >> up >> 55+16:58:49 15:48:16 >> 209 processes: 2 running, 206 sleeping, 1 zombie >> CPU: 49.8% user, 0.0% nice, 2.8% system, 0.0% interrupt, 47.4% idle >> Mem: 1493M Active, 1583M Inact, 278M Wired, 139M Cache, 112M Buf, 505M Free >> Swap: 4500M Total, 416M Used, 4084M Free, 9% Inuse >> >> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND >> 75863 www 1 4 0 162M 50020K sbwait 3 2:54 36.77% php-cgi >> 76830 www 1 103 0 156M 41556K CPU2 3 1:28 36.77% php-cgi >> 76834 www 1 4 0 163M 56628K sbwait 0 2:23 33.59% php-cgi >> 76019 www 1 4 0 150M 38948K accept 3 3:12 20.56% php-cgi >> 76825 www 1 4 0 158M 42912K accept 2 1:21 18.16% php-cgi >> 76846 www 1 4 0 162M 42600K sbwait 1 1:07 14.36% php-cgi >> 76835 www 1 4 0 151M 39948K accept 2 1:28 12.60% php-cgi >> 76829 www 1 4 0 150M 36564K sbwait 2 1:46 2.98% php-cgi >> >> This is unusually high load, a spike, for this server but it has many >> cores and it's stable. It's also running 7.1-PRERELEASE. >> >> >> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > From owner-freebsd-stable@FreeBSD.ORG Sun Nov 9 21:09:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E56E1065672; Sun, 9 Nov 2008 21:09:29 +0000 (UTC) (envelope-from vermaden@interia.pl) Received: from smtp239.poczta.interia.pl (smtp239.poczta.interia.pl [217.74.64.239]) by mx1.freebsd.org (Postfix) with ESMTP id E32C58FC08; Sun, 9 Nov 2008 21:09:28 +0000 (UTC) (envelope-from vermaden@interia.pl) Received: by smtp239.poczta.interia.pl (INTERIA.PL, from userid 502) id 445DB3971E3; Sun, 9 Nov 2008 22:09:27 +0100 (CET) Received: from f46.poczta.interia.pl (f46.poczta.interia.pl [10.217.2.46]) by smtp239.poczta.interia.pl (INTERIA.PL) with ESMTP id 9E9E7396FD9; Sun, 9 Nov 2008 22:09:26 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by f46.poczta.interia.pl (Postfix) with ESMTP id ED4CF46CCF0; Sun, 9 Nov 2008 22:09:25 +0100 (CET) Date: 09 Nov 2008 22:09:25 +0100 From: vermaden To: Boris Kochergin MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=ISO-8859-2 X-ORIGINATE-IP: 85.89.167.26 X-Mailer: PSE Message-Id: <20081109210925.ED4CF46CCF0@f46.poczta.interia.pl> X-EMID: 74540acc Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: sysctl debug.cpufreq.highest X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Nov 2008 21:09:29 -0000 Thank You mate. Works like a charm, why not merge it into STABLE and CURRENT branches? I assume that STABLE is currently frozen 'cause of the RELEASE process, but such a small (and tested as 'lowest') change should fit into RELEASE. Regards vermaden > I've rolled a patchset to do this for 7.0-RELEASE > (http://acm.poly.edu/~spawk/cpufreq/) if anyone's interested. > > -Boris > > vermaden wrote: > > Hi, > > > > Currently there is possibility to set lowest speed of > > cpu for scaling with cpufreq (debug.cpufreq.lowest), > > it would be good to include also a option to set the > > highest possible freq to use with cpufreq, some laptops > > get too hot and/or consume too much power when running > > on maximum power/speed of cpu. > > > > Regards > > vermaden ---------------------------------------------------------------------- Dzwon taniej na zagraniczne komorki! Sprawdz >> http://link.interia.pl/f1f6a From owner-freebsd-stable@FreeBSD.ORG Sun Nov 9 23:49:37 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3A361065689 for ; Sun, 9 Nov 2008 23:49:36 +0000 (UTC) (envelope-from joe@zircon.seattle.wa.us) Received: from dsl254-019-221.sea1.dsl.speakeasy.net (dsl254-019-221.sea1.dsl.speakeasy.net [216.254.19.221]) by mx1.freebsd.org (Postfix) with ESMTP id 7AF568FC16 for ; Sun, 9 Nov 2008 23:49:36 +0000 (UTC) (envelope-from joe@zircon.seattle.wa.us) Received: (qmail 2801 invoked from network); 9 Nov 2008 23:29:08 -0000 Received: from localhost (HELO zircon.zircon.seattle.wa.us) (127.0.0.1) by localhost with ESMTP; 9 Nov 2008 23:29:08 -0000 Message-ID: <49177244.9060802@zircon.seattle.wa.us> Date: Sun, 09 Nov 2008 15:29:08 -0800 From: Joe Kelsey User-Agent: Thunderbird 2.0.0.17 (X11/20081017) MIME-Version: 1.0 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= References: <20081107071752.GA5842@icarus.home.lan> <77C223A7-C5FC-45DE-BF1A-3BC7982FA582@FreeBSD.ORG> In-Reply-To: <77C223A7-C5FC-45DE-BF1A-3BC7982FA582@FreeBSD.ORG> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Mon, 10 Nov 2008 00:05:41 +0000 Cc: Jeremy Chadwick , freebsd-stable@FreeBSD.ORG, votdev@gmx.de, Peter Wemm , freebsd-hardware@FreeBSD.ORG Subject: Re: Western Digital hard disks and ATA timeouts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Nov 2008 23:49:37 -0000 Søren Schmidt wrote: > On 7Nov, 2008, at 20:12 , Peter Wemm wrote: > >> On Thu, Nov 6, 2008 at 11:17 PM, Jeremy Chadwick >> wrote: >> [..] >>> As stated, FreeBSD's ATA command timeout is hard-set to 5 seconds, and >>> is not adjustable without editing the ATA code yourself and increasing >>> the value. The FreeNAS folks have made patches available to turn the >>> timeout value into a sysctl. >>> >>> Soren and/or others, please increase this timeout value. Five seconds >>> has now been deemed too aggressive a default. And please consider >>> migrating the timeout value into a sysctl. >> >> The 5 second timeout has been a problem for quite a while actually. >> I've had a number of instances where I've had to increase it to 20 or >> 30 seconds when recovering from marginal drives. The longest >> "successful" recovery attempt I've seen was 26 seconds, I believe on a >> Maxtor drive a few years ago. ("successful" == the drive spent 26 >> seconds but eventually successfully read the sector). Even the IBM >> death star drives could take much longer than 5 seconds to do a >> recovery 5 years ago. 5 seconds has never been a good default. >> >> I think the timeout should be increased to at least 30 seconds. My >> windows box has a timeout that goes for several minutes. >> >> If there is concern about FreeBSD appearing to hang, I could imagine >> that a console warning message could be printed after 5 seconds. But >> just say "drive has not yet responded". But give it more time. >> >> In this day and age we're generally not playing games with udma33 vs >> 66, notched cables, poor CRC support etc. SATA seems to have >> eliminated all that. Hmm, it might make sense to increase the timeout >> on SATA connections to 2 or 3 minutes by default. > > Actually I do have a patch around that logs the timeout on the console > after the normal timeout (5secs), then just goes on to wait for double > the timeout and log again etc etc, final timeout was IIRC 60 secs but > could be anything. I have a disk which I am finally getting rid of that produces READ_DMA and WRITE_DMA errors at a pretty high rate. I did enable the extra ATA error reporting and it doesn't seem to indicate any sort of actual errors, just extra long itmeouts. At one time, I did change the system to extend the timeout, but I did not see any real improvement at 30 seconds. I suspect that an even more extended timeout would be necessary to solve the problem. I am removing the disk this week. Does anyone want a disk that produces DMA timeouts at a regular rate? Would it help actually solve this problem? Please let me know if you want such a beast and I will ship it to you. /Joe From owner-freebsd-stable@FreeBSD.ORG Mon Nov 10 05:46:41 2008 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A593106564A for ; Mon, 10 Nov 2008 05:46:41 +0000 (UTC) (envelope-from lehmann@ans-netz.de) Received: from avocado.salatschuessel.net (avocado.salatschuessel.net [78.111.72.186]) by mx1.freebsd.org (Postfix) with SMTP id E74198FC17 for ; Mon, 10 Nov 2008 05:46:40 +0000 (UTC) (envelope-from lehmann@ans-netz.de) Received: (qmail 51586 invoked by uid 89); 10 Nov 2008 05:46:37 -0000 Received: from unknown (HELO kartoffel.salatschuessel.net) (78.111.72.187) by avocado.salatschuessel.net with SMTP; 10 Nov 2008 05:46:37 -0000 Date: Mon, 10 Nov 2008 06:46:38 +0100 From: Oliver Lehmann To: stable@FreeBSD.org Message-Id: <20081110064638.d0f20e20.lehmann@ans-netz.de> In-Reply-To: <20081109092051.99e8d97c.lehmann@ans-netz.de> References: <20081109092051.99e8d97c.lehmann@ans-netz.de> X-Mailer: Sylpheed 2.5.0 (GTK+ 2.12.11; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Re: libzfs: vmem.h missing X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2008 05:46:41 -0000 Oliver Lehmann wrote: > Hi, > > when I try to compile an actual 7 STABLE Im getting: > > why is vmem.h missing? My cvsupfile only contained src-sys... so vmem.h got probably removed, but zfs_context.h got not updated.... -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ From owner-freebsd-stable@FreeBSD.ORG Mon Nov 10 07:16:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D51531065672 for ; Mon, 10 Nov 2008 07:16:34 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 984E88FC14 for ; Mon, 10 Nov 2008 07:16:34 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id AFCA3170E4; Mon, 10 Nov 2008 07:16:32 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id mAA7GV5w073414; Mon, 10 Nov 2008 07:16:32 GMT (envelope-from phk@critter.freebsd.dk) To: Mike Tancsa From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 03 Nov 2008 20:43:53 EST." <200811040143.mA41hjaa029665@lava.sentex.ca> Date: Mon, 10 Nov 2008 07:16:31 +0000 Message-ID: <73413.1226301391@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: freebsd-stable@freebsd.org Subject: Re: fifo log problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2008 07:16:34 -0000 In message <200811040143.mA41hjaa029665@lava.sentex.ca>, Mike Tancsa writes: >I tried changing the config so that there is only the fifo log being >written to and disabled newsyslog so that syslogd is not getting a >HUP signal. The strange thing is that reading from it gives >different results?!? > >Sometimes doing >[ps0278]# fifolog_reader all.fifo | wc >>From 0 Wed Dec 31 19:00:00 1969 >To 1225760679 Mon Nov 3 20:04:39 2008 >Read from 1d800 > 59 413 3068 >0[ps0278]# > >and a exactly for 1min it will show the correct results > >0[ps0278]# fifolog_reader all.fifo | wc >>From 0 Wed Dec 31 19:00:00 1969 >To 1225760538 Mon Nov 3 20:02:18 2008 >Read from 0 > 10765 75995 556816 >0[ps0278]# I could fear that you have two fifologs running at the same time, possibly as a result of syslogd doing something strange on sighup... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-stable@FreeBSD.ORG Mon Nov 10 10:37:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6ED48106564A for ; Mon, 10 Nov 2008 10:37:46 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id DF9288FC17 for ; Mon, 10 Nov 2008 10:37:45 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KzU9Q-0008Jd-6U for freebsd-stable@freebsd.org; Mon, 10 Nov 2008 10:37:44 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 10 Nov 2008 10:37:44 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 10 Nov 2008 10:37:44 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Mon, 10 Nov 2008 11:37:53 +0100 Lines: 46 Message-ID: References: <491726F4.4040808@lozenetz.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig607946EE2BF798EC5B686D47" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.17 (X11/20080925) In-Reply-To: <491726F4.4040808@lozenetz.org> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: php-cgi frozen with sbwait when SMP enable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2008 10:37:46 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig607946EE2BF798EC5B686D47 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Anton - Valqk wrote: > You can try taking look to lighttpd status and fcgi processes status > like this: > server.modules +=3D ( "mod_status" ) > status.status-url =3D "/server-status" > status.statistics-url =3D "/sstatus1" >=20 > status.statistics-url gives info for each fastcgi like this: >=20 > fastcgi.active-requests: 0 > fastcgi.backend.backend1.0.connected: 12493970 > fastcgi.backend.backend1.0.died: 0 > fastcgi.backend.backend1.0.disabled: 0 > fastcgi.backend.backend1.0.load: 0 > fastcgi.backend.backend1.0.overloaded: 0 > fastcgi.backend.backend1.load: 1 > fastcgi.requests: 19479062 >=20 >=20 > etc... read what each means on lighttpd site... > pls tell what caused this, it'd be very interesting to me! Yes, though I don't use lighttpd right now, I plan to one day so I'm also interested in the cause and solution for this problem. --------------enig607946EE2BF798EC5B686D47 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJGA8BldnAQVacBcgRArafAJ0a1cyjJMXyoPudp39tP2l3at8RJgCePetf uYaZDmpj3DmOeKJzxVWlAHQ= =ekqf -----END PGP SIGNATURE----- --------------enig607946EE2BF798EC5B686D47-- From owner-freebsd-stable@FreeBSD.ORG Mon Nov 10 12:45:56 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBDC0106564A for ; Mon, 10 Nov 2008 12:45:56 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id 6E7958FC1F for ; Mon, 10 Nov 2008 12:45:55 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id 17184119D91; Mon, 10 Nov 2008 13:45:54 +0100 (CET) Date: Mon, 10 Nov 2008 13:45:53 +0100 From: Victor Balada Diaz To: freebsd-stable@freebsd.org Message-ID: <20081110124553.GL2327@alf.bsdes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.3i Cc: Remko Lodder Subject: Interrupt routing issues in FreeBSD 7.1-BETA2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2008 12:45:56 -0000 Hello, last month i reported a problem with interrupt storms in re(4). You can find that report here: http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/046075.html After that, i filled a bug report: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/128287 Remko Lodder (CC'ed) suggested me that i should disable USB code in kernel if i was not using it. As i wasn't using it, i tried disabling it and so far, the problem was solved. After a few days in production with the new kernel, GENERIC without USB and firewrire i've found other interrupt problems: vmstat -i: oro# vmstat -i interrupt total rate irq1: atkbd0 2 0 irq9: acpi0 1 0 irq19: re0 39786514 42 irq22: atapci0 8050818241 8515 cpu0: timer 1890881479 1999 cpu1: timer 1890881390 1999 Total 11872367627 12557 This time the problem is not in IRQ19 (re), but on IRQ 22 atapci0. This looked weird to me, as this interrupt is not shared, so i searched what was the model and MFG of this motherboard and found with dmidecode this: Base Board Information Manufacturer: MICRO-STAR INTERANTIONAL CO.,LTD Product Name: MS-7368 Version: 1.0 Looking at freebsd archives for this model i've found other people had the same problem: http://lists.freebsd.org/pipermail/freebsd-current/2007-November/080525.html http://lists.freebsd.org/pipermail/freebsd-questions/2008-June/176794.html Related problems: http://lists.freebsd.org/pipermail/freebsd-stable/2007-November/038571.html http://lists.freebsd.org/pipermail/freebsd-current/2008-February/083584.html Does anyone know what could be the cause of this or how can i fix it? If there is any more information i could provide to help solving this, just ask for it and i'll do my best to get it. Thanks in advance. Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Mon Nov 10 13:22:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 728521065672 for ; Mon, 10 Nov 2008 13:22:00 +0000 (UTC) (envelope-from fernan.aguero@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id EE9758FC22 for ; Mon, 10 Nov 2008 13:21:59 +0000 (UTC) (envelope-from fernan.aguero@gmail.com) Received: by ey-out-2122.google.com with SMTP id 6so894460eyi.7 for ; Mon, 10 Nov 2008 05:21:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=yoL2a+bPSa2NhXM1CLl8jHamihL8itp8+AOgP/i6EOc=; b=sJXXk1fMYs4q2ACf1uYJ7bT0bPSFcNZzNJUk5+I2vu8M8MU5uXfYEsVCOQ5hXXW3h3 2bn2siEFy+Wg0Uok/D9FvkueZg/OIq79Fm2BTjUrRUVd+KKdbkDbyv/eUjYPuP6bFCDg xS2ivtQT/90ozWfl8dsXq8A13CTLiUGrg/JTw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=awCoL/KnlHST0zmZyPtCGtFLvyTBTJ9YSabt8CGA8+AB0Y8OO4P5jHpyCZcHiKznOk 8DJVMDB3/ng2PVZVumN0zBSGs9foQkidSS6PSBldP4ktlm4LyEXxHumcDSuvZIvN8T69 9bXDJ6dFXbgBJDmrIc+FflwbmYhTTSIBBw2Lc= Received: by 10.210.142.10 with SMTP id p10mr2801023ebd.144.1226321566742; Mon, 10 Nov 2008 04:52:46 -0800 (PST) Received: by 10.210.136.13 with HTTP; Mon, 10 Nov 2008 04:52:46 -0800 (PST) Message-ID: <520894aa0811100452p5f7b5ebdx9f3c9929a452ef10@mail.gmail.com> Date: Mon, 10 Nov 2008 10:52:46 -0200 From: "Fernan Aguero" To: "Kirk Strauser" In-Reply-To: <20081110120134.GB14740@iib.unsam.edu.ar> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081110120134.GB14740@iib.unsam.edu.ar> X-Mailman-Approved-At: Mon, 10 Nov 2008 14:47:52 +0000 Cc: Subject: Re: [fernan@iib.unsam.edu.ar: Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2008 13:22:00 -0000 On Mon, Nov 10, 2008 at 10:01 AM, Fernan Aguero wrote: > > Date: Wed, 29 Oct 2008 14:05:22 -0300 > From: Fernan Aguero > To: Kirk Strauser > Cc: freebsd-stable@freebsd.org, d@delphij.net, > John Baldwin , re@freebsd.org > Subject: Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1? > >> On Tuesday 07 October 2008 17:10:49 Xin LI wrote: >> > Did anyone who can trigger the data corruption has tried John's patch >> > and let us know if it worked? >> > >> > Cheers, >> >> I can confirm that it works on my PowerEdge SC1435. With both controllers >> running in SATA150 mode, I have an uptime of 101 days with moderately heavy >> load. >> -- >> Kirk Strauser > > Same here. The ata_ht1000.patch referenced in this thread > works, in my case at least with 1 controller running in > SATA150 mode (I have only 1 disk). > > However, the recent 7.1-BETA2 does not work for me, contrary > to reports saying that this BETA contains the patch. Looking > at the sources, it seems evident that the patch applied is > not identical to the ata_ht1000.patch in this thread. > > This patch: > http://people.freebsd.org/~jhb/patches/ata_ht1000.patch > is the only requirement to turn a broken 7.1-BETA1 into a > working 7.1 for a Dell PowerEdge SC1435. > > The recent 7.1-BETA2, does not work! > > Fernan > Hi, can anyone confirm if 7.1-BETA2 works for this platform? It does not for me. Will there be another BETA/RC before 7.1 is rolled out? Thanks, -- fernan From owner-freebsd-stable@FreeBSD.ORG Mon Nov 10 16:01:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04E4A1065672 for ; Mon, 10 Nov 2008 16:01:04 +0000 (UTC) (envelope-from sclark46@earthlink.net) Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by mx1.freebsd.org (Postfix) with ESMTP id C5C4C8FC14 for ; Mon, 10 Nov 2008 16:01:03 +0000 (UTC) (envelope-from sclark46@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=EnnyM3e2aJ5cjhJevTR0sD2eiKhzs4z+PWX7eT/p4jBtSGGfVIYDSDKMRyQvFaGU; h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [208.118.36.229] (helo=joker.seclark.com) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1KzZCI-0000xO-O8 for freebsd-stable@freebsd.org; Mon, 10 Nov 2008 11:01:03 -0500 Message-ID: <49185ABC.6080004@earthlink.net> Date: Mon, 10 Nov 2008 11:01:00 -0500 From: Stephen Clark User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: FreeBSD Stable Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec7964a95ab13572d44eddb818548a6f661b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 208.118.36.229 Subject: du and df don't agree X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sclark46@earthlink.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2008 16:01:04 -0000 Why would du show 630k used by /tmp while df show 161M used by /tmp? # du -sh /tmp 630K /tmp # df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1a 94M 41M 45M 47% / devfs 1.0K 1.0K 0B 100% /dev /dev/ad0s1e 193M 161M 17M 91% /tmp ... remaining fs info removed # uname -a FreeBSD 6.1-STABLE FreeBSD 6.1-STABLE I have run fstat /tmp and can't find any files that are using the space that df is claiming as being used. -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) From owner-freebsd-stable@FreeBSD.ORG Mon Nov 10 16:22:05 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0E6A1065672 for ; Mon, 10 Nov 2008 16:22:05 +0000 (UTC) (envelope-from erwan@rail.eu.org) Received: from depot.rail.eu.org (bievres.rail.eu.org [82.227.34.188]) by mx1.freebsd.org (Postfix) with ESMTP id A60EE8FC22 for ; Mon, 10 Nov 2008 16:22:05 +0000 (UTC) (envelope-from erwan@rail.eu.org) Received: from depot.rail.eu.org (localhost [127.0.0.1]) by depot.rail.eu.org (Postfix) with ESMTP id 9A0D581BC38 for ; Mon, 10 Nov 2008 17:03:19 +0100 (CET) Received: from ratagaz.lan (78-86-58-6.zone2.bethere.co.uk [78.86.58.6]) by depot.rail.eu.org (Postfix) with ESMTPSA id 7904081BC17 for ; Mon, 10 Nov 2008 17:03:19 +0100 (CET) Received: by ratagaz.lan (Postfix, from userid 501) id B88E1BD9239; Mon, 10 Nov 2008 16:03:16 +0000 (GMT) Date: Mon, 10 Nov 2008 16:03:16 +0000 From: Erwan David To: freebsd-stable@freebsd.org Message-ID: <20081110160315.GH9074@rail.eu.org> Mail-Followup-To: freebsd-stable@freebsd.org References: <49185ABC.6080004@earthlink.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49185ABC.6080004@earthlink.net> X-Republicain: 20 brumaire an CCXVII (Herse) User-Agent: Mutt/1.5.17 (2007-11-01) Subject: Re: du and df don't agree X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2008 16:22:06 -0000 Le Mon 10/11/2008, Stephen Clark disait > Why would du show 630k used by /tmp while df show 161M used > by /tmp? > > > # du -sh /tmp > 630K /tmp > # df -h > Filesystem Size Used Avail Capacity Mounted on > /dev/ad0s1a 94M 41M 45M 47% / > devfs 1.0K 1.0K 0B 100% /dev > /dev/ad0s1e 193M 161M 17M 91% /tmp > ... remaining fs info removed > > # uname -a > FreeBSD 6.1-STABLE FreeBSD 6.1-STABLE > > I have run fstat /tmp and can't find any files that are using > the space that df is claiming as being used. Because this space is used by removed, but open files. Try lsof +L1 to see them. -- Erwan From owner-freebsd-stable@FreeBSD.ORG Mon Nov 10 16:26:07 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29B1E106567D for ; Mon, 10 Nov 2008 16:26:07 +0000 (UTC) (envelope-from jille@quis.cx) Received: from mulgore.hexon-is.nl (mulgore.hexon-is.nl [82.94.237.14]) by mx1.freebsd.org (Postfix) with ESMTP id 7C8AD8FC24 for ; Mon, 10 Nov 2008 16:26:06 +0000 (UTC) (envelope-from jille@quis.cx) X-Hexon-MailScanner-Watermark: 1226938211.49569@M2lQmOEXU4QfF2HezeHecA Received: from [10.0.0.72] ([10.15.16.6]) (authenticated bits=0) by mulgore.hexon-is.nl (8.14.1/8.13.8) with ESMTP id mAAG9qOC029136; Mon, 10 Nov 2008 17:09:53 +0100 Message-ID: <49185CDB.70702@quis.cx> Date: Mon, 10 Nov 2008 17:10:03 +0100 From: Jille Timmermans User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: sclark46@earthlink.net References: <49185ABC.6080004@earthlink.net> In-Reply-To: <49185ABC.6080004@earthlink.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Hexon-MailScanner-Information: Please contact the ISP for more information X-Hexon-MailScanner-ID: mAAG9qOC029136 X-Hexon-MailScanner: Found to be clean X-Hexon-MailScanner-From: jille@quis.cx Cc: FreeBSD Stable Subject: Re: du and df don't agree X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2008 16:26:07 -0000 Probably some file descriptor to an unlinked file is still open. The space on disk will be freed when the last descriptor is closed. and because there is no file linked to the data, du can't see it. (iirc MySQL does this in some situaties when using temp-tables or rebuilding tables) -- Jille Stephen Clark wrote: > Why would du show 630k used by /tmp while df show 161M used > by /tmp? > > > # du -sh /tmp > 630K /tmp > # df -h > Filesystem Size Used Avail Capacity Mounted on > /dev/ad0s1a 94M 41M 45M 47% / > devfs 1.0K 1.0K 0B 100% /dev > /dev/ad0s1e 193M 161M 17M 91% /tmp > ... remaining fs info removed > > # uname -a > FreeBSD 6.1-STABLE FreeBSD 6.1-STABLE > > I have run fstat /tmp and can't find any files that are using > the space that df is claiming as being used. > From owner-freebsd-stable@FreeBSD.ORG Mon Nov 10 16:27:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE9F31065676 for ; Mon, 10 Nov 2008 16:27:25 +0000 (UTC) (envelope-from sclark46@earthlink.net) Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by mx1.freebsd.org (Postfix) with ESMTP id 7ABBB8FC1A for ; Mon, 10 Nov 2008 16:27:25 +0000 (UTC) (envelope-from sclark46@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Gw5FiTTR6UX8c3q6GOe9p5ZgaGkKr/5U29BPe9pPv4ozJ3K5THQPVyympXHxli0C; h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [208.118.36.229] (helo=joker.seclark.com) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1KzZbm-00006w-GS; Mon, 10 Nov 2008 11:27:22 -0500 Message-ID: <491860E9.2020400@earthlink.net> Date: Mon, 10 Nov 2008 11:27:21 -0500 From: Stephen Clark User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: Jille Timmermans References: <49185ABC.6080004@earthlink.net> <49185CDB.70702@quis.cx> In-Reply-To: <49185CDB.70702@quis.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec79da04cc8ee45de1623a184327b02e4ffd350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 208.118.36.229 Cc: FreeBSD Stable Subject: Re: du and df don't agree X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sclark46@earthlink.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2008 16:27:25 -0000 Jille Timmermans wrote: > Probably some file descriptor to an unlinked file is still open. > The space on disk will be freed when the last descriptor is closed. > and because there is no file linked to the data, du can't see it. > > (iirc MySQL does this in some situaties when using temp-tables or > rebuilding tables) > > -- Jille > > Stephen Clark wrote: >> Why would du show 630k used by /tmp while df show 161M used >> by /tmp? >> >> >> # du -sh /tmp >> 630K /tmp >> # df -h >> Filesystem Size Used Avail Capacity Mounted on >> /dev/ad0s1a 94M 41M 45M 47% / >> devfs 1.0K 1.0K 0B 100% /dev >> /dev/ad0s1e 193M 161M 17M 91% /tmp >> ... remaining fs info removed >> >> # uname -a >> FreeBSD 6.1-STABLE FreeBSD 6.1-STABLE >> >> I have run fstat /tmp and can't find any files that are using >> the space that df is claiming as being used. >> > Thanks, I managed to find the offending process with fstat and kill it. Now: Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1e 193M 666K 177M 0% /tmp $ du -sh /tmp 682K /tmp Regards, Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) From owner-freebsd-stable@FreeBSD.ORG Mon Nov 10 16:51:57 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41E651065676 for ; Mon, 10 Nov 2008 16:51:57 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 1816D8FC21 for ; Mon, 10 Nov 2008 16:51:55 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id mAAGLCE3027222; Mon, 10 Nov 2008 23:21:12 +0700 (KRAT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id mAAGLBD1027220; Mon, 10 Nov 2008 23:21:11 +0700 (KRAT) (envelope-from eugen) Date: Mon, 10 Nov 2008 23:21:11 +0700 From: Eugene Grosbein To: Stephen Clark Message-ID: <20081110162111.GA26951@svzserv.kemerovo.su> References: <49185ABC.6080004@earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49185ABC.6080004@earthlink.net> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD Stable Subject: Re: du and df don't agree X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2008 16:51:57 -0000 On Mon, Nov 10, 2008 at 11:01:00AM -0500, Stephen Clark wrote: > Why would du show 630k used by /tmp while df show 161M used > by /tmp? > > I have run fstat /tmp and can't find any files that are using > the space that df is claiming as being used. You need lsof +aL1 /tmp to see an answer. Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Mon Nov 10 19:21:45 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60906106567E for ; Mon, 10 Nov 2008 19:21:45 +0000 (UTC) (envelope-from lists@reiteration.net) Received: from smtp1.servage.net (smtp1.servage.net [77.232.76.11]) by mx1.freebsd.org (Postfix) with ESMTP id 2700D8FC12 for ; Mon, 10 Nov 2008 19:21:45 +0000 (UTC) (envelope-from lists@reiteration.net) Received: from [192.168.0.3] (roobarb.growveg.org [62.49.247.174]) by smtp1.servage.net (Postfix) with ESMTP id 784A9F984A5 for ; Mon, 10 Nov 2008 17:55:15 +0000 (GMT) Message-ID: <4918757E.7030904@reiteration.net> Date: Mon, 10 Nov 2008 17:55:10 +0000 From: John User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: FreeBSD Stable Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: OpenSSH error: error: key_read: uudecode failed FreeBSD_7 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2008 19:21:45 -0000 Hello, I installed FreeBSD from 7.0-release and brought up to stable a few days ago: lentil# uname -a FreeBSD lentil.growveg.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Mon Nov 10 09:21:06 GMT 2008 root@lentil.growveg.org:/ext0/system/src/sys/i386/compile/LENTIL i386 today I recompiled the kernel because I had stripped out the ipv6 stuff - however some apps seem to require it. That all went well. Afterwards, I set up the logging. I'm noticing the following error from the console: Nov 10 17:19:43 lentil sshd[1956]: error: key_read: uudecode AAAAB3NzaC1kc3MAAACBAKLAJVTvYOqi5bVYEyahzSTrb0L4JbLGhtiNGEXQr/pqWcTxBoicc1/EJt0MCirV3+A63smW4e7sfeZQhcKkwvL6MrSqc2wKSmJfPkV5GY/zwFiRLcsuNRWtd9Zgg8/mWhp5fZlZ6M81Cz\n failed Nov 10 17:19:43 lentil kernel: Nov 10 17:19:43 lentil sshd[1956]: error: key_read: uudecode AAAAB3NzaC1kc3MAAACBAKLAJVTvYOqi5bVYEyahzSTrb0L4JbLGhtiNGEXQr/pqWcTxBoicc1/EJt0MCirV3+A63smW4e7sfeZQhcKkwvL6MrSqc2wKSmJfPkV5GY/zwFiRLcsuNRWtd9Zgg8/mWhp5fZlZ6M81Cz\n failed Nov 10 17:19:43 lentil sshd[1956]: error: key_read: uudecode AAAAB3NzaC1kc3MAAACBAKLAJVTvYOqi5bVYEyahzSTrb0L4JbLGhtiNGEXQr/pqWcTxBoicc1/EJt0MCirV3+A63smW4e7sfeZQhcKkwvL6MrSqc2wKSmJfPkV5GY/zwFiRLcsuNRWtd9Zgg8/mWhp5fZlZ6M81Cz\n failed Nov 10 17:19:43 lentil sshd[1956]: Accepted publickey for john from 62.49.247.174 port 55327 ssh2 Nov 10 17:19:43 lentil kernel: Nov 10 17:19:43 lentil sshd[1956]: error: key_read: uudecode AAAAB3NzaC1kc3MAAACBAKLAJVTvYOqi5bVYEyahzSTrb0L4JbLGhtiNGEXQr/pqWcTxBoicc1/EJt0MCirV3+A63smW4e7sfeZQhcKkwvL6MrSqc2wKSmJfPkV5GY/zwFiRLcsuNRWtd9Zgg8/mWhp5fZlZ6M81Cz\n failed It doesn't seem to stop sshd from working, but it's annoying nonetheless. I did a quick google, and found someone describing the same problem at https://bugzilla.mindrot.org/show_bug.cgi?id=1525 but they say this was fixed in OpenSSH 4.7. - that URL is the latest report of the problem. I'm running a much later version: sshd: OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007 Can anyone help me with a fix/workaround? thanks -- John From owner-freebsd-stable@FreeBSD.ORG Mon Nov 10 22:47:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5D261065672 for ; Mon, 10 Nov 2008 22:47:50 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7A46D8FC20 for ; Mon, 10 Nov 2008 22:47:50 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 9161C28449 for ; Tue, 11 Nov 2008 06:47:49 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id 10BF3EC45CE; Tue, 11 Nov 2008 06:47:49 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id HUQfVz+VBuHV; Tue, 11 Nov 2008 06:47:42 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-62.dsl.pltn13.sbcglobal.net [76.237.33.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id E8326EC42C1; Tue, 11 Nov 2008 06:47:39 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:subject:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=XDhVBZe3M1PsSEXcji4RtEM+L2yBGwG9gevxiG0iey2zsDl84lwP1oN8QuuwFsJyk 9IpnSm5FB7sj5P07bAYAw== Message-ID: <4918BA09.5020000@delphij.net> Date: Mon, 10 Nov 2008 14:47:37 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.17 (X11/20080928) MIME-Version: 1.0 To: FreeBSD Stable X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: HEADSUP bce(4) 7-STABLE users [Fwd: svn commit: r184826 - in stable/7/sys: . dev/bce] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2008 22:47:51 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, FYI. I have just committed a MFC of most of recent bce(4) improvements. These changes were in tree for some months, while on the other hand it's a big chunk of changes. Feedbacks appreciated. - -------- Original Message -------- Subject: svn commit: r184826 - in stable/7/sys: . dev/bce Date: Mon, 10 Nov 2008 22:40:16 +0000 (UTC) From: Xin LI To: src-committers@FreeBSD.ORG, svn-src-all@FreeBSD.ORG, svn-src-stable@FreeBSD.ORG, svn-src-stable-7@FreeBSD.ORG Author: delphij Date: Mon Nov 10 22:40:16 2008 New Revision: 184826 URL: http://svn.freebsd.org/changeset/base/184826 Log: Merge the following bce(4) changes: r176448,178132,178853,179436,179695,179771,182293 r176448 (davidch) - Added loose RX MTU functionality to allow frames larger than 1500 bytes to be accepted even though the interface MTU is set to 1500. - Implemented new TCP header splitting/jumbo frame support which uses two chains for receive traffic rather than the original single receive chain. - Added additional debug support code. r178132 (davidch) - Fixed a problem with the send chain consumer index which would cause TX traffic to sit in the send chain until a received packet kick started the interrupt handler. This would cause extremely slow performance when used with NFS over UDP. - Removed untested polling code. - Updated copyright year in the file header. - Removed inadvertent ^M's created by DOS text editor. r178853 (scottl) The BCE chips appear to have an undocumented requirement that RX frames be aligned on an 8 byte boundary. Prior to rev 1.36 (now r176448) this wasn't a problem because mbuf clusters tend be naturally aligned. The switch to using split buffers with the first buffer being the embedded data area of the mbuf has broken this assumption, at least on i386, causing a complete failure of RX functionality. Fix this for now by using a full cluster for the first RX buffer. A more sophisticated approach could be done with the old buffer scheme to realign the m_data pointer with m_adj(), but I'm also not clear on performance benefits of this old scheme or the performance implications of adding an m_adj() call to every allocation. r179436 (jhb) Trim an extra semi-colon. r179695 (davidch) - Fixed kern/123696 by increasing firmware timeout value from 100 to 1000. - Fixed a problem on i386 architecture when using split header/jumbo frame firmware caused by hardware alignment requirements. - Added #define BCE_USE_SPLIT_HEADER to allow the feature to be enabled/disabled. Enabled by default. PR: kern/123696 r179771 (davidch) - Added support for BCM5709 and BCM5716 controllers. r182293 (davidch) - Updated support for 5716. - Added some additional code for debug builds. - Fixed a problem printing physical memory on 64bit system during debugging. - Modified some of the context memory and mailbox register names to more clearly distinguish their use. - Added memory barriers for Intel CPUs when accessing host memory data structures which are written by hardware. Approved by: re (kib) Modified: stable/7/sys/ (props changed) stable/7/sys/dev/bce/if_bce.c stable/7/sys/dev/bce/if_bcefw.h stable/7/sys/dev/bce/if_bcereg.h Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkYuggACgkQi+vbBBjt66AxbQCgvJlteJFhEsQSg5JEyxDhWmAx vxMAn13qErkFGa/hVGi8oyl/xiMSOW9Y =q8Qv -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 02:03:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C0101065670 for ; Tue, 11 Nov 2008 02:03:20 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by mx1.freebsd.org (Postfix) with ESMTP id C0AF88FC21 for ; Tue, 11 Nov 2008 02:03:19 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: by qw-out-2122.google.com with SMTP id 9so1784038qwb.7 for ; Mon, 10 Nov 2008 18:03:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=6Ky9ue5PcT0rVAOu+SeNOxISv5DbVrbsTpGWbTSs80E=; b=dTLrHxqLr2Rl+9gWxJJqCu7odMVwiXn+ZdDXOenKBwy0PPCh7nrd985ac3yUZBzWzK u3ia4fBMcwECULPEZUJdBPMrcFtA0+mgjzEwdUZcsNK1VNxITJFHoLTB5Y1/xo0ESH2a C9rHeTTCGL2WzL7p9OAFgAnWIAYdcyguC0/uE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=b2JJj1juXSz9BW9ntd2ZH5gativcTa77Gl6R0YckhV1Xo1iK7iuJd0NbHDxRENwP3d KXZabwdUIeCoHsjGMazv6Mw2J/xJU/hIVxPTNNeQ8dFeaw0xuWNeCpFnduw7cf4x3Udk G0fznkV5HF3s5/Ly4m6NJINZSVF+fticJe37w= Received: by 10.214.148.17 with SMTP id v17mr7609634qad.257.1226368998906; Mon, 10 Nov 2008 18:03:18 -0800 (PST) Received: from ?10.0.3.231? (pool-70-111-21-88.nwrk.east.verizon.net [70.111.21.88]) by mx.google.com with ESMTPS id 34sm19691046yxl.8.2008.11.10.18.03.16 (version=SSLv3 cipher=RC4-MD5); Mon, 10 Nov 2008 18:03:18 -0800 (PST) From: "Alexandre \"Sunny\" Kovalenko" To: vermaden In-Reply-To: <20081108012734.3274F1E3055@f03.poczta.interia.pl> References: <20081108012734.3274F1E3055@f03.poczta.interia.pl> Content-Type: text/plain; charset=utf-8 Date: Mon, 10 Nov 2008 21:03:08 -0500 Message-Id: <1226368988.1244.3.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: sysctl debug.cpufreq.highest X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 02:03:20 -0000 On Sat, 2008-11-08 at 02:27 +0100, vermaden wrote: > Hi, > > Currently there is possibility to set lowest speed of > cpu for scaling with cpufreq (debug.cpufreq.lowest), > it would be good to include also a option to set the > highest possible freq to use with cpufreq, some laptops > get too hot and/or consume too much power when running > on maximum power/speed of cpu. If temperature is the concern, you could override passive cooling threshold by putting something like hw.acpi.thermal.user_override=1 hw.acpi.thermal.tz1._PSV=75C into your /etc/sysctl.conf You will need to figure out which thermal zone you need to override _PSV for (in my case tz1) and what do you want to cap temperature at (in my case 75C) HTH, -- Alexandre "Sunny" Kovalenko (ОлекÑандр Коваленко) From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 08:03:28 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9E4E106568F for ; Tue, 11 Nov 2008 08:03:28 +0000 (UTC) (envelope-from mail25@bzerk.org) Received: from ei.bzerk.org (tunnel490.ipv6.xs4all.nl [IPv6:2001:888:10:1ea::2]) by mx1.freebsd.org (Postfix) with ESMTP id 49E1A8FC19 for ; Tue, 11 Nov 2008 08:03:28 +0000 (UTC) (envelope-from mail25@bzerk.org) Received: from ei.bzerk.org (BOFH@localhost [127.0.0.1]) by ei.bzerk.org (8.14.2/8.14.2) with ESMTP id mAB83M0Q094233; Tue, 11 Nov 2008 09:03:22 +0100 (CET) (envelope-from mail25@bzerk.org) Received: (from bulk@localhost) by ei.bzerk.org (8.14.2/8.14.2/Submit) id mAB83Lmo094232; Tue, 11 Nov 2008 09:03:21 +0100 (CET) (envelope-from mail25@bzerk.org) Date: Tue, 11 Nov 2008 09:03:21 +0100 From: Ruben de Groot To: Eugene Grosbein Message-ID: <20081111080321.GA94210@ei.bzerk.org> Mail-Followup-To: Ruben de Groot , Eugene Grosbein , Stephen Clark , FreeBSD Stable References: <49185ABC.6080004@earthlink.net> <20081110162111.GA26951@svzserv.kemerovo.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081110162111.GA26951@svzserv.kemerovo.su> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-4.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ei.bzerk.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (ei.bzerk.org [127.0.0.1]); Tue, 11 Nov 2008 09:03:25 +0100 (CET) Cc: Stephen Clark , FreeBSD Stable Subject: Re: du and df don't agree X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 08:03:28 -0000 On Mon, Nov 10, 2008 at 11:21:11PM +0700, Eugene Grosbein typed: > On Mon, Nov 10, 2008 at 11:01:00AM -0500, Stephen Clark wrote: > > > Why would du show 630k used by /tmp while df show 161M used > > by /tmp? > > > > I have run fstat /tmp and can't find any files that are using > > the space that df is claiming as being used. > > You need lsof +aL1 /tmp to see an answer. Please don't advise people to install third party apps (lsof) where base system tools (fstat) can do the job. Ruben From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 09:04:57 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0997B1065680 for ; Tue, 11 Nov 2008 09:04:56 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from core.stromnet.se (core.stromnet.se [83.218.84.131]) by mx1.freebsd.org (Postfix) with ESMTP id 7114E8FC30 for ; Tue, 11 Nov 2008 09:04:56 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from localhost (core.stromnet.se [83.218.84.131]) by core.stromnet.se (Postfix) with ESMTP id 34A0C10C738B for ; Tue, 11 Nov 2008 09:49:31 +0100 (CET) X-Virus-Scanned: amavisd-new at stromnet.se X-Spam-Flag: NO X-Spam-Score: -1.112 X-Spam-Level: X-Spam-Status: No, score=-1.112 tagged_above=-1000 required=6.2 tests=[AWL=0.694, BAYES_00=-2.599, RDNS_DYNAMIC=0.1, SPF_FAIL=0.693] Received: from core.stromnet.se ([83.218.84.131]) by localhost (core.stromnet.se [83.218.84.131]) (amavisd-new, port 10024) with ESMTP id Ouf11frR713w for ; Tue, 11 Nov 2008 09:49:29 +0100 (CET) Received: from [172.28.3.6] (78-69-139-60-no129.tbcn.telia.com [78.69.139.60]) by core.stromnet.se (Postfix) with ESMTP id 7770110C738E for ; Tue, 11 Nov 2008 09:49:28 +0100 (CET) Message-Id: <8255ED46-5A67-4A95-AFE7-34F6E8E2388E@stromnet.se> From: =?ISO-8859-1?Q?Johan_Str=F6m?= To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Tue, 11 Nov 2008 09:49:26 +0100 X-Mailer: Apple Mail (2.929.2) Subject: panic in kevent X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 09:04:57 -0000 Hi One of my DL360G5 boxes running 7.0 had a panic this night: jb-2 ~$ uname -rsv FreeBSD 7.0-RELEASE-p4 FreeBSD 7.0-RELEASE-p4 #2: Thu Sep 4 10:49:27 CEST 2008 johan@jb-2:/usr/obj/usr/src/sys/DL360G5 The config is a GENERIC with some pf, IPSEC and ALTQ stuff enabled. jb-2 /usr/obj/usr/src/sys/DL360G5# 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 "amd64-marcel-freebsd". Unread portion of the kernel message buffer: panic: page fault cpuid = 1 Uptime: 40d22h42m5s Physical memory: 10225 MB Dumping 867 MB: 852 836 820 804 788 772 756 740 724 708 692 676 660 644 628 612 596 580 564 548 532 516 500 484 468 452 436 420 404 388 372 356 #0 doadump () at pcpu.h:194 194 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) where #0 doadump () at pcpu.h:194 #1 0x0000000000000004 in ?? () #2 0xffffffff804bb259 in boot (howto=260) at /usr/src/sys/kern/ kern_shutdown.c:409 #3 0xffffffff804bb65d in panic (fmt=0x104
) at /usr/src/sys/kern/kern_shutdown.c:563 #4 0xffffffff8079ec84 in trap_fatal (frame=0xffffff01b33229f0, eva=18446742984664492240) at /usr/src/sys/amd64/amd64/trap.c:724 #5 0xffffffff8079f055 in trap_pfault (frame=0xffffffffb6337780, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:641 #6 0xffffffff8079f998 in trap (frame=0xffffffffb6337780) at /usr/src/ sys/amd64/amd64/trap.c:410 #7 0xffffffff8078560e in calltrap () at /usr/src/sys/amd64/amd64/ exception.S:169 #8 0xffffffff80494b0b in knlist_remove_kq (knl=0xffffff0114407748, kn=0xffffff0054f5fc30, knlislocked=0, kqislocked=0) at /usr/src/sys/kern/kern_event.c:1615 #9 0xffffffff80495f58 in kqueue_register (kq=Variable "kq" is not available. ) at /usr/src/sys/kern/kern_event.c:956 #10 0xffffffff804962f3 in kern_kevent (td=0xffffff01b33229f0, fd=Variable "fd" is not available. ) at /usr/src/sys/kern/kern_event.c:673 #11 0xffffffff80496ca5 in kevent (td=0xffffff01b33229f0, uap=0xffffffffb6337be0) at /usr/src/sys/kern/kern_event.c:594 #12 0xffffffff8079f2d7 in syscall (frame=0xffffffffb6337c70) at /usr/ src/sys/amd64/amd64/trap.c:852 #13 0xffffffff8078581b in Xfast_syscall () at /usr/src/sys/amd64/amd64/ exception.S:290 #14 0x0000000010999ccc in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) Please let me know if I can help with anything else. Is there any way to know which app caused this? I Did some googling with only one or two similar crashes as result, although the hits didn't give much.. I've never had this crash before. Thanks -- Johan From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 09:22:48 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 479BC1065674 for ; Tue, 11 Nov 2008 09:22:48 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (www.tegenbosch28.nl [217.21.251.97]) by mx1.freebsd.org (Postfix) with ESMTP id E6B6A8FC1A for ; Tue, 11 Nov 2008 09:22:47 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from localhost (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id 8011217681; Tue, 11 Nov 2008 10:22:46 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by localhost (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHOMVNIzLeu4; Tue, 11 Nov 2008 10:22:43 +0100 (CET) Received: from [212.61.27.67] (opteron [212.61.27.67]) by mail.digiware.nl (Postfix) with ESMTP id 56684175DF; Tue, 11 Nov 2008 10:22:43 +0100 (CET) Message-ID: <49194EE2.7060708@IMAP> Date: Tue, 11 Nov 2008 10:22:42 +0100 From: Willem Jan Withagen User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: Ruben de Groot , Eugene Grosbein , Stephen Clark , FreeBSD Stable References: <49185ABC.6080004@earthlink.net> <20081110162111.GA26951@svzserv.kemerovo.su> <20081111080321.GA94210@ei.bzerk.org> In-Reply-To: <20081111080321.GA94210@ei.bzerk.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: du and df don't agree X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 09:22:48 -0000 Ruben de Groot wrote: > On Mon, Nov 10, 2008 at 11:21:11PM +0700, Eugene Grosbein typed: >> On Mon, Nov 10, 2008 at 11:01:00AM -0500, Stephen Clark wrote: >> >>> Why would du show 630k used by /tmp while df show 161M used >>> by /tmp? >>> >>> I have run fstat /tmp and can't find any files that are using >>> the space that df is claiming as being used. >> You need lsof +aL1 /tmp to see an answer. > > Please don't advise people to install third party apps (lsof) where > base system tools (fstat) can do the job. Why not? This is one of the ways I pick up on all kinds of nice tools I've not heard of before. And it is not like this is swamping the list with of topic questions. You might have redirected the question to questions@ OTOH: The initial question indicated that fstat did not give the info wanted. Your info does not help, because you told him to use fstat, but forgot to mention HOW. So he is in no way any wiser after your answer. --WjW From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 10:55:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3296E106567F for ; Tue, 11 Nov 2008 10:55:37 +0000 (UTC) (envelope-from mail25@bzerk.org) Received: from ei.bzerk.org (tunnel490.ipv6.xs4all.nl [IPv6:2001:888:10:1ea::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8D0A48FC1C for ; Tue, 11 Nov 2008 10:55:36 +0000 (UTC) (envelope-from mail25@bzerk.org) Received: from ei.bzerk.org (BOFH@localhost [127.0.0.1]) by ei.bzerk.org (8.14.2/8.14.2) with ESMTP id mABAtUPk094826; Tue, 11 Nov 2008 11:55:30 +0100 (CET) (envelope-from mail25@bzerk.org) Received: (from bulk@localhost) by ei.bzerk.org (8.14.2/8.14.2/Submit) id mABAtU0T094825; Tue, 11 Nov 2008 11:55:30 +0100 (CET) (envelope-from mail25@bzerk.org) Date: Tue, 11 Nov 2008 11:55:30 +0100 From: Ruben de Groot To: Willem Jan Withagen Message-ID: <20081111105530.GA94707@ei.bzerk.org> Mail-Followup-To: Ruben de Groot , Willem Jan Withagen , freebsd-stable@freebsd.org References: <49185ABC.6080004@earthlink.net> <20081110162111.GA26951@svzserv.kemerovo.su> <20081111080321.GA94210@ei.bzerk.org> <49194EE2.7060708@IMAP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49194EE2.7060708@IMAP> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ei.bzerk.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (ei.bzerk.org [127.0.0.1]); Tue, 11 Nov 2008 11:55:33 +0100 (CET) Cc: freebsd-stable@freebsd.org Subject: Re: du and df don't agree X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 10:55:37 -0000 On Tue, Nov 11, 2008 at 10:22:42AM +0100, Willem Jan Withagen typed: > Ruben de Groot wrote: > >On Mon, Nov 10, 2008 at 11:21:11PM +0700, Eugene Grosbein typed: > >>On Mon, Nov 10, 2008 at 11:01:00AM -0500, Stephen Clark wrote: > >> > >>>Why would du show 630k used by /tmp while df show 161M used > >>>by /tmp? > >>> > >>>I have run fstat /tmp and can't find any files that are using > >>>the space that df is claiming as being used. > >>You need lsof +aL1 /tmp to see an answer. > > > >Please don't advise people to install third party apps (lsof) where > >base system tools (fstat) can do the job. > > Why not? Because it gives the impression the base system is incomplete, which it is not, at least not in this situation. The wording "you need lsof" is plain wrong. > This is one of the ways I pick up on all kinds of nice tools I've not heard > of before. And it is not like this is swamping the list with of topic > questions. Difference of opinion; I prefer to use FreeBSD tools before falling back to 3rd party tools, no matter how nice. > You might have redirected the question to questions@ I don't see the point. Why didn't you redirect it? > OTOH > The initial question indicated that fstat did not give the info wanted. > Your info does not help, because you told him to use fstat, but forgot to > mention HOW. So he is in no way any wiser after your answer. Yes, my bad. But he allready found the answer himself (using fstat -f I guess). Ruben From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 11:27:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 700AB106568D for ; Tue, 11 Nov 2008 11:27:52 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (www.tegenbosch28.nl [217.21.251.97]) by mx1.freebsd.org (Postfix) with ESMTP id 130E28FC21 for ; Tue, 11 Nov 2008 11:27:52 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from localhost (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id A5FE11769A; Tue, 11 Nov 2008 12:27:50 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by localhost (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6fj3j+5ao37d; Tue, 11 Nov 2008 12:27:47 +0100 (CET) Received: from [212.61.27.67] (opteron [212.61.27.67]) by mail.digiware.nl (Postfix) with ESMTP id 27B2917616; Tue, 11 Nov 2008 12:27:47 +0100 (CET) Message-ID: <49196C32.7000404@IMAP> Date: Tue, 11 Nov 2008 12:27:46 +0100 From: Willem Jan Withagen User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: Ruben de Groot , Willem Jan Withagen , freebsd-stable@freebsd.org References: <49185ABC.6080004@earthlink.net> <20081110162111.GA26951@svzserv.kemerovo.su> <20081111080321.GA94210@ei.bzerk.org> <49194EE2.7060708@IMAP> <20081111105530.GA94707@ei.bzerk.org> In-Reply-To: <20081111105530.GA94707@ei.bzerk.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Discussing non BSD tools on Stable (Was: Re: du and df don't agree) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 11:27:52 -0000 Ruben de Groot wrote: >>>> You need lsof +aL1 /tmp to see an answer. >>> Please don't advise people to install third party apps (lsof) where >>> base system tools (fstat) can do the job. >> Why not? > > Because it gives the impression the base system is incomplete, which it is not, > at least not in this situation. The wording "you need lsof" is plain wrong. Perhaps the wording is chosen to be too strong. But >> This is one of the ways I pick up on all kinds of nice tools I've not heard >> of before. And it is not like this is swamping the list with of topic >> questions. > > Difference of opinion; I prefer to use FreeBSD tools before falling back to > 3rd party tools, no matter how nice. Shure, so do I. But then base and ports are just like one very large candy store, and there are too many tools to know about. >> You might have redirected the question to questions@ > > I don't see the point. Why didn't you redirect it? 1) You made it sound like it is an obvious question with an even more obvious answer. And normally these go to questions@ 2) The reason for this is on the Unix FAQ, not shure it has this answer with it. 3) Because I would not know the answer to the question asked, And what I should have done is change the subject with the previous posting. >> OTOH >> The initial question indicated that fstat did not give the info wanted. >> Your info does not help, because you told him to use fstat, but forgot to >> mention HOW. So he is in no way any wiser after your answer. > > Yes, my bad. But he allready found the answer himself (using fstat -f I guess). You've at least now given me a reason to look at another base tool :) FAIC this is the last we post on this, and get back to using/hacking FreeBSD. --WjW From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 11:28:42 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8D2A106567D for ; Tue, 11 Nov 2008 11:28:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 562FC8FC1B for ; Tue, 11 Nov 2008 11:28:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1KzrQF-000Lrr-Ka; Tue, 11 Nov 2008 13:28:39 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mABBSaMp029008 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Nov 2008 13:28:36 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id mABBSaBZ048584; Tue, 11 Nov 2008 13:28:36 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mABBSZMd048583; Tue, 11 Nov 2008 13:28:35 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 11 Nov 2008 13:28:35 +0200 From: Kostik Belousov To: Johan Str?m Message-ID: <20081111112835.GA47073@deviant.kiev.zoral.com.ua> References: <8255ED46-5A67-4A95-AFE7-34F6E8E2388E@stromnet.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw" Content-Disposition: inline In-Reply-To: <8255ED46-5A67-4A95-AFE7-34F6E8E2388E@stromnet.se> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1KzrQF-000Lrr-Ka 617cedc692349ce83a26671d95fc9e7f X-Terabit: YES Cc: freebsd-stable@freebsd.org Subject: Re: panic in kevent X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 11:28:43 -0000 --GvXjxJ+pjyke8COw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 11, 2008 at 09:49:26AM +0100, Johan Str?m wrote: > Hi > One of my DL360G5 boxes running 7.0 had a panic this night: >=20 > jb-2 ~$ uname -rsv > FreeBSD 7.0-RELEASE-p4 FreeBSD 7.0-RELEASE-p4 #2: Thu Sep 4 10:49:27 =20 > CEST 2008 johan@jb-2:/usr/obj/usr/src/sys/DL360G5 >=20 > The config is a GENERIC with some pf, IPSEC and ALTQ stuff enabled. >=20 > jb-2 /usr/obj/usr/src/sys/DL360G5# kgdb kernel.debug /var/crash/vmcore.0 > [GDB will not be able to debug user-mode threads: /usr/lib/=20 > 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 =20 > you are > welcome to change it and/or distribute copies of it under certain =20 > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for =20 > details. > This GDB was configured as "amd64-marcel-freebsd". >=20 > Unread portion of the kernel message buffer: >=20 > panic: page fault > cpuid =3D 1 > Uptime: 40d22h42m5s > Physical memory: 10225 MB > Dumping 867 MB: 852 836 820 804 788 772 756 740 724 708 692 676 660 =20 > 644 628 612 596 580 564 548 532 516 500 484 468 452 436 420 404 388 =20 > 372 356 >=20 > #0 doadump () at pcpu.h:194 > 194 __asm __volatile("movq %%gs:0,%0" : "=3Dr" (td)); > (kgdb) where > #0 doadump () at pcpu.h:194 > #1 0x0000000000000004 in ?? () > #2 0xffffffff804bb259 in boot (howto=3D260) at /usr/src/sys/kern/=20 > kern_shutdown.c:409 > #3 0xffffffff804bb65d in panic (fmt=3D0x104
bounds>) at /usr/src/sys/kern/kern_shutdown.c:563 > #4 0xffffffff8079ec84 in trap_fatal (frame=3D0xffffff01b33229f0, =20 > eva=3D18446742984664492240) at /usr/src/sys/amd64/amd64/trap.c:724 > #5 0xffffffff8079f055 in trap_pfault (frame=3D0xffffffffb6337780, =20 > usermode=3D0) at /usr/src/sys/amd64/amd64/trap.c:641 > #6 0xffffffff8079f998 in trap (frame=3D0xffffffffb6337780) at /usr/src/= =20 > sys/amd64/amd64/trap.c:410 > #7 0xffffffff8078560e in calltrap () at /usr/src/sys/amd64/amd64/=20 > exception.S:169 > #8 0xffffffff80494b0b in knlist_remove_kq (knl=3D0xffffff0114407748, =20 > kn=3D0xffffff0054f5fc30, knlislocked=3D0, kqislocked=3D0) > at /usr/src/sys/kern/kern_event.c:1615 > #9 0xffffffff80495f58 in kqueue_register (kq=3DVariable "kq" is not =20 > available. > ) at /usr/src/sys/kern/kern_event.c:956 > #10 0xffffffff804962f3 in kern_kevent (td=3D0xffffff01b33229f0, =20 > fd=3DVariable "fd" is not available. > ) at /usr/src/sys/kern/kern_event.c:673 > #11 0xffffffff80496ca5 in kevent (td=3D0xffffff01b33229f0, =20 > uap=3D0xffffffffb6337be0) at /usr/src/sys/kern/kern_event.c:594 > #12 0xffffffff8079f2d7 in syscall (frame=3D0xffffffffb6337c70) at /usr/= =20 > src/sys/amd64/amd64/trap.c:852 > #13 0xffffffff8078581b in Xfast_syscall () at /usr/src/sys/amd64/amd64/= =20 > exception.S:290 > #14 0x0000000010999ccc in ?? () > Previous frame inner to this frame (corrupt stack?) > (kgdb) >=20 >=20 > Please let me know if I can help with anything else. Is there any way =20 > to know which app caused this? > I Did some googling with only one or two similar crashes as result, =20 > although the hits didn't give much.. > I've never had this crash before. There is very high chances that the problem fixed in the 7.1. Unless it is easily reproducable in your settings, there is no easy way to confirm this. You can do "info threads" in the kgdb to overview processes on the crashed system. The thread that was on the CPU during the crash will be marked by star. --GvXjxJ+pjyke8COw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkkZbGMACgkQC3+MBN1Mb4gg1ACgo3TIuNEKKAbwPoOXmKmousAy jgYAoMGLAuCrQh1uf/E+WoXqWSrdUIZ/ =XpRM -----END PGP SIGNATURE----- --GvXjxJ+pjyke8COw-- From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 11:56:33 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA53E106564A for ; Tue, 11 Nov 2008 11:56:33 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from crivens.kernel32.de (crivens.asm68k.org [81.169.171.191]) by mx1.freebsd.org (Postfix) with ESMTP id 70CF98FC0C for ; Tue, 11 Nov 2008 11:56:32 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from www.terrorteam.de (localhost [127.0.0.1]) by crivens.kernel32.de (Postfix) with ESMTP id 5B192B02EF; Tue, 11 Nov 2008 12:37:44 +0100 (CET) MIME-Version: 1.0 Date: Tue, 11 Nov 2008 12:37:44 +0100 From: Marian Hettwer To: Ruben de Groot In-Reply-To: <20081111105530.GA94707@ei.bzerk.org> References: <20081111105530.GA94707@ei.bzerk.org> Message-ID: <91810ad3ecdde97481e5806afd5a5dc7@localhost> X-Sender: mh@kernel32.de User-Agent: RoundCube Webmail/0.1-rc2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: Willem Jan Withagen , freebsd-stable@freebsd.org Subject: Re: du and df don't agree X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 11:56:33 -0000 On Tue, 11 Nov 2008 11:55:30 +0100, Ruben de Groot wrote: > On Tue, Nov 11, 2008 at 10:22:42AM +0100, Willem Jan Withagen typed: >> Ruben de Groot wrote: >> >On Mon, Nov 10, 2008 at 11:21:11PM +0700, Eugene Grosbein typed: >> >>On Mon, Nov 10, 2008 at 11:01:00AM -0500, Stephen Clark wrote: >> >> >> >>>Why would du show 630k used by /tmp while df show 161M used >> >>>by /tmp? >> >>> >> >>>I have run fstat /tmp and can't find any files that are using >> >>>the space that df is claiming as being used. >> >>You need lsof +aL1 /tmp to see an answer. >> > >> >Please don't advise people to install third party apps (lsof) where >> >base system tools (fstat) can do the job. >> >> Why not? > > Because it gives the impression the base system is incomplete, which it is > not, > at least not in this situation. The wording "you need lsof" is plain > wrong. > What about proposing both? As in use fstat from BASE or use lsof from ports. IMO it's good to know that there are several tools which solves your problem. As an example from real world. I love using "sockstat -4" on FreeBSD, but I'm annoyed that it doesn't exist in OpenBSD and it doesn't exist in Debian either. So I'm used to use "netstat -tulpen" on Debian, but that won't work on FreeBSD. Anyway, since I know both ways, I find my way in both systems. Summary: Good to know alternatives. ./Marian From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 13:00:05 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2C3A106567C; Tue, 11 Nov 2008 13:00:05 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9F4658FC23; Tue, 11 Nov 2008 13:00:04 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA26701; Tue, 11 Nov 2008 15:00:01 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <491981D0.7060100@icyb.net.ua> Date: Tue, 11 Nov 2008 15:00:00 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.17 (X11/20081106) MIME-Version: 1.0 To: FreeBSD Stable , freebsd-usb@freebsd.org, freebsd-hackers@freebsd.org References: <4912E462.4090608@icyb.net.ua> In-Reply-To: <4912E462.4090608@icyb.net.ua> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: Re: usb keyboard dying at loader prompt X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 13:00:05 -0000 on 06/11/2008 14:34 Andriy Gapon said the following: > I have a quite strange problem. > This is with 7-BETA amd64. > All of USB is out of kernel and is loaded via modules. > BIOS has "Legacy USB" enabled. > I have only a USB keyboard, no PS/2 port. > > The keyboard works file in BIOS and for selecting boot device in boot0 > menu. It also works in loader menu. If in the menu I select to go to > loader prompt then it works for about 5 seconds and then "dies" - no > reaction to key presses, no led change, nothing. > I haven't actually verified if the keyboard would still work if I stayed > in loader menu for longer than ~10 seconds. > > This doesn't happen if USB is built into kernel. > > Weird... I did more experimentation and the behavior seems to be quite random - sometimes keyboard works ok for long time in all places, sometimes it stops working after some period of time, sometimes it doesn't work from the start and couple of times I experienced boot process going astray. Not sure what stage that was, there were endless messages spewed on the screen very fast, I couldn't read them. This leads me to the following "crazy" question - is it possible that our boot chain corrupts some vital BIOS memory? I think loader would be a primary suspect. I am not sure of anything, but a wild guess is that RAM where BIOS stores some USB-related stuff gets corrupted. Maybe it's overwritten when kernel and modules are loaded... -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 13:14:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5995A106564A; Tue, 11 Nov 2008 13:14:08 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 3D38F8FC25; Tue, 11 Nov 2008 13:14:06 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA27811; Tue, 11 Nov 2008 15:14:03 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4919851B.7050800@icyb.net.ua> Date: Tue, 11 Nov 2008 15:14:03 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.17 (X11/20081106) MIME-Version: 1.0 To: Volker References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> In-Reply-To: <491586B9.2020303@vwsoft.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable , freebsd-usb@freebsd.org Subject: Re: usb keyboard dying at loader prompt X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 13:14:08 -0000 on 08/11/2008 14:31 Volker said the following: > Andriy, > > On 12/23/-58 20:59, Andriy Gapon wrote: >> I have a quite strange problem. >> This is with 7-BETA amd64. > > Did it work with earlier versions? Can't say, this is a new machine, FreeBSD took its virginity :-) >> All of USB is out of kernel and is loaded via modules. >> BIOS has "Legacy USB" enabled. >> I have only a USB keyboard, no PS/2 port. > > Can you check BIOS settings for EHCI handover? No such settings. > If the BIOS does not have handover enabled, it may disable legacy > support after a timeout, which is often bad. IMO this is the same with > booting off USB drives but every BIOS handles that different. This doesn't seem to be the case. The behavior is quite random, sometimes I can work at loader prompt for may minutes, sometimes keyboard is dead after a few seconds. Also, I think USB keyboard is handled by UHCI, not EHCI in my case, but I am not sure if this matters. My guess is that Legacy support should work until OS explicitly takes over by using special procedure (this should be done for UHCI as well). BTW, it seems that our UHCI take-over code is far more simple than what MS described here: http://www.microsoft.com/whdc/archive/usbhost.mspx#EQHAC Anyway, this happens after loader is done. >> The keyboard works file in BIOS and for selecting boot device in boot0 >> menu. It also works in loader menu. If in the menu I select to go to >> loader prompt then it works for about 5 seconds and then "dies" - no >> reaction to key presses, no led change, nothing. >> I haven't actually verified if the keyboard would still work if I stayed >> in loader menu for longer than ~10 seconds. >> >> This doesn't happen if USB is built into kernel. > > That sound strange. I have no idea why that might work (or I'm totally > wrong with my handover theory). I was incorrect about the above, I have already seen it happening both ways. >> Weird... > > Yes, sounds like or it's probably easily explainable ;) -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 14:16:41 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BA8D106567E for ; Tue, 11 Nov 2008 14:16:41 +0000 (UTC) (envelope-from ken73.chen@gmail.com) Received: from hs-out-0708.google.com (hs-out-0708.google.com [64.233.178.244]) by mx1.freebsd.org (Postfix) with ESMTP id B31868FC17 for ; Tue, 11 Nov 2008 14:16:40 +0000 (UTC) (envelope-from ken73.chen@gmail.com) Received: by hs-out-0708.google.com with SMTP id 54so1248593hsz.11 for ; Tue, 11 Nov 2008 06:16:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=ZtmCv+RnPw8fOVHNT0+1/ezsIFjxtMu87CRbZkm/MeE=; b=mv4wZPyMaHan8/r+mLSIMMhK1ZsScqFiC+0QYcL6EiSVUcMFKoInnkRmAkUlmuTeZG 1gAiIifx9P/ipqHENZqLTh0ZTc/cx4pB4nuJCPuxC6zFvGfkBiyCTwacUdXpvfb8uu3X 8l6acmTB2WXjYbrTIVF5EpFx6ufkm+99FtYq8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=eosli9kcCek2s0xjrSM3tR7wLAyiFWpL5xxEUn06EQxWDFw+AbYSA+r4UWwMs/gW7m lWvYDhMTZgKzIqccWTYV3IQdoDH21r2zIjVrlLqTAIzG1i4ymc7W3P2NT+eQeII1J+TU SsajQZ8HiQFqc1F6pgjkcYa4YqfRqc8E6ddk0= Received: by 10.142.50.5 with SMTP id x5mr2301144wfx.330.1226412578354; Tue, 11 Nov 2008 06:09:38 -0800 (PST) Received: by 10.142.232.19 with HTTP; Tue, 11 Nov 2008 06:09:38 -0800 (PST) Message-ID: Date: Tue, 11 Nov 2008 22:09:38 +0800 From: "Ken Chen" To: stable@freebsd.org In-Reply-To: <4917285C.2030702@lozenetz.org> MIME-Version: 1.0 References: <20081107142137.GA7051@icarus.home.lan> <4917285C.2030702@lozenetz.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: php-cgi frozen with sbwait when SMP enable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 14:16:41 -0000 I think the parent php-cgi are very health. I have tried: There are total 49 php-cgi processes are running or frozen, the '1 wait' is parent . web4# ps alx | grep php-cgi | grep -v grep | awk '{print $9}' | sort | uniq -c | sort -n 1 biowr 1 wait 15 sbwait 32 accept Kill one of frozen php-cgi processes. web4# kill -9 61392 Check again the amount of php-cgi processes, there are still 49 php-cgi procerss. web4# ps alx | grep php-cgi | grep -v grep | awk '{print $9}' | sort | uniq -c | sort -n 1 biord 1 bo_wwa 1 wait 4 - 17 sbwait 25 accept 2008/11/10 Anton - Valqk > Oh, just saw that, this could be caused by dead parent php-cgi processes > (just a guess). > I used to run lighttpd with span-fcgi executable and it happens very > often to have dead parents (of php-cgi childs) that must be killed by > killall php-cgi (eg. restart _ALL_ php-cgi processes, pretty stupid!!! > but if you have dead parent you can't know which childs to kill)... > If you run your php-cgi processes just from the lighttpd(and lighttpd > manages php-cgi processes) try running it with fcgi-spawn and write a > script to check parents of the php-cgi backends and you'll see if that's > the cause of having 'hang' phps :( > > pls tell me what is it. I'm interested! > > cheers, > valqk. > Ken Chen wrote: > > Hi Jeremy, > > > > A health FastCGI process have a lifetime, so the PIDs of all php-cgi > > processes should in a short range. > > > > There are some 'php-cgi' fall in 'sbwait' state, and stay there forever. > The > > frozen 'php-cgi' can't accept new request, so never retire. > > > > Please forgive my poor English. > > > > 2008/11/7 Jeremy Chadwick > > > > > >> On Fri, Nov 07, 2008 at 07:29:37PM +0800, Ken Chen wrote: > >> > >>> Hello, > >>> > >>> I have 4 web servers with lighttpd to serve one web site with DNS load > >>> sharing. On the 2 SMP-enable web servers, there will be many php-cgi > >>> > >> frozen > >> > >>> in 'sbwait' state every day. It means the php-cgi stay in 'sbwait' > state, > >>> and never be back to 'accept' or other state. If I restart them, there > >>> > >> will > >> > >>> be frozen php-cgi appear some hours later. > >>> > >>> There is no problem on the other single CPU web servers which running > >>> > >> same > >> > >>> php scripts and same configuration and version of PHP. > >>> > >>> Why and any solution? > >>> > >> I'm not understanding what the problem is (and I've seen the output you > >> provided later in the thread). Are you stating the problem is that you > >> see many php-cgi processes? Or are you worried they're not doing > >> anything? Does the website function, lock up, or anything like that? > >> If not, what's the issue? :-) > >> > >> -- > >> | Jeremy Chadwick jdc at 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-unsubscribe@freebsd.org > " > > > > > > From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 14:36:38 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27332106567E for ; Tue, 11 Nov 2008 14:36:38 +0000 (UTC) (envelope-from ken73.chen@gmail.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.185]) by mx1.freebsd.org (Postfix) with ESMTP id AE8FB8FC2F for ; Tue, 11 Nov 2008 14:36:37 +0000 (UTC) (envelope-from ken73.chen@gmail.com) Received: by rn-out-0910.google.com with SMTP id j71so2184197rne.12 for ; Tue, 11 Nov 2008 06:36:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=Z4QYby6jixbMjAjjHqejrpQWva7ZBfK0gKxaPKZDLnk=; b=mFcHILl909ARLe+aVe7VsThpDpTFZrzghoxDhqQzW7z+08fFw+yHEnNBNbeNJLQEjy H22WRifB1KSVLGUMw7H15Y1FG98vB2aBGf9kJRhkLLtTCvEQWEX9P6DfvHaScfgw53GA gQ/x9qYiRHa/QjIAuo5GkksQcrgKqA3K0DKWQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=SvHewqAwjGMJoZ+3MCzdii6RNcJ3lQ7SKCcPjRdHaDPB+BmlRfnAAhcDjA24pCsxpk xnhg/wlOLrJi9Ri5yaxd+Sz6C459PVucvlfXv5hjNgFeVzKYKAS48WV6lZ7uq00BKRKh pCxXFCAotLwBVdg3lH0/hptI0AeWwtHNp+Ync= Received: by 10.142.251.15 with SMTP id y15mr2986750wfh.126.1226412357409; Tue, 11 Nov 2008 06:05:57 -0800 (PST) Received: by 10.142.232.19 with HTTP; Tue, 11 Nov 2008 06:05:57 -0800 (PST) Message-ID: Date: Tue, 11 Nov 2008 22:05:57 +0800 From: "Ken Chen" To: stable@freebsd.org In-Reply-To: <491726F4.4040808@lozenetz.org> MIME-Version: 1.0 References: <491726F4.4040808@lozenetz.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: php-cgi frozen with sbwait when SMP enable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 14:36:38 -0000 The report from lighttpd looks fine: cache.cached-itmes: 98293 cache.hitrate(%): 96 cache.memory-inuse(KB): 6143 fastcgi.active-requests: 16 fastcgi.backend.0.0.connected: 419008 fastcgi.backend.0.0.died: 0 fastcgi.backend.0.0.disabled: 0 fastcgi.backend.0.0.load: 16 fastcgi.backend.0.0.overloaded: 0 fastcgi.backend.0.load: 17 fastcgi.requests: 419008 But at this moment: web4# ps alx | grep php-cgi | grep -v grep | awk '{print $9}' | sort | uniq -c | sort -n 1 biord 1 wait 2 - 16 sbwait 29 accept web4# ps alx | grep php-cgi | grep -v grep | grep sbwait 65534 61392 61384 1 4 -15 182328 69312 sbwait I< ?? 0:53.39 /usr/local/bin/php-cgi 65534 61399 61384 0 4 -15 182328 71112 sbwait I< ?? 1:09.60 /usr/local/bin/php-cgi 65534 61409 61384 0 4 -15 182328 72812 sbwait I< ?? 1:39.40 /usr/local/bin/php-cgi 65534 61411 61384 0 4 -15 183352 74536 sbwait I< ?? 1:49.08 /usr/local/bin/php-cgi 65534 61412 61384 0 4 -15 183352 74508 sbwait I< ?? 1:33.31 /usr/local/bin/php-cgi 65534 61414 61384 0 4 -15 182328 62860 sbwait I< ?? 0:28.81 /usr/local/bin/php-cgi 65534 61418 61384 0 4 -15 182328 71448 sbwait I< ?? 1:17.56 /usr/local/bin/php-cgi 65534 61426 61384 0 4 -15 183352 60456 sbwait I< ?? 0:22.16 /usr/local/bin/php-cgi 65534 71529 61384 0 4 -15 182328 74144 sbwait I< ?? 0:36.87 /usr/local/bin/php-cgi 65534 71555 61384 0 4 -15 182328 72820 sbwait I< ?? 0:19.19 /usr/local/bin/php-cgi 65534 71556 61384 0 4 -15 182328 74452 sbwait I< ?? 0:38.27 /usr/local/bin/php-cgi 65534 71590 61384 0 4 -15 182328 76828 sbwait I< ?? 0:57.42 /usr/local/bin/php-cgi 65534 71594 61384 0 4 -15 182328 75576 sbwait I< ?? 0:46.50 /usr/local/bin/php-cgi 65534 71595 61384 0 4 -15 182328 84048 sbwait I< ?? 1:52.15 /usr/local/bin/php-cgi 65534 77285 61384 0 4 -15 182328 88280 sbwait S< ?? 0:15.22 /usr/local/bin/php-cgi 65534 77288 61384 3 4 -15 182328 88808 sbwait S< ?? 0:14.43 /usr/local/bin/php-cgi 65534 77317 61384 0 4 -15 182328 88912 sbwait S< ?? 0:12.79 /usr/local/bin/php-cgi 65534 77323 61384 0 4 -15 182328 89140 sbwait S< ?? 0:13.51 /usr/local/bin/php-cgi 65534 77359 61384 6 4 -15 182328 88200 sbwait S< ?? 0:13.04 /usr/local/bin/php-cgi 65534 77372 61384 2 4 -15 182328 89200 sbwait S< ?? 0:12.16 /usr/local/bin/php-cgi 65534 77392 61384 1 4 -15 181304 87200 sbwait S< ?? 0:11.02 /usr/local/bin/php-cgi 65534 77401 61384 1 4 -15 182328 88800 sbwait S< ?? 0:12.49 /usr/local/bin/php-cgi The PID of php-cgi which are less than 71595 are frozen. 2008/11/10 Anton - Valqk > You can try taking look to lighttpd status and fcgi processes status > like this: > server.modules += ( "mod_status" ) > status.status-url = "/server-status" > status.statistics-url = "/sstatus1" > > status.statistics-url gives info for each fastcgi like this: > > fastcgi.active-requests: 0 > fastcgi.backend.backend1.0.connected: 12493970 > fastcgi.backend.backend1.0.died: 0 > fastcgi.backend.backend1.0.disabled: 0 > fastcgi.backend.backend1.0.load: 0 > fastcgi.backend.backend1.0.overloaded: 0 > fastcgi.backend.backend1.load: 1 > fastcgi.requests: 19479062 > > > etc... read what each means on lighttpd site... > pls tell what caused this, it'd be very interesting to me! > > cheers, > valqk. > > Ken Chen wrote: > > I capture something. > > > > Please check the PID 57776. It's CPU time never change since my previous > > mail here. > > > > web4# ps alx | grep php-cgi | grep -v grep | grep sbwait > > 65534 57776 47240 0 4 0 182328 84984 sbwait I ?? 2:02.12 > > /usr/local/bin/php-cgi > > 65534 57801 47240 0 4 0 182328 82408 sbwait I ?? 0:19.97 > > /usr/local/bin/php-cgi > > 65534 57809 47240 0 4 0 182328 84096 sbwait I ?? 1:12.03 > > /usr/local/bin/php-cgi > > 65534 57823 47240 0 4 0 182328 84492 sbwait I ?? 2:04.21 > > /usr/local/bin/php-cgi > > 65534 57833 47240 0 4 0 183352 83316 sbwait I ?? 0:28.62 > > /usr/local/bin/php-cgi > > 65534 57866 47240 0 4 0 182328 79952 sbwait I ?? 0:05.92 > > /usr/local/bin/php-cgi > > 65534 57870 47240 0 4 0 182328 83184 sbwait I ?? 0:56.83 > > /usr/local/bin/php-cgi > > 65534 57871 47240 0 4 0 182328 83388 sbwait I ?? 0:54.96 > > /usr/local/bin/php-cgi > > 65534 57891 47240 0 4 0 182328 84436 sbwait I ?? 1:58.32 > > /usr/local/bin/php-cgi > > 65534 57925 47240 0 4 0 182328 84380 sbwait I ?? 2:03.53 > > /usr/local/bin/php-cgi > > 65534 65944 47240 0 4 0 182328 84184 sbwait I ?? 0:39.97 > > /usr/local/bin/php-cgi > > 65534 65952 47240 0 4 0 182328 84408 sbwait I ?? 0:21.37 > > /usr/local/bin/php-cgi > > 65534 66007 47240 0 4 0 183352 90960 sbwait I ?? 1:16.81 > > /usr/local/bin/php-cgi > > 65534 66014 47240 5 4 0 182328 92748 sbwait S ?? 1:41.23 > > /usr/local/bin/php-cgi > > 65534 66038 47240 1 4 0 182328 91900 sbwait I ?? 1:38.04 > > /usr/local/bin/php-cgi > > 65534 66060 47240 0 4 0 182328 90048 sbwait I ?? 1:15.46 > > /usr/local/bin/php-cgi > > 65534 66078 47240 3 4 0 182328 92224 sbwait S ?? 1:39.66 > > /usr/local/bin/php-cgi > > web4# top -b > > last pid: 70768; load averages: 1.62, 1.65, 1.43 up 4+15:56:06 > > 22:53:48 > > 85 processes: 1 running, 84 sleeping > > > > Mem: 492M Active, 1204M Inact, 218M Wired, 60M Cache, 112M Buf, 27M Free > > Swap: 2019M Total, 20K Used, 2019M Free > > > > > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > > 69544 nobody 1 8 0 203M 38500K nanslp 1 6:31 11.33% php > > 47290 nobody 1 4 0 101M 98M kqread 1 30:42 2.98% > lighttpd > > 66526 nobody 1 4 0 178M 92796K accept 1 1:40 1.12% php-cgi > > 66077 nobody 1 4 0 178M 92512K accept 0 1:49 1.07% php-cgi > > 65921 nobody 1 4 0 178M 92696K accept 0 1:43 0.98% php-cgi > > 65968 nobody 1 4 0 178M 92484K accept 0 1:43 0.93% php-cgi > > 66017 nobody 1 4 0 178M 92444K accept 0 1:50 0.88% php-cgi > > 65979 nobody 1 4 0 178M 92676K accept 1 1:44 0.88% php-cgi > > 66424 nobody 1 4 0 178M 92928K accept 1 1:36 0.88% php-cgi > > 65938 nobody 1 4 0 178M 92336K accept 1 1:52 0.73% php-cgi > > 65951 nobody 1 4 0 178M 92704K accept 0 1:48 0.73% php-cgi > > 66016 nobody 1 4 0 178M 92232K accept 1 1:41 0.73% php-cgi > > 65950 nobody 1 4 0 178M 93192K accept 0 1:51 0.68% php-cgi > > 65999 nobody 1 4 0 178M 92940K accept 1 1:46 0.63% php-cgi > > 66008 nobody 1 4 0 178M 93000K accept 1 1:46 0.63% php-cgi > > 69286 nobody 1 4 0 178M 92208K accept 1 0:37 0.63% php-cgi > > 47289 nobody 1 4 0 73400K 70640K kqread 1 12:02 0.59% > lighttpd > > 65980 nobody 1 4 0 178M 93156K accept 1 1:51 0.59% php-cgi > > 2008/11/7 Ivan Voras > > > > > >> Ken Chen wrote: > >> > >>> Oh.. sorry, I forgot to provide the information of my environment. > >>> > >>> web4# php-cgi -v > >>> PHP 5.2.6 (cgi-fcgi) (built: Nov 2 2008 11:16:30) > >>> Copyright (c) 1997-2008 The PHP Group > >>> Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies > >>> with XCache v1.2.2, Copyright (c) 2005-2007, by mOo > >>> web4# /usr/local/lighttpd/sbin/lighttpd -v > >>> lighttpd-1.4.19 - a light and fast webserver > >>> Build-Date: Sep 1 2008 16:58:51 > >>> web4# uname -a > >>> FreeBSD web4.xxxx.com 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #11: Mon > Nov > >>> > >> 3 > >> > >>> 01:10:36 CST 2008 root@web4.xxxx.com:/usr/obj/usr/src/sys/WEB4 > i386 > >>> web4# ps alx | grep php-cgi | grep -v grep | grep sbwait > >>> 65534 57776 47240 0 4 0 182328 84984 sbwait I ?? 2:02.12 > >>> /usr/local/bin/php-cgi > >>> 65534 57801 47240 0 4 0 182328 82408 sbwait I ?? 0:19.97 > >>> /usr/local/bin/php-cgi > >>> 65534 57809 47240 0 4 0 182328 84096 sbwait I ?? 1:12.03 > >>> /usr/local/bin/php-cgi > >>> 65534 57823 47240 0 4 0 182328 84492 sbwait I ?? 2:04.21 > >>> /usr/local/bin/php-cgi > >>> 65534 57833 47240 0 4 0 183352 83316 sbwait I ?? 0:28.62 > >>> /usr/local/bin/php-cgi > >>> 65534 57866 47240 0 4 0 182328 79952 sbwait I ?? 0:05.92 > >>> /usr/local/bin/php-cgi > >>> 65534 57870 47240 0 4 0 182328 83184 sbwait I ?? 0:56.83 > >>> /usr/local/bin/php-cgi > >>> 65534 57871 47240 0 4 0 182328 83388 sbwait I ?? 0:54.96 > >>> /usr/local/bin/php-cgi > >>> 65534 57891 47240 0 4 0 182328 84436 sbwait I ?? 1:58.32 > >>> /usr/local/bin/php-cgi > >>> 65534 57925 47240 0 4 0 182328 84380 sbwait I ?? 2:03.53 > >>> /usr/local/bin/php-cgi > >>> 65534 65944 47240 0 4 0 182328 84184 sbwait I ?? 0:39.97 > >>> /usr/local/bin/php-cgi > >>> 65534 65952 47240 0 4 0 182328 84408 sbwait I ?? 0:21.37 > >>> /usr/local/bin/php-cgi > >>> > >> This does seem a bit unusual, but seeing that your execution times are > >> not null it might that the PHP servers are actually doing some useful > >> work. You should have a mixture of various states in PHP - do they show > >> up in top? > >> > >> My own example is: > >> > >> last pid: 77421; load averages: 2.82, 2.59, 2.13 > >> up > >> 55+16:58:49 15:48:16 > >> 209 processes: 2 running, 206 sleeping, 1 zombie > >> CPU: 49.8% user, 0.0% nice, 2.8% system, 0.0% interrupt, 47.4% idle > >> Mem: 1493M Active, 1583M Inact, 278M Wired, 139M Cache, 112M Buf, 505M > Free > >> Swap: 4500M Total, 416M Used, 4084M Free, 9% Inuse > >> > >> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > >> 75863 www 1 4 0 162M 50020K sbwait 3 2:54 36.77% > php-cgi > >> 76830 www 1 103 0 156M 41556K CPU2 3 1:28 36.77% > php-cgi > >> 76834 www 1 4 0 163M 56628K sbwait 0 2:23 33.59% > php-cgi > >> 76019 www 1 4 0 150M 38948K accept 3 3:12 20.56% > php-cgi > >> 76825 www 1 4 0 158M 42912K accept 2 1:21 18.16% > php-cgi > >> 76846 www 1 4 0 162M 42600K sbwait 1 1:07 14.36% > php-cgi > >> 76835 www 1 4 0 151M 39948K accept 2 1:28 12.60% > php-cgi > >> 76829 www 1 4 0 150M 36564K sbwait 2 1:46 2.98% > php-cgi > >> > >> This is unusually high load, a spike, for this server but it has many > >> cores and it's stable. It's also running 7.1-PRERELEASE. > >> > >> > >> > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org > " > > > > > > From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 15:07:04 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 457891065677 for ; Tue, 11 Nov 2008 15:07:04 +0000 (UTC) (envelope-from eksffa@freebsdbrasil.com.br) Received: from capeta.freebsdbrasil.com.br (capeta.freebsdbrasil.com.br [201.48.151.3]) by mx1.freebsd.org (Postfix) with SMTP id 1B5408FC17 for ; Tue, 11 Nov 2008 15:07:01 +0000 (UTC) (envelope-from eksffa@freebsdbrasil.com.br) Received: (qmail 98342 invoked from network); 11 Nov 2008 13:06:58 -0200 Received: by simscan 1.1.0 ppid: 98335, pid: 98336, t: 0.5153s scanners: clamav: 0.91.1/m: spam: 3.1.1 X-Spam-Checker-Version: SpamAssassin: -last, FreeBSD Brasil LTDA rulesets: Yes X-Spam-Status: No, hits=-1.9 required=3.7 Received: from unknown (HELO claire.bh.freebsdbrasil.com.br) (201.48.151.226) by capeta.freebsdbrasil.com.br with SMTP; 11 Nov 2008 13:06:57 -0200 Message-ID: <49199F76.5010800@freebsdbrasil.com.br> Date: Tue, 11 Nov 2008 13:06:30 -0200 From: Patrick Tracanelli Organization: FreeBSD Brasil LTDA User-Agent: Thunderbird 2.0.0.0 (X11/20070612) MIME-Version: 1.0 To: releng@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: MFC Request X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 15:07:04 -0000 Is it possible to have traceroute MFC'd for 7.1? I would like to have -a and -A switchs (ASN Path mapping) available. Thank you :) -- Patrick Tracanelli From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 16:05:28 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F45B106568E for ; Tue, 11 Nov 2008 16:05:28 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by mx1.freebsd.org (Postfix) with ESMTP id 0E5208FC12 for ; Tue, 11 Nov 2008 16:05:27 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA05.westchester.pa.mail.comcast.net ([76.96.62.43]) by QMTA06.westchester.pa.mail.comcast.net with comcast id dq7G1a00Z0vyq2s56s4jSB; Tue, 11 Nov 2008 16:04:43 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA05.westchester.pa.mail.comcast.net with comcast id ds5S1a00A2P6wsM3Rs5S5t; Tue, 11 Nov 2008 16:05:27 +0000 X-Authority-Analysis: v=1.0 c=1 a=WbCbx-liFbYA:10 a=tm_ATurd3F8A:10 a=QycZ5dHgAAAA:8 a=5Lo5nXYUeS24fa4D2bEA:9 a=kWjQ6Glm_3ZwQYpQUV0yJPr8KGQA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 35F9B5C19; Tue, 11 Nov 2008 08:05:26 -0800 (PST) Date: Tue, 11 Nov 2008 08:05:26 -0800 From: Jeremy Chadwick To: Ken Chen Message-ID: <20081111160526.GA1608@icarus.home.lan> References: <20081107142137.GA7051@icarus.home.lan> <4917285C.2030702@lozenetz.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: stable@freebsd.org Subject: Re: php-cgi frozen with sbwait when SMP enable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 16:05:28 -0000 On Tue, Nov 11, 2008 at 10:09:38PM +0800, Ken Chen wrote: > I think the parent php-cgi are very health. I have tried: > > There are total 49 php-cgi processes are running or frozen, the '1 wait' is > parent . > > web4# ps alx | grep php-cgi | grep -v grep | awk '{print $9}' | sort | uniq > -c | sort -n > 1 biowr > 1 wait > 15 sbwait > 32 accept > > Kill one of frozen php-cgi processes. > > web4# kill -9 61392 > > Check again the amount of php-cgi processes, there are still 49 php-cgi > procerss. > > web4# ps alx | grep php-cgi | grep -v grep | awk '{print $9}' | sort | uniq > -c | sort -n > 1 biord > 1 bo_wwa > 1 wait > 4 - > 17 sbwait > 25 accept I would recommend you try the lighttpd and fastcgi mailing lists at this point. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 17:03:09 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B3D61065686 for ; Tue, 11 Nov 2008 17:03:09 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) by mx1.freebsd.org (Postfix) with ESMTP id 3C5328FC1A for ; Tue, 11 Nov 2008 17:03:08 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from Internal Mail-Server by mx01 (envelope-from bseklecki@collaborativefusion.com) with SMTP; 11 Nov 2008 11:36:27 -0500 From: "Brian A. Seklecki" To: Patrick Tracanelli In-Reply-To: <49199F76.5010800@freebsdbrasil.com.br> References: <49199F76.5010800@freebsdbrasil.com.br> Content-Type: text/plain Organization: Collaborative Fusion, Inc. Date: Tue, 11 Nov 2008 11:36:26 -0500 Message-Id: <1226421386.27892.45.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9) Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, releng@freebsd.org Subject: Re: MFC Request X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bseklecki@collaborativefusion.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 17:03:09 -0000 On Tue, 2008-11-11 at 13:06 -0200, Patrick Tracanelli wrote: > Is it possible to have traceroute MFC'd for 7.1? I would like to have -a I second that request. I'm prepared to bribe someone as well. ~BAS > and -A switchs (ASN Path mapping) available. Thank you :) > -- Brian A. Seklecki Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 18:55:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDD301065672 for ; Tue, 11 Nov 2008 18:55:46 +0000 (UTC) (envelope-from peter@wemm.org) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id A923B8FC29 for ; Tue, 11 Nov 2008 18:55:46 +0000 (UTC) (envelope-from peter@wemm.org) Received: by yw-out-2324.google.com with SMTP id 9so19356ywe.13 for ; Tue, 11 Nov 2008 10:55:46 -0800 (PST) Received: by 10.142.163.13 with SMTP id l13mr3103833wfe.91.1226429745370; Tue, 11 Nov 2008 10:55:45 -0800 (PST) Received: by 10.142.255.21 with HTTP; Tue, 11 Nov 2008 10:55:45 -0800 (PST) Message-ID: Date: Tue, 11 Nov 2008 10:55:45 -0800 From: "Peter Wemm" To: "Andriy Gapon" In-Reply-To: <4919851B.7050800@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> Cc: Volker , FreeBSD Stable , freebsd-usb@freebsd.org Subject: Re: usb keyboard dying at loader prompt X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 18:55:47 -0000 On Tue, Nov 11, 2008 at 5:14 AM, Andriy Gapon wrote: > on 08/11/2008 14:31 Volker said the following: >> Andriy, >> >> On 12/23/-58 20:59, Andriy Gapon wrote: >>> I have a quite strange problem. >>> This is with 7-BETA amd64. >> >> Did it work with earlier versions? > > Can't say, this is a new machine, FreeBSD took its virginity :-) > >>> All of USB is out of kernel and is loaded via modules. >>> BIOS has "Legacy USB" enabled. >>> I have only a USB keyboard, no PS/2 port. >> >> Can you check BIOS settings for EHCI handover? > > No such settings. > >> If the BIOS does not have handover enabled, it may disable legacy >> support after a timeout, which is often bad. IMO this is the same with >> booting off USB drives but every BIOS handles that different. > > This doesn't seem to be the case. The behavior is quite random, > sometimes I can work at loader prompt for may minutes, sometimes > keyboard is dead after a few seconds. > Also, I think USB keyboard is handled by UHCI, not EHCI in my case, but > I am not sure if this matters. My guess is that Legacy support should > work until OS explicitly takes over by using special procedure (this > should be done for UHCI as well). > > BTW, it seems that our UHCI take-over code is far more simple than what > MS described here: > http://www.microsoft.com/whdc/archive/usbhost.mspx#EQHAC > > Anyway, this happens after loader is done. > >>> The keyboard works file in BIOS and for selecting boot device in boot0 >>> menu. It also works in loader menu. If in the menu I select to go to >>> loader prompt then it works for about 5 seconds and then "dies" - no >>> reaction to key presses, no led change, nothing. >>> I haven't actually verified if the keyboard would still work if I stayed >>> in loader menu for longer than ~10 seconds. >>> >>> This doesn't happen if USB is built into kernel. >> >> That sound strange. I have no idea why that might work (or I'm totally >> wrong with my handover theory). > > I was incorrect about the above, I have already seen it happening both ways. > >>> Weird... >> >> Yes, sounds like or it's probably easily explainable ;) > > > -- > Andriy Gapon > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Some bioses have a list of MBR partition id's and use that to determine what to do with the USB keyboard. One of my ol older amd64 motherboards worked but would always disable the usb keyboard right as loader started. I discovered the following: * If I put the freebsd bootblocks and loader on a floppy drive (no MBR), then the bios did not turn off the keyboard. It always continued to work for loader. * If i hacked the boot bootblocks and loader and kernel to recognize different MBR slice id nubmers as "ours", then changing the freebsd MBR to be "msdos" or "linux" also worked for that BIOS. It would no longer turn off the USB keyboard. I don't recall which Id number I used instead of 165 - it was about 4 years ago. * There were other consequences of using the partition ID hack - I think I remember it turning off the apic for msdos mode. Your problems may be different, but mine were caused by a BIOS whitelist of MBR partition id's. What a stupid problem. On that motherboard I ended up taking the path of least resistance and using the PS/2 adapter plug on the keyboard. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 19:14:07 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FFBC1065676 for ; Tue, 11 Nov 2008 19:14:07 +0000 (UTC) (envelope-from ken73.chen@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id D29BD8FC12 for ; Tue, 11 Nov 2008 19:14:06 +0000 (UTC) (envelope-from ken73.chen@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so23906yxb.13 for ; Tue, 11 Nov 2008 11:14:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=6ErAmUpFBF2tWi571HQUH2pCgoydbpS496kXZK841q0=; b=VUnjv71JFKzSAEn7hV9MjiqtLY0f8Ybh2CRk1rni+KOsFkvJlDSghI/G6bVBRcYDM7 1s//d5X0JhbkH1paBSH4RYKR0d8/elY9VDkSte0AuYHxDAO0AREqMYfQLX7yG17FhFlE 9qzD+TmUfKPeUlgi6mTsX764sPLXj4YGqtE9c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=vkAr7317QC4RowhnITiNw6owqOSZKYaRErYsY11hdRU33RkMiJdAi/1KNDtlAX8ZE7 UXB3qRIrnb+m2FCnUiiZRJXCPJInOsnCw5lWRK8iCCjPZTj5miuIJ60rL6boYSg8/QRs F/M350JnUylLve/dAfbfH1xcFeXllNHsZXyYw= Received: by 10.142.14.18 with SMTP id 18mr3109072wfn.35.1226430845477; Tue, 11 Nov 2008 11:14:05 -0800 (PST) Received: by 10.142.232.19 with HTTP; Tue, 11 Nov 2008 11:14:05 -0800 (PST) Message-ID: Date: Wed, 12 Nov 2008 03:14:05 +0800 From: "Ken Chen" To: stable@freebsd.org In-Reply-To: <20081111160526.GA1608@icarus.home.lan> MIME-Version: 1.0 References: <20081107142137.GA7051@icarus.home.lan> <4917285C.2030702@lozenetz.org> <20081111160526.GA1608@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: php-cgi frozen with sbwait when SMP enable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 19:14:07 -0000 Thank Jeremy, I will try. 2008/11/12 Jeremy Chadwick > On Tue, Nov 11, 2008 at 10:09:38PM +0800, Ken Chen wrote: > > I think the parent php-cgi are very health. I have tried: > > > > There are total 49 php-cgi processes are running or frozen, the '1 wait' > is > > parent . > > > > web4# ps alx | grep php-cgi | grep -v grep | awk '{print $9}' | sort | > uniq > > -c | sort -n > > 1 biowr > > 1 wait > > 15 sbwait > > 32 accept > > > > Kill one of frozen php-cgi processes. > > > > web4# kill -9 61392 > > > > Check again the amount of php-cgi processes, there are still 49 php-cgi > > procerss. > > > > web4# ps alx | grep php-cgi | grep -v grep | awk '{print $9}' | sort | > uniq > > -c | sort -n > > 1 biord > > 1 bo_wwa > > 1 wait > > 4 - > > 17 sbwait > > 25 accept > > I would recommend you try the lighttpd and fastcgi mailing lists at this > point. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 19:14:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D382F106564A for ; Tue, 11 Nov 2008 19:14:13 +0000 (UTC) (envelope-from geoff.sweet@x10.com) Received: from officesmtp.x10.com (officesmtp.x10.com [63.211.211.254]) by mx1.freebsd.org (Postfix) with ESMTP id B456D8FC1D for ; Tue, 11 Nov 2008 19:14:13 +0000 (UTC) (envelope-from geoff.sweet@x10.com) Received: from [192.168.11.201] (user201.x10wti.com [63.211.211.201]) by officesmtp.x10.com (8.13.4/8.13.4) with ESMTP id mABIj3i0098211 for ; Tue, 11 Nov 2008 10:45:05 -0800 (PST) From: Geoff Sweet To: freebsd-stable@freebsd.org Content-Type: text/plain Date: Tue, 11 Nov 2008 10:45:04 -0800 Message-Id: <1226429104.8047.5.camel@gsweet-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit Subject: /usr/local/etc/rc.d getting run twice X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 19:14:13 -0000 Greetings, I have new freshly installed servers of FreeBSD 6.3. We started our migration before 6.4 was released. Anyway we have some custom tools that we have built startup scripts for and placed them into /usr/local/etc/rc.d. However the problem is that these tools get called twice to startup. Thus leaving us with two instances of the tools running. I've read a thread similar to this question in the mailing list archive however it had to do with upgrading and didn't seem to apply to my issue. I've added a buch of logic to the script to try to determine if the tool is running or not, but that seems like band aiding the issue instead of fixing the problem. Any advice? -Geoff Sweet From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 19:54:32 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D42C1065672 for ; Tue, 11 Nov 2008 19:54:32 +0000 (UTC) (envelope-from geoff.sweet@x10.com) Received: from officesmtp.x10.com (officesmtp.x10.com [63.211.211.254]) by mx1.freebsd.org (Postfix) with ESMTP id 1248E8FC1F for ; Tue, 11 Nov 2008 19:54:31 +0000 (UTC) (envelope-from geoff.sweet@x10.com) Received: from [192.168.11.201] (user201.x10wti.com [63.211.211.201]) by officesmtp.x10.com (8.13.4/8.13.4) with ESMTP id mABJsGea001600; Tue, 11 Nov 2008 11:54:16 -0800 (PST) From: Geoff Sweet To: David Wolfskill In-Reply-To: <20081111192153.GI69155@bunrab.catwhisker.org> References: <1226429104.8047.5.camel@gsweet-laptop> <20081111192153.GI69155@bunrab.catwhisker.org> Content-Type: text/plain Date: Tue, 11 Nov 2008 11:54:17 -0800 Message-Id: <1226433257.8047.11.camel@gsweet-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: /usr/local/etc/rc.d getting run twice X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 19:54:32 -0000 Ah, indeed that seems to be the problem. Thank you, I may never have spotted that on my own. -Geoff Sweet On Tue, 2008-11-11 at 11:21 -0800, David Wolfskill wrote: > On Tue, Nov 11, 2008 at 10:45:04AM -0800, Geoff Sweet wrote: > > Greetings, I have new freshly installed servers of FreeBSD 6.3.... > > Any advice? > > Check the value of local_startup in /etc/{defaults/,}rc.conf. > > In 6.3, I believe the default was > > /usr/local/etc/rc.d /usr/X11R6/etc/rc.d > > but you may find that /usr/X11R6 has become a symlink to /usr/local > (after upgrading X11). > > If it is, you can avoid the problem by placing > > local_startup="/usr/local/etc/rc.d" > > in /etc/rc.conf. > > Peace, > david From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 19:56:22 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B24E1065670 for ; Tue, 11 Nov 2008 19:56:22 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.freebsd.org (Postfix) with ESMTP id DE1978FC1E for ; Tue, 11 Nov 2008 19:56:21 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id mABJLsu5073222; Tue, 11 Nov 2008 11:21:54 -0800 (PST) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id mABJLsQ1073221; Tue, 11 Nov 2008 11:21:54 -0800 (PST) (envelope-from david) Date: Tue, 11 Nov 2008 11:21:53 -0800 From: David Wolfskill To: Geoff Sweet Message-ID: <20081111192153.GI69155@bunrab.catwhisker.org> Mail-Followup-To: David Wolfskill , Geoff Sweet , freebsd-stable@freebsd.org References: <1226429104.8047.5.camel@gsweet-laptop> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9j2ELPqTsVbCO5A+" Content-Disposition: inline In-Reply-To: <1226429104.8047.5.camel@gsweet-laptop> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: /usr/local/etc/rc.d getting run twice X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 19:56:22 -0000 --9j2ELPqTsVbCO5A+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 11, 2008 at 10:45:04AM -0800, Geoff Sweet wrote: > Greetings, I have new freshly installed servers of FreeBSD 6.3.... > Any advice? Check the value of local_startup in /etc/{defaults/,}rc.conf. In 6.3, I believe the default was /usr/local/etc/rc.d /usr/X11R6/etc/rc.d but you may find that /usr/X11R6 has become a symlink to /usr/local (after upgrading X11). If it is, you can avoid the problem by placing local_startup=3D"/usr/local/etc/rc.d" in /etc/rc.conf. Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --9j2ELPqTsVbCO5A+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAkkZ21EACgkQmprOCmdXAD0//QCghT1VQKzlwpDwSkl9RyQJCKj8 lz0Amwftck5NxhTRxihj7JxLkddUXvCO =A9p7 -----END PGP SIGNATURE----- --9j2ELPqTsVbCO5A+-- From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 20:09:22 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CCB41065687; Tue, 11 Nov 2008 20:09:22 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id CE6B98FC16; Tue, 11 Nov 2008 20:09:21 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (Q7c04.q.ppp-pool.de [89.53.124.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 4444512883F; Tue, 11 Nov 2008 21:09:13 +0100 (CET) Received: from cesar.sz.vwsoft.com (unknown [192.168.18.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 10D892E90F; Tue, 11 Nov 2008 21:09:01 +0100 (CET) Message-ID: <4919E65C.1020307@vwsoft.com> Date: Tue, 11 Nov 2008 21:09:00 +0100 From: Volker User-Agent: Thunderbird 2.0.0.17 (X11/20080930) MIME-Version: 1.0 To: Peter Wemm References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> In-Reply-To: X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit MailScanner-NULL-Check: 1227038950.56887@G4VEviIoOmG1eOJz+zaa0A X-MailScanner-ID: 10D892E90F.AF67A X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: FreeBSD Stable , Andriy Gapon , freebsd-usb@freebsd.org Subject: Re: usb keyboard dying at loader prompt X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 20:09:22 -0000 On 11/11/08 19:55, Peter Wemm wrote: > ... > * There were other consequences of using the partition ID hack - I > think I remember it turning off the apic for msdos mode. > > Your problems may be different, but mine were caused by a BIOS > whitelist of MBR partition id's. What a stupid problem. On that > motherboard I ended up taking the path of least resistance and using > the PS/2 adapter plug on the keyboard. Peter, very interesting what you've found. That reminds me on some investigations I did as I was hunting USB boot device problems. Some BIOSes do not check the partition (slice) ID but are looking for a file system magic. If a FAT filesystem is detected, the BIOS does some stupid things (like ignoring the active partition flag and booting the FAT slice no matter what you've flagged active). Just an example and off-topic to Andriy's keyboard problem. But when combining that with your findings, it may still be a thing to check for... ;) Volker From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 20:11:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A24E1065670 for ; Tue, 11 Nov 2008 20:11:10 +0000 (UTC) (envelope-from stuartb@4gh.net) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 2D9D98FC0A for ; Tue, 11 Nov 2008 20:11:10 +0000 (UTC) (envelope-from stuartb@4gh.net) Received: from mr08.lnh.mail.rcn.net ([207.172.157.28]) by smtp02.lnh.mail.rcn.net with ESMTP; 11 Nov 2008 14:42:17 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr08.lnh.mail.rcn.net (MOS 3.10.3-GA) with ESMTP id KLC76556; Tue, 11 Nov 2008 14:42:15 -0500 (EST) Received: from 216-15-63-54.c3-0.slvr-ubr2.lnh-slvr.md.cable.rcn.com (HELO freeman.4gh.net) ([216.15.63.54]) by smtp01.lnh.mail.rcn.net with ESMTP; 11 Nov 2008 14:42:12 -0500 Received: by freeman.4gh.net (Postfix, from userid 1001) id A60345C5C1; Tue, 11 Nov 2008 14:42:10 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by freeman.4gh.net (Postfix) with ESMTP id 947CE5C292; Tue, 11 Nov 2008 14:42:10 -0500 (EST) Date: Tue, 11 Nov 2008 14:42:10 -0500 (EST) From: Stuart Barkley To: Geoff Sweet In-Reply-To: <1226429104.8047.5.camel@gsweet-laptop> Message-ID: References: <1226429104.8047.5.camel@gsweet-laptop> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: /usr/local/etc/rc.d getting run twice X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 20:11:10 -0000 On Tue, 11 Nov 2008 at 13:45 -0000, Geoff Sweet wrote: > Greetings, I have new freshly installed servers of FreeBSD 6.3. We > started our migration before 6.4 was released. Anyway we have some > custom tools that we have built startup scripts for and placed them > into /usr/local/etc/rc.d. However the problem is that these tools get > called twice to startup. Thus leaving us with two instances of the > tools running. You probably need the following line added to /etc/rc.conf: local_startup="/usr/local/etc/rc.d" The defaults in /etc/defaults/rc.conf still try to run startup scripts in /usr/local/etc/rc.d and /usr/X11R6/etc/rc.d, however these are probably the same location via a /usr/X11R6 link. One of the X ports attempts to add this, but I've seen cases where it doesn't get added. Stuart -- I've never been lost; I was once bewildered for three days, but never lost! -- Daniel Boone From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 20:23:40 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0012106567D for ; Tue, 11 Nov 2008 20:23:40 +0000 (UTC) (envelope-from peter@wemm.org) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by mx1.freebsd.org (Postfix) with ESMTP id 9597C8FC14 for ; Tue, 11 Nov 2008 20:23:40 +0000 (UTC) (envelope-from peter@wemm.org) Received: by wf-out-1314.google.com with SMTP id 24so58849wfg.7 for ; Tue, 11 Nov 2008 12:23:40 -0800 (PST) Received: by 10.142.224.5 with SMTP id w5mr3133011wfg.243.1226435020244; Tue, 11 Nov 2008 12:23:40 -0800 (PST) Received: by 10.142.255.21 with HTTP; Tue, 11 Nov 2008 12:23:40 -0800 (PST) Message-ID: Date: Tue, 11 Nov 2008 12:23:40 -0800 From: "Peter Wemm" To: Volker In-Reply-To: <4919E65C.1020307@vwsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> <4919E65C.1020307@vwsoft.com> Cc: FreeBSD Stable , Andriy Gapon , freebsd-usb@freebsd.org Subject: Re: usb keyboard dying at loader prompt X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 20:23:40 -0000 On Tue, Nov 11, 2008 at 12:09 PM, Volker wrote: > On 11/11/08 19:55, Peter Wemm wrote: >> ... >> * There were other consequences of using the partition ID hack - I >> think I remember it turning off the apic for msdos mode. >> >> Your problems may be different, but mine were caused by a BIOS >> whitelist of MBR partition id's. What a stupid problem. On that >> motherboard I ended up taking the path of least resistance and using >> the PS/2 adapter plug on the keyboard. > > Peter, > > very interesting what you've found. That reminds me on some > investigations I did as I was hunting USB boot device problems. > > Some BIOSes do not check the partition (slice) ID but are looking for a > file system magic. If a FAT filesystem is detected, the BIOS does some > stupid things (like ignoring the active partition flag and booting the > FAT slice no matter what you've flagged active). Just an example and > off-topic to Andriy's keyboard problem. > > But when combining that with your findings, it may still be a thing to > check for... ;) > > Volker I have long since stopped being surprised by what bios writers come up with. Or should I say "windows boot loader" instead of bios, because that is what it seems to have degenerated into these days. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 20:24:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABB67106567B for ; Tue, 11 Nov 2008 20:24:29 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by mx1.freebsd.org (Postfix) with ESMTP id B956A8FC24 for ; Tue, 11 Nov 2008 20:24:28 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36]) by QMTA08.westchester.pa.mail.comcast.net with comcast id dnt61a00C0mv7h058wPunh; Tue, 11 Nov 2008 20:23:54 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA11.westchester.pa.mail.comcast.net with comcast id dwQR1a00C2P6wsM3XwQR3C; Tue, 11 Nov 2008 20:24:27 +0000 X-Authority-Analysis: v=1.0 c=1 a=ux2eErHcXjUA:10 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=EhV_xG62G5wHDkLL7u4A:9 a=W_ovRdUTjs7m23KX8My7FA9f9c4A:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 563A45C1A; Tue, 11 Nov 2008 12:24:25 -0800 (PST) Date: Tue, 11 Nov 2008 12:24:25 -0800 From: Jeremy Chadwick To: Volker Message-ID: <20081111202425.GA6568@icarus.home.lan> References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> <4919E65C.1020307@vwsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4919E65C.1020307@vwsoft.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-usb@freebsd.org, FreeBSD Stable , Andriy Gapon , Peter Wemm Subject: Re: usb keyboard dying at loader prompt X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 20:24:29 -0000 On Tue, Nov 11, 2008 at 09:09:00PM +0100, Volker wrote: > On 11/11/08 19:55, Peter Wemm wrote: > > ... > > * There were other consequences of using the partition ID hack - I > > think I remember it turning off the apic for msdos mode. > > > > Your problems may be different, but mine were caused by a BIOS > > whitelist of MBR partition id's. What a stupid problem. On that > > motherboard I ended up taking the path of least resistance and using > > the PS/2 adapter plug on the keyboard. > > Peter, > > very interesting what you've found. That reminds me on some > investigations I did as I was hunting USB boot device problems. > > Some BIOSes do not check the partition (slice) ID but are looking for a > file system magic. If a FAT filesystem is detected, the BIOS does some > stupid things (like ignoring the active partition flag and booting the > FAT slice no matter what you've flagged active). Just an example and > off-topic to Andriy's keyboard problem. > > But when combining that with your findings, it may still be a thing to > check for... ;) Since you folks in this thread have some pretty good experience with BIOS behaviour and bootloader/filesystem stuff, could I ask that someone take a look at something I posted at over on -fs? I'm out of ideas at this point. http://lists.freebsd.org/pipermail/freebsd-fs/2008-November/005317.html Danke! -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 21:00:48 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CAF2106568A; Tue, 11 Nov 2008 21:00:48 +0000 (UTC) (envelope-from nakal@web.de) Received: from fmmailgate01.web.de (fmmailgate01.web.de [217.72.192.221]) by mx1.freebsd.org (Postfix) with ESMTP id E3E8A8FC18; Tue, 11 Nov 2008 21:00:47 +0000 (UTC) (envelope-from nakal@web.de) Received: from smtp07.web.de (fmsmtp07.dlan.cinetic.de [172.20.5.215]) by fmmailgate01.web.de (Postfix) with ESMTP id ECB28F96F254; Tue, 11 Nov 2008 21:33:46 +0100 (CET) Received: from [217.236.9.131] (helo=zelda.local) by smtp07.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1Kzzvm-0005QB-00; Tue, 11 Nov 2008 21:33:46 +0100 Date: Tue, 11 Nov 2008 21:33:44 +0100 From: Martin To: "Peter Wemm" Message-ID: <20081111213344.6657548c@zelda.local> In-Reply-To: References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> X-Mailer: Claws Mail 3.6.0 (GTK+ 2.12.11; amd64-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX1+MIlryiMd49qvoDAw0q5qimWGrbUdPEsXNWBbq ZsqLht5+H1qaAvxwzd8o/DeOQrhticyJk5rmlQRhOzkbptBPlO c8QvlwJPI= Cc: Volker , freebsd-usb@freebsd.org, Stable , Andriy Gapon , FreeBSD Subject: Re: usb keyboard dying at loader prompt X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2008 21:00:48 -0000 Am Tue, 11 Nov 2008 10:55:45 -0800 schrieb "Peter Wemm" : > Some bioses have a list of MBR partition id's and use that to > determine what to do with the USB keyboard. One of my ol older amd64 > motherboards worked but would always disable the usb keyboard right as > loader started. I discovered the following: > * If I put the freebsd bootblocks and loader on a floppy drive (no > MBR), then the bios did not turn off the keyboard. It always > continued to work for loader. > * If i hacked the boot bootblocks and loader and kernel to recognize > different MBR slice id nubmers as "ours", then changing the freebsd > MBR to be "msdos" or "linux" also worked for that BIOS. It would no > longer turn off the USB keyboard. I don't recall which Id number I > used instead of 165 - it was about 4 years ago. > * There were other consequences of using the partition ID hack - I > think I remember it turning off the apic for msdos mode. > > Your problems may be different, but mine were caused by a BIOS > whitelist of MBR partition id's. What a stupid problem. On that > motherboard I ended up taking the path of least resistance and using > the PS/2 adapter plug on the keyboard. Hello, I want to add some information about USB problems which occur for me very frequently. I have found out that most of the problems are related to Gigabyte mainboards. I have 2 of them now. One is "EP35C-DS3R". With this mainboard sometimes my USB keyboard and USB mouse stop working (the power is simply off). I can reattach them and they both power up again. The second mainboard is "EP45-DS3R". Here the problem is even worse. The keyboard and mouse (both USB) lose power as soon as FreeBSD scans the USB controllers. Here, I can also reattach the devices and they are usable again. One further hint: it seems Vista (64 bit version) has the same problem with this EP45-DS3R mainboard. After it boots into the login screen, I have to reattach the devices to use them. The mainboard is not broken, I have tried 3 so far and all have these strange effects. And now... I want to remind you that I have already posted here about (same) USB problems on my laptop (Lenovo Thinkpad T60p). Sometimes I have to reattach my keyboard there, too. Of course, this is not Gigabyte here, but the weird behaviour ressembles the one above. -- Martin From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 10:06:35 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D38281065687 for ; Wed, 12 Nov 2008 10:06:35 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id 5F3E58FC25 for ; Wed, 12 Nov 2008 10:06:35 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so265486nfh.33 for ; Wed, 12 Nov 2008 02:06:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=rqIW+ivaUfSTkt9r7UPj/RvB/i09ETs7Dj+PHG3016s=; b=LxYIgY167JYzV53SScocLuqV/LSP33c5+c97HdVP4qLVmNL7tgK/zkykh62zsMYi0Y Sk2T5h37kPn56NiaAZl3dwRWNVHOjDl43EcarodYP+Dg29N1l9t6a8wBlLWCsuXOHE3Q OvnV07ijFq78vxojnEO3E1cYWZwr8+08nV8kI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=J9f1oaFO2zMM5aNuU0XeF6veaxihLVWKlBp73HaKnotyncJyk2REQRukaqfTVzetde gkahCZXosiJa8nuAyOywDprH2Pl4nuCyLK6MObvHV20p4Xot1ECtqsUS1WnqNRwJBDrV t1/wBmcEGWAx7ToFmUSTpS2+fK3po2Je495bY= Received: by 10.210.130.14 with SMTP id c14mr8214233ebd.190.1226482579428; Wed, 12 Nov 2008 01:36:19 -0800 (PST) Received: by 10.210.38.6 with HTTP; Wed, 12 Nov 2008 01:36:19 -0800 (PST) Message-ID: Date: Wed, 12 Nov 2008 12:36:19 +0300 From: pluknet To: Martin In-Reply-To: <20081111213344.6657548c@zelda.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> <20081111213344.6657548c@zelda.local> Cc: Volker , Stable , freebsd-usb@freebsd.org, Peter Wemm , Andriy Gapon Subject: Re: usb keyboard dying at loader prompt X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 10:06:36 -0000 2008/11/11 Martin : > Am Tue, 11 Nov 2008 10:55:45 -0800 > schrieb "Peter Wemm" : > >> Some bioses have a list of MBR partition id's and use that to >> determine what to do with the USB keyboard. One of my ol older amd64 >> motherboards worked but would always disable the usb keyboard right as >> loader started. I discovered the following: >> * If I put the freebsd bootblocks and loader on a floppy drive (no >> MBR), then the bios did not turn off the keyboard. It always >> continued to work for loader. >> * If i hacked the boot bootblocks and loader and kernel to recognize >> different MBR slice id nubmers as "ours", then changing the freebsd >> MBR to be "msdos" or "linux" also worked for that BIOS. It would no >> longer turn off the USB keyboard. I don't recall which Id number I >> used instead of 165 - it was about 4 years ago. >> * There were other consequences of using the partition ID hack - I >> think I remember it turning off the apic for msdos mode. >> >> Your problems may be different, but mine were caused by a BIOS >> whitelist of MBR partition id's. What a stupid problem. On that >> motherboard I ended up taking the path of least resistance and using >> the PS/2 adapter plug on the keyboard. > > Hello, > > I want to add some information about USB problems which occur for me > very frequently. > > I have found out that most of the problems are related to Gigabyte > mainboards. I have 2 of them now. One is "EP35C-DS3R". With this > mainboard sometimes my USB keyboard and USB mouse stop working (the > power is simply off). I can reattach them and they both power up again. > > The second mainboard is "EP45-DS3R". Here the problem is even worse. > The keyboard and mouse (both USB) lose power as soon as FreeBSD scans > the USB controllers. Here, I can also reattach the devices and they are > usable again. > > One further hint: it seems Vista (64 bit version) has the same problem > with this EP45-DS3R mainboard. After it boots into the login screen, I > have to reattach the devices to use them. The mainboard is not broken, > I have tried 3 so far and all have these strange effects. > > > And now... I want to remind you that I have already posted here about > (same) USB problems on my laptop (Lenovo Thinkpad T60p). Sometimes I > have to reattach my keyboard there, too. Of course, this is not > Gigabyte here, but the weird behaviour ressembles the one above. I have the same problem with my ukbd&ums: they are power off'ed during the boot and I should to re-attach them . MB: Asus p5k. -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 11:29:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B30831065688; Wed, 12 Nov 2008 11:29:18 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A5F268FC0A; Wed, 12 Nov 2008 11:29:17 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA15544; Wed, 12 Nov 2008 13:29:10 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <491ABE05.5080809@icyb.net.ua> Date: Wed, 12 Nov 2008 13:29:09 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.17 (X11/20081106) MIME-Version: 1.0 To: Peter Wemm References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Volker , FreeBSD Stable , freebsd-usb@freebsd.org Subject: Re: usb keyboard dying at loader prompt X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 11:29:18 -0000 on 11/11/2008 20:55 Peter Wemm said the following: > Some bioses have a list of MBR partition id's and use that to > determine what to do with the USB keyboard. One of my ol older amd64 > motherboards worked but would always disable the usb keyboard right as > loader started. I discovered the following: > * If I put the freebsd bootblocks and loader on a floppy drive (no > MBR), then the bios did not turn off the keyboard. It always > continued to work for loader. > * If i hacked the boot bootblocks and loader and kernel to recognize > different MBR slice id nubmers as "ours", then changing the freebsd > MBR to be "msdos" or "linux" also worked for that BIOS. It would no > longer turn off the USB keyboard. I don't recall which Id number I > used instead of 165 - it was about 4 years ago. > * There were other consequences of using the partition ID hack - I > think I remember it turning off the apic for msdos mode. > > Your problems may be different, but mine were caused by a BIOS > whitelist of MBR partition id's. What a stupid problem. On that > motherboard I ended up taking the path of least resistance and using > the PS/2 adapter plug on the keyboard. Foul play on BIOS part is definitely a big possibility. What puzzles me most is random/inconsistent behavior from boot to boot. Maybe there is some misalignment between how BIOS emulates legacy keyboard and how our boot chain interacts with it, some timing issue or something. Anyway, this is very hard to debug or guess. Most probably I will have to live with it (this system doesn't have PS/2 ports at all). -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 11:36:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 076D91065672; Wed, 12 Nov 2008 11:36:50 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 359878FC12; Wed, 12 Nov 2008 11:36:47 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA15684; Wed, 12 Nov 2008 13:36:46 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <491ABFCD.3060309@icyb.net.ua> Date: Wed, 12 Nov 2008 13:36:45 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.17 (X11/20081106) MIME-Version: 1.0 To: FreeBSD Stable , freebsd-hackers@freebsd.org, freebsd-usb@freebsd.org References: <4911BA93.9030006@icyb.net.ua> In-Reply-To: <4911BA93.9030006@icyb.net.ua> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: Re: ukbd attachment and root mount X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 11:36:50 -0000 on 05/11/2008 17:24 Andriy Gapon said the following: > System is FreeBSD 7.1-BETA2 amd64. > > Looking through my dmesg I see that relative order of ukbd attachment > and root mounting is not deterministic. Sometime keyboard is attached > first, sometimes root filesystem is mounted first. Quite more often root > is mounted first, though. > Example (with GENERIC kernel): > Nov 3 15:40:54 kernel: Trying to mount root from ufs:/dev/mirror/bootgm > Nov 3 15:40:54 kernel: GEOM_LABEL: Label ufs/bootfs removed. > Nov 3 15:40:54 kernel: GEOM_LABEL: Label for provider mirror/bootgm is > ufs/bootfs. > Nov 3 15:40:54 kernel: GEOM_LABEL: Label ufs/bootfs removed. > Nov 3 15:40:54 kernel: ukbd0: 1.10/1.10, addr 3> on uhub2 > Nov 3 15:40:54 kernel: kbd2 at ukbd0 > Nov 3 15:40:54 kernel: uhid0: 1.10/1.10, addr 3> on uhub2 > > Another (with custom kernel, zfs root): > Nov 4 17:54:03 odyssey kernel: Trying to mount root from zfs:tank/root > Nov 4 17:54:03 odyssey kernel: ukbd0: rev 1.10/1.10, addr 3> on uhub2 > Nov 4 17:54:03 odyssey kernel: kbd2 at ukbd0 > Nov 4 17:54:03 odyssey kernel: kbd2: ukbd0, generic (0), config:0x0, > flags:0x3d0000 > Nov 4 17:54:03 odyssey kernel: uhid0: rev 1.10/1.10, addr 3> on uhub2 > > I have a legacy-free system (no PS/2 ports, only USB) and I wanted to > try a kernel without atkbd and psm (with ums, ukbd, kbdmux), but was > bitten hard when I made a mistake and kernel could not find/mount root > filesystem. > > So I stuck at mountroot prompt without a keyboard to enter anything. > This was repeatable about 10 times after which I resorted to live cd. > > Since then I put back atkbdc into my kernel. I guess BIOS or USB > hardware emulate AT or PS/2 keyboard, so the USB keyboard works before > the driver attaches. I guess I need such emulation e.g. for loader or > boot0 configuration. But I guess I don't have to have atkbd driver in > kernel. This turned out not to be a complete solution as it seems that there are some quirks about legacy USB here, sometimes keyboard stops working even at loader prompt (this is described in a different thread). ukbd attachment still puzzles me a lot. I look at some older dmesg, e.g. this 7.0-RELEASE one: http://www.mavetju.org/mail/view_message.php?list=freebsd-usb&id=2709973 and see that ukbd attaches along with ums before mountroot. I look at newer dmesg and I see that ums attaches at about the same time as before but ukbd consistently attaches after mountroot. I wonder what might cause such behavior and how to fix it. I definitely would like to see ukbd attach before mountroot, I can debug this issue, but need some hints on where to start. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 12:00:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66551106579B; Wed, 12 Nov 2008 12:00:21 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 070258FC1E; Wed, 12 Nov 2008 12:00:19 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA16104; Wed, 12 Nov 2008 13:58:59 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <491AC502.9000507@icyb.net.ua> Date: Wed, 12 Nov 2008 13:58:58 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.17 (X11/20081106) MIME-Version: 1.0 To: Nate Eldredge References: <4911BA93.9030006@icyb.net.ua> <491ABFCD.3060309@icyb.net.ua> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, FreeBSD Stable , freebsd-usb@freebsd.org Subject: Re: ukbd attachment and root mount X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 12:00:21 -0000 on 12/11/2008 13:53 Nate Eldredge said the following: > On Wed, 12 Nov 2008, Andriy Gapon wrote: > >> on 05/11/2008 17:24 Andriy Gapon said the following: > [...] >>> I have a legacy-free system (no PS/2 ports, only USB) and I wanted to >>> try a kernel without atkbd and psm (with ums, ukbd, kbdmux), but was >>> bitten hard when I made a mistake and kernel could not find/mount root >>> filesystem. >>> >>> So I stuck at mountroot prompt without a keyboard to enter anything. >>> This was repeatable about 10 times after which I resorted to live cd. >>> >>> Since then I put back atkbdc into my kernel. I guess BIOS or USB >>> hardware emulate AT or PS/2 keyboard, so the USB keyboard works before >>> the driver attaches. I guess I need such emulation e.g. for loader or >>> boot0 configuration. But I guess I don't have to have atkbd driver in >>> kernel. >> >> This turned out not to be a complete solution as it seems that there are >> some quirks about legacy USB here, sometimes keyboard stops working even >> at loader prompt (this is described in a different thread). >> >> ukbd attachment still puzzles me a lot. >> I look at some older dmesg, e.g. this 7.0-RELEASE one: >> http://www.mavetju.org/mail/view_message.php?list=freebsd-usb&id=2709973 >> and see that ukbd attaches along with ums before mountroot. >> >> I look at newer dmesg and I see that ums attaches at about the same time >> as before but ukbd consistently attaches after mountroot. >> I wonder what might cause such behavior and how to fix it. >> I definitely would like to see ukbd attach before mountroot, I can debug >> this issue, but need some hints on where to start. > > I haven't been following this thread, and I'm pretty sleepy right now, > so sorry if this is irrelevant, but I had a somewhat similar problem > that was fixed by adding > > hint.atkbd.0.flags="0x1" > > to /boot/device.hints . > I can try this, but I think this wouldn't help for two reasons: 1. I already tried kernel without atkb at all 2. if ukbd driver is not attached then I don't see any way USB keyboard would work in non-legacy way Anyway I will try this, thank you. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 12:14:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E63D5106567B for ; Wed, 12 Nov 2008 12:14:11 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by mx1.freebsd.org (Postfix) with ESMTP id CE8898FC12 for ; Wed, 12 Nov 2008 12:14:11 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by QMTA01.emeryville.ca.mail.comcast.net with comcast id eBPA1a00D0EPchoA1CEBga; Wed, 12 Nov 2008 12:14:11 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA01.emeryville.ca.mail.comcast.net with comcast id eCEA1a0042P6wsM8MCEAlr; Wed, 12 Nov 2008 12:14:11 +0000 X-Authority-Analysis: v=1.0 c=1 a=aarVl-9CAAAA:8 a=QycZ5dHgAAAA:8 a=HTTBBloA31bZZr2vb6AA:9 a=JxNATzhhykdpcfkF6iVXLfSzFeMA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 6B14E5C1A; Wed, 12 Nov 2008 04:14:10 -0800 (PST) Date: Wed, 12 Nov 2008 04:14:10 -0800 From: Jeremy Chadwick To: Andriy Gapon Message-ID: <20081112121410.GA24629@icarus.home.lan> References: <4911BA93.9030006@icyb.net.ua> <491ABFCD.3060309@icyb.net.ua> <491AC502.9000507@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <491AC502.9000507@icyb.net.ua> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Nate Eldredge , freebsd-hackers@freebsd.org, FreeBSD Stable , freebsd-usb@freebsd.org Subject: Re: ukbd attachment and root mount X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 12:14:12 -0000 On Wed, Nov 12, 2008 at 01:58:58PM +0200, Andriy Gapon wrote: > on 12/11/2008 13:53 Nate Eldredge said the following: > > On Wed, 12 Nov 2008, Andriy Gapon wrote: > > > >> on 05/11/2008 17:24 Andriy Gapon said the following: > > [...] > >>> I have a legacy-free system (no PS/2 ports, only USB) and I wanted to > >>> try a kernel without atkbd and psm (with ums, ukbd, kbdmux), but was > >>> bitten hard when I made a mistake and kernel could not find/mount root > >>> filesystem. > >>> > >>> So I stuck at mountroot prompt without a keyboard to enter anything. > >>> This was repeatable about 10 times after which I resorted to live cd. > >>> > >>> Since then I put back atkbdc into my kernel. I guess BIOS or USB > >>> hardware emulate AT or PS/2 keyboard, so the USB keyboard works before > >>> the driver attaches. I guess I need such emulation e.g. for loader or > >>> boot0 configuration. But I guess I don't have to have atkbd driver in > >>> kernel. > >> > >> This turned out not to be a complete solution as it seems that there are > >> some quirks about legacy USB here, sometimes keyboard stops working even > >> at loader prompt (this is described in a different thread). > >> > >> ukbd attachment still puzzles me a lot. > >> I look at some older dmesg, e.g. this 7.0-RELEASE one: > >> http://www.mavetju.org/mail/view_message.php?list=freebsd-usb&id=2709973 > >> and see that ukbd attaches along with ums before mountroot. > >> > >> I look at newer dmesg and I see that ums attaches at about the same time > >> as before but ukbd consistently attaches after mountroot. > >> I wonder what might cause such behavior and how to fix it. > >> I definitely would like to see ukbd attach before mountroot, I can debug > >> this issue, but need some hints on where to start. > > > > I haven't been following this thread, and I'm pretty sleepy right now, > > so sorry if this is irrelevant, but I had a somewhat similar problem > > that was fixed by adding > > > > hint.atkbd.0.flags="0x1" > > > > to /boot/device.hints . To those reading, the above setting enables the following option: bit 0 (FAIL_IF_NO_KBD) By default the atkbd driver will install even if a keyboard is not actually connected to the system. This option prevents the driver from being installed in this situation. > I can try this, but I think this wouldn't help for two reasons: > 1. I already tried kernel without atkb at all > 2. if ukbd driver is not attached then I don't see any way USB keyboard > would work in non-legacy way Regarding #2: at which stage? boot0/boot2/loader require an AT or PS/2 keyboard to work. None of these stages use ukbd(4) or anything -- there is no kernel loaded at this point!! Meaning: if you have a USB keyboard, your BIOS will need to have a "USB Legacy" option to cause it to act as a PS/2 keyboard, for typing in boot0/boot2/loader to work. Device hints are for kernel drivers, once the kernel is loaded. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 12:18:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D98DC1065678; Wed, 12 Nov 2008 12:18:36 +0000 (UTC) (envelope-from neldredge@math.ucsd.edu) Received: from euclid.ucsd.edu (euclid.ucsd.edu [132.239.145.52]) by mx1.freebsd.org (Postfix) with ESMTP id B9CD28FC12; Wed, 12 Nov 2008 12:18:36 +0000 (UTC) (envelope-from neldredge@math.ucsd.edu) Received: from zeno.ucsd.edu (zeno.ucsd.edu [132.239.145.22]) by euclid.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id mACBrp611316; Wed, 12 Nov 2008 03:53:51 -0800 (PST) Received: from localhost (neldredg@localhost) by zeno.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id mACBrpl17181; Wed, 12 Nov 2008 03:53:51 -0800 (PST) X-Authentication-Warning: zeno.ucsd.edu: neldredg owned process doing -bs Date: Wed, 12 Nov 2008 03:53:51 -0800 (PST) From: Nate Eldredge X-X-Sender: neldredg@zeno.ucsd.edu To: Andriy Gapon In-Reply-To: <491ABFCD.3060309@icyb.net.ua> Message-ID: References: <4911BA93.9030006@icyb.net.ua> <491ABFCD.3060309@icyb.net.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, FreeBSD Stable , freebsd-usb@freebsd.org Subject: Re: ukbd attachment and root mount X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 12:18:37 -0000 On Wed, 12 Nov 2008, Andriy Gapon wrote: > on 05/11/2008 17:24 Andriy Gapon said the following: [...] >> I have a legacy-free system (no PS/2 ports, only USB) and I wanted to >> try a kernel without atkbd and psm (with ums, ukbd, kbdmux), but was >> bitten hard when I made a mistake and kernel could not find/mount root >> filesystem. >> >> So I stuck at mountroot prompt without a keyboard to enter anything. >> This was repeatable about 10 times after which I resorted to live cd. >> >> Since then I put back atkbdc into my kernel. I guess BIOS or USB >> hardware emulate AT or PS/2 keyboard, so the USB keyboard works before >> the driver attaches. I guess I need such emulation e.g. for loader or >> boot0 configuration. But I guess I don't have to have atkbd driver in >> kernel. > > This turned out not to be a complete solution as it seems that there are > some quirks about legacy USB here, sometimes keyboard stops working even > at loader prompt (this is described in a different thread). > > ukbd attachment still puzzles me a lot. > I look at some older dmesg, e.g. this 7.0-RELEASE one: > http://www.mavetju.org/mail/view_message.php?list=freebsd-usb&id=2709973 > and see that ukbd attaches along with ums before mountroot. > > I look at newer dmesg and I see that ums attaches at about the same time > as before but ukbd consistently attaches after mountroot. > I wonder what might cause such behavior and how to fix it. > I definitely would like to see ukbd attach before mountroot, I can debug > this issue, but need some hints on where to start. I haven't been following this thread, and I'm pretty sleepy right now, so sorry if this is irrelevant, but I had a somewhat similar problem that was fixed by adding hint.atkbd.0.flags="0x1" to /boot/device.hints . -- Nate Eldredge neldredge@math.ucsd.edu From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 12:20:46 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 083F91065679; Wed, 12 Nov 2008 12:20:46 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6F5388FC08; Wed, 12 Nov 2008 12:20:44 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA16630; Wed, 12 Nov 2008 14:20:42 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <491ACA19.2040008@icyb.net.ua> Date: Wed, 12 Nov 2008 14:20:41 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.17 (X11/20081106) MIME-Version: 1.0 To: Jeremy Chadwick References: <4911BA93.9030006@icyb.net.ua> <491ABFCD.3060309@icyb.net.ua> <491AC502.9000507@icyb.net.ua> <20081112121410.GA24629@icarus.home.lan> In-Reply-To: <20081112121410.GA24629@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Nate Eldredge , freebsd-hackers@FreeBSD.org, FreeBSD Stable , freebsd-usb@FreeBSD.org Subject: Re: ukbd attachment and root mount X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 12:20:46 -0000 on 12/11/2008 14:14 Jeremy Chadwick said the following: > On Wed, Nov 12, 2008 at 01:58:58PM +0200, Andriy Gapon wrote: [snip] >> 2. if ukbd driver is not attached then I don't see any way USB keyboard >> would work in non-legacy way > > Regarding #2: at which stage? boot0/boot2/loader require an AT or PS/2 > keyboard to work. None of these stages use ukbd(4) or anything -- there > is no kernel loaded at this point!! Meaning: if you have a USB keyboard, > your BIOS will need to have a "USB Legacy" option to cause it to act as > a PS/2 keyboard, for typing in boot0/boot2/loader to work. > > Device hints are for kernel drivers, once the kernel is loaded. Jeremy, I understand all of this. In subject line and earlier messages I say that I am interested in mountroot prompt - the prompt where kernel can ask about what device to use for root filesystem. Essentially I would like kernel to recognize USB keyboard (and disable all the legacy stuff if needed) before it prompts for the root device. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 12:33:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CF6C106567B for ; Wed, 12 Nov 2008 12:33:17 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA04.emeryville.ca.mail.comcast.net (qmta04.emeryville.ca.mail.comcast.net [76.96.30.40]) by mx1.freebsd.org (Postfix) with ESMTP id E95BD8FC1A for ; Wed, 12 Nov 2008 12:33:16 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by QMTA04.emeryville.ca.mail.comcast.net with comcast id eCEQ1a0090vp7WLA4CZGmp; Wed, 12 Nov 2008 12:33:16 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA05.emeryville.ca.mail.comcast.net with comcast id eCZF1a00B2P6wsM8RCZGvm; Wed, 12 Nov 2008 12:33:16 +0000 X-Authority-Analysis: v=1.0 c=1 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=XZrmyMB4JYGd_-K7JrwA:9 a=tBf9LV8KMpQLkPyohSoA:7 a=cY6_MBOsBNGUNeLVBIN5XP9PPJ8A:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id B20FB5C19; Wed, 12 Nov 2008 04:33:15 -0800 (PST) Date: Wed, 12 Nov 2008 04:33:15 -0800 From: Jeremy Chadwick To: Andriy Gapon Message-ID: <20081112123315.GA24907@icarus.home.lan> References: <4911BA93.9030006@icyb.net.ua> <491ABFCD.3060309@icyb.net.ua> <491AC502.9000507@icyb.net.ua> <20081112121410.GA24629@icarus.home.lan> <491ACA19.2040008@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <491ACA19.2040008@icyb.net.ua> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Nate Eldredge , freebsd-hackers@FreeBSD.org, FreeBSD Stable , freebsd-usb@FreeBSD.org Subject: Re: ukbd attachment and root mount X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 12:33:17 -0000 On Wed, Nov 12, 2008 at 02:20:41PM +0200, Andriy Gapon wrote: > on 12/11/2008 14:14 Jeremy Chadwick said the following: > > On Wed, Nov 12, 2008 at 01:58:58PM +0200, Andriy Gapon wrote: > [snip] > >> 2. if ukbd driver is not attached then I don't see any way USB keyboard > >> would work in non-legacy way > > > > Regarding #2: at which stage? boot0/boot2/loader require an AT or PS/2 > > keyboard to work. None of these stages use ukbd(4) or anything -- there > > is no kernel loaded at this point!! Meaning: if you have a USB keyboard, > > your BIOS will need to have a "USB Legacy" option to cause it to act as > > a PS/2 keyboard, for typing in boot0/boot2/loader to work. > > > > Device hints are for kernel drivers, once the kernel is loaded. > > Jeremy, > > I understand all of this. > In subject line and earlier messages I say that I am interested in > mountroot prompt - the prompt where kernel can ask about what device to > use for root filesystem. > Essentially I would like kernel to recognize USB keyboard (and disable > all the legacy stuff if needed) before it prompts for the root device. I fully understand that fact. However, I don't see the logic in that statement. You should be able to remove and add a keyboard at any time and be able to type immediately. Meaning: I don't see why when the keyboard recognition is performed (e.g. before printing mountroot or after) matters. It should not. I think this is a red herring. I've seen the problem where I have a fully functional USB keyboard in boot0/boot2/loader and in multi-user, but when booting into single-user or when getting a mountroot prompt, the keyboard does not function. When the mountroot prompt is printed (before or after ukbd attached) makes no difference for me in this scenario -- I tested it many times. It's very possible that "something" (kbdcontrol?) is getting run only during late stages of multi-user, which makes the keyboard work. But prior to that "something" being run (but AFTER boot2/loader), the keyboard is not truly usable. I hope everyone here is also aware of that fact that not all keyboards are created equal. Case in point (and this reason is exactly why I am purchasing a native PS/2 keyboard, as USB4BSD doesn't work with all USB keyboards right now): http://lists.freebsd.org/pipermail/freebsd-current/2008-November/000219.html The bottom line: FreeBSD cannot be reliably used with a USB keyboard in all circumstances. And that is a very sad reality, because 90% of the keyboards you find on the consumer and enterprise market are USB -- native PS/2 keyboards are now a scarcity. Do not even for a minute tell me "buy a USB-to-PS2 adapter", because the "green ones" that come with USB mice do not work with USB keyboards. I have even bought a "purple" USB-to-PS2 keyboard adapter from Amazon, specifically for this purpose, and it *does not work*. I found out weeks later the adapters only work on CERTAIN models of USB keyboards, depending upon how they're engineered. What really needs to happen here should be obvious: we need some form of inexpensive keyboard-only USB support in boot2/loader. I would *love* to know how Linux and Windows solve this problem. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 12:49:20 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BFFE106567E; Wed, 12 Nov 2008 12:49:20 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 527958FC13; Wed, 12 Nov 2008 12:49:17 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA17199; Wed, 12 Nov 2008 14:49:16 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <491AD0CB.8050309@icyb.net.ua> Date: Wed, 12 Nov 2008 14:49:15 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.17 (X11/20081106) MIME-Version: 1.0 To: Jeremy Chadwick References: <4911BA93.9030006@icyb.net.ua> <491ABFCD.3060309@icyb.net.ua> <491AC502.9000507@icyb.net.ua> <20081112121410.GA24629@icarus.home.lan> <491ACA19.2040008@icyb.net.ua> <20081112123315.GA24907@icarus.home.lan> In-Reply-To: <20081112123315.GA24907@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Nate Eldredge , freebsd-hackers@FreeBSD.org, FreeBSD Stable , freebsd-usb@FreeBSD.org Subject: Re: ukbd attachment and root mount X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 12:49:20 -0000 on 12/11/2008 14:33 Jeremy Chadwick said the following: > On Wed, Nov 12, 2008 at 02:20:41PM +0200, Andriy Gapon wrote: >> on 12/11/2008 14:14 Jeremy Chadwick said the following: >>> On Wed, Nov 12, 2008 at 01:58:58PM +0200, Andriy Gapon wrote: >> [snip] >>>> 2. if ukbd driver is not attached then I don't see any way USB keyboard >>>> would work in non-legacy way >>> Regarding #2: at which stage? boot0/boot2/loader require an AT or PS/2 >>> keyboard to work. None of these stages use ukbd(4) or anything -- there >>> is no kernel loaded at this point!! Meaning: if you have a USB keyboard, >>> your BIOS will need to have a "USB Legacy" option to cause it to act as >>> a PS/2 keyboard, for typing in boot0/boot2/loader to work. >>> >>> Device hints are for kernel drivers, once the kernel is loaded. >> Jeremy, >> >> I understand all of this. >> In subject line and earlier messages I say that I am interested in >> mountroot prompt - the prompt where kernel can ask about what device to >> use for root filesystem. >> Essentially I would like kernel to recognize USB keyboard (and disable >> all the legacy stuff if needed) before it prompts for the root device. > > I fully understand that fact. However, I don't see the logic in that > statement. You should be able to remove and add a keyboard at any time > and be able to type immediately. Meaning: I don't see why when the > keyboard recognition is performed (e.g. before printing mountroot or > after) matters. It should not. I think this is a red herring. I think that this does matter because keyboard recognition is performed after the 'mounting from' log line *only if* root mount is done automatically. If there is an actual interactive prompt then recognition is not performed, at least I do not see any relevant lines on the screen and I am stuck at the prompt. > I've seen the problem where I have a fully functional USB keyboard in > boot0/boot2/loader For me it even randomly dies at these stages. I reported this in a different thread. But this should not be related to kernel behavior. >and in multi-user, For me this always works. > but when booting into single-user For me this always works. > or when getting a mountroot prompt, the keyboard does not function. > When the mountroot prompt is printed (before or after ukbd attached) > makes no difference for me in this scenario -- I tested it many times. For me ukbd lines are never printed if I get actual interactive mountroot prompt. > It's very possible that "something" (kbdcontrol?) is getting run only > during late stages of multi-user, which makes the keyboard work. But > prior to that "something" being run (but AFTER boot2/loader), the > keyboard is not truly usable. For me this is not true. My keyboard always works after ukbd lines appear on screen. > I hope everyone here is also aware of that fact that not all keyboards > are created equal. Case in point (and this reason is exactly why I > am purchasing a native PS/2 keyboard, as USB4BSD doesn't work with > all USB keyboards right now): For me this is not an option, no PS/2 ports. > http://lists.freebsd.org/pipermail/freebsd-current/2008-November/000219.html > > The bottom line: > > FreeBSD cannot be reliably used with a USB keyboard in all > circumstances.And that is a very sad reality, because 90% of the > keyboards you find on the consumer and enterprise market are USB -- > native PS/2 keyboards are now a scarcity. I agree that this is a sad reality but only for boot stages where we depend on external entity named BIOS to help us. This doesn't have to be a sad reality once kernel takes control. USB support in boot chain - I don't know - this would be great of course but that's a lot of code. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 13:21:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E951E1065687 for ; Wed, 12 Nov 2008 13:21:25 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA04.emeryville.ca.mail.comcast.net (qmta04.emeryville.ca.mail.comcast.net [76.96.30.40]) by mx1.freebsd.org (Postfix) with ESMTP id D11B78FC18 for ; Wed, 12 Nov 2008 13:21:25 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by QMTA04.emeryville.ca.mail.comcast.net with comcast id eBye1a00C1HpZEsA4DMRpK; Wed, 12 Nov 2008 13:21:25 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA14.emeryville.ca.mail.comcast.net with comcast id eDMQ1a00A2P6wsM8aDMQ4W; Wed, 12 Nov 2008 13:21:25 +0000 X-Authority-Analysis: v=1.0 c=1 a=_W5frmRxAAAA:8 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=2lWE_imY3XTQs1vxiW4A:9 a=1T7QYldBgFax1CoTx-0A:7 a=KfhU-U27iizIc1WJhpv8hk7dyfkA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id A0EE15C19; Wed, 12 Nov 2008 05:21:24 -0800 (PST) Date: Wed, 12 Nov 2008 05:21:24 -0800 From: Jeremy Chadwick To: Andriy Gapon Message-ID: <20081112132124.GA25637@icarus.home.lan> References: <4911BA93.9030006@icyb.net.ua> <491ABFCD.3060309@icyb.net.ua> <491AC502.9000507@icyb.net.ua> <20081112121410.GA24629@icarus.home.lan> <491ACA19.2040008@icyb.net.ua> <20081112123315.GA24907@icarus.home.lan> <491AD0CB.8050309@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <491AD0CB.8050309@icyb.net.ua> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Nate Eldredge , freebsd-hackers@FreeBSD.org, FreeBSD Stable , freebsd-usb@FreeBSD.org Subject: Re: ukbd attachment and root mount X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 13:21:26 -0000 On Wed, Nov 12, 2008 at 02:49:15PM +0200, Andriy Gapon wrote: > on 12/11/2008 14:33 Jeremy Chadwick said the following: > > On Wed, Nov 12, 2008 at 02:20:41PM +0200, Andriy Gapon wrote: > >> on 12/11/2008 14:14 Jeremy Chadwick said the following: > >>> On Wed, Nov 12, 2008 at 01:58:58PM +0200, Andriy Gapon wrote: > >> [snip] > >>>> 2. if ukbd driver is not attached then I don't see any way USB keyboard > >>>> would work in non-legacy way > >>> Regarding #2: at which stage? boot0/boot2/loader require an AT or PS/2 > >>> keyboard to work. None of these stages use ukbd(4) or anything -- there > >>> is no kernel loaded at this point!! Meaning: if you have a USB keyboard, > >>> your BIOS will need to have a "USB Legacy" option to cause it to act as > >>> a PS/2 keyboard, for typing in boot0/boot2/loader to work. > >>> > >>> Device hints are for kernel drivers, once the kernel is loaded. > >> Jeremy, > >> > >> I understand all of this. > >> In subject line and earlier messages I say that I am interested in > >> mountroot prompt - the prompt where kernel can ask about what device to > >> use for root filesystem. > >> Essentially I would like kernel to recognize USB keyboard (and disable > >> all the legacy stuff if needed) before it prompts for the root device. > > > > I fully understand that fact. However, I don't see the logic in that > > statement. You should be able to remove and add a keyboard at any time > > and be able to type immediately. Meaning: I don't see why when the > > keyboard recognition is performed (e.g. before printing mountroot or > > after) matters. It should not. I think this is a red herring. > > I think that this does matter because keyboard recognition is performed > after the 'mounting from' log line *only if* root mount is done > automatically. > If there is an actual interactive prompt then recognition is not > performed, at least I do not see any relevant lines on the screen and I > am stuck at the prompt. > > > I've seen the problem where I have a fully functional USB keyboard in > > boot0/boot2/loader > > For me it even randomly dies at these stages. > I reported this in a different thread. > But this should not be related to kernel behavior. > > >and in multi-user, > > For me this always works. > > > but when booting into single-user > > For me this always works. > > > or when getting a mountroot prompt, the keyboard does not function. > > When the mountroot prompt is printed (before or after ukbd attached) > > makes no difference for me in this scenario -- I tested it many times. > > For me ukbd lines are never printed if I get actual interactive > mountroot prompt. > > > It's very possible that "something" (kbdcontrol?) is getting run only > > during late stages of multi-user, which makes the keyboard work. But > > prior to that "something" being run (but AFTER boot2/loader), the > > keyboard is not truly usable. > > For me this is not true. My keyboard always works after ukbd lines > appear on screen. I've pointed you to evidence where this isn't true, especially when using the USB4BSD stack. There is something called "boot legacy protocol" which USB keyboards have to support to properly be interfaced with in FreeBSD using the USB4BSD stack; in the case of the Microsoft Natural Ergo 4000 keyboard, it does not play well with USB4BSD (it DOES work with the old USB stack, but none of the multimedia keys work, and worse, the F-Lock key does not work; this is because those keys use uhid(4) and not ukbd(4)). Linux has a __20 page Wiki document__ on **just this keyboard**. That should give you some idea of how complex the situation with USB keyboards is in general. http://www.gentoo-wiki.info/HOWTO_Microsoft_Natural_Ergonomic_Keyboard_4000 > > I hope everyone here is also aware of that fact that not all keyboards > > are created equal. Case in point (and this reason is exactly why I > > am purchasing a native PS/2 keyboard, as USB4BSD doesn't work with > > all USB keyboards right now): > > For me this is not an option, no PS/2 ports. I don't know what to say to ***ANY*** of the above, other than this: No one is doing anything about this problem because there does not appear to be a 100% reproducible always-screws-up-when-I-do-this scenario that happens to *every FreeBSD user*. Until we settle down, stop replying to Emails with one-liner injections, and compile a list of test scenarios/cases that people can perform, and get these people to provide both 1) full hardware details, 2) full kernel configuration files, 3) full loader.conf files, and 4) full device.hints files, we're not going to get anywhere. > > http://lists.freebsd.org/pipermail/freebsd-current/2008-November/000219.html > > > > The bottom line: > > > > FreeBSD cannot be reliably used with a USB keyboard in all > > circumstances.And that is a very sad reality, because 90% of the > > keyboards you find on the consumer and enterprise market are USB -- > > native PS/2 keyboards are now a scarcity. > > I agree that this is a sad reality but only for boot stages where we > depend on external entity named BIOS to help us. > This doesn't have to be a sad reality once kernel takes control. It's been confirmed by numerous people now, including #bsdports users, that "USB Legacy" does not work for some individuals. This is either because of BIOS bugs, or because the USB keyboards do not support tying into SMM. We don't know the true cause. One thing we do know: we have FreeBSD users stating they cannot type in boot0/boot2/loader, even with USB Legacy enabled, so going into single-user after a reboot is impossible. Another thing we do know: we have FreeBSD users who do not have fully functional USB keyboards in FreeBSD (some see ukbd attach, others do not; some are using USB4BSD, others are not). So, can someone take the time to come up with test scenarios/cases so that users can perform these tests, list off the exact hardware they have, and we can see if there is a consistent/common failure between everyone? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 13:33:52 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76D45106564A; Wed, 12 Nov 2008 13:33:52 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E65A38FC24; Wed, 12 Nov 2008 13:33:50 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA17993; Wed, 12 Nov 2008 15:33:49 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <491ADB3B.2090000@icyb.net.ua> Date: Wed, 12 Nov 2008 15:33:47 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.17 (X11/20081106) MIME-Version: 1.0 To: Jeremy Chadwick References: <4911BA93.9030006@icyb.net.ua> <491ABFCD.3060309@icyb.net.ua> <491AC502.9000507@icyb.net.ua> <20081112121410.GA24629@icarus.home.lan> <491ACA19.2040008@icyb.net.ua> <20081112123315.GA24907@icarus.home.lan> <491AD0CB.8050309@icyb.net.ua> <20081112132124.GA25637@icarus.home.lan> In-Reply-To: <20081112132124.GA25637@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Nate Eldredge , freebsd-hackers@FreeBSD.org, FreeBSD Stable , freebsd-usb@FreeBSD.org Subject: Re: ukbd attachment and root mount X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 13:33:52 -0000 on 12/11/2008 15:21 Jeremy Chadwick said the following: > I don't know what to say to ***ANY*** of the above, other than this: > > No one is doing anything about this problem because there does not > appear to be a 100% reproducible always-screws-up-when-I-do-this > scenario that happens to *every FreeBSD user*. > > Until we settle down, stop replying to Emails with one-liner injections, > and compile a list of test scenarios/cases that people can perform, and > get these people to provide both 1) full hardware details, 2) full > kernel configuration files, 3) full loader.conf files, and 4) full > device.hints files, we're not going to get anywhere. Well I started two separate threads. This thread is about one very specific issue - ukbd attaching after mountroot code. Again, in this thread I am only interested in getting ukbd to attach before the mount root. I am not interested in BIOS, boot chain, etc. I am not even interested in speculations about whether keyboard would work or not at mountroot prompt if it were attaching before it. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 16:18:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9846F106564A for ; Wed, 12 Nov 2008 16:18:13 +0000 (UTC) (envelope-from freebsd-stable@epcdirect.co.uk) Received: from gunfright.epcdirect.co.uk (gunfright.epcdirect.co.uk [195.10.242.32]) by mx1.freebsd.org (Postfix) with ESMTP id 616C08FC19 for ; Wed, 12 Nov 2008 16:18:13 +0000 (UTC) (envelope-from freebsd-stable@epcdirect.co.uk) Received: from localhost (localhost.epcdirect.co.uk [127.0.0.1]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id 053646178 for ; Wed, 12 Nov 2008 15:56:59 +0000 (GMT) X-Virus-Scanned: by GunFright.EPCDirect.co.uk Received: from gunfright.epcdirect.co.uk ([127.0.0.1]) by localhost (gunfright.epcdirect.co.uk [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id OZa+NjguUEvW for ; Wed, 12 Nov 2008 15:56:58 +0000 (GMT) Received: from lfarr (l-farr.int.epcdirect.co.uk [192.168.6.200]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id C5F816174 for ; Wed, 12 Nov 2008 15:56:58 +0000 (GMT) From: "Lawrence Farr" To: Date: Wed, 12 Nov 2008 15:56:56 -0000 Message-ID: <005601c944df$49e17d40$dda477c0$@co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AclE30m03CSD/La/Quiv9sjLVVfDAA== Content-Language: en-gb Subject: Cannot see disks attached to Marvell controller X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 16:18:13 -0000 I've got an Asus P5E3WSPro with 8 SATA ports and 8 disks attached. 6 disks are on one controller (and work perfectly) and 2 are on a second Marvell controller. FreeBSD sees the controller, but not the disks. If I move a working disk to the Marvell controller I can boot off it up to the stage of mounting root where it fails to see the disk. atacontrol shows: ATA channel 2: Master: no device present Slave: no device present ATA channel 3: Master: no device present Slave: no device present ATA channel 4: Master: ad8 Serial ATA II Slave: no device present ATA channel 5: Master: ad10 Serial ATA II Slave: no device present ATA channel 6: Master: ad12 Serial ATA II Slave: no device present ATA channel 7: Master: ad14 Serial ATA II Slave: no device present ATA channel 8: Master: ad16 Serial ATA II Slave: no device present ATA channel 9: Master: ad18 Serial ATA II Slave: no device present Here's the pciconf listing: atapci1@pci0:0:31:2: class=0x010601 card=0x82771043 chip=0x29228086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) 6 port SATA AHCI Controller' class = mass storage -- atapci0@pci0:1:0:0: class=0x01048f card=0x82201043 chip=0x614511ab rev=0xa1 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = '? Add-on IC to provide 4x SATA Ports, attached to ICH7 (SthBridge?) via PCI-Express.' class = mass storage Anyone got any ideas why they don't show up? I've tried every BIOS option with the controller, Ie raid mode etc. From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 14:11:53 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89855106564A; Wed, 12 Nov 2008 14:11:53 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms173007pub.verizon.net (vms173007pub.verizon.net [206.46.173.7]) by mx1.freebsd.org (Postfix) with ESMTP id 687308FC0A; Wed, 12 Nov 2008 14:11:53 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from verizon.net ([63.28.162.53]) by vms173007.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0KA8003HB1XVGIB9@vms173007.mailsrvcs.net>; Wed, 12 Nov 2008 07:10:46 -0600 (CST) Date: Wed, 12 Nov 2008 08:18:51 -0500 From: Sergey Babkin Sender: root To: Jeremy Chadwick Message-id: <491AD7BB.2EAA9AA0@verizon.net> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.7-RELEASE i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en, ru References: <4911BA93.9030006@icyb.net.ua> <491ABFCD.3060309@icyb.net.ua> <491AC502.9000507@icyb.net.ua> <20081112121410.GA24629@icarus.home.lan> <491ACA19.2040008@icyb.net.ua> <20081112123315.GA24907@icarus.home.lan> X-Mailman-Approved-At: Wed, 12 Nov 2008 16:47:59 +0000 Cc: Nate Eldredge , freebsd-hackers@FreeBSD.org, FreeBSD Stable , Andriy Gapon , freebsd-usb@FreeBSD.org Subject: Re: ukbd attachment and root mount X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 14:11:53 -0000 Jeremy Chadwick wrote: > > What really needs to happen here should be obvious: we need some form of > inexpensive keyboard-only USB support in boot2/loader. > > I would *love* to know how Linux and Windows solve this problem. If I remember right, UnixWare used(s) the BIOS calls in the loader. -SB From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 16:52:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54B451065698; Wed, 12 Nov 2008 16:52:30 +0000 (UTC) (envelope-from nakal@web.de) Received: from fmmailgate03.web.de (fmmailgate03.web.de [217.72.192.234]) by mx1.freebsd.org (Postfix) with ESMTP id 121B78FC2D; Wed, 12 Nov 2008 16:52:29 +0000 (UTC) (envelope-from nakal@web.de) Received: from smtp07.web.de (fmsmtp07.dlan.cinetic.de [172.20.5.215]) by fmmailgate03.web.de (Postfix) with ESMTP id 6A97DF456846; Wed, 12 Nov 2008 17:52:28 +0100 (CET) Received: from [217.236.27.27] (helo=zelda.local) by smtp07.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1L0IxA-000655-00; Wed, 12 Nov 2008 17:52:28 +0100 Date: Wed, 12 Nov 2008 17:52:17 +0100 From: Martin To: pluknet Message-ID: <20081112175217.1b37caf1@zelda.local> In-Reply-To: References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> <20081111213344.6657548c@zelda.local> X-Mailer: Claws Mail 3.6.0 (GTK+ 2.12.11; amd64-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/MjH/MToqh=oqojIix.cpuLL"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX19UlOCxKlXLMxuXngazc8BiH2XMAsCg2h2cFc50 5KbUQEBFHypeYIOAS2TNabc3bfMqEvYdyK4GnPnsMHsaCROeoE /AXGhH6J4= Cc: Volker , Stable , freebsd-usb@freebsd.org, Peter Wemm , Andriy Gapon Subject: Re: usb keyboard dying at loader prompt X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 16:52:30 -0000 --Sig_/MjH/MToqh=oqojIix.cpuLL Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Wed, 12 Nov 2008 12:36:19 +0300 schrieb pluknet : > I have the same problem with my ukbd&ums: > they are power off'ed during the boot and I should to re-attach them . > MB: Asus p5k. Hi, I've noticed one thing today. I can switch off USB-Keyboard support in my BIOS. In this case, I cannot use my keyboard during boot prompt, but FreeBSD at least initializes the USB-controller correctly, so I can use it later when entering my geli partition password. It seems the BIOS on some mainboards puts the USB controller in a state from which FreeBSD cannot initialize the hardware anymore. And, let's not forget, there is the second problem with devices that suddenly power off at apparently random times. -- Martin --Sig_/MjH/MToqh=oqojIix.cpuLL Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkbCckACgkQC3yNaKlBCg1YKgCfTRPG6yRo4bxA8GjPrHA02U45 d28AnA2r2gyaeiMtH6zFE0ri99TzUMT/ =gMbX -----END PGP SIGNATURE----- --Sig_/MjH/MToqh=oqojIix.cpuLL-- From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 17:30:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 638541065670; Wed, 12 Nov 2008 17:30:17 +0000 (UTC) (envelope-from nakal@web.de) Received: from fmmailgate01.web.de (fmmailgate01.web.de [217.72.192.221]) by mx1.freebsd.org (Postfix) with ESMTP id A56DA8FC0A; Wed, 12 Nov 2008 17:30:16 +0000 (UTC) (envelope-from nakal@web.de) Received: from smtp07.web.de (fmsmtp07.dlan.cinetic.de [172.20.5.215]) by fmmailgate01.web.de (Postfix) with ESMTP id 101FEF97A08E; Wed, 12 Nov 2008 18:30:15 +0100 (CET) Received: from [217.236.27.27] (helo=zelda.local) by smtp07.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1L0JXi-00024g-00; Wed, 12 Nov 2008 18:30:14 +0100 Date: Wed, 12 Nov 2008 18:30:12 +0100 From: Martin To: Jeremy Chadwick Message-ID: <20081112183012.57af6eb5@zelda.local> In-Reply-To: <20081112132124.GA25637@icarus.home.lan> References: <4911BA93.9030006@icyb.net.ua> <491ABFCD.3060309@icyb.net.ua> <491AC502.9000507@icyb.net.ua> <20081112121410.GA24629@icarus.home.lan> <491ACA19.2040008@icyb.net.ua> <20081112123315.GA24907@icarus.home.lan> <491AD0CB.8050309@icyb.net.ua> <20081112132124.GA25637@icarus.home.lan> X-Mailer: Claws Mail 3.6.0 (GTK+ 2.12.11; amd64-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX1/acbvjZK9J7Loya0JHgQ2FU/HIdANhopoXZvEL /Yfr2grVu+T234KfGavKbd45/Be5PP0hgdDwVh5hN2IAFrfrDf sqxa8D3qs= Cc: Nate Eldredge , freebsd-hackers@FreeBSD.org, FreeBSD Stable , Andriy Gapon , freebsd-usb@FreeBSD.org Subject: Re: ukbd attachment and root mount X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 17:30:17 -0000 Am Wed, 12 Nov 2008 05:21:24 -0800 schrieb Jeremy Chadwick : > Until we settle down, stop replying to Emails with one-liner > injections, and compile a list of test scenarios/cases that people > can perform, and get these people to provide both 1) full hardware > details, 2) full kernel configuration files, 3) full loader.conf > files, and 4) full device.hints files, we're not going to get > anywhere. Ok, I will add the details for the GA-EP45-DS3R based system. 1) dmesg Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-PRERELEASE #0: Mon Nov 10 08:23:21 CET 2008 root@kirby:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz (3166.32-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x10676 Stepping = 6 Features=0xbfebfbff Features2=0x8e3fd> AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 usable memory = 8574255104 (8177 MB) avail memory = 8286810112 (7902 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, cfdb0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xa000-0xa0ff mem 0xd0000000-0xdfffffff,0xe5000000-0xe500ffff irq 16 at device 0.0 on pci1 pcm0: mem 0xe5010000-0xe5013fff irq 17 at device 0.1 on pci1 pcm0: [ITHREAD] uhci0: port 0xe000-0xe01f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe100-0xe11f irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xe200-0xe21f irq 18 at device 26.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xe9305000-0xe93053ff irq 18 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered pcm1: mem 0xe9300000-0xe9303fff irq 22 at device 27.0 on pci0 pcm1: [ITHREAD] pcib2: irq 16 at device 28.0 on pci0 pci2: on pcib2 pcib3: irq 19 at device 28.3 on pci0 pci3: on pcib3 atapci0: port 0xb000-0xb007,0xb100-0xb103,0xb200-0xb207,0xb300-0xb303,0xb400-0xb40f irq 19 at device 0.0 on pci3 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] pcib4: irq 16 at device 28.4 on pci0 pci4: on pcib4 re0: port 0xc000-0xc0ff mem Ethernet> 0xe9010000-0xe9010fff,0xe9000000-0xe900ffff irq 16 at device Ethernet> 0.0 on pci4 re0: Chip rev. 0x3c000000 re0: MAC rev. 0x00400000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1f:d0:24:96:ab re0: [FILTER] pcib5: irq 17 at device 28.5 on pci0 pci5: on pcib5 re1: port 0xd000-0xd0ff mem Ethernet> 0xe9110000-0xe9110fff,0xe9100000-0xe910ffff irq 17 at device Ethernet> 0.0 on pci5 re1: Chip rev. 0x3c000000 re1: MAC rev. 0x00400000 miibus1: on re1 rgephy1: PHY 1 on miibus1 rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re1: Ethernet address: 00:1f:d0:24:96:a9 re1: [FILTER] uhci3: port 0xe300-0xe31f irq 23 at device 29.0 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered uhci4: port 0xe400-0xe41f irq 19 at device 29.1 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub5: on usb5 uhub5: 2 ports with 2 removable, self powered uhci5: port 0xe500-0xe51f irq 18 at device 29.2 on pci0 uhci5: [GIANT-LOCKED] uhci5: [ITHREAD] usb6: on uhci5 usb6: USB revision 1.0 uhub6: on usb6 uhub6: 2 ports with 2 removable, self powered ehci1: mem 0xe9304000-0xe93043ff irq 23 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb7: EHCI version 1.0 usb7: companion controllers, 2 ports each: usb4 usb5 usb6 usb7: on ehci1 usb7: USB revision 2.0 uhub7: on usb7 uhub7: 6 ports with 6 removable, self powered pcib6: at device 30.0 on pci0 pci6: on pcib6 fwohci0: mem 0xe9204000-0xe92047ff,0xe9200000-0xe9203fff irq 23 at device 7.0 on pci6 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:2c:a1:59:00:00:1f:d0 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:2c:a1:00:1f:d0 fwe0: Ethernet address: 02:2c:a1:00:1f:d0 fwip0: on firewire0 fwip0: Firewire address: 00:2c:a1:59:00:00:1f:d0 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0xcf2b4000 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0xe600-0xe607,0xe700-0xe703,0xe800-0xe807,0xe900-0xe903,0xea00-0xea1f mem 0xe9306000-0xe93067ff irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI Version 01.20 controller with 6 ports detected ata3: on atapci1 ata3: [ITHREAD] ata4: on atapci1 ata4: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] ata6: on atapci1 ata6: [ITHREAD] ata7: on atapci1 ata7: [ITHREAD] ata8: on atapci1 ata8: [ITHREAD] pci0: at device 31.3 (no driver attached) fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] cpu0: on acpi0 est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 61a492006004920 device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 61a492006004920 device_attach: est1 attach returned 6 p4tcc1: on cpu1 orm0: at iomem 0xd0000-0xd1fff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd0: on uhub2 kbd2 at ukbd0 uhid0: on uhub2 ums0: on uhub2 ums0: 8 buttons and Z dir. Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ad6: 476938MB at ata3-master SATA300 GEOM_JOURNAL: Journal 3939325718: ad6s1f contains data. GEOM_JOURNAL: Journal 3939325718: ad6s1f contains journal. GEOM_JOURNAL: Journal ad6s1f clean. acd0: DVDR at ata4-master SATA150 pcm0: pcm0: pcm1: pcm1: SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad6s1a cryptosoft0: on motherboard GEOM_ELI: Device ad6s1g.eli created. GEOM_ELI: Encryption: Blowfish-CBC 448 GEOM_ELI: Crypto: software GEOM_JOURNAL: Journal 2001271740: ad6s1g.eli contains data. GEOM_JOURNAL: Journal 2001271740: ad6s1g.eli contains journal. GEOM_JOURNAL: Journal ad6s1g.eli clean. GEOM_ELI: Device ad6s1b.eli created. GEOM_ELI: Encryption: AES-CBC 256 GEOM_ELI: Crypto: software 2) As you can see above, GENERIC (here stable, but also occurs on BETA2). 3) loader.conf: acpi_load="YES" acpi_video_load="YES" beastie_disable="YES" geom_journal_load="YES" #smb_load="YES" #smbus_load="YES" #ichsmb_load="YES" snd_hda_load="YES" #aio_load="YES" #kqemu_load="YES" kern.cam.scsi_delay=1000 autoboot_delay=3 linux_load="YES" linprocfs_load="YES" linsysfs_load="YES" 4) device.hints unchanged. > It's been confirmed by numerous people now, including #bsdports users, > that "USB Legacy" does not work for some individuals. This is either > because of BIOS bugs, or because the USB keyboards do not support > tying into SMM. We don't know the true cause. I'm not sure, if every BIOS has got such a setting. I'm not fully sure, if this is a BIOS bug. It could be, of course. Gigabyte has released BIOS firmware updates that are not usable, until one installs Windows (the changes history does not mention any USB fixes though). It will take some time until I can patch the firmware. > One thing we do know: we have FreeBSD users stating they cannot type > in boot0/boot2/loader, even with USB Legacy enabled, so going into > single-user after a reboot is impossible. > > Another thing we do know: we have FreeBSD users who do not have fully > functional USB keyboards in FreeBSD (some see ukbd attach, others do > not; some are using USB4BSD, others are not). Yes. These are 3 different problems. 1) No keyboard in bootloader => missing BIOS USB support. 2) No keyboard after USB controller initialisation => missing quirks? 3) No keyboard spontaneously while working => bug? > So, can someone take the time to come up with test scenarios/cases so > that users can perform these tests, list off the exact hardware they > have, and we can see if there is a consistent/common failure between > everyone? If you need anything more, I can try to deliver the information. I sometimes run out of ideas how to avoid annoying the developers. :) (In other words, I have more problems to report waiting in the queue...) ;) -- Martin From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 17:35:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 022A31065677 for ; Wed, 12 Nov 2008 17:35:54 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id D51FC8FC12 for ; Wed, 12 Nov 2008 17:35:53 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1L0JNI-0007dj-1d for freebsd-stable@freebsd.org; Wed, 12 Nov 2008 09:19:28 -0800 Message-ID: <20464994.post@talk.nabble.com> Date: Wed, 12 Nov 2008 09:19:28 -0800 (PST) From: jbondc To: freebsd-stable@freebsd.org In-Reply-To: <62b856460811031507n2bbfdc14j3bfa7b6006208ff0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jbondc@openmv.com References: <490F6EBF.5000102@minibofh.org> <62b856460811031507n2bbfdc14j3bfa7b6006208ff0@mail.gmail.com> Subject: Re: Replication system X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 17:35:54 -0000 Michael Grant-3 wrote: > > > GlusterFS http://www.gluster.org seems promising. It is a replication > layer that sits on top of FUSE (Filesystem in Userspace > http://fuse.sf.net). You can replicate pretty much any type of file > system, ufs, zfs, dos...etc. In other words, you don't need to > reformat your disk or create some special underlying file system. > GlusterFS is in userspace. > > However.... I have yet to get it working on freebsd. Anyone had any > luck with GlusterFS on Freebsd 6.x? > > The latest client currently segfaults on freebsd 6 I just created this wiki entry: http://www.freebsdwiki.net/index.php/GlusterFS On Freebsd 7 works quite well -- View this message in context: http://www.nabble.com/Replication-system-tp20311697p20464994.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 17:58:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A11B1065677 for ; Wed, 12 Nov 2008 17:58:37 +0000 (UTC) (envelope-from tdb@carrick.bishnet.net) Received: from carrick.bishnet.net (carrick.bishnet.net [IPv6:2a01:348:132::1]) by mx1.freebsd.org (Postfix) with ESMTP id E296B8FC1C for ; Wed, 12 Nov 2008 17:58:36 +0000 (UTC) (envelope-from tdb@carrick.bishnet.net) Received: from tdb by carrick.bishnet.net with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1L0Jz0-00032C-9N; Wed, 12 Nov 2008 17:58:26 +0000 Date: Wed, 12 Nov 2008 17:58:26 +0000 From: Tim Bishop To: freebsd-stable@freebsd.org Message-ID: <20081112175826.GD26195@carrick.bishnet.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Key: 0x5AE7D984, http://www.bishnet.net/tim/tim-bishnet-net.asc X-PGP-Fingerprint: 1453 086E 9376 1A50 ECF6 AE05 7DCE D659 5AE7 D984 User-Agent: Mutt/1.5.13 (2006-08-11) X-Bishnet-MailScanner-Information: Contact postmaster@bishnet.net X-Bishnet-MailScanner-VirusCheck: Found to be clean X-Bishnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1.087, required 5, BAYES_00 -2.60, DNS_FROM_SECURITYSAGE 1.51, NO_RELAYS -0.00) X-Bishnet-MailScanner-From: tdb@carrick.bishnet.net Cc: tim@bishnet.net Subject: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 17:58:37 -0000 I've been playing around with snapshots lately but I've got a problem on one of my servers running 7-STABLE amd64: FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 I run the mksnap_ffs command to take the snapshot and some time later the system completely freezes up: paladin# cd /u2/.snap/ paladin# mksnap_ffs /u2 test.1 It only happens on this one filesystem, though, which might be to do with its size. It's not over the 2TB marker, but it's pretty close. It's also backed by a hardware RAID system, although a smaller filesystem on the same RAID has no issues. Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 2078881084 921821396 990749202 48% /u2 To clarify "completely freezes up": unresponsive to all services over the network, except ping. On the console I can switch between the ttys, but none of them respond. The only way out is to hit the reset button. Any advice? I'm happy to help debug this further to get to the bottom of it. Thanks, Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 18:04:37 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FFDA1065670; Wed, 12 Nov 2008 18:04:37 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 26DB98FC12; Wed, 12 Nov 2008 18:04:37 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 476836D43F; Wed, 12 Nov 2008 17:48:29 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 3391284493; Wed, 12 Nov 2008 18:48:29 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Sergey Babkin References: <4911BA93.9030006@icyb.net.ua> <491ABFCD.3060309@icyb.net.ua> <491AC502.9000507@icyb.net.ua> <20081112121410.GA24629@icarus.home.lan> <491ACA19.2040008@icyb.net.ua> <20081112123315.GA24907@icarus.home.lan> <491AD7BB.2EAA9AA0@verizon.net> Date: Wed, 12 Nov 2008 18:48:29 +0100 In-Reply-To: <491AD7BB.2EAA9AA0@verizon.net> (Sergey Babkin's message of "Wed, 12 Nov 2008 08:18:51 -0500") Message-ID: <86iqqsx2c2.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Stable , freebsd-hackers@FreeBSD.org, Jeremy Chadwick , Andriy Gapon , freebsd-usb@FreeBSD.org, Nate Eldredge Subject: Re: ukbd attachment and root mount X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 18:04:37 -0000 Sergey Babkin writes: > Jeremy Chadwick writes: > > What really needs to happen here should be obvious: we need some > > form of inexpensive keyboard-only USB support in boot2/loader. > If I remember right, UnixWare used(s) the BIOS calls in the loader. So does FreeBSD. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 18:11:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF10D1065673 for ; Wed, 12 Nov 2008 18:11:02 +0000 (UTC) (envelope-from david@esn.org.za) Received: from serendipity.wcape.school.za (seren.esn.org.za [196.211.28.252]) by mx1.freebsd.org (Postfix) with ESMTP id E15E78FC17 for ; Wed, 12 Nov 2008 18:11:00 +0000 (UTC) (envelope-from david@esn.org.za) Received: from intsika.ct.esn.org.za ([196.211.28.250] helo=ct.esn.org.za) by serendipity.wcape.school.za with esmtp (Exim 4.30) id 1L0KB7-000G1e-7w for freebsd-stable@freebsd.org; Wed, 12 Nov 2008 20:10:57 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Wed, 12 Nov 2008 20:10:50 +0200 Message-ID: In-Reply-To: <20081112175826.GD26195@carrick.bishnet.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: System deadlock when using mksnap_ffs Thread-Index: AclE8HOlO04ZkvQBTgiIwcsV4wZDBQAAQBAA References: <20081112175826.GD26195@carrick.bishnet.net> From: "David Peall" To: "Tim Bishop" , X-Antivirus-Scanned: Clean by seren.wcsn.org.za Cc: tim@bishnet.net Subject: RE: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 18:11:02 -0000 > -----Original Message----- > From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd- > stable@freebsd.org] On Behalf Of Tim Bishop > Sent: 12 November 2008 07:58 PM > To: freebsd-stable@freebsd.org > Cc: tim@bishnet.net > Subject: System deadlock when using mksnap_ffs > > FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 > 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 >=20 > I run the mksnap_ffs command to take the snapshot and some time later > the system completely freezes up: If the file system is UFS2 it's a known problem but should have been fixed. http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues ident /boot/kernel/kernel | grep subr_sleepqueue version should be greater than 1.39.2.3? Regards -- David Peall :: IT Manager e-Schools' Network :: http://www.esn.org.za/ Phone +27 (021) 674-9140 From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 18:22:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDB911065679 for ; Wed, 12 Nov 2008 18:22:41 +0000 (UTC) (envelope-from tdb@carrick.bishnet.net) Received: from carrick.bishnet.net (carrick.bishnet.net [IPv6:2a01:348:132::1]) by mx1.freebsd.org (Postfix) with ESMTP id B3B168FC18 for ; Wed, 12 Nov 2008 18:22:41 +0000 (UTC) (envelope-from tdb@carrick.bishnet.net) Received: from tdb by carrick.bishnet.net with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1L0KMN-0003UZ-7i; Wed, 12 Nov 2008 18:22:35 +0000 Date: Wed, 12 Nov 2008 18:22:35 +0000 From: Tim Bishop To: David Peall Message-ID: <20081112182234.GE26195@carrick.bishnet.net> References: <20081112175826.GD26195@carrick.bishnet.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: 0x5AE7D984, http://www.bishnet.net/tim/tim-bishnet-net.asc X-PGP-Fingerprint: 1453 086E 9376 1A50 ECF6 AE05 7DCE D659 5AE7 D984 User-Agent: Mutt/1.5.13 (2006-08-11) X-Bishnet-MailScanner-Information: Contact postmaster@bishnet.net X-Bishnet-MailScanner-VirusCheck: Found to be clean X-Bishnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1.499, required 5, AWL -0.49, BAYES_00 -2.60, DNS_FROM_SECURITYSAGE 1.51, NO_RELAYS -0.00, TW_JH 0.08) X-Bishnet-MailScanner-From: tdb@carrick.bishnet.net Cc: Tim Bishop , freebsd-stable@freebsd.org Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 18:22:42 -0000 On Wed, Nov 12, 2008 at 08:10:50PM +0200, David Peall wrote: > > FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 > > 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 > > > > I run the mksnap_ffs command to take the snapshot and some time later > > the system completely freezes up: > > If the file system is UFS2 it's a known problem but should have been > fixed. > http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues > > ident /boot/kernel/kernel | grep subr_sleepqueue > > version should be greater than 1.39.2.3? Yes it's UFS2, and yes it's greater than 1.39.2.3: $FreeBSD: src/sys/kern/subr_sleepqueue.c,v 1.39.2.5 2008/09/16 20:01:57 jhb Exp $ Are you sure the problem referenced on that page is the same? It talks about "dog slow" snapshotting, which I see on other filesystems and machines. But in this particular case the system is dead, and does not recover. Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 18:37:29 2008 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E21F41065673 for ; Wed, 12 Nov 2008 18:37:29 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: from mail2.sea5.speakeasy.net (mail2.sea5.speakeasy.net [69.17.117.4]) by mx1.freebsd.org (Postfix) with ESMTP id C80848FC17 for ; Wed, 12 Nov 2008 18:37:29 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: (qmail 2696 invoked from network); 12 Nov 2008 18:09:24 -0000 Received: from aldan.algebra.com (HELO [127.0.0.1]) (mi@[216.254.65.224]) (envelope-sender ) by mail2.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 12 Nov 2008 18:09:24 -0000 Message-ID: <491B1BD2.4050903@aldan.algebra.com> Date: Wed, 12 Nov 2008 13:09:22 -0500 From: Mikhail Teterin User-Agent: Thunderbird 2.0.0.17 (X11/20080914) MIME-Version: 1.0 To: stable@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: dlopen-ing a library with OpenMP by a non-OpenMP process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 18:37:30 -0000 Hello! Currently, when a program built without OpenMP (-fopenmp) is trying to dlopen a library, built with the feature, the result is a crash from "bad system call": #0 0x00000008009a223c in ksem_init () from /lib/libc.so.7 #1 0x0000000800998a8f in sem_init () from /lib/libc.so.7 #2 0x00000008011a6537 in omp_get_nested () from /usr/lib/libgomp.so.1 #3 0x00000008011a3466 in ?? () from /usr/lib/libgomp.so.1 #4 0x0000000000000002 in ?? () #5 0x00000008005072b2 in dlsym () from /libexec/ld-elf.so.1 #6 0x0000000800507cd2 in dlopen () from /libexec/ld-elf.so.1 ... Can anything be done about this -- disable the OpenMP functionality, but keep the library usable (single-threaded)? The problem arises, in particular, when one is trying to use libraries built by either GraphicsMagick or ImageMagick ports. Both have an OpenMP option, which speeds up some internal algorithms. The option is off by default, but enabling it makes sense on an SMP system... Yet, this makes the library unsuitable for other purposes... Thanks! Yours, -mi P.S. I'm seeing the crash on a recent FreeBSD-7.1/amd64, but it, likely, can be seen elsewhere. From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 18:52:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 801D81065676 for ; Wed, 12 Nov 2008 18:52:54 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by mx1.freebsd.org (Postfix) with ESMTP id 218508FC13 for ; Wed, 12 Nov 2008 18:52:53 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA10.emeryville.ca.mail.comcast.net ([76.96.30.28]) by QMTA01.emeryville.ca.mail.comcast.net with comcast id eESt1a00r0cQ2SLA1Jst9y; Wed, 12 Nov 2008 18:52:53 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA10.emeryville.ca.mail.comcast.net with comcast id eJsr1a00B2P6wsM8WJsrm4; Wed, 12 Nov 2008 18:52:52 +0000 X-Authority-Analysis: v=1.0 c=1 a=becna3ql8DEA:10 a=0kYo9GeZAlkA:10 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=e7F8RB_cu7ubLTsXovMA:9 a=XfXpIeQpwVlGu-eAZygA:7 a=yizOmbJetH5hUlKGhPG31p_kcR4A:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 5458F5C19; Wed, 12 Nov 2008 10:52:51 -0800 (PST) Date: Wed, 12 Nov 2008 10:52:51 -0800 From: Jeremy Chadwick To: Tim Bishop Message-ID: <20081112185251.GA1838@icarus.home.lan> References: <20081112175826.GD26195@carrick.bishnet.net> <20081112182234.GE26195@carrick.bishnet.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081112182234.GE26195@carrick.bishnet.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Tim Bishop , freebsd-stable@freebsd.org, David Peall Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 18:52:54 -0000 On Wed, Nov 12, 2008 at 06:22:35PM +0000, Tim Bishop wrote: > On Wed, Nov 12, 2008 at 08:10:50PM +0200, David Peall wrote: > > > FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 > > > 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 > > > > > > I run the mksnap_ffs command to take the snapshot and some time later > > > the system completely freezes up: > > > > If the file system is UFS2 it's a known problem but should have been > > fixed. > > http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues > > > > ident /boot/kernel/kernel | grep subr_sleepqueue > > > > version should be greater than 1.39.2.3? > > Yes it's UFS2, and yes it's greater than 1.39.2.3: > > $FreeBSD: src/sys/kern/subr_sleepqueue.c,v 1.39.2.5 2008/09/16 20:01:57 jhb Exp $ > > Are you sure the problem referenced on that page is the same? It talks > about "dog slow" snapshotting, which I see on other filesystems and > machines. But in this particular case the system is dead, and does not > recover. This problem gets brought up every few weeks on average, I think. The problem still exists regardless of subr_sleepqueue.c 1.39.2.3. I can still reproduce it on every FreeBSD box I have access to. The last time I tried it was on 2008/10/24, on a RELENG_7 system built from source csup'd on the same day. The result of "dump -L -0 -a -f /someplace/fs.dump /usr" was the same: the system became more or less unusable (meaning to the point where you might as well not try to do anything with it because it's so incredibly slow, especially with anything I/O-bound), and mksnap_ffs remained in the following state for many, many minutes: load: 0.00 cmd: mksnap_ffs 10480 [wdrain] 0.00u 0.06s 0% 1076k Hitting ^C at this point took 4-5 *full minutes* to execute. While ^C was (hopefully) executing, the process remained in wdrain state as well. After the process was terminated fully, the system was again responsive. That filesystem (/usr) I was dumping: Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/ad4s1f 163815904 3834316 146876316 3% 254752 20942046 1% /usr -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 19:43:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B46041065670 for ; Wed, 12 Nov 2008 19:43:50 +0000 (UTC) (envelope-from lehmann@ans-netz.de) Received: from avocado.salatschuessel.net (avocado.salatschuessel.net [78.111.72.186]) by mx1.freebsd.org (Postfix) with SMTP id 0AB8C8FC13 for ; Wed, 12 Nov 2008 19:43:49 +0000 (UTC) (envelope-from lehmann@ans-netz.de) Received: (qmail 71999 invoked by uid 89); 12 Nov 2008 19:43:47 -0000 Received: from unknown (HELO kartoffel.salatschuessel.net) (78.111.72.187) by avocado.salatschuessel.net with SMTP; 12 Nov 2008 19:43:47 -0000 Date: Wed, 12 Nov 2008 20:43:51 +0100 From: Oliver Lehmann To: Philip Murray Message-Id: <20081112204351.ccc51c2f.lehmann@ans-netz.de> In-Reply-To: <13394481-8FDC-4934-BB12-FA5BCB2D35CD@nevada.net.nz> References: <20081029170728.be7cc7ab.lehmann@ans-netz.de> <13394481-8FDC-4934-BB12-FA5BCB2D35CD@nevada.net.nz> X-Mailer: Sylpheed 2.5.0 (GTK+ 2.12.11; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: 3Ware 9000 series hangs under load X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 19:43:50 -0000 Philip Murray wrote: > I used to get this (FreeBSD 6.1 days) all the time, the controller > would just lock up almost on a daily basis (and have to wait for the > fsck 4 out of 24 hours in the day). > > Anyway, I stopped running 3dmd (or 3dm2 I think it's called now) to > monitor it, and the crashes went away. It's had hundreds of days > uptime since. > > I've never been game enough to try newer versions of 3dm, but a > cronjob of tw_cli allows me to monitor it now without the lockups. > > Might not be your problem, but it's worth a shot if all else fails. Ok, it realy looks, like 3dm2 is causing the same problems here too. I've tried several 3dm2 versions and beginning with the version released with 9.1.5.2 the system is crashing on high i/o loads. The previous release included in 9.0.1 and 9.0.2 (made in 2004 iirc) is not crashing. Every release which was made later causes system crashes as well. I'll see what the support staff responds to that.... What cronjobs are you running in particlular to "replace" 3dm2? -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 19:45:55 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D7F7106567C for ; Wed, 12 Nov 2008 19:45:55 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: from mail5.sea5.speakeasy.net (mail5.sea5.speakeasy.net [69.17.117.7]) by mx1.freebsd.org (Postfix) with ESMTP id 0A8828FC13 for ; Wed, 12 Nov 2008 19:45:54 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: (qmail 24901 invoked from network); 12 Nov 2008 19:45:54 -0000 Received: from aldan.algebra.com (HELO [127.0.0.1]) (mi@[216.254.65.224]) (envelope-sender ) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 12 Nov 2008 19:45:54 -0000 Message-ID: <491B3270.5080402@aldan.algebra.com> Date: Wed, 12 Nov 2008 14:45:52 -0500 From: Mikhail Teterin User-Agent: Thunderbird 2.0.0.17 (X11/20080914) MIME-Version: 1.0 To: Kostik Belousov References: <491B1BD2.4050903@aldan.algebra.com> <20081112194350.GJ47073@deviant.kiev.zoral.com.ua> In-Reply-To: <20081112194350.GJ47073@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: dlopen-ing a library with OpenMP by a non-OpenMP process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 19:45:55 -0000 Sent by Kostik Belousov: > On Wed, Nov 12, 2008 at 01:09:22PM -0500, Mikhail Teterin wrote: > >> Hello! >> >> Currently, when a program built without OpenMP (-fopenmp) is trying to >> dlopen a library, built with the feature, the result is a crash from >> "bad system call": >> >> #0 0x00000008009a223c in ksem_init () from /lib/libc.so.7 >> #1 0x0000000800998a8f in sem_init () from /lib/libc.so.7 >> #2 0x00000008011a6537 in omp_get_nested () from /usr/lib/libgomp.so.1 >> #3 0x00000008011a3466 in ?? () from /usr/lib/libgomp.so.1 >> #4 0x0000000000000002 in ?? () >> #5 0x00000008005072b2 in dlsym () from /libexec/ld-elf.so.1 >> #6 0x0000000800507cd2 in dlopen () from /libexec/ld-elf.so.1 >> ... >> > Try "kldload sem". > Uhm... That worked... I see... Shouldn't sem_init be nicer about it, though? Thanks, -mi From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 19:47:44 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 656961065672 for ; Wed, 12 Nov 2008 19:47:44 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 081D38FC12 for ; Wed, 12 Nov 2008 19:47:43 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1L0Lgh-0001je-J8; Wed, 12 Nov 2008 21:47:39 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mACJla0b045101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Nov 2008 21:47:36 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id mACJlaMR092673; Wed, 12 Nov 2008 21:47:36 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mACJlZHK092672; Wed, 12 Nov 2008 21:47:35 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 12 Nov 2008 21:47:35 +0200 From: Kostik Belousov To: Tim Bishop Message-ID: <20081112194735.GK47073@deviant.kiev.zoral.com.ua> References: <20081112175826.GD26195@carrick.bishnet.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cEobB2knsyc5ebfU" Content-Disposition: inline In-Reply-To: <20081112175826.GD26195@carrick.bishnet.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1L0Lgh-0001je-J8 b03a9d209838f59fcaffad7869b70a85 X-Terabit: YES Cc: tim@bishnet.net, freebsd-stable@freebsd.org Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 19:47:44 -0000 --cEobB2knsyc5ebfU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: > I've been playing around with snapshots lately but I've got a problem on > one of my servers running 7-STABLE amd64: >=20 > FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:4= 9:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 >=20 > I run the mksnap_ffs command to take the snapshot and some time later > the system completely freezes up: >=20 > paladin# cd /u2/.snap/ > paladin# mksnap_ffs /u2 test.1 >=20 > It only happens on this one filesystem, though, which might be to do > with its size. It's not over the 2TB marker, but it's pretty close. It's > also backed by a hardware RAID system, although a smaller filesystem on > the same RAID has no issues. >=20 > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 2078881084 921821396 990749202 48% /u2 >=20 > To clarify "completely freezes up": unresponsive to all services over > the network, except ping. On the console I can switch between the ttys, > but none of them respond. The only way out is to hit the reset button. >=20 > Any advice? I'm happy to help debug this further to get to the bottom of > it. You need to provide information described in the http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kernel= debug.html and especially http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kernel= debug-deadlocks.html --cEobB2knsyc5ebfU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkkbMtcACgkQC3+MBN1Mb4hFIwCfU83Ua1RUyIADKc0JSPVUjTSc m2EAoNY8eRCXqdew+m5Ir7Adhu/K85Vs =1MY2 -----END PGP SIGNATURE----- --cEobB2knsyc5ebfU-- From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 19:49:42 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7DE4510656AD; Wed, 12 Nov 2008 19:49:42 +0000 (UTC) (envelope-from tdb@carrick.bishnet.net) Received: from carrick.bishnet.net (carrick.bishnet.net [IPv6:2a01:348:132::1]) by mx1.freebsd.org (Postfix) with ESMTP id B1A7E8FC1C; Wed, 12 Nov 2008 19:49:40 +0000 (UTC) (envelope-from tdb@carrick.bishnet.net) Received: from tdb by carrick.bishnet.net with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1L0LiS-00059u-R2; Wed, 12 Nov 2008 19:49:28 +0000 Date: Wed, 12 Nov 2008 19:49:28 +0000 From: Tim Bishop To: freebsd-stable@freebsd.org Message-ID: <20081112194928.GA19539@carrick.bishnet.net> References: <20081112175826.GD26195@carrick.bishnet.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081112175826.GD26195@carrick.bishnet.net> X-PGP-Key: 0x5AE7D984, http://www.bishnet.net/tim/tim-bishnet-net.asc X-PGP-Fingerprint: 1453 086E 9376 1A50 ECF6 AE05 7DCE D659 5AE7 D984 User-Agent: Mutt/1.5.13 (2006-08-11) X-Bishnet-MailScanner-Information: Contact postmaster@bishnet.net X-Bishnet-MailScanner-VirusCheck: Found to be clean X-Bishnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1.087, required 5, BAYES_00 -2.60, DNS_FROM_SECURITYSAGE 1.51, NO_RELAYS -0.00) X-Bishnet-MailScanner-From: tdb@carrick.bishnet.net Cc: Tim Bishop , Jeremy Chadwick , David Peall Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 19:49:42 -0000 On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: > I run the mksnap_ffs command to take the snapshot and some time later > the system completely freezes up: > > paladin# cd /u2/.snap/ > paladin# mksnap_ffs /u2 test.1 Someone (not named because they choose not to reply to the list) gave me the following patch: --- sys/ufs/ffs/ffs_snapshot.c.orig Wed Mar 22 09:42:31 2006 +++ sys/ufs/ffs/ffs_snapshot.c Mon Nov 20 14:59:13 2006 @@ -282,6 +282,8 @@ restart: if (error) goto out; bawrite(nbp); + if (cg % 10 == 0) + ffs_syncvnode(vp, MNT_WAIT); } /* * Copy all the cylinder group maps. Although the @@ -303,6 +305,8 @@ restart: goto out; error = cgaccount(cg, vp, nbp, 1); bawrite(nbp); + if (cg % 10 == 0) + ffs_syncvnode(vp, MNT_WAIT); if (error) goto out; } With the description: "What can happen is on a big file system it will fill up the buffer cache with I/O and then run out. When the buffer cache fills up then no more disk I/O can happen :-( When you do a sync, it flushes that out to disk so things don't hang." It seems to work too. But it seems more like a workaround than a fix? Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 20:00:37 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E3AC106568D for ; Wed, 12 Nov 2008 20:00:37 +0000 (UTC) (envelope-from brent@servuhome.net) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.186]) by mx1.freebsd.org (Postfix) with ESMTP id D24CB8FC12 for ; Wed, 12 Nov 2008 20:00:36 +0000 (UTC) (envelope-from brent@servuhome.net) Received: by rn-out-0910.google.com with SMTP id j71so536756rne.12 for ; Wed, 12 Nov 2008 12:00:36 -0800 (PST) Received: by 10.151.155.5 with SMTP id h5mr14614578ybo.133.1226518340875; Wed, 12 Nov 2008 11:32:20 -0800 (PST) Received: by 10.150.202.20 with HTTP; Wed, 12 Nov 2008 11:32:20 -0800 (PST) Message-ID: Date: Wed, 12 Nov 2008 11:32:20 -0800 From: "Brent Jones" To: "Adam McDougall" In-Reply-To: <49107CA1.5090309@egr.msu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49107CA1.5090309@egr.msu.edu> Cc: stable@freebsd.org, Eduardo Meyer , questions@freebsd.org Subject: Re: Disk top usage PIDs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 20:00:37 -0000 On Tue, Nov 4, 2008 at 8:47 AM, Adam McDougall wrote: > Eduardo Meyer wrote: >> >> Hello, >> >> I have some serious issue. Sometimes something happens and my disk >> usage performance find its limit quickly. I follow with gstat and >> iostat -xw1, and everything usually happens just fine, with %b around >> 20 and 0 to 1 pending i/o request. Suddely I get 30, 40 pending >> requests and %b is always on 100% (or more than this). >> >> fstat and lsof gives me no hint, because the type of programs as well >> as the amount of 'em is just the same. >> >> How can I find the PID which is hammering my disk? Is there an "iotop" >> or "disktop" tool or something alike? >> >> Its a mail server. I have pop3, imap, I also have maildrop and >> sometimes, httpd, working around the busiest mount point. >> >> I have also started AUDIT, however all I can get are the top PIDs >> which issue read/write requests. Not the requests which take longer to >> perform (the busiest ones), or should I look for some special audit >> class or event other than open, read and write? >> >> Thank you in advance. >> >> > > top -mio > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > I learn something new everyday on this list...! -- Brent Jones brent@servuhome.net From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 20:02:29 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63DD71065688 for ; Wed, 12 Nov 2008 20:02:29 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: from mail4.sea5.speakeasy.net (mail4.sea5.speakeasy.net [69.17.117.6]) by mx1.freebsd.org (Postfix) with ESMTP id 3C54D8FC14 for ; Wed, 12 Nov 2008 20:02:29 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: (qmail 16328 invoked from network); 12 Nov 2008 20:02:28 -0000 Received: from aldan.algebra.com (HELO [127.0.0.1]) (mi@[216.254.65.224]) (envelope-sender ) by mail4.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 12 Nov 2008 20:02:28 -0000 Message-ID: <491B3653.5080209@aldan.algebra.com> Date: Wed, 12 Nov 2008 15:02:27 -0500 From: Mikhail Teterin User-Agent: Thunderbird 2.0.0.17 (X11/20080914) MIME-Version: 1.0 To: Daniel Eischen References: <491B1BD2.4050903@aldan.algebra.com> <20081112194350.GJ47073@deviant.kiev.zoral.com.ua> <491B3270.5080402@aldan.algebra.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , stable@freebsd.org Subject: Re: dlopen-ing a library with OpenMP by a non-OpenMP process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 20:02:29 -0000 Sent by Daniel Eischen: > On Wed, 12 Nov 2008, Mikhail Teterin wrote: > >> Sent by Kostik Belousov: >>> On Wed, Nov 12, 2008 at 01:09:22PM -0500, Mikhail Teterin wrote: >>> >>>> Hello! >>>> >>>> Currently, when a program built without OpenMP (-fopenmp) is trying >>>> to dlopen a library, built with the feature, the result is a crash >>>> from "bad system call": >>>> >>>> #0 0x00000008009a223c in ksem_init () from /lib/libc.so.7 >>>> #1 0x0000000800998a8f in sem_init () from /lib/libc.so.7 >> Uhm... That worked... I see... Shouldn't sem_init be nicer about it, >> though? Thanks, > Or perhaps you should read sem(4) ;-) Daniel, what are saying? That it is all my own fault? Generic kernel does not have sem in it... I build a port with an option (OpenMP), that make perfect sense, and try to use it. Software crashes... There is a bug -- and you, instead of contemplating a fix, are telling me to read a man-page? Wow... -mi From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 20:12:58 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45C201065677 for ; Wed, 12 Nov 2008 20:12:58 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id E91568FC14 for ; Wed, 12 Nov 2008 20:12:57 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id mACKCt1B022643; Wed, 12 Nov 2008 15:12:55 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Wed, 12 Nov 2008 15:12:55 -0500 (EST) Date: Wed, 12 Nov 2008 15:12:55 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Mikhail Teterin In-Reply-To: <491B3653.5080209@aldan.algebra.com> Message-ID: References: <491B1BD2.4050903@aldan.algebra.com> <20081112194350.GJ47073@deviant.kiev.zoral.com.ua> <491B3270.5080402@aldan.algebra.com> <491B3653.5080209@aldan.algebra.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Kostik Belousov , stable@freebsd.org Subject: Re: dlopen-ing a library with OpenMP by a non-OpenMP process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 20:12:58 -0000 On Wed, 12 Nov 2008, Mikhail Teterin wrote: > Sent by Daniel Eischen: >> On Wed, 12 Nov 2008, Mikhail Teterin wrote: >> >>> Sent by Kostik Belousov: >>>> On Wed, Nov 12, 2008 at 01:09:22PM -0500, Mikhail Teterin wrote: >>>> >>>>> Hello! >>>>> >>>>> Currently, when a program built without OpenMP (-fopenmp) is trying to >>>>> dlopen a library, built with the feature, the result is a crash from >>>>> "bad system call": >>>>> >>>>> #0 0x00000008009a223c in ksem_init () from /lib/libc.so.7 >>>>> #1 0x0000000800998a8f in sem_init () from /lib/libc.so.7 >>> Uhm... That worked... I see... Shouldn't sem_init be nicer about it, >>> though? Thanks, >> Or perhaps you should read sem(4) ;-) > Daniel, what are saying? That it is all my own fault? Generic kernel does not > have sem in it... I build a port with an option (OpenMP), that make perfect > sense, and try to use it. Software crashes... > There is a bug -- and you, instead of contemplating a fix, are telling me to > read a man-page? Wow... No, I simply meant that you saw it was returning bad system call from sem_init/ksem_init. A little investigation would have turned up the reason. If you want to debate whether or not P1003_1B_SEMAPHORES should be standard, that is another issue, which I might actually agree with. -- DE From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 20:13:53 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4900F106564A for ; Wed, 12 Nov 2008 20:13:53 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id ED5988FC2A for ; Wed, 12 Nov 2008 20:13:52 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id mACJq3mM010503; Wed, 12 Nov 2008 14:52:03 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Wed, 12 Nov 2008 14:52:03 -0500 (EST) Date: Wed, 12 Nov 2008 14:52:03 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Mikhail Teterin In-Reply-To: <491B3270.5080402@aldan.algebra.com> Message-ID: References: <491B1BD2.4050903@aldan.algebra.com> <20081112194350.GJ47073@deviant.kiev.zoral.com.ua> <491B3270.5080402@aldan.algebra.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Kostik Belousov , stable@freebsd.org Subject: Re: dlopen-ing a library with OpenMP by a non-OpenMP process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 20:13:53 -0000 On Wed, 12 Nov 2008, Mikhail Teterin wrote: > Sent by Kostik Belousov: >> On Wed, Nov 12, 2008 at 01:09:22PM -0500, Mikhail Teterin wrote: >> >>> Hello! >>> >>> Currently, when a program built without OpenMP (-fopenmp) is trying to >>> dlopen a library, built with the feature, the result is a crash from "bad >>> system call": >>> >>> #0 0x00000008009a223c in ksem_init () from /lib/libc.so.7 >>> #1 0x0000000800998a8f in sem_init () from /lib/libc.so.7 >>> #2 0x00000008011a6537 in omp_get_nested () from /usr/lib/libgomp.so.1 >>> #3 0x00000008011a3466 in ?? () from /usr/lib/libgomp.so.1 >>> #4 0x0000000000000002 in ?? () >>> #5 0x00000008005072b2 in dlsym () from /libexec/ld-elf.so.1 >>> #6 0x0000000800507cd2 in dlopen () from /libexec/ld-elf.so.1 >>> ... >>> >> Try "kldload sem". >> > Uhm... That worked... I see... Shouldn't sem_init be nicer about it, though? > Thanks, Or perhaps you should read sem(4) ;-) -- DE From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 20:22:18 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46104106564A for ; Wed, 12 Nov 2008 20:22:18 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: from mail2.sea5.speakeasy.net (mail2.sea5.speakeasy.net [69.17.117.4]) by mx1.freebsd.org (Postfix) with ESMTP id 1F6CD8FC16 for ; Wed, 12 Nov 2008 20:22:17 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: (qmail 5159 invoked from network); 12 Nov 2008 20:22:13 -0000 Received: from aldan.algebra.com (HELO [127.0.0.1]) (mi@[216.254.65.224]) (envelope-sender ) by mail2.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 12 Nov 2008 20:22:12 -0000 Message-ID: <491B3AF3.9020606@aldan.algebra.com> Date: Wed, 12 Nov 2008 15:22:11 -0500 From: Mikhail Teterin User-Agent: Thunderbird 2.0.0.17 (X11/20080914) MIME-Version: 1.0 To: Daniel Eischen References: <491B1BD2.4050903@aldan.algebra.com> <20081112194350.GJ47073@deviant.kiev.zoral.com.ua> <491B3270.5080402@aldan.algebra.com> <491B3653.5080209@aldan.algebra.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , stable@freebsd.org Subject: Re: dlopen-ing a library with OpenMP by a non-OpenMP process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 20:22:18 -0000 Sent by Daniel Eischen: > No, I simply meant that you saw it was returning bad system > call from sem_init/ksem_init. Instead, I suspected, that it is the OpenMP, that's at fault. I'm sorry for failing to live up to your expectations of a true FreeBSD user. > A little investigation would have turned up the reason. If you want > to debate whether or > not P1003_1B_SEMAPHORES should be standard, that is another > issue, which I might actually agree with. Well, I'm sure, the debate on including P1003_1B_SEMAPHORES by default has already raged before... No, what I was suggesting, was that sem_init -- not the system call, but the C-function -- should be more intelligent in detecting such situations and reporting them instead of crashing... Either the C-function, or, maybe, the no-op implementation of (k)sem_init in the kernel ought to have told me (even if only in the kernel log), that I need to kldload sem and refer to the man-page. That's what well-integrated Operating Systems do, anyway... -mi From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 20:28:40 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 879D81065670 for ; Wed, 12 Nov 2008 20:28:40 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 26FA28FC0C for ; Wed, 12 Nov 2008 20:28:40 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1L0Ld3-0001N1-SA; Wed, 12 Nov 2008 21:43:54 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mACJhonb044824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Nov 2008 21:43:50 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id mACJhos2092609; Wed, 12 Nov 2008 21:43:50 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mACJhop0092608; Wed, 12 Nov 2008 21:43:50 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 12 Nov 2008 21:43:50 +0200 From: Kostik Belousov To: Mikhail Teterin Message-ID: <20081112194350.GJ47073@deviant.kiev.zoral.com.ua> References: <491B1BD2.4050903@aldan.algebra.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NqSa+Xr3J/G6Hhls" Content-Disposition: inline In-Reply-To: <491B1BD2.4050903@aldan.algebra.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1L0Ld3-0001N1-SA f8f666efc8f22a52587f8eb4c15082c3 X-Terabit: YES Cc: stable@freebsd.org Subject: Re: dlopen-ing a library with OpenMP by a non-OpenMP process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 20:28:40 -0000 --NqSa+Xr3J/G6Hhls Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 12, 2008 at 01:09:22PM -0500, Mikhail Teterin wrote: > Hello! >=20 > Currently, when a program built without OpenMP (-fopenmp) is trying to=20 > dlopen a library, built with the feature, the result is a crash from=20 > "bad system call": >=20 > #0 0x00000008009a223c in ksem_init () from /lib/libc.so.7 > #1 0x0000000800998a8f in sem_init () from /lib/libc.so.7 > #2 0x00000008011a6537 in omp_get_nested () from /usr/lib/libgomp.so.1 > #3 0x00000008011a3466 in ?? () from /usr/lib/libgomp.so.1 > #4 0x0000000000000002 in ?? () > #5 0x00000008005072b2 in dlsym () from /libexec/ld-elf.so.1 > #6 0x0000000800507cd2 in dlopen () from /libexec/ld-elf.so.1 > ... >=20 > Can anything be done about this -- disable the OpenMP functionality, but= =20 > keep the library usable (single-threaded)? The problem arises, in=20 > particular, when one is trying to use libraries built by either=20 > GraphicsMagick or ImageMagick ports. Both have an OpenMP option, which=20 > speeds up some internal algorithms. The option is off by default, but=20 > enabling it makes sense on an SMP system... Yet, this makes the library= =20 > unsuitable for other purposes... Thanks! Yours, >=20 > -mi >=20 > P.S. I'm seeing the crash on a recent FreeBSD-7.1/amd64, but it, likely,= =20 > can be seen elsewhere. Try "kldload sem". --NqSa+Xr3J/G6Hhls Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkkbMfUACgkQC3+MBN1Mb4jC2QCfTqeWHXbsp+uA7ox4/JwzZuvt HaIAnAr1TCaRKa/mR+Dd9ypbVso04NAI =1eJf -----END PGP SIGNATURE----- --NqSa+Xr3J/G6Hhls-- From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 20:37:07 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEBA21065673 for ; Wed, 12 Nov 2008 20:37:07 +0000 (UTC) (envelope-from pmurray@nevada.net.nz) Received: from bellagio.open2view.net (bellagio.open2view.net [210.48.79.75]) by mx1.freebsd.org (Postfix) with ESMTP id 825628FC0A for ; Wed, 12 Nov 2008 20:37:07 +0000 (UTC) (envelope-from pmurray@nevada.net.nz) Received: from treasure-2.office.open2view.com (ip-58-28-153-152.static-xdsl.xnet.co.nz [58.28.153.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by bellagio.open2view.net (Postfix) with ESMTP id 452DB1101AE0; Thu, 13 Nov 2008 09:37:06 +1300 (NZDT) Message-Id: <95E9EA2C-C288-4F11-AD35-FE6AF6633A09@nevada.net.nz> From: Philip Murray To: Oliver Lehmann In-Reply-To: <20081112204351.ccc51c2f.lehmann@ans-netz.de> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Thu, 13 Nov 2008 09:37:03 +1300 References: <20081029170728.be7cc7ab.lehmann@ans-netz.de> <13394481-8FDC-4934-BB12-FA5BCB2D35CD@nevada.net.nz> <20081112204351.ccc51c2f.lehmann@ans-netz.de> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-stable@freebsd.org Subject: Re: 3Ware 9000 series hangs under load X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 20:37:07 -0000 On 13/11/2008, at 8:43 AM, Oliver Lehmann wrote: > Philip Murray wrote: > >> I used to get this (FreeBSD 6.1 days) all the time, the controller >> would just lock up almost on a daily basis (and have to wait for the >> fsck 4 out of 24 hours in the day). >> >> Anyway, I stopped running 3dmd (or 3dm2 I think it's called now) to >> monitor it, and the crashes went away. It's had hundreds of days >> uptime since. >> >> I've never been game enough to try newer versions of 3dm, but a >> cronjob of tw_cli allows me to monitor it now without the lockups. >> >> Might not be your problem, but it's worth a shot if all else fails. > > Ok, it realy looks, like 3dm2 is causing the same problems here too. > > I've tried several 3dm2 versions and beginning with the version > released > with 9.1.5.2 the system is crashing on high i/o loads. The previous > release included in 9.0.1 and 9.0.2 (made in 2004 iirc) is not > crashing. > Every release which was made later causes system crashes as well. > > I'll see what the support staff responds to that.... > > What cronjobs are you running in particlular to "replace" 3dm2? > I just installed sysutils/tw_cli from ports, and it sets up some 'periodic' scripts for you. To be precise it puts 407.status-3ware- raid in /usr/local/etc/periodic/daily Cheers Phil From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 21:05:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 139EE1065676 for ; Wed, 12 Nov 2008 21:05:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id A6F538FC1D for ; Wed, 12 Nov 2008 21:05:20 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1L0Mtq-0008Rz-GU; Wed, 12 Nov 2008 23:05:18 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mACL5FbL048992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Nov 2008 23:05:15 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id mACL5FkB095168; Wed, 12 Nov 2008 23:05:15 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mACL5DM6095167; Wed, 12 Nov 2008 23:05:13 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 12 Nov 2008 23:05:13 +0200 From: Kostik Belousov To: Tim Bishop Message-ID: <20081112210513.GM47073@deviant.kiev.zoral.com.ua> References: <20081112175826.GD26195@carrick.bishnet.net> <20081112194928.GA19539@carrick.bishnet.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4ybNbZnZ8tziJ7D6" Content-Disposition: inline In-Reply-To: <20081112194928.GA19539@carrick.bishnet.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1L0Mtq-0008Rz-GU 2b2ec70661d736076d77d7f5ac614eca X-Terabit: YES Cc: Tim Bishop , Jeremy Chadwick , freebsd-stable@freebsd.org, David Peall Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 21:05:21 -0000 --4ybNbZnZ8tziJ7D6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 12, 2008 at 07:49:28PM +0000, Tim Bishop wrote: > On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: > > I run the mksnap_ffs command to take the snapshot and some time later > > the system completely freezes up: > >=20 > > paladin# cd /u2/.snap/ > > paladin# mksnap_ffs /u2 test.1 >=20 > Someone (not named because they choose not to reply to the list) gave me > the following patch: >=20 > --- sys/ufs/ffs/ffs_snapshot.c.orig Wed Mar 22 09:42:31 2006 > +++ sys/ufs/ffs/ffs_snapshot.c Mon Nov 20 14:59:13 2006 > @@ -282,6 +282,8 @@ restart: > if (error) > goto out; > bawrite(nbp); > + if (cg % 10 =3D=3D 0) > + ffs_syncvnode(vp, MNT_WAIT); > } > /* > * Copy all the cylinder group maps. Although the > @@ -303,6 +305,8 @@ restart: > goto out; > error =3D cgaccount(cg, vp, nbp, 1); > bawrite(nbp); > + if (cg % 10 =3D=3D 0) > + ffs_syncvnode(vp, MNT_WAIT); > if (error) > goto out; > } >=20 > With the description: >=20 > "What can happen is on a big file system it will fill up the buffer > cache with I/O and then run out. When the buffer cache fills up then no > more disk I/O can happen :-( When you do a sync, it flushes that out to > disk so things don't hang." >=20 > It seems to work too. But it seems more like a workaround than a fix? It looks hackish, but in fact it is not that wrong, and I even say that it provides reasonable workaround. The usual way to prevent wdrain deadlock is to issue bwillwrite() call before any vnode lock is taken. This is sufficient for most VFS syscalls that typically put dozen or less dirty buffers into delayed write queue. Snapshot creation does not call bwillwrite() at all, and then does a lot of async writes, completely saturating buffer cache with dirty buffers. bwillwrite cannot be called after the vnode is locked, and just forcing a sync for the embrionic snapshot vnode is good enough. The 10 counter is debatable, but debate shall be postponed until the patch goes into tree. I ask an anonymous submitter to commit it. Thanks ! --4ybNbZnZ8tziJ7D6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkkbRQkACgkQC3+MBN1Mb4iecwCg6wKWEMcVZ30HMLCc9kfE1J9h 6gcAnRyVqnhKYTph1pEUD4ao1OyNOkR6 =Uvcf -----END PGP SIGNATURE----- --4ybNbZnZ8tziJ7D6-- From owner-freebsd-stable@FreeBSD.ORG Wed Nov 12 22:43:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 100CF1065686 for ; Wed, 12 Nov 2008 22:43:02 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id B74E48FC08 for ; Wed, 12 Nov 2008 22:43:01 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 4210 invoked by uid 399); 12 Nov 2008 22:43:01 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 12 Nov 2008 22:43:01 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <491B5BF3.1010309@FreeBSD.org> Date: Wed, 12 Nov 2008 14:42:59 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.17 (X11/20081010) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.95.7 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: RELENG_7 build failure in rescue/ (iconv?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 22:43:02 -0000 I'm getting the following with clean, up to date sources (with the BIND 9.4.2-P2 update, but that doesn't touch this area): cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo pax.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh.lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo bsdlabel.lo camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo gbde.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo mount_ntfs.lo mount_nullfs.lo mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo slattach.lo spppcontrol.lo startslip.lo swapon.lo sysctl.lo tunefs.lo umount.lo atmconfig.lo ping6.lo ipf.lo sconfig.lo fdisk.lo dhclient.lo gzip.lo bzip2.lo tar.lo vi.lo id.lo chroot.lo /dumpster/home/dougb/src/rescue/rescue/../librescue/exec.o /dumpster/home/dougb/src/rescue/rescue/../librescue/getusershell.o /dumpster/home/dougb/src/rescue/rescue/../librescue/login_class.o /dumpster/home/dougb/src/rescue/rescue/../librescue/popen.o /dumpster/home/dougb/src/rescue/rescue/../librescue/rcmdsh.o /dumpster/home/dougb/src/rescue/rescue/../librescue/sysctl.o /dumpster/home/dougb/src/rescue/rescue/../librescue/system.o -lcrypt -ledit -lkvm -ll -lm -ltermcap -lutil -lcrypto -lalias -lcam -lcurses -ldevstat -lipsec -lipx -lgeom -lbsdxml -lkiconv -lmd -lreadline -lsbuf -lufs -lz -lbz2 -larchive csh.lo(.text+0xd4c9): In function `nlsclose': : undefined reference to `dl_iconv_close' csh.lo(.text+0xd626): In function `nlsinit': : undefined reference to `dl_iconv_open' csh.lo(.text+0xd716): In function `iconv_catgets': : undefined reference to `dl_iconv' *** Error code 1 Stop in /dumpster/home/dougb/src/rescue/rescue. *** Error code 1 -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 00:41:11 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 592351065670 for ; Thu, 13 Nov 2008 00:41:11 +0000 (UTC) (envelope-from tdb@carrick.bishnet.net) Received: from carrick.bishnet.net (carrick.bishnet.net [IPv6:2a01:348:132::1]) by mx1.freebsd.org (Postfix) with ESMTP id 156908FC0C for ; Thu, 13 Nov 2008 00:41:10 +0000 (UTC) (envelope-from tdb@carrick.bishnet.net) Received: from tdb by carrick.bishnet.net with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1L0QGc-000AB1-J1; Thu, 13 Nov 2008 00:41:02 +0000 Date: Thu, 13 Nov 2008 00:41:02 +0000 From: Tim Bishop To: Kostik Belousov Message-ID: <20081113004102.GD24360@carrick.bishnet.net> References: <20081112175826.GD26195@carrick.bishnet.net> <20081112194735.GK47073@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081112194735.GK47073@deviant.kiev.zoral.com.ua> X-PGP-Key: 0x5AE7D984, http://www.bishnet.net/tim/tim-bishnet-net.asc X-PGP-Fingerprint: 1453 086E 9376 1A50 ECF6 AE05 7DCE D659 5AE7 D984 User-Agent: Mutt/1.5.13 (2006-08-11) X-Bishnet-MailScanner-Information: Contact postmaster@bishnet.net X-Bishnet-MailScanner-VirusCheck: Found to be clean X-Bishnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1.01, required 5, BAYES_00 -2.60, DNS_FROM_SECURITYSAGE 1.51, NO_RELAYS -0.00, TW_DV 0.08) X-Bishnet-MailScanner-From: tdb@carrick.bishnet.net Cc: Tim Bishop , freebsd-stable@freebsd.org Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 00:41:11 -0000 On Wed, Nov 12, 2008 at 09:47:35PM +0200, Kostik Belousov wrote: > On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: > > I've been playing around with snapshots lately but I've got a problem on > > one of my servers running 7-STABLE amd64: > > > > FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 > > > > I run the mksnap_ffs command to take the snapshot and some time later > > the system completely freezes up: > > > > paladin# cd /u2/.snap/ > > paladin# mksnap_ffs /u2 test.1 > > > > It only happens on this one filesystem, though, which might be to do > > with its size. It's not over the 2TB marker, but it's pretty close. It's > > also backed by a hardware RAID system, although a smaller filesystem on > > the same RAID has no issues. > > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > /dev/da0s1a 2078881084 921821396 990749202 48% /u2 > > > > To clarify "completely freezes up": unresponsive to all services over > > the network, except ping. On the console I can switch between the ttys, > > but none of them respond. The only way out is to hit the reset button. > > You need to provide information described in the > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html > and especially > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html Ok, I've done that, and removed the patch that seemed to fix things. The first thing I notice after doing this on the console is that I can still ctrl+t the process: load: 0.14 cmd: mksnap_ffs 2603 [newbuf] 0.00u 10.75s 0% 1160k But the top and ps I left running on other ttys have all stopped responding. Also the following kernel message came out: Expensive timeout(9) function: 0xffffffff802ce380(0xffffff000677ca50) 0.006121001 s There is also still some disk I/O. Dropping to ddb worked, but I don't have a serial console so I can't paste the output. ps shows mksnap_ffs in newbuf, as we already saw. A trace of mksnap_ffs looks like this: Tracing pid 2603 tid 100214 td 0xffffff0006a0e370 sched_switch() at sched_switch+0x2a1 mi_switch() at mi_switch+0x233 sleepq_switch() at sleepq_switch+0xe9 sleepq_wait() at sleepq_wait+0x44 _sleep() at _sleep+0x351 getnewbuf() at getnewbuf+0x2e1 getblk() at getblk+0x30d setup_allocindir_phase2() at setup_allocindir_phase2+0x338 softdep_setup_allocindir_page() at softdep_setup_allocindir_page+0xa7 ffs_balloc_ufs2() at ffs_balloc_ufs2+0x121e ffs_snapshot() at ffs_snapshot+0xc52 ffs_mount() at ffs_mount+0x735 vfs_donmount() at vfs_donmount+0xeb5 kernel_mount() at kernel_mount+0xa1 ffs_cmount() at ffs_cmount+0x92 mount() at mount+0x1cc syscall() at syscall+0x1f6 Xfast_syscall() at Xfast_syscall+0xab --- syscall (21, FreeBSD ELF64, mount), rip = 0x80068636c, rsp = 0x7fffffffe518, rbp = 0x8008447a0 --- show pcpu shows cpuid 3 (quad core machine) in thread "swi6: Giant taskq". All the other cpus are idle. show locks shows: exclusive sleep mutex Giant r = 0 (0xffffffff806ae040) locked @ /usr/src/sys/kern/kern_intr.c:1087 There are two other locks shown by show all locks, one for sshd and one for mysqld, both in kern/uipc_sockbuf.c. show lockedvnods shows mksnap_ffs has a lock on da0s1a with ffs_vget at the top of the stack. Sorry for any typos. I'll sort out a serial cable if more is needed :-) Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 04:42:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A826106568E for ; Thu, 13 Nov 2008 04:42:03 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by mx1.freebsd.org (Postfix) with ESMTP id 9F6F48FC0C for ; Thu, 13 Nov 2008 04:42:02 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA06.westchester.pa.mail.comcast.net ([76.96.62.51]) by QMTA10.westchester.pa.mail.comcast.net with comcast id eQcQ1a00216LCl05AUhv1L; Thu, 13 Nov 2008 04:41:55 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA06.westchester.pa.mail.comcast.net with comcast id eUi01a0092P6wsM3SUi1do; Thu, 13 Nov 2008 04:42:01 +0000 X-Authority-Analysis: v=1.0 c=1 a=becna3ql8DEA:10 a=0kYo9GeZAlkA:10 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=sXe4QNHIKnmKmJ6EUnYA:9 a=-1gQyhJPHkhTO0luNUoA:7 a=EgV_WFJMUN-DIFrQ-TUXSWV3VlkA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 61D065C19; Wed, 12 Nov 2008 20:42:00 -0800 (PST) Date: Wed, 12 Nov 2008 20:42:00 -0800 From: Jeremy Chadwick To: Tim Bishop Message-ID: <20081113044200.GA10419@icarus.home.lan> References: <20081112175826.GD26195@carrick.bishnet.net> <20081112194735.GK47073@deviant.kiev.zoral.com.ua> <20081113004102.GD24360@carrick.bishnet.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081113004102.GD24360@carrick.bishnet.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Kostik Belousov , Tim Bishop , freebsd-stable@freebsd.org Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 04:42:03 -0000 On Thu, Nov 13, 2008 at 12:41:02AM +0000, Tim Bishop wrote: > On Wed, Nov 12, 2008 at 09:47:35PM +0200, Kostik Belousov wrote: > > On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: > > > I've been playing around with snapshots lately but I've got a problem on > > > one of my servers running 7-STABLE amd64: > > > > > > FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 > > > > > > I run the mksnap_ffs command to take the snapshot and some time later > > > the system completely freezes up: > > > > > > paladin# cd /u2/.snap/ > > > paladin# mksnap_ffs /u2 test.1 > > > > > > It only happens on this one filesystem, though, which might be to do > > > with its size. It's not over the 2TB marker, but it's pretty close. It's > > > also backed by a hardware RAID system, although a smaller filesystem on > > > the same RAID has no issues. > > > > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > > /dev/da0s1a 2078881084 921821396 990749202 48% /u2 > > > > > > To clarify "completely freezes up": unresponsive to all services over > > > the network, except ping. On the console I can switch between the ttys, > > > but none of them respond. The only way out is to hit the reset button. > > > > You need to provide information described in the > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html > > and especially > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html > > Ok, I've done that, and removed the patch that seemed to fix things. > > The first thing I notice after doing this on the console is that I can > still ctrl+t the process: > > load: 0.14 cmd: mksnap_ffs 2603 [newbuf] 0.00u 10.75s 0% 1160k > > But the top and ps I left running on other ttys have all stopped > responding. Then in my book, the patch didn't fix anything. :-) The system is still "deadlocking"; snapshot generation **should not** wedge the system hard like this. Also, during my own testing, I am always able to use Ctrl-T to get SIGINFO from the running process (mksnap_ffs). That behaviour does not change for me. The rest of the below information is good -- but I'm confused about something: is there anyone out there who can use mksnap_ffs on a filesystem (/usr is a good test source) and NOT experience this deadlocking problem? Literally *every* FreeBSD box I have root access to suffers from this problem, so I'm a little baffled why we end-users need to keep providing debugging output when it should be easy as pie for a developer to do "dump -0 -L -a -f /path/fs.dump /usr" and watch their system wedge. Also, a fellow on -fs just mentioned he's having this exact problem: http://lists.freebsd.org/pipermail/freebsd-fs/2008-November/005324.html > Also the following kernel message came out: > > Expensive timeout(9) function: 0xffffffff802ce380(0xffffff000677ca50) 0.006121001 s > > There is also still some disk I/O. > > Dropping to ddb worked, but I don't have a serial console so I can't > paste the output. > > ps shows mksnap_ffs in newbuf, as we already saw. A trace of mksnap_ffs > looks like this: > > Tracing pid 2603 tid 100214 td 0xffffff0006a0e370 > sched_switch() at sched_switch+0x2a1 > mi_switch() at mi_switch+0x233 > sleepq_switch() at sleepq_switch+0xe9 > sleepq_wait() at sleepq_wait+0x44 > _sleep() at _sleep+0x351 > getnewbuf() at getnewbuf+0x2e1 > getblk() at getblk+0x30d > setup_allocindir_phase2() at setup_allocindir_phase2+0x338 > softdep_setup_allocindir_page() at softdep_setup_allocindir_page+0xa7 > ffs_balloc_ufs2() at ffs_balloc_ufs2+0x121e > ffs_snapshot() at ffs_snapshot+0xc52 > ffs_mount() at ffs_mount+0x735 > vfs_donmount() at vfs_donmount+0xeb5 > kernel_mount() at kernel_mount+0xa1 > ffs_cmount() at ffs_cmount+0x92 > mount() at mount+0x1cc > syscall() at syscall+0x1f6 > Xfast_syscall() at Xfast_syscall+0xab > --- syscall (21, FreeBSD ELF64, mount), rip = 0x80068636c, rsp = 0x7fffffffe518, rbp = 0x8008447a0 --- > > show pcpu shows cpuid 3 (quad core machine) in thread "swi6: Giant taskq". > All the other cpus are idle. > > show locks shows: > > exclusive sleep mutex Giant r = 0 (0xffffffff806ae040) locked @ /usr/src/sys/kern/kern_intr.c:1087 > > There are two other locks shown by show all locks, one for sshd and one > for mysqld, both in kern/uipc_sockbuf.c. > > show lockedvnods shows mksnap_ffs has a lock on da0s1a with ffs_vget at > the top of the stack. > > Sorry for any typos. I'll sort out a serial cable if more is needed :-) > > Tim. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 05:00:53 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD467106564A; Thu, 13 Nov 2008 05:00:53 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.freebsd.org (Postfix) with ESMTP id 96A048FC17; Thu, 13 Nov 2008 05:00:53 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) X-Ambrisko-Me: Yes Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by ironport.ambrisko.com with ESMTP; 12 Nov 2008 21:01:04 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.14.1/8.14.1) with ESMTP id mAD50rcG051931; Wed, 12 Nov 2008 21:00:53 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.14.1/8.14.1/Submit) id mAD50rqt051930; Wed, 12 Nov 2008 21:00:53 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200811130500.mAD50rqt051930@ambrisko.com> In-Reply-To: <20081113044200.GA10419@icarus.home.lan> To: Jeremy Chadwick Date: Wed, 12 Nov 2008 21:00:53 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: Kostik Belousov , Tim Bishop , freebsd-stable@freebsd.org Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 05:00:53 -0000 Jeremy Chadwick writes: [snip] | The rest of the below information is good -- but I'm confused about | something: is there anyone out there who can use mksnap_ffs on a | filesystem (/usr is a good test source) and NOT experience this | deadlocking problem? Literally *every* FreeBSD box I have root access | to suffers from this problem, so I'm a little baffled why we end-users | need to keep providing debugging output when it should be easy as pie | for a developer to do "dump -0 -L -a -f /path/fs.dump /usr" and watch | their system wedge. We can at work, but we have a bunch of other patches. There are a few problems with the buffer cache: 1) The buffer daemon can't use the space that is reserved for it since to flush some stuff it needs to use more buffers. 2) The buffer cache can get fragmented to prevent large I/O which the buffer daemon may need. 3) Other issues ... I have fix for "1". It is pretty easy. I have a hack'ish fix for "2" in the I make all request use max size so it can't get fragmented since there is no code to defrag and it isn't trivial to defrag the memory. I have some fixes for some other issues, but there were some review issues with them. I might just commit the fixes for 1 and 2. It makes things better and there was no-objections at the time. We have the patches in shipping products. I can try to do some experiments at work like you said since I had similar things working before and it is pretty easy to put in printf's to see the issue. Doug A. From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 05:02:59 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C60211065674 for ; Thu, 13 Nov 2008 05:02:59 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.freebsd.org (Postfix) with ESMTP id 7B76D8FC08 for ; Thu, 13 Nov 2008 05:02:59 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id mAD52o9M079635; Wed, 12 Nov 2008 21:02:50 -0800 (PST) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id mAD52ovK079634; Wed, 12 Nov 2008 21:02:50 -0800 (PST) (envelope-from david) Date: Wed, 12 Nov 2008 21:02:50 -0800 From: David Wolfskill To: Jeremy Chadwick Message-ID: <20081113050250.GR69155@bunrab.catwhisker.org> Mail-Followup-To: David Wolfskill , Jeremy Chadwick , Tim Bishop , Kostik Belousov , freebsd-stable@freebsd.org References: <20081112175826.GD26195@carrick.bishnet.net> <20081112194735.GK47073@deviant.kiev.zoral.com.ua> <20081113004102.GD24360@carrick.bishnet.net> <20081113044200.GA10419@icarus.home.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qBjqo5c+GoerLc/a" Content-Disposition: inline In-Reply-To: <20081113044200.GA10419@icarus.home.lan> User-Agent: Mutt/1.4.2.1i Cc: Kostik Belousov , freebsd-stable@freebsd.org Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 05:02:59 -0000 --qBjqo5c+GoerLc/a Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 12, 2008 at 08:42:00PM -0800, Jeremy Chadwick wrote: > ... > > > On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: > > > > I've been playing around with snapshots lately but I've got a probl= em on > > > > one of my servers running 7-STABLE amd64: > > > >=20 > > > > FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 1= 0 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 > > > >=20 > > > > I run the mksnap_ffs command to take the snapshot and some time lat= er > > > > the system completely freezes up: > > > >=20 > > > > paladin# cd /u2/.snap/ > > > > paladin# mksnap_ffs /u2 test.1 > > > >=20 > > > > It only happens on this one filesystem, though, which might be to do > > > > with its size. It's not over the 2TB marker, but it's pretty close.= It's > > > > also backed by a hardware RAID system, although a smaller filesyste= m on > > > > the same RAID has no issues. > ... > Then in my book, the patch didn't fix anything. :-) The system is > still "deadlocking"; snapshot generation **should not** wedge the system > hard like this. >=20 > Also, during my own testing, I am always able to use Ctrl-T to get > SIGINFO from the running process (mksnap_ffs). That behaviour does not > change for me. >=20 > The rest of the below information is good -- but I'm confused about > something: is there anyone out there who can use mksnap_ffs on a > filesystem (/usr is a good test source) and NOT experience this > deadlocking problem? I hadn't ever tried until I saw your message. Granted, I'm using a smaller file system (I doubt that I have a toital of as much as 2 TB in all my machines combined), and I'm running i386, vs. amd64. But it ran just fine. I wasn't able to test SIGINFO; it finished before I had a chance. (I ran it under time(1); wall clock time was 0.91 sec.) > Literally *every* FreeBSD box I have root access > to suffers from this problem, so I'm a little baffled why we end-users > need to keep providing debugging output when it should be easy as pie > for a developer to do "dump -0 -L -a -f /path/fs.dump /usr" and watch > their system wedge. Well, I routinely use dump/restore pipelines to copy file systems around; never had a problem with it. > ... For reference: freebeast(7.1-P)[9] uname -a FreeBSD freebeast.catwhisker.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #127= : Wed Nov 12 05:16:20 PST 2008 root@freebeast.catwhisker.org:/common/S3= /obj/usr/src/sys/FREEBEAST i386 freebeast(7.1-P)[10] ls -la total 4 drwxrwxr-x 2 root operator 512 Nov 12 20:53 . drwxr-xr-x 14 root wheel 512 Jan 22 2008 .. freebeast(7.1-P)[11] /usr/bin/time -l mksnap_ffs /S2/usr test.1 0.91 real 0.00 user 0.05 sys 976 maximum resident set size 3 average shared memory size 627 average unshared data size 109 average unshared stack size 104 page reclaims 0 page faults 0 swaps 1 block input operations 230 block output operations 0 messages sent 0 messages received 0 signals received 101 voluntary context switches 34 involuntary context switches freebeast(7.1-P)[12] ls -la total 1460 drwxrwxr-x 2 root operator 512 Nov 12 20:54 . drwxr-xr-x 14 root wheel 512 Jan 22 2008 .. -r--r----- 1 root operator 2410791056 Nov 12 20:54 test.1 freebeast(7.1-P)[13]=20 Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --qBjqo5c+GoerLc/a Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAkkbtPkACgkQmprOCmdXAD1gsACeL5KCFvdfWvY/ZhuH4XtEk+Xi WlgAnAzipw8PVs/BQ0baZi++gx5MEEt+ =undU -----END PGP SIGNATURE----- --qBjqo5c+GoerLc/a-- From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 05:16:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E9BF1065695; Thu, 13 Nov 2008 05:16:54 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.freebsd.org (Postfix) with ESMTP id 403E38FC16; Thu, 13 Nov 2008 05:16:54 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) X-Ambrisko-Me: Yes Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by ironport.ambrisko.com with ESMTP; 12 Nov 2008 20:47:49 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.14.1/8.14.1) with ESMTP id mAD4lcVb051138; Wed, 12 Nov 2008 20:47:38 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.14.1/8.14.1/Submit) id mAD4lbJG051137; Wed, 12 Nov 2008 20:47:37 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200811130447.mAD4lbJG051137@ambrisko.com> In-Reply-To: <20081112210513.GM47073@deviant.kiev.zoral.com.ua> To: Kostik Belousov Date: Wed, 12 Nov 2008 20:47:37 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: Tim Bishop , Jeremy Chadwick , freebsd-stable@freebsd.org, David Peall Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 05:16:54 -0000 Kostik Belousov writes: | On Wed, Nov 12, 2008 at 07:49:28PM +0000, Tim Bishop wrote: | > On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: | > > I run the mksnap_ffs command to take the snapshot and some time later | > > the system completely freezes up: | > > | > > paladin# cd /u2/.snap/ | > > paladin# mksnap_ffs /u2 test.1 | > | > Someone (not named because they choose not to reply to the list) gave me | > the following patch: | > | > --- sys/ufs/ffs/ffs_snapshot.c.orig Wed Mar 22 09:42:31 2006 | > +++ sys/ufs/ffs/ffs_snapshot.c Mon Nov 20 14:59:13 2006 | > @@ -282,6 +282,8 @@ restart: | > if (error) | > goto out; | > bawrite(nbp); | > + if (cg % 10 == 0) | > + ffs_syncvnode(vp, MNT_WAIT); | > } | > /* | > * Copy all the cylinder group maps. Although the | > @@ -303,6 +305,8 @@ restart: | > goto out; | > error = cgaccount(cg, vp, nbp, 1); | > bawrite(nbp); | > + if (cg % 10 == 0) | > + ffs_syncvnode(vp, MNT_WAIT); | > if (error) | > goto out; | > } | > | > With the description: | > | > "What can happen is on a big file system it will fill up the buffer | > cache with I/O and then run out. When the buffer cache fills up then no | > more disk I/O can happen :-( When you do a sync, it flushes that out to | > disk so things don't hang." | > | > It seems to work too. But it seems more like a workaround than a fix? | | It looks hackish, but in fact it is not that wrong, and I even say that | it provides reasonable workaround. | | The usual way to prevent wdrain deadlock is to issue bwillwrite() call | before any vnode lock is taken. This is sufficient for most VFS syscalls | that typically put dozen or less dirty buffers into delayed write | queue. | | Snapshot creation does not call bwillwrite() at all, and then does a lot | of async writes, completely saturating buffer cache with dirty buffers. | bwillwrite cannot be called after the vnode is locked, and just forcing | a sync for the embrionic snapshot vnode is good enough. | | The 10 counter is debatable, but debate shall be postponed until the patch | goes into tree. I ask an anonymous submitter to commit it. Thanks ! I plan to commit it tomorrow since I sent it to Tim to test. The 10 can be tuned but it has kept a bunch of machines at work up. Glad people don't think it is that it is to wrong :-) It probably could be made a little more dynamic but I wonder if it would show any real performance difference and might risk more bugs. Doug A. From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 06:05:24 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8F6B106567A for ; Thu, 13 Nov 2008 06:05:24 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by mx1.freebsd.org (Postfix) with ESMTP id 782B78FC13 for ; Thu, 13 Nov 2008 06:05:24 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35]) by QMTA04.westchester.pa.mail.comcast.net with comcast id eW0l1a0070ldTLk54W5Prg; Thu, 13 Nov 2008 06:05:23 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA04.westchester.pa.mail.comcast.net with comcast id eW5N1a0012P6wsM3QW5NP9; Thu, 13 Nov 2008 06:05:23 +0000 X-Authority-Analysis: v=1.0 c=1 a=becna3ql8DEA:10 a=0kYo9GeZAlkA:10 a=QycZ5dHgAAAA:8 a=egB4EsXT1eb4ReCG-SYA:9 a=dGiZFwbhfnmsAMRzhPYA:7 a=vLRwQLkj1NJwhr-uxlfL_IkbME8A:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id E8C275C19; Wed, 12 Nov 2008 22:05:21 -0800 (PST) Date: Wed, 12 Nov 2008 22:05:21 -0800 From: Jeremy Chadwick To: David Wolfskill , Tim Bishop , Kostik Belousov , freebsd-stable@freebsd.org Message-ID: <20081113060521.GA11595@icarus.home.lan> References: <20081112175826.GD26195@carrick.bishnet.net> <20081112194735.GK47073@deviant.kiev.zoral.com.ua> <20081113004102.GD24360@carrick.bishnet.net> <20081113044200.GA10419@icarus.home.lan> <20081113050250.GR69155@bunrab.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081113050250.GR69155@bunrab.catwhisker.org> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 06:05:24 -0000 On Wed, Nov 12, 2008 at 09:02:50PM -0800, David Wolfskill wrote: > On Wed, Nov 12, 2008 at 08:42:00PM -0800, Jeremy Chadwick wrote: > > ... > > > > On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: > > > > > I've been playing around with snapshots lately but I've got a problem on > > > > > one of my servers running 7-STABLE amd64: > > > > > > > > > > FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 > > > > > > > > > > I run the mksnap_ffs command to take the snapshot and some time later > > > > > the system completely freezes up: > > > > > > > > > > paladin# cd /u2/.snap/ > > > > > paladin# mksnap_ffs /u2 test.1 > > > > > > > > > > It only happens on this one filesystem, though, which might be to do > > > > > with its size. It's not over the 2TB marker, but it's pretty close. It's > > > > > also backed by a hardware RAID system, although a smaller filesystem on > > > > > the same RAID has no issues. > > ... > > Then in my book, the patch didn't fix anything. :-) The system is > > still "deadlocking"; snapshot generation **should not** wedge the system > > hard like this. > > > > Also, during my own testing, I am always able to use Ctrl-T to get > > SIGINFO from the running process (mksnap_ffs). That behaviour does not > > change for me. > > > > The rest of the below information is good -- but I'm confused about > > something: is there anyone out there who can use mksnap_ffs on a > > filesystem (/usr is a good test source) and NOT experience this > > deadlocking problem? > > I hadn't ever tried until I saw your message. Granted, I'm using a > smaller file system (I doubt that I have a toital of as much as 2 TB in > all my machines combined), and I'm running i386, vs. amd64. But it ran > just fine. I wasn't able to test SIGINFO; it finished before I had a > chance. (I ran it under time(1); wall clock time was 0.91 sec.) > > > Literally *every* FreeBSD box I have root access > > to suffers from this problem, so I'm a little baffled why we end-users > > need to keep providing debugging output when it should be easy as pie > > for a developer to do "dump -0 -L -a -f /path/fs.dump /usr" and watch > > their system wedge. > > Well, I routinely use dump/restore pipelines to copy file systems > around; never had a problem with it. > > > ... > > For reference: > > freebeast(7.1-P)[9] uname -a > FreeBSD freebeast.catwhisker.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #127: Wed Nov 12 05:16:20 PST 2008 root@freebeast.catwhisker.org:/common/S3/obj/usr/src/sys/FREEBEAST i386 > freebeast(7.1-P)[10] ls -la > total 4 > drwxrwxr-x 2 root operator 512 Nov 12 20:53 . > drwxr-xr-x 14 root wheel 512 Jan 22 2008 .. > freebeast(7.1-P)[11] /usr/bin/time -l mksnap_ffs /S2/usr test.1 > 0.91 real 0.00 user 0.05 sys > 976 maximum resident set size > 3 average shared memory size > 627 average unshared data size > 109 average unshared stack size > 104 page reclaims > 0 page faults > 0 swaps > 1 block input operations > 230 block output operations > 0 messages sent > 0 messages received > 0 signals received > 101 voluntary context switches > 34 involuntary context switches > freebeast(7.1-P)[12] ls -la > total 1460 > drwxrwxr-x 2 root operator 512 Nov 12 20:54 . > drwxr-xr-x 14 root wheel 512 Jan 22 2008 .. > -r--r----- 1 root operator 2410791056 Nov 12 20:54 test.1 > freebeast(7.1-P)[13] David, thanks for chiming in. This is exactly what I was fearing/worried about. It would be greatly beneficial if we could figure out what triggers the slowdown for a lot of us, since for others (proof above) mksnap_ffs behaves as expected. Since I'm able to reproduce this pretty much everywhere, here's information: # df -ki /usr Filesystem 1024-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/ad4s1f 163815904 3835274 146875358 3% 254864 20941934 1% /usr # cd /usr/.snap # /usr/bin/time -l mksnap_ffs /usr test.1 load: 1.90 cmd: mksnap_ffs 11719 [wdrain] 0.00u 0.07s 0% 1092k 23.25 real 0.00 user 0.00 sys 135.98 real 0.00 user 0.62 sys 1092 maximum resident set size 4 average shared memory size 1081 average unshared data size 135 average unshared stack size 101 page reclaims 0 page faults 0 swaps 895 block input operations 13444 block output operations 0 messages sent 0 messages received 0 signals received 6433 voluntary context switches 197 involuntary context switches # ls -l test.1 -r--r----- 1 root operator 173203463240 Nov 12 21:42 test.1 David's filesystem is 2GBs, while mine is 16GB. His snap takes under 1 second, yet mine takes over 2 minutes. Possibly the large deviation is explained by the amount of space used on the filesystem or the number of inodes in use? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 06:53:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF0B51065670; Thu, 13 Nov 2008 06:53:06 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr6.xs4all.nl (smtp-vbr6.xs4all.nl [194.109.24.26]) by mx1.freebsd.org (Postfix) with ESMTP id 5735D8FC0A; Thu, 13 Nov 2008 06:53:06 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [82.95.250.254]) by smtp-vbr6.xs4all.nl (8.13.8/8.13.8) with ESMTP id mAD6r2Df060532; Thu, 13 Nov 2008 07:53:02 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.14.2/8.14.2) with ESMTP id mAD6r1dR001289; Thu, 13 Nov 2008 07:53:01 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.14.2/8.14.2/Submit) id mAD6r1ui001288; Thu, 13 Nov 2008 07:53:01 +0100 (CET) (envelope-from wb) Date: Thu, 13 Nov 2008 07:53:01 +0100 From: Wilko Bulte To: Jeremy Chadwick Message-ID: <20081113065300.GA1276@freebie.xs4all.nl> References: <20081112175826.GD26195@carrick.bishnet.net> <20081112194735.GK47073@deviant.kiev.zoral.com.ua> <20081113004102.GD24360@carrick.bishnet.net> <20081113044200.GA10419@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081113044200.GA10419@icarus.home.lan> User-Agent: Mutt/1.5.16 (2007-06-09) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Kostik Belousov , Tim Bishop , freebsd-stable@freebsd.org Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 06:53:06 -0000 Quoting Jeremy Chadwick, who wrote on Wed, Nov 12, 2008 at 08:42:00PM -0800 .. > On Thu, Nov 13, 2008 at 12:41:02AM +0000, Tim Bishop wrote: > > On Wed, Nov 12, 2008 at 09:47:35PM +0200, Kostik Belousov wrote: > > > On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: > > > > I've been playing around with snapshots lately but I've got a problem on > > > > one of my servers running 7-STABLE amd64: > > > > > > > > FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 > > > > > > > > I run the mksnap_ffs command to take the snapshot and some time later > > > > the system completely freezes up: > > > > > > > > paladin# cd /u2/.snap/ > > > > paladin# mksnap_ffs /u2 test.1 > > > > > > > > It only happens on this one filesystem, though, which might be to do > > > > with its size. It's not over the 2TB marker, but it's pretty close. It's > > > > also backed by a hardware RAID system, although a smaller filesystem on > > > > the same RAID has no issues. > > > > > > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > > > /dev/da0s1a 2078881084 921821396 990749202 48% /u2 > > > > > > > > To clarify "completely freezes up": unresponsive to all services over > > > > the network, except ping. On the console I can switch between the ttys, > > > > but none of them respond. The only way out is to hit the reset button. > > > > > > You need to provide information described in the > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html > > > and especially > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html > > > > Ok, I've done that, and removed the patch that seemed to fix things. > > > > The first thing I notice after doing this on the console is that I can > > still ctrl+t the process: > > > > load: 0.14 cmd: mksnap_ffs 2603 [newbuf] 0.00u 10.75s 0% 1160k > > > > But the top and ps I left running on other ttys have all stopped > > responding. > > Then in my book, the patch didn't fix anything. :-) The system is > still "deadlocking"; snapshot generation **should not** wedge the system > hard like this. > > Also, during my own testing, I am always able to use Ctrl-T to get > SIGINFO from the running process (mksnap_ffs). That behaviour does not > change for me. > > The rest of the below information is good -- but I'm confused about > something: is there anyone out there who can use mksnap_ffs on a > filesystem (/usr is a good test source) and NOT experience this > deadlocking problem? Literally *every* FreeBSD box I have root access > to suffers from this problem, so I'm a little baffled why we end-users > need to keep providing debugging output when it should be easy as pie > for a developer to do "dump -0 -L -a -f /path/fs.dump /usr" and watch > their system wedge. dump -L on my RELENG_7 machine does not wedge it. So there must be multiple factors influencing the snap creating problems or not. Wilko From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 07:06:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A91B91065688 for ; Thu, 13 Nov 2008 07:06:55 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail12.syd.optusnet.com.au (mail12.syd.optusnet.com.au [211.29.132.193]) by mx1.freebsd.org (Postfix) with ESMTP id 1DBDC8FC1E for ; Thu, 13 Nov 2008 07:06:54 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail12.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id mAD76n8u027286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Nov 2008 18:06:50 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id mAD76mkq003618; Thu, 13 Nov 2008 18:06:48 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id mAD76m8Q003617; Thu, 13 Nov 2008 18:06:48 +1100 (EST) (envelope-from peter) Date: Thu, 13 Nov 2008 18:06:48 +1100 From: Peter Jeremy To: Doug Ambrisko Message-ID: <20081113070648.GC1098@server.vk2pj.dyndns.org> References: <20081112210513.GM47073@deviant.kiev.zoral.com.ua> <200811130447.mAD4lbJG051137@ambrisko.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="aVD9QWMuhilNxW9f" Content-Disposition: inline In-Reply-To: <200811130447.mAD4lbJG051137@ambrisko.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 07:06:55 -0000 --aVD9QWMuhilNxW9f Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Nov-12 20:47:37 -0800, Doug Ambrisko wrote: >I plan to commit it tomorrow since I sent it to Tim to test. The 10 can= =20 >be tuned but it has kept a bunch of machines at work up. Glad people=20 >don't think it is that it is to wrong :-) It probably could be made >a little more dynamic but I wonder if it would show any real performance >difference and might risk more bugs. FWIW, I've been running the patch since I first saw Doug post it in Feb 2006 and don't recall ever having problems with mksnap_ffs since applying it (I did before) --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --aVD9QWMuhilNxW9f Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkb0ggACgkQ/opHv/APuIfn9ACgoAPXKgHPozEobZE6i7tpL8vz dRUAn286tcAl1i3Dd9VfSVijhLNketFJ =zPvP -----END PGP SIGNATURE----- --aVD9QWMuhilNxW9f-- From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 07:54:01 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FD7F106564A for ; Thu, 13 Nov 2008 07:54:01 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from tokyo01.jp.mail.your.org (tokyo01.jp.mail.your.org [204.9.54.5]) by mx1.freebsd.org (Postfix) with ESMTP id C31378FC1C for ; Thu, 13 Nov 2008 07:54:00 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from tokyo01.jp.mail.your.org (localhost.your.org [127.0.0.1]) by tokyo01.jp.mail.your.org (Postfix) with ESMTP id A6BE72AD59D5 for ; Thu, 13 Nov 2008 07:34:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=dragondata.com; h= message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date; s=selector1; bh=SNRcWdUKG56O8wj64WbQ k5TXYeM=; b=gf9/UtRbL+Rp6gUj+VUyHhLRaalQA8pbimpAUSXhsyRxf0ynDJL6 6kbcDLj1ZRoQKt8AsqYepyV+o1BvbQmnhNbnY9erC52ai50iLTtnKvV8jR8Xz1UC jY37JWRZXpuofccAe41cjHWBUTODl2sOSJV8mne/MllfgPLehfGPS0I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=dragondata.com; h=message-id:from :to:content-type:content-transfer-encoding:mime-version:subject: date; q=dns; s=selector1; b=CLtO4zTNLbtxp36dLkzq6iP0EoL9d43YlQNZ AqhS3KfMOdLu65fn4GWVAajSa0aB83Tr/pW4EgSi8EBiHVLkZPUkNAeDLDhVvteq scfb9sPVEevunEtWKiKJxcUgJCOvq+kDfquugUeCCH5+XTJxc6JvUhPyMuKY14Oa jFAe5N4= Received: from mail.your.org (server3-a.your.org [64.202.112.67]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by tokyo01.jp.mail.your.org (Postfix) with ESMTPS id 6B4872AD597E for ; Thu, 13 Nov 2008 07:34:13 +0000 (UTC) Received: from [IPv6:2002:451f:630b:1::1] (unknown [IPv6:2002:451f:630b:1::1]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.your.org (Postfix) with ESMTPSA id C9981A0A406 for ; Thu, 13 Nov 2008 07:33:50 +0000 (UTC) Message-Id: From: Kevin Day To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Thu, 13 Nov 2008 01:34:07 -0600 X-Mailer: Apple Mail (2.929.2) Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 07:54:01 -0000 (moving my thread from -fs to -stable) Before touching anything, here's a description of the symptoms I see... Rather busy system, with quite a bit of filesystem activity occurring while the snapshot is being made. Quad CPU amd64 box with 16GB of ram, 6x10Krpm RAID array. Should be reasonably fast. Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/da0s1a 739339824 74357926 605834714 11% 1718540 93855474 2% / 1.7 million inodes, 71G used of a 705G volume. Here's a timeline of what I see when starting to make a new snapshot. I've got a few windows running, showing "top", "iostat", etc. Baseline disk activity before starting anything: device r/s w/s kr/s kw/s wait svc_t b da0 24.0 2.0 355.6 32.0 1 10.7 28 0m0s: Snapshot begins, using "mount -u -o snapshot //.snap/weekly. 0 /" Drives immediately jump to 100% busy as expected. device r/s w/s kr/s kw/s wait svc_t b da0 153.8 6.0 3378.6 95.9 2 16.9 100 the mount process is spending 100% of its time in "biord". 2m10s: The mount process starts spending more and more time in "snaplk", alternating with "biord". device r/s w/s kr/s kw/s wait svc_t b da0 77.9 67.9 1270.7 3754.2 1 10.7 100 12m15s: The first intermittent slowdowns start affecting other processes on the system. Occasionally all active processes will get stuck in "snaplk" or "ufs" for 5-10 seconds before resuming. device r/s w/s kr/s kw/s wait svc_t b da0 77.9 31.0 1150.8 1054.9 1 10.4 100 114m47s: Active processes are briefly stuck in "suspfs" 115m22s: Mount is now in "snaprdb", Active processes are now completely stuck in "snaplk". Still responsive to SIGINFO, top is still running, etc. Just hangs any time anything needs the filesystem. device r/s w/s kr/s kw/s wait svc_t b da0 238.8 0.0 3820.1 0.0 1 4.1 99 143m19s: Mount now in wdrain. 143m34s: Finished. snapshot logging shows "/: suspended 13.308 sec, redo 153 of 4058" Most processes were hung for 28 minutes. Is this what others are seeing? It sounds like some of the complaints are it getting stuck in the "wdrain" state, not what I'm showing here. Another mildly annoying note: Any process that touches ".snap" while a snapshot is being generated gets stuck in "ufs" until it finishes. I can understand wanting to keep operations in there in sync, but it would be really nice if "find /" wouldn't get hung when it tries to decent into .snap, for example. ts5# cd /.snap ts5# ls -l ^T load: 0.17 cmd: ls 3696 [ufs] 0.00u 0.00s 0% 1496k From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 08:35:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A179106567E; Thu, 13 Nov 2008 08:35:12 +0000 (UTC) (envelope-from tdb@carrick.bishnet.net) Received: from carrick.bishnet.net (carrick.bishnet.net [IPv6:2a01:348:132::1]) by mx1.freebsd.org (Postfix) with ESMTP id 491278FC14; Thu, 13 Nov 2008 08:35:11 +0000 (UTC) (envelope-from tdb@carrick.bishnet.net) Received: from tdb by carrick.bishnet.net with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1L0XfM-000Kwj-Sd; Thu, 13 Nov 2008 08:35:04 +0000 Date: Thu, 13 Nov 2008 08:35:04 +0000 From: Tim Bishop To: Jeremy Chadwick Message-ID: <20081113083504.GF24360@carrick.bishnet.net> References: <20081112175826.GD26195@carrick.bishnet.net> <20081112194735.GK47073@deviant.kiev.zoral.com.ua> <20081113004102.GD24360@carrick.bishnet.net> <20081113044200.GA10419@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081113044200.GA10419@icarus.home.lan> X-PGP-Key: 0x5AE7D984, http://www.bishnet.net/tim/tim-bishnet-net.asc X-PGP-Fingerprint: 1453 086E 9376 1A50 ECF6 AE05 7DCE D659 5AE7 D984 User-Agent: Mutt/1.5.13 (2006-08-11) X-Bishnet-MailScanner-Information: Contact postmaster@bishnet.net X-Bishnet-MailScanner-VirusCheck: Found to be clean X-Bishnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1.087, required 5, BAYES_00 -2.60, DNS_FROM_SECURITYSAGE 1.51, NO_RELAYS -0.00) X-Bishnet-MailScanner-From: tdb@carrick.bishnet.net Cc: Kostik Belousov , Tim Bishop , freebsd-stable@freebsd.org Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 08:35:12 -0000 Jeremy, On Wed, Nov 12, 2008 at 08:42:00PM -0800, Jeremy Chadwick wrote: > On Thu, Nov 13, 2008 at 12:41:02AM +0000, Tim Bishop wrote: > > On Wed, Nov 12, 2008 at 09:47:35PM +0200, Kostik Belousov wrote: > > > On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: > > > > I run the mksnap_ffs command to take the snapshot and some time later > > > > the system completely freezes up: > > > > > > > > paladin# cd /u2/.snap/ > > > > paladin# mksnap_ffs /u2 test.1 > > > > > > You need to provide information described in the > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html > > > and especially > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html > > > > Ok, I've done that, and removed the patch that seemed to fix things. > > > > The first thing I notice after doing this on the console is that I can > > still ctrl+t the process: > > > > load: 0.14 cmd: mksnap_ffs 2603 [newbuf] 0.00u 10.75s 0% 1160k > > > > But the top and ps I left running on other ttys have all stopped > > responding. > > Then in my book, the patch didn't fix anything. :-) The system is > still "deadlocking"; snapshot generation **should not** wedge the system > hard like this. You missed the part where I said I "removed the patch". I did that so I could provide details with it wedged. I agree that there's still some fundamental speed issues with snapshotting though. And I'm sure the FS itself will still be locked out for a while during the snapshot. But with the patch at least the whole thing doesn't lock up. Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 09:15:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C76531065673 for ; Thu, 13 Nov 2008 09:15:52 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by mx1.freebsd.org (Postfix) with ESMTP id 6E24E8FC14 for ; Thu, 13 Nov 2008 09:15:51 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA13.westchester.pa.mail.comcast.net ([76.96.62.52]) by QMTA02.westchester.pa.mail.comcast.net with comcast id eZFU1a00C17dt5G52ZFa7C; Thu, 13 Nov 2008 09:15:34 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA13.westchester.pa.mail.comcast.net with comcast id eZFp1a0042P6wsM3ZZFqrC; Thu, 13 Nov 2008 09:15:51 +0000 X-Authority-Analysis: v=1.0 c=1 a=becna3ql8DEA:10 a=0kYo9GeZAlkA:10 a=QycZ5dHgAAAA:8 a=f26Ryk-jcW2UC960mAgA:9 a=M_tFpcYe8spZ0vzBc8YA:7 a=gdGDMaqYKlJ1c10h737Jc9yqXMMA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id B9B8F5C1A; Thu, 13 Nov 2008 01:15:49 -0800 (PST) Date: Thu, 13 Nov 2008 01:15:49 -0800 From: Jeremy Chadwick To: David Wolfskill , Tim Bishop , Kostik Belousov , freebsd-stable@freebsd.org Message-ID: <20081113091549.GA15888@icarus.home.lan> References: <20081112175826.GD26195@carrick.bishnet.net> <20081112194735.GK47073@deviant.kiev.zoral.com.ua> <20081113004102.GD24360@carrick.bishnet.net> <20081113044200.GA10419@icarus.home.lan> <20081113050250.GR69155@bunrab.catwhisker.org> <20081113060521.GA11595@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081113060521.GA11595@icarus.home.lan> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 09:15:52 -0000 On Wed, Nov 12, 2008 at 10:05:21PM -0800, Jeremy Chadwick wrote: > On Wed, Nov 12, 2008 at 09:02:50PM -0800, David Wolfskill wrote: > > On Wed, Nov 12, 2008 at 08:42:00PM -0800, Jeremy Chadwick wrote: > > > ... > > > > > On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: > > > > > > I've been playing around with snapshots lately but I've got a problem on > > > > > > one of my servers running 7-STABLE amd64: > > > > > > > > > > > > FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 > > > > > > > > > > > > I run the mksnap_ffs command to take the snapshot and some time later > > > > > > the system completely freezes up: > > > > > > > > > > > > paladin# cd /u2/.snap/ > > > > > > paladin# mksnap_ffs /u2 test.1 > > > > > > > > > > > > It only happens on this one filesystem, though, which might be to do > > > > > > with its size. It's not over the 2TB marker, but it's pretty close. It's > > > > > > also backed by a hardware RAID system, although a smaller filesystem on > > > > > > the same RAID has no issues. > > > ... > > > Then in my book, the patch didn't fix anything. :-) The system is > > > still "deadlocking"; snapshot generation **should not** wedge the system > > > hard like this. > > > > > > Also, during my own testing, I am always able to use Ctrl-T to get > > > SIGINFO from the running process (mksnap_ffs). That behaviour does not > > > change for me. > > > > > > The rest of the below information is good -- but I'm confused about > > > something: is there anyone out there who can use mksnap_ffs on a > > > filesystem (/usr is a good test source) and NOT experience this > > > deadlocking problem? > > > > I hadn't ever tried until I saw your message. Granted, I'm using a > > smaller file system (I doubt that I have a toital of as much as 2 TB in > > all my machines combined), and I'm running i386, vs. amd64. But it ran > > just fine. I wasn't able to test SIGINFO; it finished before I had a > > chance. (I ran it under time(1); wall clock time was 0.91 sec.) > > > > > Literally *every* FreeBSD box I have root access > > > to suffers from this problem, so I'm a little baffled why we end-users > > > need to keep providing debugging output when it should be easy as pie > > > for a developer to do "dump -0 -L -a -f /path/fs.dump /usr" and watch > > > their system wedge. > > > > Well, I routinely use dump/restore pipelines to copy file systems > > around; never had a problem with it. > > > > > ... > > > > For reference: > > > > freebeast(7.1-P)[9] uname -a > > FreeBSD freebeast.catwhisker.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #127: Wed Nov 12 05:16:20 PST 2008 root@freebeast.catwhisker.org:/common/S3/obj/usr/src/sys/FREEBEAST i386 > > freebeast(7.1-P)[10] ls -la > > total 4 > > drwxrwxr-x 2 root operator 512 Nov 12 20:53 . > > drwxr-xr-x 14 root wheel 512 Jan 22 2008 .. > > freebeast(7.1-P)[11] /usr/bin/time -l mksnap_ffs /S2/usr test.1 > > 0.91 real 0.00 user 0.05 sys > > 976 maximum resident set size > > 3 average shared memory size > > 627 average unshared data size > > 109 average unshared stack size > > 104 page reclaims > > 0 page faults > > 0 swaps > > 1 block input operations > > 230 block output operations > > 0 messages sent > > 0 messages received > > 0 signals received > > 101 voluntary context switches > > 34 involuntary context switches > > freebeast(7.1-P)[12] ls -la > > total 1460 > > drwxrwxr-x 2 root operator 512 Nov 12 20:54 . > > drwxr-xr-x 14 root wheel 512 Jan 22 2008 .. > > -r--r----- 1 root operator 2410791056 Nov 12 20:54 test.1 > > freebeast(7.1-P)[13] > > David, thanks for chiming in. This is exactly what I was > fearing/worried about. > > It would be greatly beneficial if we could figure out what triggers the > slowdown for a lot of us, since for others (proof above) mksnap_ffs > behaves as expected. > > Since I'm able to reproduce this pretty much everywhere, here's > information: > > # df -ki /usr > Filesystem 1024-blocks Used Avail Capacity iused ifree %iused Mounted on > /dev/ad4s1f 163815904 3835274 146875358 3% 254864 20941934 1% /usr > > # cd /usr/.snap > # /usr/bin/time -l mksnap_ffs /usr test.1 > > > > load: 1.90 cmd: mksnap_ffs 11719 [wdrain] 0.00u 0.07s 0% 1092k > 23.25 real 0.00 user 0.00 sys > > 135.98 real 0.00 user 0.62 sys > 1092 maximum resident set size > 4 average shared memory size > 1081 average unshared data size > 135 average unshared stack size > 101 page reclaims > 0 page faults > 0 swaps > 895 block input operations > 13444 block output operations > 0 messages sent > 0 messages received > 0 signals received > 6433 voluntary context switches > 197 involuntary context switches > # ls -l test.1 > -r--r----- 1 root operator 173203463240 Nov 12 21:42 test.1 > > David's filesystem is 2GBs, while mine is 16GB. His snap takes under 1 > second, yet mine takes over 2 minutes. > > Possibly the large deviation is explained by the amount of space used on > the filesystem or the number of inodes in use? I also want to add that snapshot removal (e.g. rm test.1) is equally as slow (rm process is also in wdrain); takes about 20 seconds for the above test.1 snapshot. Maybe long durations during deletion are justified though, I don't know. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 10:26:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BAD4B106564A; Thu, 13 Nov 2008 10:26:47 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 5DB248FC1E; Thu, 13 Nov 2008 10:26:47 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1L0ZPS-000NPo-0R; Thu, 13 Nov 2008 12:26:46 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mADAQg9a090506 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Nov 2008 12:26:42 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id mADAQgPo027017; Thu, 13 Nov 2008 12:26:42 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mADAQgtT027016; Thu, 13 Nov 2008 12:26:42 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 13 Nov 2008 12:26:42 +0200 From: Kostik Belousov To: Jeremy Chadwick Message-ID: <20081113102642.GQ47073@deviant.kiev.zoral.com.ua> References: <20081112175826.GD26195@carrick.bishnet.net> <20081112194735.GK47073@deviant.kiev.zoral.com.ua> <20081113004102.GD24360@carrick.bishnet.net> <20081113044200.GA10419@icarus.home.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xYeFQzU4VZLrHqxU" Content-Disposition: inline In-Reply-To: <20081113044200.GA10419@icarus.home.lan> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1L0ZPS-000NPo-0R 1f183d59b227644d4f32b9ddb93daae9 X-Terabit: YES Cc: Tim Bishop , freebsd-stable@freebsd.org Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 10:26:47 -0000 --xYeFQzU4VZLrHqxU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 12, 2008 at 08:42:00PM -0800, Jeremy Chadwick wrote: > On Thu, Nov 13, 2008 at 12:41:02AM +0000, Tim Bishop wrote: > > On Wed, Nov 12, 2008 at 09:47:35PM +0200, Kostik Belousov wrote: > > > On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: > > > > I've been playing around with snapshots lately but I've got a probl= em on > > > > one of my servers running 7-STABLE amd64: > > > >=20 > > > > FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 1= 0 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 > > > >=20 > > > > I run the mksnap_ffs command to take the snapshot and some time lat= er > > > > the system completely freezes up: > > > >=20 > > > > paladin# cd /u2/.snap/ > > > > paladin# mksnap_ffs /u2 test.1 > > > >=20 > > > > It only happens on this one filesystem, though, which might be to do > > > > with its size. It's not over the 2TB marker, but it's pretty close.= It's > > > > also backed by a hardware RAID system, although a smaller filesyste= m on > > > > the same RAID has no issues. > > > >=20 > > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > > > /dev/da0s1a 2078881084 921821396 990749202 48% /u2 > > > >=20 > > > > To clarify "completely freezes up": unresponsive to all services ov= er > > > > the network, except ping. On the console I can switch between the t= tys, > > > > but none of them respond. The only way out is to hit the reset butt= on. > > >=20 > > > You need to provide information described in the > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/= kerneldebug.html > > > and especially > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/= kerneldebug-deadlocks.html > >=20 > > Ok, I've done that, and removed the patch that seemed to fix things. > >=20 > > The first thing I notice after doing this on the console is that I can > > still ctrl+t the process: > >=20 > > load: 0.14 cmd: mksnap_ffs 2603 [newbuf] 0.00u 10.75s 0% 1160k > >=20 > > But the top and ps I left running on other ttys have all stopped > > responding. >=20 > Then in my book, the patch didn't fix anything. :-) The system is > still "deadlocking"; snapshot generation **should not** wedge the system > hard like this. You systematically mix two completely different issues: - first one is the _deadlock_ experienced by Tim; - second one is the slowdown during snapshot creation. In fact, I may count third, where dump itself hangs, as a usermode process, but kernel still normally operates. Patch posted should fix or paper over the first issue for practical means. Third issue most likely fixed by the subr_sleepqueue race fix. --xYeFQzU4VZLrHqxU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkkcAOEACgkQC3+MBN1Mb4gBLgCeJpvjH91HS+aZkdvC9fg6gAqF m6MAoK4f2shdnDrmgyu7mj0xfptk5iSM =hB/Y -----END PGP SIGNATURE----- --xYeFQzU4VZLrHqxU-- From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 10:45:16 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D66C106564A for ; Thu, 13 Nov 2008 10:45:16 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by mx1.freebsd.org (Postfix) with ESMTP id 10BF58FC0A for ; Thu, 13 Nov 2008 10:45:15 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by QMTA10.emeryville.ca.mail.comcast.net with comcast id eaej1a00B0FhH24AAalFYu; Thu, 13 Nov 2008 10:45:15 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA08.emeryville.ca.mail.comcast.net with comcast id ealE1a0032P6wsM8UalEpR; Thu, 13 Nov 2008 10:45:15 +0000 X-Authority-Analysis: v=1.0 c=1 a=becna3ql8DEA:10 a=0kYo9GeZAlkA:10 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=iKGFiojNi0eaevVoTVwA:9 a=dEKMq7jSdpIzM9ddwpEA:7 a=eSjefcXUuS4Es3spcrIGjvj5VqwA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 6F2D75C19; Thu, 13 Nov 2008 02:45:14 -0800 (PST) Date: Thu, 13 Nov 2008 02:45:14 -0800 From: Jeremy Chadwick To: Kostik Belousov Message-ID: <20081113104514.GA17589@icarus.home.lan> References: <20081112175826.GD26195@carrick.bishnet.net> <20081112194735.GK47073@deviant.kiev.zoral.com.ua> <20081113004102.GD24360@carrick.bishnet.net> <20081113044200.GA10419@icarus.home.lan> <20081113102642.GQ47073@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081113102642.GQ47073@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Tim Bishop , freebsd-stable@freebsd.org Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 10:45:16 -0000 On Thu, Nov 13, 2008 at 12:26:42PM +0200, Kostik Belousov wrote: > On Wed, Nov 12, 2008 at 08:42:00PM -0800, Jeremy Chadwick wrote: > > On Thu, Nov 13, 2008 at 12:41:02AM +0000, Tim Bishop wrote: > > > On Wed, Nov 12, 2008 at 09:47:35PM +0200, Kostik Belousov wrote: > > > > On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: > > > > > I've been playing around with snapshots lately but I've got a problem on > > > > > one of my servers running 7-STABLE amd64: > > > > > > > > > > FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 > > > > > > > > > > I run the mksnap_ffs command to take the snapshot and some time later > > > > > the system completely freezes up: > > > > > > > > > > paladin# cd /u2/.snap/ > > > > > paladin# mksnap_ffs /u2 test.1 > > > > > > > > > > It only happens on this one filesystem, though, which might be to do > > > > > with its size. It's not over the 2TB marker, but it's pretty close. It's > > > > > also backed by a hardware RAID system, although a smaller filesystem on > > > > > the same RAID has no issues. > > > > > > > > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > > > > /dev/da0s1a 2078881084 921821396 990749202 48% /u2 > > > > > > > > > > To clarify "completely freezes up": unresponsive to all services over > > > > > the network, except ping. On the console I can switch between the ttys, > > > > > but none of them respond. The only way out is to hit the reset button. > > > > > > > > You need to provide information described in the > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html > > > > and especially > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html > > > > > > Ok, I've done that, and removed the patch that seemed to fix things. > > > > > > The first thing I notice after doing this on the console is that I can > > > still ctrl+t the process: > > > > > > load: 0.14 cmd: mksnap_ffs 2603 [newbuf] 0.00u 10.75s 0% 1160k > > > > > > But the top and ps I left running on other ttys have all stopped > > > responding. > > > > Then in my book, the patch didn't fix anything. :-) The system is > > still "deadlocking"; snapshot generation **should not** wedge the system > > hard like this. > You systematically mix two completely different issues: > - first one is the _deadlock_ experienced by Tim; Re-read what he wrote. Quote: "Ok, I've done that, and removed the patch that seemed to fix things. The first thing I notice after doing this on the console is that I can still ctrl+t the process: load: 0.14 cmd: mksnap_ffs 2603 [newbuf] 0.00u 10.75s 0% 1160k But the top and ps I left running on other ttys have all stopped responding." If he can press Control-T, it means SIGINFO can be sent to the mksnap_ffs process, and the process responds with that information. So, the system is not deadlocked -- meaning, I believe what he experiences is what others experience (the system becomes completely unusable during mksnap_ffs running, but DOES NOT hang or lock up, it just becomes so god-awful slow that processes on the machine literally sit and spin for minutes at a time). > - second one is the slowdown during snapshot creation. > In fact, I may count third, where dump itself hangs, as a usermode process, > but kernel still normally operates. > > Patch posted should fix or paper over the first issue for practical means. > Third issue most likely fixed by the subr_sleepqueue race fix. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 11:22:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FB3D10656A9 for ; Thu, 13 Nov 2008 11:22:13 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id DB60E8FC22 for ; Thu, 13 Nov 2008 11:22:12 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so549636nfh.33 for ; Thu, 13 Nov 2008 03:22:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=1IvWlzguFTCt2/5NwOwxDL+5doGI0Kdi0Xi2RHvVq1U=; b=n0ywCn7WfJAiK3tlLJFAsKF9pz1azqHPhzbBKuTv+xGCYjwrAX6hIsNL+ZRnx2FvaY MdV9vSZOy3OuC9xg/LfKJngm/rvFR7BKABMD2IeNvaiIrCLiM4a5dOWwdR1Lw9BDNinS Q9bWd9gOYn5wonNpzlgiDHY5mUrDm+UVhR5ho= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=vZOPVNB019lfkVvJ7Vd7D8wQqn+jQMMyXU2ukoMqY3AL/eIUeDScfx95M5KKeX7EnZ qX216HUwAwkBizZpQzgDC/qJYWZH7muvHhSUda9ZLB+2SxXqD6lE6bzHsZ+cjCI9bF81 /WWs3ToX4M9JfHdezRs6ufvLLeXeIZV0Pp6ps= Received: by 10.103.213.19 with SMTP id p19mr5786173muq.9.1226575331690; Thu, 13 Nov 2008 03:22:11 -0800 (PST) Received: by 10.103.249.11 with HTTP; Thu, 13 Nov 2008 03:22:11 -0800 (PST) Message-ID: Date: Thu, 13 Nov 2008 12:22:11 +0100 From: "Claus Guttesen" To: "FreeBSD Stable" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: qlogic qle2462 hba and freebsd stable on a dl360 g5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 11:22:13 -0000 Hi. I'm looking at a qlogic qle2462 hba for my dl360 g5. The thread http://www.mail-archive.com/freebsd-stable@freebsd.org/msg99497.html mentions a deadlock when system is loaded. Has this issue been resolved? Are there other PCI Express hba's which are known to work with freebsd stable and dl360 g5? -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is the soonest winner. Shakespeare From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 11:24:19 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98DE2106564A for ; Thu, 13 Nov 2008 11:24:19 +0000 (UTC) (envelope-from david@esn.org.za) Received: from serendipity.wcape.school.za (seren.esn.org.za [196.211.28.252]) by mx1.freebsd.org (Postfix) with ESMTP id 8AA478FC19 for ; Thu, 13 Nov 2008 11:24:17 +0000 (UTC) (envelope-from david@esn.org.za) Received: from intsika.ct.esn.org.za ([196.211.28.250] helo=ct.esn.org.za) by serendipity.wcape.school.za with esmtp (Exim 4.30) id 1L0aJ1-000Hzx-Ee for freebsd-stable@freebsd.org; Thu, 13 Nov 2008 13:24:11 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Thu, 13 Nov 2008 13:24:10 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ipfw erratic on 7 stable Thread-Index: AclFgllrqhWm8MhgQTCpCkFS4GuT0A== From: "David Peall" To: X-Antivirus-Scanned: Clean by seren.wcsn.org.za Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ipfw erratic on 7 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 11:24:19 -0000 Hi =20 I'm having a problem with ipfw, I think. =20 For some reason it denies packets randomly for example: =20 PING 196.14.239.2 (196.14.239.2): 56 data bytes ping: sendto: Permission denied ping: sendto: Permission denied 64 bytes from 196.14.239.2: icmp_seq=3D2 ttl=3D63 time=3D0.258 ms 64 bytes from 196.14.239.2: icmp_seq=3D3 ttl=3D63 time=3D0.233 ms 64 bytes from 196.14.239.2: icmp_seq=3D4 ttl=3D63 time=3D0.211 ms =20 Not sure what else would be helpful at this point. =20 Running: FreeBSD 7.1-PRERELEASE #0: Fri Oct 31 09:44:07 UTC 2008 =20 =20 -- David Peall :: IT Manager e-Schools' Network :: http://www.esn.org.za/ =20 Phone +27 (021) 674-9140 =20 From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 12:26:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E790D106567D for ; Thu, 13 Nov 2008 12:26:13 +0000 (UTC) (envelope-from david@esn.org.za) Received: from serendipity.wcape.school.za (seren.esn.org.za [196.211.28.252]) by mx1.freebsd.org (Postfix) with ESMTP id 1CC9F8FC0A for ; Thu, 13 Nov 2008 12:26:11 +0000 (UTC) (envelope-from david@esn.org.za) Received: from intsika.ct.esn.org.za ([196.211.28.250] helo=ct.esn.org.za) by serendipity.wcape.school.za with esmtp (Exim 4.30) id 1L0bGy-000I6g-HV for freebsd-stable@freebsd.org; Thu, 13 Nov 2008 14:26:08 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Thu, 13 Nov 2008 14:26:05 +0200 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ipfw erratic on 7 stable Thread-Index: AclFgllrqhWm8MhgQTCpCkFS4GuT0AACGlPw References: From: "David Peall" To: X-Antivirus-Scanned: Clean by seren.wcsn.org.za Subject: RE: ipfw erratic on 7 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 12:26:14 -0000 Ok Sorry: ipfw: install_state: Too many dynamic rules Any idea what is a safe number to use, I've set=20 net.inet.ip.fw.dyn_max: 8192 regards -- David Peall :: IT Manager e-Schools' Network :: http://www.esn.org.za/ Phone +27 (021) 674-9140 From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 12:27:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A5FD106564A for ; Thu, 13 Nov 2008 12:27:38 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by mx1.freebsd.org (Postfix) with ESMTP id 479F78FC13 for ; Thu, 13 Nov 2008 12:27:38 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA05.westchester.pa.mail.comcast.net ([76.96.62.43]) by QMTA02.westchester.pa.mail.comcast.net with comcast id ecBp1a00d0vyq2s52cTLnW; Thu, 13 Nov 2008 12:27:20 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA05.westchester.pa.mail.comcast.net with comcast id ecTc1a00H2P6wsM3RcTdV4; Thu, 13 Nov 2008 12:27:37 +0000 X-Authority-Analysis: v=1.0 c=1 a=QycZ5dHgAAAA:8 a=i1lI_dfH-hToQv7r-lgA:9 a=pT2htGUqf2bt5VPHu1UA:7 a=NGffDORKg-lX1Dma3BYG77uDYCkA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 653BC5C19; Thu, 13 Nov 2008 04:27:36 -0800 (PST) Date: Thu, 13 Nov 2008 04:27:36 -0800 From: Jeremy Chadwick To: David Peall Message-ID: <20081113122736.GA21273@icarus.home.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: ipfw erratic on 7 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 12:27:38 -0000 On Thu, Nov 13, 2008 at 01:24:10PM +0200, David Peall wrote: > I'm having a problem with ipfw, I think. > > For some reason it denies packets randomly for example: > > PING 196.14.239.2 (196.14.239.2): 56 data bytes > ping: sendto: Permission denied > ping: sendto: Permission denied > 64 bytes from 196.14.239.2: icmp_seq=2 ttl=63 time=0.258 ms > 64 bytes from 196.14.239.2: icmp_seq=3 ttl=63 time=0.233 ms > 64 bytes from 196.14.239.2: icmp_seq=4 ttl=63 time=0.211 ms > > Not sure what else would be helpful at this point. > > Running: > FreeBSD 7.1-PRERELEASE #0: Fri Oct 31 09:44:07 UTC 2008 In my experiences, "Permission denied" is returned if you have a rule that blocks certain outbound packets; the OS tells the socket owner "no can do". There isn't enough information in the above report to help determine why it happens randomly; what flags have you passed ping? And please provide your entire ipfw ruleset, something may stand out. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 13:21:15 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5BF3106567F; Thu, 13 Nov 2008 13:21:15 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 6A4DA8FC08; Thu, 13 Nov 2008 13:21:15 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1L0c8G-000HdC-VE; Thu, 13 Nov 2008 15:21:13 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mADDLA1L002595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Nov 2008 15:21:10 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id mADDLA64032199; Thu, 13 Nov 2008 15:21:10 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mADDL9qo032198; Thu, 13 Nov 2008 15:21:09 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 13 Nov 2008 15:21:09 +0200 From: Kostik Belousov To: Jeremy Chadwick Message-ID: <20081113132109.GT47073@deviant.kiev.zoral.com.ua> References: <20081112175826.GD26195@carrick.bishnet.net> <20081112194735.GK47073@deviant.kiev.zoral.com.ua> <20081113004102.GD24360@carrick.bishnet.net> <20081113044200.GA10419@icarus.home.lan> <20081113102642.GQ47073@deviant.kiev.zoral.com.ua> <20081113104514.GA17589@icarus.home.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wYXww9TlNKyqAMAe" Content-Disposition: inline In-Reply-To: <20081113104514.GA17589@icarus.home.lan> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1L0c8G-000HdC-VE d5683dc112945d4236afcf77baaff217 X-Terabit: YES Cc: Tim Bishop , freebsd-stable@freebsd.org Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 13:21:15 -0000 --wYXww9TlNKyqAMAe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 13, 2008 at 02:45:14AM -0800, Jeremy Chadwick wrote: > On Thu, Nov 13, 2008 at 12:26:42PM +0200, Kostik Belousov wrote: > > On Wed, Nov 12, 2008 at 08:42:00PM -0800, Jeremy Chadwick wrote: > > > On Thu, Nov 13, 2008 at 12:41:02AM +0000, Tim Bishop wrote: > > > > On Wed, Nov 12, 2008 at 09:47:35PM +0200, Kostik Belousov wrote: > > > > > On Wed, Nov 12, 2008 at 05:58:26PM +0000, Tim Bishop wrote: > > > > > > I've been playing around with snapshots lately but I've got a p= roblem on > > > > > > one of my servers running 7-STABLE amd64: > > > > > >=20 > > > > > > FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon N= ov 10 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 > > > > > >=20 > > > > > > I run the mksnap_ffs command to take the snapshot and some time= later > > > > > > the system completely freezes up: > > > > > >=20 > > > > > > paladin# cd /u2/.snap/ > > > > > > paladin# mksnap_ffs /u2 test.1 > > > > > >=20 > > > > > > It only happens on this one filesystem, though, which might be = to do > > > > > > with its size. It's not over the 2TB marker, but it's pretty cl= ose. It's > > > > > > also backed by a hardware RAID system, although a smaller files= ystem on > > > > > > the same RAID has no issues. > > > > > >=20 > > > > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > > > > > /dev/da0s1a 2078881084 921821396 990749202 48% /u2 > > > > > >=20 > > > > > > To clarify "completely freezes up": unresponsive to all service= s over > > > > > > the network, except ping. On the console I can switch between t= he ttys, > > > > > > but none of them respond. The only way out is to hit the reset = button. > > > > >=20 > > > > > You need to provide information described in the > > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handb= ook/kerneldebug.html > > > > > and especially > > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handb= ook/kerneldebug-deadlocks.html > > > >=20 > > > > Ok, I've done that, and removed the patch that seemed to fix things. > > > >=20 > > > > The first thing I notice after doing this on the console is that I = can > > > > still ctrl+t the process: > > > >=20 > > > > load: 0.14 cmd: mksnap_ffs 2603 [newbuf] 0.00u 10.75s 0% 1160k > > > >=20 > > > > But the top and ps I left running on other ttys have all stopped > > > > responding. > > >=20 > > > Then in my book, the patch didn't fix anything. :-) The system is > > > still "deadlocking"; snapshot generation **should not** wedge the sys= tem > > > hard like this. > > You systematically mix two completely different issues: > > - first one is the _deadlock_ experienced by Tim; >=20 > Re-read what he wrote. Quote: >=20 > "Ok, I've done that, and removed the patch that seemed to fix things. >=20 > The first thing I notice after doing this on the console is that I can > still ctrl+t the process: >=20 > load: 0.14 cmd: mksnap_ffs 2603 [newbuf] 0.00u 10.75s 0% 1160k >=20 > But the top and ps I left running on other ttys have all stopped > responding." >=20 > If he can press Control-T, it means SIGINFO can be sent to the > mksnap_ffs process, and the process responds with that information. So, > the system is not deadlocked -- meaning, I believe what he experiences > is what others experience (the system becomes completely unusable during > mksnap_ffs running, but DOES NOT hang or lock up, it just becomes so > god-awful slow that processes on the machine literally sit and spin for > minutes at a time). Unless NOKERNINFO is specified in the local flags in the controlling terminal termios, kernel prints one line summary as shown above. This is done from the tty discipline input handler (or whatever it is in new tty code). No process cooperation is required. On the other hand, actually delivering SIGINFO and getting output from the process-installed handler do require process to either executing usermode or sleeping interruptible. --wYXww9TlNKyqAMAe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkkcKcQACgkQC3+MBN1Mb4gaUQCfbjbNGNyPx86eJrw9QlxfJ+rA sv4An32gV1qu4OUDxqO9RQYSlNkcqu8R =K4VS -----END PGP SIGNATURE----- --wYXww9TlNKyqAMAe-- From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 13:38:55 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BE191065680 for ; Thu, 13 Nov 2008 13:38:55 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9FE578FC12 for ; Thu, 13 Nov 2008 13:38:54 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA11374 for ; Thu, 13 Nov 2008 15:38:52 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <491C2DEB.3010504@icyb.net.ua> Date: Thu, 13 Nov 2008 15:38:51 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.17 (X11/20081106) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: find -L . -type l -delete X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 13:38:55 -0000 Am I stupid or is our 'find' is seriously broken in one subtle feature? $ find -L . -type l find all broken symlinks (target doesn't exists) $ find -L . -type l -delete removes all symlinks!!! FreeBSD 7.1-PRERELEASE amd64 -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 14:17:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8C70106567E for ; Thu, 13 Nov 2008 14:17:29 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 418518FC1F for ; Thu, 13 Nov 2008 14:17:28 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id mADEHQeP027758; Thu, 13 Nov 2008 21:17:26 +0700 (KRAT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id mADEHQ2U027756; Thu, 13 Nov 2008 21:17:26 +0700 (KRAT) (envelope-from eugen) Date: Thu, 13 Nov 2008 21:17:26 +0700 From: Eugene Grosbein To: Andriy Gapon Message-ID: <20081113141726.GA26583@svzserv.kemerovo.su> References: <491C2DEB.3010504@icyb.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <491C2DEB.3010504@icyb.net.ua> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: find -L . -type l -delete X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 14:17:30 -0000 On Thu, Nov 13, 2008 at 03:38:51PM +0200, Andriy Gapon wrote: > Am I stupid or is our 'find' is seriously broken in one subtle feature? > > $ find -L . -type l > find all broken symlinks (target doesn't exists) > > $ find -L . -type l -delete > removes all symlinks!!! Yes. > FreeBSD 7.1-PRERELEASE amd64 This is pretty old and known problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/90687 Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 14:33:53 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA4651065678 for ; Thu, 13 Nov 2008 14:33:53 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E4C438FC18 for ; Thu, 13 Nov 2008 14:33:52 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA12458; Thu, 13 Nov 2008 16:33:24 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <491C3AB2.5010706@icyb.net.ua> Date: Thu, 13 Nov 2008 16:33:22 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.17 (X11/20081106) MIME-Version: 1.0 To: Eugene Grosbein References: <491C2DEB.3010504@icyb.net.ua> <20081113141726.GA26583@svzserv.kemerovo.su> In-Reply-To: <20081113141726.GA26583@svzserv.kemerovo.su> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: find -L . -type l -delete X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 14:33:53 -0000 on 13/11/2008 16:17 Eugene Grosbein said the following: > On Thu, Nov 13, 2008 at 03:38:51PM +0200, Andriy Gapon wrote: > >> Am I stupid or is our 'find' is seriously broken in one subtle feature? >> >> $ find -L . -type l >> find all broken symlinks (target doesn't exists) >> >> $ find -L . -type l -delete >> removes all symlinks!!! > > Yes. > >> FreeBSD 7.1-PRERELEASE amd64 > > This is pretty old and known problem: > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/90687 Wow, that's pretty tough. I always relied on the following 3 step procedure: 1. find ... -print 2. verify output 3. find ... -delete [Profit!] But now I will have to re-tune myself to xargs. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 15:27:40 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0724E1065674 for ; Thu, 13 Nov 2008 15:27:40 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 518028FC13 for ; Thu, 13 Nov 2008 15:27:39 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id mADFRalg033343; Thu, 13 Nov 2008 22:27:36 +0700 (KRAT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id mADFRauS033342; Thu, 13 Nov 2008 22:27:36 +0700 (KRAT) (envelope-from eugen) Date: Thu, 13 Nov 2008 22:27:36 +0700 From: Eugene Grosbein To: Andriy Gapon Message-ID: <20081113152736.GA33024@svzserv.kemerovo.su> References: <491C2DEB.3010504@icyb.net.ua> <20081113141726.GA26583@svzserv.kemerovo.su> <491C3AB2.5010706@icyb.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <491C3AB2.5010706@icyb.net.ua> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: find -L . -type l -delete X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 15:27:40 -0000 On Thu, Nov 13, 2008 at 04:33:22PM +0200, Andriy Gapon wrote: > >> $ find -L . -type l -delete > >> removes all symlinks!!! > >> FreeBSD 7.1-PRERELEASE amd64 > > This is pretty old and known problem: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/90687 > Wow, that's pretty tough. > But now I will have to re-tune myself to xargs. Care to submit a followup to the PR with a note that it's still the problem for 7.1? Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 16:41:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4871F106567D; Thu, 13 Nov 2008 16:41:38 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (core.byshenk.net [62.58.73.230]) by mx1.freebsd.org (Postfix) with ESMTP id D9E5E8FC1C; Thu, 13 Nov 2008 16:41:37 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (localhost.aoes.com [127.0.0.1]) by core.byshenk.net (8.14.3/8.14.3) with ESMTP id mADG8AEv007717; Thu, 13 Nov 2008 17:08:10 +0100 (CET) (envelope-from byshenknet@core.byshenk.net) Received: (from byshenknet@localhost) by core.byshenk.net (8.14.3/8.14.3/Submit) id mADG8AjH007716; Thu, 13 Nov 2008 17:08:10 +0100 (CET) (envelope-from byshenknet) Date: Thu, 13 Nov 2008 17:08:10 +0100 From: Greg Byshenk To: freebsd-stable@freebsd.org Message-ID: <20081113160810.GN907@core.byshenk.net> References: <20081112175826.GD26195@carrick.bishnet.net> <20081112194735.GK47073@deviant.kiev.zoral.com.ua> <20081113004102.GD24360@carrick.bishnet.net> <20081113044200.GA10419@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081113044200.GA10419@icarus.home.lan> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on core.byshenk.net Cc: Jeremy Chadwick Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 16:41:38 -0000 On Wed, Nov 12, 2008 at 08:42:00PM -0800, Jeremy Chadwick wrote: > The rest of the below information is good -- but I'm confused about > something: is there anyone out there who can use mksnap_ffs on a > filesystem (/usr is a good test source) and NOT experience this > deadlocking problem? Literally *every* FreeBSD box I have root access > to suffers from this problem, so I'm a little baffled why we end-users > need to keep providing debugging output when it should be easy as pie > for a developer to do "dump -0 -L -a -f /path/fs.dump /usr" and watch > their system wedge. As an answer to the question (and additional information), I am experiencing the problem, but not on all filesystems. This is under FreeBSD 7.1-PRERELEASE #7: Thu Nov 6 11:29:52 CET 2008, amd64 (from sources csup'ed immediately prior to the build). I have four filesystems used for data storage: /dev/da1p1 96850470 7866026 81236408 9% /export/mail /dev/da1p2 1937058312 972070320 810023328 55% /export/home /dev/da1p3 1937058312 79027008 1703066640 4% /export/misc /dev/da1p4 2598991534 271980564 2119091648 11% /export/spare I can successfully mksnap_ffs the first (smaller) partition, but an attempt to do so on any of the others causes a lock. Note: this is a lockup, not a "slow". The system becomes unresponsive to any input, and there is no hard drive activity, and this does not change over a period of more than 12 hours. -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 17:38:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 087311065672; Thu, 13 Nov 2008 17:38:04 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.freebsd.org (Postfix) with ESMTP id C83948FC0A; Thu, 13 Nov 2008 17:38:03 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) X-Ambrisko-Me: Yes Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by ironport.ambrisko.com with ESMTP; 13 Nov 2008 09:38:14 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.14.1/8.14.1) with ESMTP id mADHc3aZ097313; Thu, 13 Nov 2008 09:38:03 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.14.1/8.14.1/Submit) id mADHc2Lh097312; Thu, 13 Nov 2008 09:38:02 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200811131738.mADHc2Lh097312@ambrisko.com> In-Reply-To: <20081113132109.GT47073@deviant.kiev.zoral.com.ua> To: Kostik Belousov Date: Thu, 13 Nov 2008 09:38:02 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: Tim Bishop , Jeremy Chadwick , freebsd-stable@freebsd.org Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 17:38:04 -0000 Kostik Belousov writes: | On Thu, Nov 13, 2008 at 02:45:14AM -0800, Jeremy Chadwick wrote: [snip] | > If he can press Control-T, it means SIGINFO can be sent to the | > mksnap_ffs process, and the process responds with that information. So, | > the system is not deadlocked -- meaning, I believe what he experiences | > is what others experience (the system becomes completely unusable during | > mksnap_ffs running, but DOES NOT hang or lock up, it just becomes so | > god-awful slow that processes on the machine literally sit and spin for | > minutes at a time). | | Unless NOKERNINFO is specified in the local flags in the controlling | terminal termios, kernel prints one line summary as shown above. This is | done from the tty discipline input handler (or whatever it is in new tty | code). No process cooperation is required. On the other hand, actually | delivering SIGINFO and getting output from the process-installed | handler do require process to either executing usermode or sleeping | interruptible. Also note that "dead-lock" is not just a locking issue but can be WRT to other chains such as, hit the max buffer cache usage so the buffer daemon needs to flush things out but it can't since it needs a buffer but the buffer daemon can't get it since need to flush some. Things get really bad when the buffer daemon needs a buffer but can't! In theory it can go and use "emergency space" just for it to get out of this situation but it the buffer cache is fragmented such that all available buffers are to small then the buffer daemon is stuck on itself. Note that all stuff works except for anything that touch the buffer cache, such as a program coming off disk. A program in memory is okay. To really get a good picture of this you need to look at the various buffer cache variables via ddb (ie. hi, low, running etc.) A while back I wrote a debugging function to dump that state of things every minute or so. There are various loops you can get into. So then you start playing wack a mole. Usually due to the first bug you can't hit the 2nd, 3rd and so one adding to the fun. Unfortunately there isn't one magic bullet. These are not new problems since we hit them in 4.X. I did start to go over some of this issue with Tor but ran into ENOTIME on my side :-( Snap shots can take a very long time to make depending on the amount of stuff it has to snap shot and during that time it has to effectively lock out everything from the file system or the snap shot will be wrong. This then leads to a need for a good journaling fs that can be used on "big" disks (big, isn't that big anymore). Doug A. From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 18:49:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 683AA1065670 for ; Thu, 13 Nov 2008 18:49:34 +0000 (UTC) (envelope-from reichcc@comcast.net) Received: from QMTA03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id 5C0218FC18 for ; Thu, 13 Nov 2008 18:49:34 +0000 (UTC) (envelope-from reichcc@comcast.net) Received: from OMTA09.emeryville.ca.mail.comcast.net ([76.96.30.20]) by QMTA03.emeryville.ca.mail.comcast.net with comcast id eawP1a0070S2fkCA3iZZs1; Thu, 13 Nov 2008 18:33:33 +0000 Received: from [192.168.5.230] ([98.199.139.49]) by OMTA09.emeryville.ca.mail.comcast.net with comcast id eiZT1a00P148M8q8ViZTCL; Thu, 13 Nov 2008 18:33:28 +0000 X-Authority-Analysis: v=1.0 c=1 a=becna3ql8DEA:10 a=0kYo9GeZAlkA:10 a=jo_sjndSW3kQ1XxQNmUA:9 a=9LrGp9x7HdGQLN004vAA:7 a=MsNhuEPkLad-e-BBj9mfO23dpwwA:4 a=I2EqgwFF2xUA:10 From: Patrick Reich To: freebsd-stable@freebsd.org Content-Type: text/plain Date: Thu, 13 Nov 2008 12:33:26 -0600 Message-Id: <1226601206.3091.37.camel@acheron> Mime-Version: 1.0 X-Mailer: Evolution 2.24.1.1 Content-Transfer-Encoding: 7bit Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 18:49:34 -0000 I'll just chime in briefly. I contacted Jeremy off the list about this issue a few days ago. I have one spare box i386 sitting here that I can happily test patches against; if I can be of help, let me know. > uname -a FreeBSD localhost.localdomain 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Tue Nov 11 21:40:27 CST 2008 user@localhost.localdomain:/usr/obj/usr/src/sys/GENERIC i386 > ident /boot/kernel/kernel | grep sleepqueue $FreeBSD: src/sys/kern/subr_sleepqueue.c,v 1.39.2.5 2008/09/16 20:01:57 jhb Exp $ Suffers from the description given by Jeremy: the box is not deadlocked during snapshot but I might as well walk away from it because I can't use it. I'd really like to see this get fixed; I rely on dump for backups. Regards, Pat -- "Jesus, can't I count on you people!?" --Oh Brother, Where Art Thou, George Clooney From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 21:37:31 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CCB71065679 for ; Thu, 13 Nov 2008 21:37:31 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id F372C8FC08 for ; Thu, 13 Nov 2008 21:37:30 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 1A57C1B1098 for ; Thu, 13 Nov 2008 16:37:30 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 13 Nov 2008 16:37:30 -0500 X-Sasl-enc: UznNyLNlCBYCLA3+2t+ZpY153sd/bc+sx/jpbEw+o0Dq 1226612249 Received: from anglepoise.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id A3A9A4739B for ; Thu, 13 Nov 2008 16:37:29 -0500 (EST) Message-ID: <491C9E11.7040703@incunabulum.net> Date: Thu, 13 Nov 2008 21:37:21 +0000 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.14 (X11/20080513) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: kern.ipc.maxpipekva exceeded; see tuning(7) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 21:37:31 -0000 I just got lots and lots of this: kern.ipc.maxpipekva exceeded; see tuning(7) However, tuning(7) on my system has no information about this tunable whatsoever. anglepoise:~ % uname -a FreeBSD anglepoise.lon.incunabulum.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Tue Nov 4 15:40:44 GMT 2008 root@anglepoise.lon.incunabulum.net:/home/obj/usr/src/sys/ANGLEPOISE7 amd64 anglepoise:~ % sysctl kern.ipc.maxpipekva kern.ipc.maxpipekva: 20971520 I was running a couple of copies of "synergys" at the time. After killing them, all seems fine, however this was causing most binaries on the system to error out with ENOMEM. Any ideas? BMS From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 21:56:03 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9215106568A for ; Thu, 13 Nov 2008 21:56:03 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id 8736E8FC18; Thu, 13 Nov 2008 21:56:03 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 1D1FA1B1B84; Thu, 13 Nov 2008 16:38:33 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 13 Nov 2008 16:38:33 -0500 X-Sasl-enc: cYXgSdH3uLofCXKV1ub9G1XTwmpuAtanGvpy4+k/Ui3Y 1226612312 Received: from anglepoise.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 64B2A473A3; Thu, 13 Nov 2008 16:38:32 -0500 (EST) Message-ID: <491C9E56.2050004@incunabulum.net> Date: Thu, 13 Nov 2008 21:38:30 +0000 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.14 (X11/20080513) MIME-Version: 1.0 To: Patrick Tracanelli References: <49199F76.5010800@freebsdbrasil.com.br> In-Reply-To: <49199F76.5010800@freebsdbrasil.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, releng@freebsd.org Subject: Re: MFC Request X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 21:56:03 -0000 Patrick Tracanelli wrote: > Is it possible to have traceroute MFC'd for 7.1? I would like to have > -a and -A switchs (ASN Path mapping) available. Thank you :) > There's an AS lookup capable traceroute in ports: /usr/ports/net/ntraceroute is this insufficient for your needs? thanks BMS From owner-freebsd-stable@FreeBSD.ORG Thu Nov 13 22:55:07 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D603106568C for ; Thu, 13 Nov 2008 22:55:07 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from pele.citylink.co.nz (pele.citylink.co.nz [202.8.44.226]) by mx1.freebsd.org (Postfix) with ESMTP id 489ED8FC08; Thu, 13 Nov 2008 22:55:07 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id 1BDD72BC41; Fri, 14 Nov 2008 11:32:51 +1300 (NZDT) X-Virus-Scanned: Debian amavisd-new at citylink.co.nz Received: from pele.citylink.co.nz ([127.0.0.1]) by localhost (pele.citylink.co.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DBe1rAjD1Xre; Fri, 14 Nov 2008 11:32:47 +1300 (NZDT) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Fri, 14 Nov 2008 11:32:47 +1300 (NZDT) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id BD5DD1142A; Fri, 14 Nov 2008 11:32:46 +1300 (NZDT) Date: Thu, 13 Nov 2008 14:32:46 -0800 From: Andrew Thompson To: Bruce Simpson Message-ID: <20081113223246.GA79815@citylink.fud.org.nz> References: <49199F76.5010800@freebsdbrasil.com.br> <491C9E56.2050004@incunabulum.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <491C9E56.2050004@incunabulum.net> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Patrick Tracanelli , stable@freebsd.org, releng@freebsd.org Subject: Re: MFC Request X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2008 22:55:07 -0000 On Thu, Nov 13, 2008 at 09:38:30PM +0000, Bruce Simpson wrote: > Patrick Tracanelli wrote: >> Is it possible to have traceroute MFC'd for 7.1? I would like to have -a >> and -A switchs (ASN Path mapping) available. Thank you :) >> > > There's an AS lookup capable traceroute in ports: > /usr/ports/net/ntraceroute > > is this insufficient for your needs? Also note that Rui has completed the traceroute MFC for 7.1 From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 00:23:39 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3256C106567A for ; Fri, 14 Nov 2008 00:23:39 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id 178C88FC1C for ; Fri, 14 Nov 2008 00:23:38 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 1CBDC33C62 for ; Thu, 13 Nov 2008 15:55:00 -0800 (PST) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id C020A33C5B for ; Thu, 13 Nov 2008 15:54:59 -0800 (PST) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18716.48723.452606.66518@almost.alerce.com> Date: Thu, 13 Nov 2008 15:54:59 -0800 To: freebsd-stable@freebsd.org X-Mailer: VM 7.19 under Emacs 22.1.50.1 X-Virus-Scanned: ClamAV using ClamSMTP Subject: problem moving gmirror between two machines. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 00:23:39 -0000 I have an HP DL360 with a pair of 1TB seagate disks that's been running -STABLE with a ZFS root partition set up using the tools available here: http://yds.coolrat.org/zfsboot.shtml It's been working great. As part of trying to understand what's going on, I csup'ed to -RELENG earlier today and rebuilt/installed the kernel and world whilst running on the DL360, so everything should be current. I tried to move the disks into an HP DL320 G4 and it fails to boot because it can't find /dev/mirror/boot (which it wants to mount onto /strap and then parts get nullfs'ed onto /boot and /rescue). It gives me the opportunity to start a shell, and from that shell I can do a zfs mount -a and get all of the zfs filesystems mounted, but there's nothing in /dev/mirror. No gmirror status and list are silent. I can move the disks back into the older machine and they work fine. I've run fdisk -s ad4 and bsdlabel -A /dev/ad4s1a and diffed the output from the two machines and they're identical. I've booted with kern.geom.mirror.debug=2 and the DL320G4 tastes /dev/ad4s1a (along with everything else) but doesn't do anything with it. Any ideas? g. From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 02:49:19 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3232C1065673 for ; Fri, 14 Nov 2008 02:49:19 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id F03B38FC0A for ; Fri, 14 Nov 2008 02:49:18 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1125707rvf.43 for ; Thu, 13 Nov 2008 18:49:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=etWlOhOlwxO4zsUqj64qiZ58lBLKIZypjrx/XGVT3iw=; b=UMJ71eUVlXSIZI5DcM1iMRiM73CYIZK7wXztCsBRKneBWZnb+rgCF6lTalzGaiCtIN /Ej01o4NyQVqDYEJd9qWgkYX72wivc9iZYUj7G22zXcOpRJkIglUzQbSskTWuogSy030 s4P3x5vuykq0nqyZtgniT0WFdpnVddSVwuFy4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=c5wrBD+4aYDGVdhSbM/obC6v9Rd1p6KuwFdwPqGcpCyk7jQG0ezDcTTP87hle0NHN8 4vR+36Qc1QTS+bF7/4hDQ9OKRkN1EkTVacl4ZNtI/t6gai5Fxt+rk4b7zaHYInGFAOsL AQQtoVhyhi2LR48OBc988feCDOmPJ3sRUmV/Q= Received: by 10.141.87.13 with SMTP id p13mr233950rvl.81.1226629177538; Thu, 13 Nov 2008 18:19:37 -0800 (PST) Received: by 10.141.101.21 with HTTP; Thu, 13 Nov 2008 18:19:37 -0800 (PST) Message-ID: <3c1674c90811131819s199c836av33e51ebe131c1dcd@mail.gmail.com> Date: Fri, 14 Nov 2008 02:19:37 +0000 From: "Kip Macy" Sender: mat.macy@gmail.com To: "Bruce Simpson" In-Reply-To: <491C9E11.7040703@incunabulum.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <491C9E11.7040703@incunabulum.net> X-Google-Sender-Auth: 0f00b8d213c82eb0 Cc: freebsd-stable@freebsd.org Subject: Re: kern.ipc.maxpipekva exceeded; see tuning(7) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 02:49:19 -0000 I don't know off hand how you could end up with that many pipes. Nonetheless, sys_pipe.c has a good explanation of what that does and how pipe sizing works. -Kip On Thu, Nov 13, 2008 at 9:37 PM, Bruce Simpson wrote: > I just got lots and lots of this: > kern.ipc.maxpipekva exceeded; see tuning(7) > > However, tuning(7) on my system has no information about this tunable > whatsoever. > > anglepoise:~ % uname -a > FreeBSD anglepoise.lon.incunabulum.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE > #3: Tue Nov 4 15:40:44 GMT 2008 > root@anglepoise.lon.incunabulum.net:/home/obj/usr/src/sys/ANGLEPOISE7 amd64 > anglepoise:~ % sysctl kern.ipc.maxpipekva > kern.ipc.maxpipekva: 20971520 > > I was running a couple of copies of "synergys" at the time. After killing > them, all seems fine, however this was causing most binaries on the system > to error out with ENOMEM. > > Any ideas? > BMS > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 02:49:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29B31106568B; Fri, 14 Nov 2008 02:49:21 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 605548FC12; Fri, 14 Nov 2008 02:49:19 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 6253928454; Fri, 14 Nov 2008 10:49:18 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id 2AA95EC5BFB; Fri, 14 Nov 2008 10:49:18 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id ApQQN2kjty6X; Fri, 14 Nov 2008 10:49:12 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-62.dsl.pltn13.sbcglobal.net [76.237.33.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 8ECE0EC5B92; Fri, 14 Nov 2008 10:49:07 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:x-enigmail-version:openpgp:content-type; b=gbRBXLilC6DijNA0+qFEd3bxHd8AlXQPnWAA86lKBwUs3zGDS6GRcZe1N3bsnCP6x H4LYqIqn2TDCIogcfD6bw== Message-ID: <491CE71F.2020208@delphij.net> Date: Thu, 13 Nov 2008 18:49:03 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.17 (X11/20080928) MIME-Version: 1.0 To: FreeBSD Stable , Pawel Jakub Dawidek X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: multipart/mixed; boundary="------------060902050107000202090406" Cc: Quake Lee Subject: ZFS crashes on heavy threaded environment X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 02:49:21 -0000 This is a multi-part message in MIME format. --------------060902050107000202090406 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Pawel, We can still reproduce the ZFS crash (threading+heavy I/O load) on a fresh 7.1-STABLE build, in a few minutes: /usr/local/bin/iozone -M -e -+u -T -t 128 -S 4096 -L 64 -r 4k -s 30g -i 0 -i 1 -i 2 -i 8 -+p 70 -C I have included a backtrace output from my colleague who has his hands on the test environment. Should there is more information necessary please let us know and we wish to provide help on this. It looks like that the problem has been fixed with the new ZFS version in the last patchset against -CURRENT though. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkc5x8ACgkQi+vbBBjt66B4igCfQTz0FM2yFYFwyJY26dVmdXCq ZeIAoJWGeWaBPNH31ZOoAnbbnottGzKQ =tcMs -----END PGP SIGNATURE----- --------------060902050107000202090406 Content-Type: text/plain; name="transcript.txt" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="transcript.txt" U2NyaXB0IHN0YXJ0ZWQgb24gRnJpIE5vdiAxNCAxMDozNjozMyAyMDA4CkdOVSBnZGIgNi4x LjEgW0ZyZWVCU0RdDQpDb3B5cmlnaHQgMjAwNCBGcmVlIFNvZnR3YXJlIEZvdW5kYXRpb24s IEluYy4NCkdEQiBpcyBmcmVlIHNvZnR3YXJlLCBjb3ZlcmVkIGJ5IHRoZSBHTlUgR2VuZXJh bCBQdWJsaWMgTGljZW5zZSwgYW5kIHlvdSBhcmUNCndlbGNvbWUgdG8gY2hhbmdlIGl0IGFu ZC9vciBkaXN0cmlidXRlIGNvcGllcyBvZiBpdCB1bmRlciBjZXJ0YWluIGNvbmRpdGlvbnMu DQpUeXBlICJzaG93IGNvcHlpbmciIHRvIHNlZSB0aGUgY29uZGl0aW9ucy4NClRoZXJlIGlz IGFic29sdXRlbHkgbm8gd2FycmFudHkgZm9yIEdEQi4gIFR5cGUgInNob3cgd2FycmFudHki IGZvciBkZXRhaWxzLg0KVGhpcyBHREIgd2FzIGNvbmZpZ3VyZWQgYXMgImFtZDY0LW1hcmNl bC1mcmVlYnNkIi4uLg0KDQpVbnJlYWQgcG9ydGlvbiBvZiB0aGUga2VybmVsIG1lc3NhZ2Ug YnVmZmVyOg0KDQoNCkZhdGFsIHRyYXAgMTI6IHBhZ2UgZmF1bHQgd2hpbGUgaW4ga2VybmVs IG1vZGUNCmNwdWlkID0gMDsgYXBpYyBpZCA9IDAwDQpmYXVsdCB2aXJ0dWFsIGFkZHJlc3MJ PSAweDE4DQpmYXVsdCBjb2RlCQk9IHN1cGVydmlzb3IgcmVhZCBkYXRhLCBwYWdlIG5vdCBw cmVzZW50DQppbnN0cnVjdGlvbiBwb2ludGVyCT0gMHg4OjB4ZmZmZmZmZmZiNDgzOWZiNg0K c3RhY2sgcG9pbnRlcgkgICAgICAgID0gMHgxMDoweGZmZmZmZmZmYjRiZWI4ZjANCmZyYW1l IHBvaW50ZXIJICAgICAgICA9IDB4MTA6MHhmZmZmZmZmZmI0YmViOTIwDQpjb2RlIHNlZ21l bnQJCT0gYmFzZSAweDAsIGxpbWl0IDB4ZmZmZmYsIHR5cGUgMHgxYg0KCQkJPSBEUEwgMCwg cHJlcyAxLCBsb25nIDEsIGRlZjMyIDAsIGdyYW4gMQ0KcHJvY2Vzc29yIGVmbGFncwk9IGlu dGVycnVwdCBlbmFibGVkLCByZXN1bWUsIElPUEwgPSAwDQpjdXJyZW50IHByb2Nlc3MJCT0g MzI2ICh0eGdfdGhyZWFkX2VudGVyKQ0KdHJhcCBudW1iZXIJCT0gMTINCnBhbmljOiBwYWdl IGZhdWx0DQpjcHVpZCA9IDANClVwdGltZTogOG0xNXMNClBoeXNpY2FsIG1lbW9yeTogODE3 NSBNQg0KRHVtcGluZyA2MjkgTUI6IDYxNCA1OTggNTgyIDU2NiA1NTAgNTM0IDUxOCA1MDIg NDg2IDQ3MCA0NTQgNDM4IDQyMiA0MDYgMzkwIDM3NCAzNTggMzQyIDMyNiAzMTAgMjk0IDI3 OCAyNjIgMjQ2IDIzMCAyMTQgMTk4IDE4MiAxNjYgMTUwIDEzNCAxMTggMTAyIDg2IDcwIDU0 IDM4IDIyIDYNCg0KUmVhZGluZyBzeW1ib2xzIGZyb20gL2Jvb3Qva2VybmVsL3pmcy5rby4u LlJlYWRpbmcgc3ltYm9scyBmcm9tIC9ib290L2tlcm5lbC96ZnMua28uc3ltYm9scy4uLmRv bmUuDQpkb25lLg0KTG9hZGVkIHN5bWJvbHMgZm9yIC9ib290L2tlcm5lbC96ZnMua28NClJl YWRpbmcgc3ltYm9scyBmcm9tIC9ib290L2tlcm5lbC9vcGVuc29sYXJpcy5rby4uLlJlYWRp bmcgc3ltYm9scyBmcm9tIC9ib290L2tlcm5lbC9vcGVuc29sYXJpcy5rby5zeW1ib2xzLi4u ZG9uZS4NCmRvbmUuDQpMb2FkZWQgc3ltYm9scyBmb3IgL2Jvb3Qva2VybmVsL29wZW5zb2xh cmlzLmtvDQojMCAgZG9hZHVtcCAoKSBhdCBwY3B1Lmg6MTk1DQoxOTUJcGNwdS5oOiBObyBz dWNoIGZpbGUgb3IgZGlyZWN0b3J5Lg0KCWluIHBjcHUuaA0KKGtnZGIpIGJ0DQojMCAgZG9h ZHVtcCAoKSBhdCBwY3B1Lmg6MTk1DQojMSAgMHhmZmZmZmZmZmI0YmViNTkwIGluID8/ICgp DQojMiAgMHhmZmZmZmZmZjgwNDNjYzU5IGluIGJvb3QgKGhvd3RvPTI2MCkgYXQgL3Vzci9z cmMvc3lzL2tlcm4va2Vybl9zaHV0ZG93bi5jOjQxOA0KIzMgIDB4ZmZmZmZmZmY4MDQzZDA2 MiBpbiBwYW5pYyAoZm10PTB4MTA0IDxBZGRyZXNzIDB4MTA0IG91dCBvZiBib3VuZHM+KSBh dCAvdXNyL3NyYy9zeXMva2Vybi9rZXJuX3NodXRkb3duLmM6NTc0DQojNCAgMHhmZmZmZmZm ZjgwNmQ0YzQzIGluIHRyYXBfZmF0YWwgKGZyYW1lPTB4ZmZmZmZmMDAwNDgxYjM3MCwgZXZh PVZhcmlhYmxlICJldmEiIGlzIG5vdCBhdmFpbGFibGUuDQopIGF0IC91c3Ivc3JjL3N5cy9h bWQ2NC9hbWQ2NC90cmFwLmM6NzY0DQojNSAgMHhmZmZmZmZmZjgwNmQ1MDE1IGluIHRyYXBf cGZhdWx0IChmcmFtZT0weGZmZmZmZmZmYjRiZWI4NDAsIHVzZXJtb2RlPTApIGF0IC91c3Iv c3JjL3N5cy9hbWQ2NC9hbWQ2NC90cmFwLmM6NjgwDQojNiAgMHhmZmZmZmZmZjgwNmQ1OTU4 IGluIHRyYXAgKGZyYW1lPTB4ZmZmZmZmZmZiNGJlYjg0MCkgYXQgL3Vzci9zcmMvc3lzL2Ft ZDY0L2FtZDY0L3RyYXAuYzo0NDkNCiM3ICAweGZmZmZmZmZmODA2YmIxNGUgaW4gY2FsbHRy YXAgKCkgYXQgL3Vzci9zcmMvc3lzL2FtZDY0L2FtZDY0L2V4Y2VwdGlvbi5TOjIwOQ0KIzgg IDB4ZmZmZmZmZmZiNDgzOWZiNiBpbiBkbXVfb2Jqc2V0X3N5bmNfZG5vZGVzIChsaXN0PTB4 ZmZmZmZmMDAwNDdmNDZjMCwgdHg9MHhmZmZmZmYwMDA0ZjMzMjgwKQ0KICAgIGF0IC91c3Iv c3JjL3N5cy9tb2R1bGVzL3pmcy8uLi8uLi9jZGRsL2NvbnRyaWIvb3BlbnNvbGFyaXMvdXRz L2NvbW1vbi9mcy96ZnMvZG11X29ianNldC5jOjcwNw0KIzkgIDB4ZmZmZmZmZmZiNDgzYTEx ZCBpbiBkbXVfb2Jqc2V0X3N5bmMgKG9zPTB4ZmZmZmZmMDAwNDdmNDYwMCwgcGlvPTB4ZmZm ZmZmMDAwNDM2N2FjMCwgdHg9MHhmZmZmZmYwMDA0ZjMzMjgwKQ0KICAgIGF0IC91c3Ivc3Jj L3N5cy9tb2R1bGVzL3pmcy8uLi8uLi9jZGRsL2NvbnRyaWIvb3BlbnNvbGFyaXMvdXRzL2Nv bW1vbi9mcy96ZnMvZG11X29ianNldC5jOjgwOQ0KIzEwIDB4ZmZmZmZmZmZiNDg0NzZmMiBp biBkc2xfcG9vbF9zeW5jIChkcD0weGZmZmZmZjAwMDQ3OWU0MDAsIHR4Zz00ODY0KSBhdCAv dXNyL3NyYy9zeXMvbW9kdWxlcy96ZnMvLi4vLi4vY2RkbC9jb250cmliL29wZW5zb2xhcmlz L3V0cy9jb21tb24vZnMvemZzL2RzbF9wb29sLmM6MTg4DQojMTEgMHhmZmZmZmZmZmI0ODUy MDIwIGluIHNwYV9zeW5jIChzcGE9MHhmZmZmZmYwMDA0MDI4MDAwLCB0eGc9NDg2NCkgYXQg L3Vzci9zcmMvc3lzL21vZHVsZXMvemZzLy4uLy4uL2NkZGwvY29udHJpYi9vcGVuc29sYXJp cy91dHMvY29tbW9uL2ZzL3pmcy9zcGEuYzoyOTg5DQojMTIgMHhmZmZmZmZmZmI0ODU3ZWVm IGluIHR4Z19zeW5jX3RocmVhZCAoYXJnPVZhcmlhYmxlICJhcmciIGlzIG5vdCBhdmFpbGFi bGUuDQopIGF0IC91c3Ivc3JjL3N5cy9tb2R1bGVzL3pmcy8uLi8uLi9jZGRsL2NvbnRyaWIv b3BlbnNvbGFyaXMvdXRzL2NvbW1vbi9mcy96ZnMvdHhnLmM6MzMxDQojMTMgMHhmZmZmZmZm ZjgwNDFhZTUzIGluIGZvcmtfZXhpdCAoY2FsbG91dD0weGZmZmZmZmZmYjQ4NTdkYzAgPHR4 Z19zeW5jX3RocmVhZD4sIGFyZz0weGZmZmZmZjAwMDQ3OWU0MDAsIGZyYW1lPTB4ZmZmZmZm ZmZiNGJlYmM4MCkgYXQgL3Vzci9zcmMvc3lzL2tlcm4va2Vybl9mb3JrLmM6ODA0DQojMTQg MHhmZmZmZmZmZjgwNmJiNTFlIGluIGZvcmtfdHJhbXBvbGluZSAoKSBhdCAvdXNyL3NyYy9z eXMvYW1kNjQvYW1kNjQvZXhjZXB0aW9uLlM6NDU1DQojMTUgMHgwMDAwMDAwMDAwMDAwMDAw IGluID8/ICgpDQojMTYgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojMTcgMHgwMDAw MDAwMDAwMDAwMDAxIGluID8/ICgpDQojMTggMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgp DQojMTkgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojMjAgMHgwMDAwMDAwMDAwMDAw MDAwIGluID8/ICgpDQojMjEgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojMjIgMHgw MDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojMjMgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ ICgpDQojMjQgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojMjUgMHgwMDAwMDAwMDAw MDAwMDAwIGluID8/ICgpDQojMjYgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojMjcg MHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojMjggMHgwMDAwMDAwMDAwMDAwMDAwIGlu ID8/ICgpDQojMjkgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojMzAgMHgwMDAwMDAw MDAwMDAwMDAwIGluID8/ICgpDQojMzEgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQoj MzIgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojMzMgMHgwMDAwMDAwMDAwMDAwMDAw IGluID8/ICgpDQojMzQgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojMzUgMHgwMDAw MDAwMDAwMDAwMDAwIGluID8/ICgpDQojMzYgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgp DQojMzcgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojMzggMHgwMDAwMDAwMDAwMDAw MDAwIGluID8/ICgpDQojMzkgMHgwMDAwMDAwMDAwYzQxMDAwIGluID8/ICgpDQojNDAgMHhm ZmZmZmZmZjgwOWRhODgwIGluIHRkZ19tYXhpZCAoKQ0KLS0tVHlwZSA8cmV0dXJuPiB0byBj b250aW51ZSwgb3IgcSA8cmV0dXJuPiB0byBxdWl0LS0tDQojNDEgMHhmZmZmZmZmZjgwOWU3 MDgwIGluIHRkcV9jcHUgKCkNCiM0MiAweGZmZmZmZmZmODA5ZTcwODAgaW4gdGRxX2NwdSAo KQ0KIzQzIDB4ZmZmZmZmMDAwNDgxYjM3MCBpbiA/PyAoKQ0KIzQ0IDB4ZmZmZmZmMDAwNDgx YjZhMCBpbiA/PyAoKQ0KIzQ1IDB4ZmZmZmZmZmZiNGJlYjFjOCBpbiA/PyAoKQ0KIzQ2IDB4 MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzQ3IDB4ZmZmZmZmZmY4MDQ1ZDhiOCBpbiBz Y2hlZF9zd2l0Y2ggKHRkPTB4ZmZmZmZmZmZiNDg1N2RjMCwgbmV3dGQ9MHg4MDA1NWE1ZDAs IGZsYWdzPVZhcmlhYmxlICJmbGFncyIgaXMgbm90IGF2YWlsYWJsZS4NCikgYXQgL3Vzci9z cmMvc3lzL2tlcm4vc2NoZWRfdWxlLmM6MTkzOA0KIzQ4IDB4MDAwMDAwMDAwMDAwMDAwMCBp biA/PyAoKQ0KIzQ5IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzUwIDB4MDAwMDAw MDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzUxIDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0K IzUyIDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzUzIDB4MDAwMDAwMDAwMDAwMDAw MCBpbiA/PyAoKQ0KIzU0IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzU1IDB4MDAw MDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzU2IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAo KQ0KIzU3IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzU4IDB4MDAwMDAwMDAwMDAw MDAwMCBpbiA/PyAoKQ0KIzU5IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzYwIDB4 MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzYxIDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/ PyAoKQ0KIzYyIDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzYzIDB4MDAwMDAwMDAw MDAwMDAwMCBpbiA/PyAoKQ0KIzY0IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzY1 IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzY2IDB4MDAwMDAwMDAwMDAwMDAwMCBp biA/PyAoKQ0KIzY3IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzY4IDB4MDAwMDAw MDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzY5IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0K IzcwIDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzcxIDB4MDAwMDAwMDAwMDAwMDAw MCBpbiA/PyAoKQ0KIzcyIDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzczIDB4MDAw MDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzc0IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAo KQ0KIzc1IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzc2IDB4MDAwMDAwMDAwMDAw MDAwMCBpbiA/PyAoKQ0KIzc3IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzc4IDB4 MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzc5IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/ PyAoKQ0KIzgwIDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzgxIDB4MDAwMDAwMDAw MDAwMDAwMCBpbiA/PyAoKQ0KIzgyIDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzgz IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KLS0tVHlwZSA8cmV0dXJuPiB0byBjb250 aW51ZSwgb3IgcSA8cmV0dXJuPiB0byBxdWl0LS0tDQojODQgMHgwMDAwMDAwMDAwMDAwMDAw IGluID8/ICgpDQojODUgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojODYgMHgwMDAw MDAwMDAwMDAwMDAwIGluID8/ICgpDQojODcgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgp DQojODggMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojODkgMHgwMDAwMDAwMDAwMDAw MDAwIGluID8/ICgpDQojOTAgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojOTEgMHgw MDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojOTIgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ ICgpDQojOTMgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojOTQgMHgwMDAwMDAwMDAw MDAwMDAwIGluID8/ICgpDQojOTUgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojOTYg MHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojOTcgMHgwMDAwMDAwMDAwMDAwMDAwIGlu ID8/ICgpDQojOTggMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojOTkgMHgwMDAwMDAw MDAwMDAwMDAwIGluID8/ICgpDQojMTAwIDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0K IzEwMSAweDAwMDAwMDAwMDAwMDAwMDAgaW4gPz8gKCkNCiMxMDIgMHgwMDAwMDAwMDAwMDAw MDAwIGluID8/ICgpDQojMTAzIDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzEwNCAw eDAwMDAwMDAwMDAwMDAwMDAgaW4gPz8gKCkNCiMxMDUgMHgwMDAwMDAwMDAwMDAwMDAwIGlu ID8/ICgpDQojMTA2IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzEwNyAweDAwMDAw MDAwMDAwMDAwMDAgaW4gPz8gKCkNCiMxMDggMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgp DQojMTA5IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzExMCAweDAwMDAwMDAwMDAw MDAwMDAgaW4gPz8gKCkNCiMxMTEgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojMTEy IDB4MDAwMDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KIzExMyAweDAwMDAwMDAwMDAwMDAwMDAg aW4gPz8gKCkNCiMxMTQgMHgwMDAwMDAwMDAwMDAwMDAwIGluID8/ICgpDQojMTE1IDB4MDAw MDAwMDAwMDAwMDAwMCBpbiA/PyAoKQ0KQ2Fubm90IGFjY2VzcyBtZW1vcnkgYXQgYWRkcmVz cyAweGZmZmZmZmZmYjRiZWMwMDANCihrZ2RiKSBxdWl0DQoKU2NyaXB0IGRvbmUgb24gRnJp IE5vdiAxNCAxMDozNjo0MyAyMDA4Cg== --------------060902050107000202090406-- From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 02:53:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53DB0106567C; Fri, 14 Nov 2008 02:53:52 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id E781B8FC19; Fri, 14 Nov 2008 02:53:51 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id B91A528454; Fri, 14 Nov 2008 10:53:50 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id 83471EC5C01; Fri, 14 Nov 2008 10:53:50 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id t9DITqqOeppB; Fri, 14 Nov 2008 10:53:45 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-62.dsl.pltn13.sbcglobal.net [76.237.33.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 2BD33EC5B92; Fri, 14 Nov 2008 10:53:43 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=pGm3nIVMevtQabSi5+NpkcI2699vxH0F2e9YTwNW38y4I81AvtLH2emXm0gacVFWV ZzT1VucTYZkaDz3iOsl4w== Message-ID: <491CE835.4050504@delphij.net> Date: Thu, 13 Nov 2008 18:53:41 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.17 (X11/20080928) MIME-Version: 1.0 To: d@delphij.net References: <491CE71F.2020208@delphij.net> In-Reply-To: <491CE71F.2020208@delphij.net> X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Pawel Jakub Dawidek , FreeBSD Stable , Quake Lee Subject: Re: ZFS crashes on heavy threaded environment X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 02:53:52 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xin LI wrote: > Hi, Pawel, > > We can still reproduce the ZFS crash (threading+heavy I/O load) on a > fresh 7.1-STABLE build, in a few minutes: > > /usr/local/bin/iozone -M -e -+u -T -t 128 -S 4096 -L 64 -r 4k -s 30g -i > 0 -i 1 -i 2 -i 8 -+p 70 -C > > I have included a backtrace output from my colleague who has his hands > on the test environment. Should there is more information necessary > please let us know and we wish to provide help on this. Further datapoint. The system used to run with untuned loader.conf, and my colleague just reported that with the following loader.conf, the problem can be triggered sooner: vm.kmem_size_max=838860800 vm.kmem_size_scale="2" The system is running FreeBSD/amd64 7.1-PRERELEASE equipped with 8GB of RAM with GENERIC kernel. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkc6DUACgkQi+vbBBjt66Cf7ACgjkeem1RLtDGCPF4MSvWY/1bz QvoAnjMIniOouszCIWl9JPLUn8KRuKlP =UchH -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 03:25:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF6F41065697 for ; Fri, 14 Nov 2008 03:25:38 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id A3AD18FC14 for ; Fri, 14 Nov 2008 03:25:38 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 62A8233C62; Thu, 13 Nov 2008 19:25:38 -0800 (PST) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id E67B733C5B; Thu, 13 Nov 2008 19:25:37 -0800 (PST) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18716.61361.242320.333557@almost.alerce.com> Date: Thu, 13 Nov 2008 19:25:37 -0800 To: hartzell@alerce.com In-Reply-To: <18716.48723.452606.66518@almost.alerce.com> References: <18716.48723.452606.66518@almost.alerce.com> X-Mailer: VM 7.19 under Emacs 22.1.50.1 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: Re: problem moving gmirror between two machines. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 03:25:38 -0000 George Hartzell writes: > [...] > It's been working great. As part of trying to understand what's going > on, I csup'ed to -RELENG earlier today and rebuilt/installed the > kernel and world whilst running on the DL360, so everything should be > current. > [...] Just to be clear, I mean that I have an up to date version of -STABLE on the machine (it claims to be 7.1-PRERELEASE), not that I'm running -CURRENT. g. From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 07:39:22 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95C351065673 for ; Fri, 14 Nov 2008 07:39:22 +0000 (UTC) (envelope-from axel@dnepr.net) Received: from mail.dnepr.net (mail.dnepr.net [217.198.131.97]) by mx1.freebsd.org (Postfix) with ESMTP id 4A9378FC0A for ; Fri, 14 Nov 2008 07:39:22 +0000 (UTC) (envelope-from axel@dnepr.net) Received: from gx.dnepr.net ([217.198.131.109]) by mail.dnepr.net with esmtp id 1L0t6z-0008MS-K9 for freebsd-stable@freebsd.org; Fri, 14 Nov 2008 09:29:01 +0200 Message-ID: <491D28BD.4050309@dnepr.net> Date: Fri, 14 Nov 2008 09:29:01 +0200 From: Oleg Kozheltsev Organization: ISP EuroNet User-Agent: Thunderbird 2.0.0.17 (X11/20081105) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: can't write dvd (interrupt storm) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 07:39:22 -0000 Hello, yesterday I buy new motherboard INTEL DP43TF and now I can't write dvd disks in any format (on PATA dvd-drive). but still can read any dvd and cd. cd write and blank procedure for dvd-rw done well too. when I start write dvd by growisofs (/dev/cd0 - atapicam), in log I get: Nov 14 08:28:06 gx kernel: acd0: FAILURE - RESERVE_TRACK ILLEGAL REQUEST asc=0x30 ascq=0x05 Nov 14 08:28:06 gx kernel: interrupt storm detected on "irq4:"; throttling interrupt source Nov 14 08:28:50 gx last message repeated times Nov 14 08:31:07 gx kernel: acd0: FAILURE - WRITE_BIG timed out if I use burncd (/dev/acd0. with, or without atapicam in kernel), then I get only second string in log. before upgrade, I had 6.3-RELEASE-p3, update to 7.0-RELEASE-p5, and after to 7.1-PRELEASE #5, it doesn't change anything. drive configuration in BIOS - too (change only SATA controller ICH10/AHCI). this IRQ is also used by USB and COM. turning off both in BIOS and/or kernel change IRQ map, but drive still not work correctly. present or not ACPI module - doesn't matter too. by the way, COM port I also can't reach (/dev/cuad0), but without interrupt storm in log's (through APCI or ISA. even if USB and atapicd is turned off). someone had the same problem?... thanks for attention :) system info: FreeBSD gx.dnepr.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Nov 13 16:23:09 EET 2008 root@gx.dnepr.net:/usr/obj/usr/src/sys/KERN i386 pcib3: irq 4 at device 28.3 on pci0 pci3: on pcib3 atapci0: port 0xd040-0xd047,0xd030-0xd033,0xd020-0xd027,0xd010-0xd013,0xd000-0xd00f irq 4 at device 0.0 on pci3 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered uhci4: port 0xf060-0xf07f irq 4 at device 29.1 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A acd0: DVDR at ata2- UDMA33 cd0 at ata2 bus 0 target 1 lun 0 cd0: <_NEC DVD_RW ND-3550A 1.05> Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present (if media present in boot time - interrupt storm again) From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 09:26:11 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 091D6106567B for ; Fri, 14 Nov 2008 09:26:11 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (core.byshenk.net [62.58.73.230]) by mx1.freebsd.org (Postfix) with ESMTP id 6CD118FC17 for ; Fri, 14 Nov 2008 09:26:10 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (localhost.aoes.com [127.0.0.1]) by core.byshenk.net (8.14.3/8.14.3) with ESMTP id mAE9Q8ck015860 for ; Fri, 14 Nov 2008 10:26:08 +0100 (CET) (envelope-from byshenknet@core.byshenk.net) Received: (from byshenknet@localhost) by core.byshenk.net (8.14.3/8.14.3/Submit) id mAE9Q84h015859 for freebsd-stable@freebsd.org; Fri, 14 Nov 2008 10:26:08 +0100 (CET) (envelope-from byshenknet) Date: Fri, 14 Nov 2008 10:26:08 +0100 From: Greg Byshenk To: freebsd-stable@freebsd.org Message-ID: <20081114092608.GP907@core.byshenk.net> References: <20081112175826.GD26195@carrick.bishnet.net> <20081112194735.GK47073@deviant.kiev.zoral.com.ua> <20081113004102.GD24360@carrick.bishnet.net> <20081113044200.GA10419@icarus.home.lan> <20081113160810.GN907@core.byshenk.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081113160810.GN907@core.byshenk.net> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on core.byshenk.net Subject: Re: System deadlock when using mksnap_ffs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 09:26:11 -0000 On Thu, Nov 13, 2008 at 05:08:10PM +0100, Greg Byshenk wrote: > On Wed, Nov 12, 2008 at 08:42:00PM -0800, Jeremy Chadwick wrote: > > > The rest of the below information is good -- but I'm confused about > > something: is there anyone out there who can use mksnap_ffs on a > > filesystem (/usr is a good test source) and NOT experience this > > deadlocking problem? Literally *every* FreeBSD box I have root access > > to suffers from this problem, so I'm a little baffled why we end-users > > need to keep providing debugging output when it should be easy as pie > > for a developer to do "dump -0 -L -a -f /path/fs.dump /usr" and watch > > their system wedge. > > As an answer to the question (and additional information), I am > experiencing the problem, but not on all filesystems. > > This is under FreeBSD 7.1-PRERELEASE #7: Thu Nov 6 11:29:52 CET 2008, > amd64 (from sources csup'ed immediately prior to the build). > > I have four filesystems used for data storage: > > /dev/da1p1 96850470 7866026 81236408 9% /export/mail > /dev/da1p2 1937058312 972070320 810023328 55% /export/home > /dev/da1p3 1937058312 79027008 1703066640 4% /export/misc > /dev/da1p4 2598991534 271980564 2119091648 11% /export/spare > > I can successfully mksnap_ffs the first (smaller) partition, but an > attempt to do so on any of the others causes a lock. > > Note: this is a lockup, not a "slow". The system becomes unresponsive > to any input, and there is no hard drive activity, and this does not > change over a period of more than 12 hours. As a followup to my own post, after reading this discussion, I applied the patches and rebuild my system last night. As of today, with the patched ffs_snapshot.c, I can now make snapshots of all the filesystems listed above. It takes rather a long time, but that is to be expected, I think, and the snapshots finish normally. -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 09:52:32 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD9051065782 for ; Fri, 14 Nov 2008 09:52:32 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 54E428FC0A for ; Fri, 14 Nov 2008 09:52:32 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1L0vLq-0006zD-Ja for freebsd-stable@freebsd.org; Fri, 14 Nov 2008 09:52:30 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 14 Nov 2008 09:52:30 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 14 Nov 2008 09:52:30 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Fri, 14 Nov 2008 10:51:51 +0100 Lines: 56 Message-ID: References: <491CE71F.2020208@delphij.net> <491CE835.4050504@delphij.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDB7F2FA47EAE64879C2B0653" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.17 (X11/20080925) In-Reply-To: <491CE835.4050504@delphij.net> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: ZFS crashes on heavy threaded environment X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 09:52:32 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDB7F2FA47EAE64879C2B0653 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Xin LI wrote: > Xin LI wrote: >> Hi, Pawel, >=20 >> We can still reproduce the ZFS crash (threading+heavy I/O load) on a >> fresh 7.1-STABLE build, in a few minutes: >=20 >> /usr/local/bin/iozone -M -e -+u -T -t 128 -S 4096 -L 64 -r 4k -s 30g -= i >> 0 -i 1 -i 2 -i 8 -+p 70 -C Yes, this is known. >> I have included a backtrace output from my colleague who has his hands= >> on the test environment. Should there is more information necessary >> please let us know and we wish to provide help on this. >=20 > Further datapoint. The system used to run with untuned loader.conf, an= d > my colleague just reported that with the following loader.conf, the > problem can be triggered sooner: >=20 > vm.kmem_size_max=3D838860800 > vm.kmem_size_scale=3D"2" These two settings only serve to calculate vm.kmem_size, so you could simply skip them and adjust vm.kmem_size directly. > The system is running FreeBSD/amd64 7.1-PRERELEASE equipped with 8GB of= > RAM with GENERIC kernel. You can tune vm.kmem_size to near 2 GB on your machine and OS version. --------------enigDB7F2FA47EAE64879C2B0653 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJHUp3ldnAQVacBcgRAhF9AJ9+U+lkmjl6QWJqXzZdlKl43nV/XQCg0jaP X0ISocjzXH78b+q4fdgcGO0= =PdKe -----END PGP SIGNATURE----- --------------enigDB7F2FA47EAE64879C2B0653-- From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 11:03:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9F4E106568A for ; Fri, 14 Nov 2008 11:03:50 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id 727E38FC0C for ; Fri, 14 Nov 2008 11:03:50 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 18534 invoked by uid 399); 14 Nov 2008 11:03:48 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 14 Nov 2008 11:03:48 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <491D5B13.2080800@FreeBSD.org> Date: Fri, 14 Nov 2008 03:03:47 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.17 (X11/20081010) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <491B5BF3.1010309@FreeBSD.org> In-Reply-To: <491B5BF3.1010309@FreeBSD.org> X-Enigmail-Version: 0.95.7 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: RELENG_7 build failure in rescue/ (iconv?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 11:03:50 -0000 Ignore this, turned out that PEBCAK. Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 12:20:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C6C4106564A; Fri, 14 Nov 2008 12:20:02 +0000 (UTC) (envelope-from sclark46@earthlink.net) Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by mx1.freebsd.org (Postfix) with ESMTP id 378398FC13; Fri, 14 Nov 2008 12:20:02 +0000 (UTC) (envelope-from sclark46@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=IwbhOQ6H4EBtyGj5jBbKA4fUMaG4rq59hhK5YLhV6UQMcU4sBlIGQX1glIlGLTmQ; h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [208.118.36.229] (helo=joker.seclark.com) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1L0xeZ-0000AJ-52; Fri, 14 Nov 2008 07:19:59 -0500 Message-ID: <491D6CED.50006@earthlink.net> Date: Fri, 14 Nov 2008 07:19:57 -0500 From: Stephen Clark User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: sclark46@earthlink.net References: <491B2703.4080707@earthlink.net> <491B31F7.30200@elischer.org> <491B4345.80106@earthlink.net> <491B47D2.6010804@elischer.org> <491C2235.4090509@earthlink.net> <1226589468.1976.12.camel@wombat.2hip.net> <491C4EC2.2000802@earthlink.net> In-Reply-To: <491C4EC2.2000802@earthlink.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec79345431f6a6dfb6738d00235df17b1d8d350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 208.118.36.229 Cc: freebsd-net@freebsd.org, FreeBSD Stable , Julian Elischer , Robert Noland Subject: Re: FreeBSD 6.3 gre and traceroute X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sclark46@earthlink.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 12:20:02 -0000 Stephen Clark wrote: > Robert Noland wrote: >> On Thu, 2008-11-13 at 07:48 -0500, Stephen Clark wrote: >>> Julian Elischer wrote: >>>> Stephen Clark wrote: >>>>> Julian Elischer wrote: >>>>>> you will need to define the setup and question better. >>>> thanks.. cleaning it up a bit more... >>>> >>>> 10.0.129.1 FreeBSD workstation >>>> ^ >>>> | >>>> | ethernet >>>> | >>>> v >>>> 10.0.128.1 Freebsd FW "A" >>>> ^ >>>> | >>>> | gre / ipsec >>>> | >>>> v >>>> 192.168.3.1 FreeBSD FW "B" >>>> ^ >>>> | >>>> | ethernet >>>> | >>>> v >>>> 192.168.3.86 linux workstation >>>> >>>>> $ sudo traceroute 192.168.3.86 >>>>> traceroute to 192.168.3.86 (192.168.3.86), 64 hops max, 40 byte >>>>> packets >>>>> 1 HQFirewallRS.com (10.0.128.1) 0.575 ms 0.423 ms 0.173 ms >>>>> 2 * * * >>>>> 3 192.168.3.86 (192.168.3.86) 47.972 ms 45.174 ms 49.968 ms >>>>> >>>>> No response from the FreeBSD "B" box. >>>>> >>>>> When I do a tcpdump on "B" of the gre interface I see UDP packets >>>>> with a TTL of 1 but no ICMP response packets being sent back. >>>>> If I do the traceroute from the linux workstation 192.168.3.86 I get >>>>> similar results - I don't see a response from the FreeBSD "A" box. >>>> could you try using just GRE encasulation? >>>> (i.e. turn off IPSEC for now) >>>> >>>> I think that is much more likely to be where the problem is.. >>>> >>>> >>> I'll have to set this up to test it. >> >> The ttl exceeded is triggered from one of two places. Either >> netinet/ip_fastfwd.c if fast_forwarding is enabled or in >> netinet/ip_input.c. Look for the code relating to IPTTLDEC. This isn't >> your problem though... If ttl were not being decremented, the packet >> would just be forwarded on to the next hop (IP_STEALTH), which would >> just make the firewalls invisible. The fact that you are seeing * * * >> indicates that you are not receiving the ttl exceeded message for the >> packet sent with that particular ttl. I still think that the issue you >> are seeing is that one way or another the generated ICMP response isn't >> making it back onto the tunnel. Either via security policy, firewall or >> routing. > Your right, when I do a tcpdump on the gre interface I see the udp > packet come > in with a ttl=1 but I don't see a response icmp packet. I have tested > this with > all the firewalls disabled to make sure the icmp packet was not being > blocked. > I just ran another test and did tcpdump on all the other interfaces to > make sure > the icmp's were not being misrouted, it seems they are not being > generated for some reason. Also just using gre's without the underlying > ipsec tunnels seems to > work properly. >> >> robert. >> >>> What code in the FreeBSD kernel is responsible for generating the >>> response ICMP dest unreachable message? >>> > > Another data point I had been using option FILTER_GIF I tried a kernel without that option and it behaved the same. Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 14:31:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59F241065674 for ; Fri, 14 Nov 2008 14:31:29 +0000 (UTC) (envelope-from sclark46@earthlink.net) Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by mx1.freebsd.org (Postfix) with ESMTP id 093748FC14 for ; Fri, 14 Nov 2008 14:31:28 +0000 (UTC) (envelope-from sclark46@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=UusO8+kvIwyExiwxrPJleJ9WkBRcjuIBfHP1/andN/eX39Cg7fLeDRLNIC3mNAlq; h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [208.118.36.229] (helo=joker.seclark.com) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1L0zhn-0007wU-JY for freebsd-stable@freebsd.org; Fri, 14 Nov 2008 09:31:27 -0500 Message-ID: <491D8BBC.8090201@earthlink.net> Date: Fri, 14 Nov 2008 09:31:24 -0500 From: Stephen Clark User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: FreeBSD Stable References: <491B2703.4080707@earthlink.net> <491B31F7.30200@elischer.org> <491B4345.80106@earthlink.net> <491B47D2.6010804@elischer.org> <491C2235.4090509@earthlink.net> <1226589468.1976.12.camel@wombat.2hip.net> <491C4EC2.2000802@earthlink.net> <491D6CED.50006@earthlink.net> In-Reply-To: <491D6CED.50006@earthlink.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec79f220bc3b247bd65942449f87253af95d350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 208.118.36.229 Subject: FreeBSD 6.3 ipsec and traceroute doesn't work as good as Linux -why? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sclark46@earthlink.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 14:31:29 -0000 10.0.129.1 FreeBSD workstation ^ | | ethernet | v 10.0.128.1 Freebsd FW "A" ^ | | ipsec | v 192.168.2.1 Linux FW "B" ^ | | ethernet | v 192.168.2.20 linux workstation from 192.168.2.20 Linux<->ipsec<->FreeBSD traceroute -I 10.0.129.1 traceroute to 10.0.129.1 (10.0.129.1), 30 hops max, 60 byte packets 1 192.168.2.1 (192.168.2.1) 0.434 ms 0.425 ms 0.423 ms 2 * * * 3 sclark (10.0.129.1) 42.418 ms 42.419 ms 42.727 ms traceroute -I 10.0.128.1 traceroute to 10.0.128.1 (10.0.128.1), 30 hops max, 60 byte packets 1 192.168.2.1 (192.168.2.1) 0.398 ms 0.504 ms 0.505 ms 2 10.0.128.1 (10.0.128.1) 36.066 ms 36.052 ms 37.800 ms traceroute 10.0.129.1 traceroute to 10.0.129.1 (10.0.129.1), 30 hops max, 60 byte packets 1 192.168.2.1 (192.168.2.1) 0.484 ms 0.464 ms 0.447 ms 2 * * * 3 sclark (10.0.129.1) 41.406 ms 41.391 ms 47.812 ms traceroute 10.0.128.1 traceroute to 10.0.128.1 (10.0.128.1), 30 hops max, 60 byte packets 1 (192.168.2.1) 0.473 ms 0.444 ms 0.427 ms 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * *^C from 10.0.129.1 FreeBSD<->ipsec<->Linux sudo traceroute 192.168.2.20 traceroute to 192.168.2.20 (192.168.2.20), 64 hops max, 40 byte packets 1 HQFirewallRS.com (10.0.128.1) 0.761 ms 2.551 ms 4.017 ms 2 * * * 3 192.168.2.20 (192.168.2.20) 19.956 ms 27.425 ms 27.487 ms sclark:~ $ sudo traceroute 192.168.2.1 traceroute to 192.168.2.1 (192.168.2.1), 64 hops max, 40 byte packets 1 HQFirewallRS.com (10.0.128.1) 8.069 ms 2.952 ms 4.050 ms 2 home (192.168.2.1) 26.338 ms 22.132 ms 24.233 ms sclark:~ $ sudo traceroute -I 192.168.2.20 traceroute to 192.168.2.20 (192.168.2.20), 64 hops max, 60 byte packets 1 HQFirewallRS.com (10.0.128.1) 0.714 ms 0.806 ms 0.221 ms 2 home (192.168.2.1) 25.260 ms 25.312 ms 25.868 ms 3 192.168.2.20 (192.168.2.20) 36.477 ms 24.828 ms 24.903 ms sclark:~ $ sudo traceroute -I 192.168.2.1 traceroute to 192.168.2.1 (192.168.2.1), 64 hops max, 60 byte packets 1 HQFirewallRS.com (10.0.128.1) 2.219 ms 1.889 ms 4.491 ms 2 home (192.168.2.1) 26.172 ms 25.706 ms 24.981 ms tracerouteing to Linux never just gives a * * *, * * *, * * *, etc -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 15:14:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0D681065679 for ; Fri, 14 Nov 2008 15:14:49 +0000 (UTC) (envelope-from amon@aelita.org) Received: from aelita.org (unknown [IPv6:2001:7a8:7003::3]) by mx1.freebsd.org (Postfix) with ESMTP id 4C3688FC0A for ; Fri, 14 Nov 2008 15:14:49 +0000 (UTC) (envelope-from amon@aelita.org) Received: from ra.aabs (localhost [127.0.0.1]) by aelita.org (8.14.2/8.14.2) with ESMTP id mAEGDSr8052733; Fri, 14 Nov 2008 17:13:28 +0100 (CET) (envelope-from amon@ra.aabs) Received: (from amon@localhost) by ra.aabs (8.14.2/8.14.2/Submit) id mAEGDSFu052732; Fri, 14 Nov 2008 17:13:28 +0100 (CET) (envelope-from amon) Date: Fri, 14 Nov 2008 17:13:28 +0100 From: Herve Boulouis To: Herve Boulouis Message-ID: <20081114161328.GO596@ra.aabs> References: <20081106102931.GD596@ra.aabs> <20081106150548.GF596@ra.aabs> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081106150548.GF596@ra.aabs> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Multiple panics with 7.1-PRERELEASE amd64/i386 and varnish X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 15:14:50 -0000 Le 06/11/2008 16:05, Herve Boulouis a écrit: > Le 06/11/2008 11:29, Herve Boulouis a écrit: > > I just tried to reboot one of the boxes without kern.ipc.maxpipekva=104857600 to check for kva problems > but crashes persists, though the stack is completely different now. This time I included all the corrupt > parts of the stack that I had stripped in my original email but they are similar (from frame 18 to end). > > Any ideas ? We just found the same kind of crash with a 7.0-STABLE i386 from August so there is a serious bug in the kernel making varnish with file backend totaly unusable on FreeBSD 7. Backtrace : Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x52 fault code = supervisor read, page not present instruction pointer = 0x20:0xc093b90a stack pointer = 0x28:0xe4475ad0 frame pointer = 0x28:0xe4475ad0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 34 (syncer) trap number = 12 panic: page fault cpuid = 0 Uptime: 28m52s Physical memory: 1011 MB Dumping 148 MB: 133 117 101 85 69 53 37 21 5 Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc071b3a6 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc071b67e in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:572 #3 0xc09ec2dc in trap_fatal (frame=0xe4475a90, eva=82) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc09ec54b in trap_pfault (frame=0xe4475a90, usermode=0, eva=82) at /usr/src/sys/i386/i386/trap.c:812 #5 0xc09ecf32 in trap (frame=0xe4475a90) at /usr/src/sys/i386/i386/trap.c:490 #6 0xc09d31cb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc093b90a in vm_object_pip_add (object=0x0, i=1) at /usr/src/sys/vm/vm_object.c:273 #8 0xc078c207 in cluster_wbuild (vp=0xc4616564, size=16384, start_lbn=3, len=3) at /usr/src/sys/kern/vfs_cluster.c:925 #9 0xc07829a6 in vfs_bio_awrite (bp=0xd7fde3bc) at /usr/src/sys/kern/vfs_bio.c:1668 #10 0xc091593e in ffs_syncvnode (vp=0xc4616564, waitfor=3) at /usr/src/sys/ufs/ffs/ffs_vnops.c:283 #11 0xc0910e8d in ffs_sync (mp=0xc4209b30, waitfor=3, td=0xc4044660) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1234 #12 0xc079d4ef in sync_fsync (ap=0xe4475cd4) at /usr/src/sys/kern/vfs_subr.c:3217 #13 0xc0a01392 in VOP_FSYNC_APV (vop=0xc0affa60, a=0xe4475cd4) at vnode_if.c:1007 #14 0xc079dcd5 in sched_sync () at vnode_if.h:538 #15 0xc06f77f4 in fork_exit (callout=0xc079d5d0 , arg=0x0, frame=0xe4475d38) at /usr/src/sys/kern/kern_fork.c:781 #16 0xc09d3240 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:205 (kgdb) I kept the vmcores (i386 and amd64) if someone needs them. Regards, -- Herve Boulouis From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 16:49:44 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91B101065673 for ; Fri, 14 Nov 2008 16:49:44 +0000 (UTC) (envelope-from hk@alogis.com) Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by mx1.freebsd.org (Postfix) with ESMTP id D2CB08FC1C for ; Fri, 14 Nov 2008 16:49:43 +0000 (UTC) (envelope-from hk@alogis.com) Received: from alogis.com (localhost [127.0.0.1]) by alogis.com (8.13.4/8.13.1) with ESMTP id mAEGaJJx012065; Fri, 14 Nov 2008 17:36:19 +0100 (CET) (envelope-from hk@alogis.com) Received: (from hk@localhost) by alogis.com (8.13.4/8.13.1/Submit) id mAEGaIuD012064; Fri, 14 Nov 2008 17:36:18 +0100 (CET) (envelope-from hk) Date: Fri, 14 Nov 2008 17:36:18 +0100 From: Holger Kipp To: Stephen Clark Message-ID: <20081114163618.GA10409@intserv.int1.b.intern> References: <491B2703.4080707@earthlink.net> <491B31F7.30200@elischer.org> <491B4345.80106@earthlink.net> <491B47D2.6010804@elischer.org> <491C2235.4090509@earthlink.net> <1226589468.1976.12.camel@wombat.2hip.net> <491C4EC2.2000802@earthlink.net> <491D6CED.50006@earthlink.net> <491D8BBC.8090201@earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <491D8BBC.8090201@earthlink.net> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Stable Subject: Re: FreeBSD 6.3 ipsec and traceroute doesn't work as good as Linux -why? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 16:49:44 -0000 On Fri, Nov 14, 2008 at 09:31:24AM -0500, Stephen Clark wrote: Dear Stephen, I don't want to be rude, but looking at your description I don't see what's wrong with the behaviour, but it seems you don't understand what '* * *' really means. How does traceroute work? Well, it sends out a packet with time to live (TTL) set to one. on the first hop, this will be reduced by each hop that it passes through, and if TTL reaches zero, a time exceeded message will be send back. Then another packet is send with TTL increased by one to identify the next hop and so on. If no answer is received, print out a '*' and try again (up to three tries by default). This process will stop if the last hop replies. It does not stop (or only after eg. 30 hops) if the last hop does not reply. Why is it that we sometimes do not get a reply? Possible answers: - fw-rules block these traceroute packages - routing for the answer packet is not set correctly - with IP-tunnel, the packet is not routed through the tunnel because it does not enter the ruleset from an external interface. This might be true for your firewalls. - ... So routing and fw-settings are very important here. You might want to check that first, before complaining ;-) In your setup you have not given both external and internal FW addresses. You might not want to have the FW be exposed on its internal interface to the remote network, instead you might want to have a transparent tunnel. Regards, Holger > 10.0.129.1 FreeBSD workstation > ^ > | > | ethernet > | > v > 10.0.128.1 Freebsd FW "A" > ^ > | > | ipsec > | > v > 192.168.2.1 Linux FW "B" > ^ > | > | ethernet > | > v > 192.168.2.20 linux workstation > > from 192.168.2.20 Linux<->ipsec<->FreeBSD > > traceroute -I 10.0.129.1 > traceroute to 10.0.129.1 (10.0.129.1), 30 hops max, 60 byte packets > 1 192.168.2.1 (192.168.2.1) 0.434 ms 0.425 ms 0.423 ms > 2 * * * > 3 sclark (10.0.129.1) 42.418 ms 42.419 ms 42.727 ms > > traceroute -I 10.0.128.1 > traceroute to 10.0.128.1 (10.0.128.1), 30 hops max, 60 byte packets > 1 192.168.2.1 (192.168.2.1) 0.398 ms 0.504 ms 0.505 ms > 2 10.0.128.1 (10.0.128.1) 36.066 ms 36.052 ms 37.800 ms > > traceroute 10.0.129.1 > traceroute to 10.0.129.1 (10.0.129.1), 30 hops max, 60 byte packets > 1 192.168.2.1 (192.168.2.1) 0.484 ms 0.464 ms 0.447 ms > 2 * * * > 3 sclark (10.0.129.1) 41.406 ms 41.391 ms 47.812 ms > > traceroute 10.0.128.1 > traceroute to 10.0.128.1 (10.0.128.1), 30 hops max, 60 byte packets > 1 (192.168.2.1) 0.473 ms 0.444 ms 0.427 ms > 2 * * * > 3 * * * > 4 * * * > 5 * * * > 6 * * * > 7 * * * > 8 * * * > 9 * * * > 10 * * * > 11 * * * > 12 * *^C > > > > from 10.0.129.1 FreeBSD<->ipsec<->Linux > sudo traceroute 192.168.2.20 > traceroute to 192.168.2.20 (192.168.2.20), 64 hops max, 40 byte packets > 1 HQFirewallRS.com (10.0.128.1) 0.761 ms 2.551 ms 4.017 ms > 2 * * * > 3 192.168.2.20 (192.168.2.20) 19.956 ms 27.425 ms 27.487 ms > > sclark:~ > $ sudo traceroute 192.168.2.1 > traceroute to 192.168.2.1 (192.168.2.1), 64 hops max, 40 byte packets > 1 HQFirewallRS.com (10.0.128.1) 8.069 ms 2.952 ms 4.050 ms > 2 home (192.168.2.1) 26.338 ms 22.132 ms 24.233 ms > > sclark:~ > $ sudo traceroute -I 192.168.2.20 > traceroute to 192.168.2.20 (192.168.2.20), 64 hops max, 60 byte packets > 1 HQFirewallRS.com (10.0.128.1) 0.714 ms 0.806 ms 0.221 ms > 2 home (192.168.2.1) 25.260 ms 25.312 ms 25.868 ms > 3 192.168.2.20 (192.168.2.20) 36.477 ms 24.828 ms 24.903 ms > > sclark:~ > $ sudo traceroute -I 192.168.2.1 > traceroute to 192.168.2.1 (192.168.2.1), 64 hops max, 60 byte packets > 1 HQFirewallRS.com (10.0.128.1) 2.219 ms 1.889 ms 4.491 ms > 2 home (192.168.2.1) 26.172 ms 25.706 ms 24.981 ms > > tracerouteing to Linux never just gives a * * *, * * *, * * *, etc > > -- > > "They that give up essential liberty to obtain temporary safety, > deserve neither liberty nor safety." (Ben Franklin) > > "The course of history shows that as a government grows, liberty > decreases." (Thomas Jefferson) > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 18:30:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAD901065675 for ; Fri, 14 Nov 2008 18:30:12 +0000 (UTC) (envelope-from sclark46@earthlink.net) Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by mx1.freebsd.org (Postfix) with ESMTP id 84D698FC08 for ; Fri, 14 Nov 2008 18:30:12 +0000 (UTC) (envelope-from sclark46@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=dVZhWjQsnEa/BE/KbrmDPpuPkfFKBu4ibmcY6R5ZevWXRFXyDUmuuWLbqKEiWBc9; h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [208.118.36.229] (helo=joker.seclark.com) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1L13Qp-0002OE-0W; Fri, 14 Nov 2008 13:30:11 -0500 Message-ID: <491DC3B1.10308@earthlink.net> Date: Fri, 14 Nov 2008 13:30:09 -0500 From: Stephen Clark User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: Holger Kipp References: <491B2703.4080707@earthlink.net> <491B31F7.30200@elischer.org> <491B4345.80106@earthlink.net> <491B47D2.6010804@elischer.org> <491C2235.4090509@earthlink.net> <1226589468.1976.12.camel@wombat.2hip.net> <491C4EC2.2000802@earthlink.net> <491D6CED.50006@earthlink.net> <491D8BBC.8090201@earthlink.net> <20081114163618.GA10409@intserv.int1.b.intern> In-Reply-To: <20081114163618.GA10409@intserv.int1.b.intern> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec79bddbf654595049e27d2d75ce65088192350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 208.118.36.229 Cc: FreeBSD Stable Subject: Re: FreeBSD 6.3 ipsec and traceroute doesn't work as good as Linux -why? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sclark46@earthlink.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 18:30:12 -0000 Holger Kipp wrote: > On Fri, Nov 14, 2008 at 09:31:24AM -0500, Stephen Clark wrote: > > Dear Stephen, > > I don't want to be rude, but looking at your description I don't see > what's wrong with the behaviour, but it seems you don't understand what > '* * *' really means. > > How does traceroute work? Well, it sends out a packet with time to live > (TTL) set to one. on the first hop, this will be reduced by each hop that > it passes through, and if TTL reaches zero, a time exceeded message will > be send back. Then another packet is send with TTL increased by one to > identify the next hop and so on. > > If no answer is received, print out a '*' and try again (up to three tries > by default). > > This process will stop if the last hop replies. It does not stop (or only > after eg. 30 hops) if the last hop does not reply. > > Why is it that we sometimes do not get a reply? Possible answers: > - fw-rules block these traceroute packages > - routing for the answer packet is not set correctly > - with IP-tunnel, the packet is not routed through the tunnel because > it does not enter the ruleset from an external interface. This might > be true for your firewalls. > - ... > > So routing and fw-settings are very important here. You might want to > check that first, before complaining ;-) > > In your setup you have not given both external and internal FW addresses. > You might not want to have the FW be exposed on its internal interface > to the remote network, instead you might want to have a transparent tunnel. > > Regards, > Holger > > >> 10.0.129.1 FreeBSD workstation >> ^ >> | >> | ethernet >> | >> v >> internal 10.0.128.1 Freebsd FW "A" public ip address >> ^ >> | >> | ipsec >> | >> v public ip address internal 192.168.2.1 Linux FW "B" >> ^ >> | >> | ethernet >> | >> v >> 192.168.2.20 linux workstation >> >> from 192.168.2.20 Linux<->ipsec<->FreeBSD >> >> traceroute -I 10.0.129.1 >> traceroute to 10.0.129.1 (10.0.129.1), 30 hops max, 60 byte packets >> 1 192.168.2.1 (192.168.2.1) 0.434 ms 0.425 ms 0.423 ms >> 2 * * * >> 3 sclark (10.0.129.1) 42.418 ms 42.419 ms 42.727 ms >> >> traceroute -I 10.0.128.1 >> traceroute to 10.0.128.1 (10.0.128.1), 30 hops max, 60 byte packets >> 1 192.168.2.1 (192.168.2.1) 0.398 ms 0.504 ms 0.505 ms >> 2 10.0.128.1 (10.0.128.1) 36.066 ms 36.052 ms 37.800 ms >> >> traceroute 10.0.129.1 >> traceroute to 10.0.129.1 (10.0.129.1), 30 hops max, 60 byte packets >> 1 192.168.2.1 (192.168.2.1) 0.484 ms 0.464 ms 0.447 ms >> 2 * * * >> 3 sclark (10.0.129.1) 41.406 ms 41.391 ms 47.812 ms >> >> traceroute 10.0.128.1 >> traceroute to 10.0.128.1 (10.0.128.1), 30 hops max, 60 byte packets >> 1 (192.168.2.1) 0.473 ms 0.444 ms 0.427 ms >> 2 * * * >> 3 * * * >> 4 * * * >> 5 * * * >> 6 * * * >> 7 * * * >> 8 * * * >> 9 * * * >> 10 * * * >> 11 * * * >> 12 * *^C >> >> >> >> from 10.0.129.1 FreeBSD<->ipsec<->Linux >> sudo traceroute 192.168.2.20 >> traceroute to 192.168.2.20 (192.168.2.20), 64 hops max, 40 byte packets >> 1 HQFirewallRS.com (10.0.128.1) 0.761 ms 2.551 ms 4.017 ms >> 2 * * * >> 3 192.168.2.20 (192.168.2.20) 19.956 ms 27.425 ms 27.487 ms >> >> sclark:~ >> $ sudo traceroute 192.168.2.1 >> traceroute to 192.168.2.1 (192.168.2.1), 64 hops max, 40 byte packets >> 1 HQFirewallRS.com (10.0.128.1) 8.069 ms 2.952 ms 4.050 ms >> 2 home (192.168.2.1) 26.338 ms 22.132 ms 24.233 ms >> >> sclark:~ >> $ sudo traceroute -I 192.168.2.20 >> traceroute to 192.168.2.20 (192.168.2.20), 64 hops max, 60 byte packets >> 1 HQFirewallRS.com (10.0.128.1) 0.714 ms 0.806 ms 0.221 ms >> 2 home (192.168.2.1) 25.260 ms 25.312 ms 25.868 ms >> 3 192.168.2.20 (192.168.2.20) 36.477 ms 24.828 ms 24.903 ms >> >> sclark:~ >> $ sudo traceroute -I 192.168.2.1 >> traceroute to 192.168.2.1 (192.168.2.1), 64 hops max, 60 byte packets >> 1 HQFirewallRS.com (10.0.128.1) 2.219 ms 1.889 ms 4.491 ms >> 2 home (192.168.2.1) 26.172 ms 25.706 ms 24.981 ms >> >> tracerouteing to Linux never just gives a * * *, * * *, * * *, etc >> >> -- >> >> "They that give up essential liberty to obtain temporary safety, >> deserve neither liberty nor safety." (Ben Franklin) >> >> "The course of history shows that as a government grows, liberty >> decreases." (Thomas Jefferson) >> >> >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Hi Holger, Thanks for the reply. During my test I had the firewalls on all system disabled, The problem is the FreeBSD FW does not respond correctly even if I use the -I option on traceroute which uses ICMP packets instead of UDP packets. And I agree it looks to be some kind of routing problem - I put a diag in the freebsd kernel ip_input.c if (ip->ip_ttl <= IPTTLDEC) { icmp_error(m, ICMP_TIMXCEED, ICMP_TIMXCEED_INTRANS, 0, 0); return; to make sure it was calling icmp_error - it was. I have complementary setups on both the FreeBSD and Linux sides. It just seems that Linux handles things better than FreeBSD. EG when tracerouting from Linux to internal address on FreeBSD FW: >> traceroute 10.0.128.1 >> traceroute to 10.0.128.1 (10.0.128.1), 30 hops max, 60 byte packets >> 1 (192.168.2.1) 0.473 ms 0.444 ms 0.427 ms >> 2 * * * >> 3 * * * >> 4 * * * >> 5 * * * >> 6 * * * >> 7 * * * >> 8 * * * >> 9 * * * >> 10 * * * >> 11 * * * >> 12 * *^C But when tracerouting from FreeBSD to internal address on Linux FW. sudo traceroute 192.168.2.1 >> traceroute to 192.168.2.1 (192.168.2.1), 64 hops max, 40 byte packets >> 1 HQFirewallRS.com (10.0.128.1) 8.069 ms 2.952 ms 4.050 ms >> 2 home (192.168.2.1) 26.338 ms 22.132 ms 24.233 ms Much more meaningful results! From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 18:37:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F4A31065673; Fri, 14 Nov 2008 18:37:03 +0000 (UTC) (envelope-from sclark46@earthlink.net) Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by mx1.freebsd.org (Postfix) with ESMTP id F0ACA8FC16; Fri, 14 Nov 2008 18:37:02 +0000 (UTC) (envelope-from sclark46@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=f1MKOuXTBLm+ZKI7xMLkhZ10seC+RYKdxOVJkCpaYoxJLOW3Ai8tP69kgyKR8U5R; h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [208.118.36.229] (helo=joker.seclark.com) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1L13XP-0006Rw-OF; Fri, 14 Nov 2008 13:36:59 -0500 Message-ID: <491DC54A.1090907@earthlink.net> Date: Fri, 14 Nov 2008 13:36:58 -0500 From: Stephen Clark User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: Julian Elischer References: <491B2703.4080707@earthlink.net> <491B31F7.30200@elischer.org> <491B4345.80106@earthlink.net> <491B47D2.6010804@elischer.org> <491C2235.4090509@earthlink.net> <1226589468.1976.12.camel@wombat.2hip.net> <491C4EC2.2000802@earthlink.net> <491D6CED.50006@earthlink.net> <491DC28E.80804@elischer.org> In-Reply-To: <491DC28E.80804@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec7902bd0cf6eff9e584ec18d5e033017cb2350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 208.118.36.229 Cc: freebsd-net@freebsd.org, FreeBSD Stable , Robert Noland Subject: Re: FreeBSD 6.3 gre and traceroute X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sclark46@earthlink.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 18:37:03 -0000 Julian Elischer wrote: > Stephen Clark wrote: >> Stephen Clark wrote: > >>>>>> >>>>>> 10.0.129.1 FreeBSD workstation >>>>>> ^ >>>>>> | >>>>>> | ethernet >>>>>> | >>>>>> v >>>>>> 10.0.128.1 Freebsd FW "A" >>>>>> ^ >>>>>> | >>>>>> | gre / ipsec >>>>>> | >>>>>> v >>>>>> 192.168.3.1 FreeBSD FW "B" >>>>>> ^ >>>>>> | >>>>>> | ethernet >>>>>> | >>>>>> v >>>>>> 192.168.3.86 linux workstation >>>>>> > >>> Also just using gre's without the underlying ipsec tunnels seems to >>> work properly. > > > This is the crux of the matter. > IPSEC happens INSIDE the IP stack. The IP stack is responsible for > the ICMP generation so it is much more likely that there is an > interaction there. > > Now is there an IPSEC rule to make sure that the ICMP packet can get > back? It could b ehtat in teh IP stack there is some confusion as to > whether the return packet should be encrypted or not and it might get > dropped. > > the code involved is in /sys/netinet and /sys/netipsec but you'll > probably regret looking in there ;-) > > > >>> >>> >> Another data point I had been using option FILTER_GIF I tried a kernel >> without that option and it behaved the same. >> >> Steve >> > I agree I put a diag in ip_input.c if (ip->ip_ttl <= IPTTLDEC) { icmp_error(m, ICMP_TIMXCEED, ICMP_TIMXCEED_INTRANS, 0, 0); return; and sure enough it is calling icmp_error, but I think it can't figure out how to route the packet back. I been looking at my SPD to see if I can make some adjustment to the policy that would help. -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 18:37:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99E601065782; Fri, 14 Nov 2008 18:37:36 +0000 (UTC) (envelope-from prvs=julian=1973cfe30@elischer.org) Received: from smtp-outbound.ironport.com (smtp-outbound.ironport.com [63.251.108.112]) by mx1.freebsd.org (Postfix) with ESMTP id 84B1A8FC0C; Fri, 14 Nov 2008 18:37:36 +0000 (UTC) (envelope-from prvs=julian=1973cfe30@elischer.org) Received: from jelischer-laptop.sfo.ironport.com (HELO julian-mac.elischer.org) ([10.251.22.38]) by smtp-outbound.ironport.com with ESMTP; 14 Nov 2008 10:25:18 -0800 Message-ID: <491DC28E.80804@elischer.org> Date: Fri, 14 Nov 2008 10:25:18 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914) MIME-Version: 1.0 To: sclark46@earthlink.net References: <491B2703.4080707@earthlink.net> <491B31F7.30200@elischer.org> <491B4345.80106@earthlink.net> <491B47D2.6010804@elischer.org> <491C2235.4090509@earthlink.net> <1226589468.1976.12.camel@wombat.2hip.net> <491C4EC2.2000802@earthlink.net> <491D6CED.50006@earthlink.net> In-Reply-To: <491D6CED.50006@earthlink.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, FreeBSD Stable , Robert Noland Subject: Re: FreeBSD 6.3 gre and traceroute X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 18:37:36 -0000 Stephen Clark wrote: > Stephen Clark wrote: >>>>> >>>>> 10.0.129.1 FreeBSD workstation >>>>> ^ >>>>> | >>>>> | ethernet >>>>> | >>>>> v >>>>> 10.0.128.1 Freebsd FW "A" >>>>> ^ >>>>> | >>>>> | gre / ipsec >>>>> | >>>>> v >>>>> 192.168.3.1 FreeBSD FW "B" >>>>> ^ >>>>> | >>>>> | ethernet >>>>> | >>>>> v >>>>> 192.168.3.86 linux workstation >>>>> >> Also just using gre's without the >> underlying ipsec tunnels seems to >> work properly. This is the crux of the matter. IPSEC happens INSIDE the IP stack. The IP stack is responsible for the ICMP generation so it is much more likely that there is an interaction there. Now is there an IPSEC rule to make sure that the ICMP packet can get back? It could b ehtat in teh IP stack there is some confusion as to whether the return packet should be encrypted or not and it might get dropped. the code involved is in /sys/netinet and /sys/netipsec but you'll probably regret looking in there ;-) >> >> > Another data point I had been using option FILTER_GIF I tried a kernel > without that option and it behaved the same. > > Steve > From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 18:57:28 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36F5D106564A for ; Fri, 14 Nov 2008 18:57:28 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 05D2F8FC08 for ; Fri, 14 Nov 2008 18:57:27 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from [192.168.166.46] ([68.0.14.34]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id mAEIgcLL000454 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Nov 2008 13:42:38 -0500 (EST) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Julian Elischer In-Reply-To: <491DC28E.80804@elischer.org> References: <491B2703.4080707@earthlink.net> <491B31F7.30200@elischer.org> <491B4345.80106@earthlink.net> <491B47D2.6010804@elischer.org> <491C2235.4090509@earthlink.net> <1226589468.1976.12.camel@wombat.2hip.net> <491C4EC2.2000802@earthlink.net> <491D6CED.50006@earthlink.net> <491DC28E.80804@elischer.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-tc069wmrKhgBioXbSO26" Organization: FreeBSD Date: Fri, 14 Nov 2008 13:42:33 -0500 Message-Id: <1226688153.1719.23.camel@squirrel.corp.cox.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00, RCVD_IN_SORBS_DUL,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: sclark46@earthlink.net, FreeBSD Stable , freebsd-net@freebsd.org Subject: Re: FreeBSD 6.3 gre and traceroute X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 18:57:28 -0000 --=-tc069wmrKhgBioXbSO26 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2008-11-14 at 10:25 -0800, Julian Elischer wrote: > Stephen Clark wrote: > > Stephen Clark wrote: >=20 > >>>>> > >>>>> 10.0.129.1 FreeBSD workstation > >>>>> ^ > >>>>> | > >>>>> | ethernet > >>>>> | > >>>>> v > >>>>> 10.0.128.1 Freebsd FW "A" > >>>>> ^ > >>>>> | > >>>>> | gre / ipsec > >>>>> | > >>>>> v > >>>>> 192.168.3.1 FreeBSD FW "B" > >>>>> ^ > >>>>> | > >>>>> | ethernet > >>>>> | > >>>>> v > >>>>> 192.168.3.86 linux workstation > >>>>> >=20 > >> Also just using gre's without the=20 > >> underlying ipsec tunnels seems to > >> work properly. >=20 >=20 > This is the crux of the matter. > IPSEC happens INSIDE the IP stack. The IP stack is responsible for > the ICMP generation so it is much more likely that there is an=20 > interaction there. >=20 > Now is there an IPSEC rule to make sure that the ICMP packet can get=20 > back? It could b ehtat in teh IP stack there is some confusion as to=20 > whether the return packet should be encrypted or not and it might get=20 > dropped. >=20 > the code involved is in /sys/netinet and /sys/netipsec but you'll > probably regret looking in there ;-) Right, I don't really know the IPSEC code, but I was told by someone who is familiar with it that this is a known problem and that the use of GRE is not relevant. Hopefully he will have a moment to respond to this thread with a bit more detail. robert. >=20 >=20 > >> > >> > > Another data point I had been using option FILTER_GIF I tried a kernel > > without that option and it behaved the same. > >=20 > > Steve > >=20 >=20 --=-tc069wmrKhgBioXbSO26 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEABECAAYFAkkdxpkACgkQM4TrQ4qfROOSoACaAokr54u0DNH/moMLIh/OcHnu AD4An37Pckf5o83ALDHlDC+BSC7/BpaW =KaC6 -----END PGP SIGNATURE----- --=-tc069wmrKhgBioXbSO26-- From owner-freebsd-stable@FreeBSD.ORG Fri Nov 14 19:41:13 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B2C91065672 for ; Fri, 14 Nov 2008 19:41:13 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 2BE638FC21 for ; Fri, 14 Nov 2008 19:41:13 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 346A173098; Fri, 14 Nov 2008 20:45:34 +0100 (CET) Date: Fri, 14 Nov 2008 20:45:34 +0100 From: Luigi Rizzo To: stable@freebsd.org Message-ID: <20081114194534.GA64986@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: diskless+pxe notes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2008 19:41:13 -0000 Hi, i finally decided to try and use pxeboot to replace the etherboot method I was using so far for diskless setups. The goal is to fully share the server's root and /usr directories, as documented in diskless(8). I'd like to share the following notes, hopefully to go in the manpage. cheers luigi -------------- root path configuration ----------------- There seems to be a well known problem in pxeloader, see kern/106493 , where pxeloader defaults to using a root path of /pxeroot when offered "/" . The patch suggested in http://www.freebsd.org/cgi/query-pr.cgi?pr=106493 is trivial and judging from it I believe this is addressing a true bug and not a feature. Fortunately there is a workaround (suggested in the PR) which is using "//" as a root path. ------------- sharing /boot with the server --------------- I believe it is quite useful to share the whole root partition between the server and the diskless client. This would require at a minimum some conditional code in loader.conf (or loader.rc, etc) so that at least you point to different kernels. A minimalistic approach can be adding this line to /boot/loader.conf bootfile="kernel\\${loaddev};kernel" The variable $loaddev contains the name of the load device, which is "pxe0" in the case of pxeboot, and disk* in other cases when loading from the local disk. If you make sure that there is no 'kernel.disk*' on the directory, and instead there is a kernel.pxe0 in the same directory, then the diskless machines and the server will boot from the proper file. Unfortunately i don't know how to implement a conditional in /boot/loader.conf -- otherwise one could do much nicer things such as differentiate which modules to load and so on. --------------- pxeloader bug in 7.x --------------------------- Also worth mentioning is an annoying bug in pxeloader as compiled on 7.x, see http://www.freebsd.org/cgi/query-pr.cgi?pr=118222 i.e. the pxeloader in 7.x fails to proceed and prints a message "can't figure out which disk we are booting from". The workaround is using a pxeloader from FreeBSD6 works. I guess this is a compiler-related problem (given that 6.x uses gcc 3.4 as a compiler, while 7.x uses gcc 4.2). ----------------------------------------------------------------- From owner-freebsd-stable@FreeBSD.ORG Sat Nov 15 10:40:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED6A41065674; Sat, 15 Nov 2008 10:40:17 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id A0FE08FC14; Sat, 15 Nov 2008 10:40:17 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 4065741C438; Sat, 15 Nov 2008 11:40:15 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id sBBYSULNQQaa; Sat, 15 Nov 2008 11:40:12 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id 5857241C62D; Sat, 15 Nov 2008 11:40:12 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id ECF61444888; Sat, 15 Nov 2008 10:38:34 +0000 (UTC) Date: Sat, 15 Nov 2008 10:38:34 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: sclark46@earthlink.net In-Reply-To: <1226688153.1719.23.camel@squirrel.corp.cox.com> Message-ID: <20081115102746.K61259@maildrop.int.zabbadoz.net> References: <491B2703.4080707@earthlink.net> <491B31F7.30200@elischer.org> <491B4345.80106@earthlink.net> <491B47D2.6010804@elischer.org> <491C2235.4090509@earthlink.net> <1226589468.1976.12.camel@wombat.2hip.net> <491C4EC2.2000802@earthlink.net> <491D6CED.50006@earthlink.net> <491DC28E.80804@elischer.org> <1226688153.1719.23.camel@squirrel.corp.cox.com> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, FreeBSD Stable Subject: Re: FreeBSD 6.3 gre and traceroute X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2008 10:40:18 -0000 On Fri, 14 Nov 2008, Robert Noland wrote: Hi, >>>> Also just using gre's without the >>>> underlying ipsec tunnels seems to >>>> work properly. The reason for this to my knowledge is: http://www.kame.net/dev/cvsweb2.cgi/kame/freebsd2/sys/netinet/ip_icmp.c#rev1.4 or looking at recent freebsd code: http://fxr.watson.org/fxr/source/netinet/ip_icmp.c#L164 Look for M_DECRYPTED. Now what happens in your case: you receive an IPSec ESP packet, which gets decryped, that sets M_DECRYPTED on the mbuf passes through various parts, gets up to gre, gets decapsulated is an IP packet (again) gets to ip_input, TTL expired, icmp_error and it's still the same mbuf that originally got the M_DECRYPTED set. Thus the packets is just freed and you never see anything. So thinking about this has nothing to do with gre (or gif for example as well) in first place. It's arguably that passing it on to another decapsulation the flag should be cleared when entering gre() for example. The other question of course is why we do not send the icmp error back even on plain ipsec? Is it because we could possibly leak information as it's not caught by the policy sending it back? /bz -- Bjoern A. Zeeb Stop bit received. Insert coin for new game. From owner-freebsd-stable@FreeBSD.ORG Sat Nov 15 11:03:35 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B9781065672 for ; Sat, 15 Nov 2008 11:03:35 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id D16908FC1D for ; Sat, 15 Nov 2008 11:03:34 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1L1IHT-000PML-KG; Sat, 15 Nov 2008 12:21:31 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Luigi Rizzo In-reply-to: <20081114194534.GA64986@onelab2.iet.unipi.it> References: <20081114194534.GA64986@onelab2.iet.unipi.it> Comments: In-reply-to Luigi Rizzo message dated "Fri, 14 Nov 2008 20:45:34 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 Nov 2008 12:21:31 +0200 From: Danny Braniss Message-ID: Cc: stable@freebsd.org Subject: Re: diskless+pxe notes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2008 11:03:35 -0000 > Hi, > i finally decided to try and use pxeboot to replace the etherboot > method I was using so far for diskless setups. > > The goal is to fully share the server's root and /usr directories, > as documented in diskless(8). I'd like to share the following > notes, hopefully to go in the manpage. > > cheers > luigi > Hi, With a slightly modified libstand/bootp.c - a PR was sent way back, but you can check ftp://ftp.cs.huji.ac.il/users/danny/freebsd/diskless-boot you can control the diskless boot options. by comenting out kernel= in /boot/defaults/loader.conf you can set in the dhcpd.conf. since most of the tags received via dhcp are placed in kenv, the crucial options are there! BTW, we use diskless servers/workstations for 90% of our hosts, the exception being: - the dhcp/tftp server - a 'lagged' server - the router/server get confused :-) - our mail servers, there is a bug somewhere, where some critical network resources get deadlocked. - our developement servers. the / of the diskless is almost identical to the server, but for many reasons, I like to keep it appart. The trick to overcome the read-only problem, is using unionfs for /etc: in rc.initdiskless: if [ -e /conf/union ]; then kldload unionfs mount_md 4096 /.etc mount_unionfs -o transparent /.etc /etc fi the /conf is nfs mounted from a central site, the location is passed via dhcp: confpath=`kenv conf-path` if [ -n "$confpath" ] ; then if [ "`expr $confpath : '\(.*\):'`" ] ; then echo Mounting $confpath on /conf mount_nfs $confpath /conf chkerr $? "mount_nfs $confpath /conf" to_umount="${to_umount} $confpath" fi fi the actual rc.conf is configured like this: eval `kenv | sed -n 's/^rc\.//p'` rm -f /etc/rc.conf /etc/rc.conf.local for fc in $conf0 $conf1 $conf2 $conf3 $conf4 $conf5 $conf6 $conf7 $conf8 $conf9 rc.conf.$hostname do ho=`expr $fc : '\(.*\):'` fl=`expr $fc : '.*/\(.*\)'` if [ "${ho}" != "" ]; then mp=`expr $fc : '\(.*\)/.*'` mount_nfs $mp /mnt > /dev/null 2>&1 if [ -f /mnt/$fl ]; then echo "# from $fc /mnt/$fl" >> /etc/rc.conf cat /mnt/$fl >> /etc/rc.conf fi umount /mnt > /dev/null 2>&1 elif [ -e /conf/$fc ] ; then echo "# from /conf/$fc" >> /etc/rc.conf cat /conf/$fc >> /etc/rc.conf fi done > -------------- root path configuration ----------------- > > There seems to be a well known problem in pxeloader, see > kern/106493 , where pxeloader defaults to using a root path of > /pxeroot when offered "/" . The patch suggested in > > http://www.freebsd.org/cgi/query-pr.cgi?pr=106493 > > is trivial and judging from it I believe this is addressing a > true bug and not a feature. Fortunately there is a workaround > (suggested in the PR) which is using "//" as a root path. > > ------------- sharing /boot with the server --------------- > > I believe it is quite useful to share the whole root > partition between the server and the diskless client. > This would require at a minimum some conditional code > in loader.conf (or loader.rc, etc) so that at least you > point to different kernels. > > A minimalistic approach can be adding this line to /boot/loader.conf > > bootfile="kernel\\${loaddev};kernel" > > The variable $loaddev contains the name of the load device, > which is "pxe0" in the case of pxeboot, and disk* in other > cases when loading from the local disk. > If you make sure that there is no 'kernel.disk*' on the > directory, and instead there is a kernel.pxe0 in the same > directory, then the diskless machines and the server will boot > from the proper file. > > Unfortunately i don't know how to implement a conditional > in /boot/loader.conf -- otherwise one could do much nicer things > such as differentiate which modules to load and so on. > > --------------- pxeloader bug in 7.x --------------------------- > Also worth mentioning is an annoying bug in pxeloader as compiled > on 7.x, see http://www.freebsd.org/cgi/query-pr.cgi?pr=118222 > i.e. the pxeloader in 7.x fails to proceed and prints a message > "can't figure out which disk we are booting from". > > The workaround is using a pxeloader from FreeBSD6 works. > I guess this is a compiler-related problem (given that 6.x uses gcc 3.4 > as a compiler, while 7.x uses gcc 4.2). > > ----------------------------------------------------------------- > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Sat Nov 15 11:40:21 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBF221065697 for ; Sat, 15 Nov 2008 11:40:21 +0000 (UTC) (envelope-from freebsd@the-irc.org) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.234]) by mx1.freebsd.org (Postfix) with ESMTP id AFDF78FC12 for ; Sat, 15 Nov 2008 11:40:21 +0000 (UTC) (envelope-from freebsd@the-irc.org) Received: by qb-out-0506.google.com with SMTP id e12so1413044qbe.1 for ; Sat, 15 Nov 2008 03:40:21 -0800 (PST) Received: by 10.210.51.10 with SMTP id y10mr2047438eby.87.1226748417698; Sat, 15 Nov 2008 03:26:57 -0800 (PST) Received: by 10.210.130.9 with HTTP; Sat, 15 Nov 2008 03:26:57 -0800 (PST) Message-ID: <322efb7b0811150326t7de120dfw874c4a5eec3b9c2d@mail.gmail.com> Date: Sat, 15 Nov 2008 05:26:57 -0600 From: "The-IRC FreeBSD" To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: TCP Stack Issues Under FreeBSD 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2008 11:40:22 -0000 Hi, Anyone else noticing any TCP Stack requests for information under a useraccount with mild to moderate TCP activity on HTTP and other sorts of ports returns zero results back unless you are root. [site@Eden ~]$ netstat -i reports netstat: kvm not available: /dev/mem: Permission denied ifnet: symbol not defined [site@Eden ~]$ netstat -an [site@Eden ~]$ netstat -m 377/823/1200 mbufs in use (current/cache/total) 64/378/442/32768 mbuf clusters in use (current/cache/total/max) 64/315 mbuf+clusters out of packet secondary zone in use (current/cache) 2/386/388/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) 230K/2505K/2736K 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/525/6656 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 57093 requests for I/O initiated by sendfile 0 calls to protocol drain routines FreeBSD Eden.The-IRC.Com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #4: Sun Nov 2 22:20:01 CST 2008 root@Eden.The-IRC.Com:/usr/obj/usr/src/sys/THE-IRC i386 From owner-freebsd-stable@FreeBSD.ORG Sat Nov 15 12:27:58 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87AA51065675 for ; Sat, 15 Nov 2008 12:27:58 +0000 (UTC) (envelope-from freebsd@the-irc.org) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.228]) by mx1.freebsd.org (Postfix) with ESMTP id 445BA8FC08 for ; Sat, 15 Nov 2008 12:27:57 +0000 (UTC) (envelope-from freebsd@the-irc.org) Received: by qb-out-0506.google.com with SMTP id f30so1658367qba.35 for ; Sat, 15 Nov 2008 04:27:57 -0800 (PST) Received: by 10.210.143.11 with SMTP id q11mr2082577ebd.146.1226752075143; Sat, 15 Nov 2008 04:27:55 -0800 (PST) Received: by 10.210.130.9 with HTTP; Sat, 15 Nov 2008 04:27:55 -0800 (PST) Message-ID: <322efb7b0811150427q60a128cbg66a9e312e7bd4b0f@mail.gmail.com> Date: Sat, 15 Nov 2008 06:27:55 -0600 From: "The-IRC FreeBSD" To: stable@freebsd.org In-Reply-To: <322efb7b0811150326t7de120dfw874c4a5eec3b9c2d@mail.gmail.com> MIME-Version: 1.0 References: <322efb7b0811150326t7de120dfw874c4a5eec3b9c2d@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: TCP Stack Issues Under FreeBSD 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2008 12:27:58 -0000 never mind, the TCP Stack is working perfectly under 7.1 unlike 7.0 with ghost entries from different users. It didn't show because root was behiend http. My mistake folks, keep up the good work ;) On Sat, Nov 15, 2008 at 5:26 AM, The-IRC FreeBSD wrote: > Hi, > > > Anyone else noticing any TCP Stack requests for information under a > useraccount with mild to moderate TCP activity on HTTP and other sorts of > ports returns zero results back unless you are root. > > [site@Eden ~]$ netstat -i reports > netstat: kvm not available: /dev/mem: Permission denied > ifnet: symbol not defined > [site@Eden ~]$ netstat -an > [site@Eden ~]$ netstat -m > 377/823/1200 mbufs in use (current/cache/total) > 64/378/442/32768 mbuf clusters in use (current/cache/total/max) > 64/315 mbuf+clusters out of packet secondary zone in use (current/cache) > 2/386/388/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) > 230K/2505K/2736K 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/525/6656 sfbufs in use (current/peak/max) > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 57093 requests for I/O initiated by sendfile > 0 calls to protocol drain routines > > > > FreeBSD Eden.The-IRC.Com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #4: Sun > Nov 2 22:20:01 CST 2008 root@Eden.The-IRC.Com:/usr/obj/usr/src/sys/THE-IRC > i386 > From owner-freebsd-stable@FreeBSD.ORG Sat Nov 15 18:22:11 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7B1E106564A for ; Sat, 15 Nov 2008 18:22:11 +0000 (UTC) (envelope-from jwb@hera.homer.att.com) Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.241.147]) by mx1.freebsd.org (Postfix) with ESMTP id 317F88FC08 for ; Sat, 15 Nov 2008 18:22:11 +0000 (UTC) (envelope-from jwb@hera.homer.att.com) X-VirusChecked: Checked X-Env-Sender: jwb@hera.homer.att.com X-Msg-Ref: server-5.tower-146.messagelabs.com!1226771728!8955451!1 X-StarScan-Version: 5.5.12.14.2; banners=-,-,- X-Originating-IP: [144.160.128.141] Received: (qmail 11677 invoked from network); 15 Nov 2008 17:55:29 -0000 Received: from sbcsmtp9.sbc.com (HELO flph161.enaf.ffdc.sbc.com) (144.160.128.141) by server-5.tower-146.messagelabs.com with AES256-SHA encrypted SMTP; 15 Nov 2008 17:55:28 -0000 Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flph161.enaf.ffdc.sbc.com (8.14.3/8.14.3) with ESMTP id mAFHtR5n029758 for ; Sat, 15 Nov 2008 09:55:27 -0800 Received: from klph001.kcdc.att.com (klph001.kcdc.att.com [135.188.3.11]) by flph161.enaf.ffdc.sbc.com (8.14.3/8.14.3) with ESMTP id mAFHtKR6029661 for ; Sat, 15 Nov 2008 09:55:21 -0800 Received: from kcdc.att.com (localhost.localdomain [127.0.0.1]) by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id mAFHtKI4020677 for ; Sat, 15 Nov 2008 11:55:20 -0600 Received: from ulysses.homer.att.com (ulysses.homer.att.com [135.205.193.8]) by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id mAFHtDK9020605 for ; Sat, 15 Nov 2008 11:55:13 -0600 Received: from hera.homer.att.com (hera.homer.att.com [135.205.193.102]) by ulysses.homer.att.com (8.9.3/8.9.3) with ESMTP id MAA03055 for ; Sat, 15 Nov 2008 12:55:12 -0500 (EST) Received: from hera.homer.att.com (localhost [127.0.0.1]) by hera.homer.att.com (8.9.3/8.9.3) with ESMTP id MAA26628 for ; Sat, 15 Nov 2008 12:55:12 -0500 (EST) Message-Id: <200811151755.MAA26628@hera.homer.att.com> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 Nov 2008 12:55:12 -0500 From: "J. W. Ballantine" Subject: _nyssin undefined X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2008 18:22:11 -0000 Hi Yesterday AM, 11/14, I cvs'ed the 7-stable sources and did a system build/install. Now all I get is: /lib/ld-elf.so.1: /lib/libc.so.7: Undefined symbol _nyssin. Other than a reinstall, is there any way to recover from this? Thanks Jim Ballantine From owner-freebsd-stable@FreeBSD.ORG Sat Nov 15 20:18:56 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 192291065680 for ; Sat, 15 Nov 2008 20:18:56 +0000 (UTC) (envelope-from bh@izb.knu.ac.kr) Received: from pinus.izb.knu.ac.kr (pinus.izb.knu.ac.kr [IPv6:2001:470:1f05:5f6:3::1]) by mx1.freebsd.org (Postfix) with ESMTP id C72898FC13 for ; Sat, 15 Nov 2008 20:18:55 +0000 (UTC) (envelope-from bh@izb.knu.ac.kr) Received: from pinus.izb.knu.ac.kr (localhost.izb.knu.ac.kr [127.0.0.1]) by pinus.izb.knu.ac.kr (Postfix) with ESMTP id 363933E98 for ; Sun, 16 Nov 2008 05:18:52 +0900 (KST) Comment: DKIM? See http://www.google.com/search?btnl&q=RFC+4871 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=izb.knu.ac.kr; h=message-id:date:from:mime-version:to:subject:content-type: content-transfer-encoding; s=ujuk; bh=rDDGMULu7sYJLTSWEU8P1U2iEU nUbG559CPNEZVgxCo=; b=i7hcW84RokjY2z+NwPV3hNGU2pxUsPQIsx5zHpT3w5 mWjrOXvEKyiHx4820plCiSzNv4nJ1kZ0akckrJEuJS1WY7sVQVDeuMJEhOpb6X7k +x537OBC8cJXIcT7Vn0zj7fGi0lxfWeTSlwIm+OErBeDEtsDeb4KbWUMkeqsfmmW M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=izb.knu.ac.kr; h=message-id:date :from:mime-version:to:subject:content-type: content-transfer-encoding; q=dns; s=ujuk; b=ND34QO1QAVM+wyXBZW2l yD+Gtc9kgShMq8B6V9hQRqPwvMVO72zGtntMNbq9JfB9aNJa3d+RSEWq/uDV+kQw GReMvLl4jkGQ5qmLvBYM46NTmSjeYDFtjhTTwPTPc63kyyHzKWbrThn9GSEn5LAy wmxCSE1wYxmMme/UyHspm50= Received: from chrys.izb.knu.ac.kr (chrys.izb.knu.ac.kr [IPv6:2001:470:1f05:5f8:3::1]) by pinus.izb.knu.ac.kr (Postfix) with ESMTP id BE8C53E94 for ; Sun, 16 Nov 2008 05:18:51 +0900 (KST) Received: from [118.129.178.63] (unknown [118.129.178.63]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: bh@chrys.izb.knu.ac.kr) by chrys.izb.knu.ac.kr (Postfix) with ESMTP id 25D461CD42 for ; Sun, 16 Nov 2008 05:18:51 +0900 (KST) Message-ID: <491F2EAA.9040405@izb.knu.ac.kr> Date: Sun, 16 Nov 2008 05:18:50 +0900 From: Byung-Hee HWANG Organization: InZealBomb User-Agent: Thunderbird 2.0.0.9 (X11/20080213) MIME-Version: 1.0 To: stable@freebsd.org X-Enigmail-Version: 0.95.7 OpenPGP: id=96B196FE; url=http://izb.knu.ac.kr/~bh/bh.0x96B196FE.pubkey.asc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: [OT] Waiting for 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2008 20:18:56 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When does the official version of 7.1 (7.1-RELEASE) release out? Does it have some critical issue? Or how it goes? Just i'm waiting for 7.1 because of i have some plan with 7.1 personally. Cheer up, Ken and the Release Engineering Team! byunghee -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAkkfLqoACgkQsCouaZaxlv7k4ACeMA8yzbi2dXxAFt5Xcp00wIHd +gkAnAuZv1I019+Ipi0F4VSMH9vjXsvM =Fm2L -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Sat Nov 15 22:13:52 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 398EC106564A for ; Sat, 15 Nov 2008 22:13:52 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from flat.berklix.org (flat.berklix.org [83.236.223.115]) by mx1.freebsd.org (Postfix) with ESMTP id B87408FC23 for ; Sat, 15 Nov 2008 22:13:51 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A726D.dip.t-dialin.net [84.154.114.109]) (authenticated bits=0) by flat.berklix.org (8.13.8/8.13.8) with ESMTP id mAFMDkWv055991; Sat, 15 Nov 2008 23:13:48 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id mAFMDaXU026172; Sat, 15 Nov 2008 23:13:36 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id mAFMDPo8041209; Sat, 15 Nov 2008 23:13:31 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200811152213.mAFMDPo8041209@fire.js.berklix.net> To: Byung-Hee HWANG From: "Julian Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://berklix.com In-reply-to: Your message "Sun, 16 Nov 2008 05:18:50 +0900." <491F2EAA.9040405@izb.knu.ac.kr> Date: Sat, 15 Nov 2008 23:13:25 +0100 Sender: jhs@berklix.org Cc: stable@freebsd.org Subject: Re: [OT] Waiting for 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2008 22:13:52 -0000 Hi, > When does the official version of 7.1 (7.1-RELEASE) release out? Does it > have some critical issue? Or how it goes? Just i'm waiting for 7.1 > because of i have some plan with 7.1 personally. Cheer up, Ken and the > Release Engineering Team! Previously there's been a big ToDO list, I took a quick look to see if I could quote a URL, but only see: http://www.freebsd.org/releases/7.1R/schedule.html lists RC2 builds 29 September 2008 http://www.freebsd.org/releng/index.html November 2008 No matter, re@ will release when ready :-) I'm running 7.1-BETA2 on AMD64, with a load of home built current ports too. No problems with src/, just usual ports/ things. Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org From owner-freebsd-stable@FreeBSD.ORG Sat Nov 15 22:46:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2210D1065677 for ; Sat, 15 Nov 2008 22:46:10 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail11.syd.optusnet.com.au (mail11.syd.optusnet.com.au [211.29.132.192]) by mx1.freebsd.org (Postfix) with ESMTP id AC2428FC12 for ; Sat, 15 Nov 2008 22:46:09 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail11.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id mAFMk5pQ027646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 16 Nov 2008 09:46:07 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id mAFMk4ZY033882; Sun, 16 Nov 2008 09:46:04 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id mAFMk451033881; Sun, 16 Nov 2008 09:46:04 +1100 (EST) (envelope-from peter) Date: Sun, 16 Nov 2008 09:46:04 +1100 From: Peter Jeremy To: "J. W. Ballantine" Message-ID: <20081115224604.GG51761@server.vk2pj.dyndns.org> References: <200811151755.MAA26628@hera.homer.att.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zbGR4y+acU1DwHSi" Content-Disposition: inline In-Reply-To: <200811151755.MAA26628@hera.homer.att.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: _nyssin undefined X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2008 22:46:10 -0000 --zbGR4y+acU1DwHSi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Nov-15 12:55:12 -0500, "J. W. Ballantine" wrote: >Yesterday AM, 11/14, I cvs'ed the 7-stable sources and did a >system build/install. Now all I get is: > /lib/ld-elf.so.1: /lib/libc.so.7: Undefined symbol _nyssin. I don't recognize and can't find that symbol in my (older) 7-STABLE sources so I'm not sure what might have triggered it. However, I don't have ld-elf.so.1 in /lib - it's in /libexec. Is that a typo on your part? At what point do you get that error? Can you get to a single user mode shell? The previous ld-elf.so.1 is saved as /libexec/ld-elf.so.1.old - you can use tools in /rescue to rename it (you will need to use chflags to clear the schg flag on /libexec/ld-elf.so.1 before you can overwrite it). Unfortunately, there's no backup of /lib/libc.so.7 so if that's the problem, you will need to recover it from backups or a live filesystem CD. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --zbGR4y+acU1DwHSi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkfUSwACgkQ/opHv/APuIcgQwCgueEy72NP0szOaz8Gl8AkFUAg 42EAoLpg2TCwP0HCZLlEon3cCfs+daew =zk8S -----END PGP SIGNATURE----- --zbGR4y+acU1DwHSi--